Reactivation Lock Soft Brick - T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting

Good day all,
So last Lollipop ROM I played with (maybe rapture) I accidentally left the Reactivation Lock checked not knowing what it actually was. Upon trying to flash another rom I am welcomed by "Custom binary blocked by reactivation lock". I've tried recovery with Kies but I've never been able to get a code for it. And the serial of the phone doesn't work. I've tried to 'unroot' using stock firmware and Odin. But it bootloops up to the T-Mobile logo. Trying auto root fails thanks to the lock. I'll probably give Odin another shot and see if I can at least get it booted next. But at least I've removed signs of root so I can take it back to T-Mobile. But I'd rather get this fixed myself. Any suggestions?

After you Odin to stock lollipop.
Boot into recovery and factory reset / data wipe and it should boot up instead of bootlooping.

Happened to me once.
Flash latest twrp
Unchecked auto reboot
Pull battery out
Boot into recovery
---------- Post added at 11:07 PM ---------- Previous post was at 11:06 PM ----------
SerialCynic said:
Good day all,
So last Lollipop ROM I played with (maybe rapture) I accidentally left the Reactivation Lock checked not knowing what it actually was. Upon trying to flash another rom I am welcomed by "Custom binary blocked by reactivation lock". I've tried recovery with Kies but I've never been able to get a code for it. And the serial of the phone doesn't work. I've tried to 'unroot' using stock firmware and Odin. But it bootloops up to the T-Mobile logo. Trying auto root fails thanks to the lock. I'll probably give Odin another shot and see if I can at least get it booted next. But at least I've removed signs of root so I can take it back to T-Mobile. But I'd rather get this fixed myself. Any suggestions?
Click to expand...
Click to collapse
Happened to me once
Download mode
Flash latest twrp via odin
Unchecked auto reboot
Pull battery out
Boot into recovery

The same thing happened to me here. I am following the directions posted to fix but flashing the recovery keeps failing. Please help
Edit: FIXED.

I had to Odin Cod6 stock to access my phone again. Soon as you get in, make sure you go to settings, security, and disable the lock. It will ask you for your Gmail account I believe.

Related

Custom binary blocked by reactivation lock

RESOLVED!
Turns out I had reactivation lock enabled.
Took my the whole damn day to figure this out, lol.
So, if anyone is a noob like me and ends up with this message on their screens, just go to Settings--> Security , and uncheck reactivation lock.
Now onwards to flashing heaven!
EDITED TO OP: RESOLVED
I'll post this in the OP since this is the trouble I need resolving now, and the old OP has been resolved:
NEW PROBLEM:
Sorry to bump this thread, but I keep getting this error when trying to boot into recovery.
I tried to re-flash twrp via Odin and via the twrp app with no success. The phone will boot loop into this message until I pull the battery off.
When trying to Odin twrp recovery it always ends up saying fail.
I wanted to flash a new rom and I can't because of this.
Current rom is firekat v4.
Thanks for any help.
EDIT:
I was able to flash stock recovery, but twrp still fails.
I'm really lost here.
OLD OP/RESOLVED:
So, I was trying to update super su, and I chose twrp, because I have it installed.
The phone rebooted into a yellow triangle (different from the one in download mode), with the title of this thread displayed on the top of the screen.
It kept looping into this message, I could only get it into download mode.
I had to try to Odin twrp recovery again, and even though it failed, at least it got me out of the boot loop.
Phone's working fine, but I think Knox is to blame here.
I tried updating super su by choosing the "normal" option and everything worked.
But since I have twrp,shouldn't it have worked with the twrp option?
Sent from my SM-N910T using Tapatalk
No. Normal is the normal method. TWRP is for those systems that fail when using the normal method.
Sent telepathically
MarkP80nj said:
So, I was trying to update super su, and I chose twrp, because I have it installed.
The phone rebooted into a yellow triangle (different from the one in download mode), with the title of this thread displayed on the top of the screen.
It kept looping into this message, I could only get it into download mode.
I had to try to Odin twrp recovery again, and even though it failed, at least it got me out of the boot loop.
Phone's working fine, but I think Knox is to blame here.
I tried updating super su by choosing the "normal" option and everything worked.
But since I have twrp,shouldn't it have worked with the twrp option?
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
It pays to read before mashing buttons. The dialog that displays the Normal and TWRP/CWM buttons explains the difference. You're supposed to use Normal and only use TWRP/CWM if Normal fails.
Thanks guys, I feel so dumb now, lol.
Happy thanksgiving.
Sent from my SM-N910T using Tapatalk
Copied this post and pasted to OP.
Sent from my SM-N910T using Tapatalk

Force close reactivation lock screen

After I updated my ROM and with through the set up process I thought it would be a good idea to checked the lock reactivation through samsung then afterwards I forgot all about it and went through TB and deleted all samsung apps off my phone...
Now if I try to uncheck the lock reactivation it force closes my settings so I'm thinking I should just just factory reset my phone and when everything boots back up enter my Samsung account info or would the phone act up trying to factory reset with the reactivation lock on the phone
I need to get into my custom recovery and I can't since lock reactivation is checked :/ any help is appreciated
Make sure you have stock kernel and recovery, otherwise with reactivation checked, you might end in forever bootlooop.
Note 4 ?
Are you able to boot into your phone?
Yeah my phone is fully functional I'm able to do everything fine but it's just when I mess with anything that deals with samsung account it force closes for example I tried the data reset but it force closed when I hit it
What I think I need is the Samsung apk or w.e I deleted inside titanium backup that deals with samsung accounts I'll send someone some beer money if they can help me to uncheck reactivation lock lol
Can't get into recovery with the power button + home button + up volume button combo?
new info
phone now is stuck on a bootloop since i think i copied/cut things from /system folder
does anyone know if there is a way i can get my phone back to stock or at least back to normal through ODIN?
remember im pretty sure just trying to odin a stock ROM will not work since it will fail, since its locked reactivation and i cant boot the phone either
who ever figure this out will be the man and ill throw $20 to make it interesting..
A30laa said:
new info
phone now is stuck on a bootloop since i think i copied/cut things from /system folder
does anyone know if there is a way i can get my phone back to stock or at least back to normal through ODIN?
remember im pretty sure just trying to odin a stock ROM will not work since it will fail, since its locked reactivation and i cant boot the phone either
who ever figure this out will be the man and ill throw $20 to make it interesting..
Click to expand...
Click to collapse
Flash cf auto root for our phone in odin with the reset and auto reboot unchecked. Very important to uncheck those. It will fail to flash. Pull out your battery and put back in. It should boot as normal
As for your first problem you should download ib4 sampler pack in his rapture thread and install those apks hopefully the one you need to uncheck reactivation will be in there.
well i tried the cf auto root thru odin and right at the end it failed like i thought it would because of the reactivation lock so i pulled my battery and tried booting up the phone and I am still stuck on the t mobile screen... I'm pretty sure there isn't a way to get my phone working again with odin failing because of the lock any help is appreciated.
You could try flashing a stock rom through recovery.
Then a data reset.
Or odin to stock then factory reset.
Im not home at the moment to try but i have a feeling trying to odin a stock rom will not pass since the reaactivation wont let odin doing anything right and i cant get into my recovery since it will pop up saying custom binary failed due to reactivation lock

"Custom Binary (BOOT) blocked by FRP Lock" After updating to 5.1.1

Hello, i have been researching for this issue that i have for over a month now, and yet i haven't found any solution or even a clue on how to fix it, and im sure lots of people are having the same issue that im having, let me explain what exactly happened to my phone and what i exactly tried
i was running on 5.0.1 G920TUVU1AOCG, and at that time "Ping Pong Root" was not yet available, so the only way to root the phone was to flash the "g920t_of6_aou_kernel_v1.tar" witch i did and installed SU using "g925t_of6_aou_twrp_recovery_v13.tar" and the phone worked perfect after that, and after the 5.1.1 lollipop came out, i decided to upgrade to that, so i flashed stock 5.1.1 odin firmware and flash the custom kernel "g920t_of6_aou_kernel_v1.tar" to get it out the bootloop since it was flashed previously on it, it worked and booted up and all seemed to be fine, i also wanted to perform a factory reset, and here is where the PROBLEM started, i forgot to turn on OEM Unlocking in Dev options, so after the factory reset, the phone got stuck on the bootloop "Samsung galaxy s6; powered by android" and the only way to make it bypass this bootloop is by flashing the "g920t_of6_aou_kernel_v1.tar" again, but i cant flash that because i forgot to turn on the OEM Unlocking in the dev options, and every time i try for flash any custom recovery or custom kernel and will give me "Custom Binary (BOOT) blocked by FRP Lock", so now im stuck on the bootloop, i cant access the phone to turn on the OEM Unlocking, Phone is basically STUCK.
I have tried flashing all stock firmwares that are, i have tried flashing all available kernels, i have tried Factory resetting the phone and wiping the catch, i have tried every guide on XDA and nothing ever worked for me.
i apologize for the long explanation, but i just dont want people to think that i am repeating the same question over and over since a similar question was asked by other members on XDA previously.
Thank you very much for taking the time and reading my question.
Do you still have recovery mode?
EDIT: In this thread: http://forum.xda-developers.com/sprint-galaxy-s6/help/custom-binary-blocked-frp-lock-t3152054 every person that had the problem fixed it by flashing the stock firmware. make sure you're flashing the stock firmware that's the exact same as the firmware when your phone worked. So if you were on OI1 for example, you have to flash OI1 firmware or it wouldn't work. Try a couple times too, I've heard ODIN can be wonky sometimes.
Thank you for the reply, i actually did try all stock firmwares, it was on 5.1.1 OF8 before it bricked, and i tried that one too, no luck, flashing gives me successful, but phone is still stuck on the boot loop, i hope i can find a solution for this issue.
ameenz77 said:
Thank you for the reply, i actually did try all stock firmwares, it was on 5.1.1 OF8 before it bricked, and i tried that one too, no luck, flashing gives me successful, but phone is still stuck on the boot loop, i hope i can find a solution for this issue.
Click to expand...
Click to collapse
Try to factory reset in recovery and flash the tar trough ODIN again. If that doesn't work, try to restore it with SmartSwitch. A lot of people have success restoring their phone that way. If that doesn't work then I don't know.

Phone stuck in factory reset

Hi. I'm unexperienced with this in general, so please bear with me. I treid to search similar threads but didn't find anything about my problem exactly.
I've a rooted European (Exynos, Polish or German distribution) version of Note 4. I don't run any custom OS nor did I make any changes to my phone in the last few months. As of now, it's running Lollipop.
A few weeks ago, my phone started randomly rebooting. I blamed it on old apps, did a check with antivirus and uninstalled some apps I wasn't sure about. But the problem grew worse (reboot every few minutes). I've erased all apps that had something to do with my root (Lucky Patcher was constantly popping up in my SU logs in the same minute my phone rebooted, so I uninstalled all patched app and then Lucky Patcher), deleted almost everything, checked that system apps were all the newest version. Nothing helped so I thought a factory reset seems like the best option now. I went to the Settings and did a factory reset.
But now I'M STUCK. There is this picture of the Android with the blue web that should be turning (but isn't) the screen says "Systemupdate wird installiert" (system update is installing), the picture disappears (black screen) and comes back every few seconds. There is no blue line signalising progress or anything. All this for some two hours now.
I don't want to try anything myself because I don't want to make my phone a brick. Does any of you know what my problem could be? Thanks.
I'm not too sure why your device is stuck in an update loop. But are you positive you havent tried flashing anything to your device??
---------- Post added at 05:28 PM ---------- Previous post was at 05:23 PM ----------
Wait a second, you're saying you arent running a custom rom, yet your device has root with superuser.. Therefore you should also have a custom firmware flashed to your device.. Twrp or cwm. Irecommend twrp. If you have a custom recovery. Then boot in to recovery mode and clear cache/dalvik wipe/ factory reset etc.
TheTecXpert said:
I'm not too sure why your device is stuck in an update loop. But are you positive you havent tried flashing anything to your device??
---------- Post added at 05:28 PM ---------- Previous post was at 05:23 PM ----------
Wait a second, you're saying you arent running a custom rom, yet your device has root with superuser.. Therefore you should also have a custom firmware flashed to your device.. Twrp or cwm. Irecommend twrp. If you have a custom recovery. Then boot in to recovery mode and clear cache/dalvik wipe/ factory reset etc.
Click to expand...
Click to collapse
Positive I haven't flashed anything. I didn't even connect it to a computer.
I think that my device has cwm but it's long since I've used it. I tried getting into recovery mode and the only thing I can see is the android figure with the blue ball, no menu, no anything.
UPDATE: I flashed twrp with ODIN, phone rebooted like after a factory reset.
keinalu said:
Hi. I'm unexperienced with this in general, so please bear with me. I treid to search similar threads but didn't find anything about my problem exactly.
I've a rooted European (Exynos, Polish or German distribution) version of Note 4. I don't run any custom OS nor did I make any changes to my phone in the last few months. As of now, it's running Lollipop.
A few weeks ago, my phone started randomly rebooting. I blamed it on old apps, did a check with antivirus and uninstalled some apps I wasn't sure about. But the problem grew worse (reboot every few minutes). I've erased all apps that had something to do with my root (Lucky Patcher was constantly popping up in my SU logs in the same minute my phone rebooted, so I uninstalled all patched app and then Lucky Patcher), deleted almost everything, checked that system apps were all the newest version. Nothing helped so I thought a factory reset seems like the best option now. I went to the Settings and did a factory reset.
But now I'M STUCK. There is this picture of the Android with the blue web that should be turning (but isn't) the screen says "Systemupdate wird installiert" (system update is installing), the picture disappears (black screen) and comes back every few seconds. There is no blue line signalising progress or anything. All this for some two hours now.
I don't want to try anything myself because I don't want to make my phone a brick. Does any of you know what my problem could be? Thanks.
Click to expand...
Click to collapse
There is a chance that you put your phone in odin download mode instead doing factory reset
keinalu said:
UPDATE: I flashed twrp with ODIN, phone rebooted like after a factory reset.
Click to expand...
Click to collapse
So you got it working now? Or?? You mean rebooted successfully? Or rebooted back in to download mode?
TheTecXpert said:
So you got it working now? Or?? You mean rebooted successfully? Or rebooted back in to download mode?
Click to expand...
Click to collapse
There seems to be no problem now, my phone went back from 5.1 to 5.0.1 though. Maybe the whole thing started because of the last update. I tested and I can get to recovery mode normally, so I did a back-up just in case somethin goes wrong again.
If you managed to flash twrp and successfully booted back in to your device, then i recommend rebooting back into twrp recovery, and doing a cache and dalvik cache from within the recovery menu. And if you want root access, download the latest superSU (itll be a zip file), copy the file to the download folder of your internal storage, reboot in to your recovery, install the superSU zip file you downloaded, once its indtalled, wipe both caches again. And reboot.
Let me know how you go, and if you get stuck somewhere, dont be afraid to ask. Im happy to help

Sprint Note 5 Boot-looping trouble!?

This is my first post and I'm in need of some help that I can't seem to find anywhere when searching the internet. I'm not a developer nor am I close lol I just have tons of fun learning the development process - it's seriously one of my favorite things to do. Anyways I've messed up royally with my Galaxy Note 5 N910P and I'm stumped on what I should do next! So here's the issue: My Note 5 will not stop boot looping!!! I've flashed stock, almost every version that I'm able to and nothing has worked. The last thing I remember doing before it started this b.s is rooting with CF Auto root. I've always used twrp then flashed Supersu and the dm verity and never had issue! But after flashing the CF Auto root I kept getting kernel is not seandroid enforcing and then the dreadful boot loop issue that has been going on for three days now! Is there something i'm missing? or not doing right? Please message me and let me know, and if this is the wrong place to post about this, I dont mind if my post is taken down just at least help with my question some how! Thank you, XDA is my favorite place - you guys are awesome, I don't trust any other source!!!
saywhhaa33 said:
This is my first post and I'm in need of some help that I can't seem to find anywhere when searching the internet. I'm not a developer nor am I close lol I just have tons of fun learning the development process - it's seriously one of my favorite things to do. Anyways I've messed up royally with my Galaxy Note 5 N910P and I'm stumped on what I should do next! So here's the issue: My Note 5 will not stop boot looping!!! I've flashed stock, almost every version that I'm able to and nothing has worked. The last thing I remember doing before it started this b.s is rooting with CF Auto root. I've always used twrp then flashed Supersu and the dm verity and never had issue! But after flashing the CF Auto root I kept getting kernel is not seandroid enforcing and then the dreadful boot loop issue that has been going on for three days now! Is there something i'm missing? or not doing right? Please message me and let me know, and if this is the wrong place to post about this, I dont mind if my post is taken down just at least help with my question some how! Thank you, XDA is my favorite place - you guys are awesome, I don't trust any other source!!!
Click to expand...
Click to collapse
First of all you have entered wrong model no here note 5 model no should be SM-N920xx
1)Have you enabled Oem unlocking from developers option before flashing twrp and cf-autoroot using odin? If not then you done a mistake!!
2) Have you tried to flash latest stock firmware using odin with latest usb drivers installed on you pc and proper odin flashing guide?(Flash latest 6.0.1 for your device with latest usb drivers installed on pc and connect phone to main usb port using original usb cable) After flashing stock rom if your facing bootloop then you can try reset through stock recovery (Press volume down+power button to switch off your phone..When screen shuts off immediately press volume up+power+home key simultaneously untill you see Samsung galaxy note 5 logo, release keys..You are now in stock recovery from there choose wipe data/factory reset..After reset complete reboot your device)
3)If you can boot into twrp recovery normally then flash any custom rom suitable for your device i.e. for sm-n920p..Custom roms are pre-rooted so no need to flash cf-autoroot..Flash custom rom, if you successfully boot up the rom( It's difficult to boot custom rom though if you haven't enabled oem unlocking you will face custom binary is blocked by frp protection),then enable oem unlocking from developers option and try flashing stock rom again
4) Next option for you is download Samsung smart switch for pc, install latest usb drivers on your pc, connect your phone to pc in download mode(Press volume down+power+home button simultaneously),in smartswitch select emergency software recovery, it will ask you imei,model no and serial no which you can find either on box or back panel of your phone,smartswitch will detect latest stock firmware for your device, hit update now,give some time until update complete..Your device will be automatically reboot..If even you face bootlopp, then goto stock recovery(Press volume down+power button to switch off your phone..When screen shuts off immediately press volume up+power+home key simultaneously untill you see Samsung galaxy note 5 logo, release keys..You are now in stock recovery from there choose wipe data/factory reset..After reset complete reboot your device)
**IF SUGGESTION IN SECOND POST HELPS YOU THEN ITS DONE, AVOID NEXT SUGGESTIONS**
Are you sure you can't install cf auto root again to solve it? IF not...
I did a search and got hits for twrp for N910P. Get it loaded, get it wiped and have another shot at success. Next way to get rid of the persistent rooter gone rogue, load up a factory BL + AP. If that doesn't work download another version and try again.
I've enabled OEM unlocking, flashed latest stock AP...BL.. And so on, factory reset in both factory and TWRP. I have also tried flashing CF Auto root again to see if that would fix it also custom ROMs bootloop except for CM13 and Lineage OS- Which is weird because the ROMs are for the SM N920C model and I'm and Sprint model, So I don't understand that. Weird!! Everything recognizes me as SM N920C except when I am in download mode. Also, having no imei or any back ups make its even harder since my computer completely crashed on me because I am unable to use Samsung smart switch due to the wrong model and null imei. So I'm completely stumped with this issue. Not sure if its a corrupted partition or folders not being in the correct folder locations along with wrong permissions, I've literally stressed everything to my knowledge about this and I'm all out of what issues this could be related to

Categories

Resources