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.
Related
Not sure if this is where this goes but this worked for me on 3 Nexus S 4G's today..
All of them on different accounts. One is flashed to MetroPCS and still get's Jellybean love!
Remember it will not work right away, just when your sick of doing it BAM..
One phone i tried for 2 hours and nothing..Then just before my friend left my house i tried once more and it worked..
If this does not work for you,well, at least i gave you something to do while you were bored!
But i swear it worked on 3 phones today!
================================================== =============================
Open the Settings application.
Select Apps.
Select the All drawer, and select Google Service Frameworks.
First, Force Stop the application, then Clear Data.
Now that the Google Service Frameworks are reset, you may check for an update, by selecting About Phone in Settings, and select System Update.
**The last update check should be garbled. Around 1969.**
--------------->If this did not work, try these steps several times. This is important, IT MAY TAKE SEVERAL TRIES BEFORE A RESULT.
Give a thanks if it works for you and reply back with results..
Enjoy
** Not sure about this breaking push notification on apps?
First I heard of this. I guess try at your own risk but my wife's Nexus S 4G seems to be working great after using this method.
## Maybe try to back up apps that use push notifications with Titanium Backup and reinstall after if u have any issues.
Just a thought not sure if that will help!
TONYSALEM78 said:
Not sure if this is where this goes but this worked for me on 3 Nexus S 4G's today..
All of them on different accounts. One is flashed to MetroPCS and still get's Jellybean love!
Remember it will not work right away, just when your sick of doing it BAM..
One phone i tried for 2 hours and nothing..Then just before my friend left my house i tried once more and it worked..
If this does not work for you,well, at least i gave you something to do while you were bored!
But i swear it worked on 3 phones today!
================================================== =============================
Open the Settings application.
Select Apps.
Select the All drawer, and select Google Service Frameworks.
First, Force Stop the application, then Clear Data.
Now that the Google Service Frameworks are reset, you may check for an update, by selecting About Phone in Settings, and select System Update.
**The last update check should be garbled. Around 1969.**
--------------->If this did not work, try these steps several times. This is important, IT MAY TAKE SEVERAL TRIES BEFORE A RESULT.
Give a thanks if it works for you and reply back with results..
Enjoy
Click to expand...
Click to collapse
I thought this broke the push notification on apps that use push, no?
I decided that I could resolve the push if need be and went ahead and tried this again (did it previously on other updates). Tried about five times, walked away for about 15 minutes. Tried again and it worked. Update is downloading now.
Cool. Glad its working for people! Enjoy
Sent from my SPH-D700 using xda premium
Thanks man it works!
Sent from my Nexus 7 using xda app-developers app
So, I just switched to the NS4G from my ET4G because it's been having some hardware issues (Not really relevant for this, but figured I would introduce myself to the Nexus S community this way haha...)
This is what worked for me:
*Force Stop Google Services Framework
*Clear Data On Google Services Framework
*Wait about 5 minutes
*Checked for updates
I did it 1 time, and it worked for me. Not too sure if it'll work that way for everyone, but I believe it's def worth trying.
didnt force stop at all but clear framework and checked now, didnt work.
Read your post, cleared data,
waited 5 mins.
checked and now update.
Thanks file size 121.6mb
ok, so this means only one thing could be possible...Sprint lied to us. they told us the update would start the 6th, but it didn't start until yesterday. I can't count how many posts I saw from people who tried this and it didn't work...now, miraculously, it starts working when we know it's out?!?!?!?!
Look at the facts, people!! Sprint lied to us and the update did not start the 6th like they said. if it had, this would have worked on sept 6th, and would not just magically start working on sept 10th!
This worked. I'm on jellybean now. It took over 26 attempts. No joke. But so worth it.
{
"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"
}
Sent from my Nexus S 4G using Tapatalk 2
Sprint didn't lie they said this is a two part roll out starting the 6th the galaxy nexus got its first then us look at the facts they still have a few days before some people will get it and they didn't even have to bring it out for our phone oh and download supersu and flash it thru recovery for root and air kernel r1 works with this
Sent from my Nexus S 4G using xda app-developers app
Flashable .zip
http://forum.xda-developers.com/showthread.php?p=31430372#post31430372
So question for the New Jelly Bean update... Teamviewer came out with there Quicksuppprt app. It says it only works on Stock firmware, Non modded. It works on Stock ICS but doesnt work on Stock JellyBean. Is any one else having this problem. Im not sure if its because i flashed Jellybean via ODIN yesterday since i didnt want to wait for the OTA to get pushed or is it just the fact that it doesnt work on JellyBean NS4g's yet
Also im rooted, forgot to try before i rooted my device :/
Can anyone who waited for the OTA to get pushed to there phone confirm or not if they are able to Download and install "TeamViewer QuickSupport" to there Jellybean NS4g device
Thanks and much appreciated
shrekdaklown said:
Sprint didn't lie they said this is a two part roll out starting the 6th the galaxy nexus got its first then us look at the facts they still have a few days before some people will get it and they didn't even have to bring it out for our phone oh and download supersu and flash it thru recovery for root and air kernel r1 works with this
Sent from my Nexus S 4G using xda app-developers app
Click to expand...
Click to collapse
are you kidding??
1. they never said it's a two-part update. they said updates would start the 6th...nothing about two parts. even the reps I spoke with said I should have had it already!! The funny thing is, not even two hours after I complained (and openly admitted to having looked on XDA for it and it wasn't out yet) people started getting the OTA. That's pretty coincidental, no?
2. they owed us an update. we are nexus owners. we get every update until the hardware can't run the firmware. If they don't like that, they can choose to stop selling the nexus line...there's the door. If it's a phone that's only on one carrier and the carrier doesn't update, google should step in and release the factory image immediately. Now don't take what I'm saying the wrong way. I don't mean they LEGALLY owe us an update. I mean since we own a development device, they would be pretty stupid to turn their backs on us....many of us have given google a percentage of the code used in final release versions of android. If they turn their backs on those people, they will be pretty screwed. They use quite a few features from roms that were here before google ever had the idea to do that. For example, swipe to clear notifications...that came from CM team. It sure as HELL wasn't google's baby, that's for sure!! That's why I say they owe us an update. Whether any one of us has personally contributed code or not, we have still contributed to the android project by testing the code that the developers here contributed to android.
if they are releasing a rom for two phones it wont be a single wave the galaxy nexus owners got it first because they bought the newer phones and when we bought our nexus s's they never said they would update it forever we are lucky we got it they could have been like nope you have to be a galaxy nexus and honestly we are lucky because most companys would have made us upgrade to get it or make our own i was right beside you waiting for the update and as soon as i had the image files on here i odin'ed them to my phone most sprint reps have no idea whats going on with roms and such but i know i count myself lucky to have a phone like this and not be stuck like i was with my evo shift alot of companys owe us for bettering there product but how many actually pay
wifi
Tried this using 3g or 4g all day and nothing, then tried with wifi and if worked like a charm the 1st time i tried, dont know why it worked out this way, but to those for which this method is not working when connected to 3g or 4g try using this method while connected to wifi, it might just work as it did for me.
Doing the checkin CMD does nothing but the same thing as going through the settings about phone and clicking system update..
Haven't tried this method yet.. May try soon..
Hopefully that OTA hits my way some time soon..
I forgot to add that I was on Wifi also...
Sent from my SPH-D700 using xda premium
GrimReaper24 said:
Doing the checkin CMD does nothing but the same thing as going through the settings about phone and clicking system update..
Haven't tried this method yet.. May try soon..
Hopefully that OTA hits my way some time soon..
Click to expand...
Click to collapse
Make sure your on wifi and you remove or delete Google services framework data in settings...apps. it took me over 26 times before it worked. I'm happily running stock jellybean
Sent from my Nexus S 4G using Tapatalk 2
hp420 said:
are you kidding??
1. they never said it's a two-part update. they said updates would start the 6th...nothing about two parts. even the reps I spoke with said I should have had it already!! The funny thing is, not even two hours after I complained (and openly admitted to having looked on XDA for it and it wasn't out yet) people started getting the OTA. That's pretty coincidental, no?
2. they owed us an update. we are nexus owners. we get every update until the hardware can't run the firmware. If they don't like that, they can choose to stop selling the nexus line...there's the door. If it's a phone that's only on one carrier and the carrier doesn't update, google should step in and release the factory image immediately. Now don't take what I'm saying the wrong way. I don't mean they LEGALLY owe us an update. I mean since we own a development device, they would be pretty stupid to turn their backs on us....many of us have given google a percentage of the code used in final release versions of android. If they turn their backs on those people, they will be pretty screwed. They use quite a few features from roms that were here before google ever had the idea to do that. For example, swipe to clear notifications...that came from CM team. It sure as HELL wasn't google's baby, that's for sure!! That's why I say they owe us an update. Whether any one of us has personally contributed code or not, we have still contributed to the android project by testing the code that the developers here contributed to android.
Click to expand...
Click to collapse
Sprint stores had the file so people who had a replacement or a friend inside could of got the update on the 7th.
Sprint never said it was a two part update, but they said it would be a slow rollout for ns4g not gnex, over 8 days between which leaves you to believe the first half would be gnex, second half ns4g. Gonzo posted the files he got at the service center hours before anyone got the OTA link posted so the files were out since the 6th for both phones. SO my point is big deal it was only 4 days. Better than 4 months for ICS and deff better then whats going on over at verizon. Sprint told the truth. Not all reps know the facts. I worked for target and it doesnt mean i knew when we were getting new shipments of products. You should be mad that Sprint didnt explain the process but OTA 4 days later is better than no OTA.
Hopefully, you didnt quit your job or something like that to get the update on the 6th because thats your fault.
but cheer up, you have it now. Play around with the smoothness and yell out "I CANT BELIEVE IT'S NOT BUTTER!!!"
I have been trying to get this to work the last couple of days with no success.
Would having an unlocked bootloader prevent me from getting the OTA? If so, how do I lock the bootloader only?
Edit:
you annoying bastards did it
4.4.4 are live on the site as usual.
go download em https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
edit 2:
they are still missing the VRZ. but i think that is just red tape (red, get it?) from VRZ.
doesn't hurt to continue to bug them
edit 3:
sad that we had to annoy each other but it's finally complete. maybe next time don't include a annoy.timer setting with such lower timer in your OTA app :/ (it really has that name). or make it not jump in front of gps and calls... well i should learn not to use stock roms...
-----------------------
hi, if you also have a developer edition phone, and are pissed that morola only provides 4.4.2 and 4.2.2 images, making it impossible to restore a dev device back to stock for any reason, whithout a complex (and probably dev edition warranty voiding?) downgrade procedure, please, do bug them and ask for it.
the steps are:
1. open a chat (or call 1-800-734-5870 ) at https://motorola-global-portal.custhelp.com/app/mcp/service/
2. mention that you have a developer device
3. say that the page at https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images is impacting your device usage
3.b optional. you can mention the fact that being on stock 4.4.3 and being unable to update, you will get the 4.4.4 update warning every couple minutes, even on top of the GPS while you are driving!
4. mention that the page reads "to help owners return to the latest Motorola software." on the very first paragraph.
5. recall them that the latest motorola software is 4.4.4 or at least 4.4.3
do not give up until they say "i'm escaling this to L2." whatever that means
thank you! Only with lots of people bugging them they will do something about it.
Edit:
make noise on social networks!
FB: to do
G+: https://plus.google.com/112569377970438652007/posts/NwVH9HQ6EcC
tweet: to do
tumblr: to do
reddit: http://www.reddit.com/r/MotoX/comments/2jxvdo/please_do_your_part_to_get_official_444_and_443/
(comment with the links to the above and i will update here)
Thanks for this. Doing so as we speak.
UPDATE:
Well that was highly discouraging. After being told that unlocking my bootloader wouldn't void my warranty but that to flash one of the recovery images would require root and that would void my warranty (you can be sure I responded to that, LOL!), I was told that what's up there is what's up there and that they'd pass on my request to the appropriate party. LMAO. Basically, don't hold your breath. And people wonder why I'm getting a Nexus 6. I'm sick of companies treating unlocked devices as second class citizens. My S4 GPE has never seen an ODIN image. Officially, we've got recovery images that are 2 versions old for the GSM X DE. is that acceptable to anyone? It's not to me.
SamuriHL said:
Thanks for this. Doing so as we speak.
UPDATE:
Well that was highly discouraging. After being told that unlocking my bootloader wouldn't void my warranty but that to flash one of the recovery images would require root and that would void my warranty (you can be sure I responded to that, LOL!), I was told that what's up there is what's up there and that they'd pass on my request to the appropriate party. LMAO. Basically, don't hold your breath. And people wonder why I'm getting a Nexus 6. I'm sick of companies treating unlocked devices as second class citizens. My S4 GPE has never seen an ODIN image. Officially, we've got recovery images that are 2 versions old for the GSM X DE. is that acceptable to anyone? It's not to me.
Click to expand...
Click to collapse
thanks for trying man! for me it was pretty smooth.
I did mention that i was on stock 4.4.3, installed on motorola themselves on my phone. I only had a custom recovery, because, well, that is the reason i got a developer phone. The rep never asked me if i rooted or not. because it is irrelevant as you know and mentioned above.
i'd try again later on. maybe you get a rep with a clue. either way, thanks again for trying.
We need volume! c'mon folks.
Done deal!
Ooof.. hopefully Moto will realize that they need to do this as we'll need that to update to 5.0 if released!
Well, let's see if this helps....
{
"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"
}
livinginkaos said:
Well, let's see if this helps....
Click to expand...
Click to collapse
good idea. i'm not much on social networks, but
can you give me a proper link? i will pass it around at school and work email lists to get people to bump this.
Actually, i can update the top post with tweets, FB, G+ links that everyone can repost/like/+1 etc.
sadly, i'm on none of those networks
https://plus.google.com/112569377970438652007/posts/ZYZpw33AoRA
livinginkaos said:
https://plus.google.com/112569377970438652007/posts/ZYZpw33AoRA
Click to expand...
Click to collapse
it says, this post cannot be found:
dumb google plus said:
This post could not be found.
This URL may be incorrect, the post may have been deleted, or the post may not have been shared with this account
Click to expand...
Click to collapse
Sorry, that one was semi private. This one should work.....
https://plus.google.com/112569377970438652007/posts/NwVH9HQ6EcC
sent from my G3
livinginkaos said:
Sorry, that one was semi private. This one should work.....
https://plus.google.com/112569377970438652007/posts/NwVH9HQ6EcC
sent from my G3
Click to expand...
Click to collapse
thanks! added! and +1ed
gcbxda said:
thanks! added! and +1ed
Click to expand...
Click to collapse
I plus one your post but was unable to leave a comment.
---------- Post added at 09:21 PM ---------- Previous post was at 09:19 PM ----------
SamuriHL said:
Thanks for this. Doing so as we speak.
UPDATE:
Well that was highly discouraging. After being told that unlocking my bootloader wouldn't void my warranty but that to flash one of the recovery images would require root and that would void my warranty (you can be sure I responded to that, LOL!), I was told that what's up there is what's up there and that they'd pass on my request to the appropriate party. LMAO. Basically, don't hold your breath. And people wonder why I'm getting a Nexus 6. I'm sick of companies treating unlocked devices as second class citizens. My S4 GPE has never seen an ODIN image. Officially, we've got recovery images that are 2 versions old for the GSM X DE. is that acceptable to anyone? It's not to me.
Click to expand...
Click to collapse
Looks like when google sold Moto they lost their responsibility for keeping the devices up to date with factory images. Luckily and thanks to you SamuriHL I have this from you to pull my stock 4.4.4 images for my xt1060 dev edition. http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
Travisdroidx2 said:
I plus one your post but was unable to leave a comment.
---------- Post added at 09:21 PM ---------- Previous post was at 09:19 PM ----------
Looks like when google sold Moto they lost their responsibility for keeping the devices up to date with factory images. Luckily and thanks to you SamuriHL I have this from you to pull my stock 4.4.4 images for my xt1060 dev edition. http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
Click to expand...
Click to collapse
Yea, unfortunately that doesn't help us GSM DE users. I'm incredibly frustrated. Well, it just strengthens my resolve to get a Nexus 6. At least with that I know the images will be posted by Google in a very reasonable timeframe. For my S4 GPE I have to make them myself which is equally frustrating. On the X GSM DE we may have to get to a point of a hybrid "FXZ" where we fastboot some partitions, reboot into custom recovery, and then flash a pulled system image. That just seems really wrong when it wouldn't take Moto very much to host the damn images for us.
SamuriHL said:
Yea, unfortunately that doesn't help us GSM DE users. I'm incredibly frustrated. Well, it just strengthens my resolve to get a Nexus 6. At least with that I know the images will be posted by Google in a very reasonable timeframe. For my S4 GPE I have to make them myself which is equally frustrating. On the X GSM DE we may have to get to a point of a hybrid "FXZ" where we fastboot some partitions, reboot into custom recovery, and then flash a pulled system image. That just seems really wrong when it wouldn't take Moto very much to host the damn images for us.
Click to expand...
Click to collapse
Completely agree. That is one good thing about the nexus. You can count on those image files being released in a timely matter. Thanks again though for your work. It gave me the stock images I needed for my Dev edition. Very much appreciated! As well as you old house of bionic I used on my wife's old bionic lol
Travisdroidx2 said:
Completely agree. That is one good thing about the nexus. You can count on those image files being released in a timely matter. Thanks again though for your work. It gave me the stock images I needed for my Dev edition. Very much appreciated! As well as you old house of bionic I used on my wife's old bionic lol
Click to expand...
Click to collapse
The images I got came from stras. I just post them as he gives them to me. He's awesome. Also, not to get off topic, but just so you're aware my House of Moto and RSD Flasher tools will work for your X DE and that FXZ.
SamuriHL said:
The images I got came from stras. I just post them as he gives them to me. He's awesome. Also, not to get off topic, but just so you're aware my House of Moto and RSD Flasher tools will work for your X DE and that FXZ.
Click to expand...
Click to collapse
Thanks for your time and tools. However, once I learned how to manually flash image files I left the toolkits alone. But if I was to use a tool I would trust yours.
Nothing has changed. I have it on good authority that this amounts to a bureaucratic oversight and will be taken care of ASAP.
All the right people are aware of the issue and working to address it.
cellzealot said:
Nothing has changed. I have it on good authority that this amounts to a bureaucratic oversight and will be taken care of ASAP.
All the right people are aware of the issue and working to address it.
Click to expand...
Click to collapse
That's actually really good to hear. Thanks for the info!
SamuriHL said:
That's actually really good to hear. Thanks for the info!
Click to expand...
Click to collapse
No problem! Hopefully it will be soon. The person i spoke with used to do this personally and build and sign the zips himself but has delegated that to an underling who has had a full plate and hasn't gotten to it yet, unfotunately.
He assured me there had been no change in policy regarding the availability and posting of these files!
cellzealot said:
No problem! Hopefully it will be soon. The person i spoke with used to do this personally and build and sign the zips himself but has delegated that to an underling who has had a full plate and hasn't gotten to it yet, unfotunately.
He assured me there had been no change in policy regarding the availability and posting of these files!
Click to expand...
Click to collapse
That is truly excellent news. I was very concerned since they only have 4.4.2 up there and 4.4.3 has been out for months now. Yes we've been able to get leaks until recently but we should be able to get them officially and the sbf site hasn't been updated since early September.
Sent from my SM-P600 using Tapatalk
Not sure why you guys are praising nexus. My experience with N1 was awfull. stuck on 2.3 forever. zero support. hardware problems that should have been recalled completely ignored and dismissed by google and htc... well, i think i will have my opnion change when N4 gets 5.0 (which is it capable on hardware)
also, you are all ignoring the fact that the next nexus will be churned out by motorola. and will be a even bigger phablet than motoX2.
cellzealot said:
No problem! Hopefully it will be soon. The person i spoke with used to do this personally and build and sign the zips himself but has delegated that to an underling who has had a full plate and hasn't gotten to it yet, unfotunately.
He assured me there had been no change in policy regarding the availability and posting of these files!
Click to expand...
Click to collapse
nice! (assuming that policy was to provide more than two images...) will continue to bug them daily. so you can tell your friend to tell the underling to ask for a raise! management will surely say yes
Go to this link and translate page from whatever language it is in, haven't tried it but maybe someone can and tell us if it worked
http://4pda.ru/forum/index.php?showtopic=516020&st=4760#entry38598836
Hopefully someone can shortcut a safe script and do it soon. Verizon is getting quicker at popping out root block methods. They should focus more on making lollipops!
This would be awesome.
JH1108 said:
Go to this link and translate page from whatever language it is in, haven't tried it but maybe someone can and tell us if it worked
http://4pda.ru/forum/index.php?showtopic=516020&st=4760#entry38598836
Click to expand...
Click to collapse
romma1 said:
Hopefully someone can shortcut a safe script and do it soon. Verizon is getting quicker at popping out root block methods. They should focus more on making lollipops!
Click to expand...
Click to collapse
I'm attempting this method right now, and let me tell you, this is most definitely not for the faint of heart. This process is EXTREMELY dangerous, and there's a good chance that it won't work at all. I'll fill you guys in when I'm done, but given the speed of this thing, that'll be in a day or two. If it's successful, I'll write up a tutorial in English, but again this is not for the faint of heart. It literally involves putting your phone into QHSUSB_DLOAD mode, a mode that is more wide-known as a hard brick.
Again, I'm doing it right now, it says the process will take more than 3 hours, so I'll be back sooner or later.
Edit: Also given the fact that you're going into QHSUSB_DLOAD mode, there's no safe script. This process can and probably will **** up your phone. Unfortunately, it's too late for me to turn back, so I just gotta go on ahead with it and hope for the best.
thenameisnigel said:
I'm attempting this method right now, and let me tell you, this is most definitely not for the faint of heart. This process is EXTREMELY dangerous, and there's a good chance that it won't work at all. I'll fill you guys in when I'm done, but given the speed of this thing, that'll be in a day or two. If it's successful, I'll write up a tutorial in English, but again this is not for the faint of heart. It literally involves putting your phone into QHSUSB_DLOAD mode, a mode that is more wide-known as a hard brick.
Again, I'm doing it right now, it says the process will take more than 3 hours, so I'll be back sooner or later.
Edit: Also given the fact that you're going into QHSUSB_DLOAD mode, there's no safe script. This process can and probably will **** up your phone. Unfortunately, it's too late for me to turn back, so I just gotta go on ahead with it and hope for the best.
Click to expand...
Click to collapse
You sir are a man with big balls. So this process involves hard bricking your phone and in the process of bringing it back to life, gaining root?
Also what phone are using? I know it says it's for the mini but wondered if it would work on the ultra and maxx as well.
Sent from my locked, stocked, XT1080 using XDA Free mobile app
chuck864 said:
You sir are a man with big balls. So this process involves hard bricking your phone and in the process of bringing it back to life, gaining root?
Also what phone are using? I know it says it's for the mini but wondered if it would work on the ultra and maxx as well.
Sent from my locked, stocked, XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
I'm using the Ultra and I'm literally scared ****less to be completely honest. I have to wait for it to finish the first process, and then I have four more to go. I'm hoping to be done by tonight, but considering the speed that this is going at, it'll take a day or two to finish. As dangerous as this process is, as soon as you run the script to start uploading the system.mbn files to the phone, it also fixes the boot loader (fastboot mode) so just in case your computer turns off (as mine did like an hour ago/again I was scared ****less when that happened), you just can go back to fastboot mode and start over.
I Do NOT recommend anyone try this though until I finish and post my results, but everything seems good so far. I'll post a screenshot of the process if you guys want to, and I am most definitely starting a write-up tutorial as well as trying to make a one-click, that won't be posted until I complete this successfully.
Thank you thank you thank you.... Eagerly waiting!!!!
Sent from my XT1254 using XDA Free mobile app
chuck864 said:
You sir are a man with big balls. So this process involves hard bricking your phone and in the process of bringing it back to life, gaining root?
Also what phone are using? I know it says it's for the mini but wondered if it would work on the ultra and maxx as well.
Sent from my locked, stocked, XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
drmrjake said:
Thank you thank you thank you.... Eagerly waiting!!!!
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
The first step out of five just finished like 10 minutes ago, so I'm in fastboot mode charging my phone because letting it die in the middle of the process doesn't seem like it would be good. I'll probably start step 2 in like 30-45 minutes so I can get a decent charge before I continue. Also, just giving a heads-up that rooting looks like it'll be an all-day process considering I started it at 2 and it's 6:05 right now. And that was just step one.
Well good luck to you sir... I for one (and I can probably speak for allof us out here) VERY much appreciate it.
Sent from my XT1254 using XDA Free mobile app
drmrjake said:
Well good luck to you sir... I for one (and I can probably speak for allof us out here) VERY much appreciate it.
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
Praying for you man. You would be a hero!
drmrjake said:
Well good luck to you sir... I for one (and I can probably speak for allof us out here) VERY much appreciate it.
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
Just wanna give a update while I'm letting my Ultra charge up, you should REALLY make sure your phone is at 100% charge before you attempt this because charging in fastboot mode is a bit questionable (my phone says Battery Low and the charger has been connected the entire time from entering fastboot mode), so that's something to be aware of. I'm gonna let it go until 7, and then I'll start Step 2. Hopefully it'll be done before I go to sleep so I can put it in fastboot to recharge overnight and I can continue in the morning with Step 3. This is definitely a very long process.
Sadly, It is impossible to root the Droid Maxx. I commend anyone trying their luck however.
If I'm not mistaken (and I really hope I'm wrong) I believe you need a "factory" USB cable to charge in fast boot. And by factory I don't mean the one that came with the phone. I had to order one on eBay to do what you're describing... Charge in fastboot...
Again ...I really hope I'm wrong here and just remembering incorrectly
Good luck my friend
Sent from my XT1254 using XDA Free mobile app
drmrjake said:
Well good luck to you sir... I for one (and I can probably speak for allof us out here) VERY much appreciate it.
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
drmrjake said:
If I'm not mistaken (and I really hope I'm wrong) I believe you need a "factory" USB cable to charge in fast boot. And by factory I don't mean the one that came with the phone. I had to order one on eBay to do what you're describing... Charge in fastboot...
Again ...I really hope I'm wrong here and just remembering incorrectly
Good luck my friend
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
Well, I rebooted fastboot and it says Battery OK now so it seems like it's charging. Either way, if it stops working, I'll just send it back to Moto since I'm in warranty.
---------- Post added at 06:48 PM ---------- Previous post was at 06:47 PM ----------
Samg381 said:
Sadly, It is impossible to root the Droid Maxx. I commend anyone trying their luck however.
Click to expand...
Click to collapse
In the link in the OP where I got this method from, people said they were successful, so it doesn't hurt to try. Well, it actually does hurt to try, but you catch my drift.
---------- Post added at 07:20 PM ---------- Previous post was at 06:48 PM ----------
Okay, 1 hour later and I'm still at Battery LOW (Charging).
Unable to proceed because the battery doesn't want to charge.
{
"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"
}
Does anyone have the SU6-7 FXZ because it looks like I won't be getting anywhere until I get recharged.
Edit: Found it.
thenameisnigel said:
[/COLOR]Okay, 1 hour later and I'm still at Battery LOW (Charging).
Unable to proceed because the battery doesn't want to charge.
Does anyone have the SU6-7 FXZ because it looks like I won't be getting anywhere until I get recharged.
Edit: Found it.
Click to expand...
Click to collapse
are you charging on a usb port or wall.charger? my dev maxx would charge using both, but the amps (or lack thereof) of a usb port take forever to get the battery back up. also, if ya have a friend with a turbo charger, they charge fast-er. (mini at zero takes an hour, as does the Turbo). Good luck.
kitcostantino said:
are you charging on a usb port or wall.charger? my dev maxx would charge using both, but the amps (or lack thereof) of a usb port take forever to get the battery back up. also, if ya have a friend with a turbo charger, they charge fast-er. (mini at zero takes an hour, as does the Turbo). Good luck.
Click to expand...
Click to collapse
I was attempting via a wall charger first but that got me nowhere, it didn't actually start charging until I plugged it in to a USB port. That's when I got Battery OK (Charging) but rebooting and entering fastboot again gets me Battery LOW
yeah, that sucks. good luck dude.
I've looked through the scripts to see what this does exactly but I'm not familiar with python. Is this a method to get root or just to downgrade to su5.24(which is still 4.4.4)?
chuck864 said:
I've looked through the scripts to see what this does exactly but I'm not familiar with python. Is this a method to get root or just to downgrade to su5.24(which is still 4.4.4)?
Click to expand...
Click to collapse
Downgrade and according to the OP, it's de-odexed and rooted.
thenameisnigel said:
Downgrade and according to the OP, it's de-odexed and rooted.
Click to expand...
Click to collapse
But that still would be bootloader locked, right? Can we then use sunshine to unlock bootloader, or is this to new software?
So a lil background on me... I'm very experienced in phone rooting and the like. I work for Best Buy Mobile, and see all the new stuff well before anyone else. I played with the LG G4 a month before release and it was love at first sight. Well I ordered mine thru my concessions line I have thru work and it arrived yesterday. I opened it, activated it and immediately turned on developers options, mainly because I knew some animations were turned off. Well, I had to look at the software version, and it said "MODIFIED".
I purchased the one with the leather back. It is completely stock, I've not even attempted to try root, if we even have it yet. Did anyone else purchase theirs and it have " MODIFIED" software?
{
"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"
}
Sent from my VS986 using Tapatalk
I'm not an expert, but that font is NOT the same as on my phone. Looks like it has indeed been customized to a certain extent.
If you're displeased with it, I'd exchange it for a new one.
Mejilan said:
I'm not an expert, but that font is NOT the same as on my phone. Looks like it has indeed been customized to a certain extent.
If you're displeased with it, I'd exchange it for a new one.
Click to expand...
Click to collapse
You can change the font in settings.
Sent from my LG-H812 using XDA Forums Pro.
My VS986 says same thing. Bought at Verizon kiosk in BJs.
Doug B.
Same here. I imagine activating Developer's Options, and/or turning on debugging does it.
Pretty sure it said Modified before I turned on Dev Opts.
Doug B.
I read somewhere in this forums that a lot of Verizon G4 users claim that it arrived as modified. They suspected that Verizon disabling some functions, such as FM radio, might have caused it and didn't double check to see the software version.
If I were you I'll contact Verizon to double check.
Sent from my LG-H811 using XDA Free mobile app
dvgb173 said:
Pretty sure it said Modified before I turned on Dev Opts.
Doug B.
Click to expand...
Click to collapse
Either way, it doesn't mean anything. To us, regarding root, anyway.
I agree. Sounds like Verizon's build. Nothing more. That doesn't mean it doesn't suck though.
Doug B.
Just checked on my Verizon G4, and it currently says official next to software status.
Eagle1337 said:
You can change the font in settings.
Sent from my LG-H812 using XDA Forums Pro.
Click to expand...
Click to collapse
Woops, sorry about that.
For some reason, I thought replacing fonts required some fancier, higher level customization options.
Probably thinking back to my old iPhone jailbreak days. /shudders
aosmer said:
Just checked on my Verizon G4, and it currently says official next to software status.
Click to expand...
Click to collapse
Yeah, I have the VS986 as well, and I show "Official" under status. I have USB debugging on as well. Bought the phone at Verizon this past Sunday
aosmer said:
Just checked on my Verizon G4, and it currently says official next to software status.
Click to expand...
Click to collapse
When/where did you get it?
Doug B.
spotmark said:
Same here. I imagine activating Developer's Options, and/or turning on debugging does it.
Click to expand...
Click to collapse
Mine def said modified before I did that. It just struck me as odd. Idk why it would say that.
Sent from my VS986 using Tapatalk
I bought mine from a Verizon store (not third party) on day 1. I have used Developer Options, USB Debugging, and connected via adb, and my software still says Official. Build is LMY47D, Config is J14.LGE.VS986.0
Yea I'm def not sure why mine says that at all. Mine was shipped to me. I guess it's nothing to really worry about really. Phone flies like I knew it would lol
Sent from my VS986 using Tapatalk
dvgb173 said:
When/where did you get it?
Doug B.
Click to expand...
Click to collapse
I picked it up 6/15 at my local Best Buy.
Mine says official.
I picked up mine from Verizon on Saturday, says "Official" .. enabled Developer mode .. rebooted .. still says "Official".
As stated on other threads, 'Modified' or 'Official' doesn't mean anything here.
{
"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