Stock android installation file script not working - how to install stock android without install script

Hello everybody,

I’ve installed E/Os on my Fairphone 4 5g. I want to re-install the stock android. But when I try ti run the installation script, as on the help page “https://support.fairphone.com/hc/en-us/articles/18896094650513-How-to-manually-install-Android-on-your-Fairphone” I get teh error that git bash can’t be found. I’ve tried adding to PATH. I run the script as administrator.

Is there another way, without the script, to install stock android on the FP4

Kind regards,

Stijn.

what are the possible OSes on your Computer ?

Ah sorry for the incomplete information, It is windows.

But when I run git bash as administrator and install E/Os it works like a charm.

I looks like the script can’t locate git bash or something.
The only line in the script is:
start bin-msys\git-bash.exe -c “./flash_fp4_factory.command”

Is there a possibility to run the script straight from git bash, as in; open git bash and run the “./flash_fp4_factory.command” Or what is the correct command to do so?

I’m not used to command line tools enough to fiddle around with them and try by trial and error.

I never had git bash on my PC and dont think this is needed to install FPOS? Maybe uninstall (if possible)?

The installation package contains the git bash.

Is the downloaded ZIP file corrupt? Or only partially extracted (you did first extract the ZIP file, right)?

And yes, if you start the git bash directly in the folder where the files of the extracted ZIP are located it should work by doing

./flash_fp4_factory.command

I fully extracted the archive.

The error explicitly refers to the fact it can’t find “bin-msys\git-bash.exe”. Even though it is present in the folder bin-msys.

I did work a lot with several git applications on this computer so maybe it has something to do with that.

I’ll try to start git-bash directly and execute the script. Hopelfully it works. I’ll keep you posted.

I did work a lot with git on this computer, so maybe the conflict is somewhere in the git applications i use.

It worked when I ran git_bash as administrator and ran the code as you suggested.

It did not solve my initial problem, it sure is a good workaround.

Thank you very much everybody for your help!