Well, well, well… If the update was normally set, you should have a progression line on the computer prompt… If the phone is waiting for an update and the computer sending them, that should normally be good… Try maybe to power on your phone to see what’s happening.
Do you have something like that when you apply update sideload on the phone ?
Do not forget to first put your phone on “waiting for sideload” and then throw the file from the computer. The right prompt is written in the bottom.
It powered up and directly into recovery e, just like your photo. That is good news, no “dancing e” for 20 minutes.
However, there was no progression line on the computer prompt, nothing for a while then device not found. Recovery e looks like your photo, “Now send the package…”
I’ll try the adb sideload command again.
Okay, so there is definitely a connection problem between them. Have you accepted everything when installing adb ? The cable could be a problem. I’m not an expert on that part, but if the phone isn’t recognized it might be… Wait, have you enabled adb in the recovery before ?
It says device not found in the prompt, like before…
I tried enable adb in recovery on the phone yes.
Could it be the cable? It is an about 25 cm normal USB cable. I think something else is more likely but it could be.
Are you plugging your USB cable on a dock, or directly on the computer ports ? It may be the cable, but I’m not sure… You haven’t answered my question, have you accepted everything when installing ADB ? It may be a google driver issue. They are supposed to be given when running the adb 15sec.
I unfortunately need to leave you. I will be operational tomorrow, but I don’t know when… I’ll send you a message. Do not hesitate to look for forum on internet, like demand google: “my phone isn’t recognized in the adb shell” or things like that.
Just for fututure reference and maybe, cause I’ve done +200 Samsung by now…
The SD card slot sits on the main board and for me has never ever faild.
USB port sits on the daughter board, connected with a ribbon cable.
So when working on an S7 one may mess up the connection to the daughter board, but probably never the SD slot.
I am not sure what you mean. Accepted on the phone?
I don’t understand google driver issue. Neither I or the phone have nothing to do with google, or so I thought.
Thanks for your help today!
make-nz, a tech guy in a small shop changed the screen for me. Maybe he messed up the ribbon cable. It does charge though, but maybe thats another internal cable.
The SD slot does not work, it will not load from there.
You guys have been very helpful. Even though I may never succeed to fix this phone, I learnt so much that I am a bit tempted to get another phone and try to install from scratch, but not a Samsung (this brand seems to have some peculiarities). Maybe you have a recommendation for a cheap phone (cheap, because I will certainly mess it up) that I can try on, a model with a reputation for being a little easier to install?
Well, unfortunately the phone has something to do with Google as android is a Google product… ADB means Android Debug Bridge you know…
I ask you if, when you installed the ADB 15sec on your computer, you accepted the Google pilots that ADB asked you to install. They are pretty important, you know.
We can’t exclude an issue coming from the internal card when the guy changed the screen, but we firstly have to think that he knows his work.
As far as I’m concerned, I have always fiddled with phone that we gave me for free as they were old. I’m not a specialist in this part. Maybe see with your relatives if they have a phone they no longer use…
Google pilots? I got no such question… It asked about drivers though. It asked about system wide.
I know Android is a Google product, but here we are running a modified version of it, so I thought we have nothing more to do with Google…
Well, I meant drivers of course, sorry. You have to accept the google drivers, or it won’t work. If we are running a modified version of android, the environment is still google. But that doesn’t mean trackers.
It asked (ADB) about drivers. What does that mean and what do I do about it?
What do you mean by ask ? Normally, there is a proposition of installing the google drivers when you run the ADB installer. You accept it.
It asks “do you want to install device drivers?”. If Yes then it opens a driver install popup, the usual Windown device driver install wizard. I did not know what to do here.
Now you knows what to do…
Ye, install them or it won’t work… Then, retry the procedure.
You may think this is quite stupid but I don’t understand what drivers?
Could you precise what you don’t understand ?
Is your question «what is a driver» or don’t you understand witch driver we are talking about here ?
Well, nothing is stupide to ask. When you run the adb installer that you downloaded on clubic, it will demand you if you want to install the google drivers. I’m pretty sure you didn’t install them 
They are necessary and may be the cause of the recognition issue between the computer and the phone. If you accept, it will open a wizard that will install them. I’m talking about adb on the computer.
-------- Message d’origine --------
Thanks for your patience. I know what a driver is. What I don’t understand is what to do when ADB asks for drivers. The normal Windows “driver install wizard” opens, but I was thinking “what drivers, for what? And where are they?”. Does the wizard download them automatically? Unlikely, or so I thought. Also I didn’t know what the drivers were for, found no info on that on the pages where I studied the process. So I didn’t do anything with it.
Just run the wizard and install the drivers. It’s easy. You are just stressing. That’s a normal install wizard. 
