• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
UBports Robot Logo UBports Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Call for testing: Samsung S3 Neo (s3ve3g) owners

Scheduled Pinned Locked Moved Porting
97 Posts 13 Posters 25.7k Views 4 Watching
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • F Offline
      flohack @zenfunk
      last edited by 6 Feb 2020, 21:50

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

      My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

      1 Reply Last reply Reply Quote 0
      • F Offline
        flohack
        last edited by 6 Feb 2020, 22:26

        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

        My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

        1 Reply Last reply Reply Quote 0
        • Z Offline
          zenfunk
          last edited by zenfunk 2 Jul 2020, 06:00 7 Feb 2020, 05:54

          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.

          F 1 Reply Last reply 7 Feb 2020, 08:42 Reply Quote 0
          • F Offline
            flohack @zenfunk
            last edited by 7 Feb 2020, 08:42

            @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

            My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

            1 Reply Last reply Reply Quote 0
            • Z Offline
              zenfunk
              last edited by zenfunk 2 Sept 2020, 07:26 7 Feb 2020, 17:00

              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).

              1 Reply Last reply Reply Quote 0
              • S Offline
                Speiburger
                last edited by 22 Feb 2020, 21:56

                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

                F 1 Reply Last reply 22 Feb 2020, 22:59 Reply Quote 0
                • F Offline
                  flohack @Speiburger
                  last edited by 22 Feb 2020, 22:59

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

                  My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                  S 1 Reply Last reply 23 Feb 2020, 12:53 Reply Quote 0
                  • S Offline
                    Speiburger @flohack
                    last edited by 23 Feb 2020, 12:53

                    @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!

                    F 1 Reply Last reply 23 Feb 2020, 20:41 Reply Quote 0
                    • F Offline
                      flohack @Speiburger
                      last edited by 23 Feb 2020, 20:41

                      @Speiburger What is the precise sequence of commands you type in the PC?

                      My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                      S 2 Replies Last reply 23 Feb 2020, 20:44 Reply Quote 0
                      • S Offline
                        Speiburger @flohack
                        last edited by 23 Feb 2020, 20:44

                        @Flohack

                        • First adb reboot bootloader ; this works with no problems

                        • Second fastboot oem unlock ; This causes the problem I described before.

                        I am pretty sure it is a driver problem or a problem with my permissions

                        1 Reply Last reply Reply Quote 0
                        • S Offline
                          Speiburger @flohack
                          last edited by 25 Feb 2020, 20:58

                          @Flohack Ok, quick question, from my research I concluded that I need heimdall to install the twrp and not fastboot.I also found out that the bootloader of the SIII Neo is probably unlocked from the beginning. Is this information correct? If yes, would it be enough to just flash the twrp via heimdall and continue with the installation?

                          Thanks for your quick answers and effort of porting!

                          F 1 Reply Last reply 25 Feb 2020, 21:44 Reply Quote 0
                          • F Offline
                            flohack @Speiburger
                            last edited by 25 Feb 2020, 21:44

                            @Speiburger Ok sorry I confused you:

                            • Samsung devices use a totally different bootloader concept
                            • Samsung devices are always unlocked
                            • I fixed the description: Just flash the recovery with Heimdall (I updated the step there) or follow TWRP description for Samsung on the net

                            My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                            S 1 Reply Last reply 26 Feb 2020, 10:41 Reply Quote 0
                            • S Offline
                              Speiburger @flohack
                              last edited by 26 Feb 2020, 10:41

                              @Flohack ok, thanks for your effort! While making extra sure I have the correct files and the correct device, it came to my attention that I have a GT-9301i and not a GT-9300i. So I guess I should not procced with the installation as it would probably brick my device?

                              F 1 Reply Last reply 26 Feb 2020, 17:37 Reply Quote 0
                              • F Offline
                                flohack @Speiburger
                                last edited by 26 Feb 2020, 17:37

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

                                GT-9301i

                                Oh thats the dual SIM right? This might need some modifications for supporting the 2nd SIM slot, but basically it should work, just go to try it...

                                My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                                S 1 Reply Last reply 26 Feb 2020, 18:50 Reply Quote 0
                                • S Offline
                                  Speiburger @flohack
                                  last edited by 26 Feb 2020, 18:50

                                  @Flohack I don't think i've got a second sim slot. Honestly IDK what the difference is, the only thing I know is that it's this model number. Just wanted to make sure I don't brick the system with a wron recovery. BTW, I read that in this thread that this smartphone runs android 5.1? My device never got an update over KitKat...? Strange...

                                  F 1 Reply Last reply 26 Feb 2020, 19:08 Reply Quote 0
                                  • F Offline
                                    flohack @Speiburger
                                    last edited by 26 Feb 2020, 19:08

                                    @Speiburger Smartphones are hard to brick. But you might want to google your model number for a different TWRP then...

                                    My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                                    S 4 Replies Last reply 26 Feb 2020, 19:36 Reply Quote 0
                                    • S Offline
                                      Speiburger @flohack
                                      last edited by 26 Feb 2020, 19:36

                                      @Flohack Ok, guess I'll just try it then and report back what happened... Thanks again for your help and advice!

                                      1 Reply Last reply Reply Quote 1
                                      • S Offline
                                        Speiburger @flohack
                                        last edited by 26 Feb 2020, 19:50

                                        @Flohack Soooo.. I tried installing the TWRP. The file is the same for both devices. Heimdall sent no errors, but I am not able to get into the recovery.... Neither Power + Vol. down nor Power + Home + Vol. down works. It always boots into the default recovery...

                                        1 Reply Last reply Reply Quote 0
                                        • S Offline
                                          Speiburger @flohack
                                          last edited by 26 Feb 2020, 20:25

                                          @Flohack Update 2: GOTCHA!
                                          When I press the Vol. up key just after uploading the recovery and it automaticly updates, I can get into the recovery! So next thing for me is to try and install ubuntu touch on it!

                                          1 Reply Last reply Reply Quote 0
                                          • S Offline
                                            Speiburger @flohack
                                            last edited by 26 Feb 2020, 20:43

                                            @Flohack And now I reached the next Problem:

                                            • The first command appeared to be working, complaining about not being able to create a link in the end because the file already exists.

                                            • Now for the bigger problem: In the last command, heimdall tries to download the PIT file but fails... When installing the TWRP before it worked without any Problem. I tried different cables and different USB Ports...

                                            Any Ideas on how to find the PIT are welcome!

                                            F 1 Reply Last reply 26 Feb 2020, 21:01 Reply Quote 0
                                            • First post
                                              Last post