Database Users

S7 Edge G935F // Faulty ODIN flash // Stuck in Bootloader [SOLVED]

Hi Guys,
today I wanted to flash the latest Stock ROM for my device via ODIN. I've done this many times before and (thought) I knew what I was doing. It is my third Phone frome the same carrier and none of them were branded/ locked devices before. Unfortunatly I wasn't aware that this particular device was locked.
After downloading the international firmware I tried to install it and ODIN got stuck while writing the system.img. After that my phone did not boot up (of course). After that I downloaded and tried to isntall the firmware of the carrier, but I had the exact same issue. When I turn my device on I get to an error screen which tells me to execute an "emergency recovery" via the Samsung smart switch software. But it too gets stuck on some point and only gets me to an error screen.
FRP hinders me to install a custom recovery and the stock one does not allow any isntallations via ADB or SD card.
My qustion is: Does anyone know how I can install a rom from here?
I know that I had to have made some changes prior to the flashing, but as I said I was not aware and an Idiot for not double checking.
Since it is not bricked yet I suppose there must be an answer but I can't find anything.
Thanks in advance
Edit:
After only installing the stock bootloader, I am autmaticly entering it when I boot my devive. On the bottom of the screen is an error message: "dm-verity verification failed...
E:failed to mount /system (invalid argument)"

Fix
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.

fabivons said:
hi guys,
today i wanted to flash the latest stock rom for my device via odin. I've done this many times before and (thought) i knew what i was doing. It is my third phone frome the same carrier and none of them were branded/ locked devices before. Unfortunatly i wasn't aware that this particular device was locked.
After downloading the international firmware i tried to install it and odin got stuck while writing the system.img. After that my phone did not boot up (of course). After that i downloaded and tried to isntall the firmware of the carrier, but i had the exact same issue. When i turn my device on i get to an error screen which tells me to execute an "emergency recovery" via the samsung smart switch software. But it too gets stuck on some point and only gets me to an error screen.
Frp hinders me to install a custom recovery and the stock one does not allow any isntallations via adb or sd card.
My qustion is: Does anyone know how i can install a rom from here?
I know that i had to have made some changes prior to the flashing, but as i said i was not aware and an idiot for not double checking.
Since it is not bricked yet i suppose there must be an answer but i can't find anything.
Thanks in advance
edit:
After only installing the stock bootloader, i am autmaticly entering it when i boot my devive. On the bottom of the screen is an error message: "dm-verity verification failed...
E:failed to mount /system (invalid argument)"
Click to expand...
Click to collapse
have u solved your problem ? This problem i am facing on the s7edge nougat ? Plz help ?

Hey,
look at the second post I made in this thread. There is described how I got my S7 up and running again. I'm not sure if it is a valid solution since it felt like trial and error to me, but I'm writing this text from my S7 so it might be worth a try!
Good luck!

Fabivons said:
Hey,
look at the second post I made in this thread. There is described how I got my S7 up and running again. I'm not sure if it is a valid solution since it felt like trial and error to me, but I'm writing this text from my S7 so it might me worth a try!
Good luck!
Click to expand...
Click to collapse
y i have done that and the device boots up but some applications force close and when i insert the memory card , the phone gets restarted everytime

Fabivons said:
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.
Click to expand...
Click to collapse
Tell us in detail now.

SjDU said:
Tell us in detail now.
Click to expand...
Click to collapse
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.

Fabivons said:
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.
Click to expand...
Click to collapse
the time when u were fixing your device , you were on marshmallow or nougat ? beacuse i am on nougat and whenever i flash twrp , it stucks there and not booting into it even i have ticked the oem unlock and usb debugging in developer mode ?

suhaibahmad said:
the time when u were fixing your device , you were on marshmallow or nougat ? beacuse i am on nougat and whenever i flash twrp , it stucks there and not booting into it even i have ticked the oem unlock and usb debugging in developer mode ?
Click to expand...
Click to collapse
Does the TWRP flash complete? Can you boot up the OS after you flashed TWRP? (And did you download the correct version of TWRP for your device?)
As a last resort, you could try and flash marshmallow on your device and see if it works there.

Fabivons said:
Does the TWRP flash complete? Can you boot up the OS after you flashed TWRP? (And did you download the correct version of TWRP for your device?)
As a last resort, you could try and flash marshmallow on your device and see if it works there.
Click to expand...
Click to collapse
if i flash marshmallow it doesnt even boot up and in the odin mode showing binary and everything as custom , if i flash nougat and then flash twrp and try to manually boot into twrp it stucks on the s7edge screen which comes before recovery , and if i boot the mobile normally without the button combination then it stucks on the second logo SAMSUNG . if i flash again the stock recovery then boots normally

suhaibahmad said:
if i flash marshmallow it doesnt even boot up and in the odin mode showing binary and everything as custom , if i flash nougat and then flash twrp and try to manually boot into twrp it stucks on the s7edge screen which comes before recovery , and if i boot the mobile normally without the button combination then it stucks on the second logo SAMSUNG . if i flash again the stock recovery then boots normally
Click to expand...
Click to collapse
Have you tried to perform a regular factory reset via the OS on nougat? Sometimes that does the job, too.
But as I said. I can only give you my best guess here - my phone worked after my procedure, so I didn't investigate further.
And don't forget: Google is your friend.

Fabivons said:
Have you tried to perform a regular factory reset via the OS on nougat? Sometimes that does the job, too.
But as I said. I can only give you my best guess here - my phone worked after my procedure, so I didn't investigate further.
And don't forget: Google is your friend.
Click to expand...
Click to collapse
thats your kindness , yes i have performed the factory reset several times from recovery , but when i trying to reset it from settings , it goes after restart to recovery with dm-verity error , then i wipe and factory reset from there

Fabivons said:
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.
Click to expand...
Click to collapse
Fabivons said:
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.
Click to expand...
Click to collapse
Well I had the same issue but Odin method didn't work for me on Nougat. And also FRP lock was On. every time I flashed the files it give me FRP on error. so I had to use Smartswitch. Even though I used original csc and ap files with latest Odin. BTW I have SM-G935FD model

SjDU said:
Well I had the same issue but Odin method didn't work for me on Nougat. And also FRP lock was On. every time I flashed the files it give me FRP on error. so I had to use Smartswitch. Even though I used original csc and ap files with latest Odin. BTW I have SM-G935FD model
Click to expand...
Click to collapse
Well FRP has to be turned off (the button in the menu is called "OEM unlock, the button has to be set to on which deactivates FRP). You don't mention using a PIT file - did you use one?

This is a case of expert , please have a look because nobody solved it ....

i cant root my s7edge , the latest nougat february patch installed ? am i the only one ? i untick the auto reboot in odin and manually boot into twrp after flashing it but its stucked thereand not booting into it , it is the latest twrp hero2lte 3.1.0.
i cant even flash rom on odin or through smart switch , it fails in the modem part . when i flash without the modem then flash successfully but after flash reboot and for a minute NO COMMAND screen appears , after a minute goes into recovery and saying DM VERIFICATION FAILURE .after this when i flash the csc again , the no command prompt disappear telling NO SINGLE SKU SUPPORT and dm-verity error...., then when i reboot it , the phone boots normally but keeps on crashing the applications and force closed and sometimes reboot.
The imei is normal and signals of sim works fine. On PHONE INFO application it shows that the csc is missing . The hidden codes are not working like *#0*# , *#06# etc etc .
plz someone tell me whats the issue is ? is it a hardware or software ? will jtag resolve the issue ? i dont even know about wat is jtag , i have just heard about it . Long time passed the device price decreased in the market about 200 dollars and no solution , kept in the cupboard. I hope i can get info atleast ,i have many posts here but nobody responses . maybe i am the only one who is facing this issue .

I've had that kind of problems with other samsung phone. I had to use adb and fastboot to get recovery working.
so you still have stock recovery? have you tried factory reset?

yaro666 said:
I've had that kind of problems with other samsung phone. I had to use adb and fastboot to get recovery working.
so you still have stock recovery? have you tried factory reset?
Click to expand...
Click to collapse
yes i am on stock recovery , also tried factory reset .
tell me how did u do with fastboot ? i think fastboot works on rooted phone right ?

I'm not 100% sure, it was in bootloader mode and I don't know if s7 has the same procedure. you should start with enabli g usb debugging and unlocking bootloader.
are you sure you have exynos version?

yaro666 said:
I'm not 100% sure, it was in bootloader mode and I don't know if s7 has the same procedure. you should start with enabli g usb debugging and unlocking bootloader.
are you sure you have exynos version?
Click to expand...
Click to collapse
usb debugging is enabled , it is g935f model , on samsung smartswitch it is detected as o2u model

suhaibahmad said:
i cant root my s7edge , the latest nougat february patch installed ? am i the only one ? i untick the auto reboot in odin and manually boot into twrp after flashing it but its stucked thereand not booting into it , it is the latest twrp hero2lte 3.1.0.
i cant even flash rom on odin or through smart switch , it fails in the modem part . when i flash without the modem then flash successfully but after flash reboot and for a minute NO COMMAND screen appears , after a minute goes into recovery and saying DM VERIFICATION FAILURE .after this when i flash the csc again , the no command prompt disappear telling NO SINGLE SKU SUPPORT and dm-verity error...., then when i reboot it , the phone boots normally but keeps on crashing the applications and force closed and sometimes reboot.
The imei is normal and signals of sim works fine. On PHONE INFO application it shows that the csc is missing . The hidden codes are not working like *#0*# , *#06# etc etc .
plz someone tell me whats the issue is ? is it a hardware or software ? will jtag resolve the issue ? i dont even know about wat is jtag , i have just heard about it . Long time passed the device price decreased in the market about 200 dollars and no solution , kept in the cupboard. I hope i can get info atleast ,i have many posts here but nobody responses . maybe i am the only one who is facing this issue .
Click to expand...
Click to collapse
I flashed the firmware all back to stock then i flashed twrp in odin and you need to use the supersu beta sr3 (you need to see if it is the sr3 supersu beta), only this work in nougat. follow the steps to root like always

GuevaraJezuss said:
I flashed the firmware all back to stock then i flashed twrp in odin and you need to use the supersu beta sr3 (you need to see if it is the sr3 supersu beta), only this work in nougat. follow the steps to root like always
Click to expand...
Click to collapse
the supersu can be flashed in twrp and i cant boot into twrp ?i have tried couple of times , flash firmware through odin and then untick auto reboot and flash twrp by enabling developer oem unlock option , everything i have tried ,

Try to use superman rom. It support root inside

ledanh89 said:
Try to use superman rom. It support root inside
Click to expand...
Click to collapse
to flash superman rom , i need twrp but the main problem ia i cant boot into twrp ?

suhaibahmad said:
i cant root my s7edge , the latest nougat february patch installed ? am i the only one ? i untick the auto reboot in odin and manually boot into twrp after flashing it but its stucked thereand not booting into it , it is the latest twrp hero2lte 3.1.0.
i cant even flash rom on odin or through smart switch , it fails in the modem part . when i flash without the modem then flash successfully but after flash reboot and for a minute NO COMMAND screen appears , after a minute goes into recovery and saying DM VERIFICATION FAILURE .after this when i flash the csc again , the no command prompt disappear telling NO SINGLE SKU SUPPORT and dm-verity error...., then when i reboot it , the phone boots normally but keeps on crashing the applications and force closed and sometimes reboot.
The imei is normal and signals of sim works fine. On PHONE INFO application it shows that the csc is missing . The hidden codes are not working like *#0*# , *#06# etc etc .
plz someone tell me whats the issue is ? is it a hardware or software ? will jtag resolve the issue ? i dont even know about wat is jtag , i have just heard about it . Long time passed the device price decreased in the market about 200 dollars and no solution , kept in the cupboard. I hope i can get info atleast ,i have many posts here but nobody responses . maybe i am the only one who is facing this issue .
Click to expand...
Click to collapse
anybody got the same issue , plz ?

Custom Binary Blocked By FRP Lock

I was trying to root my phone
odin failed and my phone showed "Custom Binary (Recovery): Blocked By FRP Lock"
I was following this video
https://www.youtube.com/watch?v=M8ji0yjf7IY
What went wrong ?

johngr77 said:
Probably you forgot to enable OEM unlock in developer options menu
Click to expand...
Click to collapse
I did that and I successfully installed the twrp file
Then the phone rebooted and now it is stuck in the Samsung logo !!
What should I do ?

look through this forum - i only put the answer on here yesterday

JUST FLASH with latest stock firmware.. 1st of all to get phone into main screen/ activation lock screeen

asadnow2k said:
JUST FLASH with latest stock firmware.. 1st of all to get phone into main screen/ activation lock screeen
Click to expand...
Click to collapse
I did that and its working again
But How can I root it now ?
I tried rooting it again the same way but it got stuck on logo screen again !
is there any alternative way to root it ?

HussainJH said:
I did that and its working again
But How can I root it now ?
I tried rooting it again the same way but it got stuck on logo screen again !
is there any alternative way to root it ?
Click to expand...
Click to collapse
you just install frimware latest one and activate it with ur google account. than oem unlock than flash with root via odin

Im having this issue with my phone i accidently ticked off the oem unlock in development settings I put the phone in download mode because thats the only mode i can get into (recovery and regular boot does not work) when I connect to pc now it shows up as usb serial device in ports or it shows up as samsung modem and odin wont flash the firmware

I never had any issue. You get a single recovery.IMG and flash it. The s6e+ is tricky. You should have a custom ROM or what you want to flash ready and just flash twrp, boot immediately into it. Backup phone via twrp then wipe it and flash custom ROM. This will ensure you don't get any real issues or fpr blocked. Also use XDA tuts or get help here, YouTube can go good or bad. Recovery images are device specific. If you have f and flash t it won't work. You have to really look at what you are flashing and match model information. I'm seeing a lot of people fpr blocked and in trouble. I might go make a little walkthrough

Huawei bricked

today i want to share my sad story with u guys , i got my phone huawe mla-al10 , i flash custom rom lineage os 13.1 from xda for huawei can-11 then it got bootloop , before this i succesfully install it without bootloop , so i decide to reset , then i go to the recovery , idk how my recovery become the stock one ,then i click format data , suddenly its stuck at 61% then keep reboot , i open fastboot then get frp locked , im start panic , then i do a research how to get rid frp locked , they said relock the bootloader , then i relock booatlader , haa its getting more worse , now icant even go to fastboot or update mood , its only goes to factory reset lowlevel.... then screen becomes black with blue led , i connect to pc , i found hs-usb diagnostic 9006 ( com 3 ) thats mean i can unbrick only with 1 way , with Snapdragoon flashtool , but i cant find nowhere for the firmware that make to unbrick using flashtool for my devices , hmmm im so sad right now , is there any way i can make my own flashtool file for snapdragon flashtool ? i hope i can fix this as soon as possible

If ADB is working,just flash your original (firmware) RECOVERY,BOOT and SYSTEM.img from the update.app zip file...after flashing those 3 img file,just reboot via adb...fastboot reboot
Phone should be like new

virusdunil said:
If ADB is working,just flash your original (firmware) RECOVERY,BOOT and SYSTEM.img from the update.app zip file...after flashing those 3 img file,just reboot via adb...fastboot reboot
Phone should be like new
Click to expand...
Click to collapse
to make adb working i need to enable usb debugging bla4 but my phone is totally dead , no fastboot nothing i can do except go to edl modee

shazlieyazizan1 said:
to make adb working i need to enable usb debugging bla4 but my phone is totally dead , no fastboot nothing i can do except go to edl modee
Click to expand...
Click to collapse
same problem adb is also not working did you find any solution?
I am having a problem i didnt do anything with my phone its huawei nova plus just 1 or 2 day ago open the boxed and try to update it using firmware finder app after downloading the full ota phone automatically restart and stuck on installing update 5% and its still on boot loop am not able to flash any firmware using sd card or update.app just because it always failed on 5 % even though am not able to wipe factory/reset it also failing. Can you guys please help me? to solve the problem?

abuapka said:
same problem adb is also not working did you find any solution?
I am having a problem i didnt do anything with my phone its huawei nova plus just 1 or 2 day ago open the boxed and try to update it using firmware finder app after downloading the full ota phone automatically restart and stuck on installing update 5% and its still on boot loop am not able to flash any firmware using sd card or update.app just because it always failed on 5 % even though am not able to wipe factory/reset it also failing. Can you guys please help me? to solve the problem?
Click to expand...
Click to collapse
try get correct model from huawei updater finder ..
if dload method not work then try to go to fastboot mode by tgis way >> Turn off your mobile and just click and hold on DOWN vol then connect it with usb it should work !

Bricked S7 Edge?

Recently, I turned off developer options in my rooted S7 Edge (SM-G935FD). Idk if that is the cause, but after rebooting I got the error "Custom Binary Blocked by FRP Lock". I couldnt boot into my recovery (TWRP) either. I was running on Oreo btw. I watched some Youtube guides and apparently the solution was to flash stock rom. So... I flashed an Oreo Stock Rom on my phone via Odin. I thought that would solve my problem, but instead it made it worse. It didnt give me the Custom Binary Blocked by FRP lock error but my boot screen is stuck at the boot animation (not a bootloop). I could boot into the stock recovery tho. I tried a factory reset, that didnt make things better. I could also boot into download mode. I thought I made a mistake, so I flashed like 5-8 times with both CSC an Home_CSC. The result was the same, it would get stuck at the boot animation. I tried flashing TWRP via Odin too, but it said "Custom Binary (Recovery) blocked by FRP Lock". I tried sideloading that TWRP file to my device via ADB. It gave me an error too (I think "Cannot flash from external devices" or something like that) I thought flashing with Re-partition and Nand Erase On would solve my problem, so I tried that, but it didnt work. Im running on Binary 3 apparently. Is there anything I can do?

Rapidfayaround said:
Recently, I turned off developer options in my rooted S7 Edge (SM-G935FD). Idk if that is the cause, but after rebooting I got the error "Custom Binary Blocked by FRP Lock". I couldnt boot into my recovery (TWRP) either. I was running on Oreo btw. I watched some Youtube guides and apparently the solution was to flash stock rom. So... I flashed an Oreo Stock Rom on my phone via Odin. I thought that would solve my problem, but instead it made it worse. It didnt give me the Custom Binary Blocked by FRP lock error but my boot screen is stuck at the boot animation (not a bootloop). I could boot into the stock recovery tho. I tried a factory reset, that didnt make things better. I could also boot into download mode. I thought I made a mistake, so I flashed like 5-8 times with both CSC an Home_CSC. The result was the same, it would get stuck at the boot animation. I tried flashing TWRP via Odin too, but it said "Custom Binary (Recovery) blocked by FRP Lock". I tried sideloading that TWRP file to my device via ADB. It gave me an error too (I think "Cannot flash from external devices" or something like that) I thought flashing with Re-partition and Nand Erase On would solve my problem, so I tried that, but it didnt work. Im running on Binary 3 apparently. Is there anything I can do?
Click to expand...
Click to collapse
I still have the "FRP Lock: On" on download mode, so I tried bypassing FRP lock via binary 5 combination firmware and flashing a binary 7 stock firmware. This time, it doesnt get stuck at the boot animation, instead it redirects to a screen with an android face saying "Installing System updates". A few seconds later, it says "No command" with a dead android face. Then it reboots and the same thing happens. Basically a boot loop, but in a different way. I cant seem to boot to stock recovery either. The worst thing is that I cant even turn off the thing. I have to leave it loop for the entire day until its battery dies

Rapidfayaround said:
I still have the "FRP Lock: On" on download mode, so I tried bypassing FRP lock via binary 5 combination firmware and flashing a binary 7 stock firmware. This time, it doesnt get stuck at the boot animation, instead it redirects to a screen with an android face saying "Installing System updates". A few seconds later, it says "No command" with a dead android face. Then it reboots and the same thing happens. Basically a boot loop, but in a different way. I cant seem to boot to stock recovery either. The worst thing is that I cant even turn off the thing. I have to leave it loop for the entire day until its battery dies
Click to expand...
Click to collapse
after flashing the combination firmware, flash the stock firmware and go thru the boot process

Youdoofus said:
after flashing the combination firmware, flash the stock firmware and go thru the boot process
Click to expand...
Click to collapse
That is what I literally did. I flashed a combination firmware, factory rested my entire phone, turned on developer options as well as allow usb debugging, attempted to reset FRP via Z3X Samsung Tool Pro and finally flashed a stock rom. And, the result is this. A bootloop with an android face dying. I did manage to enter a different screen by pressing volume up once along with pressing volume down and power button. It said "could not open recovery_because_no file directory" and had some more errors. The thing is....I made it worse at the first place. I could have flashed a room with binary 6 or lower, cuz at least the combination firmware would have been available to flash, but my stupid brain did not think of that. I flashed a binary 7 stock rom and there is no combination firmware with a binary of 7 or more. Which means, I will most likely get the "SW check fail Device: 7 Binary: 6 " error while flashing.

Rapidfayaround said:
That is what I literally did. I flashed a combination firmware, factory rested my entire phone, turned on developer options as well as allow usb debugging, attempted to reset FRP via Z3X Samsung Tool Pro and finally flashed a stock rom. And, the result is this. A bootloop with an android face dying. I did manage to enter a different screen by pressing volume up once along with pressing volume down and power button. It said "could not open recovery_because_no file directory" and had some more errors. The thing is....I made it worse at the first place. I could have flashed a room with binary 6 or lower, cuz at least the combination firmware would have been available to flash, but my stupid brain did not think of that. I flashed a binary 7 stock rom and there is no combination firmware with a binary of 7 or more. Which means, I will most likely get the "SW check fail Device: 7 Binary: 6 " error while flashing.
Click to expand...
Click to collapse
If the device is still entering download mode, install the recent version of stock for your device. Maybe that will solve your problem.

Rapidfayaround said:
That is what I literally did. I flashed a combination firmware, factory rested my entire phone, turned on developer options as well as allow usb debugging, attempted to reset FRP via Z3X Samsung Tool Pro and finally flashed a stock rom. And, the result is this. A bootloop with an android face dying. I did manage to enter a different screen by pressing volume up once along with pressing volume down and power button. It said "could not open recovery_because_no file directory" and had some more errors. The thing is....I made it worse at the first place. I could have flashed a room with binary 6 or lower, cuz at least the combination firmware would have been available to flash, but my stupid brain did not think of that. I flashed a binary 7 stock rom and there is no combination firmware with a binary of 7 or more. Which means, I will most likely get the "SW check fail Device: 7 Binary: 6 " error while flashing.
Click to expand...
Click to collapse
the "no such file or directory" error is due to either having had removed stock recovery in flashing the firmwares or the factory recovery corrupted due to likely the same reason. Just flash a revision 7 firmware for your phone and it will at least boot
Dark Stranger said:
If the device is still entering download mode, install the recent version of stock for your device. Maybe that will solve your problem.
Click to expand...
Click to collapse
^^^ this ^^^

Dark Stranger said:
If the device is still entering download mode, install the recent version of stock for your device. Maybe that will solve your problem.
Click to expand...
Click to collapse
I have literally flashed the latest stock rom for my device and my country which is G935FXXS7ESK8.
I am a bit confused tho...I am not sure if my device is SM-G935FD or SM-G935F. The download mode says SM-G935F...but this phone used to work with a SM-G935FD rom back in the days. Is this causing the problem most likely? And btw the repair shop said they cant fix it too

Rapidfayaround said:
I have literally flashed the latest stock rom for my device and my country which is G935FXXS7ESK8.
I am a bit confused tho...I am not sure if my device is SM-G935FD or SM-G935F. The download mode says SM-G935F...but this phone used to work with a SM-G935FD rom back in the days. Is this causing the problem most likely? And btw the repair shop said they cant fix it too
Click to expand...
Click to collapse
I am somehow relieved to know that someone else on this planet is on the same (EXACT) boat as me....this is what we get for messing around too much with our phone hum?
1 - After booting up my phone I get the blue background with a dead Android and "No Command" message
2 - I tried accessing recovery by pressing Power+Home+VolumeUp, but all I get is a black screen with a wall of code lines with "fail to open recovery_cause(No such file or directory)" at the beggining of the text.
3 - "No problem! I'll just flash TWRP with ODIN and install a custom ROM and be done with it!".
..NOPE! FRP(factory reset protection) is ON!!! I cannot install TWRP
4- I've tried to find a combination file with binary version 7...but looks like the internet doesn't seem to care about the good ol' number 7...All I can find is binary version 6.
What Im trying to do now is creating my own combination file binary version 7 (if that's even a thing...) from a stock firmware. But I'm not getting any luckier down this path.
Looks like we need a hero...:crying:

PseudoNoob said:
I am somehow relieved to know that someone else on this planet is on the same (EXACT) boat as me....this is what we get for messing around too much with our phone hum?
1 - After booting up my phone I get the blue background with a dead Android and "No Command" message
2 - I tried accessing recovery by pressing Power+Home+VolumeUp, but all I get is a black screen with a wall of code lines with "fail to open recovery_cause(No such file or directory)" at the beggining of the text.
3 - "No problem! I'll just flash TWRP with ODIN and install a custom ROM and be done with it!".
..NOPE! FRP(factory reset protection) is ON!!! I cannot install TWRP
4- I've tried to find a combination file with binary version 7...but looks like the internet doesn't seem to care about the good ol' number 7...All I can find is binary version 6.
What Im trying to do now is creating my own combination file binary version 7 (if that's even a thing...) from a stock firmware. But I'm not getting any luckier down this path.
Looks like we need a hero...:crying:
Click to expand...
Click to collapse
OMGGGGGGGG....Looks like I am not the only one. DAMN. Bro...tell me if you find a solution ok? Hopefully there is a way to solve this problem...there has to be one. And share your combination firmware after you finish it. Thank you very much

Rapidfayaround said:
OMGGGGGGGG....Looks like I am not the only one. DAMN. Bro...tell me if you find a solution ok? Hopefully there is a way to solve this problem...there has to be one. And share your combination firmware after you finish it. Thank you very much
Click to expand...
Click to collapse
No luck over here friend...
Desperate times require desperate measures. Have you ever tried flashing combination files from different S7 Edge versions?
I can find files for the G935A with a revision 7 of the binary...Im thinking flashing it into my G935F and see what happens. I've read the risks associated with installing firmwares from other phone versions, but I'll have a paperweight either way.
I'll keep this thread updated.

Rapidfayaround said:
I have literally flashed the latest stock rom for my device and my country which is G935FXXS7ESK8.
I am a bit confused tho...I am not sure if my device is SM-G935FD or SM-G935F. The download mode says SM-G935F...but this phone used to work with a SM-G935FD rom back in the days. Is this causing the problem most likely? And btw the repair shop said they cant fix it too
Click to expand...
Click to collapse
Doesn't really matter if you have a F or FD. I'd say you flash the latest stock rom for G935F or FD(which ever is latest) for any country regardless. By this you should be able to boot and won't get any odin errors.

UsmaniMustafa said:
Doesn't really matter if you have a F or FD. I'd say you flash the latest stock rom for G935F or FD(which ever is latest) for any country regardless. By this you should be able to boot and won't get any odin errors.
Click to expand...
Click to collapse
Can you provide me the link plz.

Turns out, its a hardware problem with the storage. Replacing the motherboard might be the solution I think. :/

I had solved my phone last day
At first u can flash ur phone to leatest stock rom. Then u have to turn of frp lock. Then u will able to boot up your phone. If u cant fix u can knock me on facebook. (If u r a z3x user). Bcoz u need z3x for bypass frp with ufs cable.
Im also using s7 edge.

hazratboss said:
At first u can flash ur phone to leatest stock rom. Then u have to turn of frp lock. Then u will able to boot up your phone. If u cant fix u can knock me on facebook. (If u r a z3x user). Bcoz u need z3x for bypass frp with ufs cable.
Im also using s7 edge.
Click to expand...
Click to collapse
Oh ok I will contact you

hazratboss said:
At first u can flash ur phone to leatest stock rom. Then u have to turn of frp lock. Then u will able to boot up your phone. If u cant fix u can knock me on facebook. (If u r a z3x user). Bcoz u need z3x for bypass frp with ufs cable.
Im also using s7 edge.
Click to expand...
Click to collapse
Does it matter if I use the cracked version without box. And no, I dont have the ufs cable. Is there anything else I can do?

Hi guys, I have the exact same problem with my S7 edge from T-mobile (g935t). Odin will only accept for flash the latest rom and after flash it reboots but I get BSOD. I tried a pit file also from an old g935T rom which was android 6.0 and I managed to get into recovery for a moment and I did a factory reset/wipe cache but after reboot entered again in a black screen and the blue led was lit. I finally removed the battery to turn the phone off. I can still enter download mode but is there anything else I can do to resurrect the phone?

Samsung s7 edge (g935f)
Hi everyone , please am having issue of NO COMMAND and i cant boot into recovery. My oem is on so i cant install twpr neither. Am on binary u8. Please any solution to recover my phone?

Very very good new guys...yep you guessed it right. I was able to fix this problem.
How you may ask? Follow these steps
Note: Make sure you have enough battery. Lack of battery charge in my case caused alot of problems.
1. Download a U7 Rom for your SM-G935F or SM-G935FD
2. Extract the Rom as well as the AP
3. After you extract the AP, you will be greeted with boot.lz4.img , recovery.lz4.img , system.lz4.img & meta-data
4. Make a backup of recovery.lz4.img and meta-data just in case. Also, make a copy of boot.lz4.img and rename the copied one to recovery.lz4.img. Don't forget to delete the original recovery and meta-data
5. Now, you should be left with boot.lz4.img , (modified) recovery.lz4.img and system.lz4.img.
6. Now, download this https://www.mediafire.com/file/ah20ha869prdkkc/Autotar2.0_By_FixFirmwares.com.rar/file
7. Now, make a .md5 file that contains (modified) recovery.lz4.img and system.lz4.img
8. After you are done making that .md5, flash it along with CSC, CP and BL.
9. You should directly boot into your device, (if you do), charge your phone for a while if the battery is lower than 20%.
10. Then, go to the settings and enable OEM Unlock before doing ANYTHING
11. Then, reboot to download mode and flash TWRP
12. Download the no-verity-encryption.zip
https://zackptg5.com/android.php#disverfe
13. Allow system modifications and format data (NOT WIPE)
14. If that doesn't work, go to TWRP, connect it to your PC and copy the no-verity-encryption.zip file and install it
15. If that still doesn't work then, follow this tutorial
https://www.google.com/amp/s/forum....niversal-dm-verity-forceencrypt-t3817389/amp/
16. Then, you should boot and yea...enjoy ?
If this method doesn't work then, you need to try different combinations.
Try packing these files in AP
1. Boot.lz4.img, (Modified) Recovery.lz4.img & system.lz4.img
2. (Modified) Recovery.lz4.img & system.lz4.img
3. Meta-data, Boot.lz4.img, (Modified) Recovery.lz4.img & system.lz4.img
If that doesn't work, I'm sorry this is how I fixed it. ?*
For anyone wondering how I fixed it well, firstly a HUGE THANKS TO @shah22 & @Tapas27sTapas2. This would have been LITERALLY IMPOSSIBLE WITHOUT THEM. So, basically I tried an AP with renamed recovery.lz4.img and system.lz4.img only along with CP, CSC and BL. Due to my phone having literally 0%, this journey was very difficult.
Feel free to ask any question

Very very good new guys...yep you guessed it right. I was able to fix this problem.
How you may ask? Follow these steps
Note: Make sure you have enough battery. Lack of battery charge in my case caused alot of problems.
1. Download a U7 Rom for your SM-G935F or SM-G935FD
2. Extract the Rom as well as the AP
3. After you extract the AP, you will be greeted with boot.lz4.img , recovery.lz4.img , system.lz4.img & meta-data
4. Make a backup of recovery.lz4.img and meta-data just in case. Also, make a copy of boot.lz4.img and rename the copied one to recovery.lz4.img. Don't forget to delete the original recovery and meta-data
5. Now, you should be left with boot.lz4.img , (modified) recovery.lz4.img and system.lz4.img.
6. Now, download this https://www.mediafire.com/file/ah20ha869prdkkc/Autotar2.0_By_FixFirmwares.com.rar/file
7. Now, make a .md5 file that contains (modified) recovery.lz4.img and system.lz4.img
8. After you are done making that .md5, flash it along with CSC, CP and BL.
9. You should directly boot into your device, (if you do), charge your phone for a while if the battery is lower than 20%.
10. Then, go to the settings and enable OEM Unlock before doing ANYTHING
11. Then, reboot to download mode and flash TWRP
12. Download the no-verity-encryption.zip
https://zackptg5.com/android.php#disverfe
13. Allow system modifications and format data (NOT WIPE)
14. If that doesn't work, go to TWRP, connect it to your PC and copy the no-verity-encryption.zip file and install it
15. If that still doesn't work then, follow this tutorial
https://www.google.com/amp/s/forum....niversal-dm-verity-forceencrypt-t3817389/amp/
16. Then, you should boot and yea...enjoy ?
If this method doesn't work then, you need to try different combinations.
Try packing these files in AP
1. Boot.lz4.img, (Modified) Recovery.lz4.img & system.lz4.img
2. (Modified) Recovery.lz4.img & system.lz4.img
3. Meta-data, Boot.lz4.img, (Modified) Recovery.lz4.img & system.lz4.img
If that doesn't work, I'm sorry this is how I fixed it. ?*
For anyone wondering how I fixed it well, firstly a HUGE THANKS TO @shah22 & @Tapas27s. This would have been LITERALLY IMPOSSIBLE WITHOUT THEM. So, basically I tried an AP with renamed recovery.lz4.img and system.lz4.img only along with CP, CSC and BL. Due to my phone having literally 0%, this journey was very difficult.
Feel free to ask any question