Related
I just got an email from that China middleman back from this thread http://forum.xda-developers.com/moto-x/general/verizon-moto-maker-bootloader-unlock-t2680651
Titled: moto bootloader work back 2014/05/15
Subject: price：45usd paypal:[email protected] notes:IMEI+ email !!!! in 12-48H reply
Its $5 more and he's saying hes back!
I have emailed him and I will post results but im very hopeful!
Edit: ONLY AVAILABLE FOR 2014 DEVICES
and some 2013 if your lucky
F.A.Q.
I think a recap is due...
Some background... For the Developer Editions Moto X, and some carrier editions (Like T-Mobile, Sprint, Rogers Wireless, and others), Motorola freely gives away the BootLoader Unlock codes when requested On Motorola's Web Site. In the case of the Non-Developer Editions, it voids their warranty to request the code.
I'm not going to go into the reasons why, but Moto does NOT give out the bootloader unlock code for the Retail and Moto Maker X for Verizon, ATT and a few other carriers. That is where this China Middle Man, and the Chinese web site/seller, comes in... Its a way to possibly get your bootloader unlock code if Moto can't/wont give it to you. If you are successful in getting your code from the Middle Man, it will be exactly like the code you would have received from Moto, except for the cost and the source.
If your X is NOT from Verizon, ATT, or Republic wireless, its worth checking Motorola's Web Site first, as either way voids your warranty when your phone is not a developer edition. If you can't get the bootloader unlock code from Motorola, then this China Middleman is your only other option right now (and for who knows how long).
What phones does this work with?
Based on replies and posts to this thread, it has been confirmed to work for most, but not all, Moto X, Droid Maxx, Droid Mini and G which have been assembled between January and June 2014 that have been submitted. Some others assembled out-side that range have been reported to work.
Republic Wireless X assembled in 2013 have had a fair success rate, at least enough that it is worth trying.
Since the middle man has restarted selling codes, users with Moto X from Verizon, ATT that were assembled in 2013 have rarely been able to receive a code. So you can try, but you will likely get a "no code available" response.
Update 10-21-2014: As time goes on, we are seeing an increase in post from users who have been "unsuccessful." (either they couldn't get a code, or the code they got didn't work). Its still worth a try.
This does NOT work for the 2nd Generation X or the "2014 Moto X" with the 5.2" screen.
Does it matter what ROM is on my phone?
Unlike using hacks and exploits to root, when using a Bootloader Unlock Code (from Moto or the Middle Man) your phone can be on ANY firmware version. Updates will not patch the ability to use the bootloader unlock code. And future Updates will NOT LOCK your bootloader.
On the Moto X, to find your assembled date...
Boot into FastbootAP/Bootloader mode
Option 1: power off, then press the power and volume down buttons simultaneously NOTE: you may need to have the USB cable disconnected first.
Option 2: If USB debugging option on your phone is turned on, and you have a properly setup ADB, AndroidSDK Platform tools, and moto drivers on your pc... Open a command prompt and type... adb reboot-bootloader The phone will restart into the bootloader/fastboot menu.
Option 3: You must already be rooted: you can use an application like Quick Boot (Reboot) which is available for free in the Google Play Store. It has options to reboot your phone normally, reboot into recovery, or reboot into bootloader.
Once on the FastbootAP/Booloader screen, Use the VOL DOWN to scroll and highlight Bar Codes, then use VOL UP to select it. There will be a date listed there. (use vol up or vol down to exit the screen).
How long will this be an option? or... How long will the China Middleman continue offering the codes?
We don't have any insight on that. When the China web site, and then middleman, originally started it was up for a while, then suddenly and without warning, stopped on April 1. When it restarted, this thread was born, and it has been going ever since. However, this time around, we've seen a lower success rate with getting codes.
How to send a request/payment..
The price is 45usd. (he will receive slightly less due to fees)
Send Paypal for goods/services to [email protected]
In the notes, include your IMEI and Email.
NOTE: be sure to use Goods/Services so you can dispute if you have any issues. Payment sent as GIFT can NOT be disputed!
How long does it take to get my code, or get a response?
Response times have varied from less than an hour, to almost a week. So be patient. If its been over a week, you can try to add the person to Skype and message.
I got a response that my code wasn't available. Now what?
Usually he refunds the money when replying your code wasn't available. If not, you'll need to file a PayPal dispute.
If your phone is only two or three weeks old, you can try waiting a month, try again and see if he gets a new batch of codes which contains yours.
Otherwise, you are out of luck.
UPDATE: You can try Sunshine which is being discussed in -> http://forum.xda-developers.com/moto-x/general/request-help-exploit-moto-x-bl-t2828471 That thread has the information, link to the Sunshine tool, and discussion.
Sunshine only works with certain ROM versions, but when it works on your phone it DOES UNLOCK the bootloader just like using the code would.
If Sunshine doesn't work, then you are out of luck.
I got my code, now what?
Most emailed responses containing the code have included your IMEI code and unique unlock code. The unlock code is 20 digits long and is case sensitive. Please Copy/Paste when using it, rather than typing it.
Back up your phone! the Bootloader Unlock process WILL WIPE all data, apps, settings, etc!! BACK UP FIRST!!
Make sure you have a working Android SDK/PlatformTools/ADB setup
Boot your phone into FastbootAP/Bootloader mode
Connect your phone to your PC via USB cord
From a command prompt on your PC issue the following command... fastboot oem unlock UniqueCode NOTE: please replace "UniqueCode" with a copy/paste of your code from the email!
after the process is successful, your phone will reboot and you will see the Unlocked Bootloader warning logo.
For a more detailed or novice friendly set of instructions, see -> http://mark.cdmaforums.com/MotoX-Unlocking.htm
Keep your code in a safe place. While there should be no need to relock the bootloader, if you ever need to unlock the bootloader again, you'll use that same code.
So now that I've unlocked my phone, is it now the same as a "Developer Edition"?
For all intents and purposes, Yes. From the standpoint of rooting, flashing, custom roms, hacks, etc. You can use the same instructions and do the same things. The same caveats and rules that apply to a developer edition, apply to you.
Unlike a developer edition, your warranty will be voided because you've unlocked your bootoader (if the warranty provider notices you've unlocked your bootloader).
So now that I've unlocked my phone, HOW DO I ROOT?
Download the latest TWRP Recovery from -> http://teamw.in/project/twrp2/234 (under the Download-Fastboot heading) and the latest SuperSU from -> http://download.chainfire.eu/supersu or the latest CWM / TWRP / MobileODIN installable ZIP from http://forum.xda-developers.com/showthread.php?t=1538053
And use them while following the instructions in this post -> http://forum.xda-developers.com/moto-x/moto-x-qa/step-step-instructions-unlocking-t2649738
Thats great, but I still have questions...
When this first came about, I put together this post in the old thread -> http://forum.xda-developers.com/showpost.php?p=51363645&postcount=394
I've added to it, clarified a few things and re-posted here -> http://mark.cdmaforums.com/MotoX-Unlock1.htm
Those two versions contain pretty much all of the questions/answers I've seen asked.
EDITED: Aug 13, 2014 Reason: added Background, Moved "what phones does it work with.." section, added "Does it matter what rom.." section, and added rooting info
EDITED: Aug 28, 2014 Reason: moved "how long a response could take" to its own section so it stands out more
---------- Post added at 02:01 PM ---------- Previous post was at 01:53 PM ----------
Slick52 said:
I know it's a big unknown, but what are the chances these guys will have unlock codes for the X+1? My parents are about to renew, but they will need 1 unlocked hotspot for an unlimited plan. With Aug 20th supposedly being the release date, 2weeks away, should they wait for the +1?
Sent from my XT1060
Click to expand...
Click to collapse
Nothing will be known until the X+1 comes out and someone tries to unlock it.
And this service could stop at any time.
My advice is something I got flamed in this thread for in the past.. but since you asked... Since you'll have to pay full price anyway (to keep unlimited data) Consider getting a Dev Edition X for Verizon while they are still on sale for $324.99. Its definately cheaper than buying a full price X+1 when they come out, and you can certainly unlock the bootloader without voiding the warranty.
Tag for outcome.
I got the email as well. We'll see what happens!
Sent from my XT1060 using XDA Premium 4 mobile app
Everyone who didn't get on the first boat, I would recommend jumping on this asap (if he's really back.) Nothing like having a self made Dev edition and complete freedom with nowhere near full retail cost.
Screw it, Im in. Not waiting around and getting left behind this time.
Yep, got an email from him this morning as well (should be 40+ of us since he has no idea how to use bcc). Stopped what I was doing and sent the payment & info. Will also post any results.
Might I remind everyone who is doing this to send payment as goods/services this time - the people who sent as a gift couldn't get a refund last time.....
edit: also wanted to mention that i went from 10-20 spam emails a day to over a hundred after emailing this dude the last time..... so use a junk email address you don't care about.
The original link does not seem to work for me. Can someone confirm the URL?
jasonumd2 said:
The original link does not seem to work for me. Can someone confirm the URL?
Click to expand...
Click to collapse
just do what the instructions in the first post of this thread say. send paypal payment of $45 to that address with IMEI and email address in the notes.
Duh. Thanks! Payment sent and fingers crossed.
mohlsen8 said:
just do what the instructions in the first post of this thread say. send paypal payment of $45 to that address with IMEI and email address in the notes.
Click to expand...
Click to collapse
He just responded to me. Apparently the 2013 models aren't in the database. He's initiated a refund for me.
Sent from my XT1060 using XDA Premium 4 mobile app
bummer.. guess this means i need to initiate a refund:
"2013 production was not found in the database machine, I will refund initiated paypal dispute
Can't find 2013, the data do not know where to put, no way"
edit: second email to the bigger group:
"moto bl Notice
Can't find 2013, the data do not know where to put, no way
2014 100% ok"
mohlsen8 said:
bummer.. guess this means i need to initiate a refund:
"2013 production was not found in the database machine, I will refund initiated paypal dispute
Can't find 2013, the data do not know where to put, no way"
edit: second email to the bigger group:
"moto bl Notice
Can't find 2013, the data do not know where to put, no way
2014 100% ok"
Click to expand...
Click to collapse
So, sounds like there's still an opening for devices made this year? Seems very strange, but I guess promising for the minority of people who have newer-issued devices. I bought mine on swappa, so I have no clue whether it would be included in the 2013 or 2014 group. If I had bought it in 2013, I'd probably do my best to get an on-warranty replacement any way I could.
Jumnhy said:
So, sounds like there's still an opening for devices made this year? Seems very strange, but I guess promising for the minority of people who have newer-issued devices. I bought mine on swappa, so I have no clue whether it would be included in the 2013 or 2014 group. If I had bought it in 2013, I'd probably do my best to get an on-warranty replacement any way I could.
Click to expand...
Click to collapse
it's really weird. with how flaky this situation has been, it's not even worth trying that, this could be closed up again pretty quickly.. if the dude can even get 2014 codes. strange..
btw you should probably be able to find a manufacture date or something somewhere, i dunno.
so did any other 2013's file a dispute yet? i'm pretty sure that's what he meant, that we do that and he refunds - that's how it worked last time. i didn't do it yet just on the small chance he figures it out or something, who knows. i sent him an email asking for more info but haven't gotten a response.
mohlsen8 said:
it's really weird. with how flaky this situation has been, it's not worth even trying that, this could be closed up again pretty quickly.. if the dude can even get 2014 codes. strange..
Click to expand...
Click to collapse
I mean, is he refunding your money? If the dude is in good faith it sounds like there's no harm in trying because if it doesn't work you can get your money back. If not, is there any way we can find out what devices he has access to codes for? I am looking into finding info on manufacture dates but running into a lot of dead ends. Anyone have any ideas? That way people could check beforehand and save themselves the trouble.
Jumnhy said:
I mean, is he refunding your money? If the dude is in good faith it sounds like there's no harm in trying because if it doesn't work you can get your money back. If not, is there any way we can find out what devices he has access to codes for? I am looking into finding info on manufacture dates but running into a lot of dead ends. Anyone have any ideas? That way people could check beforehand and save themselves the trouble.
Click to expand...
Click to collapse
Only place I would think to check would be the barcode sticker on the box that has IMEI etc. Otherwise you'd probably have to rip the phone apart to find it somewhere.
But yes, when this went belly up a month ago, the bunch of us who had money out to him, as long as you sent the paypal money as goods/services (and not gift) you could file a dispute with paypal and he was immediately refunding people when you did that. The others who sent money as gifts to try to help him out with paypal fees ended up getting screwed because they couldn't dispute it and he didn't respond to any emails asking for refunds - you had to go through a paypal dispute, but then he was very quick to issue it.
All that shadiness aside, if you send it for goods/services, I think you're fine trying.
mohlsen8 said:
Only place I would think to check would be the barcode sticker on the box that has IMEI etc. Otherwise you'd probably have to rip the phone apart to find it somewhere.
But yes, when this went belly up a month ago, the bunch of us who had money out to him, as long as you sent the paypal money as goods/services (and not gift) you could file a dispute with paypal and he was immediately refunding people when you did that. The others who sent money as gifts to try to help him out with paypal fees ended up getting screwed because they couldn't dispute it and he didn't respond to any emails asking for refunds - you had to go through a paypal dispute, but then he was very quick to issue it.
All that shadiness aside, if you send it for goods/services, I think you're fine trying.
Click to expand...
Click to collapse
Interesting. It's cool to see consumer safeguards working as they're intended--if he's not giving out any refunds for "gift" payments he's not interested in the ethics, just his standing with PayPal. Love it when these systems work the way they should.
I bought my X online through swappa; the guy sent it in the original box... just looked at the sticker, and nope, looks like august of 2013. Looks like I'm still out of luck. :/
I have a 2013-purchased Moto X and sent over the $45 (prior to seeing the messages above) as a Goods/Service at 11am EST. I will update this thread with any messages I receive. Fingers crossed! I'd love to know what is going on behind-the-scenes with where this database is coming from, why would 2014 work but not 2013, etc.
DogzOfWar said:
I have a 2013-purchased Moto X and sent over the $45 (prior to seeing the messages above) as a Goods/Service at 11am EST. I will update this thread with any messages I receive. Fingers crossed! I'd love to know what is going on behind-the-scenes with where this database is coming from, why would 2014 work but not 2013, etc.
Click to expand...
Click to collapse
please do. i'm waiting for some feedback before i request a refund, even it if may be hopeless for us.
I, unfortunately, paid as a gift. I have a 2014 so maybe I'll get lucky. I'll post my results.
So I paid to get the unlock code a few weeks ago and got a code back from him, but unfortunately the code failed. I'm not sure why the code failed, other than that my device is new (6-16-14 build date). I attached a screenshot with the code blurred out of my results in Terminal Anyone else experience this?
Also, since the code did not work, I initiated a dispute to say that the code didn't work (I have paid him for another unlock on my previous Moto X that worked) but he did not accept and just sent back another message with the same code that still doesn't work. What should I do?
Thanks!!!
bravesfan171 said:
So I paid to get the unlock code a few weeks ago and got a code back from him, but unfortunately the code failed. I'm not sure why the code failed, other than that my device is new (6-16-14 build date). I attached a screenshot with the code blurred out of my results in Terminal Anyone else experience this?
Also, since the code did not work, I initiated a dispute to say that the code didn't work (I have paid him for another unlock on my previous Moto X that worked) but he did not accept and just sent back another message with the same code that still doesn't work. What should I do?
Thanks!!!
Click to expand...
Click to collapse
I wonder if Moto is "poisoning" the database he is using. This could signal that the ride is ending....
bravesfan171 said:
So I paid to get the unlock code a few weeks ago and got a code back from him, but unfortunately the code failed. I'm not sure why the code failed, other than that my device is new (6-16-14 build date). I attached a screenshot with the code blurred out of my results in Terminal Anyone else experience this?
Also, since the code did not work, I initiated a dispute to say that the code didn't work (I have paid him for another unlock on my previous Moto X that worked) but he did not accept and just sent back another message with the same code that still doesn't work. What should I do?
Thanks!!!
Click to expand...
Click to collapse
Ensure the IMEI you are sending is correct.
Confirm the IMEI his response with the code matches your IMEI.
Ensure you are using only the 20digit code, which is case sensitive, and not any part of your IMEI (I've read some reports of him sending it back as something like "your code is: XXXXX YYYYYY" where one part is your IMEI and the other is your code.
KidJoe said:
Ensure the IMEI you are sending is correct.
Confirm the IMEI his response with the code matches your IMEI.
Ensure you are using only the 20digit code, which is case sensitive, and not any part of your IMEI (I've read some reports of him sending it back as something like "your code is: XXXXX YYYYYY" where one part is your IMEI and the other is your code.
Click to expand...
Click to collapse
I did do that and it is the same. I am using the code, which is 20 digits. I've also tried in Mac and Windows.
bravesfan171 said:
I did do that and it is the same. I am using the code, which is 20 digits. I've also tried in Mac and Windows.
Click to expand...
Click to collapse
In your screen shot you show using fastboot... try mFastboot?
Otherwise I don't know what to say, other than the code he has is wrong for some reason.
KidJoe said:
In your screen shot you show using fastboot... try mFastboot?
Otherwise I don't know what to say, other than the code he has is wrong for some reason.
Click to expand...
Click to collapse
Same result with mfastboot. Anyone else had issues with a code not working? Or anyone have any ideas of what I should do?
Also, has anyone unlocked a device with around a 6-16-14 build date?
bravesfan171 said:
Same result with mfastboot. Anyone else had issues with a code not working? Or anyone have any ideas of what I should do?
Also, has anyone unlocked a device with around a 6-16-14 build date?
Click to expand...
Click to collapse
IDK, but 6-16-14 seems TOO new for him to have a code for you.
I have a Moto G and my build date is 3-4-2014. He was able to get a successful code for me but on the Moto G unlock thread http://forum.xda-developers.com/moto-x/general/china-middleman-t2751177 there are some with build dates in June 2014 who were told that there devices were too new for him to have an unlock code for them and for them to check back in about a month. Kind of surprised he was able to get a code for you, albeit an unsuccessful one.
classic757 said:
IDK, but 6-16-14 seems TOO new for him to have a code for you.
I have a Moto G and my build date is 3-4-2014. He was able to get a successful code for me but on the Moto G unlock thread http://forum.xda-developers.com/moto-x/general/china-middleman-t2751177 there are some with build dates in June 2014 who were told that there devices were too new for him to have an unlock code for them and for them to check back in about a month. Kind of surprised he was able to get a code for you, albeit an unsuccessful one.
Click to expand...
Click to collapse
That's what I thought was strange too. Do you think I should try again in a couple weeks? Or would he just give me that same wrong code again?
Sent from my XT1060 using XDA Free mobile app
bravesfan171 said:
That's what I thought was strange too. Do you think I should try again in a couple weeks? Or would he just give me that same wrong code again?
Sent from my XT1060 using XDA Free mobile app
Click to expand...
Click to collapse
Maybe you can try again but I don't know if he will send you a different code since he says that is the code for your phone. You may have to contact Paypal and see what steps you can take if any to resolve your situation. I hope this gets resolved for you in a timely fashion and that you are able to get your phone unlocked.
---------- Post added at 05:47 PM ---------- Previous post was at 05:32 PM ----------
samwathegreat said:
I wonder if Moto is "poisoning" the database he is using. This could signal that the ride is ending....
Click to expand...
Click to collapse
I hear you. Sooner or later Motorola will probably find a way to put a stop to this and shut it down.
classic757 said:
Maybe you can try again but I don't know if he will send you a different code since he says that is the code for your phone. You may have to contact Paypal and see what steps you can take if any to resolve your situation. I hope this gets resolved for you in a timely fashion and that you are able to get your phone unlocked.
Click to expand...
Click to collapse
I did initiate a dispute already since the code didn't work but he didn't accept it since he already had to pay the source. I don't know if I should fight it anymore and it makes me reluctant to waste another 45 bucks that I might not be able to get back again if I try later.
Any advice guys?
bravesfan171 said:
I did initiate a dispute already since the code didn't work but he didn't accept it since he already had to pay the source. I don't know if I should fight it anymore and it makes me reluctant to waste another 45 bucks that I might not be able to get back again if I try later.
Any advice guys?
Click to expand...
Click to collapse
Send him a screenshot of it showing that the pwd is incorrect. Tell him that you expect to be refunded since the code is obviously incorrect.
If he still refuses, maintain the dispute, and let PayPal know that the seller refuses to refund you. PayPal will probably decide in your favor. Additionally, if you used a credit card to fund the paypal payment, you could dispute it with the credit card company if PayPal does not side with you.
I hate to recommend disputes, but if I received an incorrect code, I would most definitely dispute. $45 may not be much, but its the fact of the matter...
bravesfan171 said:
I did initiate a dispute already since the code didn't work but he didn't accept it since he already had to pay the source. I don't know if I should fight it anymore and it makes me reluctant to waste another 45 bucks that I might not be able to get back again if I try later.
Any advice guys?
Click to expand...
Click to collapse
IDK, this is the first time I heard about him not wanting to refund a payment, especially since the code he sent you was not successful.
From what I have read and experienced, the guy is pretty reliable.
bravesfan171 said:
I did initiate a dispute already since the code didn't work but he didn't accept it since he already had to pay the source. I don't know if I should fight it anymore and it makes me reluctant to waste another 45 bucks that I might not be able to get back again if I try later.
Any advice guys?
Click to expand...
Click to collapse
Since the code sent to you doesn't work, I would fight it.
If you did the paypal as Goods/Services, can't you state that the "goods received" are bad, not correct, etc?
KidJoe said:
Since the code sent to you doesn't work, I would fight it.
If you did the paypal as Goods/Services, can't you state that the "goods received" are bad, not correct, etc?
Click to expand...
Click to collapse
I did do it as Goods/Services. I have now had to escalate it from a dispute to a claim since he refused the refund. He now has until the 14th to review that then PayPal must look it over before I could get a refund.
I wonder why I am the only one this has happened to. I haven't seen any others saying their codes failed.
bravesfan171 said:
I did do it as Goods/Services. I have now had to escalate it from a dispute to a claim since he refused the refund. He now has until the 14th to review that then PayPal must look it over before I could get a refund.
I wonder why I am the only one this has happened to. I haven't seen any others saying their codes failed.
Click to expand...
Click to collapse
Did you try and run the "fastboot oem get_unlock_data" command first? If not, give that a shot first, and then re-try your code you received.
bravesfan171 said:
I did do it as Goods/Services. I have now had to escalate it from a dispute to a claim since he refused the refund. He now has until the 14th to review that then PayPal must look it over before I could get a refund.
I wonder why I am the only one this has happened to. I haven't seen any others saying their codes failed.
Click to expand...
Click to collapse
Others have reported unsuccessful codes but according to them they were able to get their refund in a timely fashion.
classic757 said:
Others have reported unsuccessful codes but according to them they were able to get their refund in a timely fashion.
Click to expand...
Click to collapse
Really? Could you point me to that? I'd be interested to check and see how they did that. Thanks!
bravesfan171 said:
Really? Could you point me to that? I'd be interested to check and see how they did that. Thanks!
Click to expand...
Click to collapse
See posts #'s 828 and 829 on this link: http://forum.xda-developers.com/moto-x/general/china-middleman-t2751177/page83
and post #867 on this link: http://forum.xda-developers.com/moto-x/general/china-middleman-t2751177/page87
classic757 said:
See posts #'s 828 and 829 on this link: http://forum.xda-developers.com/moto-x/general/china-middleman-t2751177/page83
and post #867 on this link: http://forum.xda-developers.com/moto-x/general/china-middleman-t2751177/page87
Click to expand...
Click to collapse
Yeah I have seen those. The difference is, he told them he did not have a code for them. He gave me a code that did not work, and since he already paid the source to get the code that he believes should work, he doesn't want to give me a refund.
Finally got my refund back after I escalated it to a claim. I might try it again sometime later down the road. If anyone successfully unlocks a mid June build date X, PLEASE let me know!! Thanks!
Every time I try the IMEI and MEID, the site says "Unable to retrieve device information. Please confirm IMEI/MEID number and try again.". I tried to go through support chat, but they need to escalate it for further review. I had tried multiple browsers, cleared cache/history... Bought directly from Moto and working on Verizon.
Trying to get Moto Care for N6, any thoughts on the issue?
Thanks!
I am having the same problem. I contacted Motorola and they said they put in a ticket for this and will contact me in a few days. Anyone else have the same issue or got this resolved some how?
Just did mine and it worked fine.
soulreaver99 said:
I am having the same problem. I contacted Motorola and they said they put in a ticket for this and will contact me in a few days. Anyone else have the same issue or got this resolved some how?
Click to expand...
Click to collapse
Just got off the phone with them and they promised a call or email back within 48 hours. I cannot seem to register my device either. Pretty frustrating since I really want to protect this $770 investment ASAP.
Edit: Not sure if this has anything to do with it, but I also noticed that before I unlocked and rooted my device that the bootloader showed that it was modified. I wonder if this was somehow a test unit or refurbished unit that someone had previously unlocked?
Mine works now. Takes a day or two for some reason
soulreaver99 said:
Mine works now. Takes a day or two for some reason
Click to expand...
Click to collapse
Confirmed, mine is working now as well. Weird that it takes a few DAYS for this to work
skaforey said:
Just got off the phone with them and they promised a call or email back within 48 hours. I cannot seem to register my device either. Pretty frustrating since I really want to protect this $770 investment ASAP.
Edit: Not sure if this has anything to do with it, but I also noticed that before I unlocked and rooted my device that the bootloader showed that it was modified. I wonder if this was somehow a test unit or refurbished unit that someone had previously unlocked?
Click to expand...
Click to collapse
No that's how they come from the factory. My first and second Nexus 6's had that message. When you relock the BL it disappears.
Quick question- if I get this phone from Verizon, can I run `fastboot oem unlock` on it to unlock the bootloader?
The reason I ask is that everything I've read online tells me that I can, but I just talked to some customer service reps at a Verizon store nearby who insisted that I couldn't (kind of--they never really answered my question). They practically got in a fist fight with me when I asked them; it was the weirdest thing--I just asked that one question, and they acted like I pulled a gun on them and practically threw me out of the store. I've never been treated anything close to that bad as a customer in my life; I was speechless.
Since I couldn't get an answer from them, does anyone here have one?
yes. its a nexus, and thats part of being a nexus
VZW reps stink. BOn the other hand, what you were asking them is how to void your warranty. So of course you got treated that way.
As said, it is Nexus device.
Code:
fastboot oem unlock
to your hearts content. Just remember to enable oem unlock and adb debugging in developer options.
Yes you can. Just cause its on Verizon doesn't mean anything. On the old galaxy nexus you could unlock the bootloader using that command. Same here. I unlocked mine within minutes of buying it. Unlocked it, flashed the supersu zip by chainfire, then flashed the newest TWRP using the fastboot flash recovery filename.img command. Good to go. The only thing I can't do is get xposed framework to work. Ugh. Making me mad.
I just want to clarify some things. So all the Roms, kernels and recoveries will work on the Verizon variant?
highdro said:
I just want to clarify some things. So all the Roms, kernels and recoveries will work on the Verizon variant?
Click to expand...
Click to collapse
Yes. Unlike other devices, every version of the Nexus 6 is exactly the same. All the chipsets, radios, etc. All these roms will work on our device.
nicholi2789 said:
Yes. Unlike other devices, every version of the Nexus 6 is exactly the same. All the chipsets, radios, etc. All these roms will work on our device.
Click to expand...
Click to collapse
OK cool. I just didn't know if anything needed to be updated to work with our phones since it is on 5.1 out of the box.
Thanks a ton guys! Awesome, it'll work. I was 99% sure I could unlock it (cf. "Don't be evil"), but the semi-coherent things the Verizon reps were saying were making me doubt.
Yeah, I could care less about voiding my warranty, but the reps didn't seem to be in the mood for me to say that haha.
I honestly don't believe unlocking the boot loader voids the warranty. Googles own instructions to update your system include unlocking your boot loader.
Sent from my Nexus 6 using XDA Premium HD app
Intub8 said:
I honestly don't believe unlocking the boot loader voids the warranty. Googles own instructions to update your system include unlocking your boot loader.
Sent from my Nexus 6 using XDA Premium HD app
Click to expand...
Click to collapse
Even if it did you can simply lock it and nobody knows otherwise
Sent from my Nexus 6 using XDA Free mobile app
Xposed is not compatible with any version of Lollipop 5.X unless something has changed recently. Having just gotten the 6 after running what seemed like forever on a non rooted Note 4 I'm a little rusty..
Verizon reps are probably butt holes because there are so many people bringing their phones in that are in boot loops because they are screwing with them not knowing what they're doing. If I worked at the Verizon store I would tell people it didn't work either. I'm certain it would save me time and effort in the future.
PSA: if you relock your Nexus 6 at the wrong time you will be in a boot loop. unless you're a secret agent or returning your phone for some reason just leave it unlocked
Sent from my Google N6 on VZ
It's Alive!
Alright I just bought it and unlocked it in two minutes lol.
I just turned on Developer Options, turned on "USB Debugging" and "Enable OEM Unlock", plugged it into my computer, ran `adb devices` and checked the box on the popup dialog on my phone in order to allow USB debugging with my computer, ran `adb reboot bootloader`, and then ran `sudo fastboot oem unlock` and hit the power button. Way too easy.
I just did in two minutes what I couldn't do in two years with my Galaxy Note II. Google's so awesome. :highfive:
Last week I went with my mom to get her a new cellphone.
She had the 1st Droid turbo.
She goes ahead and gets a new droid z force and get her stuff transferred from the turbo to the z force.
I take her old Turbo and they put my sim in and we leave.
The first time I powered it off then back on I get the "warning unlocked bootloader"
I've factory reset it and I still get the warning unlocked bootloader for about 15 seconds after powerup.
It was a replacement under their free cracked screen policy.
Its on the 49 firmware without me updating anything.
Did Verizon unlock it before transfering the data from it to her Zforce and forget to relock it?
Probably did do the update. As for the warning, what does the screen read in fastboot startup? Doubtful they forgot to relock, as it's not a repetitive process.
So was the bootloader unlocked before the upgrade or did you only notice it after.
Jacked Burton said:
Last week I went with my mom to get her a new cellphone.
She had the 1st Droid turbo.
She goes ahead and gets a new droid z force and get her stuff transferred from the turbo to the z force.
I take her old Turbo and they put my sim in and we leave.
The first time I powered it off then back on I get the "warning unlocked bootloader"
I've factory reset it and I still get the warning unlocked bootloader for about 15 seconds after powerup.
It was a replacement under their free cracked screen policy.
Its on the 49 firmware without me updating anything.
Did Verizon unlock it before transfering the data from it to her Zforce and forget to relock it?
Click to expand...
Click to collapse
Saved you $25. You can get rid of the warning, very easily. There's lots of threads to replace that graphic.
zys52712 said:
So was the bootloader unlocked before the upgrade or did you only notice it after.
Click to expand...
Click to collapse
My ma know [email protected] all about this stuff.
Somewhere between her getting a replacement droid and Verizon store transfering her "stuff" to the moto z, My new Turbo's bootloader is unlocked while having the unlockable 49
ChazzMatt said:
Saved you $25. You can get rid of the warning, very easily. There's lots of threads to replace that graphic.
Click to expand...
Click to collapse
Yeah I understand that.
But how did it get unlocked in the first place is what I want to know.
I just figured there would be a logical explanation.
I'm no programmer,but I know some of yall are.
zys52712 said:
So was the bootloader unlocked before the upgrade or did you only notice it after.
Click to expand...
Click to collapse
It was my moms old phone.
She sure as hell didn't unlock it and would never cross paths with a person that would offer to for no reason.
I mean I did spend a couple of hours reading up on all this shiz.
My only guess is Verizon had to unlock it to transfer the data to the new phone(no clue if you would have to do that) then didn't relock bootloader
or
ALIENS
Jacked Burton said:
It was my moms old phone.
She sure as hell didn't unlock it and would never cross paths with a person that would offer to for no reason.
I mean I did spend a couple of hours reading up on all this shiz.
My only guess is Verizon had to unlock it to transfer the data to the new phone(no clue if you would have to do that) then didn't relock bootloader
or
ALIENS
Click to expand...
Click to collapse
If the bootloader gets unlocked, the phone usually gets wiped, and I don't see why they would need to unlock it to transfer the data. My guess would be that the phone came unlocked when you got the replacement and somehow missed it.
zys52712 said:
If the bootloader gets unlocked, the phone usually gets wiped, and I don't see why they would need to unlock it to transfer the data. My guess would be that the phone came unlocked when you got the replacement and somehow missed it.
Click to expand...
Click to collapse
kinda where i was leaning.
But I wish it was ALIENS or a conspiracy