Database Info

Phone bricked itself and having issues recovering

Thanks in advance for any help you guys can provide. This one has me stumped.
First, I have never rooted my wife's device.
The other day it rebooted randomly and would never make it past the t-mobile splash screen. I figured since it wouldn't boot I would try clearing the cache within the bootloader. That made matters worse.
Finally, I did a factory reset to try and fix the problem and now the phone is telling me that there was a problem applying an update and I must use Smart Switch.
Well, when I tried using smart switch it get right to the very end and fails saying the it is FRP locked and no custom software can be installed. I read through some threads and tried using Odin to flash the device using the latest firmware version. Same error with FRP lock. At this point my phone wont boot and I can only get to the bootloader, or to the download screen.
Any suggestions on what I should do next? My KNOX is still at 0, but my software version reads custom for some reason, even though I didn't try to flash anything.

Have you tried using Kies recovery?

blah_blah_blah_blah said:
Have you tried using Kies recovery?
Click to expand...
Click to collapse
Yes, gives the same error as Odin and Smart Switch.
As another note when i enter the bootloader menu it says that it is unable to mount /system so it's as though it got corrupted some how. But I can't flash stock firmware to fix it due to the FRP lock.

Droid_phreek said:
Yes, gives the same error as Odin and Smart Switch.
As another note when i enter the bootloader menu it says that it is unable to mount /system so it's as though it got corrupted some how. But I can't flash stock firmware to fix it due to the FRP lock.
Click to expand...
Click to collapse
Just to make sure you use kies and emergency restore rite? You enter the phones serial number?

blah_blah_blah_blah said:
Just to make sure you use kies and emergency restore rite? You enter the phones serial number?
Click to expand...
Click to collapse
I did. It gets to the very end and then give me the FRP error. I could clear the FRP error if the stupid thing would boot to the OS so I could login.

Do you have tmobile ? And if so do you have insurance on it ?

Sounds like you should exchange. The only other thing to try is root the hell out of it.
---------- Post added at 09:51 PM ---------- Previous post was at 09:48 PM ----------
Mines had a tough life, but I brought it back to life after erasing everything in recovery. New, recovery first then the operating system. Yours could be broken, but you wouldn't know till you tripped knox. Not that t-mobile seems to care.

[GUIDE] How to fix IMEI / DRK issues

This Guide works on both the S7 and S7 Edge.
This also works on other Samsung device including Snapdragon variants as long as you have the correct files for your device.
FIll out my form if you require assistance
S8 users go HERE
​This guide is for those of you with EFS issues. This can cause your IMEI and/or Baseband to show Unknown or a bunch of zeros. The guide can also be used to fix DRK errors, but if your Device Root Key (DRK) is corrupt or missing, this guide will fix your IMEI/Baseband but will not fix your DRK error.
The guide gives instructions on how to flash the combination firmware. This installs the factory binary which allows your phone to read your IMEI and DRK. This should then restore your IMEI and DRK and then when you flash stock, the phone will be working as normal. If the Device Root Key (DRK) is corrupt or missing, this guide will only fix the IMEI, the DRK errors will still remain.
I take no responsibility for any issues that arise from following this guide. Do so at your own risk. The smallest mistake can cause a much bigger issue so make sure you know what you are doing and follow every step word for word!​
Please note that this will not work for everyone
Some people will still face getting stuck at boot when flashing the combination firmware.
This means you have at some point flashed firmware that is later than the latest combination firmware and unfortunately, it is not possible to fix this by downgrading the firmware to an earlier version.​
Before you proceed, you're going to need the following:
A copy of your phones stock firmware saved to your computer. If you do not already have these available on your computer, you can go HERE or you can use this tool to download the latest firmware for your device. Alternatively, you can find your firmware on SamMobile but this can take forever to download with a free account.
[IMPORTANT!] Switch off Factory Reset Protection (FRP) by going into Developer options and turning on 'OEM Unlock'. If you do not see 'Developer Options' under settings, then go to Settings > About Device > Software Info and keep tapping 'Build Number' until it confirms "You are now a developer" then go back to the main Settings screen and you will see Developer options.
if you skip this step, you only have yourself to blame if something goes wrong.
Odin. If you do not have it, download it from here
The Combination Firmware (Factory Binary). Download the combination firmware relevant to your phone (links below) and extract the .rar archive somewhere you will remember.
S7 International [G930F/FD] - (Mirror) [UPDATED 03/11/2017]
S7 Edge International [G935F/FD] - (Mirror) [UPDATED 03/11/2017]
S7 Canada [G930W8] - (Mirror)
S7 Edge Canada [G935W8] - (Mirror)
S7 Edge AT&T [G935A] - (Mirror)
Files for other models available on request via my form
​
Now you have all the files you need, follow the guide below to repair your S7.
There are 2 methods.
The first method (Method 1) is quick and can solve most issues. Especially DRK errors.
The second method (Method 2) is to use if Method 1 does not work. This guide requires more work and therefore takes a little longer.
Method 1
Boot into recovery and wipe data.
Put your phone straight into Download Mode (do not reboot or boot up the system between wiping data and booting to download mode). To do this, you can use recovery to reboot to Download mode. Alternatively, switch off your phone and hold 'Power' + 'Volume Down' + 'Home' until it boots to download mode. Then connect the phone to your computer with your USB cable.
Open Odin, press the 'AP' button and select the Combination tar/md5 file you downloaded/extracted earlier. Then press the 'Start' button. (If you have any errors while flashing, first make sure you are using the correct firmware for your phone. If it is still throwing errors, remove the ".md5" from the end of the file name and try again).
When Odin has completed flashing the combination file, it should boot into the Factory Binary. You may get a message asking you to reboot. Click reboot (If you do not get prompted to reboot, do a reboot manually).
When it has booted back up. Press the 'IME' button at the bottom of the screen and type *#06#. You should now see your IMEI has restored.
Now restore the stock firmware using the firmware you downloaded earlier. (If you're not sure how, follow this guide)
You should now have a restored IMEI. If not, this means your efs is damaged. Therefore, you will need to follow Method 2 below.
Method 2
You will need to start on a rooted device. If you are not rooted, follow this guide to root your phone or flash CF Auto Root in Odin.
Before you continue, it is extremely important that you backup your EFS partition, even if it is corrupt. You can backup the EFS partition using THIS APP. If you skip this step, you only have yourself to blame if something goes wrong and you have no backup to restore.
Download Root Explorer (Paid) or Root Browser (Free). Open 'Root Explorer' or 'Root Browser' (whichever you installed) and browse to the /efs folder located in the root of the device.
Inside the /efs folder, delete everything EXCEPT the 'FactoryApp' and 'prov_data' folders.
Reboot. Make sure it does a full reboot. When the phone boots back up, you may some errors or unusual settings, this is normal and nothing to worry about.
Boot into recovery and wipe data.
Put your phone straight into Download Mode (do not reboot or boot up the system between wiping data and booting to download mode). To do this, you can use recovery to reboot to Download mode. Alternatively, switch off your phone and hold 'Power' + 'Volume Down' + 'Home' until it boots to download mode. Then connect the phone to your computer with your USB cable.
Open Odin, press the 'AP' button and select the Combination tar/md5 file you downloaded/extracted earlier. Then press the 'Start' button. (If you have any errors while flashing, first make sure you are using the correct firmware for your phone. If it is still throwing errors, remove the ".md5" from the end of the file name and try again).
When Odin has completed flashing the combination file, it should boot into the Factory Binary. You may get a message asking you to reboot. Click reboot (If you do not get prompted to reboot, do a reboot manually).
When it has booted back up. Press the 'IME' button at the bottom of the screen and type *#06#. You should now see your IMEI has restored.
Now restore the stock firmware using the firmware you downloaded earlier. (If you're not sure how, follow this guide)
You should now have a restored IMEI.
​
Still Getting a DRK error?
If you are still getting a DRK error then you probably have a corrupt or missing Device Root Key (DRK). Unfortunately, this cannot be fixed without a JTag box (which aren't cheap). However, you can continue to use the phone as normal by flashing the no-verity zip in TWRP. You can then go ahead and use your phone as normal. Unfortunately, you will no longer be able to receive OTA updates. All updates will need to be made through ODIN and the no verity zip will need to be flashed every time a new firmware is flashed. However, you can still use custom roms as normal. Other than OTA updates, the DRK issue will have no effect on the use of the phone. You can still update via Smart Switch but will need to install TWRP and flash the no verity zip after every update.
If you would like any assistance in fixing your issue such as Method 1 & 2 do not work for you or if you have a different model than what is listed in this guide, please complete THIS FORM and I will try to get back to you ASAP (unfortunately I cannot always respond)
Many thanks to everyone that has donated!!
If you would like to donate, you can do so by clicking here
As you can imagine, finding fixes and assisting people takes a lot of my time so it's always great to receive a donation. Thank you.
​

Goooooooooooooooood,tnx

Very well detailed and clear guide bro. Thanks for posting this.
Tapped on my Echoe'd out G935F

Very good guide. Cubz helped me get my IMEI back so he knows his stuff. Thanks again.
Sent from my SM-G935F using XDA-Developers mobile app

ecera said:
Very good guide. Cubz helped me get my IMEI back so he knows his stuff. Thanks again.
Sent from my SM-G935F using XDA-Developers mobile app
Click to expand...
Click to collapse
No problem. Was happy to help

What else can this factory binary do? Can it restore the original CSC? I had an AFG CSC phone and after playing around with different roms, when I go back to the original firmware (although it is a multi CSC), it chooses XSG rather than AFG no matter what I do.

onurd said:
What else can this factory binary do? Can it restore the original CSC? I had an AFG CSC phone and after playing around with different roms, when I go back to the original firmware (although it is a multi CSC), it chooses XSG rather than AFG no matter what I do.
Click to expand...
Click to collapse
No it doesn't. Where are you seeing the CSC?
Sent from my SM-G935F using Tapatalk

CuBz90 said:
No it doesn't. Where are you seeing the CSC?
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
I haven't seen CSC. anywhere. I was just wondering what this firmware had up its sleeves to "fix" things.

onurd said:
I haven't seen CSC. anywhere. I was just wondering what this firmware had up its sleeves to "fix" things.
Click to expand...
Click to collapse
What I meant is that when you say you now have a different CSC, how did you know this.
This firmware basically just feels the phone where to read the imei, baseband, and other info. This does not include the CSC.
PM me for my email address and then if you email me a backup of your EFS, I will have a look and restore your CSC for you.
Sent from my SM-G935F using Tapatalk

The original firmware of the phone was AFG for csc. Now even after using odin to get the same firmware, it defaults to xsg. Not a big deal but I don't know where the csc information is stored.
Sent from my SM-G935F using XDA Premium 4 mobile app

That's what I mean by the original csc having disappeared.

sent a PM about getting an EFS file, I hope you get it

onurd said:
That's what I mean by the original csc having disappeared.
Click to expand...
Click to collapse
Read this
Code:
http://forum.xda-developers.com/showpost.php?p=49425630&postcount=3

hiepgia said:
Read this
Code:
http://forum.xda-developers.com/showpost.php?p=49425630&postcount=3
Click to expand...
Click to collapse
I see. Phone info won't show the original csc without root.
But how do you explain that despite using the appropriate firmware with odin, it always defaults to xsg rather than the original afg from the multi csc firmware?

Hey so I tried flashing the G935_Factory_Binary.tar file on a galaxy s7 edge, and the thing is stuck on splash screen. any idea why?

onurd said:
I see. Phone info won't show the original csc without root.
But how do you explain that despite using the appropriate firmware with odin, it always defaults to xsg rather than the original afg from the multi csc firmware?
Click to expand...
Click to collapse
Because you flashed another region firmware, wipe data -> All original csc will get remove. You flash back and will only get default csc. If you rooted, you can change to afg csc

Thank you CuBz90 for your great work.
I flashed the superman rom but selected the wrong CSC.
I always backup my EFS in internal storage, but today I accidently wiped my entire internal storage. LOL
I have tried your method but unfortunately my imei is still missing, I'm totally frustrating. I will follow your thread. hope some expert can figure this out.

To everyone that has PM'd me, please bare with me. I have received a hell of a lot of PM's and I am trying to get through them all. Don't worry, I will definately reply and help you as best as I can.
Please make sure you are on your original stock firmware before trying this method. I notice a lot of people have PM'ed about CSC, I will PM you with info on how to revert this but please follow my steps exactly how I write them, a lot of people have PM'ed me to say "it's not working" but I have later found they are not following my steps exactly how I say and instead are taking shortcuts. If you take shortcuts then it's not going to work. I want to help you but you need to follow my exact instructions.

How to backup Efs without root?
Wanam app only works with root.
Sent from my SM-G935F using XDA-Developers mobile app

Help me?
Who can tell me efs file? Thank
Gửi từ SM-G930F của tôi bằng cách sử dụng Tapatalk

Tried to root, failed, total noon here.

Hey guys, today I tried to root my t-mobile s7 from a random YouTube video I found. After flashing a file from Odin, my phone got stuck in a boot loop.
I did a factory reset from recovery and the phone started up fine.
Now here's my problem, after doing a reset, the first thing I noticed was that while I was booting up the phone. It showed the usual Samsung Galaxy S7, followed by an unlocked padlock with the words "Custom" under it.
2nd issue. My phone just looks a lot different than when I originally bought it. It is also very sluggish, experiencing a lot of lag.
I've looked up how to go back to stock firmware but I'm not sure which one to use.
Any help would be appreciated.
I'm currently on the PG1 firmware.

It appears you still have the eng kernal... You can just re-run the root.bat and install SuperSu, or if you want complete stock follow the steps below:
*Also Before you try this turn it off and let it charge for 45 min-1 hour or so...*
1. Volume Down + Power + Home to put it in download mode
2. Then press Volume Up to continue past the warning screen even if nothing is displayed.
3. Grab The Latest Version of Odin here
4. Then Download The Stock Firmware, in this case you will need whichever version you have (if you do not remember you can just download the latest available firmware) Download Firmware and then extract it. (If you have 5 different files in the zip go to step 8)
5. Then install Samsung device drivers(if not already).
6. Start Odin, Plug in the S7, Load in the tar.md5 in the AP/PDA and uncheck Auto Reboot and Repartition.
7. Let the phone restart... VIOLA!!!
8. Alternatively if the zip has 5 files... They should all start with the corresponding buttons in Odin For Example:
AP_G930TUVS3APD8_CL7856276_QB9546176_REV02_user_low_ship_MULTI_CERT.tar.md5
BL_G930TUVS3APD8_CL7856276_QB9546176_REV02_user_low_ship_MULTI_CERT.tar.md5
CP_G930TUVS3APD8_CL7856276_QB9546176_REV02_user_low_ship_MULTI_CERT.tar.md5
CSC_TMB_G930TTMB3APD8_CL7856276_QB9546176_REV02_user_low_ship_MULTI_CERT.tar.md5
HOME_CSC_TMB_G930TTMB3APD8_CL7856276_QB9546176_REV02_user_low_ship_MULTI_CERT.tar.md5
After they are entered into Odin you hit start and after a few minutes ... It should be fixed....
Let me know if you have any further questions or issues...

The custom is normal since you flashed a modified kernel.
Follow this instructions here for rooting / unrooting.
Most of these applies to Tmobile S7, expect specific ones mentioned for Verizon.
http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039

Thanks man, I'm gonna try to finish rooting. I thought my phone was just screwing up and the first part of the rooting process failed, since the bootloader.
I also tried sammobile and the download won't start.
If I were to download an earlier firmware, would I be able to update it to the most recent one?

Is it possible to revert to stock without wiping data?

Can I flash a custom kernel with flashfire?
Sent from my SM-G930T using XDA-Developers mobile app

xda23 said:
Can I flash a custom kernel with flashfire?
Click to expand...
Click to collapse
No you cannot. Or rather, science threw bootloader is still locked, your phone will not boot if you try.

KillerClaw321 said:
It appears you still have the eng kernal... You can just re-run the root.bat and install SuperSu, or if you want complete stock follow the steps below:
*Also Before you try this turn it off and let it charge for 45 min-1 hour or so...*
1. Volume Down + Power + Home to put it in download mode
2. Then press Volume Up to continue past the warning screen even if nothing is displayed.
3. Grab The Latest Version of Odin here
4. Then Download The Stock Firmware, in this case you will need whichever version you have (if you do not remember you can just download the latest available firmware) Download Firmware and then extract it. (If you have 5 different files in the zip go to step 8)
5. Then install Samsung device drivers(if not already).
6. Start Odin, Plug in the S7, Load in the tar.md5 in the AP/PDA and uncheck Auto Reboot and Repartition.
7. Let the phone restart... VIOLA!!!
8. Alternatively if the zip has 5 files... They should all start with the corresponding buttons in Odin For Example:
AP_G930TUVS3APD8_CL7856276_QB9546176_REV02_user_low_ship_MULTI_CERT.tar.md5
BL_G930TUVS3APD8_CL7856276_QB9546176_REV02_user_low_ship_MULTI_CERT.tar.md5
CP_G930TUVS3APD8_CL7856276_QB9546176_REV02_user_low_ship_MULTI_CERT.tar.md5
CSC_TMB_G930TTMB3APD8_CL7856276_QB9546176_REV02_user_low_ship_MULTI_CERT.tar.md5
HOME_CSC_TMB_G930TTMB3APD8_CL7856276_QB9546176_REV02_user_low_ship_MULTI_CERT.tar.md5
After they are entered into Odin you hit start and after a few minutes ... It should be fixed....
Let me know if you have any further questions or issues...
Click to expand...
Click to collapse
New to samsung here, quick question. I soft bricked with an xposed app and have to restore.
What is the difference between the csc and the home csc files and which is the correct one. I don't see a home tab in odin
Sorry for the noob question, My first Samsung device

kc6wke said:
New to samsung here, quick question. I soft bricked with an xposed app and have to restore.
What is the difference between the csc and the home csc files and which is the correct one. I don't see a home tab in odin
Sorry for the noob question, My first Samsung device
Click to expand...
Click to collapse
You can just use CSC and not the CSC Home.

Quick question, I bought a used s7 edge off Craigslist and when it's asking me to log in with another guys email. I tried contacting the guy I bought it from but he hasn't texted me back yet. Can I root it and install another rom on it to bypass the lollipop lock? Thanks guys.

Palatis3 said:
Quick question, I bought a used s7 edge off Craigslist and when it's asking me to log in with another guys email. I tried contacting the guy I bought it from but he hasn't texted me back yet. Can I root it and install another rom on it to bypass the lollipop lock? Thanks guys.
Click to expand...
Click to collapse
I don't know if this will work, but try this:
---------- Post added at 02:09 AM ---------- Previous post was at 02:07 AM ----------
Palatis3 said:
Quick question, I bought a used s7 edge off Craigslist and when it's asking me to log in with another guys email. I tried contacting the guy I bought it from but he hasn't texted me back yet. Can I root it and install another rom on it to bypass the lollipop lock? Thanks guys.
Click to expand...
Click to collapse
Wait did you try rooting the s7 or s7 edge... (Or is the s7 edge completely unrelated to the brick)

Trying to unroot a Galaxy S6...losing the will to live :(

Can anyone help? I spent a big chunk of my hard earned money on a refurbed S6 for my daughter, she's had it about a week (she's Pokemon mad btw). The latest update for Pokemon Go came out and now she's blocked from the game as it appears the phone has been rooted. If I'd known, I wouldn't have bought it. Anyway, for the last 2 days my partner and I have been trying to unroot it. We've used various versions of Odin to no avail. I had a lot of trouble finding the right firmware because it looks like the phone was Polish according to the version and CSC numbers, and tbh I'm still not sure if we're trying the right one. Software is 5.1.1. right now. I've tried installing SuperSU but it won't run, it just crashes the phone and forces a reboot. We've tried manually unrooting with a file manager but the su files we need to delete reappear seconds after they're deleted. I'm at the end of my tether, does anyone have any ideas?

You won't be able to unroot it until you flash stock firmware. I don't know if the game checks the knox status.
Give this a go
http://www.androidpolice.com/2016/09/11/guide-play-pokemon-go-0-37-rooted-android-magisk/
Enjoy

Unforunately my partner spent almost all night trying to flash the firmware. According to him it 'nearly' worked, however, I now have a phone stuck in a boot loop. :crying:

Run emergency recovery on Smart switch

ccalixtro said:
Run emergency recovery on Smart switch
Click to expand...
Click to collapse
Do I need to have smart switch installed on the phone for this to work?

amber_1978 said:
Do I need to have smart switch installed on the phone for this to work?
Click to expand...
Click to collapse
No, run it on your pc.

Thanks, I'll give it a go after work.

ccalixtro said:
No, run it on your pc.
Click to expand...
Click to collapse
Smart switch won't work, says it doesn't recognise the device

I think I would give original firmware of your country and odin a try. One of possible ways is to download all needed files from the site of sammobile.
For me this way works every time when I stuck in boot loop. Odin functionates when you are in download mode. Switch off your s6, then start by pressing home-, powerbutton and Volume down at the same time.
Then start Odin on PC, then connect USB and so on.
Greetz JG

amber_1978 said:
Smart switch won't work, says it doesn't recognise the device
Click to expand...
Click to collapse
When you select emergency recovery theres an option where you have to write the device model and the serial number

Use kies 3 on your computer. When you get it do a "firmware upgrade and installation" it will ask for your serial number which you can get from download mode when pressing the home key. After that kies 3 will ask to boot your phone to recovery but instead boot to download and bow your phone will flash to stock. This method always work!!

fahad999 said:
Use kies 3 on your computer. When you get it do a "firmware upgrade and installation" it will ask for your serial number which you can get from download mode when pressing the home key. After that kies 3 will ask to boot your phone to recovery but instead boot to download and bow your phone will flash to stock. This method always work!!
Click to expand...
Click to collapse
Thanks for the reply. Unfortunately I've tried Kies already and I can't get it to work at all. I get a message telling me my device is not compatible and the whole thing just stops. I'll give it another go though, no harm in trying. Thanks

@amber_1978, Pokemon Go does not check for root. The only thing it does seem to check for is location spoofing via another app. I'm using it on a rooted, Knox tripped, Xposed installed phone with no issues.
If you want to return the phone back to stock, the best way IMO would be to use Odin to flash a stock image, such as the EPD1 firmware.

socal87 said:
@amber_1978, Pokemon Go does not check for root. The only thing it does seem to check for is location spoofing via another app. I'm using it on a rooted, Knox tripped, Xposed installed phone with no issues.
If you want to return the phone back to stock, the best way IMO would be to use Odin to flash a stock image, such as the EPD1 firmware.
Click to expand...
Click to collapse
Really? Did you do the latest update in the game and it still worked ok? This phone has definitley not been used for location spoofing by us and I'm pretty sure there were no apps of that nature on the phone. I downloaded a root checker when everything went wrong the other day, it said the phone was rooted. I'm totally at a loss tbh. Right now it's still in a boot loop. Trying to flash it with Odin as we speak.

Just an update. Tried Smart Switch. Tried the model and serial numbers on the back of the phone case, these weren't recognised so I went to the recovery screen and hit the home button and got a completely different set of numbers. Different IMEI, model number, you name it. I'm assuming this is why Odin won't work, I'm looking for the wrong firmware? I obviously have Frankenstein's phone. No idea what to do now.

Best thing to do is to flash TWRPP and try to flash a custom stock rom through the TWRP recovery which does not have root installed..... If that doesn't work try to find a generic stock firmware for Odin, meaning a firmware that can run in any country..... If all else fails update it to 6.0.1 stock firmware. Try the closest firmwares to your location.
And if you do manage to get to the Samsung logo let the phone sit there for a good 10 minutes even if it reboots....
When I bricked my Samsung I used masiks custom 6.0.1 rom based on stock, but had all the links to bootloaders cscs radios and what not so giv that a shot if you can find it.
---------- Post added at 12:08 AM ---------- Previous post was at 12:05 AM ----------
Link to rom that helped me http://forum.xda-developers.com/galaxy-s6/development/masik-marshmallow-1-0-jan-20-2016-t3297961

do you have lucky patcher playstore installed ?

ODIN Fails Every Time

Hi,
So I was trying to root my phone and it all went wrong. I have rooted tons of phones before, but never a Samsung (never again).
The phone will show the Samsung Boot screen, but then it either goes black, with a flashing blue LED, or it boots itself into recovery.
When I use ODIN, the flash fails at "system.img.ext4" whenever I use just the AP field. If I load all the fields in, it fails at "xbl.elf"
I got the firmware file from SamMobile, so I don't think that is the issue, but who knows. It's as if the phone no longer has an OS on it. I also tried using SmartSwitch as well, but I have no idea what the S/N on this phone is. It was originally a Sprint phone and was working fine, but I could never find the S/N. It is nowhere on the phone itself, and was not listed when I typed #*06#. All I have is the IMEI.
Finally, when it is in recovery, there is a message at the bottom that reads, "dm-verity verification failed".
Sorry for the bullet point style here, I am on mobile. If anyone can assist, I would be very grateful!

ebercon said:
Hi,
So I was trying to root my phone and it all went wrong. I have rooted tons of phones before, but never a Samsung (never again).
The phone will show the Samsung Boot screen, but then it either goes black, with a flashing blue LED, or it boots itself into recovery.
When I use ODIN, the flash fails at "system.img.ext4" whenever I use just the AP field. If I load all the fields in, it fails at "xbl.elf"
I got the firmware file from SamMobile, so I don't think that is the issue, but who knows. It's as if the phone no longer has an OS on it. I also tried using SmartSwitch as well, but I have no idea what the S/N on this phone is. It was originally a Sprint phone and was working fine, but I could never find the S/N. It is nowhere on the phone itself, and was not listed when I typed #*06#. All I have is the IMEI.
Finally, when it is in recovery, there is a message at the bottom that reads, "dm-verity verification failed".
Sorry for the bullet point style here, I am on mobile. If anyone can assist, I would be very grateful!
Click to expand...
Click to collapse
I'm new to the s7. long time lg man
on lg ussally means either ure trying to flash a non signed image or downgrade a qfused bootloader anti rollback which sprint is good for.
in dl mode after fail its not showing anything about binary and stuff in red is it

TheMadScientist420 said:
I'm new to the s7. long time lg man
on lg ussally means either ure trying to flash a non signed image or downgrade a qfused bootloader anti rollback which sprint is good for.
in dl mode after fail its not showing anything about binary and stuff in red is it
Click to expand...
Click to collapse
It does say something about binary in there. Binary 3 I believe. I'll have to try again to get the error.

ebercon said:
It does say something about binary in there. Binary 3 I believe. I'll have to try again to get the error.
Click to expand...
Click to collapse
sounds the firmware u are flashing is older than what you have on the device hence the fail
try to find newer firmware and try flashing it

download
Download official nougat from sam mobile then flash with Odin. It will definitely solve your problem

amol6630 said:
Download official nougat from sam mobile then flash with Odin. It will definitely solve your problem
Click to expand...
Click to collapse
I may try this as well. I flashed the newest firmware I could find other than Nougat and I now have it booting all the way up and then after about a minute, it loops again. It is at least further along than before.
I just remembered one detail: The original issue began when I flashed a modified boot.img to the phone during a rooting attempt. Could this be what is still causing the issue and preventing a reformatting of the phone from solving the issue? So lost with this thing...

Try with latest firmware + pit file + tick re-partition

ebercon said:
I may try this as well. I flashed the newest firmware I could find other than Nougat and I now have it booting all the way up and then after about a minute, it loops again. It is at least further along than before.
I just remembered one detail: The original issue began when I flashed a modified boot.img to the phone during a rooting attempt. Could this be what is still causing the issue and preventing a reformatting of the phone from solving the issue? So lost with this thing...
Click to expand...
Click to collapse
Sorry to revive this thread but did this work cause its currently happening to me

If your phone is an original, S/N may be engraved in the back... it's a little bit hard to note but put a spotlight near it so that you can identify it better.
hhh ^^