This is my first experience with rooting a phone and I think I messed up...big time! All I wanted to do was get rid of preloaded garbage on the phone to save battery life. Now I have a red message, "Custom Binary blocked by FRP lock".
My G920T was completely stock until today when I loaded CF_Auto_Root into it with Odin.
The phone immediately went into a boot loop after the install. I was able to boot into device recovery and did a factory reset at that point. I didn't know until after I reset to factory that I had accidentally installed Auto_Root for the G920F.
No problems here, booted back into initial setup, and I completed all of the setup items. Logged into Google, Samsung, etc. Because this was my first time and ended with a boot loop, I decided I'd just deal with the battery life problems. I turned off USB Debugging and the Bootloader modify option. The phone seemed to be working normally until I unplugged the phone from my computer, plugged it into wall fast charger, the rebooted the phone.
Now all I get is the Samsung home screen with the red message in the upper left corner. It will continually loop between the home screen and a black screen if the phone is plugged in. I cannot get back into the recovery menu as the phone is unresponsive to home + power + vol. up. I can however boot into the download menu.
I have tried reflashing the stock tar file, a stock bootloader, and stock modem with Odin 3.10.6 and 3.10.7. When I attempt the reflash I get the failed message in Odin, and "SW Rev. Check Fail. Device: 3. Binary: 2.
Are there any other options I have at this point, or something I'm doing wrong or incompletely?
Thanks
Edit:
I have fixed the phone after about 10 hours of messing around with stock firmwares, Odin, Smart Switch, Kies, etc. If the option was there, I tried it.
The FRP Lock is easily fixed by flashing in the stock firmware, but it must be the version the phone was at before rooting. This seems to be pretty common knowledge but my problem was I didn't know which version I had. I started with 0F6, that didn't work because I would then get "sw rev check fail device 3 binary 2" in the download screen and Odin would show a red fail almost immediately.
At this point I was getting pretty beat up by the phone and was trying anything I could find. I noticed, when entering the download menu before you press the vol. up button, that you can press the home key and the phone will show the barcode. This was the turning point for fixing my phone. It was in the barcode screen that I found my phone's S/N. Perhaps it is located other places, like behind the battery I can't remove, or on a carriers website (checked T-Mobile and didn't see it), but this is where I found it. I then remembered that Smart Switch had an option for 'Emergency software recovery and installation'. When you enter that menu the program asks you for your phone's model number, then the phones S/N. I could now use this option because I had the required info. I thought I was making progress but this method failed at 60% of downloading the software and drivers and an error in the download screen of "sw rev check fail device 3 binary 2".
The key for Smart Switch is, after you enter your model number and serial number, the program tells you what firmware version the phone was at. The 3 fields that pop up all read "OJC". More progress! The firmware version I was trying to install, which was the newest one I could find without knowing what to look for, was 0F6. I found the OJC .zip file at sammobile.com. It took 2 hours to download to 95% and the download failed. Restarted the download and waited 2 more hours.
While the OJC was downloading I was still messing with options I was reading about from google searches. I read multiple times to try different versions of Odin, try different USB ports, try different sequences of loading/connecting device to pc. I changed USB ports on the PC and the samsung drivers started installing for the device. A second driver installed this time for Samsung Modem 2 (I only particularly remember the Modem 2 part) that I didn't see install on the other USB port. At this point I decided to try Smart Switch again. This time, with the extra driver, the download completed to 100% and started to install some files onto the phone. But, it only got to 20% installed and erred again. This time the error was "sw rev check fail device 3 binary 1". I also noticed that the Current Binary field on the download screen changed from "custom" to "Samsung Official". More Progress. At this point there was nothing more I could do until the OJC was finished downloading.
As soon as I unzipped the OJC I opened Odin v3.10.7 and loaded the firmware into the AP, plugged in the phone, hit start. Red Fail. Then tried loading the firmware with Odin v3.10.6. Loaded OJC into the AP, connect device, hit start. Red Fail, but, I made it past the Nand Write Start and got all the way down to the system installation part before it failed. More Progress! Tried v3.10.7 again and didn't make it past Nand Write before it failed again. Then I started changing the order of when I opened Odin, loaded the firmware, and connected the device. There are tutorials everywhere that specifically say, "CONNECT IN THIS ORDER OR THE FLASH WONT WORK", I found this to not be entirely true.
How I eventually got the OJC firmware loaded back onto the phone was to Restart the phone into the Download screen, connect phone to pc and wait for Odin to recognize the device, then load OJC into the AP, hit start. In v3.10.7 the install failed every way I tried at different points in the install. v3.10.6 is the one that ended completely re-flashing the phone to stock OJC firmware.
If you're new, or stuck, make sure you do the following:
- Verify you are trying to load the correct firmware with smart switch. (OJC is the last 3 characters of the file names)
- Try different versions of Odin
- Try different orders of setup processes
- Try different USB ports and MAKE SURE you have all Samsung device drivers installed
I might add .. don't forget to run ODIN as administrator.
Also, to avoid this in the future, disable the OEM Lock in Developer Options.
YOUR AN ANGEL :d
Hello there. I got "Custom Binary(RECOVERY) Blocked By R/L, I have odin and firmware but odin can`t see my phone. What i have to do?
1sicgsr said:
This is my first experience with rooting a phone and I think I messed up...big time! All I wanted to do was get rid of preloaded garbage on the phone to save battery life. Now I have a red message, "Custom Binary blocked by FRP lock".
My G920T was completely stock until today when I loaded CF_Auto_Root into it with Odin.
The phone immediately went into a boot loop after the install. I was able to boot into device recovery and did a factory reset at that point. I didn't know until after I reset to factory that I had accidentally installed Auto_Root for the G920F.
No problems here, booted back into initial setup, and I completed all of the setup items. Logged into Google, Samsung, etc. Because this was my first time and ended with a boot loop, I decided I'd just deal with the battery life problems. I turned off USB Debugging and the Bootloader modify option. The phone seemed to be working normally until I unplugged the phone from my computer, plugged it into wall fast charger, the rebooted the phone.
Now all I get is the Samsung home screen with the red message in the upper left corner. It will continually loop between the home screen and a black screen if the phone is plugged in. I cannot get back into the recovery menu as the phone is unresponsive to home + power + vol. up. I can however boot into the download menu.
I have tried reflashing the stock tar file, a stock bootloader, and stock modem with Odin 3.10.6 and 3.10.7. When I attempt the reflash I get the failed message in Odin, and "SW Rev. Check Fail. Device: 3. Binary: 2.
Are there any other options I have at this point, or something I'm doing wrong or incompletely?
Thanks
Edit:
I have fixed the phone after about 10 hours of messing around with stock firmwares, Odin, Smart Switch, Kies, etc. If the option was there, I tried it.
The FRP Lock is easily fixed by flashing in the stock firmware, but it must be the version the phone was at before rooting. This seems to be pretty common knowledge but my problem was I didn't know which version I had. I started with 0F6, that didn't work because I would then get "sw rev check fail device 3 binary 2" in the download screen and Odin would show a red fail almost immediately.
At this point I was getting pretty beat up by the phone and was trying anything I could find. I noticed, when entering the download menu before you press the vol. up button, that you can press the home key and the phone will show the barcode. This was the turning point for fixing my phone. It was in the barcode screen that I found my phone's S/N. Perhaps it is located other places, like behind the battery I can't remove, or on a carriers website (checked T-Mobile and didn't see it), but this is where I found it. I then remembered that Smart Switch had an option for 'Emergency software recovery and installation'. When you enter that menu the program asks you for your phone's model number, then the phones S/N. I could now use this option because I had the required info. I thought I was making progress but this method failed at 60% of downloading the software and drivers and an error in the download screen of "sw rev check fail device 3 binary 2".
The key for Smart Switch is, after you enter your model number and serial number, the program tells you what firmware version the phone was at. The 3 fields that pop up all read "OJC". More progress! The firmware version I was trying to install, which was the newest one I could find without knowing what to look for, was 0F6. I found the OJC .zip file at sammobile.com. It took 2 hours to download to 95% and the download failed. Restarted the download and waited 2 more hours.
While the OJC was downloading I was still messing with options I was reading about from google searches. I read multiple times to try different versions of Odin, try different USB ports, try different sequences of loading/connecting device to pc. I changed USB ports on the PC and the samsung drivers started installing for the device. A second driver installed this time for Samsung Modem 2 (I only particularly remember the Modem 2 part) that I didn't see install on the other USB port. At this point I decided to try Smart Switch again. This time, with the extra driver, the download completed to 100% and started to install some files onto the phone. But, it only got to 20% installed and erred again. This time the error was "sw rev check fail device 3 binary 1". I also noticed that the Current Binary field on the download screen changed from "custom" to "Samsung Official". More Progress. At this point there was nothing more I could do until the OJC was finished downloading.
As soon as I unzipped the OJC I opened Odin v3.10.7 and loaded the firmware into the AP, plugged in the phone, hit start. Red Fail. Then tried loading the firmware with Odin v3.10.6. Loaded OJC into the AP, connect device, hit start. Red Fail, but, I made it past the Nand Write Start and got all the way down to the system installation part before it failed. More Progress! Tried v3.10.7 again and didn't make it past Nand Write before it failed again. Then I started changing the order of when I opened Odin, loaded the firmware, and connected the device. There are tutorials everywhere that specifically say, "CONNECT IN THIS ORDER OR THE FLASH WONT WORK", I found this to not be entirely true.
How I eventually got the OJC firmware loaded back onto the phone was to Restart the phone into the Download screen, connect phone to pc and wait for Odin to recognize the device, then load OJC into the AP, hit start. In v3.10.7 the install failed every way I tried at different points in the install. v3.10.6 is the one that ended completely re-flashing the phone to stock OJC firmware.
If you're new, or stuck, make sure you do the following:
- Verify you are trying to load the correct firmware with smart switch. (OJC is the last 3 characters of the file names)
- Try different versions of Odin
- Try different orders of setup processes
- Try different USB ports and MAKE SURE you have all Samsung device drivers installed
Click to expand...
Click to collapse
HOW can i get The Serial NUMBER AND WRITE IT DOWN ON SMART SWITCH OR KIES ?? IF IT IS A BARCODED IN THE DEVICE ?!??!
Likebeast said:
HOW can i get The Serial NUMBER AND WRITE IT DOWN ON SMART SWITCH OR KIES ?? IF IT IS A BARCODED IN THE DEVICE ?!??!
Click to expand...
Click to collapse
smh, there is number on top of barcode that saids S/N
After Reading this post i felt dumb, because I thought imei on back of my phone was S/N whole time
I used SmartSwitch Emergency software recovery and installation, went through 2 cycles of installation somehow and it finally fixed my phone.
I'm using SM-920T galaxy S6
Hey sir did u just flash the stock rom u downloaded and it fix the frp lock?? I need ur help i also accidentally activated the oem.. please helppp sir
Related
i have sgs6 gm920F NEE, i tried to root it but ended up to brick my phone. When i power it up it just get stuck in the "samsung galaxy s6" screen with little red text in the left top corner saying "recovery is not seandroid enforcing"..
I cant get to recovery or get the device up and running, all i can do is to get in odin mode/download mode.
i have downloaded official 5.1.1 firmware, i have tried using different versions of odin but everytime its the same, after the "nand write start" it just fails, every single time. i have tried to use the hidden.img only from the firmware but it ends up just booting the samsung logo over and over again. also i have tried different usb ports..
Basically i cant install new firmware via odin, i cant install it via kies (i dont know the phones serial number, receipt or the box wont say this, or the phone either)..
Is there anything i can do to this?
thx, i dont want my expensive phone to be a brick.
Try this: http://forum.xda-developers.com/galaxy-s6/general/project-zero-pac-firmware-pit-file-t3181133
Try flashing stock firmware via Smart Switch.
1. Download Smart Switch.
2. Put your phone in download mode
3. Press "more"
4. Press "Emergency software recovery and initialization"
5. Device initialization
6. search for you device - For example SM-G920F
7. Type in S/N number that was on the back of your phone.
8. Follow the steps and it should reinstall stock android for you.
!!Beware that your files and stuff will be gone!!
It worked, Quintz! Thank you so much.
At first, I had a wrong modem and could not make phone calls.
After your method, I reinstalled it again using Kies and now I have my old working phone back.
Thank you sooo much !
I bought a G930F from Amazon for use with my T-Mobile service, rooted it, and flashed a custom ROM (not sure exactly which one, but I have a folder named "CF-Auto-Root-herolte-heroltexx-smg930f") to it almost a year ago and everything was working just fine until this.
I was trying to get FRep (android macro/automation) working. It uses a setup tool on a PC that requires a connection and USB debugging enabled on the phone. When trying to run the setup I was getting errors about the socket/address already being in use so I'm not sure if it ever managed to do anything, but I saw a suggestion of rebooting my phone to fix the errors. In doing that I held down the power button, for my ROM's power options, chose reboot, went to the next reboot screen (maybe TWRP?) and chose the default reboot there.
When my phone tried to boot I got the Samsung Galaxy S7 logo with small red text of "Custom binary blocked by FRP lock". I'm still not entire sure what causes this (seems like a mismatch between having a custom ROM and some other setting). I'm wondering if the FRep setup tool somehow switched from OEM firmware protection flag. I booted into the download mode and tried to just reflash my old ROM, but even in the download mode I'm seeing "Custom binary (RECOVERY) blocked by FRP lock" with "NAND Write Start!!" then "Complete(Write) operation failed." in Odin3 logs.
I'm giving as much detail as I can because I'm not exactly sure which pieces are which. I've actually tried flashing the "CF-Auto-Root-herolte-heroltexx-smg930f.tar.md5" and "twrp-3.0.2-2-herolte.img.tar" files in the "AP" slot in Odin3 as I don't remember which file is for what, but both give errors on writing. I'm wondering if I shouldn't do custom ROMs in the future as I don't follow the scene long enough to learn all that I should in order to not mess things up.
Any help will be appreciated!
edit: I'm downloading a stock S7 ROM from sammobile, but I don't think Odin3 will be able to flash it anyways. Is there any way to use the PIT settings or something else to change the OEM protection piece?
edit2: After downloading a stock ROM I was able to flash it all with Odin3. I think only part of it would have been necessary (maybe just needed a new bootloader, not entirely sure about AP/CP/CSC fields in Odin3.) Got the phone working again, but now I've gotta remove some popup inducing malware that I think I got when downloading a stock ROM the link in the instructions here: https://forum.xda-developers.com/galaxy-s7/help/frp-boot-fix-sm-g930f-t3350149
Hi guys,
I need help with my G955F. I was on Carotid's ROM and attempted to flash the AQL5 (BTU) firmware downloaded from Samfirm to go back to stock. The flash failed during writing the system.img and now it is stuck on the "Error has occurred while updating the device software" screen.
I can get into Download mode and I can boot into TWRP using ODIN.
Each attempt to flash a firmware in ODIN throws up a "FAIL" during the system.img write portion.
Each attempt to reflash a ROM from my external SD card in TWRP throws up an error while writing to system. /System is unmounted when I start up TWRP and I have to manually mount it each time.
The phone is "not supported" in Samsung Smart Switch.
Anyone have any ideas?
Never mind!
I noticed that whenever I plugged the phone into the PC when the "Error has occurred while updating the device software" screen was on it flashed up as "added" in Odin.
So I tried flashing the stock AQL5 firmware while on this screen and it worked!
I'm just going to leave this here because it's an avenue I never considered and haven't seen online.
ianrobbie said:
Never mind!
I noticed that whenever I plugged the phone into the PC when the "Error has occurred while updating the device software" screen was on it flashed up as "added" in Odin.
So I tried flashing the stock AQL5 firmware while on this screen and it worked!
I'm just going to leave this here because it's an avenue I never considered and haven't seen online.
Click to expand...
Click to collapse
Good observations.
You are correct, if the first flash fails, immediately re-enter download mode and flash again.
JeffDC said:
Yes, if the first flash fails, immediately re-enter download mode and flash again.
Click to expand...
Click to collapse
Yeah, but that's the thing. I wasn't even in Download mode for the successful flash. I was just on the Emergency Recovery screen and when I started the firmware flash, a small progress bar appeared on the screen below the text.
ianrobbie said:
Yeah, but that's the thing. I wasn't even in Download mode for the successful flash. I was just on the Emergency Recovery screen and when I started the firmware flash, a small progress bar appeared on the screen below the text.
Click to expand...
Click to collapse
Have not heard of that before - new to me, interesting find.
So the way to replicate is . . .
The way I got there was to have a screwed up install. I tried to flash a stock firmware and it generated a FAIL in Odin during the /system.img write.
The phone then rebooted to a pale green screen with a large triangle and exclamation mark advising me that the phone was in Emergency Recovery Mode and I should restore it by plugging it into a PC with Smart Switch installed.
Interestingly, Smart Switch refused to recognise my phone, saying it was an "unsupported device".
After numerous attempts to flash new firmware through Odin and TWRP (even using the two-step method of getting into Download mode) and using different cables/ports I was planning on getting it professionally repaired until I noticed that when Odin was running and I plugged the phone in, with the emergency screen on, it was "added" as it would be during Download Mode.
I loaded up the AQL5 firmware, and tried to flash. A progress bar appeared under the text on screen and it got about halfway through flashing /system when it failed again, but this time it has progressed much further than any other attempt.
I then reset everything, used an official Samsung cable and a port directly connected to the motherboard on my PC (I had been using a USB extension cable before) and attempted another flash and it worked!
I don't know how you would go about replicating those circumstances without risking your phone but if you find yourself stuck in the same situation, give it a try.
It worked for me.
Thanks, ianrobbie.
Hey guys!
So basically I will start from the top:
1. Device is Samsung Galaxy Note 10 Lite (SM-N770F) (F/DS if it matters really)
What happened is:
I've wanted to install Android 11 update on my phone - downloaded SamFirm app, searched for correct firmware for my region (I've made sure to select appropriate device and region).
Then I've downloaded Odin (3.14.1), loaded all files correctly - no errors or anything, started the process in Odin and after some time I got an error on the phone - Custom Binary(SUPER) Blocked By OEM Lock.
Now what happens is that I can't do literally anything with my device - it's turned on constantly on the same screen, on the top I can see the above error in red font, while on the center of the screen there is message "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software." - which I of course did, but Smart Switch doesn't even see the device or anything.
I can't turn off the device - while I press power and volume down button, it just goes black for a moment and comes right back up on the same screen no matter what.
Although, I think it's in downloading mode - Odin still sees it correctly (when I plug it in or out I can see changes in Odins screen).
Tried downloading older versions through SamFirm, other versions of Odin, other USB in computer, other cable - no luck at all.
Did I fully bricked the device? Or is it just soft bricked? Is there anything I can do now? Can Samsung center help me? I've tried chatting with them but they just sent me to their facility.
I'd do literally anything to fix this. Please help me, I'm desperate.
If you can get into recovery, i would try factory reset there. Then go to downloadmode and try complete new flash of newest version with csc (not home_csc). But im not sure, wether it is possible to flash with odin if bootloader is not unlocked in this new samsungs. I allways used odin with unlocked bootloader.
can't get into recovery - only thing I see is the above mentioned screen and there is 0 possibility of going anywhere else
priamusx said:
Hey guys!
So basically I will start from the top:
1. Device is Samsung Galaxy Note 10 Lite (SM-N770F) (F/DS if it matters really)
What happened is:
I've wanted to install Android 11 update on my phone - downloaded SamFirm app, searched for correct firmware for my region (I've made sure to select appropriate device and region).
Then I've downloaded Odin (3.14.1), loaded all files correctly - no errors or anything, started the process in Odin and after some time I got an error on the phone - Custom Binary(SUPER) Blocked By OEM Lock.
Now what happens is that I can't do literally anything with my device - it's turned on constantly on the same screen, on the top I can see the above error in red font, while on the center of the screen there is message "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software." - which I of course did, but Smart Switch doesn't even see the device or anything.
I can't turn off the device - while I press power and volume down button, it just goes black for a moment and comes right back up on the same screen no matter what.
Although, I think it's in downloading mode - Odin still sees it correctly (when I plug it in or out I can see changes in Odins screen).
Tried downloading older versions through SamFirm, other versions of Odin, other USB in computer, other cable - no luck at all.
Did I fully bricked the device? Or is it just soft bricked? Is there anything I can do now? Can Samsung center help me? I've tried chatting with them but they just sent me to their facility.
I'd do literally anything to fix this. Please help me, I'm desperate.
Click to expand...
Click to collapse
I experienced similar situation, but in my case, even my phone stuck in download mode screen, ODIN did not detect my phone, even PC wasn't response when plug in USB cable. As same as you say, when I tried to power off, it was power on itself and "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software" message appear on screen.
Then I tried to enter download mode again in download mode screen, by pressing power off, and after screen go black press immediately volume up+down. After that phone enter the download mode screen (again), it was looks like the same, but this time I was able to install firmware. Actually I really dont understand why this method work but you can give a try.
Unfortunately, still no luck.
But I've thought about other thing. Do you think it's possible to use .PIT file and re-partition option in Odin?
From what I've read everywhere this will wipe all partition data (so basically it should wipe every single thing) from the device, so it should be possible to overcome this oem lock, shouldn't it? Or will I just brick the device even further? I'm kinda desperate here as the phone is about 2-3 months so it's as brand new...
Edit: I think I've found another issue here. My device model is SM-N770F/DS so it's a Dual Sim model, while everywhere I only see firmware for SM-N770F so without dual sim. May it cause problems as well? How about the above option with flashin firmware with pit file and wiping partitions?
If you have figured it out by now good for you. If not, that emergency screen you see is nothing to fear. You can flash firmware with Odin from that screen...no worries your not bricked. Just do as you would if the device were in download mode..flash away.
Was your bootloader unlocked?
Condensed for brevity:
Unlocked bootloader and Debug USB enabled. Went to flash an AP and it failed. Tried to use Frija to get the most recent update, found N986BXXS3EULH REV01, tried to flash the AP/BL/CP/CSC to refresh the phone and it's failing.
Everything matches my phone when I typed *#1234# (EULB/EULH) except the download has REV01 added to the end.
Phone is stuck in download mode no matter how I reboot it. Phone isn't bricked but won't do anything else.
Edit: Updated to using Odin 3.14.4 instead of 3.13.1
Edit 2: Figured out the phone is freezing after any fail (brightness doesn't change with volume keys). I get the failed PIT as well as "Can't open specified file (Line:2006)"
Edit 3: Re-opened Frija and it gave me an entirely different FW this time that superseded what I had on the phone originally and the DL'd file (*3EULH became *3EVA9).
Tried to use new CSC and it keeps failing at prism.img. It's progress but not really at the same time.
Edit 4: It lets me install the BL and CP for either/or EULH or EVA9 but neither CSC or AP work ever. I'm thinking I just have a bad firmware or something.
Final update for the night: The files are good. Compared hashes across multiple downloads. Phone isn't seen in Samsung Smart Switch and there doesn't seem to be a recovery menu. TWRP or otherwise.
If anyone has any ideas please let me know. I'm pulling my hair out because it's brand new. All I did was try to start by updating the stock firmware with Odin (after bootloader unlocking and USB debug enabling) and this happened.
-------------------------------------------------------------------------------------
Day 2: Moved back to Odin 13.1 and extracted PIT from EULH CSC, installed it, then did the BL/CP, installed fine. Still froze with CSC/AP. Then attempted to try it all at once. PIT, CP, BL, CSC, and AP. It actually starts installing now. But it specifically always freezes at the super.img portion. So while I'm unsure what's going on now since I'm still trying to install the correct official ROM, I'm starting to think the ROM is somehow incompatible with my phone.
HERE'S THE ANSWER! Many thanks to those who attempting to help. We were doing and advising everything correctly.
The problem is the PC itself. Which was why the issues seemed so varied. I attempted every USB in my computer, none would flash (they drop out randomly with my phone), and the first sign I didn't realize was a sign was the phone wouldn't work on my USB-C ports, only 3.0/3.1.
I run a Threadripper 3960x on an Aorus TRX40board. I had to go to a 2015 touchscreen laptop to do this. If you're having issues then literally try a new PC if possible. If you see that it isn't connecting to Odin on USB-C, then you may well have the same issues I was having.
Note: this may be a driver issue, as I used every one of my 20-ish ports and they all still failed, as well as about 5 different cable options to go between USB/USB to C and USB-C to USB-C.