Hello I just tried to install iodeos in my new Pixel 7, the installer didn’t work at all, it just installed the recovery and gave back an error, so it didn’t advance any further.
After waiting for a long time i tried to boot into phone from the recovery and it just become a total dark screen.
I am seeking for advice, what should I do? Volume + Power doesn’t work, nor fastboot, nor anything, all i see is when i connect the phone with the PC, it shows “Google Pixel ROM recovery”
Hi esbardu,
@rik , who knows a lot about installation problems, is probably taking a holiday break right now, and good for him! Meanwhile I suggest that you browse through the forum, where several people had expressed concerns that they might have bricked their phones, but fortunately found a solution to their problems.
You could help by adding a bit more information about your situation: Which OS are you using on your computer? (Windows, Linux, …) Which stock-ROM did the Pixel have? (Android 15, 16?) and so on.
Thanks for your answer!
I am using Linux and i just used the GUI installer. The phone wasn’t opened nor updated so i guess it had Android 15 when I did the process.
About forum search I didn’t find anything useful for a totally bricked phone.
There is a thread with a Pixel 7a user who reports a similar problem, but I have a lot of Pixel install experience and have never faced an actual “hardware bricked” situation.
I do suspect that it had Android 16 on it before installing, which would lead to this install issue, but it could have been a problem with a USB connection or other problem as well, so it is all just speculation until you can get it back to working to try again.
Now to the problem, if the screen is active when connecting to a PC (you say it boots to Google recovery?), then you should be able to use flash.android.com from a Chromium-based browser to reflash Android 15 (using the dropdown to choose older builds or something like that until you find the Android 15 option). You do not need to re-lock the bootloader at the end of that process but it isn’t terrible if you do, you can just unlock again with fastboot flashing unlock.
It wasn’t Android 16 as it wasn’t even opened nor updated.
It doesn’t boot or do anything, but before, when I attached it to my PC it showed “Google recovery” as a pop-up.
Nothing works. It is a total brick. I will stop trying IodeOS completely. I have never had issues installing other custom ROMs, such as CalyxOS or LineageOS, and I have had enough of losing one phone because of a messy installer…
Thanks for nothing.
I do appreciate it is very frustrating, and I can’t say for certain without of course having the phone on hand to check, but again I do doubt the phone is actually “hard bricked.” The difficulty in truly “bricking” is a benefit of working with Pixels. All the Pixels I have purchased in the past 6 months have had Android 16 installed on them (even including a Pixel 6 I recently purchased). The ease in updating them mean that at least any sellers in the USA are flashing to the “newest greatest” before sending them out the door.
But again it isn’t profitable to discuss what was, that is in the past. Certainly something didn’t go well during install but we can’t fully sort out what it was to help. Sorry that the iodé install experience disappointed you.
Anyone who can install LineageOS ( Install LineageOS on
Google Pixel 7 ), can install iodéOS iode-6.9-20251105-panther-fastboot.zip even more easily (using script flash-all.bat / flash-all.sh). It works perfectly, including relocking bootloader.
I’ve flashed all models from Google Pixel 2 to Pixel 9 with iodéOS using fastboot commands, regardless of whether they are official or unofficial ROMs. I’ve not yet managed to “brick” a device.
When an installation goes wrong, users like to blame others and forget their own role in the process.
If you want an answer, you should tell more. Were there any error messages? at which point?