Perhaps they assume people will contact them directly when they have a problem that can’t be troubleshot in the community forums. Contact - iodé
1 Like
I recommend searching “+Samsung +VoLTE +custom ROMs” before considering Samsungs as a viable option.
1 Like
Indeed. Samsung devices are a dead end as far as custom ROMs are concerned. Samsung have history of making life difficult for custom ROM developers and maintainers. If you want to spend your time promoting anything, pick a manufacturer that is helpful towards custom ROMs and FOSS. Sony is one such. Fairphone is another
1 Like
And pixels
That’s not the best way.
Issues should be discussed in a community to help each other and to get a brainpool
This thing with samsung’s I find surprising, although as I pointed out, I’ve never had one and consequently no little if anything about them, but can’t help noticing that iode officially supports 13 different models. If they are as incompatible as they sound why bother with them? As for Fairphone’s they are about as rare as dual sim XA2’s and seem to have more than their share of incompatibility hiccups if the n-umber of users reporting problems on here is anything to go by. So I’ll just stick with the Sony’s at least for now.
At the moment the only positive on the horizon is the Brax 3 and I admit that I was seriously considering putting my name down for one, but I’m not a fan of Mediatek processors and when I looked at the spec’s it would make more sense for me to buy an LOS supported newer model Sony (Xp 1 or 5), that has been well cared for and install iode on that. Just hope that Brax buyers don’t think same. At least the Brax will bring new iode users in and the price will appeal to younger people that want to buy new but can’t afford the latest mainstream flagship.
Sony has to be the best option, not only for my current efforts but for a longer term strategy maybe. I need to give it some thought. Alpha just mentioned pixels I notice as I’m writing this response and although I agree with the general sentiment the problem with them is that the type of people that already buy/own them are unlikely to be open to the idea of moving over to OSS. Also you would have to be techie to even realise that a pixel running OSS is even a possibility. Very counterintuitive!
That’s exactly why I bought a pixel…so I can use GOS!!!
and yes, Alpha convinced me to do it😉… thanks again😀
and there are lots of GOS users all over the world.
Please can you take this discussion to a different thread. This thread is intended to be about publicising my builds for these Sony devices, and helping with any problems with those builds.
If you want to send time rambling about promoting IodéOS, PLEASE DO IT IN A DIFFERENT THREAD. Thank you!
Apologies to @petefoth …was no intent to hijack the thread on my part. I wasn’t expecting any responses TBH.
5.8 builds for these devices are now available from IodeOS
1 Like
Hello
Just tried (FINALLY!!) to install this last build for aurora but I get an error. See log below:
~/e$ fastboot --skip-reboot update iode-5.8-20241220-UNOFFICIAL-aurora-img.zip
extracting android-info.txt (0 MB)…
extracting boot.img (64 MB)…
target reported max download size of 805306368 bytes
archive does not contain ‘boot.sig’
archive does not contain ‘boot_other.img’
extracting dtbo.img (8 MB)…
archive does not contain ‘dtbo.sig’
archive does not contain ‘dt.img’
archive does not contain ‘recovery.img’
extracting system.img (4032 MB)…
Invalid sparse file format at header magic
archive does not contain ‘system.sig’
archive does not contain ‘system_other.img’
extracting vbmeta.img (0 MB)…
archive does not contain ‘vbmeta.sig’
extracting vendor.img (1007 MB)…
Invalid sparse file format at header magic
archive does not contain ‘vendor.sig’
archive does not contain ‘vendor_other.img’
Bootloader Version…: 1310-7079_X_Boot_SDM845_LA2.0.1_Q_207
Baseband Version…: 1311-7919_52.1.A.3.49
Serial Nmber…: CB***FSJKX
checking product…
FAILED
Device product is ‘H8166’.
Update requires ‘sdm845’.
finished. total time: 0.009s
Sorry about that. I don’t have any way of testing these builds. If you cannot install the ROM using fastboot, then try using recovery, following the LineageOS installation instructions
- flash the
bootimagefastboot flash boot iode-5.8-20241220-UNOFFICIAL-aurora-boot - reboot to recovery
With the device powered off, hold Volume Down + Power. - Sideload the ROM zip file
- On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
- On the host machine, sideload the package using:
adb -d sideload filename.zip.
Tip: After the package is installed, recovery will inform you that reboot to recovery is required to install add-ons. In case you want to do that, please select “Yes,” otherwise “No”.
Tip: Normally, adb will report
Total xfer: 1.00x, but in some cases, even if the process succeeds the output will stop at 47% and reportadb: failed to read command: Success. In some cases it will reportadb: failed to read command: No errororadb: failed to read command: Undefined error: 0which is also fine.
- Reboot the device
Thank you very much for your fast reply
I believe I have to use another image (https://download.lineage.microg.org/IodeOS/aurora/iode-5.8-20241220-aurora.zip), right?
Just one more thing before I proceed on my daily driver… Isn’t the error I got about different code for phone expected be the same if I’m using recovery?
Yes that’s the main ROM zip file that you install via recovery and adb sideload.
The custom recovery is in the boot img file iode-5.8-20241220-UNOFFICIAL-aurora-boot.img You install that recovery by flashing that with fastboot to the boot partition: fastboot flash boot iode-5.8-20241220-aurora.zip
No. That message is probably due to an error in how I built the -img.zip file. That’s why I will no longer build that file or support installation via fastboot: I don’t know what the error is, or how to fix it. 
On all the devices I’ve tried to install my builds (lilac, poplar_dsds, xz2c, sunfish) I have had no problems installing fromrecovery
Well, I thought that the boot image is this one: https://download.lineage.microg.org/IodeOS/aurora/iode-5.8-20241220-UNOFFICIAL-aurora-boot.img
I have done a lot of /e/ OS similar installations and the recovery was always an img file that I “wrote” using fastboot.
You are correct, and I have corrected my post. I should not try to do things too quickly
Thank you very much Peter. I’m running now iode OS and I have all the data from previous Lineage OS…
That’s great. Were you running normal LineageOS or LineageOS for microG? Which version?