I bought a new LTE Galaxy Tab a few days ago (Hong Kong region) and after a couple of days days of using it, the S-Pen and screen started becoming completely unresponsive. I had configured some basic things on the Tablet, activated Developer Options and installed some apps, but I didn't have tine to get TWRP or root before it broke down. After taking it to Samsung and getting it back repaired 2 days later, they told me they had to replace the whole screen and also the pen. Somehow I had the feeling they simply gave me a new unit. Fine to me..
So today, getting myself ready to install TWRP and rooting it, to my disbelief, the OEM UNLOCKING option in Developer Options is gone! It was absolutely there before I took it to Samsung for repair. This means what? Did they exchange my original purchased tablet with one that actually has a locked bootloader? Or can I still install TWRP and root as before, or what exactly is this? Im pretty upset and confused.
Thanks a lot in advance for any insight on this
If it's the LTE version, it would have an IMEI number, no? Check the IMEI on the Tab with the one on the box, (assuming you didn't also give them the box) it will tell you if they've switched them.
I could be wrong, so you may want to wait for further confirmation, but if OEM unlock is not present, it should mean the bootloader is unlocked by default. Try flashing TWRP with Odin, if the bootloader is locked, it will just fail. Again, I'm no expert, just speaking from my experience, when I first flashed TWRP to my Tab S6, I forgot to unlock the bootloader, flash just failed with no negative effect.
bartleby999 said:
If it's the LTE version, it would have an IMEI number, no? Check the IMEI on the Tab with the one on the box, (assuming you didn't also give them the box) it will tell you if they've switched them.
I could be wrong, so you may want to wait for further confirmation, but if OEM unlock is not present, it should mean the bootloader is unlocked by default. Try flashing TWRP with Odin, if the bootloader is locked, it will just fail. Again, I'm no expert, just speaking from my experience, when I first flashed TWRP to my Tab S6, I forgot to unlock the bootloader, flash just failed with no negative effect.
Click to expand...
Click to collapse
Thanks for the reply. I try flashing it and failed. And I did give them box.. my bad I guess and of court I didn't write down the IMEI number somewhere before I handed them the package. How could I have known? I am almost sure they have me a whole new system even because the USB charging cable was wrapped again like when I first unboxed it. It looked 100% a new unit in the box, minus the detail safety seals that were already broken is there repair clerk handed me the new tablet. Plus, it they had simply swapped the stylist and replaced the screen, I would not see a reason for them to have completely reset the unit to the point of the default language being again Chinese instead of English (as all TGY variants are here by default) along with all the apps that I had installed, all of which were gone as well. there's positively no need to completely wipe out and reset the unit simply because they replaced the screen. Plus, locally thinking, being just a couple days old, I'm sure they didn't want to bother for possibly a long time repair turnaround for me and gave me a new one.
That the OEM UNLOCK toggle was there originally is a given because I was just about getting ready to Flash recovery and root it and had specially gone into Developer Options and toggled it along with the USB Debugging Switch. All Samsung phones and tablets in this region have unlocked bootloaders by the default. This is one of the reasons I keep coming back to Samsung because with other brands you either can't do it or it's a nightmare to get it done. Of course, good thing I did not Flashed recovery and root before the Tablet crapped on me because of course I would have voided the warranty. Also, now it's not like I can go back to Samsung and complain about the OEM UNLOCK issue because obviously no one is supposed to be rooting the devices or asking for help on the matter.
I'll do some more research on this and if I can unlock it.. hopefully. If not I will sell it and buy another one retail again. I'm super bummed.
Thanks again for the reply.
Related
I guess the title says it all but a little info, a couple of months ago I went on to settings and ticked on the OEM unlock option but never went forward with any flashing, no custom recovery, no kernel, nothing, plain stock Samsung ROM. 3 days ago I went to pick up some newspapers for work and everything was fine, at lunch time I had to get something and upon swiping the phone on the terminal it came up with a message on my phone that this device cannot be used to pay in stores with google pay. I deleted and updated my card info since I lost it recently and the new had a different expiration date. Which I had already changed but figured it might have taken a few days to flag or something. Same result, can't pay in stores message. Got in contact with google pay support and they told me my phone had been flagged for being rooted,modified OS. I said that I'm not rooted then they said it appears I have an unlocked bootloader so google pay doesn't work on devices with unlocked bootloaders. I stated that an unlocked bootloader is perfectly legal and not a sign of a modified OS. The operator replied they can't do anything since it's policy and my only option is to relock the bootloader, so I told them it'd work if I had a modified OS but it wont if I have an unlocked bootloader with no modifications to cover the BL state and I laughed, said thank you and signed off from the support conversation.
I went back an relocked the OEM option and restarted for it to take effect and was then able to use gpay again.
I have a XEU Exynos with the April Security update.
TLR if you OEM unlock but don't flash magisk and magisk hide your google pay wont work. Relock,reboot and you're good to go.
crossmission said:
I guess the title says it all but a little info, a couple of months ago I went on to settings and ticked on the OEM unlock option but never went forward with any flashing, no custom recovery, no kernel, nothing, plain stock Samsung ROM. 3 days ago I went to pick up some newspapers for work and everything was fine, at lunch time I had to get something and upon swiping the phone on the terminal it came up with a message on my phone that this device cannot be used to pay in stores with google pay. I deleted and updated my card info since I lost it recently and the new had a different expiration date. Which I had already changed but figured it might have taken a few days to flag or something. Same result, can't pay in stores message. Got in contact with google pay support and they told me my phone had been flagged for being rooted,modified OS. I said that I'm not rooted then they said it appears I have an unlocked bootloader so google pay doesn't work on devices with unlocked bootloaders. I stated that an unlocked bootloader is perfectly legal and not a sign of a modified OS. The operator replied they can't do anything since it's policy and my only option is to relock the bootloader, so I told them it'd work if I had a modified OS but it wont if I have an unlocked bootloader with no modifications to cover the BL state and I laughed, said thank you and signed off from the support conversation.
I went back an relocked the OEM option and restarted for it to take effect and was then able to use gpay again.
I have a XEU Exynos with the April Security update.
TLR if you OEM unlock but don't flash magisk and magisk hide your google pay wont work. Relock,reboot and you're good to go.
Click to expand...
Click to collapse
This was changed a while ago, a unlocked bootloader will trip safety net, if you have no reason for the OEM unlock, don't use it
Ferbee said:
This was changed a while ago, a unlocked bootloader will trip safety net, if you have no reason for the OEM unlock, don't use it
Click to expand...
Click to collapse
Yes, I forgot to mention it triggers the CTS Profile to mismatch and thus fail the Safety Net status check even if the Safety Net Request flag itself isn't raised.
I honestly think they're just trying to cover their asses by removing functionality even though I fail to grasp that they are not aware that the people who are technically minded enough to root, and try to use the service with malicious intent, know how to bypass Safety Net checks. On the other hand it might be that if someone has an unlocked bootloader is more susceptible to remote attacks and potentially have a random apk root and take hold of their device and all their info.
It's been a long couple of days at work and while typing the original post I forgot half of what I wanted to mention hehehe!!!
I have an unlocked SM-G965F/DS (Exynos) that has not shown the OEM unlock option yet. Tried:
Installing active SIM
Logging in to Google and Samsung accounts, then
Leaving the phone online for 170 hours (uptime reached ~175 hours)
I see a few other threads on the SM-G965F/DS, also indicating no OEM unlock appeared. Has anyone actually gotten the SM-G965F/DS to show an OEM unlock option?
Firmware and hardware versions:
Hardware: SM-G965FZBDXSP
CSC code: XSP
Botloader: G965FXXU1BRE6
CSC: G965FOXM1BRE6
Android Build Number: R16NW.G965FXXU1BRE6
EDIT:
Bootloader shows:
Model: G965F
RMM State: Prenormal
FRP Lock: ON
OEM Lock: ON
Is only the single-SIM 965F unlockable? Is there a recommended dual-SIM model in case I end up just sending this one back?
Appreciate any help you guys can provide!
whitepines said:
Is only the single-SIM 965F unlockable? Is there a recommended dual-SIM model in case I end up just sending this one back?
Appreciate any help you guys can provide!
Click to expand...
Click to collapse
Mines dual sim, had oem unlock after the 7 day wait.
sent from my Exynos S9 plus, Pixel 2 XL or Note FE
force70 said:
Mines dual sim, had oem unlock after the 7 day wait.
sent from my Exynos S9 plus, Pixel 2 XL or Note FE
Click to expand...
Click to collapse
Great, thank you for the data point. Do you happen to know the CSC and stock firmware version you had installed when the OEM unlock appeared? If I don't see the option after another 7 days I intend to ODIN over a known good CSC / firmware version.
whitepines said:
Great, thank you for the data point. Do you happen to know the CSC and stock firmware version you had installed when the OEM unlock appeared? If I don't see the option after another 7 days I intend to ODIN over a known good CSC / firmware version.
Click to expand...
Click to collapse
My CSC is EGY (egypt) but no idea what the original firmware was when i got it
Mine is a S9+ dual sim and has OEM unlock
Vadwiser said:
Mine is a S9+ dual sim and has OEM unlock
Click to expand...
Click to collapse
do i need to have an active sim card in my phone to oem unlock? feeling like i wasted the last 3 days by not having one inserted. thanks in advance
this.guy.lol said:
do i need to have an active sim card in my phone to oem unlock? feeling like i wasted the last 3 days by not having one inserted. thanks in advance
Click to expand...
Click to collapse
Lol, why wouldnt you have one inserted?
sent from my Exynos S9 plus, Pixel 2 XL or Note FE
force70 said:
Lol, why wouldnt you have one inserted?
sent from my Exynos S9 plus, Pixel 2 XL or Note FE
Click to expand...
Click to collapse
because i have a oneplus 6 i am using. and because i require root. i dont use devices that are not rooted.
Did finally get it working. My device originally came with RMM prenormal, FRP lock off, OEM lock on. Setting up the phone normally and inserting a SIM, then waiting 7 days, did NOT work. I suspect the phone was in an abnormal state due to a partial setup by the prior owner / reseller.
What did the trick for me was to force reset the phone (lose all data) via the settings menu, have a SIM inserted, go through the full setup process (Google and Samsung accounts), then leave the phone on for 7 days. The reset caused RMM prenormal, FRP lock on, OEM lock on. After 168 hours the OEM unlock option appeared in the developer settings menu.
A little guidance here. I've only dealt with Google Nexus devices and the OnePlus One, which were ridiculously easy to unlock and put on a custom ROM. I'm currently running (yes, still) a Nexus 6P because there hasn't been a phone that really interests me. I do like the S9+, and can get a good price on a BNIB SM-G965F/DS. I just want to run AOSP on it, no frills, no thrills, just vanilla. That's how I roll. So, I'll need to unlock the bootloader, install TWRP, and load up a new ROM.
With that said, all that I've read, I'm a little confused. I use t-mobile, so will I need to put in the t-mobile sim for 7 days to get OEM unlock, or will I need this done in an EU country (it is an EU version) due to the region locking Samsung has been doing since 2013? There just seems to be a lot of competing and incomplete information all over the damned place.
And don't tell me to search, please. I've been around on this forum long enough to know how to search, and long enough to know that search doesn't always yield the results you're looking for. So, if you have a link to a more descriptive explanation of what to do/expect, I'd be grateful.
Thanks.
EDIT: Found this: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
Maybe that would work... but still don't understand if I need it activated on an EU SIM first.. Now I remember why I've avoided Samsung devices...
stewa2jm said:
A little guidance here. I've only dealt with Google Nexus devices and the OnePlus One, which were ridiculously easy to unlock and put on a custom ROM. I'm currently running (yes, still) a Nexus 6P because there hasn't been a phone that really interests me. I do like the S9+, and can get a good price on a BNIB SM-G965F/DS. I just want to run AOSP on it, no frills, no thrills, just vanilla. That's how I roll. So, I'll need to unlock the bootloader, install TWRP, and load up a new ROM.
With that said, all that I've read, I'm a little confused. I use t-mobile, so will I need to put in the t-mobile sim for 7 days to get OEM unlock, or will I need this done in an EU country (it is an EU version) due to the region locking Samsung has been doing since 2013? There just seems to be a lot of competing and incomplete information all over the damned place.
And don't tell me to search, please. I've been around on this forum long enough to know how to search, and long enough to know that search doesn't always yield the results you're looking for. So, if you have a link to a more descriptive explanation of what to do/expect, I'd be grateful.
Thanks.
EDIT: Found this: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
Maybe that would work... but still don't understand if I need it activated on an EU SIM first.. Now I remember why I've avoided Samsung devices...
Click to expand...
Click to collapse
Been a month and no oem unlock for me... Tried all the time trick settings and factory reset plus more time changing... I am not using a sin on this phone because I have a work phone... Why so much bs just for oem unlock?
IparryU said:
Been a month and no oem unlock for me... Tried all the time trick settings and factory reset plus more time changing... I am not using a sin on this phone because I have a work phone... Why so much bs just for oem unlock?
Click to expand...
Click to collapse
Oem unlock isnt gonna do anything for the device. Its kind of pointless to do for now.
HELP! OEM Unlock came up after 7 days. I turned it on, and it said that doing so will erase data... yadda yadda, and then it restarted, wiped, and then rebooted. ... No OEM Unlock in the menu anymore and back to RMM STATE: Prenormal.
WTF??
stewa2jm said:
HELP! OEM Unlock came up after 7 days. I turned it on, and it said that doing so will erase data... yadda yadda, and then it restarted, wiped, and then rebooted. ... No OEM Unlock in the menu anymore and back to RMM STATE: Prenormal.
WTF??
Click to expand...
Click to collapse
Multiple guides to either TWRP/root or ROM s9+ involve manually restarting the phone BEFORE samsung auto restarts your phone.
In other words, don't let the force restart from samsung go through, and manually restart it the moment you press OK to factory wipe and restart
EDIT: also make sure you have signed out of google before going into DL mode to TWRP phone, as this does the "FRP lock" from what I personally understand and Odin won't let you TWRP with FRP lock on. This was my 2nd mistake (and second 7-day lockout). First mistake was what you did, by letting samsung beat you at restarting phone.
jujubeans said:
Multiple guides to either TWRP/root or ROM s9+ involve manually restarting the phone BEFORE samsung auto restarts your phone.
In other words, don't let the force restart from samsung go through, and manually restart it the moment you press OK to factory wipe and restart
EDIT: also make sure you have signed out of google before going into DL mode to TWRP phone, as this does the "FRP lock" from what I personally understand and Odin won't let you TWRP with FRP lock on. This was my 2nd mistake (and second 7-day lockout). First mistake was what you did, by letting samsung beat you at restarting phone.
Click to expand...
Click to collapse
Thanks. I got through it all a while back now. You have to be lightning quick. So dumb. This will most likely be my last Samsung device. There are other options that are much less hassle to do this work on.
Hi!
New here, hope I am in the right place...I have limited tech skills (born pre cell phones and computers) I did manage to install a custom ROM on an old HTC years ago, and thought I could do it again!
I have a Samsung A10e (SM-A102U) locked to sprint.
I can get the developer options but can't get the OEM unlock option. I also can't wait 7 days. Have tried a few things with the date and turning off updates etc, nothing worked. Here is what I am trying to do in order (please correct me if it is the wrong order) Ultimately I want my phone unlocked for use with any sim, and install a custom rom, to remove some bloatware. Could I wipe the phone totally take it to a piece of memory with no ROM and then re-load it, or use ADB to do it? Please excuse my ignorance - if I sound clueless I kinda am!
1. Unlock the bootloader
2. Install TWRP
3. Install custom ROM
It has taken me days of searching but to no avail, literally pulling my hair out. Happy to buy a beer for anyone that helps!
Wow,thanks...
Response has been overwhelming...
SandsCayman said:
Hi!
New here, hope I am in the right place...I have limited tech skills (born pre cell phones and computers) I did manage to install a custom ROM on an old HTC years ago, and thought I could do it again!
I have a Samsung A10e (SM-A102U) locked to sprint.
I can get the developer options but can't get the OEM unlock option. I also can't wait 7 days. Have tried a few things with the date and turning off updates etc, nothing worked. Here is what I am trying to do in order (please correct me if it is the wrong order) Ultimately I want my phone unlocked for use with any sim, and install a custom rom, to remove some bloatware. Could I wipe the phone totally take it to a piece of memory with no ROM and then re-load it, or use ADB to do it? Please excuse my ignorance - if I sound clueless I kinda am!
1. Unlock the bootloader
2. Install TWRP
3. Install custom ROM
It has taken me days of searching but to no avail, literally pulling my hair out. Happy to buy a beer for anyone that helps!
Click to expand...
Click to collapse
I have the exact same question.
it will not happen alot of us based carriers will lock down the phone via bootloader our best option is to find combination firmware and hopefully find root that way assuming that method still works.
Same situation here with Verizon. And sorry to tell you but I don't think anything will happen for you after seven days either, at least nothing did for me. I've spent a long time trying to get past this with no success, trying every trick I've found (the changing the date manually trick, factory resetting and trying on WiFi, etc.).
Also, using the app "Settings Database Editor," I've found the config/property where OEM bootloader unlock has been disabled:
"sys.oem_unlock_allowed" "0"
Screenshot here.
I'm hoping maybe we can edit that property via ADB or something. I'm not really holding out any hope here though. :-/
One other random discovery (not really helpful or relevant for our OEM bootloader unlock goal, but something I discovered while trying to obtain unlock): I believe I discovered a firmware error (at least on the Verizon build). When you hold volume up + power together for about 30 seconds, the phone shows the recovery menu for a split second but then instantly/immediately wipes all data and factory resets, without ever allowing the user to choose their own recovery menu selection and without giving any reset confirmation prompt before instantly wiping all user data. It's not supposed to work that way, according to the phone's user manual/Samsung technical support instruction. It's actually really pissed me off because I've triggered this instant reset twice now by accident just by having the phone in my back pocket and sitting down. I go to pick up my phone from my pocket and notice the screen is on and then discover everything was wiped. Very annoying! I called Samsung customer support twice to try to explain that I believe there to be a firmware error present (at least on Verizon models) but they didn't seem to care/their support script told them to have me take the device to some local authorized third-party screen repair place. One good outcome I've discovered from factory resetting the phone is that you can at least avoid enrolling the phone in part of the Knox security crap, the "kme" protection. I originally couldn't use remote apps like TeamViewer or AnyDesk without some stupid "Protected by Knox" notification popping up and then my remote app instantly exiting. Made me so angry. But now I'm able to use those apps without any issue. Though, the phone does try to have me agree to enroll in kme protection or whatever about once a day and I have to manually close the enrollment agreement form that pops up.
allenjthomsen said:
it will not happen alot of us based carriers will lock down the phone via bootloader our best option is to find combination firmware and hopefully finwww reset that way assuming that method still works.
Click to expand...
Click to collapse
I've had the same issue with entire A series. All OEM's are disabled regardless of carrier. It seems to be part of Samsung's firmware. After nothing but dead ends and contacting samsung directly i was left scratching my head. Came here searching for some insights I may have overlooked.
-Enable developer options
-Enable wifi
-Join a network
-Change date to 10 days forward
-Reboot phone
-OEM unlock will be available
Thank me later
moe7863 said:
-Enable developer options
-Enable wifi
-Join a network
-Change date to 10 days forward
-Reboot phone
-OEM unlock will be available
Thank me later
Click to expand...
Click to collapse
Nothing happens/doesn't work for Verizon. :-/
I mentioned having tried this technique already in my previous post above.
---------- Post added at 07:42 PM ---------- Previous post was at 07:38 PM ----------
For what it's worth, here's a sister thread I started on this topic with a few responses/potential bootloader unlock ideas shared by other members but no real solid progress made at this point:
https://forum.xda-developers.com/galaxy-a10/help/samsung-galaxy-a10e-to-t3990817/page4
the bl is not unlockable
Bump
I know this is possible I've seen it done before. I think it had to do with a modified ota update.
SHAD0WUSER said:
Bump
I know this is possible I've seen it done before. I think it had to do with a modified ota update.
Click to expand...
Click to collapse
Do you have proof of this being done?
Because as far as I'm aware, it's been impossible to unlock bootloader for years
I actually purchased this phone from Metro last week after searching for it on XDA and seeing that is was BL unlockable. I didn't realize any the time that this was only the international variants. Good luck to all devs whose skillset is better than my own.
ShaDisNX255 said:
Do you have proof of this being done?
Because as far as I'm aware, it's been impossible to unlock bootloader for years
Click to expand...
Click to collapse
it is not possible.. also u cant flash a modified ota cuz it will fail sig check
nateberhardt81 said:
I actually purchased this phone from Metro last week after searching for it on XDA and seeing that is was BL unlockable. I didn't realize any the time that this was only the international variants. Good luck to all devs whose skillset is better than my own.
Click to expand...
Click to collapse
if u looked u would have seen the model numbers are different
elliwigy said:
if u looked u would have seen the model numbers are different
Click to expand...
Click to collapse
Yeah... I I knew better than to just look at a10e and assume they were all the same. I went through the same struggle with a J7 not too long ago... Should have learned my lesson then.
nateberhardt81 said:
Yeah... I I knew better than to just look at a10e and assume they were all the same. I went through the same struggle with a J7 not too long ago... Should have learned my lesson then.
Click to expand...
Click to collapse
no biggie.. at least those r super cheap.. i got a a50 just to brick it to try an exploit that didnt work lol.. o well
I have an A10e as well but the model number is SM-S102DL, I am a complete novice when it comes t phones but will I be able to root this without unlocking the bootloader?
xSpookyx said:
I have an A10e as well but the model number is SM-S102DL, I am a complete novice when it comes t phones but will I be able to root this without unlocking the bootloader?
Click to expand...
Click to collapse
no.. are u sure u have a a10e?
you cant root without exploits that dknt exist without unlocking the bootloader
No matter about root. but I converted many of Samsung A10e to international variant to remove any boost metropcs or any other networks bloatware application.
you can also do it without any issue. Simply flash A102U1 Firmware. I m not sure that it will work on Network Locked/Sim locked devices. I flash and convert it after using a remote unlocking service which already changed the CSC version of EFS to XAA from the BST csc...
XAA is for US Unlocked Without carrier locked phones and BST for Boost mobile carrier only which came with lots of boost bloatwares but maybe that A10e boost remote unlock service saved me.
check the screenshot attached.
Shabby The Dev said:
No matter about root. but I converted many of Samsung A10e to international variant to remove any boost metropcs or any other networks bloatware application.
you can also do it without any issue. Simply flash A102U1 Firmware. I m not sure that it will work on Network Locked/Sim locked devices. I flash and convert it after using a remote unlocking service which already changed the CSC version of EFS to XAA from the BST csc...
XAA is for US Unlocked Without carrier locked phones and BST for Boost mobile carrier only which came with lots of boost bloatwares but maybe that A10e boost remote unlock service saved me.
check the screenshot attached.
Click to expand...
Click to collapse
Careful, don't post your IMEI on the internet as some bad people can do stuff with it
Samsung A02s(SM-A025F)
I do these steps any body help
1.I unlock oem through developer option
2.I unlock bootloader successfully
3.I downloaded firmware and patch AP with magisk to root
4.I flash Patched AP
5.After getting my phone rooted successfully I want to install TWRP Recovery
6.I downloaded unofficial version of TWRP from xdaforums....
7.I followed the steps guided here
The steps are as follows
1.reboot to boot loader and flash vbmeta_disable.tar
2.Put TWRP tar in AP and flash
3.Reboot to recovery
4.Disable encryption
Go to Advanced >Terminal : type "multidisabler"
5.Go back to wipe>Format Data>type "yes"
6.Reboot system
This is my first experience to root and flash TWRP.... but after that when I reboot my phone got lock .... only official binaries allowed to be installed....and stuck there
I got frightened so I locked my bootloader
But nothing happens...
I downloaded stock firmware and flash.....now my phone works perfectly But I want to root my phone I searched and found a correct way to root but now oem unlock option is not found in developer options....
I watched hundreds of videos on yt and searched a lot on Google but
found no proper solution.....someone tell me to wait 7 days....
In about phone> phone status>uptime
Uptime should be equal to 7days... then oem unlock option will appear but ...... I want another solution date change and WiFi connect is not solution ... If any body knows any other solution please guide me ... I'll be very thankful.....
@ladlabaloch512
Perhaps your device has the same "OEM unlock" block like mine.
On mine I was supposed to wait 7d after turning on dev options.
I bypassed that by
1. switching to airplane mode
2. Setting manually date back one month
3. Restart (still in airplane mode)
4. Turning off airplane mode and let it sync date
and voila OEM unlock option was there.
Perhaps that works on your device as well.
bmwdroid said:
@ladlabaloch512
Perhaps your device has the same "OEM unlock" block like mine.
On mine I was supposed to wait 7d after turning on dev options.
I bypassed that by
1. switching to airplane mode
2. Setting manually date back one month
3. Restart (still in airplane mode)
4. Turning off airplane mode and let it sync date
and voila OEM unlock option was there.
Perhaps that works on your device as well.
Click to expand...
Click to collapse
Thanks for reply...
This bypass method doesn't work in my device
Im too
i have tried everything But I read on somewhere that policy was upgrade to 1000 hours so i waited and hopping thats work!
Now it's almost 700 and i restarted before it on 200 so it's supposed to be 900
Mahmoudm.kamal said:
Im too
i have tried everything But I read on somewhere that policy was upgrade to 1000 hours so i waited and hopping thats work!
Now it's almost 700 and i restarted before it on 200 so it's supposed to be 900
Click to expand...
Click to collapse
Keep us updated.. I'd like to get my OEM unlock to come out of hiding.. this is frustrsting.. i see all these tutorials for the A02s root, twrp and ROMs and whatnot and I'm itching to get flashing!
Is it possible to flash an unlocked carrier firmware in ODIN and then be able to unlock OEM? Without carrier issues or anything? I'm a little nervous to be the first to try.. and not sure where to find US unlocked carrier firmware or if location even matters... I have the SM-A025AZ (US Cricket variant).. I guess as long as Download Mode (fastboot) is still accessible I could just flash the Cricket version back to the device.. bricked my LG-E980 back in the day.. took me a few months how to get it back up and running with LG flash tool.. i just dont want to repeat that fiasco lol... so anybody got any updates on hacking this OEM (un)lock bs??? Or any idea on flashing some other variant to the device without interrupting carrier stuff??.. seems like alot just to get a damn virtual switch to turn on.. but damnit I need root access! Lol.. about to just exchange this phone for an actual rootable phone.. i disagree with charging for hotspot.. that should be illegal.. getting charged twice to use th same bs internet.. eff that.. i just want Rooooooot!!!
Hello,
I have also been having these troubles, with no way to unlock oem after stock flash, and the closest I've got to finding a solution was this, but I simply cannot find samsung's bootloader unlocking form like it says in the guide. I bought my phone just for a bootloader unlockable version (A025M), and now I am very angry at samsung.
also, since over a 1000 hours have gone by since last post, have any one of you solved this issue just by waiting?
Noobiu said:
Hello,
I have also been having these troubles, with no way to unlock oem after stock flash, and the closest I've got to finding a solution was this, but I simply cannot find samsung's bootloader unlocking form like it says in the guide. I bought my phone just for a bootloader unlockable version (A025M), and now I am very angry at samsung.
also, since over a 1000 hours have gone by since last post, have any one of you solved this issue just by waiting?
Click to expand...
Click to collapse
Nope, More than 2000 hours and also changed firmwares and waited again an again and tried alot of ways but enable oem still disappeared
Im also very angry from samsung
Mahmoudm.kamal said:
Nope, More than 2000 hours and also changed firmwares and waited again an again and tried alot of ways but enable oem still disappeared
Im also very angry from samsung
Click to expand...
Click to collapse
its not only samsung that does this, many other companies like motorola does this. Dont be angry, just try a different device. Also, snapdragon US models (i dont think) arent able to be unlocked. If its a mediatek model and isnt sim/carrier locked, u can try MTKClient
Swyen said:
its not only samsung that does this, many other companies like motorola does this. Dont be angry, just try a different device. Also, snapdragon US models (i dont think) arent able to be unlocked. If its a mediatek model and isnt sim/carrier locked, u can try MTKClient
Click to expand...
Click to collapse
Yes dear, i had changed it since more than 7 months with A52S , thanks.
Mahmoudm.kamal said:
Yes dear, i had changed it since more than 7 months with A52S , thanks.
Click to expand...
Click to collapse
And, my A037W doesnt have the OEM Unlock option. Use an MTK tool to unlock it, thats how I did it
ewrecc said:
Is it possible to flash an unlocked carrier firmware in ODIN and then be able to unlock OEM? Without carrier issues or anything? I'm a little nervous to be the first to try.. and not sure where to find US unlocked carrier firmware or if location even matters... I have the SM-A025AZ (US Cricket variant).. I guess as long as Download Mode (fastboot) is still accessible I could just flash the Cricket version back to the device.. bricked my LG-E980 back in the day.. took me a few months how to get it back up and running with LG flash tool.. i just dont want to repeat that fiasco lol... so anybody got any updates on hacking this OEM (un)lock bs??? Or any idea on flashing some other variant to the device without interrupting carrier stuff??.. seems like alot just to get a damn virtual switch to turn on.. but damnit I need root access! Lol.. about to just exchange this phone for an actual rootable phone.. i disagree with charging for hotspot.. that should be illegal.. getting charged twice to use th same bs internet.. eff that.. i just want Rooooooot!!!
Click to expand...
Click to collapse
STOP TRYING TO UNLOCK A US DEVICE ITS NOT POSSIBLE
Swyen said:
And, my A037W doesnt have the OEM Unlock option. Use an MTK tool to unlock it, thats how I did it
Click to expand...
Click to collapse
Which tool did you use?
Ok , lemme cover my bases here... OnePlus 10t, Android 12, T Mobile. .
I have usb debugging on, oem unlock on, and device appears in ADB ... Newest platform tools, updated drivers.... When I run 'adb reboot bootloader', the phone shuts off, then I see 'fastboot mode' for like half a second , and it goes off and boots up normal. I can enter fastbootd .. but regular fastboot causes instant reboot! Can ANYONE help me with what I need to do? You can't unlock bootloader in fastbootd... So I need help figuring out how to make it NOT kick out of fastboot when I enter the command. (Usb 2.0)
OPPO locked the bootloader permanently. They do this on the find series as well.. basically bootloader mode is disabled.
I haven't heard about this before, is it a T-Mobile only thing? That seems really bad for oppo to do that...
Hurt Copain said:
OPPO locked the bootloader permanently. They do this on the find series as well.. basically bootloader mode is disabled.
Click to expand...
Click to collapse
ok , so how then can i either re activate this mode or root this device? because that is a deal breaker for me! I wont keep the ONLY model of this phone that has Fastboot disabled, and therefore is unable to be rooted! I have about 8 days left to package back up and send back to Tmobile for refund! Now i can fully reach EDL mode, so if there is a software that can let me flash the EU Unlocked FW , then please direct me. I saw some success written about here with the new MSM, but it requires some authentication. I am 100% fully committed to any method, no matter how complex, to rectify this travesty! The ONLY reason i jumped from Samsung to OnePlus years ago was because of how Developer friendly they were... Easy unlock of bootloader... yadda yadda! Now the curse of Beatbreaker has struck again, and the impossible has happened in that SAMSUNG bootloaders are now easily unlockable via purchased token... and Oneplus has become part of an asshat dictatorship.
Please advise if there is ANYONE here who can either help me with this situation, or can direct me to instructions/software that can flip this situation around. I mean, the fact that Fastbootd reports my device in "Fastboot" when running 'Fastboot devices' ... AND that even if only for a glimpse of a second i can see FASTBOOT MODE, before it kicks me out and reboots, tells me that there must be some glitch, exploit, or workaround that can re-enable it! I only state this because some phone companies (carriers) like Metropcs were pre-installing FW that made Download mode disabled for quite a few devices, but thru some low level (edl) actions, we were able to reverse that and load a global fw to the phones, restoring all functions!
ok long posts.... ANYONE... I am up for ALL suggestions, because i can fully brick this phone and return it , but my window closes in 7 days!
beatbreakee said:
ok , so how then can i either re activate this mode or root this device? because that is a deal breaker for me! I wont keep the ONLY model of this phone that has Fastboot disabled, and therefore is unable to be rooted! I have about 8 days left to package back up and send back to Tmobile for refund! Now i can fully reach EDL mode, so if there is a software that can let me flash the EU Unlocked FW , then please direct me. I saw some success written about here with the new MSM, but it requires some authentication. I am 100% fully committed to any method, no matter how complex, to rectify this travesty! The ONLY reason i jumped from Samsung to OnePlus years ago was because of how Developer friendly they were... Easy unlock of bootloader... yadda yadda! Now the curse of Beatbreaker has struck again, and the impossible has happened in that SAMSUNG bootloaders are now easily unlockable via purchased token... and Oneplus has become part of an asshat dictatorship.
Please advise if there is ANYONE here who can either help me with this situation, or can direct me to instructions/software that can flip this situation around. I mean, the fact that Fastbootd reports my device in "Fastboot" when running 'Fastboot devices' ... AND that even if only for a glimpse of a second i can see FASTBOOT MODE, before it kicks me out and reboots, tells me that there must be some glitch, exploit, or workaround that can re-enable it! I only state this because some phone companies (carriers) like Metropcs were pre-installing FW that made Download mode disabled for quite a few devices, but thru some low level (edl) actions, we were able to reverse that and load a global fw to the phones, restoring all functions!
ok long posts.... ANYONE... I am up for ALL suggestions, because i can fully brick this phone and return it , but my window closes in 7 days!
Click to expand...
Click to collapse
Dang! This is a messy situation for yah! I contacted support for an MSM tool and they said I have to send it in for them to flash it.
I think trying to have them flash some other variant would take you past your 7 day window and they may not do it anyways.
I would say least send an email to OnePlus support and ask if they would flash to other variant otherwise you will be returning the phone. You should get a response soon. Otherwise I'd lean towards returning it... Sadly.
Then buy straight from oneplus if you still want a 10t. They may have a good blackfriday deal on this phone as well.
maamdroid said:
Dang! This is a messy situation for yah! I contacted support for an MSM tool and they said I have to send it in for them to flash it.
I think trying to have them flash some other variant would take you past your 7 day window and they may not do it anyways.
I would say least send an email to OnePlus support and ask if they would flash to other variant otherwise you will be returning the phone. You should get a response soon. Otherwise I'd lean towards returning it... Sadly.
Then buy straight from oneplus if you still want a 10t. They may have a good blackfriday deal on this phone as well.
Click to expand...
Click to collapse
thank you ... i was waiting for the response from someone who had been in contact with them. I will mail them right away.