Hi & thank you for your interest in iodé.
Sure we will add a little more details on our readme page. You can find TWRP here. You can choose your preferred recovery; I have just added LOS recovery.
1 Like
Thank you. I appreciate the reply and the link. I’m coming from years of exclusive iPhone use, so installing TWRP and sideloading flash zip files on phones is new to me. If I manage to get this installed and enjoy the experience I’ll be sure to contribute and and send some coffees your way 
Thanks again.
1 Like
Hi,
I bought my teracube 2e a couple of weeks ago directly from iodé.
Therefore my device is originally equipped with iodé OS (that is essentially a standard distribution of lineage OS with the addition of microG, some specific privacy oriented configurations and the famous iodé app).
I definitely love my privacy and now I can use a phone that does not send continuously my personal data to Google. I can control exactly the information flow originated from my phone and I can block unwanted requests.
I’m not using facebook apps, so facebook itself is not a problem for me.
I’ve replaced Google cloud with my personal cloud, using my Synology NAS. This involves contacts, calendars, notes, pictures and videos.
I also installed my preferred apps from F-Droid and from Aurora Store.
Everything seems amazing…
But my phone has rapidly become quite slow (mainly during animations, while scrolling pages or surfing the Internet via the browser) and sometimes this is frustrating. I have about 60 apps in total and the same configuration if very fluid on my Xiaomi MI A3 that runs stock android and is not a powerful phone.
There is clearly a problem with lineage OS, perhaps it should be optimized for the device. In fact there is no official distribution available up to now from lineage OS for teracube 2e.
I hope that this problem will be solved with future updates, but I think that Teracube itself should consider to work on this topic (maybe with iodé) in order to offer a privacy oriented phone without sacrifying too much the user experience.
Privacy + Sustainability = perfect phone
Have you tried rebooting occasionally? As far as I know, it does fix the issue. As long as official Lineage OS is concerned, it would be be the same thing more or less, it’d just be a tag.
User experience is a primary concern and is already being addressed.
Hi Gagan,
Rebooting doesn’t help.
I also tried to configure the “performance profile” in the battery saving menu… But unfortunately it doesn’t appear on Teracube 2E (it seems to be device dependent).
Maybe I should try to monitor the system performance, is there a way to do that?
When I fastboot recovery recovery.img, I receive an error “this partition doesn’t exist”
$ fastboot flash recovery ./Downloads/androidstudio/iode/recovery.img
target reported max download size of 134217728 bytes
sending ‘recovery’ (32768 KB)…
OKAY [ 0.955s]
writing ‘recovery’…
FAILED (remote: This partition doesn’t exist)
finished. total time: 0.958s
Is it still true that there are no iodéOS ROMs available for the TeraCube 2e - 2022 devices? If not, is there a plan to eventually do so?
@antoine can reflect in detail. I’m under the impression that they have builds ready in Beta with the potential launch coming soon.
Thank you or the fast update.
Hi,
Do you own a 2E from the 2022 version batch (emerald)?
If so then the install process is different; we will upload it soon.
You can also join our beta tester telegram group here if you want to beta test with us.
I have a 1st batch TeraCube 2e that I originally got from /e/. I decided that I want to try loading iodéOS and started following the directions on their website.
The instructions are:
How to flash Teracube (2E sold before 2022: not compatible with 2022 devices)
- Update the stock firmware to the latest
- Unlock OEM in developer settings
- Reboot to bootloader
- fastboot flashing unlock
- fastboot flash recovery recovery for 2E
- Reboot to recovery
- From recovery => Factory reset => Format Data/factory reset
- From recovery => Apply update => Apply from ADB => adb sideload <rom.zip> iodéOS for 2E
I got to step 8. The problem is, when I adb reboot recovery, it reboots into recovery mode. I select the ADB sideload on the phone and then entered the command ‘adb sideload iode-2.3-20220127-2e.zip’ where the file ‘iode-2.3-20220127-2e.zip’ is in the platform tools directory. Then I get the following message:
PS C:\platform-tools> adb sideload iode-2.3-20220127-2e.zip
serving: ‘iode-2.3-20220127-2e.zip’ (~47%) adb: failed to read command: No error.
On the phone I see the error ‘failed to verify whole-file signature’.
Any ideas?
Any help is greatly appreciated. If there is another way to load this ROM, I am definitely open to it.
Just reboot, I think flash is complete.
I rebooted and the original OS image Teracube_2e_06_2020 booted.
I will start at #5 as it is already unlocked. I might have had driver problems so I am going to chalk it up to that for the moment. The phone came with /e/ OS but i loaded the above image successfully before and that is what I have been running but I really want to try the iodeOS…
The error usually suggests that the file you’ve downloaded is corrupt. It could be that too, can you try redownloading the file instead?
The iodeOS ZIP
I will do that. Thank you.
So the plot thickens. I redownloaded the files and rebooted into recovery mode and selected factory reset and then selected ADB sideload. Then I issued an ADB sideload command and received the following error:
PS C:\platform-tools> adb sideload iode-2.3-20220127-2e.zip
adb: sideload connection failed: device unauthorized.
This adb server’s $ADB_VENDOR_KEYS is not set
Try ‘adb kill-server’ if that seems wrong.
Otherwise check for a confirmation dialog on your device.
adb: trying pre-KitKat sideload method…
adb: pre-KitKat sideload connection failed: device unauthorized.
This adb server’s $ADB_VENDOR_KEYS is not set
Try ‘adb kill-server’ if that seems wrong.
Otherwise check for a confirmation dialog on your device.
So I looked at the status of the connection and it was unauthorized:
PS C:\platform-tools> adb devices
List of devices attached
0123456789ABCDEF unauthorized
So I had a hunch to again let the ADB sideload time out on the phone and re-select it and try it again. Then I checked the status of the connection again:
PS C:\platform-tools> adb devices
List of devices attached
0123456789ABCDEF sideload
So I issued the ADB sideload command again:
PS C:\platform-tools> adb sideload iode-2.3-20220127-2e.zip
serving: ‘iode-2.3-20220127-2e.zip’ (~47%) adb: failed to read command: No error.
On the phone, it says the same error as before: ‘E: failed to verify whole-file signature’
and ‘E: signature verification failed’ and E: error 21’ and ‘Install from ADB completed with status 2. Installation aborted.’
So I tried the same process using files ‘iode-2.2-20210907-2e-recovery.img’ and iode-2.2-20210907-2e.zip’ and when I rebooted the phone it and it seems to be working!
1 Like
So the question is, why is there some sort of a delay with the ADB sideloading of files? Maybe we will figure it out over time…
No help for the last poster sadly but wanted to share my experience:
Decided to give iodeOS a try after having issues installing /e/. Flashed over the newest stable release last night (very easy, the instructions on the iode website worked for me) and it’s been excellent so far. The actual iode app is very neat. I’ve only had one app not work for me (Tidal), all the rest, even banking apps, are going strong. I haven’t tried out every feature but so far I haven’t found anything not working outside of the Tidal app. I’m on Mint Mobile fwiw, been working well.
2 Likes
The issue with iode at that point of time was that the super image was not of the right size compared to the super image in stock, and hence caused a lot of weird issues, and the issue was soon fixed and intimated by iode afaik. I apologize for the very late reply.
1 Like