I recently installed iodeos 6.1 on google pixel 5 but everytime I open developer options the settings app crashes. Any help please?
I am on a Pixel 3a XL (bonito) with iodé 6.1 and haven‘t had a problem enabling developer options, so it at least isn’t an universal issue.
Was this a new install, or an upgrade? How did you install?
I have also confirmed no issues enabling developer options on a Pixel 6a and a Pixel 7 Pro, is it still an issue for you?
I have this problem on my pixel 3a with the latest build. I also had the same problem with my pixel 8 pro when I tested about 3 months ago. It seems to be an issue just with iodéos for me. Shame because I wanted a microg os with also android auto. @rik
So you enable Developer Options (tap 7 times on build number) but when attempting to open it, the Settings app crashes / closes? No issues here on a Pixel 3a XL, which is essentially identical to a Pixel 3a (just a physically larger display, but even the same display resolution and driver, etc).
@rik I’ve uninstalled and gone back to regular lineage4microg but what I did on a clean install, was tap 7 times on build number, go to system and then when I click on developers settings then the settings app just closes. There’s no error on the screen or anything. The same thing happened on my pixel 8 pro a few months ago and that scared the life out of me because the bootloader was locked after flashing!
@Xander2m you can’t try anymore, but I did find this comment on xda suggesting that a possible fix is this:
System Settings > Apps > Special app access > Modify system settings > "3 dots" > Show system > Secure UI Service > Toggle "Allow modifying system settings"
I certainly haven’t seen this before as being necessary, but worth a check? @Cadoum2511 I don’t know if you switched to a different ROM, but worth a check if you still are stuck on this.
1 Like
I’ll have a go later and report back! I will be pleased if it does work as with the Calyxos uncertainty I would like somewhere good that allows a locked bootloader on my 8 pro
So the special app setting is already allowed on a clean install (on pixel 3a).
I also can’t set a new screen lock “screen lock was already changed. Try again with the new screen lock”. @rik
These errors are all very strange. Did you do a factory reset before install or attempt to keep userdata (aka a “dirty flash”)?
No. I installed the recovery img, factory reset, installed the 6.6 zip via adb and booted. The only other thing I can think of doing is flashing stock android before installing iodeos. I was on lineageos before testing.
I have this issue too on a Pixel 8 Pro. Installed Iode latest using the App from Windows. Previously running stock OEM Android, and didn’t try to save any data or restore anything. Didn’t install a SIM card.
I re-enabled the bootloader lock too. Does this prevent me from changing to a different ROM?!
Also couldn’t set a Screen Lock, same message as other comment. So iode is pretty useless to me. Hoping it hasn’t made my phone useless too.
Also couldn’t get the installer app to work on Debian. Think it relies on too new a version of glibc?
Getting my phone back, is my main concern atm.
1 Like
This would prevent you from changing ROMs until you unlock it again (which will wipe your userdata).
To both of your issues, I think you should try re-installing, even though it seems like insanity. The inability to set a screen lock to me is an indication that something isn’t right, but I am sure we have other Pixel 8 Pro users that have installed (using the installer) without this issue, and also there are other Pixel 3a users that I haven’t seen report this problem.
The installer one (P8P) has me baffled, as it does a full reset of both the a/b slots, it should be comprehensive.
I’ll try to see if others on the telegram / matrix channel can give any feedback.
1 Like
@rik Thanks for responding.
Unfortunately I can’t reinstall as I can’t get into the Developer Options without the Settings either not resounding or crashing. That’s what’s worrying me.
Have I go any other options? I was able to get into fastboot and unlock my bootloader.
You shouldn’t need developer settings to install, you just need the unlocked bootloader. Sorry it isn’t running on Debian due to the dependency issue, I hate having to suggest Windows to anyone 
You can use the flash-all.sh script, it may be more informative than using the graphical installer. You want the fastboot version: husky · master · ota / release · GitLab Extract the .zip then inspect the flash-all.sh script and then launch it from within a terminal to proceed.
1 Like
Looks good now : )
2 Likes
Did you just reflash from the latest android 15 at flash,android.com? On your pixel 8 pro?
1 Like
@sam yes please give us a bit more detail on how you solved the problems, this way others will benefit as well if they have the issue
I was able to unlock the bootloader again using fastboot as it was still unlockable.
Then reflashed Android 16 stable from here:
gsi_gms_arm64-exp-BP2A.250605.031.A3-13578795-38e52cb0.zip
Think I needed to come out of fastbootd first?
$ fastboot reboot fastboot
$ fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
$ fastboot flash system system.img
$ fastboot reboot
This might not have been necessary, but it reassured me that I could have a working phone again.
Then I downloaded Iode:
iode-6.6-20250729-husky-fastboot.zip
$ flash-all.sh
$ fastboot flashing lock
I’ve left out unzipping instructions and the fun and games of getting my phone in and out of recovery mode and fastbootd/fastboot. I had no adb access until I reflashed Android GSI but I didn’t really need it. And I had to relock the bootloader myself after reflashing Iode using the script.
I would be a bit concerned just flashing the gsi rather than the actual full husky Google build, as that wouldn‘t reset the partitions, proprietary blobs, etc. that Lineage and iodé will assume are in place. But if it works it works I guess, right?
So, does it work???