[ROM][S10e/S10/S10+][A13] iodéOS = LineageOS 20 + MicroG + adblocker [28/08/2023]

[Draknof]

I have similar trouble with the Aurora search.

Is there any timeline for iodeOS to upgrade to Lineage 20 / Android 13?

 

[EonOfBlack]

I have similar trouble with the Aurora search.

Is there any timeline for iodeOS to upgrade to Lineage 20 / Android 13?

There's a beta you can you install. Here's the link: https://gitlab.com/iode/ota/-/tree/master/beta. Download the 3v3 apk to receive the build.

I'm on it currently though and it seems to sometimes have issues with the mic during calls.

 

[mx82]

There's a beta you can you install....

Thanks for the info.
So there is finally an official Lineage20 for the S10:

Info about beyond0lte | LineageOS Wiki

wiki.lineageos.org

 

[mx82]

Until yesterday the aurora app was not able to login.
Now (after an update via F-Droid) this is fixed and even the search works again.

 

[Monvigliero]

[Open bootloader warning]

Hello All, maybe stupid question. I did some searching, and reading, but I would like to be sure, so I ask. I flashed two phones in the family (S10 and S10e) from factory Samsung to Iodé, I have exaclty followed the Iodé/Lineage instructions (adb sideload from iodé recovery) it works perfectly, but on reboot/turn on the phone gives the "open bootloader warning" - immediately upon turning on, and also on the top of the Samsung screen. Now one phone is without root on Iodé recovery the other is rooted on TWRP. Both with same warning. Is it normal? (Just to try I have checked also with unrooted Lineage w/Lineage recovery it was the same.) Is there any solution apart from the "up_param.tar" Odin flashing method (maybe in TWRP)? (If not, is there some reliable source for up_param.tar, or (of course I have saved the factory OS from sammobile) should I prepare it for myself? I do not really want to make mistake. Thank you in advance. (This was never the case with my previous S9+ on the same OS.)

PS.: Huge respect for the OS creators it is AWESOME!

 

[Monvigliero]

Other technical question:

I am testing the data/tracking blocker. I set full social block. According to the iodé app, traffic is blocked (grey). But Facebook app works just fine still, and I see the DNS requests on my router. Same with Private DNS settings off/auto/on. Something I set badly?

 

[metaxda]

is the latest version for the S10 [Beyond1] found here ?
--> https://github.com/iodeOS/ota/releases/tag/v4-FP4

(Released 2023 April and it's tagged "Fairphone 4")

 

[fineb]

iode for S10 is still iode3, see https://github.com/iodeOS/ota/releases/tag/v3-beyond1lte
iode4 is in beta phase and should be released soon according to the iode forum

Samsung S10e - iodé 4.0?

I think iode 4 for the s10 series is currently in beta. Vincent wrote in the matrix chat group that the next release will be delayed, maybe end of June. So my understanding is that we will get Iode 4 with Android 13 for the s10s end of June

community.iode.tech

 

[metaxda]

iode for S10 is still iode3, see https://github.com/iodeOS/ota/releases/tag/v3-beyond1lte

Thanks for that link.

I don't know why I didn't see that before,
because I had grabbed some files from that exact link, a few weeks ago.,
and now I feel silly for asking

PS:
v4 Beta discussion in Post #162 of this thread

 

[metaxda]

Installation Instructions

To download and flash our latest build, see https://gitlab.com/iode/ota.
You can also find here direct links to the latest builds.

^ I'm looking at flashing this ROM, and checked the steps at the link [ https://gitlab.com/iode/ota ] , listed below:

S10, S10e, S10+

1. Update the stock firmware to the latest
2. Unlock OEM in developer settings
3. Activate adb and type adb reboot bootloader, or shut down phone and press Vol- + Bixby while plugging to computer
4. In Download Mode (DL), long press Vol+ and unlock bootloader
5. Reboot to DL mode & flash recovery for S10 | recovery for S10e | recovery for S10+ with command: heimdall flash --RECOVERY <recovery_filename>.img
6. As soon as the flash ends, quickly press power/vol+/bixby buttons altogether to directly reboot to recovery
7. From recovery => Factory reset => Format Data/factory reset
8. From recovery => Apply update => Apply from ADB => adb sideload <rom.zip> iodéOS for S10 | iodéOS for S10e | iodéOS for S10+

So, does this mean, that there is no need to install Magisk before the recovery?
or patch the recovery with Magisk, and then flashing this patched recovery?

I read many blogs and watched Youtubes,
and it's a bit confusing to see why some S10 users have patched recovery (with vbmeta.tar),
but TWRP posted today (21 JUN 2023) that Magisk needs to be in root partition (not recovery),
and then there are other instructions which don't talk about patching, etc.

 

[StrifE]

^ I'm looking at flashing this ROM, and checked the steps at the link [ https://gitlab.com/iode/ota ] , listed below:




So, does this mean, that there is no need to install Magisk before the recovery?
or patch the recovery with Magisk, and then flashing this patched recovery?

I read many blogs and watched Youtubes,
and it's a bit confusing to see why some S10 users have patched recovery (with vbmeta.tar),
but TWRP posted today (21 JUN 2023) that Magisk needs to be in root partition (not recovery),
and then there are other instructions which don't talk about patching, etc.

You install the iodeOS recovery (which is lineage os recovery based not TWRP) and vbmeta through Odin/Heimdall.
Then you install the ROM through the recovery
Then you install the Magisk zip through the recovery
Patched TWRP with Magisk is only on OneUI ROMs

 

[metaxda]

You install the iodeOS recovery (which is lineage os recovery based not TWRP) and vbmeta through Odin/Heimdall.

I feel my issue is a bit weird.
When flashing recovery through ODIN, "nothing" happens in ODIN,
ie. no status message to show the progress.

So, I needed some advice and help,
and posted in the Q&A Forum

Having 'Trouble' Flashing Recovery -- SM-G973F [ Beyond1LTE ]
--> https://forum.xda-developers.com/t/having-trouble-flashing-recovery-sm-g973f-beyond1lte.4599067/

_______________________________________________
Model: SM-G973F [Beyond1LTE]
One UI: v4.1
Android: v12
Baseband: G973FXXSGHWB3
Build: G973FXXSGHWC1
Security Patch: 01 March 2023

Bootloader: Unlocked
(Verified through "Developer Options"
--> 'OEM Unlocked - On' (Greyed out)
_______________________________________________


I am having trouble flashing a Recovery file on this Galaxy S10.

I used Odin v3.13.3 and v3.14.1 ,
and in both times, Odin detects the phone is connected
but when I tried to flash the
• recovery.tar (in "AP")
• vbmeta.tar (in "CP")
Odin does not show that it flashed any of the files,
ie. there is no progress.
I'm waiting for about 1+ minutes, with no activity to show flashing is in progress.
Should it take longer than that?

I have also tried to patch the recovery through Magisk,
ie. after installing Magisk.apk on the phone,
and I directly patch the recovery.img file through Magisk.

Then, tried flashing this patched recovery.tar through Odin,
and there's still no progress in Odin to show me it's flashing.

 

[StrifE]

Make sure there's a "recovery.img" (by this name explicitly) inside the recovery.tar
When you go to the bootloader, go by pressing the keys and not by rebooting to bootloader (takes me to a weird screen on my s10e and I can't do anything from there), before attempting the flashing process try to disconnect and reconnect the USB cable and see if Odin responds to that action (should say disconnected and then reconnected or something like that)

 

[metaxda]

Make sure there's a "recovery.img" (by this name explicitly) inside the recovery.tar
When you go to the bootloader, go by pressing the keys and not by rebooting to bootloader (takes me to a weird screen on my s10e and I can't do anything from there), before attempting the flashing process try to disconnect and reconnect the USB cable and see if Odin responds to that action (should say disconnected and then reconnected or something like that)

Earlier, I was using a different laptop, to do the flashing,
and it simply was not working,
ie. Odin shows COM connection to the phone,
but no progress after that.

Now, I'm using a different machine [Win10].

I have following recovery files in .img format
( TWRP , iodéOS , LineageOS )

I make the .tar in 7-Zip

I load the files as follows,
• recovery.tar (in "AP")
• vbmeta.tar (in "CP")

and when I press START to flash,
the whole Odin shuts down and disappears.
This 'disappearing' happened to Odin v3.13.1 , 3.13.4 and 3.14.1

I don't know if it's an issue with the phone, or my actual computers ! :-D



EDIT:
It works now.
I flashed successfully,
ie. you were right @Strifelolz ,

the filename MUST be named exactly:
recovery.img (inside recovery.tar )

So, everyone ... don't make this mistake like me!

 

[metaxda]

So, I was having those problems before,
because I did not have the spelling correct
of 'recovery.img' inside the .TAR file.

It was completely my mistake
but that's also because I left Samsung phones, 4-5 years ago,
and returned to the S10 because I got the phone recently to use as a back-up phone.

I was testing things and I successfully flashed:
- TWRP recovery
- iodéOS ROM (2023-04-01)

I did not flash Magisk,
and everything went smoothly.

I was using the phone for several hours,
checking its operation, smoothness and apps.

Then, I wanted to flash Magisk,
so through the iodéOS ROM,
I pressed the power button (in Status Bar),
and pressed Reboot -> Recovery
and then, it went into TWRP
but I could not find the file (as device is encrypted),
and I thought I'll try with OTG later,
and I just rebooted into "System" through TWRP,
but the phone is in a bootloop.

It does not go into Recovery either.

I simply cannot get the phone to enter Recovery,
so I am perplexed !

I remembered that I switched on "USB Debugging" in Developer Options.

I just read now from a user's post on Samsung forum --> here
that if the "USB Debugging" in 'Developers Options' is switched on,
then I cannot enter the Recovery mode ?

Is this true?

What can I try to get phone to go into Recovery mode ?

( I'm sorry to trouble people in this Thread,
and I can go to another thread )

 

[metaxda]

Update:
I can get into Recovery now,
and I was able to do this,
when USB-OTG was inserted into the phone.

When I was using USB-C with the computer,
it wasn't allowing me to get into Recovery (apparently).


EDIT:
I was reading some older pages of this thread, and on Page 4,
this post caught my eye, because this was very pretty much my experience too.
So, maybe there's an underlying issue with TWRP recovery and iodéOS ROM.

Flashed IodéOS 3.1, flashed Magisk 25.2, everything works fine (S10e - exynos). After while of using I restarted device to recovery (from power menu). Device restarted, showed screen with Samsung logo, then whit android logo and then boot screen from ROM shows. But it stuck and do nothing (over 15 minutes). Device was very hot.

So I tried restart with buttons (pw + down) and after turn off immediately tried to boot recovery (TWRP, pw + bixby + down) - it just restarted and stuck on boot logo again. So I tried download mode (pw + bixby + up) and again... it just trying to start regularly, but stuck on boot screen.

So I cannot get to recovery or download mode by buttons! Turning device off is possible only by plugin to charger, restart, then charging animation shows up and if I unplug, device is off.

Any advices? Thanks.

 

[metaxda]

...
but on reboot/turn on the phone gives the "open bootloader warning" - immediately upon turning on,
and also on the top of the Samsung screen.
Now one phone is without root on Iodé recovery the other is rooted on TWRP.
Both with same warning.
Is it normal?

This is normal.
When your bootloader is unlocked,
the security message will come on as a 'warning',
to tell you that the security of the phone has been compromised, etc.

I have seen this with other brands, eg. Asus, Samsung, etc.

 

[metaxda]

After losing a day, trying to figure out my issues,
eg. phone "boot looping", entering download mode was not always consistent, etc.

I have figured out a few things,
and running iodéOS for the last few days now.

Here are some findings:

• Power Off
To power off, I must have a powered USB-C cable plugged into the phone,
and then press POWER + VOLUME DOWN buttons for ~7 seconds.
Once I see the charging logo, for a few seconds, I can let go of the buttons.


• Bootloader Mode
Assuming my Recovery is functional, to get into Download mode,
while the phone is off, plug in USB-C earphones.
( I tried other USB-C cables or OTG, but I did not get consistent results)

It only worked for me, by plugging in USB-C earphones.
Then, press continuously on POWER + VOLUME UP + BIXBY buttons,
and keep pressing, until I got to the Recovery,...and then I chose 'Reboot To Bootloader'.
Once in 'Bootloader Mode', I could flash using Odin.

• "Bootloop" Issues
My issues with the iodéOS not booting correctly, started because of my need to access Play Store.
This was my successful interaction with MicroG and a de-Googled ROM,
after trying in other years, to go down this path, but having a 'spare phone' now, meant I could pursue this objective.
I was trying to download some Apps (eg. a paid app that has train timetables) through Aurora Store,
Since I had no experience with Aurora Store before,
I saw the price of the app (which I had paid for many years ago already).
I panicked, and without clicking on the app, I shutdown the phone
and flashed "Phonesky_magiskv2.zip" (from Page #1 of this thread).
This was a Magisk module, since I did this a few times,
I learnt/discovered that this module didn't play nicely with the ROM,
no matter which Recovery I had (LOS-based or TWRP).

• Lygisk Root
So, I stopped flashing "Phonesky" (which was probably expecting Magisk)
and I proceeded with iodéOS as normal, flashing it with the LOS recovery.
I read more into Magisk vs Lygisk, and learnt more about
Samsung Exynos phones which have this encrypted /data folder,
which is what Lygisk is meant to address,
I got the canary release and it's been stable.

----------------------------------------------


My issue now with iodéOS ROM , is there are certain paid Apps from Play Store, which I need.
Some of these apps, need to connect to the Play Store for licence verification,
eg. Titanium Root Licence Key.

I tested my paid SD Maid and SD Maid Pro apps through Aurora Store,
and they work, but Titanium Backup does not.

I restored Titanium Backup Pro [Ti Pro] (with the Pro Key) through Swift Backup (which was through Aurora Store), on the iodéOS, but still, Ti Pro cannot check the licence and won't run.

Ti Pro was my favourite before I started facing issues on newer Android,
as I also use Swift Backup for troublesome Apps these days,
but there some things that I still like about TiPro.
I've also discovered AppDash (which looks great by the way, by a well-respected XDA developer )
and installed that successfully via Aurora Store in iodéOS .


However, I'm still looking for advice from anyone,
who can run paid PlayStore Apps on iodéOS.

 

[EonOfBlack]

After losing a day, trying to figure out my issues,
eg. phone "boot looping", entering download mode was not always consistent, etc.

I have figured out a few things,
and running iodéOS for the last few days now.

Here are some findings:

• Power Off
To power off, I must have a powered USB-C cable plugged into the phone,
and then press POWER + VOLUME DOWN buttons for ~7 seconds.
Once I see the charging logo, for a few seconds, I can let go of the buttons.


• Bootloader Mode
Assuming my Recovery is functional, to get into Download mode,
while the phone is off, plug in USB-C earphones.
( I tried other USB-C cables or OTG, but I did not get consistent results)

It only worked for me, by plugging in USB-C earphones.
Then, press continuously on POWER + VOLUME UP + BIXBY buttons,
and keep pressing, until I got to the Recovery,...and then I chose 'Reboot To Bootloader'.
Once in 'Bootloader Mode', I could flash using Odin.

• "Bootloop" Issues
My issues with the iodéOS not booting correctly, started because of my need to access Play Store.
This was my successful interaction with MicroG and a de-Googled ROM,
after trying in other years, to go down this path, but having a 'spare phone' now, meant I could pursue this objective.
I was trying to download some Apps (eg. a paid app that has train timetables) through Aurora Store,
Since I had no experience with Aurora Store before,
I saw the price of the app (which I had paid for many years ago already).
I panicked, and without clicking on the app, I shutdown the phone
and flashed "Phonesky_magiskv2.zip" (from Page #1 of this thread).
This was a Magisk module, since I did this a few times,
I learnt/discovered that this module didn't play nicely with the ROM,
no matter which Recovery I had (LOS-based or TWRP).

• Lygisk Root
So, I stopped flashing "Phonesky" (which was probably expecting Magisk)
and I proceeded with iodéOS as normal, flashing it with the LOS recovery.
I read more into Magisk vs Lygisk, and learnt more about
Samsung Exynos phones which have this encrypted /data folder,
which is what Lygisk is meant to address,
I got the canary release and it's been stable.

----------------------------------------------


My issue now with iodéOS ROM , is there are certain paid Apps from Play Store, which I need.
Some of these apps, need to connect to the Play Store for licence verification,
eg. Titanium Root Licence Key.

I tested my paid SD Maid and SD Maid Pro apps through Aurora Store,
and they work, but Titanium Backup does not.

I restored Titanium Backup Pro [Ti Pro] (with the Pro Key) through Swift Backup (which was through Aurora Store), on the iodéOS, but still, Ti Pro cannot check the licence and won't run.

Ti Pro was my favourite before I started facing issues on newer Android,
as I also use Swift Backup for troublesome Apps these days,
but there some things that I still like about TiPro.
I've also discovered AppDash (which looks great by the way, by a well-respected XDA developer )
and installed that successfully via Aurora Store in iodéOS .


However, I'm still looking for advice from anyone,
who can run paid PlayStore Apps on iodéOS.

I'm not too sure why you're adding root and compromising the security of the ROM Do your paid apps work without it?

 

[vince31fr]

*** New Update : 29/06/2023 ***

Upgrade to Android 13 / LineageOS 20

Available as OTA (see OP)​