Related
Okay first post on this website.
4.4.2, i9505
So, as i am a compete android n00b, i rooted my s4 with the KingoRoot tool as i thought it was an easy method, later i found out ChainFire made an easy auto root .
After i rooted with the kingo my device would randomly reboot, when i called someone, when i locked my phone and random stages throughout the day.
After some reading online i found the solution was to re-flash my phone to stock fireware. so i downloaded odin, drivers, fireware from sam and tried to re-flash it. however my phone failed after aboot.mbn. I then got the unexpected error saying the phone had to be plugged into kies etc.
I then used "philz_touch_6.07.9-i9300.tar.md5" to get rid of the error message which worked. however the phone still would radnomly restart.
Again i turnrf to the web to find a solution for the radnom booting and found this -
http://forum.xda-developers.com/showthread.php?t=2514703
telling me to delete everythinhg knox basically. after deleting everything outlined my phone is now stuck on the samsung logo.
i cannot access recovery mode! however can access download mode. but i have tried multiple times to re-flash to stock firmware to no avail...
Help, please
Recap
- Stuck on samsung logo
- Cant access recovery mode
- Can access download mode
- Deleted everything knox as specified
Thanks, Dylan
1. The error that give u ODIN is coz you are trying to flash an older firmware that the one you have installed in your device.
2. You have to flash a STOCK recovery. Flash this file via ODIN in PDA/AP (like in the pic 1 attached): HERE.
3. Turn off your device manually when the process finish. Boot it into STOCK RECOVERY by pressing and holding Volume Up, Home and Power.
4. Take a look the CSC (pic 2). "Applied the CSC-code: ............" <- This is your REAL CSC. Turn off your device again manually and boot it into DOWNLOAD MODE by pressing and holding Volume Down, Home and Power.
5. Go to Sammobile and download the LATEST firmware for your device with correct CSC and flash it via ODIN.
6. About KNOX and reboots: Delete all KNOX reminds less "Lib = libknox_encryption.so".
7. Good luck
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?
Hi,
I realy need your help,
I have a S7 edge who is stuck at the samsung logo.
I have flashed some stock rom (all in 7.0) via odin 3.12 after a wipe factory but nothing. So i decided to try it with Kies and smartSwitch but still nothing.
I have access to recovery and download mode.
FRP lock: On
The phone is not rooted, and the usb debugging not enabled.
The phone print this in the download mode:
ODIN MODE
Download speed: FAST
Product-Name: SM-G935F
Current Binary: Samsung Official
System Status: Custom
FRP lock: ON
Secure Downlaod: Enabled
Warranty Void: 0(0x000)
RP SWREV: B:1 K:0 S:0
After the installation of the flashed rom in the download mode, the phone reboot with a blue screen, a progress bar but it stop to 32%, and then it is printed "erasing.." and the phone reboot and is still stuck.
I have re-tryed with Kies, now the phone is with a green screen with 2 white Gears : "android is starting" but it is still stuck (i let him all the night but nothing)
i don't know what to do
nonechap said:
Hi,
I realy need your help,
I have a S7 edge who is stuck at the samsung logo.
I have flashed some stock rom (all in 7.0) via odin 3.12 after a wipe factory but nothing. So i decided to try it with Kies and smartSwitch but still nothing.
I have access to recovery and download mode.
FRP lock: On
The phone is not rooted, and the usb debugging not enabled.
The phone print this in the download mode:
ODIN MODE
Download speed: FAST
Product-Name: SM-G935F
Current Binary: Samsung Official
System Status: Custom
FRP lock: ON
Secure Downlaod: Enabled
Warranty Void: 0(0x000)
RP SWREV: B:1 K:0 S:0
After the installation of the flashed rom in the download mode, the phone reboot with a blue screen, a progress bar but it stop to 32%, and then it is printed "erasing.." and the phone reboot and is still stuck.
I have re-tryed with Kies, now the phone is with a green screen with 2 white Gears : "android is starting" but it is still stuck (i let him all the night but nothing)
i don't know what to do
Click to expand...
Click to collapse
You have to use smart switch emergency recovery function to restore your phone. It is a stand alone function within smart switch.
All you need is your phone model and serial number.
Apparently you missed a step when preparing your phone for flashing.
Or you can continue to use Odin which when you plug the USB in will show that a connection is made even though the phone says it's not in download mode.
Cosmic Blue said:
You have to use smart switch emergency recovery function to restore your phone. It is a stand alone function within smart switch.
All you need is your phone model and serial number.
Apparently you missed a step when preparing your phone for flashing.
Click to expand...
Click to collapse
I did an emergency recovery with my phone model and serial, same with kies.
nonechap said:
I did an emergency recovery with my phone model and serial, same with kies.
Click to expand...
Click to collapse
If that did not work, it looks like the memory chip on the mother board is damaged. Take it in if it is still under warranty.
Cosmic Blue said:
If that did not work, it looks like the memory chip on the mother board is damaged. Take it in if it is still under warranty.
Click to expand...
Click to collapse
it is not under warranty anymore, should i replace the motherboard ?
@nonechap bro
upgrade you bootloader before flash nougat rom
bootloader is here
https://www.androidfilehost.com/?fid=529152257862714907
modem is here
https://www.androidfilehost.com/?fid=529152257862714909
open odin and boot your phone into download mode
[1]Connect phone and wait until you get a blue sign in Odin
[2]Place the desired BL file in the [BL] slot.
[3]Place the desired CP file in the [CP] slot.
[4] Go to the Options section and make sure Auto Reboot, Re-Partition and F. reset time are unmarked.
[5]Push [Start]
Once odin reports "Success..." message in the Message box, boot your phone into download mode again
then flash again 7.0 roms via odin
then boot in recovery and wipe data and cache
and reboot device
be patience first boot takes 15 minutes or more
if fail you cant boot your device untill system status changed to official due to knox restrictions or bootloader changed to latest
if not boot that means your bootloader not update by odin due to frp lock is on
if you are on marshmellow before flash 6.0.1 firmware to boot device
firmwares are here
https://www.sammobile.com/firmwares/database/SM-G935F/
i suggest if device boots unlock bootloader first to disable knox
hit thumbs up if i helped you
rony raj said:
@nonechap bro
upgrade you bootloader before flash nougat rom
bootloader is here
https://www.androidfilehost.com/?fid=529152257862714907
modem is here
https://www.androidfilehost.com/?fid=529152257862714909
open odin and boot your phone into download mode
[1]Connect phone and wait until you get a blue sign in Odin
[2]Place the desired BL file in the [BL] slot.
[3]Place the desired CP file in the [CP] slot.
[4] Go to the Options section and make sure Auto Reboot, Re-Partition and F. reset time are unmarked.
[5]Push [Start]
Once odin reports "Success..." message in the Message box, boot your phone into download mode again
then flash again 7.0 roms via odin
then boot in recovery and wipe data and cache
and reboot device
be patience first boot takes 15 minutes or more
if fail you cant boot your device untill system status changed to official due to knox restrictions or bootloader changed to latest
if not boot that means your bootloader not update by odin due to frp lock is on
if you are on marshmellow before flash 6.0.1 firmware to boot device
firmwares are here
https://www.sammobile.com/firmwares/database/SM-G935F/
i suggest if device boots unlock bootloader first to disable knox
hit thumbs up if i helped you
Click to expand...
Click to collapse
In this case, when i flash the rom, should i use the 4 files or only the AP file ?
nonechap said:
In this case, when i flash the rom, should i use the 4 files or only the AP file ?
Click to expand...
Click to collapse
use old odin
rony raj said:
use old odin
Click to expand...
Click to collapse
What version of odin should i use ?
And i have to use only the AP file or the 4 files of the 7.0 rom after the bootloader update? (AP BL CP CSC)
nonechap said:
What version of odin should i use ?
And i have to use only the AP file or the 4 files of the 7.0 rom after the bootloader update? (AP BL CP CSC)
Click to expand...
Click to collapse
odin v3.09 or 3.12
update bootloader and modem from given first post by me
rony raj said:
odin v3.09 or 3.12
update bootloader and modem from given first post by me
Click to expand...
Click to collapse
Yes i know but when i have updated the bootload with the 2 files you gave me, i have to reboot in download mod and flash the 7.0 rom, but i have download the rom and i have 4 files, so should i flash only the AP or the four files ?
nonechap said:
Yes i know but when i have updated the bootload with the 2 files you gave me, i have to reboot in download mod and flash the 7.0 rom, but i have download the rom and i have 4 files, so should i flash only the AP or the four files ?
Click to expand...
Click to collapse
tell me rom on your device before bootloop
6.0 or 7.0
rony raj said:
tell me rom on your device before bootloop
6.0 or 7.0
Click to expand...
Click to collapse
6.0.1
nonechap said:
6.0.1
Click to expand...
Click to collapse
then flash 6.0 firmware
download from here
https://www.sammobile.com/firmwares/database/SM-G935F/
rony raj said:
then flash 6.0 firmware
download from here
https://www.sammobile.com/firmwares/database/SM-G935F/
Click to expand...
Click to collapse
I tried but still nothing, i think i have to replace the motherboard ?
nonechap said:
I tried but still nothing, i think i have to replace the motherboard ?
Click to expand...
Click to collapse
try another chance
To do the S7 FRP OFF - Put phone in download mode
Once phone is in download mode.
Flash the files which i will provide.
You Only need to flash boot.tar via odin for respective models (example for s7 use G930 Qualcomm folder) for (s7 edge use G935 Qualcomm folder)
Once you flash the boot tar file. The phone will reboot and it will enable ADB. Run the Bat file which i will provide and it will remove the FRP lock
Once done put the phone in Downlaod mode and flash stock ROM.
The whole process takes less than 10 mins.
Same Idea for S7 Exynos phones... put phone in downlaod mode and then flash the file (G930F(ENGroot) for s7 models & (G935F_Root for s7 edge models). Once done phone will reboot. Then use this bat file (g935f.bat). Once this is executed locks will be removed and phone will go in download mode. Flash stock Boot.img and ALL DONE.
download
https://mega.nz/#!Tw0TAI6I!jCGuxGrwqCGEy3flcRqF9EpzbaTkby7SJ_slKRaXqRs
rony raj said:
try another chance
To do the S7 FRP OFF - Put phone in download mode
Once phone is in download mode.
Flash the files which i will provide.
You Only need to flash boot.tar via odin for respective models (example for s7 use G930 Qualcomm folder) for (s7 edge use G935 Qualcomm folder)
Once you flash the boot tar file. The phone will reboot and it will enable ADB. Run the Bat file which i will provide and it will remove the FRP lock
Once done put the phone in Downlaod mode and flash stock ROM.
The whole process takes less than 10 mins.
Same Idea for S7 Exynos phones... put phone in downlaod mode and then flash the file (G930F(ENGroot) for s7 models & (G935F_Root for s7 edge models). Once done phone will reboot. Then use this bat file (g935f.bat). Once this is executed locks will be removed and phone will go in download mode. Flash stock Boot.img and ALL DONE.
download
https://mega.nz/#!Tw0TAI6I!jCGuxGrwqCGEy3flcRqF9EpzbaTkby7SJ_slKRaXqRs
Click to expand...
Click to collapse
After flashing boot.tar, when i run the .bat, it says error: closed
EDIT: i have to enter into the recovery mod and select "adb update" in order to make my phone detected by my computer
Those files are for the S7. Do they work for the S7 Edge also?
Edit - I tried it and it fails in odin. My phone is bricked.
rony raj said:
@nonechap bro
upgrade you bootloader before flash nougat rom
bootloader is here
https://www.androidfilehost.com/?fid=529152257862714907
modem is here
https://www.androidfilehost.com/?fid=529152257862714909
open odin and boot your phone into download mode
[1]Connect phone and wait until you get a blue sign in Odin
[2]Place the desired BL file in the [BL] slot.
[3]Place the desired CP file in the [CP] slot.
[4] Go to the Options section and make sure Auto Reboot, Re-Partition and F. reset time are unmarked.
[5]Push [Start]
Once odin reports "Success..." message in the Message box, boot your phone into download mode again
then flash again 7.0 roms via odin
then boot in recovery and wipe data and cache
and reboot device
be patience first boot takes 15 minutes or more
if fail you cant boot your device untill system status changed to official due to knox restrictions or bootloader changed to latest
if not boot that means your bootloader not update by odin due to frp lock is on
if you are on marshmellow before flash 6.0.1 firmware to boot device
firmwares are here
https://www.sammobile.com/firmwares/database/SM-G935F/
i suggest if device boots unlock bootloader first to disable knox
hit thumbs up if i helped you
Click to expand...
Click to collapse
Works !!!
Sorry to revive an old thread but I think it might help people recover from a bootloop with a bit of addtional explanation than initially provided.
So I have an S7 Edge as a backup phone and hadn't used it for a while. Google FRP was activated. I tried to update to a newer firmware through Odin (can't OTA since it's from Tmo and i'm in Canada). Anyways for whatever reason it failed in the middle and I was stuck in a bootloop that wouldn't stop. I tried downgrading, I tried factory, I tried new versions, nothing would do, I'm assuming because of FRP.
So I followed Rony Raj's post https://forum.xda-developers.com/showpost.php?p=71906126&postcount=17 but kept getting stuck. The thing is once you flash the proper Boot.tar file, the phone will appear to still be in a bootloop. You will have to go with the screen (the phone) and the sound of the connection and disconnection from your computer. So basically just sync with the sounds and time it so you open the ''S7 & S7 Edge QUALCOMM.bat'' file at the exact time your phone reconnects and it'll work. I had to do it about 6-7 times before i got it right.
When that is done your phone will restart in download mode. When you do just flash the latest version of the firmware you get from AndroidFileHos*.com or Sammobil*.com. Make sure you select all 4 files in Odin (BL, AP, CP and SELECT CSC HOME for CSC - NOT CSC).
Once all that is done your phone will restart and everything should be fine, well that worked for me
Thanks a lot to @rony raj for putting together the files and the steps to save my G935
Hello everyone!
I have a Samsung SM-G935F which after a system update (a patch) is no longer working, it's stuck in boot loop.
When I turn it on I get: Kernel Rev check file Device 1, Binary 0.
I can get into the Download Mode and it will be recognized by ODIN.
But I don't know how to proceed in order to solve the presented scenario. Can you help me out? Thanks!
Regards,
Oliver
Hi, First you need to try to perform a format through recovery,holding power+home+volume up.
If phone did not boot,Then download firmware from sammobile using an app called SamFrim you can find it by simple search on google.
After you downloaded thr firmware,Launch odin and boot your phone into download mode by holding power+home+volume down.
Extract the firmware and it will generate 5 files
AP
BL
CP
CSC
Home_Csc
Add every file to its correct place in odin
AP
CP
BL
Csc( don't use Home_Csc,Because we want to perform a full wipe)
Then hit start, be careful not to unplug the cable,once it's done phone will auto reboot,leave it,It will do everything by its own.
Btw you must use latest odin version because older version doesn't support Oreo roms
Good Luck
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