Hi everyone
I have a g935f with oreo firmware.But i don't have imei and baseband.I try to flash combination file but always ends with error.I can flash firmware but only binary 3, but always no modem. I try to repair with z3x box but it says
try downgrade modem if possible.
Any help will be welcome
Thank you very much
I did it after many many tries.Only solution it with combination firmware.After that write firmware but whithout CP in odin or z3x.Same binary.Repair imei and unlock.JOB DONE
marinicaalexandru said:
I did it after many many tries.Only solution it with combination firmware.After that write firmware but whithout CP in odin or z3x.Same binary.Repair imei and unlock.JOB DONE
Click to expand...
Click to collapse
Link for the combination file please?
Im with Binary 3 too and cannt downgrade
Thank you
combination file s7 edge
https://addrom.com/collection-combination-rom-samsung-s7-edge/
query, did you manage to downgrade ?, or just by flashing the firmware combination you can now repair or change the imei with the z3box in oreo?
could you tell me the steps plis? Thx
you cannot downgrade binary 3.just flash combination firmware.binary 3 of course.enable usb debugging in settings/developer options.shut down.put in download mode an flash binary 3 firmware.oreo.without boot and modem.BL and CP.after that repair imei if it not shown.i write cert data and it was ok
marinicaalexandru said:
you cannot downgrade binary 3.just flash combination firmware.binary 3 of course.enable usb debugging in settings/developer options.shut down.put in download mode an flash binary 3 firmware.oreo.without boot and modem.BL and CP.after that repair imei if it not shown.i write cert data and it was ok
Click to expand...
Click to collapse
You repaired imei you did it with the z3 box?
yes.it is possible that combination firmware read imei ok.it happens
marinicaalexandru said:
yes.it is possible that combination firmware read imei ok.it happens
Click to expand...
Click to collapse
ok, and the last thing, I can change the imei of the device with the box z3, because unfortunately I had my device with the imei changed without knowing it, so I updated my device from mm at oreo it and changed my imei and now I have no signal, so I would like to patch the certificate that I had before, since you can not do dowgrade
the imei is written on the back cover.you must write that imei.i am not sure if it works with another imei
Related
Hi guys
What the title says
Any ideas on what I can try?
Thanks in advance
Deleted
Trex888 said:
Did you try wipe cache & data factory reset from stock recovery after flashing stock firmware?
If factory reset did not work then You can try to flash repair firmware with pit file.
Click to expand...
Click to collapse
Hi. That's the first thing I tried, multiple times.
Where can I get the repair firmware? Any chance it can erase imei?
Thanks
Daved+ said:
Hi. That's the first thing I tried, multiple times.
Where can I get the repair firmware? Any chance it can erase imei?
Thanks
Click to expand...
Click to collapse
Go to www.tsar30000.com and download repair full firmware for your model.
It will erase imei if you choose in odin .
Just leave everything as it is in odin and flash 4 files firmware with pit file.
Don't tick in odin options nand erase all or erase imei.
Trex888 said:
Go to www.tsar30000.com and download repair full firmware for your model.
It will erase imei if you choose in odin .
Just leave everything as it is in odin and flash 4 files firmware with pit file.
Don't tick in odin options nand erase all or erase imei.
Click to expand...
Click to collapse
Okay, just saw repair file is for android 5 and this board already came updated to android 6.
Will I still be safe?
Thank you
Try emergency software recovery and initialization from smart switch, it worked for me when i had my device soft bricked...
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
G935t model
the phone has been flash with unauthorized software and it has been locked.
This error always apear after booting up..
I try to to flash all stock firmware from odin from old to latest
Version of G935T
Still the problem is not corrected
I try to flash using odin with pit file no change still my phone have issue
My emei is intact and my serial number is intact
Do think i corrupt my efs?
Because i try to change my imei using qpst i successfuly change my imei but i return my backups of qcn file
Please help me
My phone ia locked to t- mobile and i live in here in the Philippines i need to unlock my network but when the technician's is trying to unlock using z3x he said he ecountering error.. During unlocking processes do you think the reason is the security error?
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
installed firmware:
https://ibb.co/ggCYYkN
recovery:
https://ibb.co/bzd8dxs
i try to install :
G950FXXU4CRJ5_G950FOXM4CRJ3_ARO
Prince Comsy Odin v3.12
first time i tryed to burn the rom i got in odin write failed (or similar i didn't write it down).
second time and later i get PIT error
https://ibb.co/cxYd0YP
please your help to understand whats going on with this device \ firmware
do-d said:
installed firmware:
https://ibb.co/ggCYYkN
recovery:
https://ibb.co/bzd8dxs
i try to install :
G950FXXU4CRJ5_G950FOXM4CRJ3_ARO
Prince Comsy Odin v3.12
first time i tryed to burn the rom i got in odin write failed (or similar i didn't write it down).
second time and later i get PIT error
https://ibb.co/cxYd0YP
please your help to understand whats going on with this device \ firmware
Click to expand...
Click to collapse
Looks like judging from your screen shots
1. You are trying to flash F firmware onto a U device. Exynos to snapdragon. Will cause you issues.
2. You will need Odin ( or patched Odin ) 3.13.1 or higher
3. You will need a binary ( bootloader ) version 5 or higher.
Just download latest firmware from sammobile
spawnlives said:
Looks like judging from your screen shots
1. You are trying to flash F firmware onto a U device. Exynos to snapdragon. Will cause you issues.
2. You will need Odin ( or patched Odin ) 3.13.1 or higher
3. You will need a binary ( bootloader ) version 5 or higher.
Click to expand...
Click to collapse
thank you!
phone was sold as F model , it has all stickers saying its F model
here it looks like an F firmware installed https://ibb.co/ggCYYkN
but its a U model ?
so for next time what is the right way to get the real device model ?
do-d said:
thank you!
phone was sold as F model , it has all stickers saying its F model
here it looks like an F firmware installed https://ibb.co/ggCYYkN
but its a U model ?
so for next time what is the right way to get the real device model ?
Click to expand...
Click to collapse
There are many guides on the internet regarding to phone authentication and about refurbished phones.
On your S8, since it doesn't have a removable battery, on the back, down the bottom, should show model no. etc. engraved on it ( not stickers ).
On the back it will also show iIMEI + serial number. Compare it to what it say's on the phone ( about phone + *#06# ) to the back engraving.
There are websites that can check your IMEI number to give you various information about the phone.
Buying a phone from the internet ( eg: eBay etc.) using the IMEI can be used as a way to check the phone.
i just got one more device from a local store , it's not official retailer of samsung , its from a paralel imports
and its the same ****
firmware box and stickers say SM-G950F
recovery say SM-G950U, i didn't tried to flush because i cant get the OEM unlock.
BTW is it possible to downgrade this device to android 8 ?
image uploader
so if i understood right i should be able to flush this firmware on this phone
G950USQU5CRL2
?
do-d said:
so if i understood right i should be able to flush this firmware on this phone
G950USQU5CRL2
?
Click to expand...
Click to collapse
In download mode it will have a line with PR SWREV
The number after the B is your binary ( bootloader ) number.You will need to flash this number or higher. You can not downgrade binary numbers.
Depending on what firmware you flash U or U1 you may need patched Odin.
spawnlives said:
In download mode it will have a line with PR SWREV
The number after the B is your binary ( bootloader ) number.You will need to flash this number or higher. You can not downgrade binary numbers.
Depending on what firmware you flash U or U1 you may need patched Odin.
Click to expand...
Click to collapse
so from Download Mode picture i can say binary 7 it is
in this firmware G950USQU5CRL2 U5 is it the binary or is it the security patch ?
do-d said:
so from Download Mode picture i can say binary 7 it is
in this firmware G950USQU5CRL2 U5 is it the binary or is it the security patch ?
Click to expand...
Click to collapse
Binary ( bootloader ) is the 5th number from the right of the firmware ( in the above post it's 7 )
e.g.:G950USQU5CRL2 - 5 is the binary number.
The letters/numbers after the binary number will tell you version ( security patch ) issue information but is easier to check the date of the firmware from the website you are downloading from.
thank you @spawnlives i really appreciate this
spawnlives said:
Binary ( bootloader ) is the 5th number from the right of the firmware ( in the above post it's 7 )
e.g.:G950USQU5CRL2 - 5 is the binary number.
The letters/numbers after the binary number will tell you version ( security patch ) issue information but is easier to check the date of the firmware from the website you are downloading from.
Click to expand...
Click to collapse
Sir, my binary matched with the ROM, but I get the error again as "secure check failIT", "sw rev check fail device 2 binary 1" and "secure check fail bootloader"
can u share the link to download the appropriate bootloader for J5 Prime(G570F)