I got a new P8 lite 2017 (PRA-LX1) and the firmware was a Vodacom South Africa, not sure about exact version but it's a C02. I installed Firmware Finder and tried to download a C432 firmware, open Europe I think. The download started and then got stuck with "unstable network", I went to bed.
Next day the battery was flat and the phone wouldn't boot. Looks like the firmware download somehow finished while I was sleeping and then the phone got suck in a boot loop and drained the battery.
Booting with volume up + power doesn't work. I see the Huawei logo, then Vodacom logo, then nothing and it reboots into eRecovery.
In eRecovery it connects to my WiFi and tries to download but ends with "Getting package info failed"
fastboot works but the phone is still locked so I get "command not allowed" when I try to flash any partition.
Recovery from sd card (update.app in dload folder) ends with "Software install failed". I tried with PRA-LX1C02B150 and PRA-LX1C02B151 which should be a Vodacom firmware, my desktop Firmware Finder can't find a C432 firmware.
Can I recover from this?
I bought a Note 9 (SM-N960F) second-hand and it turns out it was rooted in the past. I wanted to update the buildprop so that S Health would work so re-rooted the phone, made the necessary changes, which worked fine and then started removing root, TWRP, etc.
I unticked OEM unlock, the phone restarted and now everytime I try to start my phone I get "Custom Binary Blocked by OEM lock" in red and that's it.
I can't access Samsung recovery (Bixby + Vol Down + Power) to re-flash a standard ROM and I cannnot boot into TWRP (Bixby + Vol Up + Power).
Have I bricked it? Is it now a £500 paperweight? Any ideas on a solution?
Your system partition is no longer intact. Of course you should keep the OEM lock off.
Have you tried entering download mode by holding vol down + bixby while plugging your cable in, while the phone is powered off?
Thank you! That worked
If you had searched you would have found that you can get S Health to work by downloading and installing an earlier version set it up, then update to the latest version. I had the same problem with my S8+. Just can't remember what earlier version to download but Google is your friend there.
Was no need to re root and edit build prop.
Cheers.
You saved me... Thank you sir.
Hello, I am also facing the same issue in Samsung S9 which I have bought from the Netherlands. I have bought a brand new Samsung s9 phone then I flushed Custom ROM and then I Off the OEM Unlocking and now when I restarted it, it's showing "Custom Binary Blocked by OEM lock" in red. I tried to install the stock ROM (version number PDA G960FXXU2BRJ8 and CSC G960FOXM2BRJ4) via Odin, but it's showing error while I install this via Odin "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 6, BINARY:2"
If I download Samsung firmware for the Galaxy S9 SM-G960F for the Netherlands, it's showing many carriers options like: Netherlands (PHN), Netherlands (Vodafone) VDF, Netherlands (Ben NL) DNL, Netherlands (T-Mobile) TNL. Which version I have to select from these before I downloaded Netherlands (PHN). I bought this S9 phone without any telecom contract (SIM Free).
Please help me out from this issue. Am I installing the right version of the stock ROM?
akshay9090 said:
Hello, I am also facing the same issue in Samsung S9 which I have bought from the Netherlands. I have bought a brand new Samsung s9 phone then I flushed Custom ROM and then I Off the OEM Unlocking and now when I restarted it, it's showing "Custom Binary Blocked by OEM lock" in red. I tried to install the stock ROM (version number PDA G960FXXU2BRJ8 and CSC G960FOXM2BRJ4) via Odin, but it's showing error while I install this via Odin "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 6, BINARY:2"
If I download Samsung firmware for the Galaxy S9 SM-G960F for the Netherlands, it's showing many carriers options like: Netherlands (PHN), Netherlands (Vodafone) VDF, Netherlands (Ben NL) DNL, Netherlands (T-Mobile) TNL. Which version I have to select from these before I downloaded Netherlands (PHN). I bought this S9 phone without any telecom contract (SIM Free).
Please help me out from this issue. Am I installing the right version of the stock ROM?
Click to expand...
Click to collapse
1- this is note 9 forums
2- you are attempting to flash OLD firmware on a newer based bootloader phone.
3- search and read.
so just don't flash old firmware. download the newest. search are read about bootloader versions so you don't get the SW REV error again and also search on how or where to download the newest firmware or at least one that matches your bootloader revision.
it happen to my note 9 today and not even let to me to boot into download or recovery, please please anyone can help.
my costum binary blocked by oem lock(j610f)
I flashed the BL and CP, but there is still an OEM lock message after the reset
timshields said:
I bought a Note 9 (SM-N960F) second-hand and it turns out it was rooted in the past. I wanted to update the buildprop so that S Health would work so re-rooted the phone, made the necessary changes, which worked fine and then started removing root, TWRP, etc.
I unticked OEM unlock, the phone restarted and now everytime I try to start my phone I get "Custom Binary Blocked by OEM lock" in red and that's it.
I can't access Samsung recovery (Bixby + Vol Down + Power) to re-flash a standard ROM and I cannnot boot into TWRP (Bixby + Vol Up + Power).
Have I bricked it? Is it now a £500 paperweight? Any ideas on a solution?
Click to expand...
Click to collapse
use FRP Hijacker
Here is the solution :
Download Frija , input your phone model and proper CSC region
e.g. = India = INS
( Make sure to uncheck binary nature and CRC check in settings or it will delete the firmware after download )
extract your downloaded firmware and flash it through odin.
i bought a s10(sm-g973f) but i turn on the oem but still giving error of oem lock
Hello All,
Device always flashed with stock DT Germany firmware. A couple of months back I toggled OEM Unlocking (off-on-off) by mistake and next morning device reboots stating "Custom binary blocked by FRP Lock", single red line on top of screen, no other information.
I have tried to flash stock DT Germany firmware several times.Process through ODIN goes fine and completes successfully but phone reboots again in "Custom Binary blocked by FRP Lock".I can only access download mode, no other modes are available (not even recovery)
Below I have attached some screen shots of download mode and ODIN process.
https://drive.google.com/open?id=10aWMWozVCweBe3UTch9PBvvw6fboYjEQ
I have tried several combination files and all have failed.
I hope anyone has faced and sorted this out
Regards
are flashing the same firmware which was on you phone? If not then try the same firmware. Because that is the only reason i think is not resetting the FRP lock.
Munawar Mehmood said:
are flashing the same firmware which was on you phone? If not then try the same firmware. Because that is the only reason i think is not resetting the FRP lock.
Click to expand...
Click to collapse
Hello Munawar,thank you for your reply. I tried to flash same stock firmware which was on phone at the time and it failed with "sw rev check fail(bootloader) device 3 binary 2". I guess this happens because last night I flashed July 2019 stock firmware (ODIN passed it successfully) and bootloader does not allow an older version. I tried with February firmware, March firmware same problem.
What I have noticed is that if I uncheck auto-reboot (ODIN) and flash latest stock AP is passes successfully and on device (download mode) CURRENT BINARY states "Samsung Official" but when I try to reboot it goes back to 'Custom binary blocked by FRP Lock' and CURRENT BINARY switches back to CUSTOM.
besmirgogu said:
Hello Munawar,thank you for your reply. I tried to flash same stock firmware which was on phone at the time and it failed with "sw rev check fail(bootloader) device 3 binary 2". I guess this happens because last night I flashed July 2019 stock firmware (ODIN passed it successfully) and bootloader does not allow an older version. I tried with February firmware, March firmware same problem.
What I have noticed is that if I uncheck auto-reboot (ODIN) and flash latest stock AP is passes successfully and on device (download mode) CURRENT BINARY states "Samsung Official" but when I try to reboot it goes back to 'Custom binary blocked by FRP Lock' and CURRENT BINARY switches back to CUSTOM.
Click to expand...
Click to collapse
your device wasint logged out of google/samsung b4 reset.
dont know where or how you got it but thats what FRP lock is.. also regardless of if you think you flash the "same" firmware as phone was on, i suspect that you did in fact not know which FW it was on. because the message you are getting:
"sw rev check fail(bootloader) device 3 binary 2"
means you are flashing old firmware on a device which has a new bootloader than the one you are trying to flash.
all in all, searching on xda would have provided the information you are seeking.
now flash back stock firmware from July or August 2019.
bober10113 said:
your device wasint logged out of google/samsung b4 reset.
dont know where or how you got it but thats what FRP lock is.. also regardless of if you think you flash the "same" firmware as phone was on, i suspect that you did in fact not know which FW it was on. because the message you are getting:
"sw rev check fail(bootloader) device 3 binary 2"
means you are flashing old firmware on a device which has a new bootloader than the one you are trying to flash.
all in all, searching on xda would have provided the information you are seeking.
now flash back stock firmware from July or August 2019.
Click to expand...
Click to collapse
@bober10113, thank you for your explanation...
I have just tried to flash (again) the following stock firmware (DT Germany-July 2019)
AP_N960FXXS3CSFC_CL16141281_QB24489477_REV00_user_low_ship_meta_OS9.tar
BL_N960FXXS3CSFC_CL16141281_QB24489477_REV00_user_low_ship.tar
CP_N960FXXS3CSG1_CP13173080_CL16141281_QB24586509_REV00_user_low_ship.tar
CSC_OMC_ODX_N960FODX3CSF3_CL16070506_QB24108956_REV00_user_low_ship.tar
I did use Odin3 v3.13.3...
Behaviour is the same:
ODIN completes successfully and it claims PASS in green, device tries to reboot and throws black screen with "Custom binary blocked by FRP Lock"
I will try DT Germany-August 2019 or a SAMMOBILE August version as well but I would expect the same behavior as I have tried during all these months.
I also tried nand erase and Re-partition by extracing PIT file from CSC file above
if anything else comes to mind please let me know...
besmirgogu said:
@bober10113, thank you for your explanation...
I have just tried to flash (again) the following stock firmware (DT Germany-July 2019)
AP_N960FXXS3CSFC_CL16141281_QB24489477_REV00_user_low_ship_meta_OS9.tar
BL_N960FXXS3CSFC_CL16141281_QB24489477_REV00_user_low_ship.tar
CP_N960FXXS3CSG1_CP13173080_CL16141281_QB24586509_REV00_user_low_ship.tar
CSC_OMC_ODX_N960FODX3CSF3_CL16070506_QB24108956_REV00_user_low_ship.tar
I did use Odin3 v3.13.3...
Behaviour is the same:
ODIN completes successfully and it claims PASS in green, device tries to reboot and throws black screen with "Custom binary blocked by FRP Lock"
I will try DT Germany-August 2019 or a SAMMOBILE August version as well but I would expect the same behavior as I have tried during all these months.
I also tried nand erase and Re-partition by extracing PIT file from CSC file above
if anything else comes to mind please let me know...
Click to expand...
Click to collapse
why are your files named . tar?
i think your not even flashing anything. how long does it take to flash?
bober10113 said:
why are your files named . tar?
i think your not even flashing anything. how long does it take to flash?
Click to expand...
Click to collapse
actually files are in ".tar.md5" but I did not include this extension, I am sorry for the confusion.
last flash took around 4minutes
Should they be in another format?
besmirgogu said:
actually files are in ".tar.md5" but I did not include this extension, I am sorry for the confusion.
last flash took around 4minutes
Should they be in another format?
Click to expand...
Click to collapse
nah i was just wondering if they acctualy were real stock unaltered firmware files.
but anyways. that should have fixed it. so i dont know what to tell you. search around i guess
bober10113 said:
nah i was just wondering if they acctualy were real stock unaltered firmware files.
but anyways. that should have fixed it. so i dont know what to tell you. search around i guess
Click to expand...
Click to collapse
ok, thank you for your help...
well start from scratch.
clean your phone port with a tooth brush gently.
remove samsung drivers, then install latest samsung drivers again. and change usb port (version 2.0) and usb cable. because sometimes damage cable cause this issue. run odin as administrator (right click on odin icon and select run as administrator) and then select nand erase and pit file and flash latest stock firmware.
Munawar Mehmood said:
well start from scratch.
clean your phone port with a tooth brush gently.
remove samsung drivers, then install latest samsung drivers again. and change usb port (version 2.0) and usb cable. because sometimes damage cable cause this issue. run odin as administrator (right click on odin icon and select run as administrator) and then select nand erase and pit file and flash latest stock firmware.
Click to expand...
Click to collapse
I tried as per above guidelines. stock firmware flashed:
AP_N960FXXS3CSG5_CL16141281_QB25130720_REV00_user_low_ship_meta_OS9.tar.md5
BL_N960FXXS3CSG5_CL16141281_QB25130720_REV00_user_low_ship.tar.md5
CP_N960FXXS3CSG2_CP13219698_CL16141281_QB24670232_REV00_user_low_ship.tar.md5
CSC_OMC_OXM_N960FOXM3CSG3_CL16141281_QB24861261_REV00_user_low_ship.tar.md5
ODIN passed it successfully. Device in download mode says CURRENT BINARY: Custom and of course "Custom binary blocked by FRP lock"
besmirgogu said:
I tried as per above guidelines. stock firmware flashed:
AP_N960FXXS3CSG5_CL16141281_QB25130720_REV00_user_low_ship_meta_OS9.tar.md5
BL_N960FXXS3CSG5_CL16141281_QB25130720_REV00_user_low_ship.tar.md5
CP_N960FXXS3CSG2_CP13219698_CL16141281_QB24670232_REV00_user_low_ship.tar.md5
CSC_OMC_OXM_N960FOXM3CSG3_CL16141281_QB24861261_REV00_user_low_ship.tar.md5
ODIN passed it successfully. Device in download mode says CURRENT BINARY: Custom and of course "Custom binary blocked by FRP lock"
Click to expand...
Click to collapse
you are doing something wrong. as stock firmware is the only option to remove custom binary error. try someone else PC and data cable.
Munawar Mehmood said:
you are doing something wrong. as stock firmware is the only option to remove custom binary error. try someone else PC and data cable.
Click to expand...
Click to collapse
I am trying to understand which of the steps I am doing wrong. I managed to successfully flash a Galaxy Note 8 today so I know that laptop, cable and steps followed are fine.
What seems strange to me is that on this Galaxy Note 9 ODIN completes successfully in 2 min and 14 seconds but every time phone states CURRENT BINARY: Custom making me think that device is not being flashed at all. Any ideas how to confirm this?
Did you flash anything onto this device that would cause a "Custom" status? For one im not sure how you managed to even get a Custom Binary without setting the Warranty Bit. 2nd I noticed "Eng Mode: Dev Device" in Download Mode. And thirdly How do you manage to tick OEM Unlocking Off, On and then back Off accidentally? Changing the OEM Unlocking setting requires a Factory Reset each time.
last1youlove said:
Did you flash anything onto this device that would cause a "Custom" status? For one im not sure how you managed to even get a Custom Binary without setting the Warranty Bit. 2nd I noticed "Eng Mode: Dev Device" in Download Mode. And thirdly How do you manage to tick OEM Unlocking Off, On and then back Off accidentally? Changing the OEM Unlocking setting requires a Factory Reset each time.
Click to expand...
Click to collapse
I have never flashed anything other than stock DT firmware on this device (multiple times). It was never rooted...
It seems strange to me as well that Warranty bit is 0 while it says "Current Binary: Custom".
It says "Eng Mode: Dev Device" as this is a testing device that Samsung releases to its partners (mainly Telco Partners) for testing and development, so it never was a commercial unit for sale.
OEM Unlocking was off and I remember ticking it "on" by mistake as I did not intend to perform any flashing at the time. As I can recall I left it on and next morning phone reboots claiming "Custom binary blocked by FRP Lock". I would bet that I left it on but in download mode you can see that it says "OEM LOCK: ON" which I guess means "OEM UNLOCK: OFF".
besmirgogu said:
I have never flashed anything other than stock DT firmware on this device (multiple times). It was never rooted...
It seems strange to me as well that Warranty bit is 0 while it says "Current Binary: Custom".
It says "Eng Mode: Dev Device" as this is a testing device that Samsung releases to its partners (mainly Telco Partners) for testing and development, so it never was a commercial unit for sale.
OEM Unlocking was off and I remember ticking it "on" by mistake as I did not intend to perform any flashing at the time. As I can recall I left it on and next morning phone reboots claiming "Custom binary blocked by FRP Lock". I would bet that I left it on but in download mode you can see that it says "OEM LOCK: ON" which I guess means "OEM UNLOCK: OFF".
Click to expand...
Click to collapse
so this is the problem, you are flashing commercial firmware on testing device to rectify the custom lock. try flashing combination firmware. in this guide is a link to download combination firmware. it is official combination firmware to solve device problems.
Munawar Mehmood said:
so this is the problem, you are flashing commercial firmware on testing device to rectify the custom lock. try flashing combination firmware. in this guide is a link to download combination firmware. it is official combination firmware to solve device problems.
Click to expand...
Click to collapse
I managed to flash COMBINATION_FAC_FA81_N960FXXU3ASF1_BoxWares.tar.md5. Phone tries to reboot showing corrent model but on top of screen it says "Boot image signature check fail!!!" and "Reboot to avoid Warranty bit set!!!"
In download mode CURRENT BINARY:Custom and SYSTEM STATUS:Custom
I have added below a couple of screen shots of the situation now:
https://drive.google.com/open?id=1lwbblCDLKnvDkyBMtlsOOhH_F1c4HpeJ
i have once again gone through the entire thread and i see that you mention odin version 3.13.3, while the latest version of odin is 3.13.1. and i am using odin version 3.13.1. try this specific version of odin. and flash combination firmware. it seems from latest screen shot that your phone is not flashing any firmware. it just shows progress on pc but on phone it is not happening at all. try the odin version i mentioned.
My working theory is that because this is a testing device it's marking any firmware that isn't the specific engineering firmware the device shipped with as a "Custom Binary" you wouldn't be able to flash official releases. (Including Combination Firmware) You would probably need to return the device to the manufacturer or provider and request that the original operating system image be restored.
However please take this with a grain of salt. I'm not certain this is the case.
last1youlove said:
My working theory is that because this is a testing device it's marking any firmware that isn't the specific engineering firmware the device shipped with as a "Custom Binary" you wouldn't be able to flash official releases. (Including Combination Firmware) You would probably need to return the device to the manufacturer or provider and request that the original operating system image be restored.
However please take this with a grain of salt. I'm not certain this is the case.
Click to expand...
Click to collapse
you sir are making alot of sense.
Hi! I've tried following dr.ketan's post on rooting a Note 9 with the first method ("(Guide)Root +Busybox + OEM Fix + EFS backup Note 9 N960F/FD/N Exynos only").
After that I've flashed RomAur via TWRP, booted up and while setting up my account the screen became black with the message "only official released binaries are allowed" . I've then tried to flash the stock firmware via Odin but on the screen of my phone I get a "SW REV CHECK FAIL (BOOTLOADER) DEVICE 4 BINARY 1" error.
Odin seemed stuck so I unplugged my phone and then got a screen saying "An error has occured updating the device software. Use the Emergency recovery function in the Smart Switch PC software."
My phone's a N960F/DS
After further research I've come to the conclusion that:
1) SW REV CHECK FAIL (BOOTLOADER) DEVICE 4 BINARY 1 means the firmware I was trying to flash was too old and Samsung decided that downgrading isn't an option anymore.
2) I'm unable to flash anything else besides Samsung official firmware for a 7 or more days because of a Knox Guard (RMM/KG state prenormal). So reinstalling any custom recovery to then flash a new Rom can't be done since there's no way to bypass this time period on Pie.
I did end up flashing stock but I can't mod my phone until the kg state goes back to normal or checking
I've tried waiting for 168 hours twice since the last post. KG State won't change from prenormal. I should mention that my OEM unlock option is available but I can't flash anything besides Samsung binaries. Last week I've flashed TWRP despite the KG State not changing and I got the same "only official released binaries are allowed" error followed by a red fail box in ODIN. At this point I have no idea how to fix it. Does anyone have any suggestion?
I've downloaded the latest stock (N960FXXU4DSLB) and installed it. After that it looks like the prenormal state went away. Immediately I've toggled the OEM Unlock option, waited for the factory reset to be done and checked to see if the toggle was still there. The OEM unlock option works just like before BUT I've successfully installed geiti94's latest TWRP (3.2.3 ATM). Flashing RMM-State_Bypass_Mesa_v2.zip no-verity-opt-encrypt-6.0.zip and Magisk 20.2 seem to be able to get root working but there are some weird bugs:
- can't set up any security measure such as a pin, patter or biometrics
- if I try to log into my Samsung account I get a "processing failed" pop up
- restarting my phone causes it to bootloop
I think I've softbricked my Redmi Note 10 Pro. I've flashed the stock MIUI 13 Global ROM with the MiFlash tool and it failed at the end with an error about sparse files.
After rebooting, it got stuck in an orange Fastboot logo. Pressing Volume Down + Power just restarts, back into this orange Fastboot logo.
MiFlash no longer detects it. XiaoMiTool V2 also doesn't detect it.
I need this phone desperately. Please help what to do.
OK, after rebooting my PC, I could flash it again.
During the first flash I made the mistake to select "Save user data" which probably caused the error.
The flash worked second time with "Clean all". I did fail at the end with "not catch checkpoint", but apparently that's not a big deal. It works.