You guys really need to work on your documentation. I couldn’t find any installation instructions on the xda thread I discovered iode on and the instructions on the gitlab page that it linked to are incredibly scarce and ultimately of no value.
As part of my reading on iode I saw one of the major selling points being the locked bootloader. So after the installer finished doing its thing, I said hell yeah I wanna lock my bootloader. And now I’m stuck in fastboot. Interestingly enough, I was able to unlock the bootloader again very easily (I always thought it was such a hassle and this scary thing but no, I’ve been toggling it on and off like a light switch. Huh).
Unlocking status is 1. Switched back and forth between slots. Can access recovery and adb sideload, tried that too. Nothing.
I went through a bunch of reddit and forum posts trying what was suggested to them to no avail. One comment from this forum actually suggested that it could be FRP getting triggered to prevent downgrading. That makes perfect sense because I’m coming from PixelDust ROM (Android 13) and the installer probably assumed I was running the last official stock version which would include much older security updates. The official iode version I downloaded was 4, so I downloaded the latest one 5. No difference.
I’m currently downloading the last stock factory image for this old Pixel 3 as a hail mary while I wait for someone here to hopefully help me. And for the love of Android please work on your docs. I’ll gladly help out if my Pixel 3 gets successfully unblocked and running iode.
Erasing 'avb_custom_key' OKAY [ 0.407s]
Finished. Total time: 0.534s
Warning: skip copying avb_custom_key image avb footer (avb_custom_key partition size: 0, avb_custom_key image size: 1032).
Sending 'avb_custom_key' (1 KB) OKAY [ 0.111s]
Writing 'avb_custom_key' OKAY [ 0.219s]
Finished. Total time: 0.703s
Warning: metadata type is raw, but ext4 was requested for formatting.
mke2fs 1.46.6 (1-Feb-2023)
Creating filesystem with 4096 4k blocks and 4096 inodes
Allocating group tables: done
Writing inode tables: done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: done
Warning: skip copying metadata image avb footer due to sparse image.
Sending 'metadata' (52 KB) OKAY [ 0.113s]
Writing 'metadata' OKAY [ 0.063s]
Finished. Total time: 0.629s
Erasing 'metadata' OKAY [ 0.126s]
Finished. Total time: 0.250s
Warning: userdata type is raw, but f2fs was requested for formatting.
F2FS-tools: mkfs.f2fs Ver: 1.16.0 (2023-04-11)
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 = 108167128 (52815 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: 638] Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 672] Filling nat area at offset 0x00a00000
[f2fs_add_default_dentry_root:1255] Writing default dentry root, at offset 0x16400
[f2fs_write_root_inode:1300] Writing root inode (hot node), offset 0x15e00
[f2fs_write_default_quota:1387] Writing quota data, at offset 00016401 (1/2)
[f2fs_write_default_quota:1387] Writing quota data, at offset 00016402 (2/2)
[f2fs_write_qf_inode:1438] Writing quota inode (hot node), offset 0x15e01
[f2fs_write_default_quota:1387] Writing quota data, at offset 00016403 (1/2)
[f2fs_write_default_quota:1387] Writing quota data, at offset 00016404 (2/2)
[f2fs_write_qf_inode:1438] Writing quota inode (hot node), offset 0x15e02
[f2fs_write_default_quota:1387] Writing quota data, at offset 00016405 (1/2)
[f2fs_write_default_quota:1387] Writing quota data, at offset 00016406 (2/2)
[f2fs_write_qf_inode:1438] Writing quota inode (hot node), offset 0x15e03
[f2fs_update_nat_default:1475] Writing nat root, at offset 0x00000a00
Info: Overprovision ratio = 0.630%
Info: Overprovision segments = 167 (GC reserved = 165)
[f2fs_write_check_point_pack: 854] Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack: 942] Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack: 956] Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack: 968] Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack: 979] Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack: 987] Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack:1007] Writing NAT bits pages, at offset 0x000003fe
[f2fs_write_check_point_pack:1028] Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack:1047] Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1080] Writing super block, at offset 0x00000000
Info: format successful
Warning: skip copying userdata image avb footer due to sparse image.
Sending 'userdata' (97 KB) OKAY [ 0.114s]
Writing 'userdata' OKAY [ 0.067s]
Finished. Total time: 0.791s
Erasing 'userdata' OKAY [ 8.890s]
Finished. Total time: 9.015s
Sending 'modem_b' (71468 KB) OKAY [ 1.926s]
Writing 'modem_b' FAILED (remote: 'Not allowed to flash (modem_b)')
fastboot: error: Command failed
--------------------------------------------
Bootloader Version...: b1c1-0.4-7617406
Baseband Version.....: g845-00194-210812-B-7635520
Serial Number........: 8BCX1806L
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.057s]
Setting current slot to 'b' OKAY [ 0.075s]
extracting fastboot-info.txt (0 MB) to RAM...
extracting super_empty.img (0 MB) to RAM...
extracting super_empty.img (0 MB) to disk... took 0.000s
extracting super_empty.img (0 MB) to RAM...
extracting super_empty.img (0 MB) to RAM...
extracting super_empty.img (0 MB) to RAM...
extracting super_empty.img (0 MB) to RAM...
extracting super_empty.img (0 MB) to RAM...
extracting super_empty.img (0 MB) to RAM...
extracting super_empty.img (0 MB) to RAM...
extracting super_empty.img (0 MB) to RAM...
extracting super_empty.img (0 MB) to RAM...
extracting super_empty.img (0 MB) to RAM...
extracting boot.img (64 MB) to disk... took 0.286s
archive does not contain 'boot.sig'
extracting super_empty.img (0 MB) to RAM...
Sending 'boot_b' (65536 KB) OKAY [ 1.787s]
Writing 'boot_b' OKAY [ 0.383s]
extracting super_empty.img (0 MB) to RAM...
extracting dtbo.img (8 MB) to disk... took 0.039s
archive does not contain 'dtbo.sig'
extracting super_empty.img (0 MB) to RAM...
Sending 'dtbo_b' (8192 KB) OKAY [ 0.307s]
Writing 'dtbo_b' OKAY [ 0.099s]
extracting super_empty.img (0 MB) to RAM...
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
extracting super_empty.img (0 MB) to RAM...
Sending 'vbmeta_b' (8 KB) OKAY [ 0.118s]
Writing 'vbmeta_b' OKAY [ 0.065s]
Rebooting into fastboot OKAY [ 0.059s]
< waiting for any device >
extracting super_empty.img (0 MB) to disk... took 0.001s
Sending 'super' (4 KB) OKAY [ 0.002s]
Updating super partition FAILED (remote: 'Cannot find super, build may be missing broken or missing boot_devices')
fastboot: error: Command failed
is-userspace: yes
Sending 'abl_b' (1024 KB) OKAY [ 0.029s]
Writing 'abl_b' OKAY [ 0.020s]
Finished. Total time: 0.066s
Sending 'aop_b' (184 KB) OKAY [ 0.006s]
Writing 'aop_b' OKAY [ 0.003s]
Finished. Total time: 0.029s
Sending 'cmnlib64_b' (492 KB) OKAY [ 0.014s]
Writing 'cmnlib64_b' OKAY [ 0.004s]
Finished. Total time: 0.033s
Sending 'cmnlib_b' (372 KB) OKAY [ 0.011s]
Writing 'cmnlib_b' OKAY [ 0.004s]
Finished. Total time: 0.029s
Sending 'devcfg_b' (40 KB) OKAY [ 0.001s]
Writing 'devcfg_b' OKAY [ 0.002s]
Finished. Total time: 0.018s
Sending 'hyp_b' (388 KB) OKAY [ 0.010s]
Writing 'hyp_b' OKAY [ 0.033s]
Finished. Total time: 0.063s
Sending 'keymaster_b' (216 KB) OKAY [ 0.006s]
Writing 'keymaster_b' OKAY [ 0.009s]
Finished. Total time: 0.028s
Sending 'qupfw_b' (64 KB) OKAY [ 0.002s]
Writing 'qupfw_b' OKAY [ 0.002s]
Finished. Total time: 0.018s
Sending 'tz_b' (1996 KB) OKAY [ 0.053s]
Writing 'tz_b' OKAY [ 0.022s]
Finished. Total time: 0.096s
Sending 'xbl_config_b' (96 KB) OKAY [ 0.003s]
Writing 'xbl_config_b' OKAY [ 0.005s]
Finished. Total time: 0.023s
Sending 'xbl_b' (3584 KB) OKAY [ 0.099s]
Writing 'xbl_b' OKAY [ 0.037s]
Finished. Total time: 0.149s
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.003s
< waiting for any device >
OKAY [ 0.097s]
Finished. Total time: 0.098s
This is a strange one. The only command I’ve tried that I haven’t been able to run.
fastboot --disable-verity --disable-verification
fastboot: usage: no command
Hi I’m happy to not be alone to have this problem, if you have the bootloader unlocked you could go there (use chromium base browser) : Android Flash Tool
It will reinstall google base os and you should be able to use your phone again unlike me );
Well this is interesting. I assumed this wouldn’t work because I was running Android 13 but I got hit with this instead:
Idk maybe reboot the computer
If you are on linux it may be permission issues
1 Like
Man. It never ceases to amaze me just how often “turn it off and back on again” actually fixes things.
Restarting the computer made Android Flash Tool work. After flashing stock and running the installer, I got stuck at fastboot again but I managed to make iode boot.
In your case, are you able to reach fastboot? Why can’t you unlock the bootloader? And even if you can’t, AFT detected my phone in fastboot (or maybe it was bootloader/fastbood, I can’t remember) so you don’t have to be in recovery/ADB for it to work.
Celebrated too soon. I bricked it again.
I spent 3 hours setting it all up, logging into stuff, downloading apps and everything, but the 5.0 update wouldn’t work. It would download in the updater but when I hit install it would blink and do nothing. Stayed stuck on “waiting for first boot”, though sometimes it said “error” until I hit install again.
The really weird part is that even though I enabled adb, the notification wouldn’t show up. It would show up briefly upon boot but when I go to click it it would disappear.
So I tried to flash the update manually via recovery. Nope. Kept giving me a “installdeviceopenerror”. So I tried fastboot. And now I’m stuck in fastboot again.
I was somehow able to flash an official Android 14 build. Installed successfully but wouldn’t boot. Flashing iode 5 after it hasn’t helped. The boot animation of AFT’s Android 14 build lasts quite a while before looping though. Hopefully this info means something to someone that can help me understand what’s going on and how to fix it. Until then I guess I’m sticking with iode 4.
That last AFT thing (idk anything about AFT btw) was flashing a GSI. It may have messed with vbmeta.img but without log who knows.
Step 1: I recommend getting your phone back to a normal stock state by manually flashing the penultimate google build from the Factory Images page and going no further until you have it running.
Get full log from terminal after flashing (the one above is missing a chunk).
Step 2:Update with the last OTA from the google OTA images page.
1 Like
Yes I’ve done that a bunch of times so far. That’s the easy part. What I want to do is run iode 5, not stock Android 12. Where I get into trouble is the update from 4 to 5. Though after the gsi flash I haven’t even been able to get 4.
Edit: Sorry I just noticed you said penultimate and then OTA update. What good would that do? Don’t I want to be on the latest possible security update?
It would return your phone to a “normal” stock state where it’s google both slots with current slot updated to final google build. That’s the ideal base for moving on to iode or lineage.
Take care to set usb debugging and get the confirmation on phone each time.
No. See LOS instructions for some relevant info.
A fixed build of Pixel 3 has been published. We are very sorry for the inconvenience.
2 Likes
Thanks! That worked perfectly. Now I see how smooth the experience is supposed to be lol
