Hi everyone!
I have a Samsung Note 4 (SM-910U) Chile version. Came with Firmware N910UXXU1ANJ4 Chile. Then I changed the FW by N910UXXU1ANJ4 New Zealand (Vodafone). I run the automatic updates until the last FW N910UXXU2COJ2 Android 5.1.1.
I did a factory reset.
Had his Samsung account on it and Reactivation Lock was turned on. We put phone on Wifi and tried to turn off Reactivation Lock. Just loops back to same screen and remains turned on.
Correct Password and Email as we were able to hard reset phone and at the Reactivation Lock screen during setup, it was accepted and we continued through to set up phone.
Still Reactivation Lock won't turn off, just loops back to same screen.
So we decided to delete Samsung account from phone.. Email and Password accepted, Samsung account deleted.
Thought we were good. Nope.
Now Reactivation Lock is on, grayed out and we cannot add back the Samsung account. Press on Add Samsung account and nothing happens.
Also cannot do Factory Reset from within Setting. Just press Reset Device and nothing happens.
Thanks for your help!
enter recovery mode and do the factory reset there..
turn off the phone first then
hold power + volume up + home at the same time
Related
I just rooted a brand new Galaxy S4 on i9505xxuemke
Before I encrypted and decrypted several times. Always worked great. Now after root when it should encrypt display shows shortly the green android and then it goes black. Device does not react anymore. After about 1 minute it vibrates and reboots. However I don't have to enter my password to boot. Only to unlock. Now I can go to options and try encrpyting again. Hower same behaviour as before. Any suggestions?
There are no apps installed, no google account and so on. Its factory fresh. I even restored factory settings. Same behaviour.
Any ideas?
I flashed the kitkat firmware and then, after it boot to set up wizzard after i entered my name it asked me thw samsung account. but my reactivation lock is off. What is the problEm? i go to settings and i saw that the lock is no check. And i try to factory resset and it comes again even i off already the reactivation lock. Whats wrong?
I see reactivation lock under security > find my phone. I am able to toggle it on but as soon as i do that i get the standard window message which offer me to cancel or OK the operation.
Whether i OK or cancel, the message screen disappears and it simply resets reactivation lock to off.
any idears? thanks!
Hi, I have a dual SIM S5 which I updated from Lollipop to Marshmallow using the normal phone update feature. I haven't done anything clever like rooting etc. Today I've been exploring 'Find-my-phone' on Samsung's website and am unable to set the Reactivation Lock on the phone. I check the box and get the warning message to remember the password and press OK and then the warning message disappears and I'm left with the Reactivation Lock box unchecked. If I check it I get the warning box again. I didn't try setting the Lock with Lollipop. Any ideas as to how to get it to work. Tried rebooting. Didn't do a factory reset after updating to MM, could this be the problem?
Solved
Found that reactivation lock was selectable immediately after doing a 'Wipe the cache partition' by holding vol up, power and home buttons on phone reboot and selecting this option from the menu.
My S5 did an operating system software update yesterday and same reactivation problem as before so I wiped the cache partition and problem remained so maybe wiping the cache partition does nothing and the solution lies elsewhere. If anybody else has any ideas please chime in.
Reactivation lock is useless anyway, easy to bypass
I've purchased 12 of these Tablets for my company. Out of the box they were android 6.0, as soon as we connected them to WiFi the 7.0 Update option came up so we updated all 12. We then loaded our Comodo MDM enrollment on them. Well Next time they rebooted 9 of them would not come up, they just sit at the samsung screen fading in and out. I went into recovery mode to try factory reset & wipe, I get the message that "mdm does not allow factory reset". So I tried resetting the cache which did nothing as well. So I loaded Odin and booted into odin mode tried to load a stock rom and I get the message that the device is in FRP mode and cannot load a custom image...
I have ALWAYS had droids and I favor Samsungs normally.... I have always rooted and unrooted every device I've ever had, but these have me stumped... I cannot get into USB debugging mode, I cannot get the things to boot at all. Every tutorial requires debugging mode. Samsung Business support is NO help at all. So I turn to the dark side... HELP!!!
cpubugs said:
I've purchased 12 of these Tablets for my company. Out of the box they were android 6.0, as soon as we connected them to WiFi the 7.0 Update option came up so we updated all 12. We then loaded our Comodo MDM enrollment on them. Well Next time they rebooted 9 of them would not come up, they just sit at the samsung screen fading in and out. I went into recovery mode to try factory reset & wipe, I get the message that "mdm does not allow factory reset". So I tried resetting the cache which did nothing as well. So I loaded Odin and booted into odin mode tried to load a stock rom and I get the message that the device is in FRP mode and cannot load a custom image...
I have ALWAYS had droids and I favor Samsungs normally.... I have always rooted and unrooted every device I've ever had, but these have me stumped... I cannot get into USB debugging mode, I cannot get the things to boot at all. Every tutorial requires debugging mode. Samsung Business support is NO help at all. So I turn to the dark side... HELP!!!
Click to expand...
Click to collapse
Sounds to me like the problem isn't with Google's FRP lock but with the Comodo MDM enrollment. First thing I'd do is contact their tech support. The FRP lock doesn't prevent you from flashing a ROM with Odin. The FRP lock would just ask for the Google login and password on the first reboot. And I have seen other security apps blame the FRP lock for not allowing a ROM to flash via Odin.