Related
After giving the V10 a month, I decided to swap it out (why is for another thread, I suppose). I had rooted and installed TWRP, so I used the stock files provided in the dev threads to go back to stock and relock the bootloader. I did a factory reset to make sure everything was working properly.
When I went to turn in the device, the guy at the store ran a phone code and got a code back from the network. Apparently, it does a check to make sure the device is the same one that I originally purchased and that it hasn't been rooted (in a Samsung phone's case, it checks Knox status as well). If it comes back as rooted or having ever been rooted, he said the system will deny the exchange. Mine passed (since thankfully LG's stuff can be completely reset), and I didn't volunteer that I had rooted it.
Just be aware that you need to go completely to stock in order to return the phone to swap out for a new one. I'll assume if your phone get's flagged in the system once, you can't ever return it, even if you try to flash back to stock again.
I love Jump on Demand, but I think it's going to keep me stuck unrooted for the most part - can't risk blowing $700.
Thanks for the heads up! With JUMP it shouldn't matter, but a device exchange may flag.
Sent from my LG-H901 using Tapatalk
I rooted my Note 4 and 5 with twrp aswell.... Did jump from both with no problem! My last jump was Nov. 15th for the V10 and the promo and had no problem, must be a new policy!!! But yes, always go back to stock before upgrade lol
That's good you passed the network check, I wonder how that works? When you rooted, did you freeze that weird pr.adapt app that kept requesting root access?
YrrchSebor said:
That's good you passed the network check, I wonder how that works? When you rooted, did you freeze that weird pr.adapt app that kept requesting root access?
Click to expand...
Click to collapse
I did freeze it, but the T-mobile app (which I use to check my data usage) still saw that my device was rooted, even though I never gave that app root access. However, when I start the app, I told it I didn't want it to share any info with T-mobile, so it shouldn't have had permission to report my root status to T-mobile (and apparently it didn't).
daveeckert said:
I did freeze it, but the T-mobile app (which I use to check my data usage) still saw that my device was rooted, even though I never gave that app root access. However, when I start the app, I told it I didn't want it to share any info with T-mobile, so it shouldn't have had permission to report my root status to T-mobile (and apparently it didn't).
Click to expand...
Click to collapse
Ahh OK, I guess that could be an important point then! I always disallow sending the diagnostics and such in the my T-Mobile app... Thank god. Hopefully it'll be OK. Thanks for the heads up!
I just jumped from a Note 5 to the V10. I reset the Note 5 using Kies, but knox was still tripped. No issue at the store. The G4 that I jumped from to go to the Note 5 also had been rooted/bootloader unlock, no issue when I did that either.
That's weird. I called a store and asked them this exact question before turning in my G3. She said it didn't matter and they were gonna wipe the phone. It's possible she didn't understand the question, but I turned it in with no issues and haven't received any calls over the few days I've had the V10. I'm on the basis Jump plan too.
No issues trading in my Knox-tripped Note 4 a couples months ago. Maybe just that one store is getting a little wacky with the checking lol
Unheard said:
I just jumped from a Note 5 to the V10. I reset the Note 5 using Kies, but knox was still tripped. No issue at the store. The G4 that I jumped from to go to the Note 5 also had been rooted/bootloader unlock, no issue when I did that either.
Click to expand...
Click to collapse
Just curious how you like the V10 vs. the Note 5? I kinda like the V10 hardware, but it seems there will be very little development done on this phone (I'm dying for CM in particular). Doesn't seem as popular as I had hoped it would be with the dev community. I'm considering the Note 5 as a JoD exchange (and thanks to OP for the heads up here), since there seems to be a lot of dev activity for it. Just don't know if I'll be able to deal with that hardware home button. Guess I'm picky.
I can't tell the number of rooted phones I've sent back to Verizon and T-mobile, never a word.
Sent from my LG-H901 using Tapatalk
YrrchSebor said:
Ahh OK, I guess that could be an important point then! I always disallow sending the diagnostics and such in the my T-Mobile app... Thank god. Hopefully it'll be OK. Thanks for the heads up!
Click to expand...
Click to collapse
Okay you could also block it with root cloak...
Sent from my LG-H901 using Tapatalk
Been on Verizon, Alltel, Sprint, and Ma'Bell. always rooted, never had e Problem. Just make shure you return to stock. I even exchanged a couple of Samsungs with Knox trip, Lucky I guess. I've heard Stories but never met anyone that has been returned or charged a device.
spg900ny said:
Just curious how you like the V10 vs. the Note 5? I kinda like the V10 hardware, but it seems there will be very little development done on this phone (I'm dying for CM in particular). Doesn't seem as popular as I had hoped it would be with the dev community. I'm considering the Note 5 as a JoD exchange (and thanks to OP for the heads up here), since there seems to be a lot of dev activity for it. Just don't know if I'll be able to deal with that hardware home button. Guess I'm picky.
Click to expand...
Click to collapse
Currently have the Note 5. I wouldn't say there is a lot of dev activity. Then again, I came from a Nexus 6. [emoji2]
I can tell you that this policy was implemented just a few weeks ago. I work for T-Mobile (Corporate Store) and every time you take a phone for Jump, Jump 2 or Jump on demand; the system is asking for a code (it doesn't matter if its android or ios) that the phone displays (usually a 3-4 characters) when you enter a "##" code. Then we enter it on the system and we either get a "thumbs up" or a "denied". I haven't seen a denial at my store, but when I saw this policy, the first thing that I thought was that it was looking for a modified system.
Cool, so no more Jump for me. Looks like a steady stream of Priv's, 950XL's, Moto's, or Nexuses.
xxdjvalexx said:
I can tell you that this policy was implemented just a few weeks ago. I work for T-Mobile (Corporate Store) and every time you take a phone for Jump, Jump 2 or Jump on demand; the system is asking for a code (it doesn't matter if its android or ios) that the phone displays (usually a 3-4 characters) when you enter a "##" code. Then we enter it on the system and we either get a "thumbs up" or a "denied". I haven't seen a denial at my store, but when I saw this policy, the first thing that I thought was that it was looking for a modified system.
Click to expand...
Click to collapse
I just got the V10 and traded in my rooted and ROM'd Galaxy S6 for it. She did the code thing, didn't bat an eye.
Sent from my LG-H901 using Tapatalk
xxdjvalexx said:
I can tell you that this policy was implemented just a few weeks ago. I work for T-Mobile (Corporate Store) and every time you take a phone for Jump, Jump 2 or Jump on demand; the system is asking for a code (it doesn't matter if its android or ios) that the phone displays (usually a 3-4 characters) when you enter a "##" code. Then we enter it on the system and we either get a "thumbs up" or a "denied". I haven't seen a denial at my store, but when I saw this policy, the first thing that I thought was that it was looking for a modified system.
Click to expand...
Click to collapse
What ## code do you enter?
I would imagine that code is more of a quick IMEI/"is the phone stolen" verification rather than checking for root.
daveeckert said:
After giving the V10 a month, I decided to swap it out (why is for another thread, I suppose). I had rooted and installed TWRP, so I used the stock files provided in the dev threads to go back to stock and relock the bootloader. I did a factory reset to make sure everything was working properly.
When I went to turn in the device, the guy at the store ran a phone code and got a code back from the network. Apparently, it does a check to make sure the device is the same one that I originally purchased and that it hasn't been rooted (in a Samsung phone's case, it checks Knox status as well). If it comes back as rooted or having ever been rooted, he said the system will deny the exchange. Mine passed (since thankfully LG's stuff can be completely reset), and I didn't volunteer that I had rooted it.
Just be aware that you need to go completely to stock in order to return the phone to swap out for a new one. I'll assume if your phone get's flagged in the system once, you can't ever return it, even if you try to flash back to stock again.
I love Jump on Demand, but I think it's going to keep me stuck unrooted for the most part - can't risk blowing $700.
Click to expand...
Click to collapse
No, he was pulling your leg. I turned in my note 4 with twrp and a custom rom in October and I had to do the same check, it's just a service code check to make sure it's the same one you bought from tmo, if it checked for root I would never be able to get a phone again because I flashed that phone so much. I talk to the guys at the store and told them I rooted do they.
I'm about to go for it and buy a 7 Pro, do we have an MSM Download Tool available yet here on XDA for the 7 Pro? I'm coming from the 6T and that tool is a MUST. Thanks guys!
No not yet. We have the files but its password protected.
slayerh4x said:
No not yet. We have the files but its password protected.
Click to expand...
Click to collapse
Ah thanks! That's how it all started with the 6T, password protected file. It's a matter of time though! Cool! :good:
You'll be waiting for two weeks or more. I set oem lock to "off" in settings, and then did "fastboot oem lock" like an idiot and I literally can't get into my phone at all now. All fastboot commands fail and I can't reboot into recovery either because it just says "your device is corrupt" every single time. I contacted oneplus support multiple times and they told me "we don't have anything available yet to help you, so you can just return it to us." Huge waste of time speaking to all those useless reps and I'm definitely not going to buy another oneplus product again. It's actually ridiculous that they don't just provide those tools upon release, especially when this issue has PERSISTED across all of their devices. I still have the phone for now, so if anyone finds a useful Oneplus rep who actually has the tools, or if someone figures out how to fix this issue, please let me know.
Lucifer6 said:
You'll be waiting for two weeks or more. I set oem lock to "off" in settings, and then did "fastboot oem lock" like an idiot and I literally can't get into my phone at all now. All fastboot commands fail and I can't reboot into recovery either because it just says "your device is corrupt" every single time. I contacted oneplus support multiple times and they told me "we don't have anything available yet to help you, so you can just return it to us." Huge waste of time speaking to all those useless reps and I'm definitely not going to buy another oneplus product again. It's actually ridiculous that they don't just provide those tools upon release, especially when this issue has PERSISTED across all of their devices. I still have the phone for now, so if anyone finds a useful Oneplus rep who actually has the tools, or if someone figures out how to fix this issue, please let me know.
Click to expand...
Click to collapse
1. If you do your research before just throwing fastboot commands you would have read that others on here have done the same, so do your homework.
2. If it's ridiculous that they don't just provide those tools upon release, especially when the issue has PERSISTED across all of their devices, then why run fastboot oem lock?
Everyone is always so quick to blame OEMs but not their own poor decision making. Take responsibility for your own actions even if you run them in cmd prompt.
T_VASS said:
1. If you do your research before just throwing fastboot commands you would have read that others on here have done the same, so do your homework.
2. If it's ridiculous that they don't just provide those tools upon release, especially when the issue has PERSISTED across all of their devices, then why run fastboot oem lock?
Everyone is always so quick to blame OEMs but not their own poor decision making. Take responsibility for your own actions even if you run them in cmd prompt.
Click to expand...
Click to collapse
Thank you for your reply. This is my first time owning a OnePlus device, so I hadn't looked at anything at on any of the community forums about it except how to root it and install magisk.
My last device was a razer phone 2, which had similar steps towards rooting it, and I actually did use "fastboot flashing lock_critical" to re-lock the bootloader after unlocking it, so I assumed that it would be the same for the oneplus, which in hindsight, obviously I was wrong.
But even if that was a minor screw up, I can't access the device at all, and that's what's bugging me. I do frequent backups, so having an option to erase all my data wouldn't be an issue if that was given, but not having that option at all and then bring told by OnePlus that the only option is to return it is absurd. I appreciate your feedback towards what I said, and if you are a OnePlus employee then I'm still standing by what I said and calling all of the 'support' I received useless, as it was just a waste of time and didn't lead to any sort of fix
Lucifer6 said:
Thank you for your reply. This is my first time owning a OnePlus device, so I hadn't looked at anything at on any of the community forums about it except how to root it and install magisk.
My last device was a razer phone 2, which had similar steps towards rooting it, and I actually did use "fastboot flashing lock_critical" to re-lock the bootloader after unlocking it, so I assumed that it would be the same for the oneplus, which in hindsight, obviously I was wrong.
But even if that was a minor screw up, I can't access the device at all, and that's what's bugging me. I do frequent backups, so having an option to erase all my data wouldn't be an issue if that was given, but not having that option at all and then bring told by OnePlus that the only option is to return it is absurd. I appreciate your feedback towards what I said, and if you are a OnePlus employee then I'm still standing by what I said and calling all of the 'support' I received useless, as it was just a waste of time and didn't lead to any sort of fix
Click to expand...
Click to collapse
LOL if I was a OP employee I would be helping out with the MSM tool! I cannot tell you the last device I rooted and installed ROMs on as its probably been close to 5 years and I see many things have changed. This is my first OP device since the original OP. I'll have my bin tonight but I am 99% sure I am going to wait for the MSM tool to come out whenever and do the international conversion that way. I hope you get everything sorted out!
Lucifer6 said:
You'll be waiting for two weeks or more. I set oem lock to "off" in settings, and then did "fastboot oem lock" like an idiot and I literally can't get into my phone at all now. All fastboot commands fail and I can't reboot into recovery either because it just says "your device is corrupt" every single time. I contacted oneplus support multiple times and they told me "we don't have anything available yet to help you, so you can just return it to us." Huge waste of time speaking to all those useless reps and I'm definitely not going to buy another oneplus product again. It's actually ridiculous that they don't just provide those tools upon release, especially when this issue has PERSISTED across all of their devices. I still have the phone for now, so if anyone finds a useful Oneplus rep who actually has the tools, or if someone figures out how to fix this issue, please let me know.
Click to expand...
Click to collapse
OOF! That's awful! I'm going to buy the 7 pro soon here, and as tempted as I am to root the device and start tampering with it, I'm going to wait until we have an MSM tool here to use. It's a must have.
Lucifer6 said:
Thank you for your reply. This is my first time owning a OnePlus device, so I hadn't looked at anything at on any of the community forums about it except how to root it and install magisk.
My last device was a razer phone 2, which had similar steps towards rooting it, and I actually did use "fastboot flashing lock_critical" to re-lock the bootloader after unlocking it, so I assumed that it would be the same for the oneplus, which in hindsight, obviously I was wrong.
But even if that was a minor screw up, I can't access the device at all, and that's what's bugging me. I do frequent backups, so having an option to erase all my data wouldn't be an issue if that was given, but not having that option at all and then bring told by OnePlus that the only option is to return it is absurd. I appreciate your feedback towards what I said, and if you are a OnePlus employee then I'm still standing by what I said and calling all of the 'support' I received useless, as it was just a waste of time and didn't lead to any sort of fix
Click to expand...
Click to collapse
Really? You have been offered a fix! Send your phone on, and you'll have a working phone back weeks before the MSM tool is available. You are responsible, not OnePlus, SMH.
Sent from my GM1915 using Tapatalk
Anyone figure out the pSswared for the international msm file? Need it to flash my TMobile oneplus 7 pro to international it's getting bad battery life
Lucifer6 said:
Thank you for your reply. This is my first time owning a OnePlus device, so I hadn't looked at anything at on any of the community forums about it except how to root it and install magisk.
My last device was a razer phone 2, which had similar steps towards rooting it, and I actually did use "fastboot flashing lock_critical" to re-lock the bootloader after unlocking it, so I assumed that it would be the same for the oneplus, which in hindsight, obviously I was wrong.
But even if that was a minor screw up, I can't access the device at all, and that's what's bugging me. I do frequent backups, so having an option to erase all my data wouldn't be an issue if that was given, but not having that option at all and then bring told by OnePlus that the only option is to return it is absurd. I appreciate your feedback towards what I said, and if you are a OnePlus employee then I'm still standing by what I said and calling all of the 'support' I received useless, as it was just a waste of time and didn't lead to any sort of fix
Click to expand...
Click to collapse
Bashing OP support reps here is uncalled for. A rep can't help you because the method of trying to do what you want wasn't built into the software. Not the reps fault they can''t fix that they didn't build the software. Also OEM unlocking, rooting, flashing ROMs isn't covered by any type of warranty or support. So you better be thankful they are letting you send it in. If you choose to root, mod, or install software it's at your own risk.
TechOut said:
Bashing OP support reps here is uncalled for. A rep can't help you because the method of trying to do what you want wasn't built into the software. Not the reps fault they can''t fix that they didn't build the software. Also OEM unlocking, rooting, flashing ROMs isn't covered by any type of warranty or support. So you better be thankful they are letting you send it in. If you choose to root, mod, or install software it's at your own risk.
Click to expand...
Click to collapse
Yeah other people already said the same thing, thanks though!
I just need to get rid of the T-Mobile software. between the non fuctioning OnePlus site and the standard wait time it will be a month possibly before I get the unlock bin
Any new information around?
Enddo said:
Any new information around?
Click to expand...
Click to collapse
As far as I know, what we have is for the GM21AA for 9.5.3.
I think I saw one for the T-Mobile variant here as well, just haven't paid much attention there because I have AA model personally.
Not too sure about GM21BA either, someone add info for that here if you want.
Enddo said:
Any new information around?
Click to expand...
Click to collapse
https://piunikaweb.com/2019/05/29/how-to-unbrick-oneplus-7-pro-using-msm-download-tool/
Works like a charm, used it myself!
kimpreza said:
https://piunikaweb.com/2019/05/29/how-to-unbrick-oneplus-7-pro-using-msm-download-tool/
Works like a charm, used it myself!
Click to expand...
Click to collapse
NICE! Appreciate the info!
H4X0R46 said:
NICE! Appreciate the info!
Click to expand...
Click to collapse
I thought you had the 7pro already... I'm guessing I seen you on the 6t side
mlock420 said:
I thought you had the 7pro already... I'm guessing I seen you on the 6t side
Click to expand...
Click to collapse
I do! I have the global model so I tend to focus on stuff here that applies to my model lol I had the 6T for a while but did move over to the 7 Pro.
Long story short, I got a brain tumor (that's not going to kill me) but it's messed up my eyesight... which is great... so I decided to finally get rid of my beloved Pixel2 and get something with a larger screen so I could see the thing. Hence the S21+ and... it works for that. The screen is way bigger so it's great.
The problem is, one other thing that really worked well for my eye problem is VR. I have the Google Daydream headset and my eye problem means my left eye kind of moves around on its own. It's super fun... lol... but somehow, the VR tracks that and I can actually see in VR, use the browser, etc... It's not perfect but it gives my eyes a rest. But, apparently this phone doesn't work with Daydream unless I have root and edit some files. So ok, I need root.
My carrier is Google FI and I was under the impression that all of their phones came with OEM unlock, but I have no "OEM Unlock" option in developer tools. I am very confused by all the different information I'm finding out there.
So, here are my questions:
1. Is my phone already OEM unlocked because this is GoogleFI or am I screwed?
2. Is there some other way to get the OEM unlock?
3. I'm assuming there's no way to get root without OEM unlock?
4. Barring all of the above, does anyone know of any way to trick Google Daydream into working on this phone?
5. If I can't get Daydream to work, I can just pop out the daydream RFID thingy and use the headset as if it weren't daydream, but the controller doesn't seem to do anything. Is there a way to set that up? or is it possible to get a "Wand style" controller like this outside of daydream?
1 no
2 pay 150, look for a paid service on 1st page, I personally don't like that, I went with g9960 route
3 correct
4
https://www.reddit.com/r/daydream/comments/5jg33j
5 see pt 4
Thanks! That's a bummer... I'll wait until there's a community unlock somewhere.
The Daydream link you offered doesn't really help me. If you switch to the cardboard headset, it doesn't support the controller anymore. But I did find a post that helped me get it working:
Trying to get Daydream working on the MZP without root.
Can some one please help me edit the Daydream related APK's to automatically pass the checks in /system/etc/permissions/handheld_core_hardware.xml for and
forum.xda-developers.com
Basically you modify and recompile the daydream app.
I still want root, it's unfortunate Samsung sucks.
If your phone's model number is SM-G996U1 then it is unlocked. I'm thinking about getting one. Did you get it directly from Fi?
Lancez said:
If your phone's model number is SM-G996U1 then it is unlocked. I'm thinking about getting one. Did you get it directly from Fi?
Click to expand...
Click to collapse
Yes, I got it directly from FI.
So the problem is, I'm not up on the current lingo, but there are multiple kinds of unlocks. In this case, my phone is definitely carrier unlocked. Google FI requires that because it hopps carriers. But is it bootloader unlocked? I'm trying to figure that out, but none of the dialer codes work on this phone. I tried to get to fastboot, but Samsung phones are weird. It's almost like they have their own set of rules. lol
Any idea how I can check the bootloader?
It's been a loooong time since my last Samsung phone. But if my memory serves me well, you can turn off the phone then press and hold vol up or down and power button simultaneously (or even 3 buttons at same time). It'll take you to bootloader or recovery mode. You can try all possible combinations until you get what you want, it won't hurt your phone.
Oh, one more thing. If you are using third party dialer app instead of built-in. All codes are not gonna work.
Fi is offering $300 discount for existing customers, That's a pretty good deal. I'm ordering one right now.
Lancez said:
Oh, one more thing. If you are using third party dialer app instead of built-in. All codes are not gonna work.
Click to expand...
Click to collapse
I've tried both the default google dialer and the samsung dialer that came with it. Neither will do anything when I enter a dialer code. :-/
Lancez said:
Fi is offering $300 discount for existing customers, That's a pretty good deal. I'm ordering one right now.
Click to expand...
Click to collapse
I've tried a dozen different ways to get this to work. I do not think the bootloader is unlocked, and I do not think its unlockable without that paid services which is $150
OEM unlocking does not exist, even after waiting the 7 days.
I can boot into download mode, but the volume up thing does nothing
If I chose "Reboot to bootloader" it just boots the phone into safemode.
I've read that if you try and flash TWRP with the bootloader locked, it can brick your phone.
I've found no way to check if a samsung phone is bootloader unlocked.
I don't want to flash it, trip knox, and then end up having it bricked. lol
I'll take a look when I have the phone handy next week and keep you updated
Samsung's Galaxy S21 series can now be rooted with Magisk
You can now root your Galaxy S21, Galaxy S21 Plus, and Galaxy S21 Ultra using Magisk. Follow the link in the post for instructions.
www.xda-developers.com
As topjohnwu notes ... as of now, only the Exynos and Hong Kong Snapdragon Galaxy S21 devices can be bootloader unlocked,...
Click to expand...
Click to collapse
if that's not true I would be slightly annoyed cuz I spent extra 100$ to get the Hk version
fenvy said:
Samsung's Galaxy S21 series can now be rooted with Magisk
You can now root your Galaxy S21, Galaxy S21 Plus, and Galaxy S21 Ultra using Magisk. Follow the link in the post for instructions.
www.xda-developers.com
if that's not true I would be slightly annoyed cuz I spent extra 100$ to get the Hk version
Click to expand...
Click to collapse
It is true. You can root the phone, but you have to unlock the bootloader before you can root it. Currently the only way to unlock the bootloader in the US versions is to pay $150 to the dude that came up with the exploit. If you have the non us version, you can unlock it yourself.
charliemopps said:
I've tried a dozen different ways to get this to work. I do not think the bootloader is unlocked, and I do not think its unlockable without that paid services which is $150
OEM unlocking does not exist, even after waiting the 7 days.
I can boot into download mode, but the volume up thing does nothing
If I chose "Reboot to bootloader" it just boots the phone into safemode.
I've read that if you try and flash TWRP with the bootloader locked, it can brick your phone.
I've found no way to check if a samsung phone is bootloader unlocked.
I don't want to flash it, trip knox, and then end up having it bricked. lol
Click to expand...
Click to collapse
Just got my S21+ today and you were right. Bootloader is indeed unlockable by average users at least. I did get into recovery mode by using Vol up+power and I can see there's reboot to bootloader option. But it does nothing other then restarting the phone. I don't know how did you get into safe mode tho. (attached a pic of recovery mode from my phone)
Anyway, I'm pretty happy with the way it is and I personally would not pay anything over 50 bucks to get bootloader unlocked.
Lancez said:
If your phone's model number is SM-G996U1 then it is unlocked. I'm thinking about getting one. Did you get it directly from Fi?
Click to expand...
Click to collapse
Unlock means ?
My model is g996u . Will i get ota update ?
Anyone know if the Canadian version (SM-A536W) has OEM Unlock?
I'm thinking about purchasing this phone but I really want to be able to install a custom rom sometime in the future, I see that the US version has a locked bootloader even if purchasing a unlocked phone.
Here is a link to the actual phone on Amazon.ca
Thanks
I looked into the missing oem unlock a bunch today. Apparently, there's no real way to know for sure.
Even a more expensive recent Samsung phone had it get removed on an update and nothing would bring it back from an example I found (although that person didn't look into as I do below).
My A53 definitely doesn't have it and its flagged as what's known for it to be showing yet its not. UK may have it happen same as US. The chip used apparently doesn't matter. The guides for missing oem unlock out there all copied each other and they don't really know anything besides that it worked at times - it doesn't here.
Side point: I don't know if the following will work. Fastboot is disabled on my device (odin is used) so if patching recovery to enable fastboot is possible, it might help? I don't see how doing that would make oem unlock show up though so I feel like its not a complete picture, https://forum.xda-developers.com/t/unlock-the-bootloader-and-install-gsi-rom.4453961/ but the wipe part in theory might (some bring that up as a thing though noted it also doesn't seem to work for some as well). I'm not wiping my device as I'm not unlocking since I need the official rom so not testing it to find out.
Further side point: On opening developer options menu, it does checks for oem unlock to know if it should show, enable, or disable the setting preference. eg A53
Code:
OemUnlockPreferenceController: enableUnlock : 1 = /dev/block/persistent / 2 = 1
Apparently, that may also be tied to Google FRP eg https://github.com/shunf4/magisk-blockfrpwriting/blob/master/README.md and https://android.googlesource.com/platform/frameworks/base/+/master/services/core/java/com/android/server/oemlock/OemLockService.java line 229 etc. and also https://www.samsung.com/nz/support/mobile-devices/what-is-google-frp/ and its also tied to some other things.
Also, the build.prop isn't even listing ro.oem_unlock_supported for me. I would think it may have to be there ...compared to my last Samsung which does have that listed https://source.android.com/devices/bootloader/locking_unlocking (adb shell getprop ro.oem_unlock_supported)
Its possible that the unlock ability will show up randomly. Its possible that it never will. Its possible ones that have it right now will have it go missing after updates.
So is the way of Samsung today
S22 Ultra Exynos 2200 1TB doesn't support OEM Unlock?
I have ordered my S22 Ultra 1 TB storage ( SM-S908B) from Samsung website in UK. I have enabled the Developers mode in settings and now when i wanted to root my phone i can't believe it... my device doesn't have the OEM Unlock option in there...
forum.xda-developers.com
If its a requirement for you then it would be the better choice to choose another brand that's strong in allowing it. Samsung isn't. I don't know if its an accidental part of their security measures (difficult to deal with) or on purpose but its fickle with it.
Looks like its fickle anyway though with too much stuff needing to be checked and aligned with it showing in the first place because of Google. Google also didn't put in place any info to state why its disabled as the code decides lol. I love when devs do that /s.
That's everything I can find on the issue and my advice. I added all this info here as others can still see it and just used your post to let you know its iffy at best.
Thanks for all the info you posted!, I've been sorta outa the loop on what's been going on with Samsung and changes they have done.
My current device is an old Galaxy S2 T989D running my own custom rom from 2014 heh, I don't really use phone much for anything really just figured it might be a good time to upgrade to something newer and saw the A53 for a pretty good price for a mid range phone, has more than ample features for me - really only thinking that I might want run a custom rom sometime after they no longer give security updates etc.
I did come across this info today which does seem to give a pretty good explanation of how much has changed over the years with the OEM Unlock and unlocking the bootloader with Samsung devices.
Almite said:
I did come across this info today which does seem to give a pretty good explanation of how much has changed over the years with the OEM Unlock and unlocking the bootloader with Samsung devices.
Click to expand...
Click to collapse
Yeah. What I typed above was based on that and a lot more. However even that link is not the full picture.
Example "Samsung Galaxy devices that are sold in the USA with a Qualcomm Snapdragon SoC come with non-unlockable bootloaders (officially). And so, the OEM unlocking option does not exist on such devices."
The A53 I'm using has an exynos. So processor doesn't matter as oem unlock is missing with Samsung's exynos.
As well based on that quote you might see the country but CA, UK, etc can have it go missing or not found. There's no way to know for sure at all times.
Hence my post above. You just can't be sure if you can ever unlock or not. Unless someone finds a way that will do it and unless an update doesn't kill it. If you see it available then use it as it might go missing.
International models have the best chance though it seems but no one can guarantee what Samsung will do.
Bought phone off marketplace; verified it was working by inserting my SIM card and making a phone call prior to purchase. Later on while setting up the phone I discover that it's got administrative software installed on it and retail mode turned on.
Looking closer at the box, it said it's a demo unit. (I know, should've been more thorough)
The question I have is if it's a true demo unit that's unsalvageable, why was I able to make the call? (I used my own SIM)
Some demo units can make calls. People like to try them out in stores. Personally, I'd try to return it. Maybe you can flash a new firmware. Doubt makeup of hardware any different since it works. Never know though.
mt2020 said:
Some demo units can make calls. People like to try them out in stores. Personally, I'd try to return it. Maybe you can flash a new firmware. Doubt makeup of hardware any different since it works. Never know though.
Click to expand...
Click to collapse
Unfortunately returning isn't an option, the guy knew this thing had an issue and decided to not tell me. I figured since it made a call, it should be fine.
The IMEI number comes back as clean, I might try and see if I can use it for a "trade In" if flashing new firmware doesn't seem like it can happen.
How much did you pay?
kat3k said:
How much did you pay?
Click to expand...
Click to collapse
Too much of course.
Just go into Settings->Developer Options->Demo mode and take it out of demo mode.
Rubby1025 said:
Just go into Settings->Developer Options->Demo mode and take it out of demo mode.
Click to expand...
Click to collapse
Doesn't allow me to, asks for a password, none of the ones i've found floating around have worked.
there's a admin lockdown, software called SENNCO from Brichtec, its what's removed the "wipe data/factory reset" from the recovery menu im guessing.
mt2020 said:
Some demo units can make calls. People like to try them out in stores. Personally, I'd try to return it. Maybe you can flash a new firmware. Doubt makeup of hardware any different since it works. Never know though.
Click to expand...
Click to collapse
I'm able to get to the recovery screen and it seems to allows me to install updates from ADB; am I okay trying to use my pc/ODIN to flash tmobile firmware I have for this device?
Why not? You said if non of this works you're going to trade it in... As long as you don't brick it... And if you're on TMobile... Is it eligible for care plus? If so, you may be able to pass it off to them for repair
Great minds...i was doing that while you posted i guess. Was able to flash and reboot and it went back to the same locked down version that was there before. I guess this means that it's the bootloader/recovery that's locked down? Will try replacing that next.
Any idea where I might find the TWRP for this phone?
ankur079 said:
Great minds...i was doing that while you posted i guess. Was able to flash and reboot and it went back to the same locked down version that was there before. I guess this means that it's the bootloader/recovery that's locked down? Will try replacing that next.
Any idea where I might find the TWRP for this phone?
Click to expand...
Click to collapse
Not really sure, haven't rooted or used recovery software in a long time. Finally decided to let others be beta testers and just want a working phone. Go to Samsung Care plus web site, plug in your serial number or IMEI and it will tell you if it qualifies for coverage. If so, $8 month, first 3 or 4 months free, cancel at anytime. If covered, pay deductible and let them fix or replace, which in this case would most likely be replace. Past that, USA phones are pretty locked down if they weren't purchased unlocked. Yea, you can unlock a provider phone after a while on their plan, but boot loader still tough to Crack. I think that's what you just ran into.
mt2020 said:
Not really sure, haven't rooted or used recovery software in a long time. Finally decided to let others be beta testers and just want a working phone. Go to Samsung Care plus web site, plug in your serial number or IMEI and it will tell you if it qualifies for coverage. If so, $8 month, first 3 or 4 months free, cancel at anytime. If covered, pay deductible and let them fix or replace, which in this case would most likely be replace. Past that, USA phones are pretty locked down if they weren't purchased unlocked. Yea, you can unlock a provider phone after a while on their plan, but boot loader still tough to Crack. I think that's what you just ran into.
Click to expand...
Click to collapse
thanks, worth a try i suppose if nothing else pans out.