Database Users

Seriously NEED HELP (S4 Bricked) !!!!!!

i have a verizon s4. i tried to install custom rom in it now i am stuck at this screen which says " downloading.." "do not turn off target"
i tried every version of odin and multiple roms to flash but it says " SW RV. CHECK FAIL : FUSED 5 : BINARY 1"
WHAT ???? IS THAT ??

You might probably have flashed the wrong firmware for your device or Downgraded to older version. I am Attaching a link here please go through it carefully and try recovering your phone with care.
http://forum.xda-developers.com/showthread.php?t=2511880
This is for Note 3 but you can follow the same for yours, download the stock and latest available firmware (KITKAT 4.4.2) for your phone and flash via odin.

tune345 said:
i have a verizon s4. i tried to install custom rom in it now i am stuck at this screen which says " downloading.." "do not turn off target"
i tried every version of odin and multiple roms to flash but it says " SW RV. CHECK FAIL : FUSED 5 : BINARY 1"
WHAT ???? IS THAT ??
Click to expand...
Click to collapse
You are at the wrong forum. This is not for the verizon s4. Go there for anwsers.
Probably you just need to reflash stock firmware or something.

Aamirx12 said:
You might probably have flashed the wrong firmware for your device or Downgraded to older version. I am Attaching a link here please go through it carefully and try recovering your phone with care.
http://forum.xda-developers.com/showthread.php?t=2511880
This is for Note 3 but you can follow the same for yours, download the stock and latest available firmware (KITKAT 4.4.2) for your phone and flash via odin.
Click to expand...
Click to collapse
secure check fail sbl1

tune345 said:
secure check fail sbl1
Click to expand...
Click to collapse
what you did this time, please post in detail.
Get your official firmware from http://www.sammobile.com/firmwares/
register there, then download the firmware for your phone( Please check beneath your battery the proper info about your phone and download the same for your phone)

Aamirx12 said:
what you did this time, please post in detail.
Get your official firmware from http://www.sammobile.com/firmwares/
register there, then download the firmware for your phone( Please check beneath your battery the proper info about your phone and download the same for your phone)
Click to expand...
Click to collapse
i am downloading the firmware from sammobile it was showing me 3 hours to download so i download the same file from a different location , that might be a problem i guess.
but i used odin 3.07 and 3.04
it is showing me the same error
i am about to tried the official rom in a few minutes from the sammobile.

flash the appropriate one.. and reply after flashing

ok so after trying the rom from sammobile it's showing me the same error.
i am attaching pictures for details , please help !!! .... am goingggggg nutssss !!:crying:
took off from work just to do this lol

tune345 said:
ok so after trying the rom from sammobile it's showing me the same error.
i am attaching pictures for details , please help !!! .... am goingggggg nutssss !!:crying:
took off from work just to do this lol
Click to expand...
Click to collapse
Which ROM you were using before all this happened

tune345 said:
ok so after trying the rom from sammobile it's showing me the same error.
i am attaching pictures for details , please help !!! .... am goingggggg nutssss !!:crying:
took off from work just to do this lol
Click to expand...
Click to collapse
You should go to the forum for you device. This forum is NOT for you device.
http://forum.xda-developers.com/sitesearch.php?q=SW REV. CHECK FAIL
And because you posted little usefull information in this topic it's hard to help.

Aamirx12 said:
Which ROM you were using before all this happened
Click to expand...
Click to collapse
i was using the stock ROM when i tried to install cyanogen few months back but the processed did not go through successfully so now when i start the phone i get the samsung custom logo.
so i was using that for months now because it did let me go thru normally even though the process of installing cyanogen didn't completed. So i think i messed up some internal files.
but phone was working good and everything until when i wanted to factory reset , it goes into odin mode and then gives me that error no matter
what version or Stock rom i use

Mod Edit
Please post in your variant's forum:
http://forum.xda-developers.com/forumdisplay.php?f=2314
Thread closed
malybru
Forum Moderator

[Q] Help needed bricked my SM-N900

So today I was trying to update my phone to a newer version of 4.4.2 I downloaded N900ZSUDNG1_N900OZSDNG1_BRI also Odin v3.09, Odin detects my phone perfectly but flashing fails every time i tried 4 different USB ports and same thing at the end of flashing it says FAILED but i see no error on the log it goes all the way to where it writes CACHE it seems and then says FAILED any ideas as to what to do to recover my phone would be appreciated.

Hey good morning,
I would suggest you to flash root (knox will be flagged 0x1)
Then flash cwm (or any recovery you like)
Put a nice ROM in your SD card (use another device or a card reader for pc)
Boot into recovery, wipe all data and flash the rom.
(* the steps above WILL void your warranty)

bligui said:
So today I was trying to update my phone to a newer version of 4.4.2 I downloaded N900ZSUDNG1_N900OZSDNG1_BRI also Odin v3.09, Odin detects my phone perfectly but flashing fails every time i tried 4 different USB ports and same thing at the end of flashing it says FAILED but i see no error on the log it goes all the way to where it writes CACHE it seems and then says FAILED any ideas as to what to do to recover my phone would be appreciated.
Click to expand...
Click to collapse
Download again may what u download is corrupted.

bligui said:
So today I was trying to update my phone to a newer version of 4.4.2 I downloaded N900ZSUDNG1_N900OZSDNG1_BRI also Odin v3.09, Odin detects my phone perfectly but flashing fails every time i tried 4 different USB ports and same thing at the end of flashing it says FAILED but i see no error on the log it goes all the way to where it writes CACHE it seems and then says FAILED any ideas as to what to do to recover my phone would be appreciated.
Click to expand...
Click to collapse
Try a different region other than Hong Kong.

Flash again stock with odin and check md5 before

rayman95 said:
Flash again stock with odin and check md5 before
Click to expand...
Click to collapse
Usually Odin checks the MD5 validity of the file before it begins anything. If he just gets stuck on cache, the MD5 check must have passed.

bligui said:
So today I was trying to update my phone to a newer version of 4.4.2 I downloaded N900ZSUDNG1_N900OZSDNG1_BRI also Odin v3.09, Odin detects my phone perfectly but flashing fails every time i tried 4 different USB ports and same thing at the end of flashing it says FAILED but i see no error on the log it goes all the way to where it writes CACHE it seems and then says FAILED any ideas as to what to do to recover my phone would be appreciated.
Click to expand...
Click to collapse
try a different usb cable, or use the original samsung cable that you got from the box...

nicholaschum said:
Try a different region other than Hong Kong.
Click to expand...
Click to collapse
Fixed thank you guys it was the actual file I downloaded the problem downloaded a different regions an all worked Ok, will mark as solved.

bligui said:
Fixed thank you guys it was the actual file I downloaded the problem downloaded a different regions an all worked Ok, will mark as solved.
Click to expand...
Click to collapse
Clicking thanks will suffice

Flash problem? PIT? Bricked

Hi all,
Over the weekend my phone died in my hands, it was on charge (low battery), turned off and wouldn't turn on again. It just displays the Samsung Galaxy Note logo and never gets passed that.
I tried to get into recovery CWM is installed) and I get MMC: mmc_read fail and Moviand Checksum Confirmation Fail.
I've tried to upload a PIT as Odin reports that there is no PIT partition - I'm using a few .pits I've found on the forum and am trying to use these (I'll attach one) and also using the ROM from SamMobile - I believe this is the correct one. My sim is Everything Everywhere but the phone is unlocked so I picked the United Kingdom one. N9005XXUGNG1_N9005OXAGNJ3_N9005XXUGNG1_HOME.tar
However when I add the PIT to Odin and the tar to "PDA" in Odin I get "There is no PIT partition":
and on the screen itself in Download Mode gives these errors:
MMC: mmc_read fail
ODIN: flash read failure
SECURE CHECK FAIL: PIT
What am I doing wrong here? Could the hardware have failed... I'm not even that bothered about the phone itself, I just really want to try and get the data off it - but don't think there is a way to do this without booting into a ROM or at least recovery to use ADB.
Any help would be appreciated!

I know how you feel
oli356 said:
Hi all,
Over the weekend my phone died in my hands, it was on charge (low battery), turned off and wouldn't turn on again. It just displays the Samsung Galaxy Note logo and never gets passed that.
I tried to get into recovery CWM is installed) and I get MMC: mmc_read fail and Moviand Checksum Confirmation Fail.
I've tried to upload a PIT as Odin reports that there is no PIT partition - I'm using a few .pits I've found on the forum and am trying to use these (I'll attach one) and also using the ROM from SamMobile - I believe this is the correct one. My sim is Everything Everywhere but the phone is unlocked so I picked the United Kingdom one. N9005XXUGNG1_N9005OXAGNJ3_N9005XXUGNG1_HOME.tar
However when I add the PIT to Odin and the tar to "PDA" in Odin I get "There is no PIT partition":
and on the screen itself in Recovery Mode gives these errors:
MMC: mmc_read fail
ODIN: flash read failure
SECURE CHECK FAIL: PIT
What am I doing wrong here? Could the hardware have failed... I'm not even that bothered about the phone itself, I just really want to try and get the data off it - but don't think there is a way to do this without booting into a ROM or at least recovery to use ADB.
Any help would be appreciated!
Click to expand...
Click to collapse
Hi Oli,
I've had the same issue a few months ago on my pretty much brand new N3, Canadian. I tried a few "PIT" files as well, with no success! My solution, can't recommend to you, was to install i.e. Slimkat ROM or CM11. I'm never concerned about data partition as I can always drop my MP3s once I'm able to boot into the OS. All important ROMs, Gapps and Apps are on EXT SD card .
So, that was my last resort to bring the N3 back to life. I have flashed a few TW based ROMs after, and it was all well.
But honestly, (someone else confirm this) you can "dirty" flash AOSP based ROM without wiping data partition. In other words when you think about what I did, that's what fixed the problem. I wish you nothing but good luck!
Are you even able to get to CWM recovery point? I do NOT remember if mine was broken, TWRP, that is.
Kind regards,
Sonny B.

Hi Sonny B
Unfortunately I can't boot into CWM recovery as I get this:
MMC: mmc_read fail and Moviand Checksum Confirmation Fail.
As far as I know though right CM11/Slimkat can't be installed from Odin so I would need to be in TWRP or CWM which I can't get to
I guess I need to know why I can't push the PIT file from Odin... if this works then hopefully I can install CWM recovery and get somewhere.
Thanks

My, My...
oli356 said:
Hi Sonny B
Unfortunately I can't boot into CWM recovery as I get this:
MMC: mmc_read fail and Moviand Checksum Confirmation Fail.
As far as I know though right CM11/Slimkat can't be installed from Odin so I would need to be in TWRP or CWM which I can't get to
I guess I need to know why I can't push the PIT file from Odin... if this works then hopefully I can install CWM recovery and get somewhere.
Thanks
Click to expand...
Click to collapse
Oli, oli...
If I could just remember what I've done in my case. I don't think I ever received that many "serious" error messages when my phone was down. I honestly think that my recovery was not broken, therefore I was able to install custom ROM, when original stock ROM was not working for me!
I'll definitely keep my eye on this thread. Don't give up please! I hope seasoned kanger can chime in here with a solution.
Good luck,
Sonny B.

sonny_b_bih said:
Oli, oli...
If I could just remember what I've done in my case. I don't think I ever received that many "serious" error messages when my phone was down. I honestly think that my recovery was not broken, therefore I was able to install custom ROM, when original stock ROM was not working for me!
I'll definitely keep my eye on this thread. Don't give up please! I hope seasoned kanger can chime in here with a solution.
Good luck,
Sonny B.
Click to expand...
Click to collapse
Given up for now - just getting no where and out of ideas on how to get this to work.
Can't flash a ROM because no PIT is found but then I can't re-partition with the PIT either =/

After trying more PIT files and ROMS from different sources I have well and truly given up. I've requested the phone to be recycle so at least I can get some money for it

I used to the same problem this summer you should try reflashing a stock rom with odin

o-ellinas said:
I used to the same problem this summer you should try reflashing a stock rom with odin
Click to expand...
Click to collapse
Tried a few now from Samsmobile and other sites but just get the message about no PIT partition.

http://www.galaxynote3update.com/fi...-the-unbrick-and-recovery-guide-just-for-you/
Check this out

Thanks but its unfortunately just the same as every other help guide They all seem to suggest that if you can get into download mode then it's possible to fix the phone but after trying so many different stock ROMs from different sources and using the PIT file.. it's just not happy.
Reluctant to recycle the phone though based on the fact that I keep reading that it can be fixed...

[Q] Bricked Galaxy S4, pls help (everything tried)

Hi all ! Hope sb help me with this...
I updated my S4 i9500 to android 5.0.1 lollipop (XXUHOAA ) about 8 months ago. No problem untill 2 days ago my phone turned off itself then went to bootloop.
Now it just shows the s4 logo then restarts again all the time. SOMETIMES it turns on but after 4 or 5 seconds again turns off (not able to do anything during 4 seconds)
I CAN NOT access recovery mode. The recovery mode became a black screen and not able to wipe/factory reset.
Before I bring it to serviceman I want to see if u can help me with this(It's warranty is voided now)
WHAT I HAVE TRIED RECENTLY:
I tried to flash 4 different Roms using 3 different odin versions but no success
[flashing roms get the error "complete(write) operation failed" and by using the suitable PIT file I get the error "repartition operation failed"]
Also tried flashing 5-files-firmware (with pit file) but again "repartition operation failed"
I used 3 usb cables including the original one
I did all of those steps using 2 different laptops and also different ports
I'm sure the samsung drivers are installed[odin port comes blue or yellow]
I used SkipSoft ToolKit and one click unsoftbrick softwares but no success
Also used adb to factory reset phone but it doesn't detect my phone[ seems it needs to be turned on]
I removed simcard, format extra sd card, remove battery for a long time and.....
Is there anything I haven't tried yet?? Can somone help ? I appreciate any suggestion,Thanks
[[Sorry my English]]

Try flashing a custom recovery and then factory reset?

KennethHau said:
Try flashing a custom recovery and then factory reset?
Click to expand...
Click to collapse
Hi and Thanks for replying, Well I downloaded some CWM/TWRP recoveries but the problem is that I can't flash anything with Odin. I always get the error:
<ID:0/007>NAND Write Start!!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed
And this error is the same while flashing anything like Rom,Recovery,philz_touch and even auto root files.
I'm so confused

Have you tried downloading stock firmware from sammobile for your model and carrier and installing? If that doesn't work you may have a serious issue.
Sent from my unknown using Tapatalk
---------- Post added at 01:12 AM ---------- Previous post was at 01:10 AM ----------
alimtale said:
Hi and Thanks for replying, Well I downloaded some CWM/TWRP recoveries but the problem is that I can't flash anything with Odin. I always get the error:
<ID:0/007>NAND Write Start!!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed
And this error is the same while flashing anything like Rom,Recovery,philz_touch and even auto root files.
I'm so confused
Click to expand...
Click to collapse
Is the Odin version the proper one for your phone?
Sent from my unknown using Tapatalk

Jchef said:
Have you tried downloading stock firmware from sammobile for your model and carrier and installing? If that doesn't work you may have a serious issue.
Is the Odin version the proper one for your phone?
Click to expand...
Click to collapse
Of course I did. I even downloaded different android versions (5.0.1,4.4.2,4.2.2) But non of them flashed
I remember I used Odin 3.0.9 to upgrade my S4 to 5.0.1 months ago but I tried different Odin versions (1.85,3.0.7,3.0.9) for in case.
Unfortunately,I face an error all the time that is related to Nand write corruption .

If you have flashed 4.2.2 it's a brick ,for sure.

ludoke said:
If you have flashed 4.2.2 it's a brick ,for sure.
Click to expand...
Click to collapse
No it didn't flashed. After I got error while flashing 5.0.1 firmware I tried other versions to see if it works. But the error is the same.

alimtale said:
No it didn't flashed. After I got error while flashing 5.0.1 firmware I tried other versions to see if it works. But the error is the same.
Click to expand...
Click to collapse
Even trying to flash 4.2.2 will result in a brick,so it's normal that it didn't work

ludoke said:
Even trying to flash 4.2.2 will result in a brick,so it's normal that it didn't work
Click to expand...
Click to collapse
My phone turned off itself. I tried flashing firmware after the problem occurred. I don't think the problem is because of flashing 4.2.2

Deleted

Maybe it's the battery

ludoke said:
Even trying to flash 4.2.2 will result in a brick,so it's normal that it didn't work
Click to expand...
Click to collapse
This is incorrect. You don't brick your phone when you try to flash 4.2.2. That's simply not possible.

dorian2kx said:
Maybe it's the battery
Click to expand...
Click to collapse
I have 2 batteries...both of them same result (bootloop)

alimtale said:
I have 2 batteries...both of them same result (bootloop)
Click to expand...
Click to collapse
Does it reboot when you are in download mode? If so, then it's your power button that is faulty. Either try to wiggle it loose or replace it.
If it doesn't reboot while in download mode then you have some other hardware damage. Probably your motherboard is damaged.

Lennyz1988 said:
Does it reboot when you are in download mode? If so, then it's your power button that is faulty. Either try to wiggle it loose or replace it.
If it doesn't reboot while in download mode then you have some other hardware damage. Probably your motherboard is damaged.
Click to expand...
Click to collapse
No it doesn't reboot while download mode.Maybe hardware damage but it sometimes turns on and I can access applications and settings for a short time (about 5 seconds)
I have rooted my device when upgraded to 5.0.1. And recently I unchecked "enable superuser" in the superuser app.( I have done this before many times without problem)
I guess there is a problem related to that because when my phone turned on I tried to check the enable option in the superuser but as soon as I touch the check box my phone turns off instantly

If your phone goes into download mode. I don't think it is bricked.
Sent from my unknown using Tapatalk

You cannot fix your phone by Odin because of the Secure Download enabled bootloader.
You will have to pay a JTAG repair service.
Android 5.0.1 is a crap, which replaces your bootloader with a secure-download featured one,
so you won't ever be able to have the control of your phone again!

@Killnolife: A little melodramatic? It's not a locked bootloader so he still has total control over the device. Come back with an AT&T or Verizon S4 and then complain about having no control.
OP, Lennyz1988's advice is sound. Follow it.

Well I got tired of trying to flash my device with Odin. Always error... The Only choice I have is to take the phone to the service center and see what they can do...I'll share the result...

I took my phone to service centers for repair, they said the hard is damaged and it takes about 100$ to replace that:crying: if I pay that much I'm not sure it wont damage again
So my phone is dead now on my table and I gonna buy a new phone (maybe s5 or z3). Hope no one experience this situation

Bricked my Galaxy S7 Edge: Odin stuck at initialization, Odin protocol version error.

Hello everyone, hope all is well.
I was trying to install a factory ROM for my Galaxy S7 Edge and during the process, I believe I went and flashed a wrong ROM file (I think it was Galaxy S6 Edge's).
Anyways, due to that, my phone is completely bricked (softbricked? because I can turn it on?).
The problem I'm having is that when I turn on the device normally, it will show the GALAXY S7 EDGE logo but then it'd go straight into recovery mode.
In the recovery mode, it'd say "dm-verity verification failed.. " , "E: failed to mount /system (Invalid argument)". Then when I press Apply update from ADB/SD Card, it gives an error saying "Update from external storage is disabled".
I am able to get into the download mode also and downloaded correct factory ROM and flashed it but it gives me an error saying "Odin protocol version error" in the phone, and in Odin, it stops at "Initializing..." and the program crashes after 5 minutes or so.
I there anything I can do to unbrick this dude? I've been searching all over the place yesterday and could't find a right solution for me so I decided to write one myself.
Thanks in advance and I'll appreciate any help.
Model: G935A. AT&T.

schoolbus11 said:
Hello everyone, hope all is well.
I was trying to install a factory ROM for my Galaxy S7 Edge and during the process, I believe I went and flashed a wrong ROM file (I think it was Galaxy S6 Edge's).
Anyways, due to that, my phone is completely bricked (softbricked? because I can turn it on?).
The problem I'm having is that when I turn on the device normally, it will show the GALAXY S7 EDGE logo but then it'd go straight into recovery mode.
In the recovery mode, it'd say "dm-verity verification failed.. " , "E: failed to mount /system (Invalid argument)". Then when I press Apply update from ADB/SD Card, it gives an error saying "Update from external storage is disabled".
I am able to get into the download mode also and downloaded correct factory ROM and flashed it but it gives me an error saying "Odin protocol version error" in the phone, and in Odin, it stops at "Initializing..." and the program crashes after 5 minutes or so.
I there anything I can do to unbrick this dude? I've been searching all over the place yesterday and could't find a right solution for me so I decided to write one myself.
Thanks in advance and I'll appreciate any help.
Model: G935A. AT&T.
Click to expand...
Click to collapse
what firmware was you running and what firmware are you trying to flash ?

schoolbus11 said:
Hello everyone, hope all is well.
I was trying to install a factory ROM for my Galaxy S7 Edge and during the process, I believe I went and flashed a wrong ROM file (I think it was Galaxy S6 Edge's).
Anyways, due to that, my phone is completely bricked (softbricked? because I can turn it on?).
The problem I'm having is that when I turn on the device normally, it will show the GALAXY S7 EDGE logo but then it'd go straight into recovery mode.
In the recovery mode, it'd say "dm-verity verification failed.. " , "E: failed to mount /system (Invalid argument)". Then when I press Apply update from ADB/SD Card, it gives an error saying "Update from external storage is disabled".
I am able to get into the download mode also and downloaded correct factory ROM and flashed it but it gives me an error saying "Odin protocol version error" in the phone, and in Odin, it stops at "Initializing..." and the program crashes after 5 minutes or so.
I there anything I can do to unbrick this dude? I've been searching all over the place yesterday and could't find a right solution for me so I decided to write one myself.
Thanks in advance and I'll appreciate any help.
Model: G935A. AT&T.
Click to expand...
Click to collapse
First of all why were you trying to flash a stock Rom? Next its a piece of cake take it to your local warranty store and ask them to flash your stock ROM as long as you didn't try to root it they should fash it for you. I've done it many times. Just tell them you were charging it overnight and had it turned off and when you booted up the next morning it was going crazy.
As I said if you weren't trying to root they should do it for you.
"All we know is...He's called the Stig!"
Sent from my Echoe driven G935F

strikerdj2011 said:
what firmware was you running and what firmware are you trying to flash ?
Click to expand...
Click to collapse
I was on a rooted Galaxy S7 firmware for development purpose but I wanted to take it back to factory setting and un-root the device by installing a fresh new one.
s7freak said:
First of all why were you trying to flash a stock Rom? Next its a piece of cake take it to your local warranty store and ask them to flash your stock ROM as long as you didn't try to root it they should fash it for you. I've done it many times. Just tell them you were charging it overnight and had it turned off and when you booted up the next morning it was going crazy.
As I said if you weren't trying to root they should do it for you.
"All we know is...He's called the Stig!"
Sent from my Echoe driven G935F
Click to expand...
Click to collapse
That sounds like a clever idea but if there's any way I could try to do it by myself before I take it to them, I wanted to try.

schoolbus11 said:
I was on a rooted Galaxy S7 firmware for development purpose but I wanted to take it back to factory setting and un-root the device by installing a fresh new one.
Click to expand...
Click to collapse
if your rooted who dont you just flash a custom rom boot up then flash stock ? and i thought you cant root the american model as of the locked bootloader just you said 935a thought that was usa model ?

strikerdj2011 said:
if your rooted who dont you just flash a custom rom boot up then flash stock ? and i thought you cant root the american model as of the locked bootloader just you said 935a thought that was usa model ?
Click to expand...
Click to collapse
Well now I couldn't flash any of the firmwares out there that I found. I kept on getting the same error stated above. It is usa at&t model.
Perhaps, is there a custom ROM and/or other steps you'd recommend me to try?
Thanks for your replies though, I appreciate it very much.

schoolbus11 said:
Well now I couldn't flash any of the firmwares out there that I found. I kept on getting the same error stated above. It is usa at&t model.
Perhaps, is there a custom ROM and/or other steps you'd recommend me to try?
Thanks for your replies though, I appreciate it very much.
Click to expand...
Click to collapse
just a massive shot in the dark here dm-verity verification failed when we flash a custom rom on our international 935f in twrp we have to format data in twrp to be able to flash any thing how about if there is a twrp for the qualacom version how about you flash the twrp format data then flash stock via twrp i know its a shot in the dark but best i can think of at the moment

strikerdj2011 said:
just a massive shot in the dark here dm-verity verification failed when we flash a custom rom on our international 935f in twrp we have to format data in twrp to be able to flash any thing how about if there is a twrp for the qualacom version how about you flash the twrp format data then flash stock via twrp i know its a shot in the dark but best i can think of at the moment
Click to expand...
Click to collapse
I will try what you have suggested. But isn't twrp only install-able when the phone is actually turned on to OS? As far as I've researched, I saw that it needs to have developer mode on.

schoolbus11 said:
I will try what you have suggested. But isn't twrp only install-able when the phone is actually turned on to OS? As far as I've researched, I saw that it needs to have developer mode on.
Click to expand...
Click to collapse
no odin flash twrp in download mode make sure there is a twrp for you device i know there is for the flat s7

Try smart switch emergancy mode

strikerdj2011 said:
no odin flash twrp in download mode make sure there is a twrp for you device i know there is for the flat s7
Click to expand...
Click to collapse
I tried to download one here http://androiding.how/galaxy-s7-edge-twrp-recovery/ and tried to flash it but I get the same error => "Odin protocol version error!", and stuck at "Initialization..".
Do you think you could verify if that link could be the one I'm looking for?
MATRIKS said:
Try smart switch emergancy mode
Click to expand...
Click to collapse
I tried it but unfortunately, I don't understand why but it doesn't recognize my S/N.

schoolbus11 said:
I tried to download one here http://androiding.how/galaxy-s7-edge-twrp-recovery/ and tried to flash it but I get the same error => "Odin protocol version error!", and stuck at "Initialization..".
Do you think you could verify if that link could be the one I'm looking for?
I tried it but unfortunately, I don't understand why but it doesn't recognize my S/N.
Click to expand...
Click to collapse
thats for the international version which is exynos and not qualacom

strikerdj2011 said:
thats for the international version which is exynos and not qualacom
Click to expand...
Click to collapse
Right.. Then that means I should wait for Qualcomm version to be released?

there doesnt seem to be one yet for the usa version of the edge you did turn on thre allow oem unlock in developer options on the device before you started playing with the firmwares didnt you ?

strikerdj2011 said:
there doesnt seem to be one yet for the usa version of the edge you did turn on thre allow oem unlock in developer options on the device before you started playing with the firmwares didnt you ?
Click to expand...
Click to collapse
Allow oem unlock.. I didn't allow it.. I regretted so much after I flashed everything and realized i didnt turn it on. -_- Probably not fixable?

schoolbus11 said:
Allow oem unlock.. I didn't allow it.. I regretted so much after I flashed everything and realized i didnt turn it on. -_- Probably not fixable?
Click to expand...
Click to collapse
i am not a dev mate just learn from observation lol but from other devices i have seen them bricked if thats not been allowed in dev options but i am not 100% sure on this one service center is probs you best bet as some one said earlier as am sure if thats not checked nothing can be flashed as that command allows it its like the bootloader is still locked kind of thing

I would take it a service repair center before messing it up anymore, just to be on the safe side, you never know with these things, yeah it might be fixable but if knox isn't voided then you can just have it repaired properly for free.

strikerdj2011 said:
i am not a dev mate just learn from observation lol but from other devices i have seen them bricked if thats not been allowed in dev options but i am not 100% sure on this one service center is probs you best bet as some one said earlier as am sure if thats not checked nothing can be flashed as that command allows it its like the bootloader is still locked kind of thing
Click to expand...
Click to collapse
samuel2706 said:
I would take it a service repair center before messing it up anymore, just to be on the safe side, you never know with these things, yeah it might be fixable but if knox isn't voided then you can just have it repaired properly for free.
Click to expand...
Click to collapse
I figured... Thanks for your help and suggestions anyways. Have a good one.

schoolbus11 said:
I figured... Thanks for your help and suggestions anyways. Have a good one.
Click to expand...
Click to collapse
Did you manage to get this sorted?
I'm having same issue

bump