I just got this phone today, and I want to root it and use custom ROM, but having troubles. Previously did this on an S6 and it was fairly easy.
Was following one guide, and was getting Fail Auth error from Odin.
Now trying to follow this guide:
https://forum.xda-developers.com/galaxy-s8/how-to/guide-how-to-install-twrp-root-galaxy-t3752480
But I don't even have OEM unlock in Developer options....
I'm still running 8.0 android. But an update is available, should I update to 9.0?
Please help
Edit:
In an effort to find a way to get the OEM unlock , i found this:
https://www.the***********.com/fix-missing-oem-unlock-toggle-samsung-galaxy-devices/
"The method below has stopped working on the newer firmware released in or after August 2018. In most situations, your device will be forcibly locked and the OEM Unlock toggle will be missing. Ensure that you insert a SIM card, connect to your network, and NOT REBOOT your Galaxy device for straight 7 Days (168 Hours)."
Is this accurate? Would it have to be a sim that's currently network activated if so? I was thinking of continuing to use the active sim in the s6, and an old sim in the s8 until I have it all set up. Also, if I have to wait a week, I probably might as well update to 9.0 that samsung is providing.
Thoughts? Suggestions?
ukie.int said:
I just got this phone today, and I want to root it and use custom ROM, but having troubles. Previously did this on an S6 and it was fairly easy.
Was following one guide, and was getting Fail Auth error from Odin.
Now trying to follow this guide:
https://forum.xda-developers.com/galaxy-s8/how-to/guide-how-to-install-twrp-root-galaxy-t3752480
But I don't even have OEM unlock in Developer options....
I'm still running 8.0 android. But an update is available, should I update to 9.0?
Please help
Edit:
In an effort to find a way to get the OEM unlock , i found this:
https://www.the***********.com/fix-missing-oem-unlock-toggle-samsung-galaxy-devices/
"The method below has stopped working on the newer firmware released in or after August 2018. In most situations, your device will be forcibly locked and the OEM Unlock toggle will be missing. Ensure that you insert a SIM card, connect to your network, and NOT REBOOT your Galaxy device for straight 7 Days (168 Hours)."
Is this accurate? Would it have to be a sim that's currently network activated if so? I was thinking of continuing to use the active sim in the s6, and an old sim in the s8 until I have it all set up. Also, if I have to wait a week, I probably might as well update to 9.0 that samsung is providing.
Thoughts? Suggestions?
Click to expand...
Click to collapse
You will need OEM unlocked in developer menu to flash twrp etc. As for getting unlocked you can try different variations of the date method. I have 2 S8's one Oreo one pie both with twlrp, etc got OEM by using a variation of the date method. If not you will have to wait.
As to updating to pie well personal choice my daily driver is still on Oreo while my other phone is on pie.
As to the method the thread you quoted is still valid but a bit outdated as it doesn't take into account of rrm state ( and kg state introduced in pie ). This guide is more up to date but is basically the same procedure but includes RMM fix.
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
Also be aware the have been updates to twrp as well.
Yea, I've been trying various date methods, but none of them worked for me. The lack of OEM is likely the issue here, so I'll probably just have to wait for a week to proceed
Hey i have samsung galaxy tab s5e lte (sm-t727v) it is unlocked verizon tab i want to flash samsung stock firmware to remove varizon boatload & pre-installed apps & also some features like call & message continuity are blocked by verizon. So can you please suggest which firmware stall i flash & how. I’ve tried flsahing sm-t727 & sm-t725 via odin but it gives error (secure check fail : Pit)
Im curious about tthis myself, but ive kind of resignes myself to the fact im probably goong to have to get an s6 directly from samsung that allows the option to unlock the bootloadr out of the box. There is a new "security update" from verizon though, im curious about what it actually patches before I update.
Sorry for the double post, but I need information by those much more experienced.
So thanks to the 3D patched Odin, my T727V is now a T727U. So basically It's like I bought the thing from Samsung with no carrier bloat and all the nice little things like calling and texting through the phone that Verizon blocks and things like that. Things is I still have no OEM unlock in the dev options, so now I have a few options. Apparently the remote OEM Unlock enable in Pie is CSC based? So obviously the csc is still registered as a VZW, so does that immediately kill the chances and thus it would be a waste of time to wait for the RMM lock (which I'm pretty sure I would have triggered), right?
Also, even though transforming the tablet into a fully featured unbranded is really nice, I still would love custom firmware, and I'm at a catch-22. If OEM Unlock is governed by the csc or imei and not the firmware, I really have no way to change either without root, which I can't accomplish without custom recovery, which of course I need OEM unlock. A question and a tidbit though, question being why I can flash between carriers and unbranded, but I cannot flash to say the Turkish T727 firmware. The interesting tidbit being in the recovery logs for the T727U firmware flash I did, one of the build.prop properties that was set at flash by the firmware is "ro.oem_unlock_supported = 1" This does NOT appear when flashing the Verizon firmware.
Edit: Welp. To any other Verizon S5e owners, flash the T727R4 US cellular firmware. OEM Unlock toggle available immediately.
purplerose1414 said:
Sorry for the double post, but I need information by those much more experienced.
So thanks to the 3D patched Odin, my T727V is now a T727U. So basically It's like I bought the thing from Samsung with no carrier bloat and all the nice little things like calling and texting through the phone that Verizon blocks and things like that. Things is I still have no OEM unlock in the dev options, so now I have a few options. Apparently the remote OEM Unlock enable in Pie is CSC based? So obviously the csc is still registered as a VZW, so does that immediately kill the chances and thus it would be a waste of time to wait for the RMM lock (which I'm pretty sure I would have triggered), right?
Also, even though transforming the tablet into a fully featured unbranded is really nice, I still would love custom firmware, and I'm at a catch-22. If OEM Unlock is governed by the csc or imei and not the firmware, I really have no way to change either without root, which I can't accomplish without custom recovery, which of course I need OEM unlock. A question and a tidbit though, question being why I can flash between carriers and unbranded, but I cannot flash to say the Turkish T727 firmware. The interesting tidbit being in the recovery logs for the T727U firmware flash I did, one of the build.prop properties that was set at flash by the firmware is "ro.oem_unlock_supported = 1" This does NOT appear when flashing the Verizon firmware.
Edit: Welp. To any other Verizon S5e owners, flash the T727R4 US cellular firmware. OEM Unlock toggle available immediately.
Click to expand...
Click to collapse
Where did you find the T727R4 firmware?
Ryche666 said:
Where did you find the T727R4 firmware?
Click to expand...
Click to collapse
Frija! Use CSC code USC on auto mode, boom. Now it's US cellular, which did not like my Verizon sim card at all, so here's a really short summary and links to much better help to do all this (knowing all risks and pitfalls etc.) and end up rooted and your Verizon sim still functioning.
Few things, one this was written up with a Verizon s5e in mind, I don't know if the PITs are different for the other carriers, so this one operates with Verizon's in mind. Two, you MUST have a patched Odin. Also standard advice of backing up everything before hand, and finally, I was dumb and had my SIM card in during the whole process. I'm not sure it had any ill effect but if you want to be super safe, go ahead and keep it out until you're on T727U firmware.
Pre-note: I have no clue if you can substitute t727v for t727u in the following write up. I wanted all traces of Verizon out of my tablet when I was figuring how to enable the Bootloader unlock. We're using the R4 BL files for the whole process so it may or may not effect anything as far as that goes.
1. Do a standard flash of the R4 official Samsung firmware. (You might have to use the us cellular pit for this flash. If so remember to use either the U or V pit for step 3.)
2. Follow AHE_XDA's fantastic guide, right now only the parts about unlocking the bootloader.
3.Once that's done, flash The AP of T727U firmware, with the cp and csc ofT727V Note: Not the BL. We do not flash anything to the BL after the R4 firmware in step 1.
Addendum: Use the Verizon pit (usa_open) when flashing to t727U the first time if you get a "could not open file on line ****" error from odin.
4: Follow the rest of AHE_XDA's guide on rooting and there you go!
purplerose1414 said:
Frija! Use CSC code USC on auto mode, boom. Now it's US cellular, which did not like my Verizon sim card at all, so here's a really short summary and links to much better help to do all this (knowing all risks and pitfalls etc.) and end up rooted and your Verizon sim still functioning.
Few things, one this was written up with a Verizon s5e in mind, I don't know if the PITs are different for the other carriers, so this one operates with Verizon's in mind. Two, you MUST have a patched Odin. Also standard advice of backing up everything before hand, and finally, I was dumb and had my SIM card in during the whole process. I'm not sure it had any ill effect but if you want to be super safe, go ahead and keep it out until you're on T727U firmware.
Pre-note: I have no clue if you can substitute t727v for t727u in the following write up. I wanted all traces of Verizon out of my tablet when I was figuring how to enable the Bootloader unlock. We're using the R4 BL files for the whole process so it may or may not effect anything as far as that goes.
1. Do a standard flash of the R4 official Samsung firmware. (You might have to use the us cellular pit for this flash. If so remember to use either the U or V pit for step 3.)
2. Follow AHE_XDA's fantastic guide, right now only the parts about unlocking the bootloader.
3.Once that's done, flash The AP of T727U firmware, with the cp and csc ofT727V Note: Not the BL. We do not flash anything to the BL after the R4 firmware in step 1.
Addendum: Use the Verizon pit (usa_open) when flashing to t727U the first time if you get a "could not open file on line ****" error from odin.
4: Follow the rest of AHE_XDA's guide on rooting and there you go!
Click to expand...
Click to collapse
anyone else have success with this? ive followed everything so far but i'm stuck trying to unlock bootloader. the option is there in developer options i can turn it on or off in there but when i power down and boot into download mode the option to unlock bootloader isnt there and it says OEM Lock On (u1)
I hate that, that was the part that was no hassle for me so I dont know where to begin...I used the December R4 us cellular firmware, if that helps at all. The same thing that unlocks the toggle should have given the long press up option in download mode. You started with a US T727 Verizon model, right? Now I had changed it to t727U first, maybe that had something to do with it?
purplerose1414 said:
I hate that, that was the part that was no hassle for me so I dont know where to begin...I used the December R4 us cellular firmware, if that helps at all. The same thing that unlocks the toggle should have given the long press up option in download mode. You started with a US T727 Verizon model, right? Now I had changed it to t727U first, maybe that had something to do with it?
Click to expand...
Click to collapse
It was cuz i was on a newer fw version for R4 (feb4) i downgraded to the Dec one and i now i have my bootloader unlocked (shows in dev settings, get notification at boot, and says oem lock off in download mode) but i keep getting a error about "only being able to flash official firmware versions (vbmeta)" . turns out this is from my KG Status being PRENORMAL instead of Checking. you can check this in download mode as well. did you have any issues with that or kknow what i'm talking about? there are guides that say to do things like roll the date back on your phone manually then check for updates but it doesnt work
---------- Post added at 05:02 PM ---------- Previous post was at 04:56 PM ----------
purplerose1414 said:
I hate that, that was the part that was no hassle for me so I dont know where to begin...I used the December R4 us cellular firmware, if that helps at all. The same thing that unlocks the toggle should have given the long press up option in download mode. You started with a US T727 Verizon model, right? Now I had changed it to t727U first, maybe that had something to do with it?
Click to expand...
Click to collapse
also i'm a little confisued about the end of your directions. I am not a Verizon Subscriber i bought this 2nd hand for a deal i am on TMO (not planning on really using data on thin atm but still) Am i correct in thinking after you flashed R4 BL AP CP and CSC, then booted into the R4 firmware and went through initial setup, then reboot to recovery to unlock bootloader and then flashed the t727u AP, left the R4 bootloader, and flasshed VZW CP and CSC? i cant seem to get mine to boot if i do that i get hash check errors when it tries to boot and spits me out into download mode. if this is the case do you remember or can you check the exact versions of CP, AP, and CSC you flashed? right now what i did was flash all R4 tars to go from 727v to 727r4, went though setup and verified i have oem unlock option in dev options then rebooted to download mode and unlocked bootloader THEN i FLASHED 727u versions of AP CP and CSC since my error with the vzw ones i mentioned earlier. Last question. should i be putting my sim in? i notice when i flash the U firmware i get a message about carrier settings update and it makes it reboot
thanks for replying btw
purplerose1414 said:
I hate that, that was the part that was no hassle for me so I dont know where to begin...I used the December R4 us cellular firmware, if that helps at all. The same thing that unlocks the toggle should have given the long press up option in download mode. You started with a US T727 Verizon model, right? Now I had changed it to t727U first, maybe that had something to do with it?
Click to expand...
Click to collapse
could you check something for me real quick? could you boot to download mode and look for "KG STATUS" and tell me what it says. i think my issue is somewhere in the processs of flashing the different firmwares KG gets set to "PRENORMAL" which acts kind of like a secondary bl lock. if i restore to the oldest vzw firmware i could find (june24) it puts it back to "CHECKING" which is good but i loose bootloader unlock in the process obviously thus the catch 22.
albinoman887 said:
could you check something for me real quick? could you boot to download mode and look for "KG STATUS" and tell me what it says. i think my issue is somewhere in the processs of flashing the different firmwares KG gets set to "PRENORMAL" which acts kind of like a secondary bl lock. if i restore to the oldest vzw firmware i could find (june24) it puts it back to "CHECKING" which is good but i loose bootloader unlock in the process obviously thus the catch 22.
Click to expand...
Click to collapse
See, as soon as I switched from T727V to T727U I stopped even seeing kg status in download mode. In my original post in this thread I thought that meant I had tripped it. I really have no clue why just switching to unbranded firmware would make that difference either. I just lucked out on the magic cocktail to unlock Verizons bootloder, I was kind of hoping it would be easy peasy for others. Like, my poor tablet went through odin every day for a straight month.
E: Just saw your edit in your post. I'll have exact firmwares I used asap. In the meantime, my hotspot worked just fine on the unbranded CP and CSC, maybe try that?
ok let me know ill be up a few more hrs
---------- Post added March 10th, 2020 at 12:19 AM ---------- Previous post was March 9th, 2020 at 11:55 PM ----------
you didnt happen to do anything outlined in this thread did you?
https://forum.xda-developers.com/tab-s5e/how-to/samsung-galaxy-tab-s5e-debloat-root-info-t3935010
i wonder if you disabled a Knox apk at the right time to make KG status go away
I'm really scared of bricking my LTE AT&T tablet if I flash the only firmware I was able to grab.
Any way to find the specific stock firmware for my sm-t727A? I've tried Frija, and went all over google to no avail; I can only find other stock firmware.
If I just want to switch to sm-t727u firmware from sm-t727v firmware without rooting do I need to go through the extra step of flashing the us cellular version first?
purplerose1414 said:
Frija! Use CSC code USC on auto mode, boom. Now it's US cellular, which did not like my Verizon sim card at all, so here's a really short summary and links to much better help to do all this (knowing all risks and pitfalls etc.) and end up rooted and your Verizon sim still functioning.
Few things, one this was written up with a Verizon s5e in mind, I don't know if the PITs are different for the other carriers, so this one operates with Verizon's in mind. Two, you MUST have a patched Odin. Also standard advice of backing up everything before hand, and finally, I was dumb and had my SIM card in during the whole process. I'm not sure it had any ill effect but if you want to be super safe, go ahead and keep it out until you're on T727U firmware.
Pre-note: I have no clue if you can substitute t727v for t727u in the following write up. I wanted all traces of Verizon out of my tablet when I was figuring how to enable the Bootloader unlock. We're using the R4 BL files for the whole process so it may or may not effect anything as far as that goes.
1. Do a standard flash of the R4 official Samsung firmware. (You might have to use the us cellular pit for this flash. If so remember to use either the U or V pit for step 3.)
2. Follow AHE_XDA's fantastic guide, right now only the parts about unlocking the bootloader.
3.Once that's done, flash The AP of T727U firmware, with the cp and csc ofT727V Note: Not the BL. We do not flash anything to the BL after the R4 firmware in step 1.
Addendum: Use the Verizon pit (usa_open) when flashing to t727U the first time if you get a "could not open file on line ****" error from odin.
4: Follow the rest of AHE_XDA's guide on rooting and there you go!
Click to expand...
Click to collapse
I get to the unlock the bootloader part but then when I go back in and try to flash the U software according to your instructions, it doesn't work. Could it be that the software has been updated since the instructions were written and it won't work now?
I have tried every version of Patched Odin and followed these directions to a T. I even went back and tried other things and can't get this to work. If someone can help me get the U software to flash on my SM-T727V, I got $20 I'll Venmo or Zelle you.
purplerose1414 said:
Frija! Use CSC code USC on auto mode, boom. Now it's US cellular, which did not like my Verizon sim card at all, so here's a really short summary and links to much better help to do all this (knowing all risks and pitfalls etc.) and end up rooted and your Verizon sim still functioning.
Few things, one this was written up with a Verizon s5e in mind, I don't know if the PITs are different for the other carriers, so this one operates with Verizon's in mind. Two, you MUST have a patched Odin. Also standard advice of backing up everything before hand, and finally, I was dumb and had my SIM card in during the whole process. I'm not sure it had any ill effect but if you want to be super safe, go ahead and keep it out until you're on T727U firmware.
Pre-note: I have no clue if you can substitute t727v for t727u in the following write up. I wanted all traces of Verizon out of my tablet when I was figuring how to enable the Bootloader unlock. We're using the R4 BL files for the whole process so it may or may not effect anything as far as that goes.
1. Do a standard flash of the R4 official Samsung firmware. (You might have to use the us cellular pit for this flash. If so remember to use either the U or V pit for step 3.)
2. Follow AHE_XDA's fantastic guide, right now only the parts about unlocking the bootloader.
3.Once that's done, flash The AP of T727U firmware, with the cp and csc ofT727V Note: Not the BL. We do not flash anything to the BL after the R4 firmware in step 1.
Addendum: Use the Verizon pit (usa_open) when flashing to t727U the first time if you get a "could not open file on line ****" error from odin.
4: Follow the rest of AHE_XDA's guide on rooting and there you go!
Click to expand...
Click to collapse
I am trying to copy your process with a Tab A 2019 unlocked, but Sprint variant with no success so far. I have bricked it a lot, but it doesn't seem to want an unlocked firmware for the same model . I haven't tried flashing it's bootloader though, out of fear of bricking it ( I have unlocked its bootloader already).
Hey guys, just found the thread. Anyone know if an unlocked SM-T727A can be OEM unlocked? I mean the bootloader. The option is always missing no matter how many time I try according to the tutorials, which makes me doubt if a branded S5e doesn't even have this capabililty. Perhaps that's why I am here seeking a chance to flash it to an SM-T727U. Thanks for anyone who replies.
Ok so after three months I turned my mind back to this topic again. And yes, I struggled for a couple of hours overnight last night and got the ATT T727A flashed with Lineage. There are a few tricks: First, the USC R4 firmware can be flashed, with the modified version (3B) of Odin, which bypasses the SHA256 error check; Second, when the USC R4 firmware (latest for now is Mar 2021 version, Android 10) is flashed, the start logo changes from slick ATT to full screen big fat US Cellular. Need to wait for a few minutes and let it do its work. Through this flash, user data will not be lost. Third, the USC R4 version does have OEM Unlock automatically present and all it needs is to flip the switch, then go to download mode to unlock the bootloader. This will erase the user data. Fourth, from then on it's all standard procedures to flash any third party roms like LineageOS with MicroG pursuant to their instructions. Four hours work made a good result, and the cellular data is usable without problem.
PS: the concept of timed OEM unlock switch (a week after factory reset) is wrong. It's non-existent so do not waste time on it. Just straigntly flash the USC R4 Version. To flash other roms like Lineage, it would be better to download the Odin with their specified version to prevent hiccups.
Wieczorkiewicz said:
Ok so after three months I turned my mind back to this topic again. And yes, I struggled for a couple of hours overnight last night and got the ATT T727A flashed with Lineage. There are a few tricks: First, the USC R4 firmware can be flashed, with the modified version (3B) of Odin, which bypasses the SHA256 error check; Second, when the USC R4 firmware (latest for now is Mar 2021 version, Android 10) is flashed, the start logo changes from slick ATT to full screen big fat US Cellular. Need to wait for a few minutes and let it do its work. Through this flash, user data will not be lost. Third, the USC R4 version does have OEM Unlock automatically present and all it needs is to flip the switch, then go to download mode to unlock the bootloader. This will erase the user data. Fourth, from then on it's all standard procedures to flash any third party roms like LineageOS with MicroG pursuant to their instructions. Four hours work made a good result, and the cellular data is usable without problem.
PS: the concept of timed OEM unlock switch (a week after factory reset) is wrong. It's non-existent so do not waste time on it. Just straigntly flash the USC R4 Version. To flash other roms like Lineage, it would be better to download the Odin with their specified version to prevent hiccups.
Click to expand...
Click to collapse
Help me ola if u r there. I have same t727a of att live outside The US. I just want to skip Att block and use SMS app, so flash Usc t727r4 via Odin patched is enough for me? And if i want update from android 9 to 10 i just do same thing with Q firmware?
i try flash USC T727R4 on ATT T727A success for first time, but Massage app still require link other SamSung phone to use. I have full funtion simcard inserted but Google massage app cant recognize too.
Btw, convert to USC is good, no ATT bloatware and now have OTA outsite The US.
Hello everyone. I'm just getting my new device situated and, knowing that unlocking the bootloader often requires a factory reset, I thought to make that one of my first tasks with my T-Mobile McLaren 5G. I was able to successfully activate the Developer menu but when I went there, I found that the OEM Unlock setting was not only off, but greyed out and unable to be enabled! If I'm correct, enabling OEM Unlocking in the Dev menu is the first step to unlocking the bootloader, before connecting via ADB or using some sort of toolkit.
I called T-Mobile to ensure this was not their doing and according to their rep (after getting transferred from CS, to a tech, to a senior tech) apparently this is not something they have control over ; they can unlock the phone to use other SIMs but don't have anything to do with the bootloader, the ROMs etc. They suggested contacting OnePlus and gave me an 800 number, but I thought I'd check with the community first just in case.
Should this OEM Unlocking option be capable of being enabled? Is there a way to unlock the bootloader without this step? I'm a bit out of date on the current state of unlocking / custom ROMs and the like - is there any sort of open source GUI (or for that matter, CLI) based toolkit for easily flashing/unlocking bootloader and other tasks? There used to be some tools available for older Nexus, Pixel, and OnePlus devices a few years back but the older ones I recall don't seem to be updated since then. If not and it all needs to be done manually, do we still use the Android SDK Platform Tools (I assume you don't need the whole Android Studio or even Android Studio CLI)?
Regarding T-Mobile, there seems to be some discussion about certain OnePlus devices requiring a code from OnePlus itself via ( https://www.oneplus.com/unlock_token ) in order to unlock the bootloader? I don't remember it being this much trouble with past earlier devices (including Nexus and OnePlus)! Is this step required or is there a workaround? Regardless, even that page describes being able to toggle the OEM Unlocking setting before anything else, so something seems to be of concern. Ideas? Thanks!
The device sim unlock for the OnePlus 7T Pro 5G McLaren is hidden in Settings-->SIM & network-->ADVANCED Network Unlock; it doesn't have a separate magenta colored unlock app icon like some older T-Mobile phones do. But, the rest should be similar to the T-Mobile OnePlus 7 Pro process https://www.xda-developers.com/unlock-bootloader-root-oneplus-7-pro/
After the permanent device sim unlock is completed, the OEM unlocking option should no longer be greyed out.