No only can, it WILL, sadly.
Speculation, nicofonk perhaps used testing channel as it seemed expedient for this overnight replacement.
The .zip file extension I know you know indicates an archived or bundled package while we see .img where loosely speaking the file aims to fill a partition.
Oh, that I know, sure. I am a software engineer, just made a (ehmmā¦ stupid) mistake last night. However, I got intrigued by that differentiation between official vs. testing.
That is why I am asking.
it still doesnāt work.
thereās a problem with adb on mac
1 Like
Try using a complete path instead of the file name only. Thatās what i usually do and it has always worked so far.
However, i have not been a mac user for a long timeā¦
It would be more useful if you show the error.
But if you think adb is the problem rather than path, I think others have said that it may be more correct to put platform-tools in the Applications folder ā¦ or similar [1] ā¦ as executable items cannot work in all areas of a Mac (if my partial understanding is correct).
[1] Or according to Quick Guide to Installing Android SDK Platform Tools on macOS and Windows - DEV Community
Extract the contents and move the folder to a directory like /usr/local.
Edit. Reading more, this /usr/local advice may require following a further link for full usability.
1 Like
The forum system just remembered me that Iāve been in this community for 5 years now.
Five years with /e/os!
Thankās @Manoj , thankās DevTeam, thank you all in this community!
5 Likes
I succeeded, with the help of 2 great people here! thanks to them!
thanks, 2 people helped me in private, and it was due to the cable. On new macs, you have to have a sort of hub to plug your mac, and when I connected my phone directly to my mac, and not to the hub, it worked okā¦ā¦ā¦.
can tell that to other mac users in my case!
thanks
|
TransfƩrƩ depuis ls1sztad5@mozmail.compar Firefox Relay Premium
|
0 traqueur dāe-mail supprimĆ©
GĆ©rer cet alias
|
- | - | - |
|
|
aibd /e/ user |
vega:
āterminalā @ordi-fano platform-tools % ./adb sideload e-3.0.1-t-20250606498706-official-FP5.zip
adb: failed to stat file e-3.0.1-t-20250606498706-official-FP5.zip: No such file or directory
When you change directory to platform-tools you have access to adb.
You do not seem to have access to
e-3.0.1-t-20250606498706-official-FP5.zip: No such file or directory
Please try moving a copy of e-3.0.1-t-20250606498706-official-FP5.zipinto the platform-tools directory.
Hi @Manoj im glad the issue has been found and fixes are being rolled out! 
Could you let me know about my case? What do I do now? I dont think waiting longer will help so do I send the phone in to you guys? I do need it for work urgently even if resetted as I dont have an alternative device. Again, just to be clear, I cant access adb on this fastboot loop so I probably cant update.
OTA updates will not work from Fastboot mode. Recovery of data cannot be done from Fastboot, but this is not to say that paid for āExpert recoveryā would be impossible.
A stable Fastboot mode will allow a fresh install. Unlock and total loss of data is involved.
To find the e-3.0.1 install ROM for FP4, the source Post #217 we are given the link to the Update ROM
FP4: https://test.ota.ecloud.global/official/FP4/e-3.0.1-a14-20250607498722-official-FP4.zip
If we prepend IMG- to the file address we get
- https://test.ota.ecloud.global/official/FP4/IMG-e-3.0.1-a14-20250607498722-official-FP4.zip
- https://test.ota.ecloud.global/official/FP4/IMG-e-3.0.1-a14-20250607498722-official-FP4.zip.sha256sum
This will install as Install /e/OS on a Fairphone FP4 - āFP4ā.
Greetings,
New here. Iām not an expert at this stuff so apologies if I sound like a noviceā¦
Running a Teracube 2e (2021) and attempting this sideload fix with a Linux machine. Currently stuck on Download /e/OS 3.0.1 on your computer step 5. Find the e-3.0.1 build. For my device, I click on S official and Iām directed to the link below:
https://images.ecloud.global/official/emerald/
I donāt see a 3.0.1 option for me, but above there is a link: Release notes available here. Clicking that sends me to a page were I can only GUESS my appropriate option would be scrolling down to the v3.0.1-s option. Link/screenshot:
When I hover over the Source Code (zip) link, I donāt see that the file name contains the word āofficialā.
My questions are, should we avoid using this file, if so why? Do we need to wait for the 3.0.1 official to be listed as in my first link, and if so, when can we expect to see it there for we Teracube Emerald folks?
Thank you in advance.
2 Likes
After 4 days of using my s7 with v3.0 (same header information as obacht) everything still seems fine, not even disturbing statements about the ownership of my device as obacht and didou report. Thanks again to all of you at e! 
3 Likes
Hello
From USA
Teracube 2e (emerald)
All went well with downloading/installing 3.0 .
3.0-s-20250528496287-official-emerald
Previous version 2.9 official
Build
e_emerald-user 12 SQ3A.220705.004 eng.root.20250528.163613
Device not rooted.
Running Android 12
OS very responsiveāeverythibg works!
Many thanks to the teamā¦Excellent work!
āBill D
1 Like
- Are you still on e-2.9?
- Did you already update to e-3.0?
- Is e-3.0 problematic in any way?
Personally I would hold on unless you have a problem. It would seem that any even slightly ādubiousā builds were withdrawn; this protects users from any further risks and they can expect to be able to update ānormallyā OTA when an āapprovedā update becomes available.
Even then many users would wait say 7 days after seeing the update offered on the device and watch this thread for āissuesā.
Meanwhile if you do have a problem, there is a revised list of 3.0.1 builds listed in Post #217 but I do not see emerald there at present.
2 Likes
Could you provide us the md5sum and sha256sum files for these files (#209 by nicofonk) ?
I want to check it for the e-3.0.1-a14-20250607498722-official-FP4.zip file.
Thanks.
1 Like
you can download such files by adding the extension at the end of the url I shared.
examples:
2 Likes
Hi All,
I have also a OP8T kebab with /e/OS 2.9U. The OTA update to /e/OS 3.0 goes smoothly.
Nevertheless a couple of things to notice :
- My caldav agenda has disappear from agenda app. The murena agenda is still visible but my main agenda is not! My main agenda is hosted on another caldav server (mailo.com). I donāt success to put it back and still investigating on that strange behavior. It seems the old account parameter app (looking like Davx5) is not fully operational. In some case I have a new parameter display, a little bit weirdā¦
- Iām surprised the V3.0 img file has been discarded from the image server. Iām quite sure it was here on last friday (june 6th). What does it mean, a major bug???
Hello to everyone,
recently Iāve had a reason to full reset, update and experiment with one of my phones and so far Iām quite happy with /e/ OS. Cleaner and more functionally (basic system applications) than microG LineageOS, let alone the brand original stock ROMs, which are a bloatware- and telemetry-horror.
Vendor Name: OnePlus
Device name: OnePlus 9 Pro Europe Vers. (LE2123)
Device CodeName: lemonadep
Version which existed previously: Varying. Before /e/ 3.0 it was Stock OxygenOS 14.0.0.1901(EX01)
Is the device Rooted / Not rooted: Not rooted right now.
Thereās only a community version for this device, so thatās what I used.
Iāve experimented with vendor most recent Android 14 (OxygenOS 14.0.0.1901) as full update(s) after flashing a clean vendor partition array via MSM tool.
Initially as an experimental tryout, if it would work based on this A14 (I could always reset it, even if it soft-bricked).
Afterwards flashed the necessary /e/ partitions (dtbo, vbmeta and vendor_boot) via command line, then sideload of the community 3.0 /e/ for lemonadep.
Almost everything works fine and without any noticeable hassle.
What caught my attention in terms of bugs:
ā there are three antenna signal strength symbols in half-extended scroll down, while (left) two are clones (dual SIM phone, no eSIMs).
In full-extended (two time scroll down) mode only one sim is shown with one signal strength (antenna) icon.
ā The āDark designā - āfull / pure blackā function works in several desktop menus, as shown in the images upwards, but as example in āsettingsā it is a light grey not āOLED full blackā option.
ā The āTrustā status shows āvendor: outdatedā, while it is presumably newer than recommended (latest official security vendor update which the device probably gets, as update timeline ran out after it).
Those aside it works, even with the unfortunate bug found in 3.0 mostly associated by the unfortunate FairPhone users (fixed in 3.0.1 that might take a few days for community versions like mine for the OnePlus 9 Pro) Iāve had no problems aka automatic reboots or even just any crash, it never crashed anything.
Flashing hung two times at restarts, which was easily fixable by manual enforced shutdown, but thatās possibly linked to me not using an A13 vendor image priorly to /e/ 3.0.
Another find is related to the embedded Google applications (mainly Google assistant) in a probably non-functional form as system app, which was initially mentioned for the OnePlus 9 Pro by @Ahappo in this thread:
It was brought to attention by @particularteal as the threadās Original Poster for another device initially.
Thank you, @Manoj and all others for the good communication regarding the withdrawal of v3.0 and the coming v3.0.1.
Iām interested if other users of v3.0 on the OnePlus 9 Pro or different devices as well experience the mentioned effects with signal strength symbol / pure black mode on their devices.