Database Users

[UNBRICK Guide][for Bootloader v1 jb only][I9195]How to unbrick your device

Disclaimer:
I'm not liable to any demage to your device, including Knox. The information here is as good as I know, there is no guarantee.
(If you like to provide extra information or have a correction, I'll add it to the OP)
>>I'm searching for more full repair firmwares (Containing, PIT, Bootloader, etc. seperated), if anyone could send me the files for I9195 and I9192 etc. i'd upload them too, please help and help others.<<
There are several types of a brick:
Bootloop (usually possible to unbrick)
Stuck at splash screen (a bit harder but still usually possible)
Hardbrick (black screen and nothing works) (there is also a possible solution but it could also mean the end)
Full brick (black screen, nothing works, even the hardbrick method doesn't work. solution could be using a JTAG)
How to unbrick a bootloop and stuck at splash screen brick
Download one of the repair firmwares from here
I9195 Here
Thanks a lot for providing the I9195 files to: @b0g
PIT file:
https://drive.google.com/file/d/0Bx2R0nz6jh17bllKenctWnVsWkE/edit?usp=sharing
Other files:
https://drive.google.com/file/d/0Bx2R0nz6jh17aEVHMHkwLVRjWVE/edit?usp=sharing
###########################################################################################
- Unzip/unrar the files
- Install usb drivers and use the Odin program
- Put the files like the following:
(file names starting with: )
Bootloader (BL) > BOOTLOADER...
PDA (AP) > CODE...
PHONE (CP) > MODEM...
CSC > CSC...
PIT > CSB...
- Make sure your device has enough charge 40% is recommended
- Enter download mode (press volume down + home + power button in the booting process for around 20 seconds)
- connect your device (Odin should say "Added")
- Click start (do NOT disconnect your device or restart your computer in the flashing process, this could make things worse)
- Wait until the phone has fully reset and enter the recovery
- Do a "Factory reset" and "Wipe cache"
- Reboot
- Done
How to unbrick a Hardbricked phone
- Buy a USB-JIG online
- Make sure that the devices battery has charged (even if it doesn't show charging animation)
- Remove your battery
- Plug the USB-JIG inside your phone
- Wait 3 minutes and put the battery back inside
- Wait 40 seconds and the "download mode" screen should appear
- Follow the steps like in the "Bootloop and stuck at splashscreen guide" as above (note: you don't have to enter download mode because using the JIG it should enter it automatically)
Credits:
Me
@b0g

reserved

edited

I9195 mirror at Google drive added
Huge thanks go to @b0g for providing the files for I9195! :good:

hi.
i search a solution repair my s4 mini for hours. tried many ways on this forum and others, but nothing works. so i found this and use the data follow the steps above to ressurrect my phone of bootloop and stuck.
odin flashs correctly i think, but after the reset the phone stucks in "recovery booting..."
i checked autoreboot and re partitition, unchecked f reset time. the odin log says everthing ok:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_OXA_I9195OXABML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> persist.img.ext4
<ID:0/003> persdata.img.ext4
<ID:0/003> NON-HLOS.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
what can i do, please help?

skortax said:
hi.
i search a solution repair my s4 mini for hours. tried many ways on this forum and others, but nothing works. so i found this and use the data follow the steps above to ressurrect my phone of bootloop and stuck.
odin flashs correctly i think, but after the reset the phone stucks in "recovery booting..."
i checked autoreboot and re partitition, unchecked f reset time. the odin log says everthing ok:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_OXA_I9195OXABML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> persist.img.ext4
<ID:0/003> persdata.img.ext4
<ID:0/003> NON-HLOS.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
what can i do, please help?
Click to expand...
Click to collapse
try flashing twrp recovery and wipe all then (despite external sd)
also try flashing with f reset time enabled...

thanks for the quick help. flashed twrp and it boots in recovery, but full wipe doesnt run, so i wiped manually - unfortunately i get bluescreen and i am again at the beginning.
every method i tried ends with the same result: bluescreen, blackscreen, greenscreen and every other existing screen, in every possible loop or odin stuck during the flash process
i think the problem lies deeper and can only be solved with jtag, if it is not an hardware error. what do you think?

Hi I'm having a similar issue with my i9195 getting stuck on boot screen. I think mine has something todo with the new battery i got for it, as the new one only has 3 pins and the old has 4?
one way i found of being able to boot my phone was to take out the battery plug the charger in then put the battery back in once the green battery icon shows that it is charging hold the power until it vibrates and it should (it does for me) start up, i was also able to get into recovery using the above method by holding the home and volume up as normal.

Thanks for this, I will probably use it in near future.

Please someone has the i9192???

Aronuser said:
....
I9195 Here
Thanks a lot for providing the I9195 files to: @b0g
PIT file:
https://drive.google.com/file/d/0Bx2R0nz6jh17bllKenctWnVsWkE/edit?usp=sharing
Other files:
https://drive.google.com/file/d/0Bx2R0nz6jh17aEVHMHkwLVRjWVE/edit?usp=sharing
###########################################################################################
- Unzip/unrar the files
- Install usb drivers and use the Odin program
- Put the files like the following:
(file names starting with: )
Bootloader (BL) > BOOTLOADER...
PDA (AP) > CODE...
PHONE (CP) > MODEM...
CSC > CSC...
PIT > CSB...
- Make sure your device has enough charge 40% is recommended
- Enter download mode (press volume down + home + power button in the booting process for around 20 seconds)
- connect your device (Odin should say "Added")
- Click start (do NOT disconnect your device or restart your computer in the flashing process, this could make things worse)
- Wait until the phone has fully reset and enter the recovery
- Do a "Factory reset" and "Wipe cache"
- Reboot
- Done
.....
Click to expand...
Click to collapse
hi !
can i use this part for to try to downgrade a KK firmware to JB ???!!!
have to check "re-partition" ???

Loulou-13 said:
hi !
can i use this part for to try to downgrade a KK firmware to JB ???!!!
have to check "re-partition" ???
Click to expand...
Click to collapse
yes check re partition, ah and it's not sure yet if it's possible to downgrade from KK i wanna know myself please tell me the result if you know it

yes ,i think i will try it , but i'm "nervious" with re-partition and pit ! i'm a little afraid ...
i would have prefered an advise to a person"spécialist" who know Samsung very well ...... before testing with this flash .
but i know "re-partition" and Odin (I have already had olds Samsungs )
it's principaly the **** of **** of ****** of HELL "Knox" who scares me ...
The pit here is REALLY the good ???
There are devises who have good(s) method(s) for to downgrade , there are other that it's really impossible ..... but for the S4-mini ,nobody have done expérimenations about ,no tutorials ...etc ...
everybody flash as one file .tar now ...
EDIT !
maybe the master @arco68 can answer to this problem ???!!!

... no idea ?!

Hello, can you please help me? I have problems with random restarting of my i9195 S4 Mini (Vodafone). I tried to flash another official ROM, but this problem remains. When I try flash back original stock ROM (or any other ROM - with root or without root), the results are still same - FAIL message in ODIN after aboot.mbn file.
I tried this guide, but again, everything was ended with fail message (check the attached log).
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_OXA_I9195OXABML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can you please help me and tell me what I can do if I want to put back any stock ROM? I am going crazy with the fail message which shows me in every try. Checked with Odin 3.09, 3.07, 1.83 and still no success.

jerrry said:
Hello, can you please help me? I have problems with random restarting of my i9195 S4 Mini (Vodafone). I tried to flash another official ROM, but this problem remains. When I try flash back original stock ROM (or any other ROM - with root or without root), the results are still same - FAIL message in ODIN after aboot.mbn file.
Can you please help me and tell me what I can do if I want to put back any stock ROM? I am going crazy with the fail message which shows me in every try. Checked with Odin 3.09, 3.07, 1.83 and still no success.
Click to expand...
Click to collapse
Can you tell what is the text in download mode screen? If the last 2 lines say BOOTLOADER SW REV : 2, then you have latest bootloader and IT IS IMPOSSIBLE TO DOWNGRADE.

sasank360 said:
Can you tell what is the text in download mode screen? If the last 2 lines say BOOTLOADER SW REV : 2, then you have latest bootloader and IT IS IMPOSSIBLE TO DOWNGRADE.
Click to expand...
Click to collapse
Thank you for reply. Yes, I have Bootloader AP SWREV: 2. But what can I do if I want to change actual ROM which is flashed in device? I would like to get back original Vodafone ROM (stock), but I can't do anything (flash same ROM which is now in device, flash Vodafone ROM, flash custom ROM).

jerrry said:
Hello, can you please help me? I have problems with random restarting of my i9195 S4 Mini (Vodafone). I tried to flash another official ROM, but this problem remains. When I try flash back original stock ROM (or any other ROM - with root or without root), the results are still same - FAIL message in ODIN after aboot.mbn file.
I tried this guide, but again, everything was ended with fail message (check the attached log).
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_OXA_I9195OXABML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can you please help me and tell me what I can do if I want to put back any stock ROM? I am going crazy with the fail message which shows me in every try. Checked with Odin 3.09, 3.07, 1.83 and still no success.
Click to expand...
Click to collapse
I had the same issue (aboot.mbn failing and finally I managed to fix it by flashing I9195XXUCNE6_I9195OXACNE6_DBT with Odin 3.09. Downloaded the firmware from sammobile (http://www.sammobile.com/firmwares/3/?confirm=31540). Had to wipe data/cache after flashing the ROM. Not the ROM I wanted, but at least now I have a working S4 mini again.

jerrry said:
Thank you for reply. Yes, I have Bootloader AP SWREV: 2. But what can I do if I want to change actual ROM which is flashed in device? I would like to get back original Vodafone ROM (stock), but I can't do anything (flash same ROM which is now in device, flash Vodafone ROM, flash custom ROM).
Click to expand...
Click to collapse
skip the modem file and the bootloader file at flashing and you should be fine

Aronuser said:
skip the modem file and the bootloader file at flashing and you should be fine
Click to expand...
Click to collapse
How can I skip these files? Because in ODIN I am selecting just only one file.

[AT&T S7] Please help if you can. ODIN flashing stock error

EDIT: I HAVE SOLVED THE ISSUE. I am not sure how but I got into a different download mode and the flash worked. I also used different SM-930A Files and it worked but system status is still custom.
I want to put my phone back to stock after I have installed a custom ROM. I have an AT&T S7. I get this error while flashing the firmware using Odin
----------------------------------------------------------------------------------------------------------
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
------------------------------------------------------------------------------------------------------
On the phone it says the following
"SW REV CHECK FAIL : [system]Fused 3 > Binary 1"
If you could tell me how to flash my phone back to stock without getting this error it would be very much appreciated.

I got the same error a while back. For me, it was because I was using Odin 3.11.1. Once I updated to Odin 3.12.3, the restore went smoothly. Someone correct me if that's not the way to fix this issue, but that is what worked for me.

lukemarcondes said:
I got the same error a while back. For me, it was because I was using Odin 3.11.1. Once I updated to Odin 3.12.3, the restore went smoothly. Someone correct me if that's not the way to fix this issue, but that is what worked for me.
Click to expand...
Click to collapse
I have resolved the issue. I have been trying for almost a month now to fix the phone and I finally did it. The device still says custom although I have flashed the official firmware on. Somehow I got into an alternative download mode that accepted the flash. I have no clue how I got it into the mode but it only said "downloading" and showed nothing in the top right corner. No white text.

ColbyTrip1 said:
I have resolved the issue. I have been trying for almost a month now to fix the phone and I finally did it. The device still says custom although I have flashed the official firmware on. Somehow I got into an alternative download mode that accepted the flash. I have no clue how I got it into the mode but it only said "downloading" and showed nothing in the top right corner. No white text.
Click to expand...
Click to collapse
I see. Glad you were able to fix it!

UnRoot Not Working (Save Me Please!!!)

So a few months back I followed PSouza's guide (https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039) to rooting the S7 Edge and everything worked perfectly. As of late, the phone has had many general performance issues and I decided today unrooting may be the best option for right now. So I cracked back open the thread and followed the instructions and low and behold, as always, something had to go wrong. For starters, Odin gives me a fail before it even really gets started (log below).
"<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!"
The phone itself gives a SW Rev check fail after that (in the download mode).
So I thought to myself I'd just keep it in the meantime and just restart it and use it for now, but low and behold I now can't leave download mode. If I restart regularly, I'm brought back to a software update failed screen, and if I switch to recovery mode (? vol up + home + power) I've wiped the cache partition as another forum suggested, but then going to reboot system now... That restart brings me right back into recovery. I currently have the phone off charger in hopes the battery dies and something changes then.
I'm also downloading the very very latest firmware update for the S7 Edge in hopes that maybe Odin will like it a bit better than this one (VZW_G935VVRU2APE1.zip).
Any ideas? Any solution that gets me a working phone again, I'll definitely make a donation to your PayPal! Thanks in advance for any help!

To anyone reading this having the same issue, follow the instructions in this post (https://forum.xda-developers.com/showpost.php?p=71133959&postcount=27) worked like a charm.

zwroberts1 said:
To anyone reading this having the same issue, follow the instructions in this post (https://forum.xda-developers.com/showpost.php?p=71133959&postcount=27) worked like a charm.
Click to expand...
Click to collapse
Have you tried using smart switch? It is a PC app by Samsung which will automatically choose the correct firmware for you, flash it and also unroot your phone. It is the easiest way to do it.

TheSproker said:
Have you tried using smart switch? It is a PC app by Samsung which will automatically choose the correct firmware for you, flash it and also unroot your phone. It is the easiest way to do it.
Click to expand...
Click to collapse
The issue I was having was that Smart Switch wasn't recognizing my phone off the bat, and when I went to emergency recovery, it would say my serial number was incorrect so it wasn't useable for me.

"Only officially released binaries..." error and I can't flash the stock firmware

"Only officially released binaries..." error and I can't flash the stock firmware
I sort of bricked my phone (i think this is considered bricked anyway) after rooting it and getting the "only official binaries allowed" message. I tried to flash the stock firmware via odin, and it was stuck at "NAND write start" with the box reading "set partition". The only options ticked in odin were f.reset time and auto reboot. I'm really scared I've messed it up permanently somehow, please help if you can.
Model: SM-G950F, Exynos (I don;t know what other info to include or how to find that info without my phone on, if anything is needed, please tell me and Ill try and find it)
LOG:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1100)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin.lz4
<ID:0/005> NAND Write Start!!
UPDATE: tried again, three lines were added
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
I also tried it on another machine, got the same thing including those three lines but in a different order:
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> sboot.bin
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007>Complete(write) operation failed.
<OSM> All threads complete. (succeed 0 / failed 1)
<ID:0/007> Removed!!
In addition, I'm not certain if this was there before, but a line in my download mode says:
"SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 3, BINARY: 2"
I saw a similar line on one of the threads, so I realise that may be important
Thanks for any help in advance
--End Update
Exact steps taken to root the phone:
I decided to root my phone via magisk. I installed TWRP via odin, didn't quite immediately boot into recovery, so I flashed it once more, and this time managed to. I kept it read only, and then formatted the phone via TWRP, rebooted into recovery again, flashed the no-verity file (no-verity-opt-encrypt-6.0). I did not flash that RMM file I've seen after looking for solutions, and then rebooted my phone. It worked fine, magisk was installed, I went through the initial setup, restored my stuff from a backup etc. and then, I tried to install the xposed module in the magisk repo. Rebooted, and got the whole "Only official released binaries are allowed to be flashed" message and couldn't boot up past the initial "samsung galaxy 8 - powered by android" screen, nor into my recovery. So, I went looking for solutions, and did something dumb. I tried to flash this file here (Nougat G950FXXU1AQL5 bootloader) before restoring the original firmware. I'm not sure what problems that might have caused, and the flash failed anyhow, but I don't know still. Moving on,

twinsniper said:
I sort of bricked my phone (i think this is considered bricked anyway) after rooting it and getting the "only official binaries allowed" message. I tried to flash the stock firmware via odin, and it was stuck at "NAND write start" with the box reading "set partition". The only options ticked in odin were f.reset time and auto reboot. I'm really scared I've messed it up permanently somehow, please help if you can.
Model: SM-G950F, Exynos (I don;t know what other info to include or how to find that info without my phone on, if anything is needed, please tell me and Ill try and find it)
LOG:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1100)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin.lz4
<ID:0/005> NAND Write Start!!
UPDATE: tried again, three lines were added
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
I also tried it on another machine, got the same thing including those three lines but in a different order:
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> sboot.bin
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007>Complete(write) operation failed.
<OSM> All threads complete. (succeed 0 / failed 1)
<ID:0/007> Removed!!
In addition, I'm not certain if this was there before, but a line in my download mode says:
"SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 3, BINARY: 2"
I saw a similar line on one of the threads, so I realise that may be important
Thanks for any help in advance
--End Update
Exact steps taken to root the phone:
I decided to root my phone via magisk. I installed TWRP via odin, didn't quite immediately boot into recovery, so I flashed it once more, and this time managed to. I kept it read only, and then formatted the phone via TWRP, rebooted into recovery again, flashed the no-verity file (no-verity-opt-encrypt-6.0). I did not flash that RMM file I've seen after looking for solutions, and then rebooted my phone. It worked fine, magisk was installed, I went through the initial setup, restored my stuff from a backup etc. and then, I tried to install the xposed module in the magisk repo. Rebooted, and got the whole "Only official released binaries are allowed to be flashed" message and couldn't boot up past the initial "samsung galaxy 8 - powered by android" screen, nor into my recovery. So, I went looking for solutions, and did something dumb. I tried to flash this file here (Nougat G950FXXU1AQL5 bootloader) before restoring the original firmware. I'm not sure what problems that might have caused, and the flash failed anyhow, but I don't know still. Moving on,
Click to expand...
Click to collapse
For starters use latest Odin 3.13.1 it supports the lz4 compression.
Device 3 binary 2 error means you are trying to flash early version firmware use the same or later version firmware

Oh wow, okay, I didn't realize I was flashing an earlier firmware, it's one I flashed earlier in the year and still the latest on updato for vodafone, but yeah there was an update to that. Thank you, so, so much. I was terrified and up till like 5 am last night trying to fix it, sick to my stomach etc. thinking I'd permanently messed things up.
For anyone reading this in the future, as of right now, the latest Vodafone SM-G950F Firmware (Australia) on updato is not the latest firmware (from what I understand you don't want to flash anything with XXU2. you want XXU3), but if you go to sammobile or use samfirm (helluva lot faster download speed for the record) you can get the latest firmware.
Anyway, thanks a lot spawnlives, really appreciate the help, and its good to know for the future If i ever do anything like this again what that message means.

twinsniper said:
Oh wow, okay, I didn't realize I was flashing an earlier firmware, it's one I flashed earlier in the year and still the latest on updato for vodafone, but yeah there was an update to that. Thank you, so, so much. I was terrified and up till like 5 am last night trying to fix it, sick to my stomach etc. thinking I'd permanently messed things up.
For anyone reading this in the future, as of right now, the latest Vodafone SM-G950F Firmware (Australia) on updato is not the latest firmware (from what I understand you don't want to flash anything with XXU2. you want XXU3), but if you go to sammobile or use samfirm (helluva lot faster download speed for the record) you can get the latest firmware.
Anyway, thanks a lot spawnlives, really appreciate the help, and its good to know for the future If i ever do anything like this again what that message means.
Click to expand...
Click to collapse
Glad you got sorted out.
I am aware of the new firmware with ver3 bootloader it has been out for a while. Samfirm is probably the best for latest versions. I am using XSA (Australian unbranded) firmware i try not to use branded firmware like Telstra,Optus or Vodafone.

Samsung Galaxy S8 no OS while current binary is custom (0xe) Odin fails flashing roms

After rooting my Samsung Galaxy S8 I accidentally wiped all data including the OS. I'm completely new to this and wish for some detailed help from a professional.
Odin keeps giving a fail at param.bin using different ROMs. I've heard it might be the bootloader version that's incompatible but I'm not sure what to do and which bootloader version I have. I'm using the same firmware I've downloaded from sammobile before for my model number SM-G950F and even an extra one with Android pie on it, the same android version before this happened, but to no avail. Here is the log from Odin. Appreciate all help since I wiped the data after being stuck in the bootloader with a Samsung logo on it (alone) but after wiping everything it's the screen before it with the samsung logo AND "powered by android".
It may be relevant to note that I'd rather use Odin than an SD-card.
Edit: I checked the download screen on my s8 and found an error saying that SW REV. Failed Bootloader device 6 binary 4. I checked next to SWREV: B:6
So it apparently is a binary incompatibility for bootloader. Now my question is where can I find the suitable binary? All I see while downloading firmware is the model version and the date but not the binary.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1401)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 5716 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> param.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks in advance!

It worked!
So as a beginner's guide you need to check the error code given after failing in Odin in the download screen in the phone itself at the end of these codes.
My error code was as mentioned in the edit that I was trying to install a firmware with a binary version 4 whereas my device's version is 6. To find the correct firmware version you need to look for the part in the PDA code where it says U6 or U5 or U4 (binary version 6, 5 or 4 as examples respectively).
PDA code is for example: G950FXXU6DSK9 as in my case. This is different from the CSC code, you can find both in the sammobile website. You just have to compare your device's binary version found next to SWREV and identified with a B up among the codes in the download screen of your phone (after holding volume down power and bixby at the same time).
That's it. Special thanks to ZeroXO who contributed to the resolution of the issue and was very helpful ^^

Kindly share your experiences after you rooted your device. What are the pros n cons?