Database Info

I cant unroot my Galaxy S7 Verizon (SM-G930V)

I rooted my phone with odin and i decided later that i wanted to unroot it. So i went into SuperSu and went to settings and tried the full unroot thing. My phone restarted and everything and i went to the root checker and it said i was unrooted. Then, i was still getting the Security notification that always pops up saying " Security Notice: Unauthorized actions have been detected ". So i went to that and i decided to try to factory reset my phone from that screen. So I cleared all the data on the phone and everything and it came back completely reset. The only problem was that I am still getting the notification. I have no idea what to do to get rid of it and i want to completely unroot my phone. I have looked all over the internet for the Galaxy S7 Verizon stock firmware. I can't find the firmware anywhere and its really bugging me having that notification there still. If there is no unroot available for the S7 right now, i was wondering if there is someway i can hide that notification for now to give me peace of mind. Thank you so much in advance.

Parteeajp said:
I rooted my phone with odin and i decided later that i wanted to unroot it. So i went into SuperSu and went to settings and tried the full unroot thing. My phone restarted and everything and i went to the root checker and it said i was unrooted. Then, i was still getting the Security notification that always pops up saying " Security Notice: Unauthorized actions have been detected ". So i went to that and i decided to try to factory reset my phone from that screen. So I cleared all the data on the phone and everything and it came back completely reset. The only problem was that I am still getting the notification. I have no idea what to do to get rid of it and i want to completely unroot my phone. I have looked all over the internet for the Galaxy S7 Verizon stock firmware. I can't find the firmware anywhere and its really bugging me having that notification there still. If there is no unroot available for the S7 right now, i was wondering if there is someway i can hide that notification for now to give me peace of mind. Thank you so much in advance.
Click to expand...
Click to collapse
Hi mate
Just flash a stock rom with odin on top of it
http://www.sammobile.com/firmwares/database/SM-G930V/
back up everything important before you do it ..just in case

Hey, i have a whole new problem now. When i was trying to unroot my phone, i accidentally installed the wrong firmware on to the phone. I turned my verizon phone into a t-mobile phone.
Im not exactly sure what flashing is, but is it where you put the BL, AP, CP, and CSC things into Odin and start it?
I might have already done that because i found the verizon firmware somewhere and when i try to do it in odin. It gives me an error and says fail.

Parteeajp said:
Hey, i have a whole new problem now. When i was trying to unroot my phone, i accidentally installed the wrong firmware on to the phone. I turned my verizon phone into a t-mobile phone.
Im not exactly sure what flashing is, but is it where you put the BL, AP, CP, and CSC things into Odin and start it?
I might have already done that because i found the verizon firmware somewhere and when i try to do it in odin. It gives me an error and says fail.
Click to expand...
Click to collapse
Hi
Yes you need to flash it with Odin
did you downloaded from sammobile?
if not try i from there , follow their instructions :
Extract (unzip) the firmware file
Download Odin v3.11.1
Extract Odin ZIP file
Open Odin v3.11.1
Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the firmware file to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back and wait few minutes
Usually sammobile has only one tar file ( unzip it just once) , back up you photos and files before just in case
Check this thread is not for your phone but the basics apply to all samsung phones
http://forum.xda-developers.com/galaxy-s7/how-to/official-stock-firmware-update-odin-t3369431

Parteeajp said:
Hey, i have a whole new problem now. When i was trying to unroot my phone, i accidentally installed the wrong firmware on to the phone. I turned my verizon phone into a t-mobile phone.
Im not exactly sure what flashing is, but is it where you put the BL, AP, CP, and CSC things into Odin and start it?
I might have already done that because i found the verizon firmware somewhere and when i try to do it in odin. It gives me an error and says fail.
Click to expand...
Click to collapse
Can you post a pic of the back of the phone showing the model number as SM-G930V and FCC ID. Then take a pic of the bootloader screen and show what what model number it has, if flash successfully it should be showing as SM-G930T. If proven true then it may seem that as the S7 is a Universal Hardware phone (QCOMM that is).

Please Help
I'm not sure if this is the right place to post, but I have a similar problem.
I tried flashing SM-G930U to my SM-G930V.
Odin failed, and I rebooted my phone. It will only reboot to download mode or recovery mode.
- I have tried redownloading files to check for corruption.
- Using different versions of Odin.
- Flashing to the stock files, which also fails.
- Using stock USB cable.
- Using different ports.
It doesn't seem like Odin will flash anything

Benaiah1287: I am in the exact same predicament...
I got the G930U firmware from sammobile and have tried flashing it with Odin versions 3.10, 3.11, and 3.12, all with failure.
My next steps are to try the stock G930V firmware or to see if the Samsung Software Upgrade Assistant can repair.

Benaiah1287 said:
I'm not sure if this is the right place to post, but I have a similar problem.
I tried flashing SM-G930U to my SM-G930V.
Odin failed, and I rebooted my phone. It will only reboot to download mode or recovery mode.
- I have tried redownloading files to check for corruption.
- Using different versions of Odin.
- Flashing to the stock files, which also fails.
- Using stock USB cable.
- Using different ports.
It doesn't seem like Odin will flash anything
Click to expand...
Click to collapse
nitropowrd said:
Benaiah1287: I am in the exact same predicament...
I got the G930U firmware from sammobile and have tried flashing it with Odin versions 3.10, 3.11, and 3.12, all with failure.
My next steps are to try the stock G930V firmware or to see if the Samsung Software Upgrade Assistant can repair.
Click to expand...
Click to collapse
You need to use the prince comsey's modified odin that bypasses SHA verification.

Saga's End
aromerblz said:
You need to use the prince comsey's modified odin that bypasses SHA verification.
Click to expand...
Click to collapse
I hunted down the Comsy version of Odin 3.12 Odin3_v3.12_PrinceComsy.zip (MD5 hash 136E707B39C2E4CDC47820C68065CD5C)
but I still received a failure with the following output:
<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)
and on the phone (Download-mode) display:
DVIF!!
S REV CHECK FAIL : [aboot]Fused 4 > Binary 2
[1] eMMC write fail : aboot
I also tried it without copying the BL file only, as I have also read that this could work, but no dice.
I then tried the stock G930V firmware (for my G930V) with the following result:
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> emmc_appsboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
on reboot it gave me the 'Software Update Failed' screen
I then used the Samsung Repair Utility and after half an hour it was able to restore the original OS. It did give me a new warning about it not being able to make calls until it was set up with a Verizon account, but after reboot it still just has the message "SIM card is not from Verizon Wireless," so I'm assuming it is still in its original "factory unlocked" state.
So, about 8 hours of tinkering later, I cannot recommend trying to flash the SM-G930V at all.
My sole purpose for all this was in trying to get compatibility with Republic Wireless (which claims it supports the unlocked S7 but really means the North American 930U only).

nitropowrd said:
I hunted down the Comsy version of Odin 3.12 Odin3_v3.12_PrinceComsy.zip (MD5 hash 136E707B39C2E4CDC47820C68065CD5C)
but I still received a failure with the following output:
<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)
and on the phone (Download-mode) display:
DVIF!!
S REV CHECK FAIL : [aboot]Fused 4 > Binary 2
[1] eMMC write fail : aboot
I also tried it without copying the BL file only, as I have also read that this could work, but no dice.
I then tried the stock G930V firmware (for my G930V) with the following result:
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> emmc_appsboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
on reboot it gave me the 'Software Update Failed' screen
I then used the Samsung Repair Utility and after half an hour it was able to restore the original OS. It did give me a new warning about it not being able to make calls until it was set up with a Verizon account, but after reboot it still just has the message "SIM card is not from Verizon Wireless," so I'm assuming it is still in its original "factory unlocked" state.
So, about 8 hours of tinkering later, I cannot recommend trying to flash the SM-G930V at all.
My sole purpose for all this was in trying to get compatibility with Republic Wireless (which claims it supports the unlocked S7 but really means the North American 930U only).
Click to expand...
Click to collapse
You are trying to flash a downgraded bootloader version/firmware. Your phone has bootloader v4 and you are trying to flash a v2 firmware. Flashing a v4 or above will work.

aromerblz said:
You are trying to flash a downgraded bootloader version/firmware. Your phone has bootloader v4 and you are trying to flash a v2 firmware. Flashing a v4 or above will work.
Click to expand...
Click to collapse
For anyone keeping up, the source of the 930U with bootloader version 4 is here
...which I found through Fix For Those Who Tried Flashing The g930u Firmware
Too bad I just ordered a G930U instead thinking there was no current release
It appears it was also uploaded to sammobile just yesterday...but I am only assuming because the naming convention does not agree to the guide I found here, and I don't understand the 'PL#' part

nitropowrd said:
For anyone keeping up, the source of the 930U with bootloader version 4 is here
...which I found through Fix For Those Who Tried Flashing The g930u Firmware
Too bad I just ordered a G930U instead thinking there was no current release
It appears it was also uploaded to sammobile just yesterday...but I am only assuming because the naming convention does not agree to the guide I found here, and I don't understand the 'PL#' part
Click to expand...
Click to collapse
thanks a lot. I had 2 S7s. One I was able to flash with G930UUEU2APEH, but the other one couldn't...but I could with the one you posted ( SM-G930U_1_20160921124641_vvcrzx3ej5_fac)

Help please <ID:0/006> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> skip file list for home binary
<ID:0/006> persist.img.ext4
<ID:0/006> Home Binary Download
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> emmc_appsboot.mbn
<ID:0/006> lksecapp.mbn
<ID:0/006> xbl.elf
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

aromerblz said:
You are trying to flash a downgraded bootloader version/firmware. Your phone has bootloader v4 and you are trying to flash a v2 firmware. Flashing a v4 or above will work.
Click to expand...
Click to collapse
I am having the same problem. How do I know the version before trying and failing until I get one that works?

Couldn't the boot loader 'version' be changed/hacked within the (down graded) boot loader so the version check would pass?

Problems after rooting

Hello, I just bought S7 (second-hand) last week and wondering to root it out.
My question is, is there any laggy or issue or something that feels 'downgraded' after the root? Because I've seen many people complain about after their phones being rooted.
Thanks in advance!

isssaputra said:
Hello, I just bought S7 (second-hand) last week and wondering to root it out.
My question is, is there any laggy or issue or something that feels 'downgraded' after the root? Because I've seen many people complain about after their phones being rooted.
Thanks in advance!
Click to expand...
Click to collapse
If you trip Knox you won't be able to use Secure folder, Samsung Pay or Samsung Health and that's it.
You won't get any other problems.

Hi!
Yesterday I rooted my S7 (SM-G930F) with CF-Auto Root (from desktop.firmware.mobi)
Unfortunately, I didn't notice that the Kernel was 7.0, while my S7 was already on 8.0.
Now I have a lot of apps (including camera, youtube, lightning launcher, opera, ...) that either crash directly after starting or freeze shortly after they are opened.
Do you know if/how it is possible to get a working system again?
Thank you in advance (and forgive my bad english),
Andi

If you download 8.0 firmware files (either use samfirmtool, or go to sammobile.com or updato.com) and flash using Odin, use AP, BL, CP and HOME_CSC instead of normal CSC (HOME_CSC keeps data, normal CSC wipes data), it should set your kernel and everything back to 8.0 without causing any data loss.
Flash guide here https://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin
However I'm pretty sure doing this will reset your root, your best bet is to flash TWRP and root using Magisk as its the more modern and updated root method.

Hi @Beanvee7,
thanks for your info!
In the meantime, I have installed TWRP, and downloaded the firmware from sammobile, but failed with magisk (since it is one of the apps that keep on crashing right after startup).
So, I'll have to install it the old fashioned way with odin tomorrow.
But I have one more question left: Is there an advantage of using CSC vs. HOME_CSC? Since I have backups of all my data, and rooting wiped data anyways (the system was encrypted), a wipe does not inflict any (addiditional) damage.
Thanks,
Andi

CSC is probably preferred because it means a clean wipe, so you won't be carrying across any potentially broken apps/system files.
If you have backups then I'd recommend CSC.

Hi!
I am still stuck: No matter what type of installation I choose, it fails:
Odin reports success, but doesn't install the new firmware (neither 7.0 nor 8.0, from updato or sammobile).
<ID:0/006> modem_debug.bin
<ID:0/006> cache.img.lz4
<ID:0/006> hidden.img.lz4
<ID:0/006> Home Binary Download
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> modem.bin
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes
<ID:0/006> Receive Response from boot-loader
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Added!!
<ID:0/004> Removed!!
Click to expand...
Click to collapse
The "Now Writing.. Please wait about 2 minutes"-part only takes one second or so.
Installing via TWRP reports "Invalid zip file format".
ROM Toolbox Pro also reports "Invalid ZIP file"
Magisk still crashes upon startup.
Do you have any ideas left?

SM-G892A to G892USQU2BRE3 repartition failed error

I have a sim unlocked AT&T Galaxy S8 Active (SM-G892A) that I've had number-ported over to T-Mobile for a month or so now.
as it has firmware G892AUCS2BRD4 on it now I wasn't able to update it to T-Mobile's firmware as they WERE on Bootloader V1.
Well today on TMO web site I saw they now have G892USQU2BRE3 out and I was trying to use a modded Odin 3.13.1 to update it.
I previously used this Odin to flash two S7's from AT&T firmware to T-Mobile with no issues so I thought Odin was okay
When I attempted to do this on my S8 Active I get the following:
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 4306 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> FAIL!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I re-downloaded the firmware using SAM-FIRM to ensure it was Legit and got same error.
What am I missing here?
I think I even tried to select Re-partition in odin once (tired and went thru a lot of retries tonight).
Do I need a Super-Special Odin for this newer firmware?
Is it AT&T's darned bootloader causing issues?
Thans in Advance
Dave in Tampa

eplerd said:
I have a sim unlocked AT&T Galaxy S8 Active (SM-G892A) that I've had number-ported over to T-Mobile for a month or so now.
as it has firmware G892AUCS2BRD4 on it now I wasn't able to update it to T-Mobile's firmware as they WERE on Bootloader V1.
Well today on TMO web site I saw they now have G892USQU2BRE3 out and I was trying to use a modded Odin 3.13.1 to update it.
I previously used this Odin to flash two S7's from AT&T firmware to T-Mobile with no issues so I thought Odin was okay
When I attempted to do this on my S8 Active I get the following:
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 4306 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> FAIL!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I re-downloaded the firmware using SAM-FIRM to ensure it was Legit and got same error.
What am I missing here?
I think I even tried to select Re-partition in odin once (tired and went thru a lot of retries tonight).
Do I need a Super-Special Odin for this newer firmware?
Is it AT&T's darned bootloader causing issues?
Thans in Advance
Dave in Tampa
Click to expand...
Click to collapse
Im getting the same error trying to load a custom rom from PartyCyborgROM over G892USQU2BRE3. I had to revert back to the exact stock rom. If you find anything let me know.

pwoolston said:
Im getting the same error trying to load a custom rom from PartyCyborgROM over G892USQU2BRE3. I had to revert back to the exact stock rom. If you find anything let me know.
Click to expand...
Click to collapse
RATS - saw the reply and got excited thinking someone had a fix :crying:
Still Hopeful...

CF-Root
eplerd said:
RATS - saw the reply and got excited thinking someone had a fix :crying:
Still Hopeful...
Click to expand...
Click to collapse
I am going to try CF-Auto-Root for Nougat to see if it works on Oreo Cookie. It's worth a try I guess.

pwoolston said:
I am going to try CF-Auto-Root for Nougat to see if it works on Oreo Cookie. It's worth a try I guess.
Click to expand...
Click to collapse
Yeah - I don't wanna root my phone - no need, just want AT&T Bloatware that's useless now gone, and T-Mobile apps on my cell - like I did for friends S7's

Has ANYBODY done this?
I really NEED to get this done as I'm missing phone calls and can't afford a new cell now.
Sure wish I had bought a cheaper S7 as converting it to a T-mobile model was easy on my friends 2 phones.
I'm now wondering IS the S8 active the same across cell vendors (T-mobile, ATT, Sprint, etc) like the S7 is??

S8+ - sm-g955 - SW Rev. CHECK FAIL (BOOTLOADER) DEVICE: 4 BINARY: 3

Hello, please I need help on this
Model: SM-G955 - MX Telcel
Update: I cannot reproduce the issue of the Kernel rev. I tried in another computer and the result continue SW Rev. CHECK FAIL (BOOTLOADER) DEVICE: 4 BINARY: 3
Having this issue:
Odin 3.13
<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/015> Odin engine v(ID:3.1301)..
<ID:0/015> File analysis..
<ID:0/015> Total Binary size: 5529 M
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> NAND Write Start!!
<ID:0/015> SingleDownload.
<ID:0/015> boot.img
<ID:0/015> FAIL!
<ID:0/015>
<ID:0/015> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Steps to Reporduce
I was following this thread [GUIDE] How To Install TWRP & Root Galaxy S8 After Oreo Update breaking the device, and get a loop device with the legend of the OEM. After that, I follow this thread [ROM] [8.0] [OFFICIAL] [CRGB] [ODIN FLASHABLE] For Galaxy S8+ [G955F/FD] [08.09.2018]. Everything was ok, I received an OTA didn't remember the version and continue configuring until I install the Magisk.apk and restart the device, the device stays on OEM boot loop again, trying to reflash S8+ Official Oreo CRGB Firmware 07.09.2018 this version, comes the error SW rev. check to fail device 4 binary 3 related that I am trying to use an older version.
So I find 2 newer versions: SM-G955F_1_20180904043214_2afttpa4az_fac // SM-G955F_1_20180904010814_39o648ohci_fac. Try and now the error is the Kernel rev.
Hope you can help me with some guideline here.
Thank you!

hackerjj22 said:
Hello, please I need help on this
Model: SM-G955 - MX Telcel
Update: I cannot reproduce the issue of the Kernel rev. I tried in another computer and the result continue SW Rev. CHECK FAIL (BOOTLOADER) DEVICE: 4 BINARY: 3
Having this issue:
Odin 3.13
<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/015> Odin engine v(ID:3.1301)..
<ID:0/015> File analysis..
<ID:0/015> Total Binary size: 5529 M
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> NAND Write Start!!
<ID:0/015> SingleDownload.
<ID:0/015> boot.img
<ID:0/015> FAIL!
<ID:0/015>
<ID:0/015> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Steps to Reporduce
I was following this thread [GUIDE] How To Install TWRP & Root Galaxy S8 After Oreo Update breaking the device, and get a loop device with the legend of the OEM. After that, I follow this thread [ROM] [8.0] [OFFICIAL] [CRGB] [ODIN FLASHABLE] For Galaxy S8+ [G955F/FD] [08.09.2018]. Everything was ok, I received an OTA didn't remember the version and continue configuring until I install the Magisk.apk and restart the device, the device stays on OEM boot loop again, trying to reflash S8+ Official Oreo CRGB Firmware 07.09.2018 this version, comes the error SW rev. check to fail device 4 binary 3 related that I am trying to use an older version.
So I find 2 newer versions: SM-G955F_1_20180904043214_2afttpa4az_fac // SM-G955F_1_20180904010814_39o648ohci_fac. Try and now the error is the Kernel rev.
Hope you can help me with some guideline here.
Thank you!
Click to expand...
Click to collapse
As you have already guessed you are trying to flash older firmware than what is on your phone. Device 4 = current bootloader version on phone.Binary 3 = bootloader your trying to flash.
Have a look through this and use samfirm to download latest firmware then flash with odin. Or download latest from sammobile and flash.
When looking at firmware names the 5th number from the right is the bootloader version number.You will need version 4 bootloader firmware.
https://www.xda-developers.com/download-stock-odin-firmware-samfirm/

spawnlives said:
As you have already guessed you are trying to flash older firmware than what is on your phone. Device 4 = current bootloader version on phone.Binary 3 = bootloader your trying to flash.
Have a look through this and use samfirm to download latest firmware then flash with odin. Or download latest from sammobile and flash.
When looking at firmware names the 5th number from the right is the bootloader version number.You will need version 4 bootloader firmware.
https://www.xda-developers.com/download-stock-odin-firmware-samfirm/
Click to expand...
Click to collapse
Thank you Spawnlives, you are right, I reflash this one: BL_G955FXXU4CRI5_CL14315050_QB19732162_REV00_user_low_ship.tar from Device 4, and everything is ok.

thanks so much my brother your tips working
:angel:
spawnlives said:
As you have already guessed you are trying to flash older firmware than what is on your phone. Device 4 = current bootloader version on phone.Binary 3 = bootloader your trying to flash.
Have a look through this and use samfirm to download latest firmware then flash with odin. Or download latest from sammobile and flash.
When looking at firmware names the 5th number from the right is the bootloader version number.You will need version 4 bootloader firmware.
https://www.xda-developers.com/download-stock-odin-firmware-samfirm/
Click to expand...
Click to collapse

Hi, but what if Lineage OS is Android 10 (currently running) and Samsung / Sammobile doesnt offer a ROM with corresponding bootloader version? I want to go back to stock but it doens't work, right? Thanks!

spawnlives said:
As you have already guessed you are trying to flash older firmware than what is on your phone. Device 4 = current bootloader version on phone.Binary 3 = bootloader your trying to flash.
Have a look through this and use samfirm to download latest firmware then flash with odin. Or download latest from sammobile and flash.
When looking at firmware names the 5th number from the right is the bootloader version number.You will need version 4 bootloader firmware.
https://www.xda-developers.com/download-stock-odin-firmware-samfirm/
Click to expand...
Click to collapse
Anyway to flash older firmware once the device has been updated?
Used to be absolutely fine on older devices, could rollback and flash any firmware you wanted.

ben.marks said:
Anyway to flash older firmware once the device has been updated?
Used to be absolutely fine on older devices, could rollback and flash any firmware you wanted.
Click to expand...
Click to collapse
No anti rollback prevents this thus this error

spawnlives said:
As you have already guessed you are trying to flash older firmware than what is on your phone. Device 4 = current bootloader version on phone.Binary 3 = bootloader your trying to flash.
Have a look through this and use samfirm to download latest firmware then flash with odin. Or download latest from sammobile and flash.
When looking at firmware names the 5th number from the right is the bootloader version number.You will need version 4 bootloader firmware.
https://www.xda-developers.com/download-stock-odin-firmware-samfirm/
Click to expand...
Click to collapse
you seem to know things brother how about a little help
so my running bootloader is G9550FXXSBDUA3 what binaries are used in case i want to load a combination file
p.s: i cant boot the device only runs download mode and bootmenu

Nima_shah said:
you seem to know things brother how about a little help
so my running bootloader is G9550FXXSBDUA3 what binaries are used in case i want to load a combination file
p.s: i cant boot the device only runs download mode and bootmenu
Click to expand...
Click to collapse
Bootloader version numbers,
A - bootloader version 10
B - bootloader version 11
C - bootloader version 12
And so on
You can check bootloader version in download mode.

Nima_shah said:
you seem to know things brother how about a little help
so my running bootloader is G9550FXXSBDUA3 what binaries are used in case i want to load a combination file
p.s: i cant boot the device only runs download mode and bootmenu
Click to expand...
Click to collapse
your best bet is to go to sammobile.com/firmwares and download the latest FW for your device and flash it with Odin. I bet itll boot right up barring any hardware issues

only official released binaries are allowed to be flashed samsung note 8

when( only official released binaries are allowed to be flashed ) come out ,i try to downloading and install the SM-950F Firmware,but the error always come out,the phone come out SW REV.CHECK FAIL(BOOTLOADR) DEVICE:11 ,BINARY: 1
and this is computer run out
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 6042 M
<ID:0/006> SetupConnection..
<ID:0/006> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
any solution ?
by the way all lock is off

HansomeC said:
when( only official released binaries are allowed to be flashed ) come out ,i try to downloading and install the SM-950F Firmware,but the error always come out,the phone come out SW REV.CHECK FAIL(BOOTLOADR) DEVICE:11 ,BINARY: 1
and this is computer run out
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 6042 M
<ID:0/006> SetupConnection..
<ID:0/006> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
any solution ?
by the way all lock is off
Click to expand...
Click to collapse
You are trying to flash a firmware that has an older binary version than what is already on the device. You can't do that, you have to flash a firmware that has the exact same binary as what is already on the device or you need to flash a firmware that has a newer binary.
In other words, you can not downgrade, you can only flash what you already have installed on the device or you can only flash an upgraded firmware, you can not go backwards.
If you are trying to downgrade your device in order to root the device, that is not going to work.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
You are trying to flash a firmware that has an older binary version than what is already on the device. You can't do that, you have to flash a firmware that has the exact same binary as what is already on the device or you need to flash a firmware that has a newer binary.
In other words, you can not downgrade, you can only flash what you already have installed on the device or you can only flash an upgraded firmware, you can not go backwards.
If you are trying to downgrade your device in order to root the device, that is not going to work.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
ok understand,thank you solve my problem

HansomeC said:
ok understand,thank you solve my problem
Click to expand...
Click to collapse
Are you saying that you solved the problem or are you saying that you understand but still need help solving the problem?
Find the newest firmware available for your device, one that has a binary that is higher than what was on the device when the problem started.
Sent from my SM-S767VL using Tapatalk