Pixel 7 Bootloop & Rooting

Operating System
1

I am failing to install iode on my pixel 7 (panther).
The install console output seems to indicate everything is ok but after the install the device bootloops.
Log:

Sending ‘bootloader_b’ (12544 KB) OKAY [ 0.130s]
Writing ‘bootloader_b’ (bootloader) Flashing pack version cloudripper-1.0-9894666
(bootloader) flashing platform gs201
(bootloader) Validating partition ufs
(bootloader) Validating partition ufs
(bootloader) Validating partition ufs
(bootloader) Validating partition partition:0
(bootloader) Validating partition partition:1
(bootloader) Validating partition partition:2
(bootloader) Validating partition partition:3
(bootloader) Validating partition bl1_b
(bootloader) Validating partition pbl_b
(bootloader) Validating partition bl2_b
(bootloader) Validating partition abl_b
(bootloader) Validating partition bl31_b
(bootloader) Validating partition tzsw_b
(bootloader) Validating partition gsa_b
(bootloader) Validating partition ldfw_b
(bootloader) Flashing partition ufs
(bootloader) Flashing partition ufs
(bootloader) Flashing partition ufs
(bootloader) Flashing partition partition:0
(bootloader) Flashing partition partition:1
(bootloader) Flashing partition partition:2
(bootloader) Flashing partition partition:3
(bootloader) Flashing partition bl1_b
(bootloader) Flashing partition pbl_b
(bootloader) Flashing partition bl2_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition bl31_b
(bootloader) Flashing partition tzsw_b
(bootloader) Flashing partition gsa_b
(bootloader) Flashing partition ldfw_b
(bootloader) Loading sideload ufsfwupdate
OKAY [ 0.598s]
Finished. Total time: 0.782s
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.018s
< waiting for any device >
Sending ‘radio_b’ (78312 KB) OKAY [ 1.104s]
Writing ‘radio_b’ (bootloader) Flashing pack version g5300g-230323-230525-M-10200345
(bootloader) Flashing partition modem_b
OKAY [ 0.171s]
Finished. Total time: 1.453s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.044s
< waiting for any device >
Erasing ‘avb_custom_key’ (bootloader) avb custom key: erase done
OKAY [ 0.030s]
Finished. Total time: 0.104s
Sending ‘avb_custom_key’ (1 KB) OKAY [ 0.001s]
Writing ‘avb_custom_key’ (bootloader) avb custom key: flash done
OKAY [ 0.029s]
Finished. Total time: 0.042s
Warning: userdata type is raw, but f2fs was requested for formatting.

F2FS-tools: mkfs.f2fs Ver: 1.14.0 (2020-08-24)

Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Enable Project quota
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 230502568 (112550 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
Info: add quota type = 2 => 6
Info: format version with
“”
[f2fs_init_sit_area: 626] Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 660] Filling nat area at offset 0x00e00000
[f2fs_write_root_inode:1274] Writing root inode (hot node), 1d200 0 200 at offset 0x00119296
[f2fs_write_default_quota:1350] Writing quota data, at offset 0001d801, 0001d802
[f2fs_write_qf_inode:1407] Writing quota inode (hot node), 1d200 0 200 at offset 0x00119297
[f2fs_write_default_quota:1350] Writing quota data, at offset 0001d803, 0001d804
[f2fs_write_qf_inode:1407] Writing quota inode (hot node), 1d200 0 200 at offset 0x00119298
[f2fs_write_default_quota:1350] Writing quota data, at offset 0001d805, 0001d806
[f2fs_write_qf_inode:1407] Writing quota inode (hot node), 1d200 0 200 at offset 0x00119299
[f2fs_update_nat_root:1461] Writing nat root, at offset 0x00000e00
[f2fs_add_default_dentry_root:1658] Writing default dentry root, at offset 0x0001d800
Info: Overprovision ratio = 0.600%
Info: Overprovision segments = 675 (GC reserved = 341)
[f2fs_write_check_point_pack: 819] Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack: 975] Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack:1002] Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack:1014] Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack:1025] Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack:1033] Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack:1053] Writing NAT bits pages, at offset 0x000003fe
[f2fs_write_check_point_pack:1074] Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack:1093] Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1126] Writing super block, at offset 0x00000000
Info: format successful
Sending ‘userdata’ (97 KB) OKAY [ 0.002s]
Writing ‘userdata’ OKAY [ 0.210s]
Finished. Total time: 1.531s

Bootloader Version…: cloudripper-1.0-9894666
Baseband Version…: g5300g-230323-230525-B-10200345
Serial Number…: 34131FDH20076C

extracting android-info.txt (0 MB) to RAM…
Checking ‘product’ OKAY [ 0.001s]
Setting current slot to ‘b’ OKAY [ 0.071s]
extracting boot.img (64 MB) to disk… took 0.332s
archive does not contain ‘boot.sig’
Sending ‘boot_b’ (65536 KB) OKAY [ 0.625s]
Writing ‘boot_b’ OKAY [ 0.080s]
extracting init_boot.img (8 MB) to disk… took 0.100s
archive does not contain ‘init_boot.sig’
Sending ‘init_boot_b’ (8192 KB) OKAY [ 0.083s]
Writing ‘init_boot_b’ OKAY [ 0.015s]
extracting dtbo.img (16 MB) to disk… took 0.109s
archive does not contain ‘dtbo.sig’
Sending ‘dtbo_b’ (16384 KB) OKAY [ 0.171s]
Writing ‘dtbo_b’ OKAY [ 0.023s]
archive does not contain ‘dt.img’
extracting pvmfw.img (1 MB) to disk… took 0.016s
archive does not contain ‘pvmfw.sig’
Sending ‘pvmfw_b’ (1024 KB) OKAY [ 0.011s]
Writing ‘pvmfw_b’ OKAY [ 0.004s]
archive does not contain ‘recovery.img’
extracting vbmeta.img (0 MB) to disk… took 0.002s
archive does not contain ‘vbmeta.sig’
Sending ‘vbmeta_b’ (12 KB) OKAY [ 0.001s]
Writing ‘vbmeta_b’ OKAY [ 0.002s]
extracting vbmeta_system.img (0 MB) to disk… took 0.001s
archive does not contain ‘vbmeta_system.sig’
Sending ‘vbmeta_system_b’ (4 KB) OKAY [ 0.001s]
Writing ‘vbmeta_system_b’ OKAY [ 0.003s]
extracting vbmeta_vendor.img (0 MB) to disk… took 0.003s
archive does not contain ‘vbmeta_vendor.sig’
Sending ‘vbmeta_vendor_b’ (4 KB) OKAY [ 0.002s]
Writing ‘vbmeta_vendor_b’ OKAY [ 0.003s]
extracting vendor_boot.img (64 MB) to disk… took 0.289s
archive does not contain ‘vendor_boot.sig’
Sending ‘vendor_boot_b’ (65536 KB) OKAY [ 0.694s]
Writing ‘vendor_boot_b’ OKAY [ 0.084s]
extracting vendor_kernel_boot.img (64 MB) to disk… took 0.247s
archive does not contain ‘vendor_kernel_boot.sig’
Sending ‘vendor_kernel_boot_b’ (65536 KB) OKAY [ 0.711s]
Writing ‘vendor_kernel_boot_b’ OKAY [ 0.078s]
extracting super_empty.img (0 MB) to disk… took 0.001s
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Sending ‘super’ (5 KB) OKAY [ 0.007s]
Updating super partition OKAY [ 0.004s]
Resizing ‘product_b’ OKAY [ 0.005s]
Resizing ‘system_b’ OKAY [ 0.005s]
Resizing ‘system_dlkm_b’ OKAY [ 0.005s]
Resizing ‘system_ext_b’ OKAY [ 0.006s]
Resizing ‘system_a’ OKAY [ 0.006s]
Resizing ‘vendor_b’ OKAY [ 0.011s]
Resizing ‘vendor_dlkm_b’ OKAY [ 0.006s]
Resizing ‘vendor_a’ OKAY [ 0.008s]
archive does not contain ‘boot_other.img’
archive does not contain ‘odm.img’
archive does not contain ‘odm_dlkm.img’
extracting product.img (1148 MB) to disk… took 7.454s
Invalid sparse file format at header magic
archive does not contain ‘product.sig’
Resizing ‘product_b’ OKAY [ 0.010s]
Sending sparse ‘product_b’ 1/5 (261988 KB) OKAY [ 1.412s]
Writing ‘product_b’ OKAY [ 0.301s]
Sending sparse ‘product_b’ 2/5 (262056 KB) OKAY [ 1.441s]
Writing ‘product_b’ OKAY [ 0.265s]
Sending sparse ‘product_b’ 3/5 (261912 KB) OKAY [ 1.464s]
Writing ‘product_b’ OKAY [ 0.285s]
Sending sparse ‘product_b’ 4/5 (262000 KB) OKAY [ 1.465s]
Writing ‘product_b’ OKAY [ 0.305s]
Sending sparse ‘product_b’ 5/5 (123456 KB) OKAY [ 0.737s]
Writing ‘product_b’ OKAY [ 0.176s]
extracting system.img (851 MB) to disk… took 5.526s
Invalid sparse file format at header magic
archive does not contain ‘system.sig’
Resizing ‘system_b’ OKAY [ 0.007s]
Sending sparse ‘system_b’ 1/4 (262108 KB) OKAY [ 1.378s]
Writing ‘system_b’ OKAY [ 0.279s]
Sending sparse ‘system_b’ 2/4 (262104 KB) OKAY [ 1.444s]
Writing ‘system_b’ OKAY [ 0.300s]
Sending sparse ‘system_b’ 3/4 (262004 KB) OKAY [ 1.468s]
Writing ‘system_b’ OKAY [ 0.266s]
Sending sparse ‘system_b’ 4/4 (82444 KB) OKAY [ 0.466s]
Writing ‘system_b’ OKAY [ 0.126s]
extracting system_dlkm.img (0 MB) to disk… took 0.002s
archive does not contain ‘system_dlkm.sig’
Resizing ‘system_dlkm_b’ OKAY [ 0.005s]
Sending ‘system_dlkm_b’ (340 KB) OKAY [ 0.003s]
Writing ‘system_dlkm_b’ OKAY [ 0.037s]
extracting system_ext.img (484 MB) to disk… took 3.289s
Invalid sparse file format at header magic
archive does not contain ‘system_ext.sig’
Resizing ‘system_ext_b’ OKAY [ 0.008s]
Sending sparse ‘system_ext_b’ 1/2 (262056 KB) OKAY [ 1.446s]
Writing ‘system_ext_b’ OKAY [ 0.306s]
Sending sparse ‘system_ext_b’ 2/2 (226087 KB) OKAY [ 1.796s]
Writing ‘system_ext_b’ OKAY [ 0.421s]
extracting system_other.img (21 MB) to disk… took 0.191s
archive does not contain ‘system.sig’
Resizing ‘system_a’ OKAY [ 0.011s]
Sending ‘system_a’ (22496 KB) OKAY [ 0.138s]
Writing ‘system_a’ OKAY [ 0.068s]
extracting vendor.img (652 MB) to disk… took 4.058s
Invalid sparse file format at header magic
archive does not contain ‘vendor.sig’
Resizing ‘vendor_b’ OKAY [ 0.006s]
Sending sparse ‘vendor_b’ 1/3 (262116 KB) OKAY [ 1.416s]
Writing ‘vendor_b’ OKAY [ 0.296s]
Sending sparse ‘vendor_b’ 2/3 (260780 KB) OKAY [ 1.459s]
Writing ‘vendor_b’ OKAY [ 0.293s]
Sending sparse ‘vendor_b’ 3/3 (140980 KB) OKAY [ 0.797s]
Writing ‘vendor_b’ OKAY [ 0.172s]
extracting vendor_dlkm.img (40 MB) to disk… took 0.278s
archive does not contain ‘vendor_dlkm.sig’
Resizing ‘vendor_dlkm_b’ OKAY [ 0.011s]
Sending ‘vendor_dlkm_b’ (41784 KB) OKAY [ 0.245s]
Writing ‘vendor_dlkm_b’ OKAY [ 0.078s]
archive does not contain ‘vendor_other.img’
Finished. Total time: 81.442s
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.022s
< waiting for any device >
OKAY [ 0.216s]
Finished. Total time: 0.219s
Press any key to exit…

Afterwards I select to not lock the bootloader (I intend to root it).
The same behavior is with both iode-4.8-20231213-panther-fastboot and iode-4.8-20231217-panther-fastboot.
For the context: I was running grapheneos originally. I went back to stock google image first (following the graphene recommendations and using googles web-flashing utility). Stock ran fine.

Any hints on what to try next. Has anyone had success with the pixel7 image yet?

2

Try hard holding vol down as it bootloops , to try and get back to fastboot mode. Then try selecting recovery from the fastboot menu. If it boots into iode recovery, try factory reset.

3

BTW did you go back to stock 13.0.0 (TQ3A.230901.001, Sep 2023) ? Actually, I’m not sure it matters anymore.

7a lynx is running fine for me.

4

That did the trick! I’m very grateful for the suggestion :slight_smile: Have a nice Christmas

5

Excellent!

And the same to you. :grinning:

6

Actually follow-up question. Has anyone succeeded in rooting iode. I read a while back that this should be possible but I keep failing :slight_smile:
Recovery doesn’t allow to ignore the bad signature.
Any attempt to patch boot.img is overwritten even if I also reflash vbmeta with the disable verification option. Background: I need the android auto patch: GitHub - sn-00-x/aa4mg: Android Auto 4 microG

7

I rooted lynx whilst on unofficial lineage some time ago.

Follow the official magisk guide to patch init_boot.img.

Recovery not recommended by magisk for a long time now.

Don’t think I flashed vbmeta.

8

I use a Pixel 7a with Iodé. Rooting with Magisk worked well. I patched the init_boot.img and flashed the patched img with adb sideload.
(init-boot.img extracted from iode-4.7-20231209-lynx-fastboot.zip → iode-4.7-20231209-lynx-img.zip → )
After the OTA update root got lost so I had to flash again the patched init_boot.img.
I didn’t touch vbmeta.

1 Like
9

OK, but from memory I think there is a routine to update ota without losing root. It’s a bit of a process but it worked for me back in the day. I’ll get the link.

TLDR for the following link would be to scroll to the section " How to Install OTA Updates on Rooted Android Devices?"

1 Like
10

Thanks. I did the whole process again from the start and this time around rooting worked. I guess the patch wasn’t properly applied the first time round.