Xiaomi Redmi Note 8 (without NFC) ginkgo
Xiaomi Redmi Note 8T (NFC) willow
Stock Android 11.0 | Kernel version 4.14.190
iode-5.4-20240831-gsi.img [ fix 2024093 ]
Immediately trouble-free iodéOS GSI + microG installation
Welcome iodè GSI 
1 Like
I have tested if my MTK device boots with kernel 4.4.146, but it is stuck in the OEM bootloop 
How can I post a log 
Unihertz Atom L
4-inch small, robust smartphone, IP68 protection class
Stock Android 11.0 | Kernel version 4.14.186
iode-5.4-20240831-gsi.img [ fix 2024093 ]
Immediately trouble-free iodéOS GSI + microG installation
Terminal-log
adb\unihertz>fastboot flash system iode-5.4-20240831-gsi_fix20240903.img
Resizing 'system' OKAY [ 0.009s]
Sending sparse 'system' 1/12 (262116 KB) OKAY [ 7.734s]
Writing 'system' OKAY [ 2.188s]
Sending sparse 'system' 2/12 (262116 KB) OKAY [ 7.558s]
Writing 'system' OKAY [ 2.215s]
Sending sparse 'system' 3/12 (262096 KB) OKAY [ 7.121s]
Writing 'system' OKAY [ 2.210s]
Sending sparse 'system' 4/12 (262128 KB) OKAY [ 7.831s]
Writing 'system' OKAY [ 2.202s]
Sending sparse 'system' 5/12 (262120 KB) OKAY [ 7.414s]
Writing 'system' OKAY [ 2.207s]
Sending sparse 'system' 6/12 (262124 KB) OKAY [ 7.735s]
Writing 'system' OKAY [ 2.224s]
Sending sparse 'system' 7/12 (262124 KB) OKAY [ 7.224s]
Writing 'system' OKAY [ 2.199s]
Sending sparse 'system' 8/12 (262128 KB) OKAY [ 7.575s]
Writing 'system' OKAY [ 2.200s]
Sending sparse 'system' 9/12 (262076 KB) OKAY [ 7.666s]
Writing 'system' OKAY [ 2.207s]
Sending sparse 'system' 10/12 (262124 KB) OKAY [ 7.858s]
Writing 'system' OKAY [ 2.192s]
Sending sparse 'system' 11/12 (262128 KB) OKAY [ 7.666s]
Writing 'system' OKAY [ 2.241s]
Sending sparse 'system' 12/12 (199220 KB) OKAY [ 5.694s]
Writing 'system' OKAY [ 2.017s]
Finished. Total time: 130.263s
Welcome iodè GSI
1 Like
Samsung Galaxy Tab Active3 (T575) gtactive3
8.0-inch ruggedized tablet, MIL-STD-810H compliant
Stock Android 13.0 Bootloader unlocked | Kernel version 4.9.191
iode-5.4-20240831-gsi.img via DSU Sideloader F-Droid Store
Immediately trouble-free iodéOS GSI installation (Dual-Boot)
While booting the iodéOS GSI ROM via DSU, it created a new and temporary system and data partitions on your device that are stored inside the /data/gsi partition. As a result, the DSU then booted these partitions rather than the original ones and your device would then be booted to the installed iodéOS 5.4 GSI.
2 Likes
Installation variant via (F-Droid) DSU Sideloader
Hello,
I managed to install the GSI on a Poco F3 (Alioth). The boot is long but everything works except the WIFI.
I don’t remember which firmware was installed, so I tried to flash the last one (fw_alioth_miui_ALIOTHGlobal_OS1.0.3.0.TKHMIXM_57a88631b9_13.0).
Unfortunately, rebooting after flashing this firmware doesn’t work: the phone remains on the Poco logo and nothing else.
If anyone has a clue, I’d love to hear from you.
Thanks in advance,
fw_alioth_miui_ALIOTHGlobal_OS1.0.3.0.TKHMIXM_57a88631b9_13.0 is wrong! It’s only a Global Recovery ROM with 141.1 MB (!!!)
Install via fastboot it again (flash_all*.*).
Global Fastboot ROM
alioth_global_images_OS1.0.3.0.TKHMIXM_20240604.0000.00_13.0_global_af9c432b92.tgz with 6 GB (!!!)
Samsung Galaxy S21 FE 5G (2022) SM-G990B2 | r9q
Stock Android 14.0 Bootloader unlocked | Kernel version 5.4.254
iode-5.4-20240831-gsi.img via DSU Sideloader F-Droid Store
Left image: Stock Android 14 ::: Right image: iodéOS 5.4 GSI
[Dual-Boot] runs well. All basic apps work: 5G | 4G LTE, Wi-Fi /WLAN, Bluetooth, Main + Selfie camera.
1 Like
T Tablet 5G (2023) Hubbs
Stock Android 14.0 Bootloader unlocked | Kernel version 4.19.191+
iode-5.4-20240831-gsi.img via DSU Sideloader F-Droid Store
.
All basic apps work: 5G | 4G LTE, Wi-Fi /WLAN, Bluetooth, Main + Selfie camera.
1 Like
@vince31fr @Antoine Pls check
I’ve grab log’s 
Log's
Log’s from iodé 5.4
console-ramoops
FileSend.jp - Easily share files online
last_kmsg
FileSend.jp - Easily share files online
Hey, why don’t you call us MTK device by its full name, including the Android device codename?
I have, look at the list
Stock Android 9.0 (pie) ?
Yep, but currently running on A14 QPR3 RisingOS 3.2 GSI.
All others like VoltageOS 3.6, iodéOS 5.4 or RisingOS 5.2 stuck in bootloop OEM logo
I’ve given the maintainer’s also log’s for fixing!!!
I have experienced this several times: one GSI runs, the other does not. There is no guarantee of functionality.
Try it out once via TWRP:
Permissiver_v5.zip for the -Android- Generic Device/Other, by @erfanoabdi
what’s with your LeOS GSI?
No comments
1 Like
That’s not the solution!!!
Permissive Selinux it’s not really good, it’s a joke, it’s a car without brakes, says Phh.
The problem is, that’s a kernel issue that must fixed by the maintainer’s.
BTW, I’ve many experience with GSI’s, Admin in two groups. And I release my own group soon.
I’ve helped many users.
Good to know !
Try it out as a test: VOS 3.2 GSI
I have use it before RisingOS
I hope Chris fixed it 