Unbrick soft bricked Samsung Galaxy Exhibit 4G (SGH-T679)

Posted on :

This post here is to unbrick soft bricked Samsung Galaxy Exhibit 4G model SGH-T679 only. Don’t try this on any other Galaxy variant. Also this post is only for a soft bricked device not hard bricked (see the difference). This will flash Samsung Galaxy Exhibit 4G to Gingerbread v2.3.

We are not responsible for any data loss or other problems that occur by using this tutorial. Flashing ROM deletes internal memory. Use at your own risk.

Requirements :-

  • 1
    Samsung USB drivers for SGH-T679
  • 2
    Odin and stock Android factory images (uvlg3.odin.zip).
  • 3
    PC with Windows OS on it.

All the downloading links are provided at the end of the post.

Unbrick soft bricked Samsung Galaxy Exhibit 4G (SGH-T679) :-

  • 1
    Download and install Samsung USB drivers, if not already present.
  • 2Unzip the uvlg3.odin.zip on your PC. In there you will find Odin Multi Downloader v4.43.exe, run it as Administrator.
  • 3
    In Odin, make sure that One Package, Auto Reboot, Protect OPS and Reset Time (300 sec) are checked.
  • 4
    Click on OPS button and browse for Ancora.ops file.
  • 5
    Click on One Package button and browse for T679LG3.tar file.odin unbrick soft bricked Samsung Galaxy Exhibit 4G
  • 6
    Switch off and reboot your device into Downloading mode by pressing and holding Volume down + Power button until you see a Warning! screen. Once there, press Volume up to enter into download mode.
  • 7
    Once in download mode, plug-in your device into PC using USB cable. If Odin detects your device, the Message window at the bottom left should read Added!!! and Detected!!!. If Odin doesn’t detects your device then try to reinstall drivers or plug it into a different USB port.
  • 8
    Once everything is ok, press Start button to begin flashing procedure. DON’T UNPLUG YOUR DEVICE WHILE FLASHING IS BEING PERFORMED OTHERWISE YOUR DEVICE WILL BE HARD BRICKED. Flashing process will take a while so have patience.
  • 9
    Once flashing is successfully completed, Odin will show PASS and your device will reboot. First boot is always longest and will take some time. After some time your device will boot into Gingerbread.

Done !! Your device is successfully unbricked now.


The Ancora.ops file is the uvlg3.odin.zip is missing a line 12,preload. Since the download link was from official source, I never thought of this and I apologize for that. So, DON’T USE THE Ancora.ops FILE FROM uvlg3.odin.zip, USE THE FILE FROM SEPARATE DOWNLOAD.

Downloads :

Content Protection by DMCA.com

Get Tips for your device, Free!
No Spam Promise, Your email address is SAFE with us!

Rohan Kandwal

I am an Android Enthusiast and love to learn new techniques, tips and tricks. I also love to help other who face any difficulty in using technical stuff.. Google+

  • riko lobo

    hey i tried to do the things you said to do and everything was ok till rightnow ‘cuase now my device only says samsang and it gets restarted anrestarted and restarted. do you have an answer or solution for it??

    • RohanKandwal

      what do you mean by “everything was ok till rightnow” ? what was your device’s state before following my procedure? Did Odin showed PASS? Have you tried to get in recovery mode and do a cache/data wipe? Most of the bootloops are caused by corrupt caches. So, try wiping cache and data partition. It must boot normally.

    • Alexander Lopez

      Did you ever get this resolved? Was the boot loop occurring before or after you attempted this procedure?

  • Alexander Lopez

    For some odd reason, ODIN shows pass yet after rebooting, it remains on the Samsung Logo. It cannot boot into Recovery, but does boot into download mode. Any suggestions?

    • RohanKandwal

      first boot is always the longest, it might take about 5 min to boot into home screen. Have you waited that long?

      • Alexander Lopez

        Waited more than 20 minutes actually. I know first boot is the longest; the issue happened when downgrading my ROM due to issues with KitKat; (my 5th or 6th ROM on this phone). I got it to go through by downgrading the recovery to CWM recovery for Samsung W, then flashing the recovery for the Exhibit 4G.

        • RohanKandwal

          Why you flashed CWM recovery for Samsung W? You shouldn’t have done that. You might be in a big trouble now. Try flashing a CWM flashable ROM using CWM (Search on XDA). If flashing is successful, then try again follow this procedure.

          • Alexander Lopez

            Wow…you just completely breezed right by the key point there, didn’t you. “I got it to go through by downgrading the recovery.” I FIXED IT!!! Because my brain works I’m not “in big trouble now”. Please refrain from further comments…on any post, if you are not going to read; it only serves to aggravate me.

          • RohanKandwal

            First of all buddy, drop the hate. You aren’t paying me and I don’t even ask for any donations. What I do here is only to help.
            Secondly, if you know anything about Android and flashing then you must know that you must NEVER EVER flash stuff that isn’t made for your device. You flashed a CWM version made for a GSM model.
            Thirdly, what you provided me were breadcrumbs and I tried to help. I didn’t just said that “you’re screwed”, I also provided you a way.
            Fourthly, it’s just my assumption here- that you installed the latest CWM for KitKat, then tried to downgrade it using a CWM for another device and then installed a CWM for your device. The CWM that flashes KitKat, generally, won’t allow downgrading a ROM. Than might be your case but you never explicitly mentioned it (about CWM).

            I don’t know if you are an expert on Android flashing or not. I try to treat everyone a newbie and provide basic solution, which a newbie can understand. Whatever you did to your phone, only you knew it. I am here to help people and I will. I welcome any negative criticism and will try to provide more solutions in one comment.

          • Alexander Lopez

            For your second point; it is incorrect, if a downgraded firmware in order to bypass a frozen boot screen. Also, if a credible developer who has tested and can assure it in fact works, then yes it can be done and is not ill-advised.
            As to your fourth point, once again, my initial post stated I downgraded the recovery so it would go beyond the frozen screen. I downgraded with TWRP, but that is when the issue occurred. To get passed the issue, I flashed the downgraded CWM for Samsung W, (which I stated), then flashed the updated CWM from the recovery. If one gets stuck on the Samsung logo, booting into recovery is impossible, because that is AFTER the logo screen; (which is also the point of riko lobo, the poster below, gets the boot loop at preventing him from booting into recovery). Download mode is still accessible, though, which is why the downgraded CWM was needed.

            As I had mentioned the “hate” was due responding without fully reading and comprehending the post. I see too much of not reading things before offering opinions in the U.S. due to a lack of quality education…and that is annoying. So when someone responds without fully reading or understanding what they’re giving input to, it’s even more so annoying.

          • RohanKandwal

            please various post on what happened when you flash a wrong CWM firmware https://www.google.co.in/search?q=flashed+wrong+clockworkmod+recovery

            These are not my posts, see what happened to many users.

            Who told you that if you are stuck on a bootloop or on manufacturer logo then you ALWAYS can’t access a recovery? See http://forum.xda-developers.com/showthread.php?t=2426426 and also http://xda-university.com/as-a-user/how-to-recover-from-a-bootloop All the steps mentioned to recover from a bootloop asks to go into the recovery.

            Thirdly, this guide here is to unbrick your device not downgrade it. The solution I provided, i.e. flashing a CWM flashable ROM would make your device unbricked. That’s the whole point of this post. My focus was to recover your device, in whatever way possible. Then you can downgrade, upgrade or do whatever you want.

            As far as Mr. riko lobo is concerned, he was in a bootloop, which might occur due to various reasons see http://forum.xda-developers.com/showthread.php?t=1965653 Since he never replied, I couldn’t help him.

            I have provided you with many links, read them carefully and if you still are confused, write another comment. 😉

          • Alexander Lopez

            I’ve already read them, though it appears you are mistaken in the association. In example, the Flashing of the wrong CWM…those people were advised to flash the correct CWM from recovery (which had you paid attention I had to use a downgraded on to get back into recovery…which I had said). They all were still able to access their recovery.

            There is also a major difference between a frozen boot screen and a boot loop. Frozen boot remains stuck on Samsung, which a person has to get passed to be able to get into the recovery. There is a difference between recovery and download mode. If you worked with enough Android phones, you’d know this.

            Lastly, I said (and am saying again) I FIXED it. So I have no questions. You had begun the whole back and fourth with your assumption that flashing a CWM that will allow a person back into recovery is always a negative. The only negative from flashing it to a Galaxy Exhibit 4G was having to figure the alternate buttons. (When doing so, the search button is now the one to select, but otherwise the other recovery allowed flashing the updated one and booting into the updated recovery from the Samsung W recovery.)

            So… if YOU have any questions on how to actually get things done, feel free to post. Otherwise, stop offering links that are not relevant.

          • RohanKandwal

            Mr. Alexander my point was to tell you what happens when you flash a wrong version of CWM (not particularly your case). Sometimes device might not even get in download or recovery mode see http://forum.xda-developers.com/showthread.php?t=2506754 and the only solution remains is a JIG.

            Didn’t I say “bootloop or on manufacturer logo” ? and FYI Samsung is a manufacturer. Where I said “flashing a CWM that will allow a person back into recovery”? I said that flashing a CWM flashable ROM will unbrick your device, which it will.

            I am glad you fixed your device, I really am. But please don’t think that the other person is a fool. I develop Android apps for living and recently completed creation of my very own custom ROM. So, I know what I am talking about.

            The reason that I replied to your comments was to have a constructive debate. Seeing that its no longer possible, I am ending this debate. Once again, congrats that you unbricked your device and best of wishes for your future.

  • Jason

    How long should the flashing procedure take? It’s been going on 50 minutes. It says it will take “a while”, but is this normal?

    • RohanKandwal

      That’s way too much. It should take 10-15 minutes at the most.

  • Gary Kitchen

    Went through all instructions, Odin sees phone (T Mo SGH-T679), but never performs the MD5 check. If I press start, the process fails w/abort messages

    • RohanKandwal

      MD5 mismatch means that the file that you downloaded is corrupt. Please download the file once again.

      • Gary Kitchen

        Not a mismatch, the MD5 check is never performed, not getting any result, even though the phone is seen by Odin

        • RohanKandwal

          Personally, I have never seen Odin behave like that. Make sure that Kies isn’t running in the background. I see think that you made a post on sammobile too, anyways can you send a Odin’s log (Message box text).

          • Gary Kitchen

            I will try again this evening and copy the log result

          • RohanKandwal

            Hi Gary, before you retry the procedure, make sure that you are using the new Ancora.ops file.

  • Roberto Rojas

    I have no recovery mode, only Downloading…. I have done the steps as you instructed, the Odin pass and completes, but when its time to reboot, nothing happends, it’s still black screen, no sighns of booting up.

  • Nikhil George

    Just don’t work…Odin showed Passed but still it’s stuck at booting screen showing Samsung..!!

    • RohanKandwal

      Tried cleaning caches and wiping partitions?

  • Akesi Cave

    Hey. I have a Galaxy Exhibit (t599n). The phone fell on its side a while ago and few days after that the Wi-Fi stopped enabling. Whenever i try to enable it it just shows that it’s enabling then automatically disables. I havent been able to connect to any Wi-Fi since then. I should also mention that exactly before the Wi-Fi stopped enabling, i used an application called “Wi-Fi Recovery Manager” that requires root permissions to Restore my Wi-Fi networks immediately after which the Wi-Fi disabled and did not enable again. Please Help!!

    • RohanKandwal

      Was your device able to discover WiFi? If it isn’t a hardware issue then you can try reinstalling the ROM.

  • Jonny

    Thank You so much! At first my phone would stay on the samsung logo then to “Samung exibit 4g” and it wouldnt go past that. So i decided to go to the recovery and wipe the data and that fixed it!

    • RohanKandwal

      Glad to be of help buddy. please share this site so others will benefit from it.

  • Edcel L. Anzures

    thanks, my first time to connect a cellphone to a PC hoping to unbrick my nephew’s

    sgh-T679. I just follow the step by step procedure on the topic.

    ” Unbrick soft bricked Samsung Galaxy Exhibit 4G (SGH-T679)”. To my surprised it


    thanks guys