Database Info

[Q] Bricked phone, need help unbricking. (System software not authorized....etc.)

So, I've done this before, and I've never bricked a device until now.
I tried installing a custom rom for my Galaxy S3 on Verizon, but when I restarted, it says this:
System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help.
I can't get into clockwork, or any bootloader. Any attempt to do anything brings this screen up.
Now, I can get into the Odin downloader. (Power, volume down and home). But, I can't figure out how to get a Rom to load. This is where I am stuck. I have downloaded a few roms, all stock, but none of them want to be recognized. I have no idea where to go. I've been downloading stuff for 5 hrs and nothing has worked, so now Im going to the forumns. Any help is appreciated.
I have the Verizon i-535 Galaxy SIII.

You did not brick your phone you failed to unlock your bootloader. There are 2 guides in the android dev section for rooting.

http://forum.xda-developers.com/showthread.php?t=1974114

Odin back to stock and next time after rooting make sure to use EZUnlock 1.2 to unlock the bootloader BEFORE loading a ROM

[Q] samsung galaxy s3 root accidentyl updated help!

I have a rooted android device samsung galaxy s3 and it was running fine and everything till one day it said to install an update. i accepted it and while it was updating all of a sudden it went to that black screen and says, " system software not authorized by Verizon Wireless has been found on your phone. Please turn off you phone and go to the nearest Verizon Wireless store for help." Then thats where i couldn't do anything with my phone but go to download/ODIN MODE and rebooting system thing where you can reboot system. I am very new and i don't know much about rooting and the meanings of a lot of words like unlock bootloader. If i go to ODIN MODE it says
ODIN MODE
PRODUCT NAME: SCH-1535
CUSTOM BINARY DOWNLOAD: Yes (1 Counts)
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty bit: 1
BOOTLOADER RP SWREV:1
I think this doesn't look good. What should I do to make my phone be working again and not showing that black screen?
I already wiped all data and tried to do that StockROm thing on my computer ODIN and still nothing.
Is my bootloader locked? if so do I need to unlock it to make my phone work again? Thanks so much for your time

Did you updated after rooting your SGS3 Verizon?
Games are a part of Life but Life is not a part of a game!

I am in the same position as a lot of people with the s3. I have the Verizon model and had it unlocked using Odin while it was on 4.2. I accepted the Verizon update to 4.3 forgetting that it unroots it. Some people are saying that the only way to get my phone unlocked again is to find a way to flash it back to 4.2 version. Is there ANYWAY to unlock it on the 4.3 without bricking it??? If there is, how so???? Please help!!
Sent from my SCH-I535 using xda app-developers app

Check modem version and your product code and massage me again!
Games are a part of Life but Life is not a part of a game!

Not sure what happened....PLEASE HELP

Hey. So I have a note 2 on at&t. It was on 4.3. I used odin to downgrade to 4.1.1, then factory unlocked it and all was well. I tested with tmobile sim and it was on tmobile 4g and able to make calls using tmobile. I then went to update the version (I read once its unlocked it can be updated) Now, it gets stuck at "samsung galaxy note 2" when booting up and wont go past it. I tried to odin it again and successfully installed 4.1.1, but still wont get past samsung galaxy note 2. have disconnected phone and tried to boot up using vol+ (+) home button (+) power button, but nothing......PLEASE HELP
thanks

scottrf8 said:
Hey. So I have a note 2 on at&t. It was on 4.3. I used odin to downgrade to 4.1.1, then factory unlocked it and all was well. I tested with tmobile sim and it was on tmobile 4g and able to make calls using tmobile. I then went to update the version (I read once its unlocked it can be updated) Now, it gets stuck at "samsung galaxy note 2" when booting up and wont go past it. I tried to odin it again and successfully installed 4.1.1, but still wont get past samsung galaxy note 2. have disconnected phone and tried to boot up using vol+ (+) home button (+) power button, but nothing......PLEASE HELP
thanks
Click to expand...
Click to collapse
I don't have a Note (I have the GS3 on TMO). Do you have any idea if the Note 2 has the same issue that the GS3 has, where with the 4.3 update you get a new locked bootloader that prevents you from going back to anything earlier than 4.3? That's the way it is on the GS3. I guess if you were able to actually boot up and make calls after you downgraded back to 4.1.1, then that must not be the case.
In any case, you're getting stuck on the boot logo when you power it on? Can you get into the recovery at all? Do you have the stock recovery or a custom recovery installed? Have you tried clearing cache/dalvik and fixing perms? That often fixes things for me when I'm stuck on the boot logo.

scottrf8 said:
Hey. So I have a note 2 on at&t. It was on 4.3. I used odin to downgrade to 4.1.1, then factory unlocked it and all was well. I tested with tmobile sim and it was on tmobile 4g and able to make calls using tmobile. I then went to update the version (I read once its unlocked it can be updated) Now, it gets stuck at "samsung galaxy note 2" when booting up and wont go past it. I tried to odin it again and successfully installed 4.1.1, but still wont get past samsung galaxy note 2. have disconnected phone and tried to boot up using vol+ (+) home button (+) power button, but nothing......PLEASE HELP
thanks
Click to expand...
Click to collapse
I start to wonder if people research before doing anything.
To say again. You can't downgrade. You have Knox. You possibly tripped the Knox flag. Reflash the 4.3 stock ROM. If that fails, It's most probably eFuse, if It's 4.3.
(Basically, eFuse messes up your phone aka bricks You phone aka @#%& it up.)
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
---------- Post added 5th January 2014 at 12:05 AM ---------- Previous post was 4th January 2014 at 11:59 PM ----------
mcgrabowski said:
I don't have a Note (I have the GS3 on TMO). Do you have any idea if the Note 2 has the same issue that the GS3 has, where with the 4.3 update you get a new locked bootloader that prevents you from going back to anything earlier than 4.3? That's the way it is on the GS3. I guess if you were able to actually boot up and make calls after you downgraded back to 4.1.1, then that must not be the case.
In any case, you're getting stuck on the boot logo when you power it on? Can you get into the recovery at all? Do you have the stock recovery or a custom recovery installed? Have you tried clearing cache/dalvik and fixing perms? That often fixes things for me when I'm stuck on the boot logo.
Click to expand...
Click to collapse
You're right. The locked bootloader messed those who didn't research about it's life's real bad. 4.3 supposedly has eFuse in it, which FU*CKS your phone. I read it up on the Samsung Knox website, and it said that eFuse "rewrites a read-only part of the phone, resulting in a unusable phone." If u triggered that, it'll be a hard brick, (in my knowledge)
Knox itself is irritating. The Knox Warranty Void counter, which max at 1, is unresetable, (even with JTAG, will brick if h try) so your warranty is *poof*
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.

I did a fair amount of research before downgrading. In fact I didn't want to downgrade, but I did want to unlock it. It is unlocked and it's running on 4.1.1. So when you say that you can't downgrade, you mean you shouldn't downgrade cause then you will be stuck with 4.1.1?

scottrf8 said:
I did a fair amount of research before downgrading. In fact I didn't want to downgrade, but I did want to unlock it. It is unlocked and it's running on 4.1.1. So when you say that you can't downgrade, you mean you shouldn't downgrade cause then you will be stuck with 4.1.1?
Click to expand...
Click to collapse
When you were on 4.3, was that an OTA update or an ODIN flash of a stock firmware? Or did you just have a 4.3 ROM from the forums that you loaded (AOSP or rooted stock based ROM with Knox, etc., removed) with TWRP or CWM? Supposedly from what I've been reading if you take the 4.3 OTA or ODIN flash the stock 4.3, the bootloader gets updated, as Irwenzhao mentions above and I've experienced, where you CAN'T downgrade again to 4.1.2 or earlier. I believe that just means you can't go back to a fully stock pre 4.3. I THINK it just means you can't ODIN back to a factory image earlier than 4.3, which is what I experienced. But with TWRP or CWM, I believe I can still load other ROMs at will regardless if they are pre 4.3 or not.

yeah, that sounds kinda like the same thing I have come across. 4.3 was OTA and downgraded to a stock 4.1.1 ROM. Guess this triggers KNOX cause now KNOX WARRANTY VOID is 1. which once that is triggered, you cannot go from a non KNOX version (4.1.1) to a version that has KNOX. My question now is does that apply to just the stock firmware? Would ANY of the ROM's created by the devs work?
There were some posts in the unlock thread that people were able to go from 4.1.1 (after downgrading) back up to 4.3. Just trying to figure out how that would be the case? Could the knox warranty flag not have been set for them?

scottrf8 said:
yeah, that sounds kinda like the same thing I have come across. 4.3 was OTA and downgraded to a stock 4.1.1 ROM. Guess this triggers KNOX cause now KNOX WARRANTY VOID is 1. which once that is triggered, you cannot go from a non KNOX version (4.1.1) to a version that has KNOX. My question now is does that apply to just the stock firmware? Would ANY of the ROM's created by the devs work?
There were some posts in the unlock thread that people were able to go from 4.1.1 (after downgrading) back up to 4.3. Just trying to figure out how that would be the case? Could the knox warranty flag not have been set for them?
Click to expand...
Click to collapse
Just to make it clear, Knox is a bootloader, which means u can flash anything that's not a bootloader, but your warranty would be history. Flashing anything trips the flag, even 4.1.1/2 stock ROMs.
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.

Truthfully, that doesn't clear it up. Do the stock firmware through Kies or ota include a bootloader and that's why it won't install? Thanks

Flashing the stock firmware through kies, ODIN, or the OTA update will update the boot loader as far as I know and will ruin any chance of returning to stock and void your warranty. As long as you don't want to do that, I don't think it's too big of a deal.
At this point, I couldn't care less about the warranty. I would think it's expired now anyhow. As long as I can flash ROMs and boy the phone up and use it. I'm happy.
Sent from my SGH-T999 using xda app-developers app

Hard bricking Galaxy S7

I wrote in separate thread 10 days ago.
I got the rooted Galaxy S7 (SM-G930F) which if I try to boot to recovery gives an error: dm-verity verification need to check drk first.
Then following step by step instructions I installed TWRP.
And flashed custom rom SuperMan-Rom V1.6.5
Rom worked fine until I rebooted the device for the first time. Then I got message:
Code:
Custom Binary Blocked By FRP
Maybe I accidentally turned off OEM unlock in Developer settings, but I honestly don't remember I did that.
And after that I got the hard brick. This is confirmed by @CuBz90 in this thread
So my question is:
1. After the Galaxy S7 is rooted/custom recovery is installed, the DRK is damaged and dm-verity verification will fail if stock rom is installed, right?
2. If user accidentally turn off OEM Unlock the device will be hard bricked, right?
Is that two steps one way ultimate bricking?
I'm asking that because I'm thinking of buying new Galaxy S7 to replace the bricked one, but if hard bricking is that easy, than I'm not really sure I will buy it again.

Dude, try to kill him completly ( nothing on screen ) then send him to warranty, you got nothing to lose.

NeoDJW said:
Dude, try to kill him completly ( nothing on screen ) then send him to warranty, you got nothing to lose.
Click to expand...
Click to collapse
It's not possible since I bought it second hand.
Even if I had a warranty, in my country (Serbia) warranty for smartphones doesn't mean much, I think I could write PhD thesis easier than to make seller replace/fix smartphone with warranty

mss1988 said:
I wrote in separate thread 10 days ago.
I got the rooted Galaxy S7 (SM-G930F) which if I try to boot to recovery gives an error: dm-verity verification need to check drk first.
Then following step by step instructions I installed TWRP.
And flashed custom rom SuperMan-Rom V1.6.5
Rom worked fine until I rebooted the device for the first time. Then I got message:
Code:
Custom Binary Blocked By FRP
Maybe I accidentally turned off OEM unlock in Developer settings, but I honestly don't remember I did that.
And after that I got the hard brick. This is confirmed by @CuBz90 in this thread
So my question is:
1. After the Galaxy S7 is rooted/custom recovery is installed, the DRK is damaged and dm-verity verification will fail if stock rom is installed, right?
2. If user accidentally turn off OEM Unlock the device will be hard bricked, right?
Is that two steps one way ultimate bricking?
I'm asking that because I'm thinking of buying new Galaxy S7 to replace the bricked one, but if hard bricking is that easy, than I'm not really sure I will buy it again.
Click to expand...
Click to collapse
Maybe you can find the solution here:
http://androidforums.com/threads/custom-binary-block-by-frp-lock.977734/

Erik1805 said:
Maybe you can find the solution here:
http://androidforums.com/threads/custom-binary-block-by-frp-lock.977734/
Click to expand...
Click to collapse
Thanks but this will not fix my problem.

Have you tried this: http://pangu.in/frp.error.html

Bright.Light said:
Have you tried this: http://pangu.in/frp.error.html
Click to expand...
Click to collapse
No I didn't but the fact is it will not work.
There is currently no way to fix that. The only way would be to unlock FRP by some box, but it isn't released yet.
What I am asking here is true that Galaxy S7 could be hard bricked that easy? By steps I wrote in my first post.

My questions are partially answered in this article
But I still don't understand what's the problem with dm-variety if I flashed stock rom?
Is there are any other parts of the NAND that are not original/signed and that's why dm-verity fails?
If that's the case can they be backed up then reflashed with the Odin if I get into same problem with new phone?
Thanks

@mss1988 Even if you get message as locked because of FRP, just use Smart switch with Emergency recovery mode and you will get the device back to its original state. This works even if the device is rooted or Twrp'd

harshang2007 said:
@mss1988 Even if you get message as locked because of FRP, just use Smart switch with Emergency recovery mode and you will get the device back to its original state. This works even if the device is rooted or Twrp'd
Click to expand...
Click to collapse
Thanks, but Smart Switch Emergency Recovery is basically the same thing as Kies Firmware update. Which I already tried and that didn't fixed my problem.

mss1988 said:
Thanks, but Smart Switch Emergency Recovery is basically the same thing as Kies Firmware update. Which I already tried and that didn't fixed my problem.
Click to expand...
Click to collapse
@mss1988 I have personally faced this issue on Samsung J7 and J5 and later I had to use Smart Switch's Emergency recovery functionality by enter my Serial number and Device Model Number and Successfully finished flashing the stock ROM. Yes, This works.

harshang2007 said:
@mss1988 I have personally faced this issue on Samsung J7 and J5 and later I had to use Smart Switch's Emergency recovery functionality by enter my Serial number and Device Model Number and Successfully finished flashing the stock ROM. Yes, This works.
Click to expand...
Click to collapse
I don't have the phone anymore to confirm or to deny this. But the whole procedure in Kies and Smart Switch is the same. There are other people with the same problem too in this thread too, and they still didn't found the way to unbrick their devices.

mss1988 said:
I wrote in separate thread 10 days ago.
I got the rooted Galaxy S7 (SM-G930F) which if I try to boot to recovery gives an error: dm-verity verification need to check drk first.
Then following step by step instructions I installed TWRP.
And flashed custom rom SuperMan-Rom V1.6.5
Rom worked fine until I rebooted the device for the first time. Then I got message:
Code:
Custom Binary Blocked By FRP
Maybe I accidentally turned off OEM unlock in Developer settings, but I honestly don't remember I did that.
And after that I got the hard brick. This is confirmed by @CuBz90 in this thread
So my question is:
1. After the Galaxy S7 is rooted/custom recovery is installed, the DRK is damaged and dm-verity verification will fail if stock rom is installed, right?
2. If user accidentally turn off OEM Unlock the device will be hard bricked, right?
Is that two steps one way ultimate bricking?
I'm asking that because I'm thinking of buying new Galaxy S7 to replace the bricked one, but if hard bricking is that easy, than I'm not really sure I will buy it again.
Click to expand...
Click to collapse
I went through this procedure: http://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516 which gives a link to downloading the factory binary (of either version). It reinstated my IMEI which had been turned to a string of zeroes. I will say that when you reboot after flashing the factory binary it's pretty different looking so be prepared for that. I then went to Sammobile and downloaded the appropriate stock ROM for my s7 and flashed that with Odin. I flashed TWRP, formatted internal data when given the opportunity, flashed the no-verity-opt-encrypt.zip, and I was able to use my s7 again. At any rate, you might follow the guide at the link I gave you and see if it helps. As always, no guarantee is given or implied. It's just what I did.

Thanks man, but I can't flash the Factory binary, my FRP is unfortunately ON.

E pa brate nemoj se više onda igrati sa telefonom, nije to za svakoga,...
Mod Edit: Please post in English only:
Well, the brothers do not come then play with the phone, it's not for everyone

now phone detect usb ? i mean adb devices

mss1988 said:
I wrote in separate thread 10 days ago.
I got the rooted Galaxy S7 (SM-G930F) which if I try to boot to recovery gives an error: dm-verity verification need to check drk first.
Then following step by step instructions I installed TWRP.
And flashed custom rom SuperMan-Rom V1.6.5
Rom worked fine until I rebooted the device for the first time. Then I got message:
Code:
Custom Binary Blocked By FRP
Maybe I accidentally turned off OEM unlock in Developer settings, but I honestly don't remember I did that.
And after that I got the hard brick. This is confirmed by @CuBz90 in this thread
So my question is:
1. After the Galaxy S7 is rooted/custom recovery is installed, the DRK is damaged and dm-verity verification will fail if stock rom is installed, right?
2. If user accidentally turn off OEM Unlock the device will be hard bricked, right?
Is that two steps one way ultimate bricking?
I'm asking that because I'm thinking of buying new Galaxy S7 to replace the bricked one, but if hard bricking is that easy, than I'm not really sure I will buy it again.
Click to expand...
Click to collapse
wild guess....
Install dm-verity and force encryption disabler
Wipe Cache
install custom kernel

chandarakk said:
now phone detect usb ? i mean adb devices
Click to expand...
Click to collapse
There's no adb/fastboot access from Samsung recovery or Samsung download mode, as far as I know.

Just get your phone into downloadmode and then flash the stock firmware witch you can find on sammobile. I got also this problem, and then everything will be fine ?

did you try use Kies or Smart swticher to factory restore the phone ?
because as far as i know , even FRP is on , you can still flash stock firmware.
and , try local shop to find any place have z3x box or Octopus box .

Galaxy S6 Edge SoftBrick (DRK)

Hi,
I've one (big) problem that I can't fix.
I've been using Android 5.0.1 for more than 1 year as I didn't want to upgrade (it worked pretty well) and because I had the S6 rooted with PingPong root.
However, one month ago it started to run slowly, crashing apps, ... so I decided that, as I wanted to wipe the device, why not upgrade to MM (6.0.1)??, so I did.
I did a backup of all my data and EFS folder and downloaded a 6.0.1 ROM to flash it with ODIN. Everything went OK and finished flashing the rom, but when the S6 restarted it showed this in the recovery:
'dm-verity verificztion failed...
Need to check DRK first...'
And I cant boot.
I've tried some tips that are here and in other websites:
- I've flashed stock rom again
- I've flashed a stock rom without cache.img file.
- I Can't flash some files as I've R/L ON. (I've been trying to disable it for many months but I couldn't).
But the S6 doesn't boot...
Thank you!

What worked for me.
So this is my current issue, but i was able to resolve the issue you are having. so what i did was get the 5.1X OK7 (My phone is Verizon) firmware and flashed through ODIN 3.12.5, this flashed stock 5.1.1 in my phone and it worked good. however i have issue with my phone random restarts and power button not working in recovery or in rom. however i can go in and out of downloading mode or maintenance mode.

Critical_DoubleShot said:
So this is my current issue, but i was able to resolve the issue you are having. so what i did was get the 5.1X OK7 (My phone is Verizon) firmware and flashed through ODIN 3.12.5, this flashed stock 5.1.1 in my phone and it worked good. however i have issue with my phone random restarts and power button not working in recovery or in rom. however i can go in and out of downloading mode or maintenance mode.
Click to expand...
Click to collapse
Thanks for your reply!
I tried to downgrade to 5.1.1 or 5.0.1 but I get an error.
(SW REV CHECK FAIL DEVICE 2 BINARY 1)

That happens when you don't have the right firmware you have.

You CANNOT downgrade to 5.1 or 5.0 since you are on 6.0. The bootloaders refuses to be overwritten.

Critical_DoubleShot said:
That happens when you don't have the right firmware you have.
Click to expand...
Click to collapse
I'm trying to flash another 6.0.1 ROM (a bit older), but I get 'CHECK FAIL. DEVICE: 4, BINARY:3'

I've read that DRK problems are related with EFS files, so... Can I restore EFS folder (I've a backup from Android 5.0.1) to solve?? I don't know how to restore it without booting into the sistem (and without custom recovery)

I am afraid that downgrade to 5.0.1 is not possible, at least I dont know anyone who succedeed in doing that.
If you were on systemless root, probably your Knox is still 0, check it in DL mode, if it is and you have the phone less that 3 yrs (1 yr warranty+2yrs factory warranty) best solution would be to ask in Samsung repair center if the factory warranty would be accepted (ofcourse dont mention flashing, just say you tried official update, and play dumb).
If not you can try custom kernel wich will bypass DRK, and prolly make the phone bootable, but there is no guarantee everything will work well (maybe it will, but mostly it doesnt, forget using Samsung pay, and KNOX tripped)
As for EFS, maybe I am wrong, but I think EFS contains IMEI and sn info, and DRK is something else.

brenner650 said:
I am afraid that downgrade to 5.0.1 is not possible, at least I dont know anyone who succedeed in doing that.
If you were on systemless root, probably your Knox is still 0, check it in DL mode, if it is and you have the phone less that 3 yrs (1 yr warranty+2yrs factory warranty) best solution would be to ask in Samsung repair center if the factory warranty would be accepted (ofcourse dont mention flashing, just say you tried official update, and play dumb).
If not you can try custom kernel wich will bypass DRK, and prolly make the phone bootable, but there is no guarantee everything will work well (maybe it will, but mostly it doesnt, forget using Samsung pay, and KNOX tripped)
As for EFS, maybe I am wrong, but I think EFS contains IMEI and sn info, and DRK is something else.
Click to expand...
Click to collapse
Thank you for your reply!!
I had the device rooted, but with PingPong root, so Knox is still 0. However it shows that the system is "custom".
I'll try the warranty, they may not notice the "custom", just the knox.

I'm with the same problem when trying to flash stock BTU QA7..and only if i flashing cf_root my phone is booting.
Any idea? I don't care about the Knox..
Sent from my SM-G920F using Tapatalk

orbgel10 said:
I'm with the same problem when trying to flash stock BTU QA7..and only if i flashing cf_root my phone is booting.
Any idea? I don't care about the Knox..
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
If you are talking about DRK, the only way to fix it that I know of, other than hw replacement, is via 3rd party professional repair tool. (Octopus/Octoplus box)
If DRK is ok, phone boots normaly, if it is messed up, the only way of booting is with custom kernel which bypass DRK check.
You can check it in recovery, if messed up it will say DM verity failed on bottom of the screen.

Ok, i send my phone to fix, i will tell you what happened.
Sent from my Redmi 3S using Tapatalk

brenner650 said:
I am afraid that downgrade to 5.0.1 is not possible, at least I dont know anyone who succedeed in doing that.
If you were on systemless root, probably your Knox is still 0, check it in DL mode, if it is and you have the phone less that 3 yrs (1 yr warranty+2yrs factory warranty) best solution would be to ask in Samsung repair center if the factory warranty would be accepted (ofcourse dont mention flashing, just say you tried official update, and play dumb).
If not you can try custom kernel wich will bypass DRK, and prolly make the phone bootable, but there is no guarantee everything will work well (maybe it will, but mostly it doesnt, forget using Samsung pay, and KNOX tripped)
As for EFS, maybe I am wrong, but I think EFS contains IMEI and sn info, and DRK is something else.
Click to expand...
Click to collapse
Thanks for your reply!!.
I took my S6 (925F) to a Samsung service center as you said. However, they told me that my S/N was incorrect (I bought a second-hand S6 edge, I think someone changed it) so they couldn't fix it.
Now I'm trying to use SmartSwitch to do a factory reset but it asks me for the S/N and I don't have the original one, just a S/N from a non edge S6 (920F). How can I do the factory reset without my S/N??? Can I use the serial number from another 925F??

Now I'm trying to find an engineering bootloader, to bypass the R/L and flash CF-AutoRoot, custom recovery.... but I only find it for 5.0.1 or... for galaxy S6 G925T, not F.

Finally, I managed to fix my S6 by myself!! (not really, but at least it boots...)
This is what I did:
- I found a factory binary for my S6 so I flashed it via ODIN
- I flashed a 6.0.1 ROM without hidden and without cache
Then it boots without any problems. However, now I can't get into recovery
I hope this will help someone