Call for testing: Samsung S3 Neo (s3ve3g) owners

zenfunk

it was lineage 7.1.
I just reformated /data to ext3, but no improvement.
There are two different kinds of s3 neos around. One with Sony and one with a Samsung camera module. May this be it (not sure which one I have. Will reflash android 5.1 (which one did you use) and then we'll see.
Thank you very much for your time and efforts,
Chris

flohack

@zenfunk Hmm the camera should not block the UI to start, actually. Very weird also that you do not get ssh connection. Did you specify -p ut parameter when installing?

zenfunk

Actually I didn't use -p ut because the script then exits.

./halium-install -p ut ubports-touch.rootfs-xenial-armhf.tar.gz system.img
usage: ./halium-install rootfs.tar[.gz] system.img [release]

positional arguments:
    rootfs.tar[.gz]
    system.img

optional arguments:
    release: run common post installation tasks for release.
             supported: none, halium, pm, ut
             defaults : none

zenfunk

./halium-install ubports-touch.rootfs-xenial-armhf.tar.gz system.img ut

works, I'm trying to boot as we speak. I keep you posted.

zenfunk

Well, with the above command I got to pick a unix password, but still hangs at the boot screen.

flohack

@zenfunk Hmm seems to be the wrong halium-install, how did you get it? The right one has the parameter -p ut as first argument.

zenfunk

I got it from there: https://gitlab.com/JBBgameich/halium-install/-/releases
I downloaded the zip file, unzipped everything, put the imagefiles in the folder as well and ran the script.

flohack

@zenfunk Ohhh thats very old! The continous release is not working anymore it seems. Can you please try to clone the code instead directly? Have you got experience with git?

zenfunk

Funny, I just did this.
The -p ut option works now. dmesg output is:

[ 9620.086869] usb 2-1.2: new high-speed USB device number 20 using ehci-pci
[ 9620.200193] usb 2-1.2: New USB device found, idVendor=18d1, idProduct=d001, bcdDevice= 2.28
[ 9620.200199] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 9620.200203] usb 2-1.2: Product: SAMSUNG_Android
[ 9620.200206] usb 2-1.2: Manufacturer: SAMSUNG
[ 9620.200210] usb 2-1.2: SerialNumber: Halium initrd Debug telnet on port 23 on rndis0 192.168.2.15 - also running udhcpd
[ 9620.207225] rndis_host 2-1.2:1.0 eth0: register 'rndis_host' at usb-0000:00:1d.0-1.2, RNDIS device, 00:00:00:00:00:00
[ 9620.250120] rndis_host 2-1.2:1.0 enp0s29u1u2: renamed from eth0
chris@funkbook:~$ ssh phablet@192.168.2.15
ssh: connect to host 192.168.2.15 port 22: Network is unreachable

On reboots I don't even get the RNDIS device.

Will start over...

zenfunk

I tried again with an 5.1 Android, used the cloned installer, used your heimdall, and now I don't even get to the ubuntu boot screen.

No clue what to do next.

flohack

@zenfunk said in Call for testing: Samsung S3 Neo (s3ve3g) owners:

used the cloned installer, used your heimdall, and now I don't even get to the ubuntu boot screen.

Hmm sounds weird. what does dmesg say

zenfunk

[14506.583270] usb 2-1.2: new high-speed USB device number 41 using ehci-pci
[14506.691529] usb 2-1.2: no configurations
[14506.691542] usb 2-1.2: can't read configurations, error -22
[14506.779122] usb 2-1.2: new high-speed USB device number 42 using ehci-pci
[14507.079205] usb 2-1.2: device descriptor read/64, error -71
[14507.297126] usb 2-1.2: New USB device found, idVendor=18d1, idProduct=d001, bcdDevice= 2.28
[14507.297133] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[14507.297137] usb 2-1.2: Product: SAMSUNG_Android
[14507.297140] usb 2-1.2: Manufacturer: SAMSUNG
[14507.297143] usb 2-1.2: SerialNumber: halium-initrd
[14507.301658] rndis_host 2-1.2:1.0 eth0: register 'rndis_host' at usb-0000:00:1d.0-1.2, RNDIS device, 00:00:00:00:00:00
[14507.362236] rndis_host 2-1.2:1.0 enp0s29u1u2: renamed from eth0

flohack

@zenfunk Looks like now we are kinda stuck with the init. Can you send me again cmdline you used for halium-install?

flohack

I just found out that I linked the wrong halium-install release, in case you dont want to clone. Please use only this: https://github.com/JBBgameich/halium-install/releases

zenfunk

OK, I slept it over and also think that there is something wrong with halium-install.
I clone the script from git, put all the imagefiles in this folder and run:

./halium-install -p ut ubports-touch.rootfs-xenial-armhf.tar.gz system.img

Of course halium-install is not installed system whide that is why I have to use the ./ . I now think that there might be the culprit since your instructions don't use it.
When I use make, it gives me a script called halium-install-standalone.sh in a local bin folder which cannot be installed (no "make install" available). When I run hte standalone script it exits with an error BTW. I found no instructions about how to install the current halium- install system wide. I am sure chucking the script in /usr/bin won't do it :).

~~Your link ( https://github.com/JBBgameich/halium-install/releases) gets me to a page where I don't see any link to download stuff, what am I missing?~~ Edit: found it, it is under Assets.

flohack

@zenfunk Ok seems standalone is broken a bit - I will remove the instructions to use it. Note that there is no option to install it systemwide, so its just a convenient way to not use git for cloning.

So please do only use the git clone method

zenfunk

With standalone I don't mean the zipped version. When you do "make" in the cloned folder a script gets creeated that is called halium-install-standalone.sh and that doesn't work.

With systemwide I meant that you seem to have your halium install script in your $PATH since you don't have a ./ in front of your "halium-install" command (if you have, your instructions are wrong).

I used the git clone files and they do not work on my setup (see the four last posts).

Speiburger

Hello, today I tried to install Ubuntu Touch on my S3 Neo by following your instructions. Sadly I hit a roadblock nearly instantly: My PC does not recognize my device once it enters boot mode (adb reboot bootloader) ADB works just fine, but once I reboot into the bootloader, the device is not recognized anymore. I tried every possible solution I could find on the internet. Here is what I tried:

Using different Cables, USB Ports and even PC's
Using different installs of ADB
Using sudo
Adding my device to /udev...(I don't remember the exact location of the file)

Sorry if this is a very obvious problem, but I don't know anything else to try at this point. If someone could help me or point me in the right direction, I would be very thankful.

Best Regards,
Speiburger

flohack

@Speiburger Hi, what do you see on the device screen in this case, and whats the error output you got on the PC?

Speiburger

@Flohack The Device is in it's "Downloading, do not turn off" Mode. The same you can access by holding power and volume down. The PC just says "<waiting for any device>" and does not change untill I kill the program.

Thanks for your quick response!