[LOLLIPOP WARNING]Those Who Unlocked Via Sunshine or Purchasing a Code from China - Moto X General

There is an Enable OEM Unlock option that is appearing in the Developer Options of the N6 and MX14 running 5.1 and if it is not checked, you cannot unlock your bootloader. If you unlocked via Sunshine or purchased a code for your device from the Chinese code seller, we do not know what is going to happen wrt this Enable OEM Unlock option for your phone if you upgrade to 5.1.
Until we do, it is safest to not upgrade and stay unlocked until 5.1 drops and the situation becomes clearer.

JulesJam said:
There is an Enable OEM Unlock option that is appearing in the Developer Options of the N6 and MX14 running 5.1 and if it is not checked, you cannot unlock your bootloader. If you unlocked via Sunshine or purchased a code for your device from the Chinese code seller, we do not know what is going to happen wrt this Enable OEM Unlock option for your phone if you upgrade to 5.1.
Until we do, it is safest to not upgrade and stay unlocked until 5.1 drops and the situation becomes clearer.
Click to expand...
Click to collapse
I don't think this is going to be an issue. People said in the N6 forums that they were able to unlock via fastboot without ever changing that setting in developer options. They hadn't even booted the phone into Android yet, just took it out of the box, put it in fastboot and unlocked.
I can't imagine the OTA would lock the bootloader, but who knows...

fury683 said:
I don't think this is going to be an issue. People said in the N6 forums that they were able to unlock via fastboot without ever changing that setting in developer options. They hadn't even booted the phone into Android yet, just took it out of the box, put it in fastboot and unlocked.
Click to expand...
Click to collapse
But others relocked after unlocking and didn't check the box then flashed something, ended up in a bootloop and were unable to unlock again to repair their phones.
Regardless, you cannot rely on what happens with a Nexus device. These MX13's were never intended to have unlockable bootloaders, whereas the Nexi were intended to have unlockable bootloaders.
fury683 said:
I can't imagine the OTA would lock the bootloader, but who knows...
Click to expand...
Click to collapse
I don't think it will relock the bootloader either. I am more concerned about those who relock then take the update not realizing that they will not be able to unlock again.

JulesJam said:
These MX13's were never intended to have unlockable bootloaders, whereas the Nexi were intended to have unlockable bootloaders.
Click to expand...
Click to collapse
Except the Developer Edition units that are identical in every way to the retail versions, but the unlock code is obtainable.
Regardless, I will wait until the process is confirmed and use the same process that I did to update from 4.4.2 to 4.4.4. Reflash stock /recovery and a clean /system, take OTA, then reflash TWRP and flash SuperSU. I value my root to much to risk it.
Didn't intend to say you were wrong in my first post, just that people had the same thoughts when the N6 came out and it wasn't a problem. People freaked out when My Verizon updated a while back and it requested root permissions, too. It's an abundance of caution, I get it.

fury683 said:
Except the Developer Edition units that are identical in every way to the retail versions, but the unlock code is obtainable.
Click to expand...
Click to collapse
The GSM Dev Ed is not identical to the AT&T MX13. But still, so what? None of us know how this is going to be implemented in 5.1. We can speculate all we want but we will know for sure once it is released.
fury683 said:
Regardless, I will wait until the process is confirmed and use the same process that I did to update from 4.4.2 to 4.4.4. Reflash stock /recovery and a clean /system, take OTA, then reflash TWRP and flash SuperSU. I value my root to much to risk it.
Click to expand...
Click to collapse
Rather than take the OTA, I would use Motorola Device Manager to upgrade - it leaves a copy of the fxz on your computer.

fury683 said:
, just that people had the same thoughts when the N6 came out
Click to expand...
Click to collapse
No, they could not have had the same thoughts as the N6 was always an unlockable device. You don't have to use Sunshine or purchase an unlock code to unlock the N6. So whatever thoughts anyone has had about the Enable OEM Unlock feature wrt how it would work with the N6 have nothing at all to do with this thread. The situations are totally different.
fury683 said:
and it wasn't a problem
Click to expand...
Click to collapse
On the contrary - it has been quite a problem for a lot of people with N6's who relocked their bootloaders. That is well documented on the N6 forum.

Why would I relock my bootloader to take the OTA? Why would I relock for any purpose?

Running the soak test of Android 5.1 and there is no Enable OEM Unlock option on it..

Saythis said:
Running the soak test of Android 5.1 and there is no Enable OEM Unlock option on it..
Click to expand...
Click to collapse
The option only appears when you update to 5.1 with your bootloader locked.

fury683 said:
Except the Developer Edition units that are identical in every way to the retail versions, but the unlock code is obtainable...
Click to expand...
Click to collapse
Most would expect that for those Moto freely gives away the bootloader unlock code for (on their web site), should be ok and not impacted. At least that is what we hope, otherwise Moto could have a bunch (maybe a small bunch) of angry users on their hand
But the thought about a warning or caution was directed toward those with ATT, Republic Wireless, or Verizon (non-dev) units who either purchased their bootloader unlock code from the China seller (or middle man) when it was available, or used Sunshine in order to bootloader unlock... since those devices were not ever intended to be bootloader unlocked.... There is uncertainty over this new "check box" in the rom. Moto could leave it out for those models (especially since ATT and RW use their own roms, VZW could be a little trickier since all XT1060's, dev and non-dev use the same rom), and if so, how does that impact any user who had a code and didn't use it yet, or unlocked, and might later want to relock for some reason.
For Sunshine, the concern would be due to changes in the phone's bootloader, TZ, or other parts that might be included in the update which might close that exploited vulnerability down. Think back to how some of the early Root/WPDisable processes were said to be "permanent" only to find they were NOT when the next OTA came out and "un-did" the hack.
So yeah, as you said...
fury683 said:
It's an abundance of caution, I get it.
Click to expand...
Click to collapse

superkeest said:
Why would I relock my bootloader to take the OTA? Why would I relock for any purpose?
Click to expand...
Click to collapse
Some people relock b/c they think it is more secure if they lose their phone or it gets stolen.

it leaves a copy of the fxz on your computer.

sseuorosal said:
it leaves a copy of the fxz on your computer.
Click to expand...
Click to collapse
Motorola Device Manager does, yes if you upgrade using MDM, you will have a copy of the fxz on your computer.

Any Updates on this situation?
It's almost been a month. Has anything new been discovered? I'd like to know if I can update to 5.1.

dont know about 5.1 but when i flashed 4.4.4 removing cm 12.1 on my att moto x it didnt relock my bootloader hope this stays same with 5.1 i used sunshine to unlock.

Icon000 said:
It's almost been a month. Has anything new been discovered? I'd like to know if I can update to 5.1.
Click to expand...
Click to collapse
The 5.1 OTA for ATT, Republic Wireless and Verizon hasn't been available yet, so I doubt anyone has tried it.
The only ones upgrading to 5.1 right now are those with a bootloader that is unlockable via code from Moto's web site.
I haven't seen Jcase, Beaups, or anyone related to Sunshine make any comments.

Further... I asked in the Sunshine thread...
See JCASE's response -> http://forum.xda-developers.com/showpost.php?p=61503326&postcount=3529

I have an XT1060 (VZW), unlocked via Sunshine. I recently switched to T-Mo, and although the VZW build worked fine, I wanted Lollipop, so I flashed the stock T-Mo 4.4.4 build, and then sideloaded the 5.1 update. I am still unlocked and everything is working fine. I'm not sure if this totally mimics your situation, but I can say that the 5.1 update rolling out to T-Mobile doesn't affect the bootloader status for Sunshine unlocked devices.

breakthestatic said:
I have an XT1060 (VZW), unlocked via Sunshine. I recently switched to T-Mo, and although the VZW build worked fine, I wanted Lollipop, so I flashed the stock T-Mo 4.4.4 build, and then sideloaded the 5.1 update. I am still unlocked and everything is working fine. I'm not sure if this totally mimics your situation, but I can say that the 5.1 update rolling out to T-Mobile doesn't affect the bootloader status for Sunshine unlocked devices.
Click to expand...
Click to collapse
Exactly what I've done, converted my mother's Sunshine unlocked BL Verizon Moto X into a T-Mobile one. I'm waiting for the OTA instead of sideloading to see how things go. I'm guessing by your experience she shouldn't have any problems taking the OTA update to 5.1.

Maverick-DBZ- said:
Exactly what I've done, converted my mother's Sunshine unlocked BL Verizon Moto X into a T-Mobile one. I'm waiting for the OTA instead of sideloading to see how things go. I'm guessing by your experience she shouldn't have any problems taking the OTA update to 5.1.
Click to expand...
Click to collapse
How did you convert it, I'm considering converting my att moto x to retail version. Btw its bootloader is unlocked

Related

Why one should never unlock the Motorola Razr HD bootloader (xt925) !

The pro & cons of unlocking the bootloader:
Pro: Install customs ROMS with custom kernels (basically that's it)
Cons: - Loosing warranty from Motorola & your carrier
- No more firmware upgrades (your IMEI is dropped out of Motorola databank)
- Little verity of quality custom ROMs or development (close to none) exist for the Razr HD
- Future upgrade to JB & KLP will never happened (this phone is listed as a potential candidate for KLP update)
- Keeping your xt925 beyond your 1 year warranty will still guaranty, a steady upgrades of firmware
- Can root a phone with bootloader locked (without loosing warranty - root is reversible)
- Legally (Motorola binding Bootloader unlock contract), you can't sell a BL unlock Motorola Razr HD phone !
If someone can add some Pro's to an unlock bootloader please do it..
Are you sure about the firmware upgrades? I read somewhere that's not the case.
I wish I had known all this before I unlocked my phone.
Are you sure about the firmware upgrades? I read somewhere that's not the case.
Click to expand...
Click to collapse
I spoke to Motorola & my carrier services, also read the warning details before the unlock process begins.
I wish I had known all this before I unlocked my phone
Click to expand...
Click to collapse
Same here..(I learned all that after the fact)
I'd add this to Pro:
If you're stuck on Rogers 49003 ICS because you flashed the ROM trying to get root, your best option to get anything above 4.0.4 is to unlock bootloader?
Perhaps a CWM install will be possible for those with unlocked bootloaders when updates come.
It seems that in one form or another an unlocked bootloader means being able to push all the new files in doesn't it? Is there any limitation on this phone, for example flashing a new modem or kernel?
Cons one by one:
itzik_man said:
- Loosing warranty from Motorola & your carrier
Click to expand...
Click to collapse
True, but obvious.
itzik_man said:
- No more firmware upgrades (your IMEI is dropped out of Motorola databank)
Click to expand...
Click to collapse
Nope. Even if you were not to receive OTA, which by the way is not true as I've observed on my Photon Q, you can still freely flash the new firmwares yourself ^^
itzik_man said:
- Little verity of quality custom ROMs or development (close to none) exist for the Razr HD
Click to expand...
Click to collapse
Depends on ones point of view. Usually a CM port means you get newer Android sooner.
itzik_man said:
- Future upgrade to JB & KLP will never happened (this phone is listed as a potential candidate for KLP update)
Click to expand...
Click to collapse
Why it wouldn't? Unlocking BLs has no impact on upgrade schedule.
itzik_man said:
- Keeping your xt925 beyond your 1 year warranty will still guaranty, a steady upgrades of firmware
Click to expand...
Click to collapse
No. That's solely on Moto / Google decision. They don't have to update it at all. (See Droid 3, Milestone 3, Motorola XT720 etc.)
itzik_man said:
- Can root a phone with bootloader locked (without loosing warranty - root is reversible)
Click to expand...
Click to collapse
Yes, although you have to be careful, because there are scirpts checking if you're rooted.
itzik_man said:
- Legally (Motorola binding Bootloader unlock contract), you can't sell a BL unlock Motorola Razr HD phone !
Click to expand...
Click to collapse
You can sue Moto for breaking laws. They can't forbid you doing that (don't know honestly how is that in US / Canada, but I doubt that seeing how it works with computer games).
So please, while for normal user not willing to flash custom ROMs it's true that they should not unlock the bootloader, don't spill nonsenses around that. It's just that when you unlock your bootloader, you're on your own when playing with the firmware. But when you have stock firmware back on it, nothing prevents you from getting the OTA.
don't spill nonsenses around that. It's just that when you unlock your bootloader, you're on your own when playing with the firmware. But when you have stock firmware back on it, nothing prevents you from getting the OTA.
Click to expand...
Click to collapse
Possible 90% of your response represent just false theories..
OTA is goneforever once you unlock your bootloader ! If & when you be able manually to install JB, still your IMEI (not registered with Motorola) wont OTA.
You can sue nobody ! it's a contractual agreement you "sign" when you agree to unlock BL !
And if you can't OTA, No future auto upgrades.
So, before you use a statement "don't spill nonsense" make sure you are talking sense...
At least on my O2 Germany xt925 I got the update OTA from ICS to JB after unlocking. Had to return to the stock bootloader because the OTA relies on it after rebooting though.
itzik_man said:
Possible 90% of your response represent just false theories..
OTA is goneforever once you unlock your bootloader ! If & when you be able manually to install JB, still your IMEI (not registered with Motorola) wont OTA.
You can sue nobody ! it's a contractual agreement you "sign" when you agree to unlock BL !
And if you can't OTA, No future auto upgrades.
So, before you use a statement "don't spill nonsense" make sure you are talking sense...
Click to expand...
Click to collapse
Once again.
A) The reason why the page says "no updates" is beacuse OTA updates only work when you're on stock firmware, which is unlikely when you have the bootloader unlocked. That's all.
B) There are things that such "agreement" cannot contain. Being unable to sell the phone is one of them in most countries.
I disagree from the op.
Every change to device firmware compromises the warranty, not just bootloader, read the agreements ... If you exploit a bug to have root access, you will have to fool everyone who will have contact with your phone so they don't see what you have done. Even if you try to "reverse" the root, you(or the program you use) will always leave a trace.
We should be promoting "unlock the world"
This is not to imply everything should be free, however if I own something it should be mine in every regard, that includes breaking it.
Sent from my Galaxy Nexus using Tapatalk 2
---------- Post added at 03:13 PM ---------- Previous post was at 03:12 PM ----------
@skrilax thanks for you work on the a500.
Sent from my Galaxy Nexus using Tapatalk 2
I have xt925, first thing I did was unlock boot loader. Then I updated ota to Telstra JB. OP is misleading people.
Once again.
A) The reason why the page says "no updates" is beacuse OTA updates only work when you're on stock firmware, which is unlikely when you have the bootloader unlocked. That's all.
B) There are things that such "agreement" cannot contain. Being unable to sell the phone is one of them in most countries.
Click to expand...
Click to collapse
To end my part in this discussion: The limitations, restrictions & disadvantages of unlocking the bootloader are much greater then any benefit or gain under the current availability of development !
Darbness said:
I have xt925, first thing I did was unlock boot loader. Then I updated ota to Telstra JB. OP is misleading people.
Click to expand...
Click to collapse
Have you tried out lte tethering? It doesn't work on Rogers.
To epinter -
I disagree from the op.
Every change to device firmware compromises the warranty, not just bootloader, read the agreements ... If you exploit a bug to have root access, you will have to fool everyone who will have contact with your phone so they don't see what you have done. Even if you try to "reverse" the root, you(or the program you use) will always leave a trace.http://www.linuxmobile
Click to expand...
Click to collapse
I did not notice your response at first, now to the point -
Without any disrespect to the work, time & effort invested, the main point is being ignored by the developers: All comments I got on this OP didn't touched the number one reason of my suggestion to not unlock the bootloader: There in not really enough of a variety of development options today to justification the bootloader unlocked of the xt925.
Skrilax_CZ said:
Cons one by one:
Yes, although you have to be careful, because there are scirpts checking if you're rooted.
Click to expand...
Click to collapse
Can someone elaborate on this point; I read in another thread that when you remove all rooted apps and data, clear out the files left in /system, that there is still info stored stated if the device has ever been rooted, and that this can be cleared using an app on a PC (don't remember which) however when I looked at the app it was specific to the XT926 and thus I wouldn't be able to use it.
After a thorough clean of every rooted app and everything left behind by rooted apps, is there a known way (or assumed to be working way) on XT925 to erase the record of the root.
Also, assuming I was to get my phone back to that state and remove proof of root, what specifically do I need to do in order to be careful as stated... or is epinter correct in saying that there is always a trace left behind, and if so, is this a blatant trace or something that hasn't been of much concern for Motorola in the past when servicing phones?
Tombs1234 said:
At least on my O2 Germany xt925 I got the update OTA from ICS to JB after unlocking. Had to return to the stock bootloader because the OTA relies on it after rebooting though.
Click to expand...
Click to collapse
How would I return to a stock bootloader if I were to unlock mine and an OTA didn't work? How did you do it?
itzik_man said:
The limitations, restrictions & disadvantages of unlocking the bootloader are much greater then any benefit or gain under the current availability of development !
Click to expand...
Click to collapse
It's your decision whether to unlock the bootloader or not. I'm just saying (for other users) that many of the cons you wrote were absolutely incorrect.
PantsDownJedi said:
Can someone elaborate on this point; I read in another thread that when you remove all rooted apps and data, clear out the files left in /system, that there is still info stored stated if the device has ever been rooted, and that this can be cleared using an app on a PC (don't remember which) however when I looked at the app it was specific to the XT926 and thus I wouldn't be able to use it.
After a thorough clean of every rooted app and everything left behind by rooted apps, is there a known way (or assumed to be working way) on XT925 to erase the record of the root.
Also, assuming I was to get my phone back to that state and remove proof of root, what specifically do I need to do in order to be careful as stated... or is epinter correct in saying that there is always a trace left behind, and if so, is this a blatant trace or something that hasn't been of much concern for Motorola in the past when servicing phones?
Click to expand...
Click to collapse
I believe there is something stored in the pds partition. Or at least it is that way on Droid RAZR XT912 and you had to fix it to remove the remaining traces. Flashing FXZ is also a way how to get a clean stock firmware, but pds partition is not affected that way.
PantsDownJedi said:
How would I return to a stock bootloader if I were to unlock mine and an OTA didn't work? How did you do it?
Click to expand...
Click to collapse
I think he meant "stock firmware" instead of "stock bootloader"
So if that were the case on this phone, I wonder if doing a dd backup of the pds partition before rooting at ICS, for restoring after downgrade, would be the way to go. Assuming it restores properly, it would be a good thing to add to the sticky thread about rooting. I did a dd of all my partitions except for /data last night, but I'm already rooted.
hmm... I'm wondering if there's something inaccessable in /system or even the sdcard since they get mounted with fuse. My only other Android phone was the Galaxy S II which was pretty straightforward and dead simple to root and unroot. I was surprised to see the fuse module being used to mount anything when I got this one.
The original topic is here: http://forum.xda-developers.com/showthread.php?t=1857558
I don't know if there was a proper fix developed (haven't checked) on the RAZR.

[BootLoader/Root Discussion] No Bounty, Just plain discussion

Okay we have a Bounty thread... Leave that for just plain Bounty pledges..
In here feel free to talk about BootLoader discusions, Root discussions..
Nice thread. Would be nice to discuss about Moto Maxx root as well. Since it has unlockable bootloader, I believe root is pretty doable, but I have no idea how to, since there's no custom recovery yet.
Nice thread.... looking forward
[ ]'s
some one knows how can we help to find a exploit or something that will make our Turbo able to get root??
When lollipop gets released for the Turbo, I'm going to have a tough decision. I really want that sweet new lollipop, but I also know that the chances of rooting it will go down significantly. So, the question is, should we stay on KitKat in hopes of getting root? It's going to be really hard to resist 5.0. And since the 2014 Moto X just got it, I think we're not far behind.
There's a vulnerability in KitKat, we just have to figure out how to exploit it. CVE-2014-7911. More info can be found at http://seclists.org/fulldisclosure/2014/Nov/51.
Your chances of getting root with LP and a locked bootloader depend on an exploit which has yet to be found and that may be some time and on some phones has never happened on previous operating systems. You would be much better off if the phone was released for unrestricted world wide sales but being CDMA and a Verizon exclusive is guaranteed to prevent the large scale adoption that would have made it more attractive to developers. Realistically no one here knows better than you whether root is more important than getting LP are for you. For my purposes I consider root a must have while having no issues with kk which I like just fine which would make it an easy choice.
Correct me if I'm wrong, but can't we just revert to kitkat if an exploit is found?
http://forum.xda-developers.com/showthread.php?t=2929737
That's the factory firmware we could flash if need be.
madeiracam said:
Correct me if I'm wrong, but can't we just revert to kitkat if an exploit is found?
http://forum.xda-developers.com/showthread.php?t=2929737
That's the factory firmware we could flash if need be.
Click to expand...
Click to collapse
Maybe. With Qualcomm chips, it's possible to make reverting to an older version result in a hard brick. With Big Red's knowledge of what they can do, unfortunately, they might implement this "feature". Plus, a vulnerability has already been found. We just need to figure out how to exploit it.
madeiracam said:
Correct me if I'm wrong, but can't we just revert to kitkat if an exploit is found?
http://forum.xda-developers.com/showthread.php?t=2929737
That's the factory firmware we could flash if need be.
Click to expand...
Click to collapse
At least with my Motorola RAZR M, every time they had a big version upgrade they also upgraded the security partition (which would be incompatible with prior firmwares), making it impossible to downgrade without an unlocked bootloader.
Sent from my Droid Turbo.
I think I have an idea on how to obtain a bootloader unlock. It most likely will not work, though, as I highly doubt it would be this stupid simple. As I do not yet have a Turbo, could someone send me the result of "fastboot oem get_unlock_data"? PM it to me and I'll test my theory. I'll also need one from some other (model doesn't matter) Motorola device, too, that actually is eligible for official bootloader unlocking.
r3pwn said:
I think I have an idea on how to obtain a bootloader unlock. It most likely will not work, though, as I highly doubt it would be this stupid simple. As I do not yet have a Turbo, could someone send me the result of "fastboot oem get_unlock_data"? PM it to me and I'll test my theory. I'll also need one from some other (model doesn't matter) Motorola device, too, that actually is eligible for official bootloader unlocking.
Click to expand...
Click to collapse
I have both a Droid Turbo and a Motorola device that is eligible for bootloader unlocking, but I don't know if I can trust to give my oem unlock data if that is in any kind "dangerous" for me or my guarantee. Can you just give me a hint and I check it out?
josebama said:
I have both a Droid Turbo and a Motorola device that is eligible for bootloader unlocking, but I don't know if I can trust to give my oem unlock data if that is in any kind "dangerous" for me or my guarantee. Can you just give me a hint and I check it out?
Click to expand...
Click to collapse
Yeah, sure. I'll send I sent you a PM.
Do you still need this? I have a Turbo with a cracked screen um about to send back.
greekstile said:
Do you still need this? I have a Turbo with a cracked screen um about to send back.
Click to expand...
Click to collapse
Yes, but not if you're about to send it back. I'll get another one. I wouldn't be able to test if the unlock worked.
When I say send it back, I don't have to send it right away. If the unlock does work, I assume I could lock it back down before sending back?
greekstile said:
When I say send it back, I don't have to send it right away. If the unlock does work, I assume I could lock it back down before sending back?
Click to expand...
Click to collapse
With Motorola devices, I don't think it's possible. I think the qfuse gets permanently blown. I would send it back if I were you. This method probably won't work anyways.
EDIT: qfuse, stupid autocorrect
I'm willing to give it a shot. Just let me know.
r3pwn said:
With Motorola devices, I don't think it's possible. I think the cause gets permanently blown. I would send it back if I were you. This method probably won't work anyways.
Click to expand...
Click to collapse
i will help u too if needed
got a Droid turbo
danger2u said:
i will help u too if needed
got a Droid turbo
Click to expand...
Click to collapse
How does one have a Turbo that is eligible for unlocked bootloader? This sounds like candy covered in gold to me.

[UNLOCK] Bootloader unlock for MotoX 2014 via Sunshine!

Greetings!
As of today there is a method to completely unlock the bootloader on all variants (yes, this includes the Verizon and AT&T models). The one stipulation is you need to have root.
DISCLAIMER #0: This is NOT MY WORK. I'm merely posting steps to use other peoples' work (with permission) in order to achieve an unlocked device. Do not donate to me for this. Any donations sent to me for this post will be promptly returned and you will be publicly shamed, most likely Game of Thrones style, for not reading the entire OP and following directions.
DISCLAIMER #1: Unlocking your device is dangerous! I am in no way responsible for anything that happens to you, your device, your significant other, or any random person that you feel the need to harm after this destroys your device! You are making the decision to run these tools and you alone are responsible for the consequences!
DISCLAIMER #2: As of right now this method has ONLY been tested on variants running kitkat (4.4) roms/bootloaders. Do not be the first to try it on a lollipop version without first understanding the risks. If you try and successfully use this method on lollipop (5.x) please let me know so I adjust this post accordingly.
DISCLAIMER #3: Do not attempt to re-lock your bootloader after using Sunshine. It is unclear how the device will act and you may end up with one of these.
PREFACE:
- You're going to want adb and fastboot set up on your computer. If you don't know what these are, or don't know how to set them up, google it. Having these tools is insanely helpful anyway for debugging and getting logs for developers later. You're going to want these in the long run.
- This method in the end is going to set you back $25. Sunshine is the tool used to unlock the bootloader and the people that develop this spend insane amounts of time developing/breaking/buying devices. Trust me, its worth it.
- Enable Unknown sources in Settings > Security before starting
STEP 1: Root (This root method only works on 4.4. If you are already rooted, say via mofo or another method, you may skip to step 2)
- You just skipped to this step didn't you? Go read the disclaimers and the preface. They are extremely important.
- Root your phone using KingRoot (obviously click the image with the little android guy on it) mirror
Code:
adb install -r <filename>.apk
- Run it from your app drawer and follow the prompts. I did have it fail a couple times, if that happens, try rebooting and running it again. I also had it say it failed a couple times, but still was able to gain root by typing 'su' in an adb shell.
- KingRoot is a temp root, which means upon a reboot, you will lose root and need to run it again. That's fine for our purposes here, it gives us the in we need for the bootloader exploit (see step 2)
STEP 2: Unlock That Bootloader
- This step involves running an app called Sunshine. Download the apk from there and install it:
Code:
adb install -r <filename>.apk
- Again, this unlock will cost you a one time fee of $25, more info on their FAQ. There seems to be a lot of animosity about this, but in the end the choice is yours. An extreme amount of development time goes in to these types of exploits and these guys do a fantastic job. It is worth it.
- Follow the prompts, get out the wallet, and enjoy an unlocked bootloader!
STEP 3: Install a custom recovery
- This could be considered an optional step, but there's really no reason to go through all of this if you don't plan to do some custom things. Custom recovery allows you to install/backup/restore ROMs on your phone.
- Follow the instructions here now that you have an unlocked bootloader in order to install TWRP.
STEP 4: Enjoy!
- You now have a completely unlocked phone! Start installing roms, enjoy yourself! Be careful though! Make sure you are only flashing things that are known to work on this device.
SunShine 3.1.16 is out, better support for MotoX 2014, including custom roms
Just ran Sunshine 3.1.17 on my 5.1 XT1097 rooted via MoFo, device is unlocked and working flawlessly.
invisiblek said:
(This root method only works on 4.4. If you are already rooted, say via mofo or another method, you may skip to step 2)
Click to expand...
Click to collapse
Kingroot is available for MX14 XT1085 (Chinese MX14) running 5.1. Do you think it will work on a MX14 XT1096 running 5.1?
JulesJam said:
Kingroot is available for MX14 XT1085 (Chinese MX14) running 5.1. Do you think it will work on a MX14 XT1096 running 5.1?
Click to expand...
Click to collapse
Only way to know is try if okay with the risks.
We talked about it in the general thread. Sometimes it even works on other devices running 5.1.1 (even not officially supported). I cannot assume the risk being my only phone to try.
Visi0nofExcellence2 said:
There are posts of it working for other devices. It will fail a couple of times and then just work. Also cases where the phone won't boot anymore. More of the latter now.
Not attempting and I suggest others dont either. Risk outweighs rewards with this being my main phone.
Click to expand...
Click to collapse
Visi0nofExcellence2 said:
jcase said:
Kingroot shouldnt cause the phone to stop booting, odd. Thanks for makign the thread btw
Click to expand...
Click to collapse
Not bootng is horribly ambiguous wording on my part.
chicodelta said:
My shield is running 5.1..1. I tried kingroot 4.5, since others have reported success and now my tablet won't boot past the nvidia screen. Anyone else encountered this issue?
Click to expand...
Click to collapse
http://forum.xda-developers.com/shield-tablet/general/root-kingroot-t3112722/page4
Click to expand...
Click to collapse
JulesJam said:
Kingroot is available for MX14 XT1085 (Chinese MX14) running 5.1. Do you think it will work on a MX14 XT1096 running 5.1?
Click to expand...
Click to collapse
I tried it (several times). It doesn't.
Sent from my XT1096 using Tapatalk
I did mofo yesterday and did SunShine today, worked great. I had 5.0 on my 1096.
Sent from my XT1096 using XDA Free mobile app
Any known root methods for 5.1 yet? AT&T Moto X via OTA.
I have tried both kingroot and mofo. Neither work for the xt1097 att variant on 5.1. However looking on some pages on xda noticed that the xt1097 from Brazil has the same specs as the att variant. The files look pretty much the same as well. Do you think it would be possible to flash the 5.1 Brazil to the att without bricking? Bootloader is also the same. Flash the Brazil over the att and then try Motorola unlock tool online
christopher68369 said:
I have tried both kingroot and mofo. Neither work for the xt1097 att variant on 5.1. However looking on some pages on xda noticed that the xt1097 from Brazil has the same specs as the att variant. The files look pretty much the same as well. Do you think it would be possible to flash the 5.1 Brazil to the att without bricking? Bootloader is also the same. Flash the Brazil over the att and then try Motorola unlock tool online
Click to expand...
Click to collapse
No
Sent from my XT1096 using Tapatalk
christopher68369 said:
I have tried both kingroot and mofo. Neither work for the xt1097 att variant on 5.1. However looking on some pages on xda noticed that the xt1097 from Brazil has the same specs as the att variant. The files look pretty much the same as well. Do you think it would be possible to flash the 5.1 Brazil to the att without bricking? Bootloader is also the same. Flash the Brazil over the att and then try Motorola unlock tool online
Click to expand...
Click to collapse
It won't work. You can't flash the firmware from other carriers with a locked bootloader. It will fail when you try.
Sent from my XT1095 using Tapatalk
Only firmware you can flash with a locked bootloader has to contain the same signature of the firmware your on, which is literally only that firmware. EG. ATT 5.1 sig does not match any other sig.
Yes I realised that after doing research. Butbim wondering if we were able to change the cid to lets say the Brazil variant if we would be able to flash the firmware. If we could maybe change the cid from dfs software or GSM tools software and then try to flash the firmware if it would work. If someone knew how to change the cid without root I wouldn't mind trying it out to see if it would work. I'm planning on buying the moto x pure edition that comes out on Sept 2 but i f I was able to unlock the bootloader then I wouldn't really mind waiting on a new phone for another year since the moto x 2014 is really a great phone and with root has alot of potential
Same problem, you can't do that either without root and bootloader unlocked. There is no way to do it until someone can find a vulnerability in the 5.1 firmware. For now you are stuck.
Sent from my XT1095 using Tapatalk
I don't understand. Motorola officially provides the way to unlock bootloaders. Why does this method exist? Does this method help unlock bootloaders of devices that cannot be unlocked or something like that?
Yes, this is only for the Verizon xt1096 and the AT&T xt1097. Those 2 models cannot unlock their bootloader from motorola's website. This is a method to get around that and unlock it anyway.
Sent from my XT1095 using Tapatalk
So I have a Verizon model XT1096 running 5.0.
From the searches I've performed and from what I've read so far, Root can be achieved via Mofo (kingroot failed) and then I can unlock the bootloader via sunshine and then flash TWRP, flash a 5.1.1 ROM and I'm good to go?
There are several threads with a little info here and there, so I apologize for the questions. I just want to get my ducks in a row.
You are correct.
Sent from my XT1095 using Tapatalk
Ed Murray said:
So I have a Verizon model XT1096 running 5.0.
From the searches I've performed and from what I've read so far, Root can be achieved via Mofo (kingroot failed) and then I can unlock the bootloader via sunshine and then flash TWRP, flash a 5.1.1 ROM and I'm good to go?
There are several threads with a little info here and there, so I apologize for the questions. I just want to get my ducks in a row.
Click to expand...
Click to collapse
Kingroot said that it failed for me but sunshine still worked normally afterwards. If you haven't already paid for mofo then you can just pay for sunshine
Sent from my XT1095 using Tapatalk
Moto X 2013 (Verizon and ATT) got root on 5.1 with locked bootloader. Maybe we can use the same exploit?
http://forum.xda-developers.com/moto-x/general/root-moto-x-att-xt1058-5-1-lpa23-12-21-1-t3164125

Sprint S7 unlocked: Is there a way to update it safely?

Long time reader...first time poster
I bought an unlocked sprint s7 from ebay and it works like a dream and i was wondering if there was a safe method to update the phone WITHOUT ruining the unlock that the seller put on the phone.
Current software is update PC5 and i would love to benefit from security and bug fixes in new releases.
Thanks in advance!
nmarz3 said:
Long time reader...first time poster
I bought an unlocked sprint s7 from ebay and it works like a dream and i was wondering if there was a safe method to update the phone WITHOUT ruining the unlock that the seller put on the phone.
Current software is update PC5 and i would love to benefit from security and bug fixes in new releases.
Thanks in advance!
Click to expand...
Click to collapse
I always thought if a phone gets carrier unlocked it didnt matter what u did to it, it would stay unlocked. Unless the way he got it unlocked was thru a mod maybe that can b ruined. Im not sure
shooterlgk said:
I always thought if a phone gets carrier unlocked it didnt matter what u did to it, it would stay unlocked. Unless the way he got it unlocked was thru a mod maybe that can b ruined. Im not sure
Click to expand...
Click to collapse
Most likely not a carrier unlock do to a unlocked padlock during boot animation as well as samsung pay not working due to software mods that im guessing made it unlocked in the first place. Thanks for the reply!
nmarz3 said:
Most likely not a carrier unlock do to a unlocked padlock during boot animation as well as samsung pay not working due to software mods that im guessing made it unlocked in the first place. Thanks for the reply!
Click to expand...
Click to collapse
Yea ur safest bet is to keep it as it is so u wont lose that. No problem
nmarz3 said:
Most likely not a carrier unlock do to a unlocked padlock during boot animation as well as samsung pay not working due to software mods that im guessing made it unlocked in the first place. Thanks for the reply!
Click to expand...
Click to collapse
Bootloader unlock and sim unlock are two different things. You said it has an unlock pad on boot up screen. That means it's bootloader is unlocked. Which means if I am correct if it has a custom recovery you are unable to do future ota updates. Can and possibly brick your phone. You can flash a ton that has the new update no issues developers are usually fairly quick to update there rom on the latest ota.
marcviado said:
Bootloader unlock and sim unlock are two different things. You said it has an unlock pad on boot up screen. That means it's bootloader is unlocked. Which means if I am correct if it has a custom recovery you are unable to do future ota updates. Can and possibly brick your phone. You can flash a ton that has the new update no issues developers are usually fairly quick to update there rom on the latest ota.
Click to expand...
Click to collapse
Now my question is that since my phones bootloader is unlocked via custom software, would it be safe to root it and install custom roms that have the current updates? thanks
nmarz3 said:
Now my question is that since my phones bootloader is unlocked via custom software, would it be safe to root it and install custom roms that have the current updates? thanks
Click to expand...
Click to collapse
Yes! You are in the wrong forum though. You are on sprint but need to be with the enxyos forum ND running their tarp and roms
Have the same dilemma as OP.
unlocked on PC5 firmware with GCPro. No root was used
Should i update OTA or leave it be.
xronikus said:
Have the same dilemma as OP.
unlocked on PC5 firmware with GCPro. No root was used
Should i update OTA or leave it be.
Click to expand...
Click to collapse
I can confirm that updating over OTA will NOT screw with the unlock of the device. If your samsung pay does not work i would disable knox with a package disabler app to receive samsung pay in you new updated state.
OTA update from PC5 to PH7 on unlocked phone went smoothly.
Thanks
I have a unlocked Sprint S7 but im outside of America, is there any way i can update without losing the unlock? i don't want to end with an expensive brick.
Im stuck in G930PVPU2APC5 and i can't receive OTA updates
I bought unlocked sprint s7 that I'm using with metro PCS, but it's not letting me update the profile and because of that I'm not getting the wifi hotspot option. How do I get it to work?
@ThaDunder : You must initially do it manually over samsung smart switch then OTA will work @zirnitra : Sadly wifi tethering is not working for me either...no idea how to fix it =/ must be a symptom of the unlocking like wifi calling
nmarz3 said:
@ThaDunder : You must initially do it manually over samsung smart switch then OTA will work @zirnitra : Sadly wifi tethering is not working for me either...no idea how to fix it =/ must be a symptom of the unlocking like wifi calling
Click to expand...
Click to collapse
I already tried that, smart switch says there is no update available.

Updated software today - ads are back :(

I did the big update today for the newest software patch available for the Motorla G4.
My ads are back unfortunately.
Does anyone know if there's a tutorial to remove the ads for the latest version of the software update?
Thanks!!
topslop1 said:
I did the big update today for the newest software patch available for the Motorla G4.
My ads are back unfortunately.
Does anyone know if there's a tutorial to remove the ads for the latest version of the software update?
Thanks!!
Click to expand...
Click to collapse
I don't recall anyone getting an Amazon update. Sadly you did answer a question I'm sure all the Amazon G4 owners had.
I have the same experience - can we use the same process as before, or use the just posted factory image?
Was you rooted with unlocked bootloader? It just appeared for me as well. I want to update but don't want to relock bootloader but I do still have the original code from moto to unlock it I think.
brownd7380 said:
Was you rooted with unlocked bootloader? It just appeared for me as well. I want to update but don't want to relock bootloader but I do still have the original code from moto to unlock it I think.
Click to expand...
Click to collapse
If you're rooted you can't install an OTA but it doesn't matter if you're unlocked. Once you've used the unlock code from MOTO you're always unlocked and won't have to enter it again. If for some way they've managed to relock it on the Amazon ad phones then I would imagine they've also blocked it from a future unlock. In the past though once unlocked the bootloader is always unlocked.
I'm not locked to any specific carrier as far as I know.. purchased this off of Amazon for $125.. USA version.
topslop1 said:
I'm not locked to any specific carrier as far as I know.. purchased this off of Amazon for $125.. USA version.
Click to expand...
Click to collapse
I was talking about an unlocked bootloader.
Tel864 said:
I was talking about an unlocked bootloader.
Click to expand...
Click to collapse
gotcha, unfortunately these ones you can't unlock
You are more likely to find help in the Moto G4 section. This is Moto G4 plus, of which there is no Amazon variant.

Resources