Yes, I am doing that. However, once I get to the Download Mode, I can go no further as I cannot get a connection between the phone and the laptop.
Does this mean that I cannot install eOS on a Samsung Note3 using Linux? I don’t have a Windows computer to try with that.
I am running V1.4.0. Do you think that might be the problem?
The Heimdall project does not provide package for the last version. So you need to build it manually from [our fork]
(https://gitlab.e.foundation/e/tools/heimdall).
The binaries provided by /e/ web site [here]
(https://images.ecloud.global/tools/heimdall/)
are just working for ubuntu, if you use another distribution, you have to build them
V1.4.0 is a very old version.The /e/ documention also → recommends Heimdall v1.4.2 via → Build Heimdall.
These requirements for flashing /e/ OS ROM are not easy for everyone to understand. In contrast, using Samsung’s Odin3 under OS Windows Desktop Computer is a breeze.
Thank you again. I’ll have a go at building Heimdall although this will be new to me.
If I can get access to a Windows OS machine and dowload Odin3, is the flashing process the same as the instructions I have been following?
Yes, Odin3 does the “same” as Heimdall.
See also → [HOWTO] Install /e/ on a Samsung smartphone with Windows easily
OK, I’ll look at both methods and see how I get on. It will be a few days before I get a chance to do this but I will post back on here and let you all know how I progress.
https://linuxfr.org/news/installer-lineageos-sur-son-appareil-android
.
i think you can find the solution to your problems with the fastboot command-lines describes in the superman’s how-to, in french :
.
Boot to your Stock-ROM,
in the dev options, enable ADB debuging,
reboot the device in “bootloader” mode by typing :
adb reboot bootloader
Check if the device is reconised by the PC :
fastboot devices
if it ils good, type :
fastboot oem unlock
fastboot flashing unlock
Then reboot the device by :
fastboot reboot
return to the dev options and re-enable “ADB debugging” and “OEM unlock” if you find it.
.
Samsung devices don’t support “Fastboot” - only “ADB commands.” You need Odin or Heimdall to flash.
The tool “Minimal ADB and Fastboot” is a slim alternative to the extremely extensive and complex Android SDK complete package. Samsung devices can only use the ADB commands.
Other devices like the manufacturer Xiaomi need ADB & Fastboot commands.
This explanation looks to be more for people at my level - I find it a bit easier to understand. I will try to get access to a Windows machine and give it a go.
If you have questions - ask. You are not alone…
Hi
Have a look at my own experience with N9005
I have /e/ running for a year now.
If you have access to a Windows computer, download and install …
and follow this instruction …
N©te → I’m archje a.k.a. archie.
This link takes me to a ‘Page Not Found’. I tried to work back through the Samsung site to find the files. It prompts me to create an account - but it won’t let me as it requires a US zip-code. Do you have a link to a EU/UK Samsung site?
This Samsung’s website was still available this morning.
Click on the picture and you will get a serious Samsung Driver download.
You don’t need to register anywhere. The downloads for → Samsung Driver and → Odin3 are without obligation to register.
Many thanks, I got the drivers at that site.
archje: This proved to be a very useful link. I borrowed a Windows laptop and between the advice on this link and other advice provided by yourself and others on here, I have successfully installed /e/ on my Note 3.
I am very grateful to you all. I have made my first call and so far so good.
If I come upon any little problems, I hope you won’t mind if I ask again for your help.
Thank you again to all who took the time to offer me help and advice - I am now an /e/ user.
I will of course donate to the e.foundation as a thank you.
archje:
i have the phone running an it makes calls, texts, browses etc - so I am more than happy with it.
I have noticed a couple of wee things, one of which is that when I connect my phone to the laptop via USB, the laptop ‘sees’ the device but there are no files or folders showing.
If I ADB the phone I get a message:
'no permissions (user in plugdev group; are your udev rules wrong?)
I am curious now as to what this means and to know if it is something I should be able to fix by adjusting settings. I have looked all through settings but cannot find anything that looks likely.
This is not preventing me from using the phone however other than I cannot copy/move files betwee the two devices.
@dsimpson,
in order to be able to offer specific assistance, it is always important for me to know which desktop computer system is used to run the (ADB) commands, i.e. Windows 10, 8.1 7 or Linux (Ubuntu, Mint, elementary OS, etc.).
At first sight I assume that after successfully flashing under Windows you are now working with the Linux PC again, right?
If so, I suspect that this issue isn’t able to access the AdB shell due to some permission restrictions.
Try to use it with sudo permissions i.e. “sudo adb devices” .