What is "OEM unlock" under Developer options? - T-Mobile Samsung Galaxy S7 Edge Questions & Answer

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

So you can do fastboot OEM unlock I believe. If you don't have that checked on a Nexus it wouldn't work. So I am guessing Samsung is following that route now.

It's to unlock the bootloader and not all phones will have it.
Sent from my SM-N920T using Tapatalk

Tidbits said:
So you can do fastboot OEM unlock I believe. If you don't have that checked on a Nexus it wouldn't work. So I am guessing Samsung is following that route now.
Click to expand...
Click to collapse
Samsung has to follow. It's a generalized security pick-up made by Google. Now on, every new smartphone/tablet that comes up, will have this. Without enabling it, there is no bootloader unlocking.

That's if the carrier or manufacturers allow bootloader unlocking I am going to add that.
Sent from my SM-G935T using Tapatalk

Tidbits said:
That's if the carrier or manufacturers allow bootloader unlocking I am going to add that.
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
Yeah you're right. I forget that not all carriers allow that. T-Mobile seems pretty chill about it.
Sent from my SM-N920T using Tapatalk

they they are. I believe back when HTC started to lock their bootloaders on their own T-Mobile went out and said "We leave it up to the manufacturers to decide if they want to lock the bootloaders or not, but we will not have them lock bootloaders by our choice(paraphrasing of course)." So far they have stuck to that. People say T-Mobile is the one locking the Xperia Z line, but I don't buy it simply because why is the Xperia so special that T-mobile would lock those with no way to unlock while all their other devices have all been unlockable or locked by the manufacturer(with some manufacturers have a way to unlock them like HTC). Doesn't make sense to me.

Tidbits said:
they they are. I believe back when HTC started to lock their bootloaders on their own T-Mobile went out and said "We leave it up to the manufacturers to decide if they want to lock the bootloaders or not, but we will not have them lock bootloaders by our choice(paraphrasing of course)." So far they have stuck to that. People say T-Mobile is the one locking the Xperia Z line, but I don't buy it simply because why is the Xperia so special that T-mobile would lock those with no way to unlock while all their other devices have all been unlockable or locked by the manufacturer(with some manufacturers have a way to unlock them like HTC). Doesn't make sense to me.
Click to expand...
Click to collapse
From what I understand, Xperia is owned by Sony, and knowing Sony, they're pretty "an*l" about their security features. Look at how long Sony PlayStation 3 took to be Jailbroken completely? Look at PS4 now and how it still not jailbroken yet.
I guess Sony has a contract with T-Mobile (not sure about this until someone correct me), which probably requires T-Mobile to lock it down since Xperia is also suppose to use the feature, "Remote Play", which can tie your phone and allow you to access your system via your phone over the internet.

Now that we have this option after the most recent update, does that mean root is soon to follow? This is what we have been waiting for this whole time, right? Or is there more to it?

DesignGrits said:
Now that we have this option after the most recent update, does that mean root is soon to follow? This is what we have been waiting for this whole time, right? Or is there more to it?
Click to expand...
Click to collapse
Don't hold your breath. They aren't just going to "give us root" anytime soon. Else, they wouldn't have worked so hard to keep it from us to begin with.

DesignGrits said:
Now that we have this option after the most recent update, does that mean root is soon to follow? This is what we have been waiting for this whole time, right? Or is there more to it?
Click to expand...
Click to collapse
This option has been there since day 1. The switch doesn't do anything

unknownbeing said:
This option has been there since day 1. The switch doesn't do anything
Click to expand...
Click to collapse
Gotcha, sorry for the post. I was told this was recently added. Thank you

Android OEM unlock (kill-switch)
Read the article in: android.wonderhowto.com or you can google OEM unlock
The OEM Unlock is basically an extra security precaution (Kill-Switch) designed by Android (not Samsung or nexus or whoever) to detour theives and help make it harder to root your phone, which will most likely brick your phone if you don't know what you are doing or know about this feature. This is all thanks to the great state (SARCASM) of California. Its a bill they passed: "August of 2014, the state of California signed SB-962; the so-called "Smartphone Kill Switch" law; and this had some major repercussions on Android."
"Enabling a single Android setting called "OEM unlocking" has the potential to prevent your device from falling victim to complete software failure, and it only takes a minute to turn this on. If you'd like to know why this option can cause your device to become bricked, I'll explain it all below."
This is just a paragraph out of the article for basic explanation. search for yourself if you want more information.

Hellbilly083 said:
Read the article in: android.wonderhowto.com or you can google OEM unlock
The OEM Unlock is basically an extra security precaution (Kill-Switch) designed by Android (not Samsung or nexus or whoever) to detour theives and help make it harder to root your phone, which will most likely brick your phone if you don't know what you are doing or know about this feature. This is all thanks to the great state (SARCASM) of California. Its a bill they passed: "August of 2014, the state of California signed SB-962; the so-called "Smartphone Kill Switch" law; and this had some major repercussions on Android."
"Enabling a single Android setting called "OEM unlocking" has the potential to prevent your device from falling victim to complete software failure, and it only takes a minute to turn this on. If you'd like to know why this option can cause your device to become bricked, I'll explain it all below."
This is just a paragraph out of the article for basic explanation. search for yourself if you want more information.
Click to expand...
Click to collapse
I think you are 100% wrong. Sorry. OEM unlock is used to unlock bootloaders on Nexus devices (and applicable phones with unlockable bootloaders). It has nothing to do with a kill switch. In fact, the article you quote even says that enabling this option can allow a hacker/thief to bypass Factory Reset Protection. The only (illogical) security gain it speaks of is being able to unlock the bootloader to directly flash a system image in case an OTA fails, which is complete nonsense anyways, as an unlocked bootloader only allows flashing unsigned code (you can always flash properly signed firmwares).

Hellbilly083 said:
Read the article in: android.wonderhowto.com or you can google OEM unlock
The OEM Unlock is basically an extra security precaution (Kill-Switch) designed by Android (not Samsung or nexus or whoever) to detour theives and help make it harder to root your phone, which will most likely brick your phone if you don't know what you are doing or know about this feature. This is all thanks to the great state (SARCASM) of California. Its a bill they passed: "August of 2014, the state of California signed SB-962; the so-called "Smartphone Kill Switch" law; and this had some major repercussions on Android."
"Enabling a single Android setting called "OEM unlocking" has the potential to prevent your device from falling victim to complete software failure, and it only takes a minute to turn this on. If you'd like to know why this option can cause your device to become bricked, I'll explain it all below."
This is just a paragraph out of the article for basic explanation. search for yourself if you want more information.
Click to expand...
Click to collapse
You are either a troll, a moron, or both.
Either way. You are 100% spreading false information.
OEM Unlock has to be turned on in order to be able to unlock the bootloader.
Sent from my SM-G935T using XDA-Developers mobile app

v8dreaming said:
You are either a troll, a moron, or both.
Either way. You are 100% spreading false information.
OEM Unlock has to be turned on in order to be able to unlock the bootloader.
Sent from my SM-G935T using XDA-Developers mobile app
Click to expand...
Click to collapse
The article is somewhat correct. It was designed to make unlocking the bootloader harder to do if you don't have access to the operating system. This is to prevent a backdoor in the kill switch system (you need to log on to the phone using your Google account after an 'unusual' wipe. With our this or would be possible to steal a phone and root it, killing the kill switch.
The article reads like a political bashing of the law though, and that's not very informative at all.
Sent from my SM-G935V using Tapatalk

Lmfaoooooo "Kill Switch"???
Sent from my Nexus 6P using XDA-Developers mobile app

Still wonder why Samsung left it dev options, got my hope up when I first got my s7
Sent from my SM-G935T using Tapatalk

It also has a hand in the Google security, if you reset your device and forget your Google password and change it before you log back into your device it soft brick's your device for 72 hours. Nothing you can do about it.
Sent from my SM-G935T using Tapatalk

chakra said:
It also has a hand in the Google security, if you reset your device and forget your Google password and change it before you log back into your device it soft brick's your device for 72 hours. Nothing you can do about it.
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
They changed the policy to 24 hours finally
Sent from my SM-G935T using XDA-Developers mobile app

Related

Got my Note 4 Today :)

I got my Note 4 Today! I love it already. Once I get my old phone official transferred to a family a member I think I'm going to root her. But first I wnated to know whats the process for rooting? And is it possible to unroot without signs its been rooted in case I need to send it for repairs? Thanks
My advice, start reading a little. I think I have seen your questions answered before?
gravatrax1 said:
I got my Note 4 Today! I love it already. Once I get my old phone official transferred to a family a member I think I'm going to root her. But first I wnated to know whats the process for rooting? And is it possible to unroot without signs its been rooted in case I need to send it for repairs? Thanks
Click to expand...
Click to collapse
There are many tutorial here on XDA about rooting, flashing etc.Read carefully and you'll be good to go.Also there is a section for question(Help&Troubleshooting), this is the general forum section, make sure where you post next.
Ah, cut him some slack, he's just excited he got a new phone!
But yes, you should do some reading before you do anything as drastic as modifying system files. There are tutorials and that will guide you through the process and a lot of threads discussing issues such as unrooting and warranty. Good luck!
As of right now, there is no known method to reset value of knox to default once rooted. Hopefully, someone will come up with a to root it without tripping knox or a way to reset the knox to default value. I also recently got my Note 4 and weighing in on whether I should root it or not.
I'm familiar with rooting and it's risks. I've rooted other devices. I just didn't want to dive headfirst into rooting this phone if I was not able to get it back to stock with no evidence of tampering. I have total equipment protection which covers any physical damage to the phone, and its come in handy in the past with devices that hav enot been rooted. I don't eve recall them doing anything at the store to check for modications to the software. Ultimately I plan on just rooting the device nad installing SU to get rid of bloatware and used some Xposed modules, no flashing of custom roms or anything.
gravatrax1 said:
I'm familiar with rooting and it's risks. I've rooted other devices. I just didn't want to dive headfirst into rooting this phone if I was not able to get it back to stock with no evidence of tampering. I have total equipment protection which covers any physical damage to the phone, and its come in handy in the past with devices that hav enot been rooted. I don't eve recall them doing anything at the store to check for modications to the software. Ultimately I plan on just rooting the device nad installing SU to get rid of bloatware and used some Xposed modules, no flashing of custom roms or anything.
Click to expand...
Click to collapse
rooting a note 4 is extremely silly. you lose half the functionality including a nice secure app store. and you lose it permanently with no possibility of getting it back along with the warranty.
zurkx said:
rooting a note 4 is extremely silly. you lose half the functionality including a nice secure app store. and you lose it permanently with no possibility of getting it back along with the warranty.
Click to expand...
Click to collapse
I've had mine 4 days and rooted it. Just becos....well, cos I always have! Nowhere did I readabout losing functionality app Store, Samsung's l assume?Care to expand on that further?? while I search it?
Gotta say I'm impressed with the note so far- -Spen rocks-- no more keyboard which for me is the best feature, still exploring.. Any hints on using the note 4 to it's fullest capablities would be greatly appreciated.
Sent from my SM-N910U using Tapatalk
you lose the knox secure app store and obviously all the apps like knox email and secure/business versions of common apps as well.
zurkx said:
obviously all the apps like knox email
Click to expand...
Click to collapse
and secure/business versions of common apps as well.
Click to expand...
Click to collapse
ok, thanks for your reply and heads up-my phone is pure indulgence, not for the business side of things. will keep in mind though, and look into this 'Knox' thing a bit more .
Sent from my SM-N910U using Tapatalk
But you don't lose access to the galaxy apps such as s write s health etc.? If that's so I really don't care. I will probably never even look at this so called Knox app store.
youre going to write off half your phone functionality permanently without even trying it out once ?
zurkx said:
youre going to write off half your phone functionality permanently without even trying it out once ?
Click to expand...
Click to collapse
mate it would be really nice. you could explain what this "half the functionality" we are losing, is-Samsung Apps still work,. Google search turned up only one post regarding ''losing functionality" and that was yours?? So I am a bit confused?
Sent from my SM-N910U using Tapatalk
dibb_nz said:
mate it would be really nice. you could explain what this "half the functionality" we are losing, is-Samsung Apps still work,. Google search turned up only one post regarding ''losing functionality" and that was yours?? So I am a bit confused?
Sent from my SM-N910U using Tapatalk
Click to expand...
Click to collapse
you lose a huge huge amount of functionality. too much to describe. an entire separate app store with only secure apps. a stripped down and fast encrypted personality (basically a second phone with no bloat). seamless switching. secure email and separate invisible device storage. secure calendars and notes. device tracking and logging. remote wipe and remote lock/unlock. there is literally a multi hundred page manual for all the functionality available.
have a look at just one screen of knox emm and you can see how much functionality you lose :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
zurkx said:
you lose a huge huge amount of functionality. too much to describe. an entire separate app store with only secure apps. a stripped down and fast encrypted personality (basically a second phone with no bloat). seamless switching. secure email and separate invisible device storage. secure calendars and notes. device tracking and logging. remote wipe and remote lock/unlock. there is literally a multi hundred page manual for all the functionality available.
have a look at just one screen of knox emm and you can see how much functionality you lose :
Click to expand...
Click to collapse
Off Topic: Is that a 4K screen? Damn that DPI must be pretty low I couldn't read without my glasses
Basically, yes, you lose Knox. Which is something that no app can replace right now. Knox is what iCloud Security is for iPhones. If somebody stoles your phone, you can track it, or delete everything and render it unusable to the thieft. Also, with knox and reactivation lock enabled, no one can root the phone and delete knox as it prevents to flash anything via Odin. It makes your phone really safe, but it's a worth losing.
I've rooted my phone since the first day I bought it. I don't have warranty as I've imported the phone from USA, so Samsung Argentina doesn't cover it. It's totally worth. If you use Kitkat, Xposed is the best addition for your rooted device. If you're in Lollipop, you can always flash custom themes/mods via Recovery. Root (almost) always is a benefit. I recommend you to enjoy your phone as is, and when you're prepared (or bored, whatever you want to call it), go ahead and root it. Congratulations and cheers!
zurkx said:
you lose a huge huge amount of functionality. too much to describe. an entire separate app store with only secure apps. a stripped down and fast encrypted personality (basically a second phone with no bloat). seamless switching. secure email and separate invisible device storage. secure calendars and notes. device tracking and logging. remote wipe and remote lock/unlock. there is literally a multi hundred page manual for all the functionality available.
have a look at just one screen of knox emm and you can see how much functionality you lose :
Click to expand...
Click to collapse
Thankyou, I've had abitof a read up on Knox, I guess,.if this was a company phone, or I worked in IT then this ' feature would be the' bees knees'. fortunately its purely for pleasure!!
galaxynote2 said:
Off Topic: Is that a 4K screen? Damn that DPI must be pretty low I couldn't read without my glasses
Basically, yes, you lose Knox. Which is something that no app can replace right now. Knox is what iCloud Security is for iPhones. If somebody stoles your phone, you can track it, or delete everything and render it unusable to the thieft. Also, with knox and reactivation lock enabled, no one can root the phone and delete knox as it prevents to flash anything via Odin. It makes your phone really safe, but it's a worth losing.
I've rooted my phone since the first day I bought it. I don't have warranty as I've imported the phone from USA, so Samsung Argentina doesn't cover it. It's totally worth. If you use Kitkat, Xposed is the best addition for your rooted device. If you're in Lollipop, you can always flash custom themes/mods via Recovery. Root (almost) always is a benefit. I recommend you to enjoy your phone as is, and when you're prepared (or bored, whatever you want to call it), go ahead and root it. Congratulations and cheers!
Click to expand...
Click to collapse
nice, thanks for the info chap, I'm absolutely loving this thing. Root was done in first few hours, used CF Root and Odin all good.
Hope OP has enough info now to make a decision,
Sent from my SM-N910U using Tapatalk
I can see how Knox would be detrimental to someone in a business or tech related job where security is upmost importance however I am not that person so it's just something that' snot useful to me. I think for the time being I'll just keep the phone as is but eventually I will probably root it. I'm only a few days in and I already miss some of my apps and Xposed modules that I used one my One from when it was rooted.
Personally I wouldn't bother rooting. Losing a warranty isn't worth it considering the minimal benefits of rooting.
You'll soon learn to live without the limited additions that exposed offers, and you'll not miss the performance hit exposed offers the Note 4 which is slow enough already.
There is a thread that suggests alternatives to rooting.
If you're anything like me, you'll be onto another phone soon enough and no one will want to buy a phone with no warranty that someone's been trashing with Root.
Jonathan-H said:
Personally I wouldn't bother rooting. Losing a warranty isn't worth it considering the minimal benefits of rooting.
You'll soon learn to live without the limited additions that exposed offers, and you'll not miss the performance hit exposed offers the Note 4 which is slow enough already.
There is a thread that suggests alternatives to rooting.
If you're anything like me, you'll be onto another phone soon enough and no one will want to buy a phone with no warranty that someone's been trashing with Root.
Click to expand...
Click to collapse
Not me I wen the Sprint easy pay route. I'll have this phone for the next two years. I think I'll wait till OTA of Lollipop comes out then wait for a stable root and do it then.

Does HTC still provide bootloader unlocking?

The last time I had an HTC phone, HTC provided a bootloader unlocking tool for phones bought on contract through carriers. Is this still the case? I'd probably end up having a Verizon model.
http://forum.xda-developers.com/htc-10/how-to/unlockable-bootloader-t3357220
The GSM version will be unlockable. Unknown if Verizon will screw that up or not.
Responding to my question, Jeff Gordon - Senior Global Online Communications Manager at HTC Corp said:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
God dam it. What is this bs with unlockable bootloader lately. This was my #1 choice. Now I guess I'll have to wait for the next nexus.
Sent from my Nexus 5 using XDA-Developers mobile app
@nitramus I think you have misread. For the 10 if you buy direct from HTC, it looks like the bootloader will be unlocked out of the box. If you buy from a service provider, it may be locked, but can be unlocked via the HTC website.
Might be because English is not my primary language but when I read this what I get is that it can not be unlocked.
nitramus said:
Might be because English is not my primary language but when I read this what I get is that it can not be unlocked.
Click to expand...
Click to collapse
Yeah, you're not reading it correctly. HTC is still offering dev unlocking. You will be able to unlock it.
Sweet, thanks!
Awesome news, I hope verizon doesn't screw this up...
Sent from my SM-G930V using XDA-Developers mobile app
gleggie said:
Awesome news, I hope verizon doesn't screw this up...
Sent from my SM-G930V using XDA-Developers mobile app
Click to expand...
Click to collapse
Verizon branded devices are NOT unlockable through HTC Dev. Verizon requests that HTC block their branded devices from that service. Verizon users must rely on Java card or software exploits such as sunshine to be updated to work with the 10.
Behold_this said:
Verizon branded devices are NOT unlockable through HTC Dev. Verizon requests that HTC block their branded devices from that service. Verizon users must rely on Java card or software exploits such as sunshine to be updated to work with the 10.
Click to expand...
Click to collapse
Thanks for the info, would a carrier unlocked HTC 10 work on Verizon? I've been hearing mixed information
Sent from my SM-G930V using XDA-Developers mobile app
gleggie said:
Thanks for the info, would a carrier unlocked HTC 10 work on Verizon? I've been hearing mixed information
Sent from my SM-G930V using XDA-Developers mobile app
Click to expand...
Click to collapse
That's kind of tough to answer. First, according to the specs on HTC's page it does have the correct LTE and CDMA radios to work on Verizon. That being said, you would still have to get the device activated on Verizon's Network and that can be difficult with devices Verizon does not carry.
Second, responses from official HTC employees (e.g. Mo Versi and others) state that you will need to purchase the Verizon branded model, once available, to get full support. Seems to be intentionally vague. The answer to your question: it may well work and it may well not, you have to roll the dice to find out.
Behold_this said:
That's kind of tough to answer. First, according to the specs on HTC's page it does have the correct LTE and CDMA radios to work on Verizon. That being said, you would still have to get the device activated on Verizon's Network and that can be difficult with devices Verizon does not carry.
Second, responses from official HTC employees (e.g. Mo Versi and others) state that you will need to purchase the Verizon branded model, once available, to get full support. Seems to be intentionally vague. The answer to your question: it may well work and it may well not, you have to roll the dice to find out.
Click to expand...
Click to collapse
I'm wondering if someone will figure out how to trick Verizon into thinking the unlocked version is one of its own.
Ajfink said:
I'm wondering if someone will figure out how to trick Verizon into thinking the unlocked version is one of its own.
Click to expand...
Click to collapse
You'd need to change the device CID to match Verizon's to trick them. For that, s-off is required, bootloader unlock will not give required access to change that.

Unlocked Bootloader

I am not all that familiar with unlocked bootloaders but after skimming some of the posts on the Moto Z Force I am seeing a lot of discussion about, I replied to one thread decided perhaps I should start a new.
The bootloader is able to be unlocked from the settings menu.
First you must go to settings then about phone. Go to build number and tap it 7 times. This will enable developer options.
Again go to the settings menu, go to developer options and there is a toggle for OEM unlocking.
Hope this helps as I am new to xda(new member, long time reader)
LeeMullinsII said:
I am not all that familiar with unlocked bootloaders but after skimming some of the posts on the Moto Z Force I am seeing a lot of discussion about, I replied to one thread decided perhaps I should start a new.
The bootloader is able to be unlocked from the settings menu.
First you must go to settings then about phone. Go to build number and tap it 7 times. This will enable developer options.
Again go to the settings menu, go to developer options and there is a toggle for OEM unlocking.
Hope this helps as I am new to xda(new member, long time reader)
Click to expand...
Click to collapse
Dude you rock! But will this allow root? Using known methods like ping-pong or towel root? I've been with Samsung for 6 years, so this Moto z force thing is still new to me. And I'm just starting to dig through the threads on this.
I just made the switch from Samsung myself so I am not entirely sure. I happened to stumble upon that accidentally and saw a few questions about unlocking a bootloader. Now I am not sure if it makes a difference but my device is not under contract as I paid full price and activated on prepaid.
This will not unlock your bootloader
Sent from my XT1650 using Tapatalk
This will not unlock your bootloader. This will not allow root. There is almost zero chance of this phone ever having its bootloader able to be unlocked and you can call Verizon at (800) 922-0204 to thank them for it. They are tyrants and I will never give them a dollar.
Yeah its the same for me, it will allow you to unlock the bootloader, but it will void the warranty so I haven't done it yet but I will later on. Hopefully it works! It make it really easy to root with Verizon.
Please read everything in this thread. Thank you.
Braydenc1997 said:
Yeah its the same for me, it will allow you to unlock the bootloader, but it will void the warranty so I haven't done it yet but I will later on. Hopefully it works! It make it really easy to root with Verizon.
Click to expand...
Click to collapse
This is NOT an option to unlock your bootloader...sorry
Sent from my XT1650 using Tapatalk
Yeah, it doesn't work that way with Big Red.
Sent from my XT1575 using XDA-Developers mobile app
Braydenc1997 said:
Yeah its the same for me, it will allow you to unlock the bootloader, but it will void the warranty so I haven't done it yet but I will later on. Hopefully it works! It make it really easy to root with Verizon.
Click to expand...
Click to collapse
Checking this box will NOT unlock the bootloader. Anyone that has had a phone where you CAN in fact unlock the bootloader knows this.
Would quadrooter exploits work on this phone? This phone is running the snapdragon chip set and has the following vulnerabilities:
CVE-2016-2503, CVE-2016-2504 and CVE-2016-5204
Y'all should be able to check your phones as well using the quadrooter scanner app from play s.
micmatt said:
Would quadrooter exploits work on this phone? This phone is running the snapdragon chip set and has the following vulnerabilities:
CVE-2016-2503, CVE-2016-2504 and CVE-2016-5204
Y'all should be able to check your phones as well using the quadrooter scanner app from play s.
Click to expand...
Click to collapse
It would take an experienced dev to turn those exploits into a root avenue for us. I doubt that person will show up for this device.
They may very well show up. This is a new phone and somewhat a power house. A lot of people leaving Samsung and coming to this device. I just left the gs6. So I am still holding up hope. It's still new and may take a little time.
Sent from my XT1650 using Tapatalk
This will be one of the few Verizon phones which will get the Dev love it needs to be unlocked and rooted.Being now in my thirties and running Arch Linux for years I really don't care anymore,..there isn't a need for me ..I get my Rock's off on my box and keep my phone working .
I can clarify, my Moto Z Force does have those three vulnerabilities.
These vulnerabilities are global for Android MM, so perhaps someone, somewhere can use the exploit to gain root on Android - we'd be able to use that method on our phones. Here's to being hopeful!

Inquiry to join up with fellow Moto Z / Z Force owners (Verizon) to work on root.

Hello all! Just Inquiring to the geniuses that float around on this site about working to help bring root to this device. I have all the standard things (wired connection to PC, adb access, etc.). Just wondering if anyone needed any extra help or if they need someone to test methods out.
Before I get flamed, I DO know the risks of running commands incorrectly, and running them not knowing if it will work, not work or brick the device.
Currently looking into the mod interface as well. (Might be useful)
unless I understand incorrectly the biggest issue isn't root itself but the needed boot.img that requires an unlocked bootloader because if Android 6.
I'm going to inquire with Moto and see if they would be so gracious enough to unlock my bootloader since the option is there in dev settings. I know this might be a lost cause but maybe if I can get that done, and upload any stock images for people to tinker around with, do you believe it would help the dev community find an exploit?
WestTexasCoder said:
I'm going to inquire with Moto and see if they would be so gracious enough to unlock my bootloader since the option is there in dev settings. I know this might be a lost cause but maybe if I can get that done, and upload any stock images for people to tinker around with, do you believe it would help the dev community find an exploit?
Click to expand...
Click to collapse
Will not happen. Verizon won't let them. Just wait for the unlocked version to come out and a dev to get that.
Question: when the unlocked version comes out, that won't matter to us stuck using big red's version, will it?
Ace2cool said:
Question: when the unlocked version comes out, that won't matter to us stuck using big red's version, will it?
Click to expand...
Click to collapse
Dont know. It could or it might not. It could lead to the finding of an exploit that we can use. When that comes out we have better odds. Heck we might just be able to do a simple flash and flash some verizon stuff....Prob not knowing verizon but it could happen. My advice is not to update until we see how the unlocked versions development is going. But as of right now no one is working on this phone.
Good odds tho. Unlocked comes out and people start working on it to unlock even more stuff for more mod development we might get lucky and get some trickle down exploits that will free us.
But knowing verizon i bet they have something in the works to force people to update. Because they are shady like that. Oh here is a new moto mod. And its only $20 and will add like wireless charging and a second sd card slot....but it wont work unless you use this software update. And oh by the way it fixes that exploit. I could see them doing something like that. Using a cheap mod that would be awesome like a mod that gives wireless charging and a second micro sd card slot to force us to update to use it and patch a exploit.
Great phone only phone i have ever had that i did not require root and a bootloader unlock. Hell its the only phone i will use stock...Well i use nova launcher but not to speed it up. Just to block the verizon bloatware from my app list. God i cant wait for them to load down the phones with all the yahoo bloat now. My god help us next year.
yahoo maps
yahoo messenger
yahoo news
yahoo search
Just to name a few of the crap they will load down. Get a 32gig phone. 5gigs of it will be verizon and yahoo apps you will never use that cant be uninstalled.
If our project was only gaining root access, then the Verizon Moto Z / Z Force currently has vulnerabilities listed under quadrooter.
http://blog.checkpoint.com/2016/08/07/quadrooter/
The international version does come out soon and hopefully we can get some progress on the bootloader!
As far as gaining root access, if I knew how to code we would already have it since every Moto Z / Z Force has 3 of the quadrooter vulnerabilities. If you want screenshots of which ones and their details let me know :3
WestTexasCoder said:
As far as gaining root access, if I knew how to code we would already have it since every Moto Z / Z Force has 3 of the quadrooter vulnerabilities.
Click to expand...
Click to collapse
That's a bold statement...
Do you have a development background? I wasn't sure from your first post and your last one.
Not well enough to attempt any of these vulnerabilities on my own. Each of the three vulnerabilities allows users to access root privilege on the device without the device being rooted.
I'll put the three vulnerabilities here.
1. https://www.codeaurora.org/invalid-path-check-ashmem-memory-file-cve-2016-5340.
2 and 3. https://www.codeaurora.org/use-afte...tions-kgsl-module-cve-2016-2504-cve-2016-2503
2 and 3 both are very similar, hence the reason for one URL.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Been messing around with my development kit. Good chance of a bootloader unlock and root with this. Bad news is its going to be over $125 for you to get the dev kit. But I think I might be on to something. Won't go into details on here because we all know Verizon watches for stuff like this.
Still gathering more info before I test anything since this is my daily driver. I'll start work when I get my back up phone.
Method will require a dev kit and a PC. So it's not going to be something you can just plug into your PC
bignazpwns said:
Been messing around with my development kit. Good chance of a bootloader unlock and root with this. Bad news is its going to be over $125 for you to get the dev kit. But I think I might be on to something. Won't go into details on here because we all know Verizon watches for stuff like this.
Still gathering more info before I test anything since this is my daily driver. I'll start work when I get my back up phone.
Method will require a dev kit and a PC. So it's not going to be something you can just plug into your PC
Click to expand...
Click to collapse
This sounds very promising! I've been doing a bit of research and I have a much broader understanding of how gaining root access is accomplished, but not necessarily the bootloader.
I can save up some money and grab a dev kit as well if you want another set of hands on this.
If you need my email let me know, but i've been messing around with some of the exploits and once i get back home (hooray for IT job) i'm going to try out the system-less root, then go from there.
Good findings, and I believe you're on the right track! I read up on what the mods can access and control on the Android system and I'm actually impressed by what it can access and do. Heck, maybe we can even get a script going to utilize most moto mods to allow access to certain areas that we need, aside from the extra battery. I doubt that one will allow any kind of unintended access to areas of the phone. :silly:
If I can grab any kind of root access, would images be helpful to the much smarter people here?
WestTexasCoder said:
This sounds very promising! I've been doing a bit of research and I have a much broader understanding of how gaining root access is accomplished, but not necessarily the bootloader.
I can save up some money and grab a dev kit as well if you want another set of hands on this.
If you need my email let me know, but i've been messing around with some of the exploits and once i get back home (hooray for IT job) i'm going to try out the system-less root, then go from there.
Good findings, and I believe you're on the right track! I read up on what the mods can access and control on the Android system and I'm actually impressed by what it can access and do. Heck, maybe we can even get a script going to utilize most moto mods to allow access to certain areas that we need, aside from the extra battery. I doubt that one will allow any kind of unintended access to areas of the phone. :silly:
If I can grab any kind of root access, would images be helpful to the much smarter people here?
Click to expand...
Click to collapse
I figured the system for the mods would be the easiest way in. Working on a mod with my dev kit after that I'm going to start messing around more with seeing what I can do. There has to be something in here. First phone to use them first version of moto mods. There is somthing
Good chance root may happen tonight. Meet more work on it. But it won't be something everyone can do. Will require aoto mod dev kit and a fair amount of work. But if I can get it working tonight there seems to be some hope.
in4updates. Great work and keep it up! Only reason I want root is for new emojis haha. I will most likely unroot once 7.0 releases (assuming we get root before we get 7.0)
bignazpwns said:
Good chance root may happen tonight. Meet more work on it. But it won't be something everyone can do. Will require aoto mod dev kit and a fair amount of work. But if I can get it working tonight there seems to be some hope.
Click to expand...
Click to collapse
Please don't break my heart.
Me either.. just got moto z force today ..Will speaker ,projector,battery wireless mod ..and a couple backs...But boy root and Roms would be a bonus...
Sent from my XT1650 using Tapatalk
Nevermind project scrapped.
bignazpwns said:
The method i used 99% of the people here will not be able to do. Requires a moto mod dev kit and some other stuff. I'll work on getting the getting the bootloader from the non Verizon version on it when i get it. As of right now im back to working on my Moto mod so it will be a week or two before i go back to this.
Progress will be very slow. This is my only phone i sold my 6p so i cant do anything to risky on this. I got some ideas on working out a cheaper version. Drop the price of hardware needed from $200+ to $80.
Click to expand...
Click to collapse
this photo looks shopped, poorly as well
bignazpwns said:
Been messing around with my development kit. Good chance of a bootloader unlock and root with this. Bad news is its going to be over $125 for you to get the dev kit. But I think I might be on to something. Won't go into details on here because we all know Verizon watches for stuff like this.
Still gathering more info before I test anything since this is my daily driver. I'll start work when I get my back up phone.
Method will require a dev kit and a PC. So it's not going to be something you can just plug into your PC
Click to expand...
Click to collapse
Where can I get my hands on this kit?
bignazpwns said:
Nevermind project scrapped.
Click to expand...
Click to collapse
lol why? because you got caught?

True Verizon Pixel 2 XL Unlocked Bootloader (Not Google Ver) Refurb Devices Look Here

This might be a long shot for anyone else but I managed to allow the verizon version of the pixel 2 xl to let me unlock the bootloader. I can try and explain what i did to get work. I am working on the pictures and the post for you guys. Bare with me as I was pretty excited.
EDIT: I received a direct verizon replacement as you can see.
Im still dumb founded. Phone came with opd3.170816.012. Which is the verizon flash. I did muliple things try to flash new images, unlock, hidden keys and so forth this whole time no sim card and no wifi and with wifi. I tried changing oem unlock multiple times and going in and out of stock recovery and doing multiple random steps not getting nowhere, then finally booted up and decided to say f**k it. I let it connect to wifi and let it update to newest version march. I let it reboot and checked dev settings for the heck of if and to turn on adb. Boom! OEM unlocking was highlighted. I rebooted and checked it again still highlighted. Then went to recovery and fastboot flashing unlock along with critical.
The wire and the line are blocking the imei number.
EDIT 2: The Last two pics. One from verizon website is the pixel on the left in the last pixel pic side by side and the one on the right on the website is the one on the right. Obviously. The picture of the two side by side was taken with the third pixel 2 xl locked from verizon.
EDIT #3: Two more pictures showing that last four of the imei on http://www.imeipro.info/check_lg.html and the last four on my phone (wifes phone) asking for root request.
EDIT #4: Seems the two different phones I am showing is confusing people. So here is a better side by side.
Her phone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My phone
Her phone
My phone
Then here is her phone with the same last four on the imei
It's an unlocked one. Verizon replacements from Verizon stores are Google unlocked ones. Thanks for getting hopes up for the billionth time lol.
---------- Post added at 05:32 AM ---------- Previous post was at 05:01 AM ----------
What exactly did you do. Step by step
---------- Post added at 05:53 AM ---------- Previous post was at 05:32 AM ----------
Never mind. You couldn't toggle oem unlock until you connected to the internet.
GokuSSJgod said:
It's an unlocked one. Verizon replacements from Verizon stores are Google unlocked ones. Thanks for getting hopes up for the billionth time lol.
---------- Post added at 05:32 AM ---------- Previous post was at 05:01 AM ----------
What exactly did you do. Step by step
---------- Post added at 05:53 AM ---------- Previous post was at 05:32 AM ----------
Never mind. You couldn't toggle oem unlock until you connected to the internet.
Click to expand...
Click to collapse
I was connected to the internet and still would allow the unlock. I tried it fresh out the box on opd3 Sept version on WiFi and wouldn't allow toggle in OEM unlock. See the screen shot. Did a bunch of stuff trying to mess around and unlock but all failed. Eventually after factory restore. Even tho there was no account or sim installed. I took the March 5 update and rebooted it and it let me toggle the OEM unlock. Then rebooted to check if it still was toggled. Then went to bootloader to unlock. Called Google not Verizon to verify this wasn't a refurbished phone and was a Verizon phone. He confirmed it was a new Verizon. He said most refurbs are on some image other than stock out the box anyways. So either he was wrong and the actual Verizon image in the phone doesn't mean anything?
Sent from my Pixel 2 XL using Tapatalk
Edit: the last pic is a sticker on the back of the phone out of the replacement box. Not a new style box. Just a phone was in there.
Go here: http://www.imeipro.info/check_lg.html
Enter your IMEI and tell us the model number.
I was going to suggest that. It'll say something like goo or vzw
bryantjopplin said:
I was connected to the internet and still would allow the unlock. I tried it fresh out the box on opd3 Sept version on WiFi and wouldn't allow toggle in OEM unlock. See the screen shot. Did a bunch of stuff trying to mess around and unlock but all failed. Eventually after factory restore. Even tho there was no account or sim installed. I took the March 5 update and rebooted it and it let me toggle the OEM unlock. Then rebooted to check if it still was toggled. Then went to bootloader to unlock. Called Google not Verizon to verify this wasn't a refurbished phone and was a Verizon phone. He confirmed it was a new Verizon. He said most refurbs are on some image other than stock out the box anyways. So either he was wrong and the actual Verizon image in the phone doesn't mean anything?
Sent from my Pixel 2 XL using Tapatalk
Edit: the last pic is a sticker on the back of the phone out of the replacement box. Not a new style box. Just a phone was in there.
Click to expand...
Click to collapse
What's the bunch of stuff you tried
slogar25 said:
What's the bunch of stuff you tried
Click to expand...
Click to collapse
Going through even hidden menu codes multiple times, unlocking, flashing factory images, fastboot format userdata. Basically nothing worked tho. Lol
Sent from my Pixel 2 XL using Tapatalk
bryantjopplin said:
Going through even hidden menu codes multiple times, unlocking, flashing factory images, fastboot format userdata. Basically nothing worked tho. Lol
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
So what is the model number from the IMEI checker?
Scott said:
So what is the model number from the IMEI checker?
Click to expand...
Click to collapse
So yours shows a model number?
Sent from my Pixel 2 XL using Tapatalk
Wasteof time again. I'm done checking these forums on here.
Please provide a detailed Step by Step instruction
Sent from my Pixel 2 XL using XDA-Developers Legacy app
ralph97 said:
Please provide a detailed Step by Step instruction
Sent from my Pixel 2 XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
Is yours still on the opd3 Sept image from Verizon? If not I don't know if that works. I have only done it on that.
Sent from my Pixel 2 XL using Tapatalk
GokuSSJgod said:
Wasteof time again. I'm done checking these forums on here.
Click to expand...
Click to collapse
Waste of time posting a negative and non informative sentence.
Sent from my Pixel 2 XL using Tapatalk
Here's all three if you're still sceptical
Sent from my Pixel 2 XL using Tapatalk
bryantjopplin said:
Here's all three if you're still scepticalView attachment 4448432
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Middle is the only Google unlocked version. Left is locked march Verizon version. Right is unlocked Verizon version.
Sent from my Pixel 2 XL using Tapatalk
So basically, what you did was update the phone without the sim card in it and it let you enable oem unlocking?
Yes, i am sure thats all that was needed. None of the other stuff shown any output or i just errors saying device wasnt unlocked. I am trying to provide more information in OP to show. But i believe the key is to be on opd3 sept patch with no sim card or activation. But i am unsure of the activation part. I did not activate it until now 8:15 pm
MColbath said:
So basically, what you did was update the phone without the sim card in it and it let you enable oem unlocking?
Click to expand...
Click to collapse
MColbath said:
So basically, what you did was update the phone without the sim card in it and it let you enable oem unlocking?
Click to expand...
Click to collapse
That happened with one of the replacements I received. Unfortunately that phone had a scratched back panel and I sent it back. The subsequent device I received did not allow me to do the same thing. For the first device I did this:
1) Turned on the phone without sim. OEM unlocking was grayed out.
2) Connected to WiFi still with no sim. OEM unlocking still grayed out.
3) Took the available update which I think was to 8.1. Still no sim. OEM locking no longer grayed out.
4) Unlocked bootloader.
mlin said:
That happened with one of the replacements I received. Unfortunately that phone had a scratched back panel and I sent it back. The subsequent device I received did not allow me to do the same thing. For the first device I did this:
1) Turned on the phone without sim. OEM unlocking was grayed out.
2) Connected to WiFi still with no sim. OEM unlocking still grayed out.
3) Took the available update which I think was to 8.1. Still no sim. OEM locking no longer grayed out.
4) Unlocked bootloader.
Click to expand...
Click to collapse
I'm wondering if it's an activation thing. If they have ever been activated on vzw and used they won't unlock. But a new one that hasn't been can? Verizon versions that is
Sent from my Pixel 2 XL using Tapatalk
bryantjopplin said:
I'm wondering if it's an activation thing. If they have ever been activated on vzw and used they won't unlock. But a new one that hasn't been can? Verizon versions that is
Click to expand...
Click to collapse
That's pretty much what it is. If you perform the first time boot without a sim card you should be able to OEM unlock, if the sim card is in you won't be able to.

Categories

Resources