STUCK IN BOOTLOOP
coming from e/OS| Kernel version 4.14.352qclp
twrp-3.7.1_12-0-ginkgo
iode-5.5-20241010-arm64_ab.img
here is the output, not sure what I am doing wrong, since Iodysseus got ginkgo to work.
$ fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
Erasing 'system' OKAY [ 0.358s]
Finished. Total time: 0.363s
$ fastboot flash system iode-5.5-20241010-arm64_ab.img
Sending sparse 'system' 1/5 (734104 KB) OKAY [ 29.756s]
Writing 'system' OKAY [ 0.001s]
Sending sparse 'system' 2/5 (707536 KB) OKAY [ 28.549s]
Writing 'system' OKAY [ 0.002s]
Sending sparse 'system' 3/5 (783908 KB) OKAY [ 33.182s]
Writing 'system' OKAY [ 0.001s]
Sending sparse 'system' 4/5 (785424 KB) OKAY [ 33.474s]
Writing 'system' OKAY [ 0.001s]
Sending sparse 'system' 5/5 (75368 KB) OKAY [ 3.400s]
Writing 'system' OKAY [ 0.001s]
Finished. Total time: 135.752s
$ fastboot -w
Erasing 'userdata' OKAY [ 0.488s]
F2FS-tools: mkfs.f2fs Ver: 1.16.0 (2023-04-11)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Enable Project quota
Info: not exist /proc/version!
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 224788440 (109759 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
Info: add quota type = 2 => 6
Info: format version with
"5.15.0-122-generic"
[f2fs_init_sit_area: 638] Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 672] Filling nat area at offset 0x00e00000
[f2fs_add_default_dentry_root:1255] Writing default dentry root, at offset 0x1d200
[f2fs_write_root_inode:1300] Writing root inode (hot node), offset 0x1cc00
[f2fs_write_default_quota:1387] Writing quota data, at offset 0001d201 (1/2)
[f2fs_write_default_quota:1387] Writing quota data, at offset 0001d202 (2/2)
[f2fs_write_qf_inode:1438] Writing quota inode (hot node), offset 0x1cc01
[f2fs_write_default_quota:1387] Writing quota data, at offset 0001d203 (1/2)
[f2fs_write_default_quota:1387] Writing quota data, at offset 0001d204 (2/2)
[f2fs_write_qf_inode:1438] Writing quota inode (hot node), offset 0x1cc02
[f2fs_write_default_quota:1387] Writing quota data, at offset 0001d205 (1/2)
[f2fs_write_default_quota:1387] Writing quota data, at offset 0001d206 (2/2)
[f2fs_write_qf_inode:1438] Writing quota inode (hot node), offset 0x1cc03
[f2fs_update_nat_default:1475] Writing nat root, at offset 0x00000e00
Info: Overprovision ratio = 0.440%
Info: Overprovision segments = 241 (GC reserved = 234)
[f2fs_write_check_point_pack: 854] Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack: 942] Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack: 956] Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack: 968] Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack: 979] Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack: 987] Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack:1007] Writing NAT bits pages, at offset 0x000003fe
[f2fs_write_check_point_pack:1028] Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack:1047] Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1080] Writing super block, at offset 0x00000000
Info: format successful
Warning: skip copying userdata image avb footer due to sparse image.
Sending 'userdata' (97 KB) OKAY [ 0.015s]
Writing 'userdata' OKAY [ 0.003s]
Erasing 'cache' OKAY [ 0.010s]
mke2fs 1.46.6 (1-Feb-2023)
128-byte inodes cannot handle dates beyond 2038 and are deprecated
Creating filesystem with 98304 4k blocks and 98304 inodes
Filesystem UUID: 0d577a1c-5461-47da-a088-7447d33d606a
Superblock backups stored on blocks:
32768
Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
Warning: skip copying cache image avb footer due to sparse image.
Sending 'cache' (56 KB) OKAY [ 0.009s]
Writing 'cache' OKAY [ 0.008s]
Erasing 'metadata' OKAY [ 0.006s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 16.325s
$ fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.051s
tried and got bootloop with other versions as well:
iode-5.5-20240930-arm64_ab.img
Note: Although the basic functions of a beta version can already be used, it has not yet been fully tested for issues ((but this version is already running extremely well and, depending on the device and stock firmware, can be used as a daily driver)).
iodéOS GSI (as well as iodéOS CustomROMs) have the microG services implemented by default, which serve as an open source alternative to the spying Google services (Google Mobile Services - GMS).
However, there is the option of de-activating the microG App Suite and re-activating it during operation. A feature that not every Generic System Image (GSI) can offer.
telegram is official
matrix not
but yes, both are bridge together
If the topic gets out of hand, we have to consider whether this liaison should be ended again. Then I will separate the (my) matrix room from Telegram and delete it.
Iode must or can then decide to open a new room (officially) and bridge it. That is not up to me.
Or to rely solely on Telegram.
It disturbs me as a user whenever I see OSS communities arguing over trivial matters, I say trivial because everyone on here wants the project to be successful and if that is to be the likeliest outcome it needs both tech’ teams and users working in accord. I’ve been a linux user (PC’s mainly), for over twenty years now and have seen many projects fail due to the lack of accordance between the principle contributors. A user that posted on here recently (can’t remember who it was), posited that we should build the kind of community support structure that Linux Mint has adopted, (or words to that effect). I remember thinking that it was a little optimistic to say the least for what is a project that is relatively speaking still in the early stages of development, but in a way I kind of understand what he/she was getting at.
No matter how innovative a project is its success in reality can only be judged by the amount of users that actually load up the software and use it. For them to make the leap from the likes of Schmoogle and Apple they will need to have full confidence in the product and that just isn’t going to happen without them seeing some kind of robust structure behind it that they know they can depend upon if and when required. Thinking that a project of this nature can survive solely on ‘techie’ users is, I believe, a big mistake in the longer term.
Installé sur un Poco F4 (Munch) depuis quelques jours, tout est OK (seul souci constaté, au démarrage du tél, pour accèder au code pin je suis obligé de ‘passer’ avant par le lecteur d’empreinte -rien de bien méchant-).
Et je me suis même payé le luxe de restaurer des applis d’un Pixel sous GrapheneOS avec SeedVault…
Un grand merci aux Dev’s
reverting back to xiaomi stock and trying again with the latest image resulted in a bootloop with this (rather distrubing screen. I can’t help but think the commands listed the blog (https://blog.iode.tech/what-are-gsis-and-how-to-install-them/) are not the ones people are using to get the same results. @iodysseus which commands did you use on the redmi note 8t?
This version was the only one that worked on my Galaxy a54 5g the others didn’t even boot the only defect I found was the fingerprint that doesn’t work the rest is flowing perfidiously I would like more updates for my device. I hope that in the future an official version will come for the Galaxy a54 5g A546E.
Hello. I installed the [iode-5.6-20241024-arm64_ab.img.xz] before on my infinix note 10 pro and I am able to boot it. However, games and banking apps says the rom is rooted and unable to use them. I don’t want to use Magisk as I do not want to use root and just stay with stock iode-5.6. Can you help me fix this? I would like to try the new version 5.7 but I am afraid to install this due to root problems.
PS: One of the Banking apps I am using detects that I am using root even I don’t have one. The other banking app is fine.
Hello everyone,
I have flashed the iodéGSI on my SHIFTphone 8.0. When I tried to close the bootloader via fastboot flashing lock, my phone fell into a bootloop. I was able to fix this by rebooting into fastboot using the buttons, but I would still like to close the bootloader. Does anyone have any idea if this is possible?
Bootloop is a “normal” reaction of the system. Re-locking the bootloader is not possible! At least one device-specific avb_custom_key would be required.
December marks 10 years of DivestOS!
There were over 7,000 git commits created in this time.
I believe the projects were highly successful in their goals, however this month will mark the end.
DivestOS and its apps will not receive any further updates.
Hypatia and Carrion will no longer receive database updates.
The non-mobile Divested projects (eg. Brace, D-WRT, real-ucode, and DNS blocklists) will continue to be maintained.
Most of our forum threads will be closed and the DivestOS XMPP chat rooms will also be turned off.
Donations will no longer be accepted and all recurring donations will be cancelled.
Thank you to all the users, contributors, and donors for this time. -Tavi
Sad to see another OSS project bite the dust but only goes to reinforce the point I made on this board just a few days ago. Sure, techies will always be the driving force of any IT project, but you can’t depend upon them alone as users for long term support. Their loyalties tend to be highly susceptible to new ideas and new concepts. 25 years of being a linux user doesn’t go by without you noticing just how many distro’s have fallen foul of exactly the same problem. On the upside it’s reassuring to see that the iode team may already be aware of this pitfall as the release of a dedicated iode phone goes a long way to proving their commitment to bringing in new users even if they should have had the ‘iode’ brand on the actual phone itself. The Brax-iode also brings an air of class with it that ‘Brax 3’ sorely misses out on.
There may well be reasons that I am unaware of as to why iode could not be on the phone. Maybe someone might enlighten us with them some day, but at least the iode project will benefit from the promotion of the Brax phone as being a practical every day alternative to G android for privacy/security driven users. The price point of the Brax demonstrates that such a project could be expanded to other, more mainstream, manufacturers particularly so if the volumes could be leveraged. We can only hope that the team pursue this opportunity to show the industry that with the right marketing and the right product a FOSS phone can be a commercially viable project.
screen. I can’t help but think the commands listed the blog (
