So I downloaded TWRP manager off Google Play to my rooted device and attempted to install the recovery. When I attempted to reboot, it said custom binary blocked by reactivation lock and was stuck in bootloop. I tried then using odin to install stock firmware, but it ended with an error and now it says that an error has occured and to use the Smart Switch PC software, but that requires serial, which I can't seem to find anywhere. What can I do?
wedu96 said:
So I downloaded TWRP manager off Google Play to my rooted device and attempted to install the recovery. When I attempted to reboot, it said custom binary blocked by reactivation lock and was stuck in bootloop. I tried then using odin to install stock firmware, but it ended with an error and now it says that an error has occured and to use the Smart Switch PC software, but that requires serial, which I can't seem to find anywhere. What can I do?
Click to expand...
Click to collapse
Serial number should be on your box.. Also on back of the device....
wrong person
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/
I have an S4 SGH-I337 I'm trying to fix for a friend. It's stuck in a boot loop, but I'm still able to get into "Recovery Mode" and "Download Mode". The phone is not "USB Debugging" enabled, and is bootloader locked ATT... I assume. Owner says its still stock and he didn't try to flash or unlock it in any way. I've installed Odin v.3.10.7 and tried to flash a stock ROM from Sammobile.com, but got the message : Failed (Auth). When I tried another ROM I found on a blog about fixing a soft-bricked s4, I was able to get a PASS on Odin. I rebooted into recovery and cleared cache/factory reset after it finished but still have a bootloop. I tried adding a PIT file to the process and still bootloop. Why doesn't the ROM from samobile.com work if it's a stock ROM? Are there any other files I can flash like a new bootloader or whatever, or just the two I tried? Is it possible the hardware is fried? I'm not ready to give up yet.
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.
I recently bought an S7 and wanted to root. It's my first Samsung phone so the software is new to me so apologies if there is an easy answer. I (extremely stupidly) re-enabled FRP lock within Android after rooting (hoping that it was stop the unauthorised actions warning). This now means when i start the phone it states "Custom Binary Blocked by FRP lock" and would not boot in to Android. I've read some threads but the current situation is:
1) When i tried to boot it would not boot to Android and stuck at the first splash screen and warning. Whilst i had rooted i did not flash twrp so only have the stock recovery.
2) I went in to the stock recovery and did a factory reset and cache clear. No change.
3) I tried Smart switch and kies - no luck - both said un-supported device or hung on connecting
4) I went to the thread with the most recent stock download (Netherlands) and downloaded that. I tried to install that and it hung for about an hour. I disconnected and it now says "An error has occurred whilst updating the device software" and does not boot.
So i cannot boot in to Android, have no custom recovery and KIES/SmartSwap do not work.
Any ideas????!?!?
Download the latest MM stock rom and try to bypass the frp lock.
lord_melchett said:
I recently bought an S7 and wanted to root. It's my first Samsung phone so the software is new to me so apologies if there is an easy answer. I (extremely stupidly) re-enabled FRP lock within Android after rooting (hoping that it was stop the unauthorised actions warning). This now means when i start the phone it states "Custom Binary Blocked by FRP lock" and would not boot in to Android. I've read some threads but the current situation is:
1) When i tried to boot it would not boot to Android and stuck at the first splash screen and warning. Whilst i had rooted i did not flash twrp so only have the stock recovery.
2) I went in to the stock recovery and did a factory reset and cache clear. No change.
3) I tried Smart switch and kies - no luck - both said un-supported device or hung on connecting
4) I went to the thread with the most recent stock download (Netherlands) and downloaded that. I tried to install that and it hung for about an hour. I disconnected and it now says "An error has occurred whilst updating the device software" and does not boot.
So i cannot boot in to Android, have no custom recovery and KIES/SmartSwap do not work.
Any ideas????!?!?
Click to expand...
Click to collapse
Flash latest nougat Stock rom from sammobile using The latest ODIN software. You shouldnt disable OEM unlock next time you root/install custom recovery to your phone or else this will happen again, and you'll have to flash stock firmware again.