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
Related
Hello,
I'm new on XDA, but I've got a question.
I tried to install TWRP on my Note 2 with Odin 3.07. It seemed to work, until I tried to enter in TWRP. I checked the phone status and it says "Customized", which means the recovery should be installed correctly. Once I turned off the phone and tried to go into recovery, it just says "no command" and boots the stock Android recovery. When I reboot my phone and I check the phone status, it says "Official" What should I do? I hope you can help me.
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.
I've successfully rooted some of my previous androids, and currently have a rooted LG tablet, today I was trying to root my Galaxy S7 and I bricked it and can't unbrick it. I was following this guide devs-lab. com/root-samsung-galaxy-s7-s7-edge.html. Everything looked like it worked Odin said pass but my phone got stuck in a boot loop. I tried to root it with a tar.md5 from a different site but it fails. When I put it into recovery mode it shows the droid with a red caution sign and says "No command". From there I can get into the recovery menu and I've tried wiping the cache and that didn't work, I then tried the factory reset and that didn't work. I then downloaded the "Stock_DeOdexed_Debloated" ROM from here and tried to sideload it using adb but that fails saying "E:footer is wrong. E:Signature verification failed" I tried to install it from the SD card but get the same message. In the recovery menu it says "No Support SINGLE-SKU, Supported API:3, # MANUAL MODE #, -- Appling Multi-CSC..., Applied the CSC-code : TMB, Successfully applied multi-CSC., Successfully verify for dmverity hash tree". I'm currently downloading a stock firmware zip file I found on a different site. Is there any way I can unbrick it or is it permanently bricked? Any help would be greatly appreciated.
I flashed the files that were inside the zip using Odin and fixed it, I can’t figure out how to attach files so I've included links to the stock firmware I used as well as the version of Odin I used.
Stock firmware - downloadmirror. co/Urs/G930TUVU4APK1_G930TTMB4APK1_TMB.zip?download_token=20ae1b122f8519d6cfc69c0ef013b3f4c6856d15149bdc46bc3bcfecfb91ee1f
Odin - dropbox. com/s/go43hspdcbg9rld/Odin3_v3.12.5.rar?dl=0
It sounds like you have only soft bricked. As long as you flash the same firmware you had before everything got borked, it should work. Search the threads here at xda for links to the firmware you need or download from sammobile to be safe.
Also make sure you have the latest version of Odin, and all the Samsung drivers are installed. Hope this helps and good luck.
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.
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)