Related
Hi!
For some strange reason, after flashing a rom, I can't turn off the reactivation lock of my phone. I uncheck it, but when I enter download or recovery mode, it is still turned on..
Anyone faced something like that? Any suggestion would be fine.
Thanks and regards!
Sent from my SM-N9005 using XDA Premium 4 mobile app
It occurs toghether with a boot loop problem, such as described in other thread on this forum..maybe they are related?
Regards!
empat said:
Hi!
For some strange reason, after flashing a rom, I can't turn off the reactivation lock of my phone. I uncheck it, but when I enter download or recovery mode, it is still turned on..
Anyone faced something like that? Any suggestion would be fine.
Thanks and regards!
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Try a factory reset
jaythenut said:
Try a factory reset
Click to expand...
Click to collapse
Thank you for your atention. After many attempts, I finally managed to uncheck the reactivation lock, problem solved. I still have this boot loop bug reported on this forum, but this is anothe issue...
Regards!
empat said:
Thank you for your atention. After many attempts, I finally managed to uncheck the reactivation lock, problem solved. I still have this boot loop bug reported on this forum, but this is anothe issue...
Regards!
Click to expand...
Click to collapse
How did you solve it?
empat said:
Thank you for your atention. After many attempts, I finally managed to uncheck the reactivation lock, problem solved. I still have this boot loop bug reported on this forum, but this is anothe issue...
Regards!
Click to expand...
Click to collapse
me too.I have the same problems as you did. Reactivation lock on. always boot loop. HOW to lock off
I had a similar issue. I can't remember exactly how I got there, but I had the boot loops and wasn't able to flash anything via Odin/twrp. The way I solved it was by flashing a stock rom through Odin (equivalent to my build number not a newer one as that wouldn't flash either)
Sent from my SM-N9005 using XDA Premium 4 mobile app
hi .. i have the same issue. is there a way to disable reactivation lock without flashing a new rom? i just want to enter the recovery mode
Same Problem
empat said:
It occurs toghether with a boot loop problem, such as described in other thread on this forum..maybe they are related?
Regards!
Click to expand...
Click to collapse
I am having the same problem and in the boot loop problem. How to resolve this issue?
Which is the other thread on this forum where this is discussed? let me know please.
sshamim said:
I am having the same problem and in the boot loop problem. How to resolve this issue?
Which is the other thread on this forum where this is discussed? let me know please.
Click to expand...
Click to collapse
Hey i had the same problem and solved it. I have tried many things like reflashing recovery and afther that reflashing root and those went failed.
-->I was unable to do factory default.
-->reactivation lock was unchecked but was strangly still active
-->I also tried reflashing the stock firmware from
HTML:
www.sammobile.com/firmwares/
and strangly enough this one completed 100% and it solved my problem with reactivation lock.
so the only way to solve this issues is to flash the stock rom ?
Me too with lollipop
Hi I'm ressurecting this subject because I just have the problem and i'm not able to install another recovery or root my device. Even installing a stock rom fom Sammobile doesn't solve the problem :crying:
Every time i uncheck lock reactivation button it steels activate
I'm using lollipop BNL9 stock rom
Thanks for help
azerty-666 said:
Hi I'm ressurecting this subject because I just have the problem and i'm not able to install another recovery or root my device. Even installing a stock rom fom Sammobile doesn't solve the problem :crying:
Every time i uncheck lock reactivation button it steels activate
I'm using lollipop BNL9 stock rom
Thanks for help
Click to expand...
Click to collapse
This exact thing is happening to my galaxy s5 running lollipop firmware. I cannot unchecked the reactivation lock in security, even with the correct password. I can't flash custom recovery or root cause reactivation lock always enables Odin to fail! Did you find any solutions?
At last
dbowmanda115 said:
This exact thing is happening to my galaxy s5 running lollipop firmware. I cannot unchecked the reactivation lock in security, even with the correct password. I can't flash custom recovery or root cause reactivation lock always enables Odin to fail! Did you find any solutions?
Click to expand...
Click to collapse
Yes at last I called Samsung support to get help and and athe solution may be problematic for some people. In fact you need to suppress your Samsung Service account at http://account.samsung.com :crying: , after that reboot your phone and that's it. You can now check in download mode that reactivation lock is now :fingers-crossed: . When you do that you will loss all apps you buy through Galaxy Apps and nedd to eventually recreate a new account,if needed.
azerty-666 said:
Yes at last I called Samsung support to get help and and athe solution may be problematic for some people. In fact you need to suppress your Samsung Service account at http://account.samsung.com :crying: , after that reboot your phone and that's it. You can now check in download mode that reactivation lock is now :fingers-crossed: . When you do that you will loss all apps you buy through Galaxy Apps and nedd to eventually recreate a new account,if needed.
Click to expand...
Click to collapse
Thanks for your help! I didn't read this until after I tried another solution. I flashed stock 4.4.2 and I could uncheck without any hassle. It seems Lollipop was the problem.
Hey.
Having the same problem here. What do you mean with "suppress your Samsung Service account"? Delete the account?
azerty-666 said:
Yes at last I called Samsung support to get help and and athe solution may be problematic for some people. In fact you need to suppress your Samsung Service account at http://account.samsung.com :crying: , after that reboot your phone and that's it. You can now check in download mode that reactivation lock is now :fingers-crossed: . When you do that you will loss all apps you buy through Galaxy Apps and nedd to eventually recreate a new account,if needed.
Click to expand...
Click to collapse
by "suppressing" the account, do you mean deleting the samsung account? because i dont see any other option there.
i dont want to lose my data and apps, so a factory reset is out of option.
Infortunately yes. You must delete your Samsung account
azerty-666 said:
Infortunately yes. You must delete your Samsung account
Click to expand...
Click to collapse
Thanks buddy.. Just one more question.. deleting the account wont affect anything else than the paid galaxy apps.. right? i mean, will it interfere with other phone functionalities or not?
Edit: I just deleted my samsung account online and restarted my phone. Still unable to uncheck the reactivation lock. any ideas?
Edit: I had to factory reset my phone from the stock recovery. When it booted it asked for samsung account password, I clicked on forgot password, created a new password from my laptop and used that to login to the samsung account. After that I was unable to uncheck the reactivation lock. Downside is that I had to lose my data, I could get my apps back from the google account.
I think the account is not deleted because I had exactly the same symptoms before deleting my account.
Did you follow my link on the previous messages?
I flashed XtreStoLite rom through custom recovery, everything went well. During the setup menus before entering the os it asked something about a reactivation lock. It sounded good so i turned it on. Next thing i know i cant boot into my custom recovery and i can't boot the phone. I put it in download mode flash the first thing i find with odin (it failed) but the phones boots. (I found this solution online)
There is no reactivation lock in settings but i can find it when i search settings. Needless to say when I disable the reactivation and search for it again it is still enabled.
Kies will not recognise it. There is no Samsung account of any kind in this rom. anything i've seen anyway.
When i try to factory reset through settings it says "Unfortunately, Settings has stopped".
What do i do? pls help
the phone is an SM-G900F running the latest XtreStoLite_ROM_v2.2_LP_ with a custom touch recovery which i cannot access.
As far as some users who encountered this problem said... Flashing a stock ROM with the same build number through odin was able to fix this issue.
Riyal said:
As far as some users who encountered this problem said... Flashing a stock ROM with the same build number through odin was able to fix this issue.
Click to expand...
Click to collapse
i did that everything works fine but i can't install a custom recovery or root and i cant turn off reactivation lock. its in settings now but when i deactivate it it asks me to login to my samsung account. i do that it signs in fine but it is still enabled.
Like I said Flashing a stock ROM with the same build number... What I meant was a ROM that wasn't prepackaged by any members of xda but instead was built from samsung. Perhaps try using Kies to factory reset your phone instead.
When reactivation lock is on you can't boot to recovery & can't debrand your phone. But that doesn't block your from reflashing a ROM with the same build number as your current custom ROM has.
So what you need to do is
1. Flash a full stock ROM.
2. Factory reset
3. From Setup wizard login your samsung account and other details and disable reactivation lock.
4. Install custom recovery and root your device again.
rockon92 said:
i did that everything works fine but i can't install a custom recovery or root and i cant turn off reactivation lock. its in settings now but when i deactivate it it asks me to login to my samsung account. i do that it signs in fine but it is still enabled.
Click to expand...
Click to collapse
Back to Kitkat and disable.
Then upgrade to Lollipop and install the custom files.
thank you very much everybody! its working fine now!
i just downgraded to kit kat 4.4.2 logged in to my samsung account and disabled reactivation lock with no problems. i then update with ota and everything is fine until now!
thanks again!
On.my 900f s5 uk edition on lollipop the reactivation lock was in the security menu. I had to flash twrp using flashify as it locked my phone when using odin and the twrp app. Of course now I know to deactivate the lock first lol
tony_76 said:
On.my 900f s5 uk edition on lollipop the reactivation lock was in the security menu. I had to flash twrp using flashify as it locked my phone when using odin and the twrp app. Of course now I know to deactivate the lock first lol
Click to expand...
Click to collapse
I already had twrp when i flashed the custom rom and during the setup the custom rom asked to enable reactivation lock, it sounded good at the time..little did i know! next time i reboot the phone into recovery to flash the aroma addon package for the rom i used, it locked the phone down.
I had to flash something with odin to make it boot into the os, the flash failed but it did boot! then i flashed the stock kit kat 4.4.2 from sammobile, did the setup, logged in to my samsung account and reactivation lock disabled just fine! did the OTA updates then root, installed twrp recovery and installed the xtresto rom with the aroma addon package.
Everything seems to be fine now!
I'm in the same boat. I can't even factory reset and cannot turn of activation lock KK.
phone still works. i just can't access recovery. cannot use odin to push kitkat back.
cannot use TWRP either. i'm stuck.
Damn XtreSto Lite Rom...what the heck.
found a way. Download and install Kies 3 on your comp. Follow the Firmware upgrade and initialization. it'll flash back to stock. follow the instructions.
Omg took me forever to find this solution.
melloyellowkc said:
found a way. Download and install Kies 3 on your comp. Follow the Firmware upgrade and initialization. it'll flash back to stock. follow the instructions.
Omg took me forever to find this solution.
Click to expand...
Click to collapse
it seems that for some people kies works to recover the phone (for me it didn't) and for some odin works to push kit kat and disable reactivation lock
anyway am glad you fixed it
Flash something from odin. The flash will fail but the phone boots afterwards. Don't know why this works but it did for me and rocking above. Once booted turn off the reactivation lock.
Try to flash kitkat firmware original with bootloader end pit file for ur device model you find in xda
What worked for me!!
Had the same problem. The rom locked me out. (reactivation lock was activated)
I flashed the stock LOLLIPOP firmware i got from sammobile using odin, the KITKAT firmware does not flash.
Logged into the phone with my original samsung account.
Removed that account from the device
Created a new samsung account from the computer.
Added that account to the device.
Turned of reactivation lock, and viola!! it worked
do i need to downgrade to kitkat just to make it work? remote control and reactivation lock? before im using stock rom rooted but still doesn't work. then i tried custom rom it's working but the only problem is private mode is failed to enable. then i switch to another custom rom then almost perfect but the remote control and reactivation lock is not working.
Just letting people know:
I had the same issue as OP, except that when I was locked in the first time setup thing, trying to log in with my Samsung account credentials resulted in the error message "Processing failed". I tried the reactivation lock bypassing trick that takes advantage of the samsung default browser and acessibility settings (can be foun on YouTube) but it still didn't help because when I pressed to add a Samsung account, nothing happened. It was probably due to some of Samsungs files missing on my phone due to the previous XtreStoLite installation that I was originally updating when I got into this mess.
What fixed it for me was flashing the stock 4.4.2 KitKat firmware from sammobile with Odin and THEN doing the reactivation lock bypassing trick. Just downgrading to KitKat and trying to login normally in the first time setup thingy didn't work as it resulted in the same "Processing failed" error as before on Lollipop. You guys have no idea how happy I was when I booted to download mode and saw "REACTIVATION LOCK(KK): OFF". I had already lost almost all hope! :victory:
i have a more sexy problem ! i don`t have the reactivation lock option on website not even on my phone....! how to disable it ?
melloyellowkc said:
I'm in the same boat. I can't even factory reset and cannot turn of activation lock KK.
phone still works. i just can't access recovery. cannot use odin to push kitkat back.
cannot use TWRP either. i'm stuck.
Damn XtreSto Lite Rom...what the heck.
Click to expand...
Click to collapse
same here... my g900w8 is on download mode only now!
mp_79 said:
same here... my g900w8 is on download mode only now!
Click to expand...
Click to collapse
Thanks for your idea a few days helped me deactived my samsung s5. it has the same problem when i up rom xtrestolite 2.2 and active reactivation lock without knowledge what is it.
I declare my way:
1. find stock rom with same baseband in sammobile.com, there are 2 version: 5.0 and 4.4.2, you should choose both and use 4.4.2 first, if success, next step.
2. use odin, in tab AP choose file rom above
3. pass, finish
4. find on youtube "how to remove or bypass reactivation lock", find correct version for you.
5. finish, enjoy it
sorry my bad english
i flashed with 4.4.2 many time but not remove reactivation lock still here not disable
Long story short, the re-activation lock on my partners S5 (g900i) came on, and when deactivated it didn't go away like it should have.
I can use the phone completely normal except i cant login to a samsung account (it says network error or doesn't do anything) - and i'm locked out of ODIN so i cant flash a stock ROM, or custom recovery.
All i'd like to do to make it properly usable again, is root the damn thing but i'm not aware of any root methods for lollipop that don't use a custom recovery.
Anyone know of a root method i can use from within the phone itself, or over USB from the PC or something?
Reactivation lock should still allow you to flash a KK ROM, log into the Samsung account and disable the lock
That's how most people fix Lollipop with the same problem
AFAIK, there are no alternative root methods for Lollipop that don't require ODIN, (CF Auto Root works)
http://forum.xda-developers.com/showthread.php?t=2696537
*Detection* said:
Reactivation lock should still allow you to flash a KK ROM, log into the Samsung account and disable the lock
That's how most people fix Lollipop with the same problem
AFAIK, there are no alternative root methods for Lollipop that don't require ODIN, (CF Auto Root works)
http://forum.xda-developers.com/showthread.php?t=2696537
Click to expand...
Click to collapse
unfortunately kitkat is not recognising the account, where lollipop kinda does but then glitches out.
is it possible to ODIN flash a rooted stock ROM?
Mussels84 said:
unfortunately kitkat is not recognising the account, where lollipop kinda does but then glitches out.
is it possible to ODIN flash a rooted stock ROM?
Click to expand...
Click to collapse
Yea, you should be able to ODIN flash your phone in any state, so long as it boots into download mode
But the only way I've seen to disable a stuck reactivation lock is to downgrade to KK and log in / disable it from there, then upgrade back to LP
Are you sure the credentials for the samsung account are correct? - Maybe try resetting the password on a PC first so you are 100% sure
*Detection* said:
Yea, you should be able to ODIN flash your phone in any state, so long as it boots into download mode
But the only way I've seen to disable a stuck reactivation lock is to downgrade to KK and log in / disable it from there, then upgrade back to LP
Are you sure the credentials for the samsung account are correct? - Maybe try resetting the password on a PC first so you are 100% sure
Click to expand...
Click to collapse
On KK, the samsung account isnt accepted. on lollipop i can get in, but its like it partially unlocks only - i can use the phone but cant untick the activation lock button, and i cant login to a samsung account (it shows none as active)
I figured root would let me force-clear the data on the samsung apps and possibly resolve the issue.
Mussels84 said:
On KK, the samsung account isnt accepted. on lollipop i can get in, but its like it partially unlocks only - i can use the phone but cant untick the activation lock button, and i cant login to a samsung account (it shows none as active)
Click to expand...
Click to collapse
Ive just remembered, there is a video on how to bypass the lock
https://www.youtube.com/watch?v=E41tLyi59II
Another possible method
http://forum.gsmhosting.com/vbb/f77...ck-solution-galaxy-s5-no-root-needed-1865438/
*Detection* said:
Ive just remembered, there is a video on how to bypass the lock
https://www.youtube.com/watch?v=E41tLyi59II
Another possible method
http://forum.gsmhosting.com/vbb/f77...ck-solution-galaxy-s5-no-root-needed-1865438/
Click to expand...
Click to collapse
those methods have been fixed because there is no blue email link to click, even on KK firmwares.
as for the lollipop videos, they show you being able to sign into any app that uses samsung accounts and that one doesnt work for me either - they popup and disappear. maybe i need an older lollipop build...
anyone got a mega link for one of the first G900i 5.0 firmwares?
i waited for sammobiles slow ass downloads and flashed the initial 5.0 release for the S5 and got an even weirder result - it asked if i wanted to activate the lock.
it allowed me to say no... but same damn bug! once i'm into the phone, the tickbox turns itself back on automatically! arrrgghh
husainbeg786786 said:
Click to expand...
Click to collapse
uh, thanks?
Hello,
I have a note 4 (Italian) blocked on the lockscreen.
after updating to 5.1 lollipopop (samsung official update via wifi),
the fingerprint reader has started to give some problems, then in about 24 hours by the update the phone does not ask me more unlocking fingerprint, but only by backup password;
but also by entering the backup password will not unlock, and says password wrong.
unfortunately debugging is not active ....
What can I do before performing a hard reset?
thanks!
Happened twice with my phone ...at last it accepted the backup password. .
Sent from my SM-N910C using Tapatalk
i don't think that work on my note.... i have I tried a million times
Help!!
Doesnt it give you an Unlock via Google option?
Use Find my phone for unlock
You can unlock your phone screen with browser.
https:// findmymobile samsung com
Do hard reset if u don't find solution.
I think there is a way that's need TWRP recovery and you must flash a file!
Sent from my SM-N920C using Tapatalk
unfortunately I tried using Google Android Device to replace the password and lock the phone but it says it on the phone already has a password ....
I did not want to make a hard reset because I do not have a data backup ....
I can use this procedure http://forum.xda-developers.com/not...ck-screen-pattern-password-pin-t2948336/page7 ? But I do not have root permissions, and I would not risk after knox 0x1 because I noticed a spot in the display that I should replace warranty
thanks
mdp987 said:
unfortunately I tried using Google Android Device to replace the password and lock the phone but it says it on the phone already has a password ....
I did not want to make a hard reset because I do not have a data backup ....
I can use this procedure http://forum.xda-developers.com/not...ck-screen-pattern-password-pin-t2948336/page7 ? But I do not have root permissions, and I would not risk after knox 0x1 because I noticed a spot in the display that I should replace warranty
thanks
Click to expand...
Click to collapse
You can't use it without root...
Sorry.
I can do is root and then go back?
mdp987 said:
I can do is root and then go back?
Click to expand...
Click to collapse
You can always go back to your original software after root bat you will trip Knox for ever that mean you will void your warranty.
I saw that came out a firmware in late November N910FXXS1COK2 always based on 5.1.1 but with the fix, if I did the flash of this by Odin on my mobile in theory should fix it if it really had been caused by the previous update?
Odin also works with phone locked and debugging disabled?
thank you
So long story short I was intoxicated and for some reason disabled OEM in debugging then sometime later I restarted my tablet to get the frp binary locked. It has a custom rom with twrp I absolutely need the data off of this tablet and the only way I see is to reinstall the default os through Odin but that wipes the device I need a method to get the data off of the tablet or a method to bypass frp entirely it would be mighty appreciated if I could have some help
Why don't you try a backup in TWRP?
Reinstalling the stock firmware with Odin won't wipe the device.
slop_me said:
So long story short I was intoxicated and for some reason disabled OEM in debugging then sometime later I restarted my tablet to get the frp binary locked. It has a custom rom with twrp I absolutely need the data off of this tablet and the only way I see is to reinstall the default os through Odin but that wipes the device I need a method to get the data off of the tablet or a method to bypass frp entirely it would be mighty appreciated if I could have some help
Click to expand...
Click to collapse
It's difficult to say if you can keep your data. The binary FRP lock is quite different that the average FRP lock that's associated with the Google sign in. Usually whenever you trip the binary lock it's because some firmware was installed such as a Root or a ROM that was flawed or invalid. It's an overstacking of binaries and therefore you get a "Custom Binaries Blocked by FRP Lock" notification. I've had this problem on another varient of the Tab A, the Galaxy Tab A6 SM-T580. I have found about four diferent variations of this. You may not have turned off OEM because in Binary lock it will act like you have. Possible reason to think that is the way it acts in Download Mode where you can't seem to flash anything especially the official firmware. Sound familiar?
Version 1. If you try to go to Recovery you get redirected to a screen similar to the Download Mode. In the upper left are red lettered "Custom Binaries Blocked by FRP Lock.. Download Mode is accessable but won't initialize when trying to flash stock firmware. Binary 4 FRP Unlock file was accepted and flashed in by Odin3. Stock firmware installs afterwards.
Version 2. Device is stuck in bootloop. "Custom Binaries Blocked by FRP Lock" appears on Logo screen. Recovery and Download Modes are so far, useless. Binary 4 FRP Unlock used, no positive results. Binary U 4 used. Positive result. Stock firmware flashed in afterwards.
Version 3. "Custom Binaries Blocked by FRP Lock" appears on Download Mode which either stalls right after or fails to initialize. Binary 4 FRP Unlock and Binary U 4 yeild no positive results. (This ones on it's way to me).
Version 4. "Custom Binaries Blocked by FRP Lock appears on Recovery Mode. Download Mode useless. I'm currently following this one.
Solution: I don't know if the one I have will work, they may be device specific. Research for a "SM-T280 Binary 4 FRP Unlock" which I couldn't yet find.
Casper Young said:
It's difficult to say if you can keep your data. The binary FRP lock is quite different that the average FRP lock that's associated with the Google sign in. Usually whenever you trip the binary lock it's because some firmware was installed such as a Root or a ROM that was flawed or invalid. It's an overstacking of binaries and therefore you get a "Custom Binaries Blocked by FRP Lock" notification. I've had this problem on another varient of the Tab A, the Galaxy Tab A6 SM-T580. I have found about four diferent variations of this. You may not have turned off OEM because in Binary lock it will act like you have. Possible reason to think that is the way it acts in Download Mode where you can't seem to flash anything especially the official firmware. Sound familiar?
Version 1. If you try to go to Recovery you get redirected to a screen similar to the Download Mode. In the upper left are red lettered "Custom Binaries Blocked by FRP Lock..
Solution: I don't know if the one I have will work, they may be device specific. Research for a "SM-T280 Binary 4 FRP Unlock"
But I couldn't find one.
Here's my post, it may help.
https://forum.xda-developers.com/general/help/custom-binary-blocked-frp-lock-2019-t3979661
Click to expand...
Click to collapse
Nothing needs to be done except install the stock firmware.
The device hasn't been reset so no need for any kind of bypass.
FRP has kicked in purely because unsigned software is installed.
Replace the unsigned software with stock and it'll boot just fine. Data fully intact.
ashyx said:
Nothing needs to be done except install the stock firmware.
The device hasn't been reset so no need for any kind of bypass.
FRP has kicked in purely because unsigned software is installed.
Replace the unsigned software with stock and it'll boot just fine. Data fully intact.
Click to expand...
Click to collapse
I hate to argue with you but that wasn't so easy with mine. While in Binary FRP lock I, along with a few others that have the SM-T580 or the SM-T585 couldn't use Download Mode to flash in the official stock firmware. Trial and error followed. The solve was first I had to flash in the Binary FRP Unlock and then I could flash in the firmware. With another device the owner tried the Binary Frp Unlock which didn't fix it. Later he flashed in the U4 Binary and that worked for him. I passed the info along to some others in the same predicament and it helped them. So I don't know what to tell you but what you're stating is not always applicable.
Casper Young said:
I hate to argue with you but that wasn't so easy with mine. While in Binary FRP lock I, along with a few others that have the SM-T580 or the SM-T585 couldn't use Download Mode to flash in the official stock firmware. Trial and error followed. The solve was first I had to flash in the Binary FRP Unlock and then I could flash in the firmware. With another device the owner tried the Binary Frp Unlock which didn't fix it. Later he flashed in the U4 Binary and that worked for him. I passed the info along to some others in the same predicament and it helped them. So I don't know what to tell you but what you're stating is not always applicable.
Click to expand...
Click to collapse
Trust me, I have 3 of these devices. I've bricked them, frp locked them every possible way during development for this device.
The T580 is a different device and may be more difficult to bypass if and only if FRP has kicked in because of a device reset.
However for EVERY Samsung device that has simply had non stock software installed the only fix that's required is to install the stock firmware.
This is the case on all the Samsung devices I own and I have quite a few from lollipop to Pie.
ashyx said:
Trust me, [not happening!]I have 3 of these devices. I've bricked them, frp locked them every possible way during development for this device. [Well, umm. No, you haven't. And take a wild guess how many devices I have, like that matters.]
The T580 is a different device and may be more difficult to bypass if and only if FRP has kicked in because of a device reset. [Everytime you turn off the device it resets.]
However for EVERY Samsung device that has simply had non stock software installed the only fix that's required is to install the stock firmware. [You obviously have difficulties comprehending that I said otherwise]
This is the case on all the Samsung devices I own and I have quite a few from lollipop to Pie.
Click to expand...
Click to collapse
Wow, you're on a roll ain't ya? Hey ASHYX, dont misjudge me because of my stats you see here. Over a decade ago I was stacking ROMs into my HTC-G1. 3 decades ago I was an Electrical Engineer and Sonar Operator in the Navy. Let me tell you point blank, you're mistaken! Normally you would think you can just flash in stock OTA firmware into the device via Odin3 and you get to return to normal. Well that wasn't the solve for this. This was a new one to me also. If you think you're so right on what you say I'll be more than happy to point you in the direction of some XDA visitors, two of which are still Binary FRP locked. You can try telling them what you just told me and they'll probably call you a blooming idiot. No offense but you could try reading it properly which might help.
I said, [QOUTE] " While in Binary FRP lock I, along with a few others that have the SM-T580 or the SM-T585 couldn't use Download Mode to flash in the official stock firmware. [END QOUTE]
Take my word for it, the method you stated was already tried AND DID NOT WORK!
If you want to insist you're all that, here ya go, these people need your expertise in development
https://forum.xda-developers.com/ga...frp-locked-t3772512/post80420061#post80420061
Data loss when flashing stock firmware.
ashyx said:
Reinstalling the stock firmware with Odin won't wipe the device.
Click to expand...
Click to collapse
That depends on which stock firmware you're using. Typically what you get OTA (over the air) is the same as the 4File Official Stock Firmware. These are the 4 files that go into each section when using Odin3 to flash firmware. BL is for the Bootloader which controls security, start-up and recovery. AP is Android Partitioning, CP is Cellular Processor. Now let's talk about the CSC. file. The 4File contains two CSC files, one is listed as HOME CSC. If you flash the CSC file you will lose your App data. If you flash the HOME CSC you do not lose your App data.
Casper Young said:
That depends on which stock firmware you're using. Typically what you get OTA (over the air) is the same as the 4File Official Stock Firmware. These are the 4 files that go into each section when using Odin3 to flash firmware. BL is for the Bootloader which controls security, start-up and recovery. AP is Android Partitioning, CP is Cellular Processor. Now let's talk about the CSC. file. The 4File contains two CSC files, one is listed as HOME CSC. If you flash the CSC file you will lose your App data. If you flash the HOME CSC you do not lose your App data.
Click to expand...
Click to collapse
ashyx said:
Nothing needs to be done except install the stock firmware.
The device hasn't been reset so no need for any kind of bypass.
FRP has kicked in purely because unsigned software is installed.
Replace the unsigned software with stock and it'll boot just fine. Data fully intact.
Click to expand...
Click to collapse
Thank you for confirming I won't loss any data upon installing the original ROM I did just have a custom ROM installed I was super concerned that I would lose all the data upon installing the original ROM thank you so much <3
slop_me said:
Thank you for confirming I won't loss any data upon installing the original ROM I did just have a custom ROM installed I was super concerned that I would lose all the data upon installing the original ROM thank you so much <3
Click to expand...
Click to collapse
Depends on which custom rom you had installed? If it's stock based on lollipop then you should be fine. If its lineage then it may not boot without a data wipe.
ashyx said:
Depends on which custom rom you had installed? If it's stock based on lollipop then you should be fine. If its lineage then it may not boot without a data wipe.
Click to expand...
Click to collapse
Yeah it was just stock lollipop with a root. Will that cause an issue or am I good to continue?
ashyx said:
Depends on which custom rom you had installed? If it's stock based on lollipop then you should be fine. If its lineage then it may not boot without a data wipe.
Click to expand...
Click to collapse
Props to you thanks for the knowledge it worked flawlessly I mean kinda half way through it did say erasing and I kinda **** the bed and got scared because I really needed the data off of there but my man you are right just flashing stock ROM worked flawlessly everywhere online says it will wipe the device but it didn't. Thank you so much for your fantastic help <3