But that is not specific to GSI builds. Are you suggesting that all builds should be named e.g. iode-5.5-microG-noSU-20240617-lilac.zip? Or maybe, to be clearer for people who want to install IodéOS wthout finding out what it is , iode-5.5-microG-noGAPPS-noSU-built-in-blocker-and-vpn-including-fdroid-and-aurora-store-20240617-lilac.zip 
Have you try this???
or this
Or better use latest SPFT from here
I am using product_gsi.img
But that doesn’t solve my problem N°1: After fastboot reboot fastboot = fastboot’D’ the bootloader is suddenly locked again as if by magic(!)
As I wrote before, it is described here that microG is integrated into iodéOS ota / ota · GitLab
The long name is not nice 
Rather, as in my last post, either bfvN or what I would find better bmvN
By the way, it is no longer a ZIP, but IMG.xz 
I can’t find anything about these two devices Telekom T Phone 2 5G Puma
Telekom T Phone Pro Lion
I assume that it is blocked by the Telekom to open the bootloader 
Hello.
I tried this GSI on my Ulefone Armor 26 Ultra, and it works well. Latest version has a problem logging into Aurora Store, but earlier one marked Beta is good.
I was wondering if it is possible to include a system app from my phone to use the 2-way radio (Walkie Talkie) feature. How would I go about setting that up?
Yes, I suspect that too. The future for custom operating systems looks bleak, because more and more device manufacturers are blocking the unlocking of the bootloader.
Deutsche Telekom proudly reports:
Together with Google, Deutsche Telekom and T-Mobile US have developed 5G-enabled smartphones for the European market. The T Phone and T Phone Pro are based on the established “REVVL” product range from T-Mobile US.
The new T Phone 2 devices are the second generation of models that are developed in partnership with Google.
Goolag is evil.
Hi everybody,
Wow! One of the best GSIs I’ve tried so far. It’s stable, the battery life is good, and after some configurations, everything I need is working pretty nicely!
My device is a Samsung Galaxy S20 FE 5G, by the way, with the 4.19 kernel.
What’s working that always caused issues on other GSIs?
- Bluetooth
- all Sensors
- all Cameras with the correct GCam and config file
- SMS!
- Signal Bar
- SD Card
What’s missing (mostly personal preferences)
- more back gesture options (I would love to toggle the torch with “long back gesture” or to open Notification Panel with “left+down back gesture”)
Bugs I may have found a fix for:
- Setting “Allow Background Usage” to “off” sometimes doesn’t work; it just reverts to “on” after leaving the screen and returning.
- After a few tries, it randomly works (sometimes).
- Logcat says:
java.lang.SecurityException: Specified package “com.Slack” under uid 10248 but it is not
- If I do it via “Settings → Apps → App Battery Usage → select app”, it works, but when I check it via “long press on app → App Info → App Battery Usage”, it’s still set to “on”.
- I’ve only encountered this with WhatsApp and Slack (and maybe only after reinstalling them).
- (and yes I know WhatsApp is evil…)
Some tips and tricks for people with similar issues (it took me a while to figure these out):
-
Aurora Store and WhatsApp: I couldn’t log into Aurora (neither anonymously nor with an account), and WhatsApp couldn’t register or act as a linked device.
- Reason: brand and model aren’t set in build.props
- Solution: Use Magisk with the “MagiskHide Props Config” module. I tested “Device Simulation” with no luck, so I added custom props:
ro.product.brand=Samsungro.product.model=G781
- These values make sense for my device; you might need to use others depending on your device.
- Not sure if this can be fixed by the development team?
- just saw, that @clewis.it seems to have the same problem with the Aurora Store, maybe this helps?
-
microG Coarse Location not working
- Reason: Mozilla ended their location service
- Solution: Turn off both Mozilla options in “System → microG Settings → Location” and, in the three-dot menu, enter:
https://api.positon.xyz/?key=74600654-2aec-11ef-aa95-3b7218da6865
- Now, location via hotspots or cell towers should work again.
- Cached locations allow for some kind of offline functionality for places you’ve already visited.
- The microG team is working on an importable offline database solution, similar to how it was done with UnifiedNlp before.
- Source: Mozilla Location Service is retiring · Issue #2237 · microg/GmsCore · GitHub
That’s all from me for now. I hope more versions of this really fine GSI will be provided! I’ve heard a lot about iodé, and I’m really happy to be using it now!
Hey, thanks for sharing your detailed experience and tips.
Does GSI OTA update work for you - compare with System update available > Preparing system update > New update failed to be installed
It’s exactly the same for me. Maybe the Logs could help?
More detailed Log
1727735916.059 1000 6165 6165 E PHH : Device variant is: lineage_arm64_ab
1727735916.059 1000 6165 6165 E PHH : Security patch date: 2024-09-05
1727735916.059 1000 6165 6165 E PHH : Device is dynamic
1727735916.059 1000 6165 6165 E PHH : Updating OTA info at: https://gitlab.iode.tech/ota/ota/-/raw/gsi/gsi.json
1727735916.255 1000 6165 8817 E PHH : Got response
1727735916.255 1000 6165 8817 E PHH : Response body: {
1727735916.255 1000 6165 8817 E PHH : "version": "5.5",
1727735916.255 1000 6165 8817 E PHH : "date": "1727705420",
1727735916.255 1000 6165 8817 E PHH : "variants": [
1727735916.255 1000 6165 8817 E PHH : { "name": "lineage_arm64_bvN", "size": 1209695464, "url": "https://gitlab.iode.tech/ota/release/-/raw/master/gsi/iode-5.5-20240930-arm64_ab.img.xz"},
1727735916.255 1000 6165 8817 E PHH : { "name": "lineage_arm64_ab", "size": 1209695464, "url": "https://gitlab.iode.tech/ota/release/-/raw/master/gsi/iode-5.5-20240930-arm64_ab.img.xz"},
1727735916.255 1000 6165 8817 E PHH : { "name": "useless", "size": 0, "url": "http://devnull.org"}
1727735916.255 1000 6165 8817 E PHH : ]
1727735916.255 1000 6165 8817 E PHH : }
1727735916.255 1000 6165 6165 E PHH : OTA image date: 1727705420
1727735916.255 1000 6165 6165 E PHH : System image date: 1727081937
1727735916.256 1000 6165 6165 E PHH : Device variant is: lineage_arm64_ab
1727735916.256 1000 6165 6165 E PHH : Security patch date: 2024-09-05
1727735916.256 1000 6165 6165 E PHH : OTA variants found: 3
1727735916.256 1000 6165 6165 E PHH : OTA variant found: lineage_arm64_bvN
1727735916.256 1000 6165 6165 E PHH : Device variant is: lineage_arm64_ab
1727735916.256 1000 6165 6165 E PHH : OTA variant found: lineage_arm64_ab
1727735916.256 1000 6165 6165 E PHH : Device variant is: lineage_arm64_ab
1727735916.256 1000 6165 6165 E PHH : OTA variant is the same
1727735916.257 1000 6165 6165 E PHH : OTA variant size: 1209695464
1727735916.255 1000 6165 6165 E PHH : System image date is newer than the currently installed
1727735917.333 1000 6165 6165 E PHH : OTA variants found: 3
1727735917.333 1000 6165 6165 E PHH : OTA variant found: lineage_arm64_bvN
1727735917.334 1000 6165 6165 E PHH : Device variant is: lineage_arm64_ab
1727735917.334 1000 6165 6165 E PHH : OTA variant found: lineage_arm64_ab
1727735917.524 1000 6165 8829 E PHH : OTA image install started
1727735917.335 1000 6165 6165 E PHH : Device variant is: lineage_arm64_ab
1727735917.563 root 8832 8832 E phh-ota : Backing image system_otaphh_a is not mapped
1727735918.212 root 8832 8832 E phh-ota : Cannot map image: /data must be mounted on top of device-mapper.
1727735928.285 1000 6165 8829 E PHH : New slot created
1727735928.285 1000 6165 8829 E PHH : OTA image extracting
1727735928.288 1000 6165 8829 E PHH : Failed applying OTA image. Error: java.io.FileNotFoundException: /dev/phh-ota: open failed: EACCES (Permission denied)
1727735928.288 1000 6165 8829 E PHH : java.io.FileNotFoundException: /dev/phh-ota: open failed: EACCES (Permission denied)
1727735928.288 1000 6165 8829 E PHH : at libcore.io.IoBridge.open(IoBridge.java:574)
1727735928.288 1000 6165 8829 E PHH : at java.io.FileOutputStream.<init>(FileOutputStream.java:259)
1727735928.288 1000 6165 8829 E PHH : at java.io.FileOutputStream.<init>(FileOutputStream.java:147)
1727735928.288 1000 6165 8829 E PHH : at me.phh.treble.app.UpdaterActivity.extractUpdate(UpdaterActivity.kt:468)
1727735928.288 1000 6165 8829 E PHH : at me.phh.treble.app.UpdaterActivity.access$extractUpdate(UpdaterActivity.kt:32)
1727735928.288 1000 6165 8829 E PHH : at me.phh.treble.app.UpdaterActivity$downloadUpdate$2.invoke(UpdaterActivity.kt:337)
1727735928.288 1000 6165 8829 E PHH : at me.phh.treble.app.UpdaterActivity$downloadUpdate$2.invoke(UpdaterActivity.kt:320)
1727735928.288 1000 6165 8829 E PHH : at kotlin.concurrent.ThreadsKt$thread$thread$1.run(Thread.kt:30)
1727735928.288 1000 6165 8829 E PHH : Caused by: android.system.ErrnoException: open failed: EACCES (Permission denied)
1727735928.288 1000 6165 8829 E PHH : at libcore.io.Linux.open(Native Method)
1727735928.288 1000 6165 8829 E PHH : at libcore.io.ForwardingOs.open(ForwardingOs.java:563)
1727735928.288 1000 6165 8829 E PHH : at libcore.io.BlockGuardOs.open(BlockGuardOs.java:274)
1727735928.288 1000 6165 8829 E PHH : at libcore.io.ForwardingOs.open(ForwardingOs.java:563)
1727735928.288 1000 6165 8829 E PHH : at android.app.ActivityThread$AndroidOs.open(ActivityThread.java:8478)
1727735928.288 1000 6165 8829 E PHH : at libcore.io.IoBridge.open(IoBridge.java:560)
1727735928.288 1000 6165 8829 E PHH : ... 7 more
Probably interesting Part of the Log:
1727735917.563 root 8832 8832 E phh-ota : Backing image system_otaphh_a is not mapped
1727735918.212 root 8832 8832 E phh-ota : Cannot map image: /data must be mounted on top of device-mapper.
1727735928.285 1000 6165 8829 E PHH : New slot created
1727735928.285 1000 6165 8829 E PHH : OTA image extracting
1727735928.288 1000 6165 8829 E PHH : Failed applying OTA image. Error: java.io.FileNotFoundException: /dev/phh-ota: open failed: EACCES (Permission denied)
1727735928.288 1000 6165 8829 E PHH : java.io.FileNotFoundException: /dev/phh-ota: open failed: EACCES (Permission denied)
Edit: Here seems to be someone with the same issue:
I linked to:
To join: Telegram: Join Group Chat or https://matrix.to/#/#iodeOS:matrix.org (they are bridged together).
1 Like
hi there, thanks for that. I’m new to GSIs… did you just use the native Xiaomi recovery? or did you already have some other recovery installed like lineage or twrp? the install instructions don’t specify. I tried on a mi 8 lite platina and just got a bootloop.
Hey, to install iodéOS GSI a custom recovery is not mandatory, but useful. The stock Android recovery is sufficient.
It is always useful and sometimes necessary to provide detailed information about the device to avoid unnecessary consultations. Minimum required:
- Code name of the device
- Stock Android version
- Kernel version
@Der_Baliner, thank you, but this variant does not work even on my “normale” T Phone (Jaguar) [Stock Android 14], although I was finally able to install iodéOS GSI with a different installation variant - see #30