Has anyone tried iodé on the OnePlus 11 yet? (salami · master · ota / release · GitLab) I’m thinking of buying one and am curious to hear people’s experience.
My experience is hours wasted trying the automatic Linux installer which thinks Iode 6.0 will run. Bricked, “orange,” bootloop. I finally figured out how to do the manual install for 5.8 and it’s good so far.
I’m about to try it out now. Wish me luck!
1 Like
Currently in a hard brick state while trying to flash the ROM. Will update my response once I get the device back online.
Perhaps I should have restored factory settings first before attempting.
After testing for about 3hrs, I realised that I could achieve what iode has set out to achieve using rooted stock ROM with Adguard.
Root implementation is also limited to magisk. KernelSU (and I suspect Apatch as well) don’t work.
So, tried 6.5 (and 6.4) on a PHB110. The installer-app did absolutely nothing, which should probably have been my first warning, but I went on to do the flash-all.sh script and now it boots to the iode logo (sometimes with a narrow scribble through) then screen goes black. So far it’s only a soft-brick, but oneplus aren’t generous with their system images (outside OTA), so I have no idea how to revert it.
Anybody know a way of getting hold of a iode 5.8 image today? Gitlab only has 6.4-6.5 AFAICT.
I do see that the iodé shop has a page for the OP11, but since it is out of stock I am not certain if it was sold with a 6.x version (Lineage 22 / A15 base). Are you willing to try stock LineageOS or LineageOS for microG to see if it installs fine on them?
If so maybe we can get more info on if this is an iodé specific issue or a broader issue of Lineage 22 based builds on the OP11.
Thanks for the reply.
I originally didn’t do that because they write in red letters that one must have stock ROM installed. I didn’t have that (and can’t find a way of getting hold of a stock image). Since the phone isn’t functional anyway, I tried, but LineageOS behaves the same way, boots to logo, then goes to blank screen.
I wonder if some part of the original ROM is supposed to be retained and that something got wiped.
OK, since i hijacked this thread, I should probably summarise in case people find it, looking for answers.
Tl;dr: my problem is likely limited to the Chinese PHB110 model. I believe, but do not know for a fact, that the missing piece was writing oplusstanvbk.img from a Chinese ColorOS after install, so overwriting whatever iode had written.
While troubleshooting the failing bootup, I downgraded my phone to OOS 14 (via OOS 13), which allowed me to install /e/ os U (A14). That caused a boot loop, which was fixed by writing oplusstanvbk.img from fastboot.
This thread has a lot of discussion on the issue.
All the degoogled ROMs claim to support the Chinese OnePlus version, which in my infinite cheapness, I had bought. It does seem to make things harder and they should probably not list PHB110 or at least mention the complications.
I haven’t tried installing iodé using the above, so this is at best a hint, not a recipe.