I would like to offer a solution to a problem that I have encountered personally. Only after going through many topics did I finally find an effective method of solving it. In my case, the problem was with two Samsung Galaxy S3 Neo (GT-I9301I). After uploading the stock version: I9301IXXSAPG5, the camera stopped working. When I tried to start it, I got the error: "A server error has occurred. Please restart the camera". Restoring factory settings, reloading the software or installing other camera applications from the store did not fix the resulting error. In a few steps I will tell you how I solved the problem.
1. I downloaded the firmware version I9301IXXUANH1 from sammobile.com, but it may also be I9301IXCSAPG6.
2. I downloaded the pit file for my model: http://gsm-firmware.com/index.php?a=browse&b=file-info&id=15927
3. I launched Odin3 v1.85. For example, download here: https://osdn.net/projects/sfnet_zootop/downloads/Odin3-v1.85.zip/. In my opinion, there may also be another version of Odin.
4. In the PDA field, I chose the firmware: I9301IXXUANH1.
5. In the PIT field, I chose the pit file: S3VE3G_EUR_OPEN.pit. Note that the Re-Partition box is checked.
6. I put the phone into Download Mode: Vol- + Home + Power. Entering the download mode must be confirmed with the Vol + button.
7. I connected the phone to the computer. Remember to upload drivers to support our phone. For download, e.g. from here: http://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
8. The yellow color of the ID: COM field indicates that Odin correctly recognizes the phone.
9. I started the update by pressing the button: Start.
10. The green color and the word PASS inform us about the completion of the update process. The phone can be disconnected from the computer.
11. The phone turns on by itself. However, you have to be patient, because such a first launch after the update takes much longer than normal.
Of course, it remains to reconfigure the phone from scratch. A faulty camera should suddenly start working. I would like to add that this tutorial should be effective for all Samsung Galaxy from the information I have logged somewhere. Of course, you should search for the appropriate firmware for your model, preferably from sammobile.com and the pit file. From the information read, it can be concluded with a high degree of probability that Samsung is deliberately releasing the software versions that cause the described problem. They also send back the phones informing that the motherboard has been damaged.
I created a guide because, apart from brief information, I could not find one. I hope it will be useful to more than one person.
1. I downloaded the firmware version I9301IXXUANH1 from sammobile.com, but it may also be I9301IXCSAPG6.
2. I downloaded the pit file for my model: http://gsm-firmware.com/index.php?a=browse&b=file-info&id=15927
3. I launched Odin3 v1.85. For example, download here: https://osdn.net/projects/sfnet_zootop/downloads/Odin3-v1.85.zip/. In my opinion, there may also be another version of Odin.
4. In the PDA field, I chose the firmware: I9301IXXUANH1.
5. In the PIT field, I chose the pit file: S3VE3G_EUR_OPEN.pit. Note that the Re-Partition box is checked.
6. I put the phone into Download Mode: Vol- + Home + Power. Entering the download mode must be confirmed with the Vol + button.
7. I connected the phone to the computer. Remember to upload drivers to support our phone. For download, e.g. from here: http://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
8. The yellow color of the ID: COM field indicates that Odin correctly recognizes the phone.
9. I started the update by pressing the button: Start.
10. The green color and the word PASS inform us about the completion of the update process. The phone can be disconnected from the computer.
11. The phone turns on by itself. However, you have to be patient, because such a first launch after the update takes much longer than normal.
Of course, it remains to reconfigure the phone from scratch. A faulty camera should suddenly start working. I would like to add that this tutorial should be effective for all Samsung Galaxy from the information I have logged somewhere. Of course, you should search for the appropriate firmware for your model, preferably from sammobile.com and the pit file. From the information read, it can be concluded with a high degree of probability that Samsung is deliberately releasing the software versions that cause the described problem. They also send back the phones informing that the motherboard has been damaged.
I created a guide because, apart from brief information, I could not find one. I hope it will be useful to more than one person.
