Database Users

Stuck in a boot loop even after flashing to stock from odin.

I was using stock firmware and all of a sudden today the phone stuck into a boot loop. I flashed the stock firmware all the way back to 4.4.4 with Odin but right after the successful message I get on odin the phone restarts and it gets into the same boot loop. I suspected it might have been an issue with the partition since when I first got the phone 6 months ago I used a pit file in odin (I know I shouldn’t have) but the phone still worked fine. Now I googled the N910F+pit file, downloaded the first pit file I found, flashed it together with the kit kat stock rom but the results are still the same. I’ve tried flashing the stock lollipop rom for my Country and different countries with the same result. I have also tried flashing CF-Auto-Root and TW but odin gives an error and I get an error on the phone as well. One error that I have gotten which was not consistent since I can’t reproduce the result was “Custom binary blocked by Reactivation Lock”.
I would really appreciate any input.

I'm in the same situation exactly. At the moment I'm trying to download UK 5.1 to play with odin once again.

did you manage to fix it?

BettlePimp said:
I was using stock firmware and all of a sudden today the phone stuck into a boot loop. I flashed the stock firmware all the way back to 4.4.4 with Odin but right after the successful message I get on odin the phone restarts and it gets into the same boot loop. I suspected it might have been an issue with the partition since when I first got the phone 6 months ago I used a pit file in odin (I know I shouldn’t have) but the phone still worked fine. Now I googled the N910F+pit file, downloaded the first pit file I found, flashed it together with the kit kat stock rom but the results are still the same. I’ve tried flashing the stock lollipop rom for my Country and different countries with the same result. I have also tried flashing CF-Auto-Root and TW but odin gives an error and I get an error on the phone as well. One error that I have gotten which was not consistent since I can’t reproduce the result was “Custom binary blocked by Reactivation Lock”.
I would really appreciate any input.
Click to expand...
Click to collapse
It looks like your problem is that you forgot to turn off the samsung activation lock before flashing. If you forgot what that is see this I have not used this feature on my phone; however, I would suggest wiping with odin then flash the official stock ROM for your phone that you previously had on it when it did work, hopefully it will boot then login to you samsung account when it asks you about the reactivation lock. There are some activation lock bypass methods out there if you do a quick google search. Hopefully this will point you in the right direction.

The reactivation lock is indeed on. "Reactivation Lock(KK): On"
I have no way of turning it off since I'm stuck in a boot loop no matter what firmware I flash through Odin.
Any other suggestions?

I have same problem on my SM-910H
This problem was after updating 5.1.1 and isntallind micro-sd card (128gb)
In 4-5 days after this, bootloop began.
I deisntalled micro sd, checked it in computer for mistakes, fixed it and after this phone worked fine.
Today same problem, but when I deisntall micro-sd my problem does not go away.
I downgraded phone to 4.4 - does not help
Data wipe, cache wipe etc - does not help...
Waiting for solution from proffesionals (
update^
I've found 4 file Factory firware and tried to falsh it
What does Odin say:
<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/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse

Do this, it worked for me. In ODIN, just AP/PDA Autoroot md5 file. It will not be successful and you will get "FAILED" message. Disconnect the phone from PC, pull out battery. Reinsert the battery and boot.

The same happened to me.

To all with this problem. My history:
1. Suddenly my stock device go in bootloop
2. Tried to flash it with official software it does not help
3. Tried to flash it with 3 or 4 file service firmware - did not help
4. Service center (not official, that was service center of my internet market) falshed it with some firmware and sad do not update it. It helped for 2 days.
5. They replaced the motherboard. Only this can help.
So, if you have bootloop in your stock device - try to falsh it with firmware if it does not help - take it to service center and say that they do not spent their and your time and change device or mother board.
Now its ok, working fine.
Wrote it because I spent a lot of time to repair it and maby it will help to some one.

SM-G550T1 boot loop "Custom binary is blocked by FRP Lock"

I had used TWRP to install SuperSU to root. This seemed successful, but a day or two later the phone had powered itself off, and on power-up loops displaying the tiny red "Custom binary is blocked by FRP Lock" message. The phone will boot into download mode, but won't enter recovery mode.
I tried repeating the install of TWRP using ODIN 3.12, but now that fails. Tried installing factory images (\BL_G550T1UVU1APF1_CL8180604_QB9902404_REV00_user_low_ship.tar.md5 etc.) w/ ODIN, and that fails too.
Is this an indication I don't have the latest image files? ODIN messages 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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)​

Made some progress
Reviewing other threads I found a not that talked about installing only the "AP" file using ODIN. That seems to have worked.

BHarris said:
Reviewing other threads I found a not that talked about installing only the "AP" file using ODIN. That seems to have worked.
Click to expand...
Click to collapse
what worked? and what firmware. I have 2 on5's one sm-G-550T and a sm-g550T1 that both ended up with the "custom binary blocked by FRP lock" on the same day..
Please help!

I just tried a bin I downloaded from S U site and it didn't work. Gotta love the On5 lol.

Custom Binary Lock
The same happened to me: i have not found a complete solution, the closest i get to anything is; i put the On5 in Odin3 v3.12 and select the AP option and putting the recovery.tar file and running it. it goes good till its done and the result is Custom Binary (recovery) blocked by FRP lock in green letters. but still no success. i have tried trwp recovery, the home.tar file, each file by them selves and having trouble. i may not be an expert at this type of programimng but i pick things up quickly if there is any solution to my problem please let me know. thx............ by the way i have also tried kies and wont connect to it as well

Same Problem FRP Blocked Bootlooping
I did all the same as you and have the same problem. Everything was fine till the phone got restarted.
XDA HEEEEEEEELP!!

SeleneKnightress said:
I did all the same as you and have the same problem. Everything was fine till the phone got restarted.
XDA HEEEEEEEELP!!
Click to expand...
Click to collapse
You need to reinstall the firmware using Odin. Then, when you root again, you need to make sure you have oem unlock and usb debugging on in the developer options. Not having those on and rebooting when rooted cause the custom binary problem.

Help needed.

So I tried to root using an old youtube tutorial (which I since have learned is a bad idea), now it's stuck in a boot loop. Tried to factory restore from boot menu, didn't work. Took my S7 SM-G930V to Geek Squad at Best Buy, and the Samsung guy basically told me he couldn't fix it and neither would Samsung, as a punishment for trying to root. Maybe if he comes into the ER needing life-saving treatment, I'll tell him I won't help him as punishment for doing one of the stupid things I see every day.... I was just going to throw the damn thing away and buy a new phone, but he pissed me off, so now I want to fix it just to spite him.
Tried kies (said to use smart switch), smart switch (unsupported device), and Odin, all fail. Used the links for the correct firmware here. Tried Verizon's software assistant... also fails. During flash with Odin, it gets about 3 seconds into the bar that goes across the bottom of the phone, then Odin says failed. I'm on android 7.0 snapdragon.
I can get it into download mode, but flashing fails nearly immediately. In download mode, at the top left it says: "ODIN MODE (HIGH SPEED), PRODUCT NAME: SM-G930V, CURRENT BINARY: Samsung Official, SYSTEM STATUS: Official, FRP LOCK: OFF, QUALCOMM SECUREBOOT: ENABLE, AP SWREV: B4(2,1,1,1,1) K1 S3, SECURE DOWNLOAD: ENABLE
Also, I wrote down the Build # and baseband in case they help... Build #: NRD90M.G930VVRS4BRA1 Baseband: G930VVRS4BRA1
Im sure you experts need additional more specific information, so ask away. And thank you!
Just tried Odin PrinceComsy version and the firmware on the tutorial thread in here for unrooting Verizon Galaxy S7, and failed again. Here's the log:
<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> emmc_appsboot.mbn
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Anybody???
I'm sure you're tired of walking noobs through this crap, but I'm sure you can sympathize the idea of suddenly losing access to your smart phone. Does anyone have any ideas on what to try next? I've read for hours and tried dozens of tutorials and I'm just not getting anywhere. FRUSTRATING AS HELL!!! I can stop a heart attack or a tension pneumothorax in my sleep, but trying to program a damn smart phone correctly... you might as well tell me to try to fly.

ERDOC76 said:
So I tried to root using an old youtube tutorial (which I since have learned is a bad idea), now it's stuck in a boot loop. Tried to factory restore from boot menu, didn't work. Took my S7 SM-G930V to Geek Squad at Best Buy, and the Samsung guy basically told me he couldn't fix it and neither would Samsung, as a punishment for trying to root. Maybe if he comes into the ER needing life-saving treatment, I'll tell him I won't help him as punishment for doing one of the stupid things I see every day.... I was just going to throw the damn thing away and buy a new phone, but he pissed me off, so now I want to fix it just to spite him.
Tried kies (said to use smart switch), smart switch (unsupported device), and Odin, all fail. Used the links for the correct firmware here. Tried Verizon's software assistant... also fails. During flash with Odin, it gets about 3 seconds into the bar that goes across the bottom of the phone, then Odin says failed. I'm on android 7.0 snapdragon.
I can get it into download mode, but flashing fails nearly immediately. In download mode, at the top left it says: "ODIN MODE (HIGH SPEED), PRODUCT NAME: SM-G930V, CURRENT BINARY: Samsung Official, SYSTEM STATUS: Official, FRP LOCK: OFF, QUALCOMM SECUREBOOT: ENABLE, AP SWREV: B4(2,1,1,1,1) K1 S3, SECURE DOWNLOAD: ENABLE
Also, I wrote down the Build # and baseband in case they help... Build #: NRD90M.G930VVRS4BRA1 Baseband: G930VVRS4BRA1
Im sure you experts need additional more specific information, so ask away. And thank you!
Just tried Odin PrinceComsy version and the firmware on the tutorial thread in here for unrooting Verizon Galaxy S7, and failed again. Here's the log:
<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> emmc_appsboot.mbn
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I finally figured it out. Thanks for all your help!

:good: but what was your solution?
edit: I think you didn't get much attention because your title likely turned people off -- it's kind of petty to call attention to someone's background if it's not part of the discussion. I saw you had another post where you didn't do that, and got help, so :good:
chill,
Procrastinatron

What's with the title of your post? We don't need that BS on these forums.

ERDOC76 said:
So I tried to root using an old youtube tutorial
Click to expand...
Click to collapse
You'll be fine man go to sammobile look up your G930V in firmware. You can get your current or update to oreo (no root method for oreo yet) unzip
Make sure you have all samsung drivers and adb uninstall kies maybe reboot your computer and make sure your cable is mtp compatible not just a charging cable. Reboot into download mode flash the BL, AP, CP, and CSC .md5 files in their respective Odin slots. Let recovery do its thing first boot will take some time.
Rooting is even quicker and easier so if you're still confident in yourself look up the methods here on here xda. G930V, G930A, G930T, G930U and G930P pretty much use the same root methods as far as nougat goes.
this is probably the biggest thread all credit to those guys that developed it and shared the files, this is probably the best place to start before you discover safestrap and what mods you can actually do (dual speaker ect.). Rooting, like everything else in life is always at your own risk
https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502

my S7 edge bricked?

Can someone help me with my issue. Im getting error "sw rev. check fail. device: 2, binary: 1" when flashing back to 6.0.1 stock rom.
This is the log from Odin. I accidentally flashed a 7.0 stock firmware and cannot get back to 6.0.1 anymore.
my model SM-G935FD, came from Dubai UAE manufactured in Vietnam.
My phone frequently freezes on samsung logo when booting up and restarts then goes to bootloop.
My phone has also heating on the right front side of the screen when booting up. Is my phone having fried motherboard already?
<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> 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> 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)

U probably updated, bootloader and cp.Flash again 7.0,and then flash twrp,and install custom 6.0.1.

As mentioned, your 7.0 before you tried flashing back to 6.0.1 was with bootloader ending DRA#, that's why you have this error.

MS420 said:
U probably updated, bootloader and cp.Flash again 7.0,and then flash twrp,and install custom 6.0.1.
Click to expand...
Click to collapse
Thank you for the response. yes I wento to 7.0 but I dont like its because 7.0 gives me random freezes. When can i get custom 6.0.1 rom for s7 edge?

Cholek3 said:
As mentioned, your 7.0 before you tried flashing back to 6.0.1 was with bootloader ending DRA#, that's why you have this error.
Click to expand...
Click to collapse
Thank you for the response, Yes I think having an newer version of Bootloader wont let you flash back to the previous version because of that error :

You still can flash back, but you need to use newest bootloader and modem files, where CSC and AP files can be from older firmware. I got back to 6.0.1 that way, although vibration no longer works. It works only on 7.0

Jefjefy88 said:
Thank you for the response. yes I wento to 7.0 but I dont like its because 7.0 gives me random freezes. When can i get custom 6.0.1 rom for s7 edge?
Click to expand...
Click to collapse
Rom section,and watch for older versions.

Cholek3 said:
You still can flash back, but you need to use newest bootloader and modem files, where CSC and AP files can be from older firmware. I got back to 6.0.1 that way, although vibration no longer works. It works only on 7.0
Click to expand...
Click to collapse
My phone wont let me get into the Setup stage, it automatically freezes on Samsung logo whatever official rom I install. Do you think its a hardware issue?

There is a possibility, but you have to flash the newest possible firmware with the CSC version you had before it stopped working (so before first flash).

Galaxy a5 2017 odin fails at cm.bin tried 2 lots fmware

Hi, tried to flash my a5 sm-a520f from 7.0 to 6.0.1 everything seems fine then it fails after cm.bin i've tried using A520FXXU1APLL VOD United Kingdom (Vodafone). and A520FXXU2AQF5 XEU United Kingdom.
I've searched but can't find a definitive answer. Tried as others suggested by changing ports several times and downloaded a second lot of firmware both for my phone and get the same.
Any help please?
Thanks
Below is log from the last time.
<ID:0/006> 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/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> skip file list for home binary
<ID:0/006> param.bin
<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> sboot.bin
<ID:0/006> cm.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.

So no one can help me?
I found out it's the bootloader and found posts about taking all the .bin files out before flashing but that would leave the whole of the BL file out which is like 4gb the bulk of the whole thing. I've tried 5 different UK roms. Tried using CSC instead of home_CSC and that time after sboot.bin in place of cm.bin there's param.bin and no cm. The phone does say odin mode at the top.
Found loads of posts saying because 7 has a different bootloader than 6 it can't be done but many people have done it successfully without a problem. Is there a way to flash it a different bootloader to downgrade to 6.0.1.
I have done a lot of searching about 15 hours worth but can't find the right solution.
I can't get into the phones settings because like a prat i did a factory reset without knowing the password for the email address. Bought the phone, got the login passwords/pattern so was able to use it but it still had sellers gmail and couldn't get in touch with the seller, still can't. Decided to do an frp unlock which i've done many times for people but never on android 7.0. Found out after trying all other methods i had to downgrade which brings me to this problem.
The phone never had/has the the usual startup logos for service providers so i don't know if that means it came without bloatware. I bought it network unlocked, he had it on o2. I've tried stock 6.0.1 firmware for o2, Voda, EE, XEU & BTU.
Please help, already receding don't want to make it worse!
Thanks

Hi. I guess you're on either A520FXXU3 or A520FXXU4 firmware., and that's why you won't be able to downgrade to any lower binary version. Normally it works fine to downgrade without the .bin files as you would still use the updated sboot and baseband ,but with older system files without any problems. All good for daily use, but not for frp reset.
Problem is that it won't help you to bypass frp because you still have the updated binary version.
What you need is a factory combination firmware with the same binary version that you have installed.
That would make it possible to flash it, enable oem unlock to remove the frp protection, then flash a full 4-file firmware with factory reset.

Hi thanks for replying. My firmware version is a520fxxu4brb1. Do you mean the combination file has to hav u4 in its name? Will this one work? A520FXXU4ARA4
Thanks

skg76 said:
Hi thanks for replying. My firmware version is a520fxxu4brb1. Do you mean the combination file has to hav u4 in its name? Will this one work? A520FXXU4ARA4
Thanks
Click to expand...
Click to collapse
Yes, afaik it should work.
Sent from my Moto G5 using Tapatalk

Did you manage to get this working? I can't find any decent links anywhere for the A520FXXU4ARA4 combination file, found one on pakfirmware but md5 was invalid and wouldnt accept in odin..

Sorry mate just seen your message. Yes it did work was a pain though, took a week. I think i found a link on boxwares.
link is here. clicking download leads to a fast google download.
https://shell.boxwares.com/Download.aspx?L=4474
If link is gone just google the combi and look for shell.boxwares link.
Afterwards i just used any u4 stock rom and it worked. Done like 30 phones with this method since.

Odin fail
Help!!
I have the same problem..i've tried everything even turned the anti virus off and nothing works..if i flash a different costum rom would it fix the problem or should i downgrade the firmware to nougat couse last version i had installed was oreo..