Hi,
On my side, not possible to update to 3.0 because no update is available : /e/OS community beyond0lte download
Vendor Name : Samsung
Device name : S10e
Device CodeName : beyond0lte
Version of /e/OS or Stock which existed previously : 2.9
Is the device Rooted / Not rooted : Not rooted
@Manoj , when is it plan to give again access to update for S10e (no 2.9, no 3.0) ?
Hi,
On my side, not possible to update to 3.0 because no update is available : /e/OS official tangorpro download
Vendor Name : Murena
Device name : Pixel tablet
Device CodeName : tangorpro
Version of /e/OS or Stock which existed previously : 2.9
Is the device Rooted / Not rooted : Not rooted
@Manoj , when is it plan to give access to 3.0 update for Murena product ?
Hi aibd,
Iām actually here as a result of the 3.0 update problem. I was previously on 2.9. Phone was working fine for a few days after the 3.0 update. Then the morning I posted, my phone started behaving exactly as an Anonymous user posted above in what looks like post #189:
( āfor my Pixel 5 this process doesnāt work.
The failure point is after step 8 : as soon as I unlock the screen the phone restarts automatically so I have no time to change the settings unfortunately.
Iāve tried the plug/unplug of the USB method you mentioned at steps 4 and 7 but it did not gave me more time to change settings after I entered the pin codeā¦ā)
At that point, the only way I could even turn my phone off was to pull the battery. It now boots directly into the recovery screen. I am able to āmove aboutā through that recovery mode so I think the side load will work. The problem is, I suppose I have to wait for an official Emerald build, as you also stated.
And yes, Iāve always heard to give an update a week or so and check forums before updating, but against my better judgment, I jumped the gun. Wonāt be doing that againā¦
For now, Iāve got my SIM in my previous flip phone and can run it as a hot spot for a laptop. Hopefully an emerald comes soon because I love this phone and OS. Not going back to the other guysā¦
Thank you!
Letās ask @nicofonk if there is a 3.0.1 cooking for emerald.
3.0.1 will be released for all devices which should have or got the 3.0 build. If there are any exceptions we shall update on the forum.
I just decided to wait. I was too scared to try it.
Glad to see another Zenfone 8 user
When approximately can we get 3.0.1 OTA ?
There is an update on the release dates. We are going ahead with a staggered release to avoid any issues with the roll out. The updated dates are given above.
This comes up quite often and I find that section unhelpful at best; as I understand it neither AOSP nor /e/ has tried to eliminate it.
Loosely speaking when a manufacturer gets into bed with Googleās software they undertake to keep the firmware up to date by release of Vendor Security Patches as frequently as required. Manufactures vary, some may do this for < 18 months others longer. Once Google deems the Updates were not sufficiently frequent this āTrustā is lost. Some would say that this is a fine way to encourage users to buy a new phone.
You can check the actual Vendor SPL from Settings > About phone > tap Android version.
Most devices will follow this example; with /e/OS correctly installed observing the install page (quoting lemonadep)
Before following these instructions please ensure that the device is on the latest Android 13 firmware.
this will result in the user having already installed the final manufacturerās software revision.
Of course, never mind the āTrustā issue, having the final manufacturerās software revision is very much worth checking in the event of problems.
Many /e/OS builds from AOSP 13 (T) on do actually contain the vendor parts in the ROM that provide these final blobs.
These comments should not apply in the case of a phone here the Android OS is still in active development.
Hi,
Iāve been having major problems since 3.0 and 3.0.1. Version 3.0.1 fixed the recovery boot issue, but itās also causing other major problems.
My system battery level is frozen (it wonāt go down). I was at 68%, and I recharged with the USB cable for a short while (smartphone off). Iām at 70%, and E/OS is showing 70%. However, I used the internet for 15 minutes, and the battery percentage hasnāt changed. This is a very big problem.
Regarding the internet, last night, I tried using the internet via 4G and 5G, but I couldnāt. This morning, I tried again, and itās fine (on 4G and 5G). However, IP address masking was enabled. I disable IP address masking. I restart the browser, and it tells me: āNo internet connection.ā OK. I reactivate IP address masking, I restart the browser, and it tells me: āConnection established,ā but it doesnāt display anything. I canāt connect to the search engine (errors).
Notes:
So, two major issues for now (FP4 A14 Official). A 3.0.2 version will be necessary.
Thank you very much to you.
@nicofonk for non-pactes users:
Will they be able to download and install the 3.0.1 update as usual via the built-in updater?
Definitely - while I can understand the wish/need for this āanalysisā through Trust, it is misleading in many ways and might confuse ānoviceā users.
Yes, Iāve an A14 /e/ 3.0 flashed over an A14 latest vendor setup with latest updates (probably the last updates OS-version related to this device, as the three-year support time ran out end of may, if Iām correct).
The vendor security patch level is from 5th Jan. 2024, which seems to be the latest time they added new vendor security patches in their vendor firmware (and as such in any third-party OS, as well).
Even as it is still describing A13 as the necessary firmware, I was interested in checking if it works well with the newest stock vendor updates prior to the community (only available) A14 /e/ for lemonadep.
And it works fine, no big flaws, aside those described upwards.
No crashes, sound is okay, camera app works with photos (didnāt try videos yet) and is ways more versatile and configurable compared to what official vendor ROM and LineageOS offered 2023 (LOS added GCam if Iām right on a later version).
So the āplease ensure that the device is on the latest Android 13 firmware.ā is not an ultimate necessity for the actual /e/ for this device to work fine - but it is a good information for all those which are not into the technical backgrounds and just āwant to install and use itā.
Definitely, thatās the reason why I went the ālatest stock vendor ROM updates of May 2025ā route prior to /e/, because there were critical security flaws patched by it and if some were based on the device vendor firmwareā¦ better to have them fixed. Edit: Seems not to be the case, as of the Jan. 2024 latest vendor patches.
Even if it goes against the āAndroid 13ā requirement of the FAQ.
Thatās good to know, thanks! Iām no Android programmer / developer, so even if I can understand and follow the technical compositions, I donāt have the experience to āknowā whatās standard in the ROMs nowadays, even less for /e/.
I guess the A13 instruction could be changed to āA13 or A14ā for lemonadep, if the 3.0(.1) releases are available (again), as the latest vendor parts seem to work just fine. I didnāt try it with /e/ 2.9, tho.
They work fine with A15 of LineageOS, as well, I tested this prior as they changed their information to ārequires A13 or A14 latest firmwareā in the FAQ already).
A quick information for interested users:
On OnePlus 9 Pro aka lemonadep with /e/ 3.0 the update to 3.0.1 is now available.
BUT: It does not show on each manual refresh in the update menu/component under Settings.
It sometimes takes 1 - 5 retries until it is shown.
If it is shown, donāt click ārefreshā again, else it is gone again - until you click a few times and it pops back up. 
I assume thatās a slight bug, which could be existent for other devices, as well.
So: if you want to check if 3.0.1 is available for a community build (device), you should not just refresh it once, but instead wait a few seconds and refresh it 2, 3, 4ā¦ times.
If thereās no update after 4-5 tries, it is fair to assume that it is not yet available.
Edit: If you start the download and then pause it, it will stay visible - even after refresh / check for new versions again.
(Other alternative would be to download it manually and use ālocal updateā method in the updater, but thatās more work than checking a few times.)
And: I personally would - if your device is on 3.0 right now and works without flaws - wait a few hours to days and check if there are new critical issues reported. Because there was at least one new issue reported further upwards for one device:
Many users are already aware of the nature of the āstaggered releaseā. A previous briefing included the concept of 25% available ā as if to say only 1 in 4 requests to the server can be successful. 
Ahh, I see - wasnāt sure if it was a wanted feature or a bug.
Usually in staggered distribution it isnāt refreshed to random values, but more or less linked to something - IP address of requester, client ID (not an option if thereās no identifier or it isnāt used for such purposes, which would be privacy-oriented).
This would be helpful to actually enforce the staggered distribution, as it wouldnāt change the results by each refresh, but only by a server set time span after which it is newly ādicedā.
But good to know thatās the reason. 
Interesting that the update client as well removes it from the results if it isnāt received by the query anymore (a positive effect in terms of withdrawn defective updates, which are not yet downloaded to a device, I assume).
Hello. This is my first post as I just started testing /e/OS before v3.0 was released. Everything has been running smoothly before & after the update.
Vendor Name: OnePlus
Device name: 8 Pro
Device CodeName: instantnoodlep
Version of /e/OS or Stock which existed previously: Not sure. Whatever I downloaded a week or so before v3.0 war released.
Is the device Rooted / Not rooted: Not Rooted
This is good for the user to know ā¦ but my remarks started āLoosely speakingā on the subject of Vendor SPL ā¦ I mentioned firmware revisions ā¦ but one has to bear in mind around the world there can be firmware revisions which do not impact SPL.
I say this because one should not go on to think to challenge Install instructions (not that you actually were ā¦ experimentation is fine).
Back to my concern: Install instructions
It is good information. Period.
We should perhaps look at the build frozen when the developer created the build, we look at the Device tree, there is only one branch for AOSP 13 (T) GitHub - LineageOS/android_device_oneplus_lemonadep at lineage-20.
In the Lineage world there is only one branch for a14 GitHub - LineageOS/android_device_oneplus_lemonadep at lineage-21.
In the ādevelopingā Lineage scenario there are branches for Lineage 22.0, 22.1 and 22.2. This is where the bleeding edge lies ā¦ but not where /e/ Install instructions are at.
(Maybe worth bearing in mind that lemonadp almost certainly was liberated to AOSP while active manufacturer development was ongoing ā¦ but this is not really a subject for the Feedback thread, inho.)
I followed the procedure described here: Feedback for v3.0 - #217 by nicofonk
and downloaded the correct build for FP3:
https://test.ota.ecloud.global/official/FP3/e-3.0.1-t-20250606498724-official-FP3.zip
The installation went through without any visible errors on slot B (via fastboot set_active b).
However, now my phone wonāt boot at all. It gets stuck on the Fairphone logo and vibrates every 4ā5 seconds.
I also tried booting on slot A (fastboot set_active a), but I get the same result: bootloop.
This is very frustrating. I feel completely stuck and donāt know what to do next. My phone is currently unusable, and I have important, unsaved data on it. Iām honestly really disappointed by this situation.
If anyone has advice on how to restore access to the device without data loss, I would be extremely grateful.
Thanks in advance for your help 
v3.0.1-community is now available OTA for the Fairphone 3, Fairphone 4, Fairphone 5.