Call for testing: Samsung S3 Neo (s3ve3g) owners
-
@Speiburger Hi, what do you see on the device screen in this case, and whats the error output you got on the PC?
-
@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!
-
@Speiburger What is the precise sequence of commands you type in the PC?
-
-
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
-
-
@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!
-
@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
-
@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?
-
@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...
-
@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...
-
@Speiburger Smartphones are hard to brick. But you might want to google your model number for a different TWRP then...
-
@Flohack Ok, guess I'll just try it then and report back what happened... Thanks again for your help and advice!
-
@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...
-
@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! -
@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!
-
-
@Speiburger are you sure you are in download mode again, not in recovery?
-
@Flohack 100% sure, big Downloading, do not turn off target sign.
BTW, I just realized that I didn't allow TWRP to write to my device. Could this be the Problem? -
@Speiburger No we bypass twrp normally. You can check in recovery whats the content of /data, should be a rootfs.img and a system.img
-
@Flohack Nope, in the /data folder, there is a bunch of other folders(anr,app,app-lib,etc...) does this mean the first command was not working in the first place?
-
@Flohack So I tried the first command again, no change, same error :
ln: Die symbolische Verknüpfung '.halium-install-rootfs.thm7J/cache' konnte nicht angelegt werden: Die Datei existiert bereitsIn case you don't know german, it just states that ln could not create a link .halium-install-rootfs.thm7J/cache because the file already exists.
-
Yeah seems you got 2 issues which one is that halium-install did not work out, and also seems that flashing of the boot image did not work. Are you able to join the German Telegram group, we might be able to sort it out there...
