So i recently switched to a new rom from my previous rooted one. Unfortunatly, i forgot to enable developer debugging or oem unlock in developer options before i restarted, so now my phone is in a boot loop. It wont go into recovery mode, or boot into the system. I can only go into download mode. My knox is tripped, and it shows frp lock. So far i tried flashing the stock 5.1.1 firmware using odin, and it fails on nand write. Tried flashing a new bl and cp, but frp blocks it. What can i do to fix this!?
Right, model of my phone is SM-G920T
EDIT: Seems to be when i was trying to flash the original firmware, i got an old one, F6, when the correct one is F8. Went through with odin and seems like everything is back on track!
Flash this updated stock 5.1.1 ROM via odin to overcome your woes:
http://www.sammobile.com/firmwares/download/51233/G920TUVU2COF8_G920TTMB2COF8_TMB/
Hi, I tried everything, from evening since now (2AM) I serached everywhere, I put all my possible efforts to load TWRP on my S5, nothing to do! You my last chance before I crash the phone..
On boot recovery Odin says SECURE CHECK FAIL: recovery.
I've USB debug turned on, but anyhow I can see the popup for RSA where I can always allow my laptop.
I've Samsung Reactivation Lock unchecked
what it reports:
CURRENT BINARY: Samsung official
SYSTEM STATUS: official
REACTIVATION LOCK (KK): OFF
SECURE DOWNLOAD: ENABLE
UDC START
Tried CWM too, old TRWP versions, nothing.
I tried any kind of root, all the applications are fakes. To root I tried CF-autoroot but it requires Odin, and odin isn't flash nothing in this phone, always an autorization fail!
may chances are that the firmware 3.4.0 inside has been modified/uploaded to avoid any update?
Hi,
I just "slightly" bricked my S7 (SM-G930F), and I hope someone can help me. My first S7 (which had Superman-Rom installed) had a burnt-out USB port, so I got a brand new replacement. I made a TWRP backup from the old one and installed that on the new one, but I think I made 1 (or even 2) critical mistakes here: I installed TWRP with ODIN on the phone directly out of the box without starting it once, so I never activated the OEM unlock. Furthermore I restored the backup including the EFS partition. The first start-up went fine, just I couldn't unlock the screen (password not valid). After restarting the phone I got the message "Custom binary locked by FRP lock". Using Smart Switch's device initialization, I could get the phone into download mode again and flashed the stock rom (G930FXXU1DQEI with VD2 carrier) via ODIN. But that got me nowhere, after showing "Installing system update" I just got a screen with "No command". Then the phone rebooted again and went directly to the recovery, showing "Successfully verify for dmverity hash tree". Any attempt to restart the phone just shows the Samsung boot logo two times and then I'm back in recovery, where it then shows "No Support SINGLE-SKU, Supported API: 3, dm-verity error, failed code: 0x02". Trying to install TWRP again just triggers FRP lock. I tried both Smart Switch and ODIN several times in different orders, but nothing works.
Here the timeline again:
1. TWRP-Backup old phone (Superman-Rom)
2. First start new phone directly to download mode, installing TWRP (no OEM unlock)
3. TWRP-Restore new phone, EFS included
4. Rom starts, lock screen password not valid
5. Restart
6. FRP lock
7. Smart Switch
8. Stock rom via ODIN
9. "No command"
10. Starting to recovery, dm-verity ok
11. Restart
12. Starting to recovery, dm-verity error
13. Restart
14. GOTO 12
15. ???
Another interesting thing is that at the first start into recovery after flashing the VD2 stock rom, I also get the message "# MANUAL MODE#, Appling Multi-CSC, Applied the CSC-code : DBT, Successfully applied multi-CSC". As I downloaded the VD2 rom, why is it setting the csc to DBT?
Anyone who can help me break the loop?
Yanai1701 said:
Hi,
I just "slightly" bricked my S7 (SM-G930F), and I hope someone can help me. My first S7 (which had Superman-Rom installed) had a burnt-out USB port, so I got a brand new replacement. I made a TWRP backup from the old one and installed that on the new one, but I think I made 1 (or even 2) critical mistakes here: I installed TWRP with ODIN on the phone directly out of the box without starting it once, so I never activated the OEM unlock. Furthermore I restored the backup including the EFS partition. The first start-up went fine, just I couldn't unlock the screen (password not valid). After restarting the phone I got the message "Custom binary locked by FRP lock". Using Smart Switch's device initialization, I could get the phone into download mode again and flashed the stock rom (G930FXXU1DQEI with VD2 carrier) via ODIN. But that got me nowhere, after showing "Installing system update" I just got a screen with "No command". Then the phone rebooted again and went directly to the recovery, showing "Successfully verify for dmverity hash tree". Any attempt to restart the phone just shows the Samsung boot logo two times and then I'm back in recovery, where it then shows "No Support SINGLE-SKU, Supported API: 3, dm-verity error, failed code: 0x02". Trying to install TWRP again just triggers FRP lock. I tried both Smart Switch and ODIN several times in different orders, but nothing works.
Here the timeline again:
1. TWRP-Backup old phone (Superman-Rom)
2. First start new phone directly to download mode, installing TWRP (no OEM unlock)
3. TWRP-Restore new phone, EFS included
4. Rom starts, lock screen password not valid
5. Restart
6. FRP lock
7. Smart Switch
8. Stock rom via ODIN
9. "No command"
10. Starting to recovery, dm-verity ok
11. Restart
12. Starting to recovery, dm-verity error
13. Restart
14. GOTO 12
15. ???
Another interesting thing is that at the first start into recovery after flashing the VD2 stock rom, I also get the message "# MANUAL MODE#, Appling Multi-CSC, Applied the CSC-code : DBT, Successfully applied multi-CSC". As I downloaded the VD2 rom, why is it setting the csc to DBT?
Anyone who can help me break the loop?
Click to expand...
Click to collapse
Hi
Main issue I see is:
Install EFS partition from one phone to the other.....lets hope you did not mess the IMEI , EFS are device specific.
OEM unlock maybe an issue but Odin flashing should solve it ( most of the times)
You said you flashed with ODin , what file you used CSC or home_csc? if you used CSC did you selected re partition?
MAX 404 said:
Install EFS partition from one phone to the other.....lets hope you did not mess the IMEI , EFS are device specific.
Click to expand...
Click to collapse
Is there a way to restore the original EFS partition? ODIN has the option to clear the EFS, but I could not find any information on what this does, only "stay away from it!!!!!".
MAX 404 said:
You said you flashed with ODin , what file you used CSC or home_csc? if you used CSC did you selected re partition?
Click to expand...
Click to collapse
I tried both, but mainly CSC to also do a factory reset, and I also tried to repartition. Only thing I still haven't tried is "Nand Erase All", because "stay away from it!!!!!"
Yanai1701 said:
Is there a way to restore the original EFS partition? ODIN has the option to clear the EFS, but I could not find any information on what this does, only "stay away from it!!!!!".
I tried both, but mainly CSC to also do a factory reset, and I also tried to repartition. Only thing I still haven't tried is "Nand Erase All", because "stay away from it!!!!!"
Click to expand...
Click to collapse
There are ways to restore the EFS , the question is do you have a copy of the original EFS??
Do not use option in Odin you do not know about.... re partition is known did you use it?
check this info regarding that
Yes, I already tried to repartition. And no, I don't have a backup of the original EFS, I accidentally restored it because I overlooked that is was checked in TWRP (or just checked everything that was there without really looking?).
Regarding Odin it's just sad that nobody seems to know what some of the options really do, maybe some combination could help me.
Yanai1701 said:
Yes, I already tried to repartition. And no, I don't have a backup of the original EFS, I accidentally restored it because I overlooked that is was checked in TWRP (or just checked everything that was there without really looking?).
Regarding Odin it's just sad that nobody seems to know what some of the options really do, maybe some combination could help me.
Click to expand...
Click to collapse
long shot but you could try this.
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
or may have to take it to a service shop ( a good one) they have special boxes with special options to fix this kind of problems
Thanks for your help Max, but it seems I have to pick your last option and search for a service shop. I downloaded the latest available combination firmware, but after installing it the phone gets stuck on the boot screen with displaying "ASV TBL VER = 10; ASV TBL VER2 = 0; NAD: PASSED; NAD ACAT: FAILED; RPMB PROVISIONED" on the top. Reverting to the normal firmware brings me back to the recovery loop. The problem is also that there seems to be no combination firmware for Nougat, all the files are for Marshmallow. Not sure if this is the reason that the phone gets stuck, but I think it likely.
So I wiped all of my data with TWRP and went to boot the phone up so that it was as thought I factory reset it, but there's no OS installed and it boots to TWRP.
When I try to flash the stock rom (all 4 variants from Updato) Odin fails and I get an error on the phone saying "SW REV. CHECK FAIL. DEVICE: 3. BINARY: 2."
Any help for this, or is the phone just useless now?
CSMNT said:
So I wiped all of my data with TWRP and went to boot the phone up so that it was as thought I factory reset it, but there's no OS installed and it boots to TWRP.
When I try to flash the stock rom (all 4 variants from Updato) Odin fails and I get an error on the phone saying "SW REV. CHECK FAIL. DEVICE: 3. BINARY: 2."
Any help for this, or is the phone just useless now?
Click to expand...
Click to collapse
What model J3 do you have? I can try to help you
CSMNT said:
So I wiped all of my data with TWRP and went to boot the phone up so that it was as thought I factory reset it, but there's no OS installed and it boots to TWRP.
When I try to flash the stock rom (all 4 variants from Updato) Odin fails and I get an error on the phone saying "SW REV. CHECK FAIL. DEVICE: 3. BINARY: 2."
Any help for this, or is the phone just useless now?
Click to expand...
Click to collapse
I did the exact same thing and got the same problems with Odin. Best I can suggest is to try and flash a custom ROM through TWRP. That's what I did and I can use my device, though my ROM doesn't match my baseband and I can't turn on wi-fi, but I think that's just gonna be on my end.
Try looking at @Sands207 or @SonderTech XDA threads for custom ROMs and try and flash one of those. Be really careful to download and flash the correct ones.
CSMNT said:
So I wiped all of my data with TWRP and went to boot the phone up so that it was as thought I factory reset it, but there's no OS installed and it boots to TWRP.
When I try to flash the stock rom (all 4 variants from Updato) Odin fails and I get an error on the phone saying "SW REV. CHECK FAIL. DEVICE: 3. BINARY: 2."
Any help for this, or is the phone just useless now?
Click to expand...
Click to collapse
you need the latest binary for your device. you cannot downgrade if the sw revision does not match up.
I have a Samsung Galaxy A7 (T500) on fw BUJ1 which I rooted using magisk. It all seemed to work fine except a cpl of weeks later, there was an error of 'Enrolled knox guard prevent flashing factory binary(vbmeta)' in red, with a message of 'security error This phone has been flashed with unauthorised software & is locked'
I then re-flashed the stock version of this fw back on it and it boots as normal.
Problem is that I can no longer flash anything via odin. When I go to download mode and flash the patched fw, when the flashing process is almost complete it fails and the error 'enrolled knox guard prevent flashing factory binary(vbmeta) ' is displayed on the download mode screen and odin fails.
I also no longer have the oem unlock option in dev options, tho in download mode it does have 'oem lock off (u)' and 'kg status normal'.
How I can get past this error and how to get oem unlock to re-appear? (the date change stuff hasnt worked)