[LIST] Devices working with the Easy Installer

/e/ team itself stated that the easy installer should be delivering android 10 version by now so I don’t see why there would be such a problem.

For us non technical people who own a S9 already running android 10 the purpose itself of the easy installer is totally defeated if we have to realize other obscure manipulations outside the easy installer.

@Manoj, what is the current situation about the issue of the easy installer not delivering the appropriate android version for some devices?
When will I be able to flash my S9 on android 10 with the easy installer?

1 Like

Sorry I am not of much help on the S9. TWRP flashed to my S9 via Odin and on my S9+s TWRP and eOS was done using various methods combined. Good luck.

There was an issue with the q builds on v0.15 and v0.16 . This was reported here.

I didn’t find anything related to an easy installer issue with the S9 or with Q builds related to the easy installer.
Is the easy installer now delivering android Q for the S9? If not, when will I be able to install /e/ android Q on my S9 with the easy installer?

Could you answer me please @Manoj?

I think your answers are here

More details are in the other topic.

So the list in the first post of this topic is still correct (Oreo for the Samsungs, Q for Fairphone and Gigaset) :wink:

2 Likes

I believe Easy Installer is instructed to install the latest Stable build for that device.

Thanks to the very recent open publishing of the stable builds urls, users can now hope to tell what version will be installed by Easy Installer by searching for their device in the Smartphone Selector

These were my results of my search today:

Gigaset GS290 (https://images.ecloud.global/stable/GS290/) expect Q
Fairphone 3 (https://images.ecloud.global/stable/FP3/) expect Q
Fairphone 3+ (https://images.ecloud.global/stable/FP3/) expect Q
Samsung Galaxy S9 (https://images.ecloud.global/stable/starlte/) expect Oreo
Samsung Galaxy S9+ (https://images.ecloud.global/stable/star2lte/) expect Oreo
Samsung Galaxy S8 (https://images.ecloud.global/stable/dreamlte/) expect Pie
Samsung Galaxy S8+ (https://images.ecloud.global/stable/dream2lte/) expect Pie
Samsung Galaxy S7 (https://images.ecloud.global/stable/herolte/) expect Nougat
Samsung Galaxy S7 Edge (https://images.ecloud.global/stable/hero2lte/) expect Nougat

(This lack of disclosure was the reason for me offering to populate this page with /e/ version installed, which had remained a mystery! I will modify the “List” shortly making it less of a maintenance liability. Done.)

1 Like

Thank you for your answers.

What a disappointment to see that unlike what has been stated by @Manoj here, it is still impossible to flash /e/ android 10 on a S9 with the easy installer.

It makes the easy installer useless for people wanting to flash a S9 since almost all S9 have been upgraded to android 10 for a long time.
Having to do complex manipulations in order to downgrade the S9 to android 8 totally defeats the easy installer’s purpose.

@Manoj has this problem been fixed yet? If not, when will we finally be able to flash /e/ android 10 on a S9 with the easy installer?

Hi @Privacyman.

I agree the downgrade idea just so that you can use /e/asy installer makes no sense.

Have you read the manual install instructions? Where do you think you would get stuck?

I am sure there are those here who would help you.

Feel free to open a new thread with any “before you start” questions, I am sure any such thread would be useful for others too. :smiley:

1 Like

Thank you so much for your answer and help proposal but having no technical knowledge, I’m not planning to go to such lengths to install /e/ and it is the same for the vast majority of people allegedly targeted by /e/. I want to be able to recommend /e/ for other people who have a S9 or who would be interested in having one with /e/ but it is impossible since /e/ unfortunately still doesn’t offer an easy way to flash them.

I will wait /e/ team’s fix for this major flaw in order to flash my S9 and the ones of the people I know. I guess they have to fix that really quickly since such a contradiction for the allegedly easy installer makes no sense at all.

What does “except nougat” mean on the S7s? Does it mean the install will not work on phones that have been upgraded to nougat?

I haven’t bought the phone yet, so it would be good to know. As I understand it, an S7 can have anything from Marshmallow to Pie.

You are correct in thinking that a device already on Pie should not be downgraded to Nougat. Nougat is what to expect from Easy Installer today. The dev build however is Pie.

1 Like

Most of the used phones I’ve come across are still on marshmallow, so I probably won’t have a problem. I’m just kind of poor and can’t afford to make too many bricks.

@Manoj could you not ignore my questions?

Thanks in advance

No it has not been fixed . The Easy installer is a community based development initiative. Users with development experience are free to pitch in and help with its enhancement.

In this particular case, what would have to be done in the easy-installer source code? My understanding so far was that the installer always installs what is called “stable” currently.
So wouldn’t be the easy “fix” to declare Android 10 stable for starlte? :wink:

Or are you talking about letting the user choose between stable and dev channel?

2 Likes

I went through the process of attempting an upgrade of my S9 but it only reloaded v. 0.16. I probably misunderstood what was going to happen. I run Ubuntu 20.04 and loaded the Easy Installer and then downloaded e-0.16-o-20210422111918-stable-starlte.zip. I followed the installation/upgrade instructions at the devices/starlte/upgrade site. All went well but I came up with Android 8.1.
I guess I will wait for the OTA version and hope for the best.

Gigaset GS290: worked for me :smiley:

Brand new GS290, without google account, Android 10 was pre installed, only needed Wifi connection to run system update and do OEM unlock.

Easy Installer 0.12.3-beta installed via snap on Linux (Manjaro).

All steps as described in the installer were done. Installation went without problems.
/e/ 0.16-20210422111920 is now running.

Thanks!

5 Likes

A report that Samsung G960N is not yet supported.

Review of Easy Installer help request on Telegram

Our contact asked for help where mysteriously Easy Installer failed to complete.

  1. We see that we have sound contact with the device.
    OS name = Windows 10
    List of devices attached

21xxxxxxxxxxxxec device product:starltexx model:SM_G960F device:starlte transport_id:28

  1. Downloading reported ok.

validChecksum(C:\Users\DXX.xxxxx\AppData\Local\easy-installer\sources\e-latest-starlte.zip.sha256sum)
2021-05-27 13:09:41,614 DEBUG [Thread-5] e.e.i.t.DownloadTask [null:-1] ChecksumLine = ddad9d6e11f681dd4801b9fd55b911f1ea9374f9691e1055a44eaa143c5824d7 e-latest-starlte.zip
2021-05-27 13:09:41,615 DEBUG [Thread-5] e.e.i.t.DownloadTask [null:-1] createFileChecksum()
2021-05-27 13:09:44,463 DEBUG [Thread-5] e.e.i.t.DownloadTask [null:-1] compare checksum: ddad9d6e11f681dd4801b9fd55b911f1ea9374f9691e1055a44eaa143c5824d7 vs ddad9d6e11f681dd4801b9fd55b911f1ea9374f9691e1055a44eaa143c5824d7
2021-05-27 13:09:44,464 DEBUG [JavaFX Application Thread] e.e.i.c.s.DownloadSrcController [null:-1] DownloadService.succeeded()
2021-05-27 13:09:44,464 INFO [JavaFX Application Thread] e.e.i.c.s.DownloadSrcController [null:-1] startNextDownload()

  1. Fails:

(debug)C:\Program Files\easy-installer>“C:\Program Files\easy-installer\bin\heimdall” detect 1>nul
2021-05-27 13:10:10,133 DEBUG [Thread-17] e.e.i.m.Command [null:-1]
(debug)ERROR: Failed to detect compatible download-mode device.

and,
2021-05-27 13:11:14,637 DEBUG [Thread-17] e.e.i.m.Command [null:-1]
(debug)ERROR: Failed to access device. libusb error: -12
ERROR: Failed to access device. libusb error: -12

and at the end,
(debug)C:\Program Files\easy-installer>“C:\Program Files\easy-installer\bin\adb\adb” -s ““21xxxxxxxxxxxxec”” wait-for-recovery

  1. libusb error: -12 error is reported against Heimdall #243

Benjamin-Dobell commented (re the general thread there) “Hmm. it couldn’t open /dev/bus/usb/001/050, due to a general IO error, which unfortunately isn’t very specific, and is quite odd. It’s not a permission issue, because there’s a separate error code for that.
I did some quick digging through libusb and for this error message to occur POSIX open() is setting errno to EIO, which is unfortunately a general error. However, under normal circumstances, realistically it shouldn’t occur, you should get a more specific error. This makes me think that there is a driver bug, or some kind of hardware failure on your system - but it’s hard to tell with such a generic error.”

  1. [Solved] Try a different cable! The caller told us he had been using the Samsung cable that came with the device, a replacement allowed Easy Installer to complete.

What does this tell us?

Perhaps everyone planning to flash a phone should blow all their USB ports out with compressed air.

Throw away any USB cables with slack connection.

Throw away any twisted usb cables. The only good reason to wind a wire is to create an Electromagnetic force.

Buy a new data cable for good luck.