I’m like 75% sure they can use ADB sideload to run scripts, if it’s fixed by a fsck couldn’t they write that into an OTA.zip and sign it with their key so devices will run it? Then all users would have to do is plug it into a website similar to the Pixel Flash Tool they have and boot into fastboot.
I’m not an Android dev, I’ve just installed my fair share of ROMS and I’m just throwing stuff out there and seeing what sticks. Feel free to tell me I’m wrong and a moron
Based on the admittedly sparse technical details we have available, yes, that should fix it. Just waiting on Google to work on it as it needs to be signed with their keys since most people have a locked bootloader. Why it’s taking them so long, I couldn’t say.
I don’t use multiple profiles, but couldn’t those with bootlooping devices flash the OTA from recovery?
According to this twitter, the data partition needs an fsck: https://twitter.com/MishaalRahman/status/1721945205119553794
And people have tried the Nov OTA image, it didn’t help: https://issuetracker.google.com/u/1/issues/305766503#comment843
Yikes, the situation is worse than I thought.
I’m like 75% sure they can use ADB sideload to run scripts, if it’s fixed by a fsck couldn’t they write that into an OTA.zip and sign it with their key so devices will run it? Then all users would have to do is plug it into a website similar to the Pixel Flash Tool they have and boot into fastboot.
I’m not an Android dev, I’ve just installed my fair share of ROMS and I’m just throwing stuff out there and seeing what sticks. Feel free to tell me I’m wrong and a moron
Based on the admittedly sparse technical details we have available, yes, that should fix it. Just waiting on Google to work on it as it needs to be signed with their keys since most people have a locked bootloader. Why it’s taking them so long, I couldn’t say.