Related
Hi everyone.
I wanted to root my device and it didn't work, allways got Auth fail recovery on odin and device, until I unchecked the reactivation lock, then it rooted flawlessly.
(I know my google account and password)
I was curious is it safe to stay with reactivation lock checked in case this happens:
Lets say the soft bricks into a boot loop who knows why but recovery still works.. so if I want to factory reset from custom recovery(philz recovery, with Nandroid and efs backed up), I think it is the best to unroot before factory reset(hope I'm wrong), witch will be imposible if the root didn't worked because of the reactivation lock, the unroot won't work too?
I gues before trying any flashing etc is good to uncheck reactivation lock, but I can allways make a mistake and forget it on.
So let me make that short, is it safe to activate ractivation lock when rooted in case something bad happens with the boot start?
I want to activate it for safety but this safety could block me too?
Do you guys keep it on after rooting?
I hope the readers will understand my question and don't get any headakes, sometimes I gould it hard to express myself in english, sorry about that.
alexpu1u said:
So let me make that short, is it safe to activate ractivation lock when rooted in case something bad happens with the boot start?
Click to expand...
Click to collapse
Well reactivation lock is an anti-theft feature. Theft deterrents are good although they only have significant value when they are well implemented. Which is arguable in this case. It's hardly undefeatable. 2 strikes. And can be as annoying as hell in not liking your custom kernel. Strike thr ...
Bottom line, if you are good at making backups and believe in theft deterrents, then enable it. It makes it slightly more likely that a lost phone would make it back to you. Or at least ruin the thief's day. There should always be a way to restore your device if you have a backup and your credentials.
However if you are forgetful, bad with backups or simply have no patience for having to search XDA threads or enter something on a command line to disable reactivation lock and recover from a bootloop, etc.. then obviously don't use it. It could cause you some exasperation if you are in an unbootable state and it is interferring with an Odin flash.
Pick one. And either way try not to lose your phone.
.
That's what I wanted to hear, so it's safe to keep it on if I'm backedup and pacient in case of a problem.
Thank you for your time. I activated it .
alexpu1u said:
That's what I wanted to hear, so it's safe to keep it on if I'm backedup and pacient in case of a problem.
Thank you for your time. I activated it .
Click to expand...
Click to collapse
Well, I'm not concerned with being locked out of my phone permanently. Nor convinced that RA would really stop a stolen phone from being reactivated. But it's plausible that it would delay some thieves from using Odin to obliterate your tracking software.
So a longer window in which it might be possible to pin down your phone's location. Or perhaps spur someone to return your phone in the case of a lost, rather than stolen phone.
Whether to use RA depends mostly on your willingness to put up with some temporary frustration should your phone somehow end up unbootable and you have to jump through a few hoops to disable the reactivation lock.
.
alexpu1u said:
Hi everyone.
I wanted to root my device and it didn't work, allways got Auth fail recovery on odin and device, until I unchecked the reactivation lock, then it rooted flawlessly...
Click to expand...
Click to collapse
But you can't enable this option after root, it does not work!
knox 0x1 (2)
jgfernog said:
But you can't enable this option after root, it does not work!
Click to expand...
Click to collapse
interesting finding from me:
even if you are not root, with samsung knox 0x1 (2) the option is automatically enabled but you won't see it ticked. You can factory reset your phone when you have knox 0x1 (2) and see it will ask for reactivation account in order to by pass the phone. There is no solution. Samsung knox is funny.
MaXi32 said:
interesting finding from me:
even if you are not root, with samsung knox 0x1 (2) the option is automatically enabled but you won't see it ticked. You can factory reset your phone when you have knox 0x1 (2) and see it will ask for reactivation account in order to by pass the phone. There is no solution. Samsung knox is funny.
Click to expand...
Click to collapse
Yeah! There are some problems with it. I saw people saying that their devices had KNOX enabled even with the option unchecked in settings.
I wouldn't bother with reactivation lock for any scenario
1. Easy to bypass
2. Only causes problems for yourself if you forget to disable it before flashing
3. Anyone who knows how to flash a new ROM, which is what it's designed to prevent, can bypass it flashing a KitKat ROM anyway
4. You've lost your phone anyway, they're not gonna give it back because they can't use it
Hi everybody!! I've installed cyanogenmod 11 on galaxy s5 g900f stock with root. Now at boot it show this message: "Kernel is not seandroid enforcing set warranty bit: Kernel". How can I hide it? However the phone works well. The message shows also when I connect it to charger. How can I change the ugly charging battery animation? Thank you in advance
Anyone can help me?
glegoodroid said:
Anyone can help me?
Click to expand...
Click to collapse
i am still currently finding out how to disable the error , by the only way is to flash back Stock ROM into the phone so SnapDragon SECURE BOOT will not have problems will third party kernels . . . , i will update you once i done a research to disable SnapDragon Secure Boot ! :good:
---------- Post added at 09:08 PM ---------- Previous post was at 09:03 PM ----------
When you flashed from MKE the newer locked bootloader JB is already contained 4.3, which now more aggressively responds in conjunction with the eFuse chip if you try a different kernel or recovery on your Galaxy S4 to flash. Not only that you have you now changed in all probability due to the flash the CF-Auto-Root Kernel, the Knox Warranty Void recognition to 0x1, you'll love this regard with the message of life must, because you've made a change in the system by the eFuse- chip and bootloader was detected . If you want to understand it so, the eFuse chip as a kind of guardian because that monitors not only the boot loader, but also the SELinux kernel, and the CWM Recovery . In conjunction with the bootloader, which acts as a kind of BIOS, will now be started for the system normally because of your made flash operations, but detects the change as such, which is out now displayed accordingly. If you have very bad luck now (will most likely also occur), you will get with subsequently installed root apps also some problems that are being monitored by the Knox apps to avoid the additional system modifications you make will. If you do then you bear with the idea that you some Knox Apps example, try the app Titanium Backup to remove it, you'll end up in a subsequent reboot your Galaxy S4 in a bootloop and your Galaxy S4 can not start. This means in turn then for you that you get this error only resolved when you XXUEMKE new flashst the original Samsung firmware build on the PC Odin Flash program on your Galaxy S4. As you will probably notice about my design now, you have almost no more opportunities your Galaxy S4 to manipulate the way you would want it but you yourself to make certain modifications to your usual Galaxy S4, then without problems to get , :good:
Just my fun ......my phone (900M) is with the new bootloader and new modem and then I installed the 2.2 Xtrolite with 900M kernel and tried to enter the recovery to install the update of the rom and it appeared:
samsung reactivated LOCKED(ON)..secure download:enable...UDC start (in download mode).....does not enter recovery....Odin installed with the official firm and now enters the original recovery but does not accept odin to install custom recovery ...FAIL...damn burglar with myself....normal works but only with firm default. No root no fun...finish line form me with S5.
I can not disable activation lock with my own password.
It was a damn Iphone ...
any solution? I've tried a few things and nothing
I had before 2.1 without problems. great rom
Is the result:
reactivation lock problem
Am Stock at this ? my account work but i cant unchech RL
brayhanrd said:
Am Stock at this ? my account work but i cant unchech RL
Click to expand...
Click to collapse
Yes...I will put that **** in the trash
brayhanrd said:
Am Stock at this ? my account work but i cant unchech RL
Click to expand...
Click to collapse
I have the same problem, uncheck reactivation lock then input password. It then comes back to the previous screen with the lock still checked.
I have the exact same problem, put XtreStoLite with the bootloader, modem etc... reactivation lock was on, flashed back to stock to turn it off, now im unable to uncheck the box. I uncheck and it asks me to log into the samsung account... i do this and the box is still checked.
No idea where to go from here.
Fix
1. going to downgrade phone to KIT KAT 4.4.2 OFFICIAL
How to.
1. downgrade kitkat stock from sammobile.com
2. Turn off the Phone Remove battery, to take off Sim Card and Micro SD.
3. Full Wipe Phone on recovery
4.now we are going to Used Odin to Flash 4.4.2 firmewire.
wait to it done. when it get done u go to ur sam account and them go to security and esea like that u can turn off Reactivation Lock
i do by my self. and it work
Now back to XtreStolite 2.2
---------- Post added at 09:57 PM ---------- Previous post was at 09:48 PM ----------
vioSTYLE said:
I have the exact same problem, put XtreStoLite with the bootloader, modem etc... reactivation lock was on, flashed back to stock to turn it off, now im unable to uncheck the box. I uncheck and it asks me to log into the samsung account... i do this and the box is still checked.
No idea where to go from here.
Click to expand...
Click to collapse
Reactivation Lock Fix
1. going to downgrade phone to KIT KAT 4.4.2 OFFICIAL
How to.
1. downgrade kitkat stock from sammobile.com
2. Turn off the Phone Remove battery, to take off Sim Card and Micro SD.
3. Full Wipe Phone on recovery
4.now we are going to Used Odin to Flash 4.4.2 firmewire.
wait to it done. when it get done u go to ur sam account and them go to security and esea like that u can turn off Reactivation Lock
i do by my self. and it work
Now back to XtreStolite 2.2
brayhanrd said:
1. going to downgrade phone to KIT KAT 4.4.2 OFFICIAL
How to.
1. downgrade kitkat stock from sammobile.com
2. Turn off the Phone Remove battery, to take off Sim Card and Micro SD.
3. Full Wipe Phone on recovery
4.now we are going to Used Odin to Flash 4.4.2 firmewire.
wait to it done. when it get done u go to ur sam account and them go to security and esea like that u can turn off Reactivation Lock
i do by my self. and it work
Now back to XtreStolite 2.2
---------- Post added at 09:57 PM ---------- Previous post was at 09:48 PM ----------
Reactivation Lock Fix
1. going to downgrade phone to KIT KAT 4.4.2 OFFICIAL
How to.
1. downgrade kitkat stock from sammobile.com
2. Turn off the Phone Remove battery, to take off Sim Card and Micro SD.
3. Full Wipe Phone on recovery
4.now we are going to Used Odin to Flash 4.4.2 firmewire.
wait to it done. when it get done u go to ur sam account and them go to security and esea like that u can turn off Reactivation Lock
i do by my self. and it work
Now back to XtreStolite 2.2
Click to expand...
Click to collapse
Perfect, WORK.
THANK YOU.
sachs said:
Perfect, WORK.
THANK YOU.
Click to expand...
Click to collapse
You welcome
brayhanrd said:
You welcome
Click to expand...
Click to collapse
Same here, thanks man
THX man, it´s so simple. I tried for a week....
Valeu galera, salvou minha vida e minha noite.
Tecla SAP: Thanks guys. You saved my life and my night
anyone have a link to downgrade to kitkat? using Canadian G900W88VLU1BOC1
got the reactivation lock when i wanted to flash the Aroma package. oh man.
Couldnt find it on sammobile.
much appreciated.
when i tried to use odin to downgrade, it says failed.
steps:
power down phone > Cable plugged > volume down + home + power > volume up . odin > AP> insert kitkat rom> start > Failed.
sigh. this damn XtreStoLite rom screwed me over. can't get past anything because when i got the phone i didnt activate my samsung account. well i did but i never got the e-mail, then I looked in my spam mail, and i couldn't activate it now because the link expired. ffffffffffff!!!!!!!!
It worked for me
brayhanrd said:
1. going to downgrade phone to KIT KAT 4.4.2 OFFICIAL
How to.
1. downgrade kitkat stock from sammobile.com
2. Turn off the Phone Remove battery, to take off Sim Card and Micro SD.
3. Full Wipe Phone on recovery
4.now we are going to Used Odin to Flash 4.4.2 firmewire.
wait to it done. when it get done u go to ur sam account and them go to security and esea like that u can turn off Reactivation Lock
i do by my self. and it work
Now back to XtreStolite 2.2
Thanks X1000
Click to expand...
Click to collapse
SM-N910C
Just if anyone asks himself: the deactivation of the Reactivation Lock works the same way for the galaxy Note 4. Just flash KitKat (4.4.4), register your samsung-account, deactivate the Reactivation Lock in the security settings and you're done!
Note: flashinf/upgrading to newer firmwares does NOT change the Reactivation Lock setting! Once deactivated - it stays deactivated!
A BIG thank you to the original poster of the workaround!
and s6?
I am having the same problem however is the galaxy s6 . Can anyone help ?
hey i need help. So i got my s5 from a friend's brother because the screen on my s7 shattered. anyway when I went to power on the device, it gave me a "custom binary blocked by reactivation lock. Secure fail: Recovery" message. I did some research and found out that pressing the volume down+home+power button at the same time would take me to the odin screen. From there, i needed to reboot the device. Which it did. Now, i tried to factory reset the device but the Reactivation Lock prevented me from doing so. Naturally, i went to turn it off but i didn't know the prior owner's sam account password. I somehow managed to remove the sam accoount from the device (settings>application manager>all>samsung account>clear cache &disable then settings>accounts>samsung account>tap on email>tap on 3 dot menu>remove account). removing the sam account didn't help deactivate the Reactivation Lock. everytime i click on it, it unticks but then ticks itself back on. Eventually my friends brother finally gave me his sam account password but now i have a new issue. I cant add the sam account back on the device! Damn it! i tried the 4 steps but when i get to #3, i cant access the stock recovery. It takes me to the original "custom binary blocked by reactivation lock. Secure fail: Recovery" screen. can anyone please help? My S5 is model SM-G900P completely stock (no root/custom anything).
HI im new here, and also I do have realy new problem.
my phone is: Samsung Galaxy S5 (SM-G900F)
Stock Android 5.0
Problem Explain:
Reactivation Lock, that I accidentally activated was enablad on custom rom XtreStoLite. The biggest problem is that I did not activate my Samsung Account when I enabled it, and now I have stock firmware non -rooted Android 5.0 installed via Kies
I watched couple of youTube videos, but with no luck, I also send message to FindMyMobile but no luck as well.
When I logging to FindMyMobile, I can lock screen, ring to my device, acctually I can do everything except enable and disable reactivation lock.
Please I do realy need help with this
Same problem here.. Can't find reliable solution. Went back to stock ROM and tried to disable it and it didn't work
Downgrade to KitKat, log into accounts on phone, disable reactivation lock has worked for a few people
Thank you for help
*Detection* said:
Downgrade to KitKat, log into accounts on phone, disable reactivation lock has worked for a few people
Click to expand...
Click to collapse
Downgrade by Odin you mean?
if yes, then that is imposible, becase in ODIN MODE says: "REACTIVATION LOCK(KK): ON"
i will try that one, but i guess it will not work.
Thread moved to proper forum.
Treno00 said:
Thank you for help
Downgrade by Odin you mean?
if yes, then that is imposible, becase in ODIN MODE says: "REACTIVATION LOCK(KK): ON"
i will try that one, but i guess it will not work.
Click to expand...
Click to collapse
Yes via ODIN, people have reported success with that method, some with KIES
Fixed
Thank you sooooo much, but I had little problem. So I will explain step by step what I have done.
1. Odin 3.10.6 + Stock Firmware KitKat 4.4.2
2. In options I leave checked F. Reset Time and Auto Reboot
3. After it's done, I stuck in boot logo so
4. Switch phone off and go to recovery mode
5. wipe data/factory reset and wipe cache partition
6. Reboot device and, yes. system is booted
7. Then after setting up I went to Settings>Security>Reactivation Lock (but I did use Mobile Data, don't know about WiFi)
8. DONE!
PS. You can upgrade your android via Kies from 4.4.2 to 5.0
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
Mr. Clown said:
Thread moved to proper forum.
Click to expand...
Click to collapse
Maybe merge with existing thread? http://forum.xda-developers.com/galaxy-s5/help/reactivation-lock-t3118566
me also i can't activate reactivation lock and remote control.
---------- Post added at 03:57 AM ---------- Previous post was at 03:51 AM ----------
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.
Treno00 said:
Thank you sooooo much, but I had little problem. So I will explain step by step what I have done.
1. Odin 3.10.6 + Stock Firmware KitKat 4.4.2
2. In options I leave checked F. Reset Time and Auto Reboot
3. After it's done, I stuck in boot logo so
4. Switch phone off and go to recovery mode
5. wipe data/factory reset and wipe cache partition
6. Reboot device and, yes. system is booted
7. Then after setting up I went to Settings>Security>Reactivation Lock (but I did use Mobile Data, don't know about WiFi)
8. DONE!
PS. You can upgrade your android via Kies from 4.4.2 to 5.0
Click to expand...
Click to collapse
uhm hey hi where did u dl your stock 4.4.2 rom? we have the same problem actually same cause too haha need help real bad
OK, in this folder you will find all possible stock firmware for [SM-G900F]
https://mega.nz/#F!i9dm2LKL!fzGY14qi4pYiEczNQy5KWA!uoFXBSDZ
Hi everyone !
I'm actually working in an IT centre (Don't know how to call that, or to traduce to you), and I just got a customer who handed me a Samsung SM-T580 tablet who is FRP locked... I've been searching since 3 days now, trying various methods, even trying a downgrade to other versions, but no luck. I've searched on XDA to see if anyone has got the same problem, but everyone has a different build number, as mine is T580XXU2AQA2. I've seen that if the 3 finals letters/number are PG1, I'm in luck, but if they're PL4, I'm unlucky. But what about QA2 ? And what about the FRP Lock on this build ?
Thanks for help, as I begin to lose hope...
TheHapist said:
Hi everyone !
I'm actually working in an IT centre (Don't know how to call that, or to traduce to you), and I just got a customer who handed me a Samsung SM-T580 tablet who is FRP locked... I've been searching since 3 days now, trying various methods, even trying a downgrade to other versions, but no luck. I've searched on XDA to see if anyone has got the same problem, but everyone has a different build number, as mine is T580XXU2AQA2. I've seen that if the 3 finals letters/number are PG1, I'm in luck, but if they're PL4, I'm unlucky. But what about QA2 ? And what about the FRP Lock on this build ?
Thanks for help, as I begin to lose hope...
Click to expand...
Click to collapse
Before attempting to flash ANY ROM on a T580, you have to enable "OEM unlock" in the /Setup/Developer options. If you don't, the way to unbrick the tablet is by using the Samsung Smart Switch app via a PC.
lewmur said:
Before attempting to flash ANY ROM on a T580, you have to enable "OEM unlock" in the /Setup/Developer options. If you don't, the way to unbrick the tablet is by using the Samsung Smart Switch app via a PC.
Click to expand...
Click to collapse
I can't do anything as I had the tablet already locked :/ I can just access the recovery and the download mode (As well as the normal boot, but it is pointless here).
I already flashed a stock ROM via Odin, and it worked fine as it was the same version in the tablet
TheHapist said:
I can't do anything as I had the tablet already locked :/ I can just access the recovery and the download mode (As well as the normal boot, but it is pointless here).
I already flashed a stock ROM via Odin, and it worked fine as it was the same version in the tablet
Click to expand...
Click to collapse
This one works with the latest build from PL4 to QC2 ( P= 2016, Q= 2017 ) , Android 6 ; not work with Android 7
https://www.youtube.com/watch?v=Xo9uJDDuSxw
Try it, if you can get the Assist then it will work as you can open Chrome to download Google Account Manager to add you own Google account and do the factory reset or just keep it as you are the owner now, taking full control of the tablet.
---------- Post added at 09:17 PM ---------- Previous post was at 09:04 PM ----------
lewmur said:
Before attempting to flash ANY ROM on a T580, you have to enable "OEM unlock" in the /Setup/Developer options. If you don't, the way to unbrick the tablet is by using the Samsung Smart Switch app via a PC.
Click to expand...
Click to collapse
If you can go to Setting and enable the OEM Unlock, you're not FRP lock and in owner account.
FRP ( Factory Reset Protection ) is a secured method from Google prevents anyone to continue in the settings without passing the verified account steps.
Without the previous synced account ID and password, it will keep you in a loop in the setting steps.
Beut said:
This one works with the latest build from PL4 to QC2 ( P= 2016, Q= 2017 ) , Android 6 ; not work with Android 7
https://www.youtube.com/watch?v=Xo9uJDDuSxw
Try it, if you can get the Assist then it will work as you can open Chrome to download Google Account Manager to add you own Google account and do the factory reset or just keep it as you are the owner now, taking full control of the tablet.
---------- Post added at 09:17 PM ---------- Previous post was at 09:04 PM ----------
If you can go to Setting and enable the OEM Unlock, you're not FRP lock and in owner account.
FRP ( Factory Reset Protection ) is a secured method from Google prevents anyone to continue in the settings without passing the verified account steps.
Without the previous synced account ID and password, it will keep you in a loop in the setting steps.
Click to expand...
Click to collapse
Obviously it is to late for the OP to change to "OEM enable" setting. I was merely pointing out the cause of the problem. But it also seemed apparent that the Google account settings are unknown.
I bought a tablet on eBay that had this problem and was able to get it working using Samsung Smart Switch run from a PC connected to the tablet in the download mode.
TheHapist said:
But what about QA2 ? And what about the FRP Lock on this build ?
Thanks for help, as I begin to lose hope...
Click to expand...
Click to collapse
The latest build QC2 from US can bypass easily by Google Account Manager app, I believe it will work with your build.
Beut said:
The latest build QC2 from US can bypass easily by Google Account Manager app, I believe it will work with your build.
Click to expand...
Click to collapse
Yep, it WORKED ! I'm really grateful, I was losing hope. Thank you so much !
The hapist how did you manage to bypass the frp on the tablet I am having the same problem I can’t get it to figure out please help me I have the t 580 Samsung Tab a 10.1 running Android 7.0
El sal said:
The hapist how did you manage to bypass the frp on the tablet I am having the same problem I can’t get it to figure out please help me I have the t 580 Samsung Tab a 10.1 running Android 7.0
Click to expand...
Click to collapse
Watch the youtube video posted by Beut in post #4
TheHapist said:
Hi everyone !
I'm actually working in an IT centre (Don't know how to call that, or to traduce to you), and I just got a customer who handed me a Samsung SM-T580 tablet who is FRP locked... I've been searching since 3 days now, trying various methods, even trying a downgrade to other versions, but no luck. I've searched on XDA to see if anyone has got the same problem, but everyone has a different build number, as mine is T580XXU2AQA2. I've seen that if the 3 finals letters/number are PG1, I'm in luck, but if they're PL4, I'm unlucky. But what about QA2 ? And what about the FRP Lock on this build ?
Thanks for help, as I begin to lose hope...
Click to expand...
Click to collapse
I have same problem QA2 & FRP lock SM-T580 but I have the original owners info but error message still says wait 24 hours?????
Ahlonnae said:
I have same problem QA2 & FRP lock SM-T580 but I have the original owners info but error message still says wait 24 hours?????
Click to expand...
Click to collapse
You see this message because you're still at first page of sign in. Reset it: Power + Volume Up + Home you should get to the Recovery and do a Factory Data Reset.
If you already have original owner information, you shouldn't have any problem of setting the tablet at the step of verifying google account.
I have done FRP bypass on the SM-T580 at least 10 tablets a day, so I can say FRP of Google is a joke. I have to deal with FRP lock everyday and I only need 10 minutes to bypass it.
[EDIT] Damned font I misread FRP for FAP
Posted elsewhere, but as I'm getting rather anxious and as I'm waiting for DBT-T580XXU2BQE4-20170525170357.zip to download... I ended up with a FAP lock. I can't find out if there's any difference from FRP lock - is there any?
Also, about Smart Switch, do the instructions from https://www.sammobile.com/forum/showthread.php?t=34745 apply? Smart Switch tells me that the device is unsupported and I don't get the Device Initialization tab!
Thanks!
[EDIT2] FW downloaded. Tried to use Odin, but there are four options: BL/AP/CP/CSC. Yet the FW package has these entries:
AP_T580XXU2BQE4_CL11316739_QB13491827_REV00_user_low_ship_meta.tar.md5
BL_T580XXU2BQE4_CL11316739_QB13491827_REV00_user_low_ship.tar.md5
CSC_OXA_T580OXA2BQE4_CL11316739_QB13491827_REV00_user_low_ship.tar.md5
HOME_CSC_OXA_T580OXA2BQE4_CL11316739_QB13491827_REV00_user_low_ship.tar.md5
So which one is CP?
You only need to load BL, AP, and CSC, ignore the HOME_CSC, but it seems you're flashing the Android 7 build from Germany which no method works.
You need to downgrade to Android 6, region doesn't matter for the purpose of bypass FRP. When it's done, flash back to your original region in Android 7.
Cellular South PL4 is the build you can downgrade and bypass FRP.
Beut said:
You only need to load BL, AP, and CSC, ignore the HOME_CSC, but it seems you're flashing the Android 7 build from Germany which no method works.
You need to downgrade to Android 6, region doesn't matter for the purpose of bypass FRP. When it's done, flash back to your original region in Android 7.
Cellular South PL4 is the build you can downgrade and bypass FRP.
Click to expand...
Click to collapse
First of all, thank you for your reply indeed.
Yes, I guess it was from Germany since German was its language when it first booted and it was 7.0.
So I'm downloading XAR-T580UEU2APL4-20170407113933.zip (Cellular South PL4) and flashing it with Odin, but once it's done, how do I flash 7 again? Use Odin with the initial BL/AP/CSC that I got?
Again, thank you!
[EDIT] Oh yeah, 6.0 flashed successfully and I'm off FRP lock!!!! Thanks so much... Now I guess I turn on OEM enable in Dev options and flash BL/AP/CSC in Odin?
No need to flash back if you want to keep current US build if it has your prefer language.
However, it's now US tablet, it only update the latest one from US build.
No need to turn on OEM unlock if you know your own Google ID and password.
If you like, flash the Europe build as it has more languages than US one, the same way as you downgrade firmware: load BL, AP, and CSC to Odin.
You're right. I was asking because I thought I'd have lost OTA, which was not the case - device updated OTA to 7.0 so I then proceeded and rooted it again. *Now* OTA is dead, but I'm good.
I was thinking, probably, than on Samsung devices tripping Knox would disable OTA.
Thanks for your reply once more
Tripping Knox doesn’t disable OTA but if the status of firmware is Custom, you won’t be able to update software. I have some tablets which have Knox count more than 1, they update normally because I run stock firmware
Beut said:
Tripping Knox doesn’t disable OTA but if the status of firmware is Custom, you won’t be able to update software. I have some tablets which have Knox count more than 1, they update normally because I run stock firmware
Click to expand...
Click to collapse
Yup! I'm learning by doing
I guess that having an official FW but custom recovery equals to Custom, correct? Which means if I reflash original OTA will be back?
In the setting, About Tablet, Status, if the device status is Official, you have no problem of update via OTA.
Or in Download Mode, if the System Status is Official. I believe your system is Custom if having custom recovery.
Rooted device will become Official if you flash back the stock firmware , however the Knox counting is not rolling back to zero.
Yup, I did know about Knox (that would defeat the purpose, right? ).
If I'm not mistaken flashing original FW will erase data, no? So I'll save it for when there's a decent Oreo ROM out there. Then again, it won't be Original even then so I guess I'm off that road, but I don't think Samsung will be releasing any new OTAs any time soon so there's no meaning in it, surely?