IMPORTANT!
DO NOT USE THESE IMAGES/PACKAGES ON NON-DEVELOPER EDITION DEVICES OR ON DEVICES WITH A LOCKED BOOTLOADER.
Why wouldnt this work on a Moto X with a unlocked bootloader? I have a Rogers variant, with TWRP / Unlocked bootloader.. I'm assuming the modem files might be different but other then that there shouldn't be that much of a difference is there?
Tempted to try it out..
I have an unlocked bootloader GSM developer edition without any carrier branding and Cant find my factory image.
g2tegg said:
IMPORTANT!
DO NOT USE THESE IMAGES/PACKAGES ON NON-DEVELOPER EDITION DEVICES OR ON DEVICES WITH A LOCKED BOOTLOADER.
Why wouldnt this work on a Moto X with a unlocked bootloader? I have a Rogers variant, with TWRP / Unlocked bootloader.. I'm assuming the modem files might be different but other then that there shouldn't be that much of a difference is there?
Tempted to try it out..
Click to expand...
Click to collapse
Thanks for the video Heyitslou, is the developer edition GSM the same as the tmobile one? On motorola website it says "MOTO X, GSM Dev Edition: KK-4.4.2-KXA20.16-1.25_MR3 (Retail)"
and i saw on XDA firmware:
"Android 4.4.2 Blur_Version.161.44.25.ghost_row.Retail.en.US" where filename is similar with MR3 in it.
OK NEVERMIND. Motorola send me link to this file "TMO_RETAIL_XT1053_4.4.2-KXA20.16-1.25_MR3_CFC.xml.zip" for my developer edition GSM.
Related
[Tried posting this in Q&A forum but received no answers]
I am coming from Droid Incredible running CM 7.1 on PagePlus for 3 years (Verizon MVNO for those who don't know). So I am familiar with Android ecosystem and rooting.
I am looking to buy Moto X to be used in USA on H2O (AT&T MVNO) because on Pageplus the speed are limited to 3G and most new phones cannot be activated without flashing which I don't want to do.
1) Is there any reason NOT to buy Developer Edition (GSM Networks)? Current price is now the same as AT&T branded version and I am OK with just one color being available.
2) Am I correct in understanding that this version of the phone supports all LTE and HSPA frequencies both for AT&T and TMobile? Quote from the spec:
Networks
GSM/GPRS/EDGE - UMTS/HSPA + up to 42 Mbps - 4G LTE
2G/2.5G GSM/GPRS/EDGE bands
850/900/1800/1900 MHz
3G UMTS bands
850/900/ AWS/1900/2100 MHz with HSPA+ up to 42 Mbps (B5/B8/B4/B2/B1)
4G LTE bands
700/AWS/1900MHz (B17/B4/B2)
3) Are there any known issues with Moto X that has not been fixed with software updates yet? I am also considering Moto G which would be good enough for me but it has battery issues ("instant" drops from full charge to 1%) that are now investigated by Motorola but no solution yet. For Moto X so far I only found that some people have small cracks on their cases that are fixed by mailing it for warranty work.
1) I too considered the GSM Dev Edition of the Moto X but decided not to get it based on looks. I don't like white phones. The Dev Moto X has a woven white back and I didn't like that. I also have not use for 32GB of internal storage. I didn't even fill the 8GB that was on my RAZR M (previous phone). This was my reasoning, so I went with the MotoMaker GSM unlocked retail Moto X (also referred to as the T-Mobile version).
2)I don't know about the Dev version but if I had to guess I'd say it's like my phone, so yes. I have an AT&T SIM in my Moto X and I get 4G LTE when I'm in town.
3)The only issues I know of are the cracks as you mentioned and the some of the wood backs having a poor finish applied. There may be another that I've yet to read here but I've not had any problem with the phone.
Hikikomori-Otaku said:
1) I too considered the GSM Dev Edition of the Moto X but decided not to get it based on looks. I don't like white phones. The Dev Moto X has a woven white back and I didn't like that. I also have not use for 32GB of internal storage. I didn't even fill the 8GB that was on my RAZR M (previous phone). This was my reasoning, so I went with the MotoMaker GSM unlocked retail Moto X (also referred to as the T-Mobile version).
2)I don't know about the Dev version but if I had to guess I'd say it's like my phone, so yes. I have an AT&T SIM in my Moto X and I get 4G LTE when I'm in town.
3)The only issues I know of are the cracks as you mentioned and the some of the wood backs having a poor finish applied. There may be another that I've yet to read here but I've not had any problem with the phone.
Click to expand...
Click to collapse
I don't like white phones either but I want to be able to root. Is what you went with (MotoMaker GSM unlocked retail Moto X) essentially the same as Dev Edition other than color? Or is it only carrier unlocked but not bootloader unlocked?
JoeSchmoe007 said:
I don't like white phones either but I want to be able to root. Is what you went with (MotoMaker GSM unlocked retail Moto X) essentially the same as Dev Edition other than color? Or is it only carrier unlocked but not bootloader unlocked?
Click to expand...
Click to collapse
The main differences between the two would be the retail version can be customs made in MotoMaker and when the bootloader is unlocked you loose your warranty. The Dev version only comes in one style but your warranty will still be intact after unlocking the bootloader.
Hikikomori-Otaku said:
The main differences between the two would be the retail version can be customs made in MotoMaker and when the bootloader is unlocked you loose your warranty. The Dev version only comes in one style but your warranty will still be intact after unlocking the bootloader.
Click to expand...
Click to collapse
Thank you for responding. So the warranty will be void completely, even for the hardware issues completely unrelated to unlocking bootloader?
Can bootloader on retail version be re-locked to send it in for warranty?
I think I read that each time OS updates are released for Moto X new exploit may need to be found to root/unlock bootloader. Did I get it right or am I confusing something?
Can root be achieved without unlocking bootloader? If I understand correctly unlocking bootloader is really only needed if one wants to try different ROM-s and root can sometimes be achieved without unlocking bootloader. But Moto X is almost stock Android, so I see no point in trying other ROM-s but I do want to have root.
JoeSchmoe007 said:
Thank you for responding. So the warranty will be void completely, even for the hardware issues completely unrelated to unlocking bootloader?
Can bootloader on retail version be re-locked to send it in for warranty?
I think I read that each time OS updates are released for Moto X new exploit may need to be found to root/unlock bootloader. Did I get it right or am I confusing something?
Can root be achieved without unlocking bootloader? If I understand correctly unlocking bootloader is really only needed if one wants to try different ROM-s and root can sometimes be achieved without unlocking bootloader. But Moto X is almost stock Android, so I see no point in trying other ROM-s but I do want to have root.
Click to expand...
Click to collapse
Yes, your warranty will be completly void if you unlock the bootloader on any Moto X except the Dev version.
You can relock (and reunlock) the bootloader but because you have to get the unlock key from Motorola, they will know even if you relock it. I believe there is also a line in fastboot that will will indicate if the warrently is void (as a result of the first unlock).
This is true. With any update there is the potential for an exploit being 'removed'. The same is true for most bootloaders but not necessarily for this phone. Even if the bootloader is updated, the unlock code for your phone will still work.
Yes, root can be achieved without unlocking the bootloader but it's a complex method for this phone. It's much easier to unlock the bootloader, flash a custom recovery, and flash the SU binary. This is also the preferred method if it's avalible for your Moto X.
Unlocking your bootloader let's you do a few things. The most common it to flash another recovery image and thus a new ROM. You can also flash kernals, binaries, apps, and a few other things with the bootloader unlocked.
Hikikomori-Otaku said:
....
This is true. With any update there is the potential for an exploit being 'removed'. The same is true for most bootloaders but not necessarily for this phone. Even if the bootloader is updated, the unlock code for your phone will still work.
Yes, root can be achieved without unlocking the bootloader but it's a complex method for this phone. It's much easier to unlock the bootloader, flash a custom recovery, and flash the SU binary. This is also the preferred method if it's avalible for your Moto X.
Unlocking your bootloader let's you do a few things. The most common it to flash another recovery image and thus a new ROM. You can also flash kernals, binaries, apps, and a few other things with the bootloader unlocked.
Click to expand...
Click to collapse
So what specific exploit can be removed? For rooting? Or for unlocking bootloader? The way I understand one can always unlock bootloader using code from Motorola no matter if your phone is retail or Dev. Edition, however then root may or may not work? But this contradicts with what you said about if bootloader is unlocked then you can flash custom recovery and SU, so you can still always achieve root. Is there an FAQ or thread on this forum where this is described in details?
JoeSchmoe007 said:
So what specific exploit can be removed? For rooting? Or for unlocking bootloader? The way I understand one can always unlock bootloader using code from Motorola no matter if your phone is retail or Dev. Edition, however then root may or may not work? But this contradicts with what you said about if bootloader is unlocked then you can flash custom recovery and SU, so you can still always achieve root. Is there an FAQ or thread on this forum where this is described in details?
Click to expand...
Click to collapse
Any exploit can be removed, so long as they're found and will not inhibit the use of the device. I guess I should clarify a bit. Your bootloader and root access have different ways to get them. The bootloader basically protects the partitions of the phone. The only way to unlock the bootloader of the Moto X is to go to Motorola and get the unique unlock code for your Moto X. The Verizon retail and AT&T retail versions are the only two models of my knowledge that can't be unlocked by Motorola and no exploit has been found for them. How root is achieved by having an unlocked bootloader is as followed; The bootloader is unlocked giving the user access to the partitions of the phone > a custom recovery is flashed > using the new recovery SU binary is added (flashed) to the dormant Android OS. Without an unlocked bootloader, this method is impossible as you can't complete the first step. This is when an exploit in the Android OS is needed. The current SlapMyMoto exploit takes advantage that Motorola lets Moto X users downgrade. Once on a lower version of Android, we can root that and basically 'tunnel' up a path to give ourselves root in they newer version of Android. The unlocked bootloader method is preferred because it's easier and will almost always work (unless Android is given a huge remake). While in recovery, the Android OS is not loaded and thus can't protect itself. This makes adding stuff to it much simpler. When the Android OS is booted though, there are security measures in place that we unrooted can't get past without an exploit.
http://forum.xda-developers.com/showthread.php?t=2603358
This thread has a lot of good info from rooting on both locked and unlocked bootloaders, downgrading, and much more.
Honestly I think you answered your own question. If rooting is your number one priority and you don't mind the white back (which I like actually), then I think the Developer Edition is a no brainer for you.
If you want a custom phone and rooting isn't that important, or you don't care about the warranty, then I'd say get the MotoMaker version.
As far as bugs, the only bug I know of is an exchange bug (which I don't use exchange so I don't even know what the bug is/was), but it was fixed in 4.4.2.
You can root the carrier version ie motomaker. That's all you really need is root along with greenify, xposed, gravity box, and viper4android.
MOTO X Slapped
[email protected] said:
You can root the carrier version ie motomaker. That's all you really need is root along with greenify, xposed, gravity box, and viper4android.
MOTO X Slapped
Click to expand...
Click to collapse
Currently there is NO root method for 4.4.2 without unlocking the bootloader.
I checked the FIND YOUR DEVICE link where Motorola has "Can the bootloader on your device model be unlocked?"
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
I am not a developer and lack the skills to understand this process, but wondered if anyone has checked into this more.
nismopc said:
I checked the FIND YOUR DEVICE link where Motorola has "Can the bootloader on your device model be unlocked?"
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
I am not a developer and lack the skills to understand this process, but wondered if anyone has checked into this more.
Click to expand...
Click to collapse
You can only unlock the developer edition of the device through Motorola. Any others must be exploited.
Sent from my RAZR M on BlissPop Lollipop 5.0.2 from Tapatalk
xKroniK13x said:
You can only unlock the developer edition of the device through Motorola. Any others must be exploited.
Sent from my RAZR M on BlissPop Lollipop 5.0.2 from Tapatalk
Click to expand...
Click to collapse
I thought the same until I saw under the warnings...
"You have only yourself to blame. Unless you have a Developer Edition device, once you get the unlock code, your device is no longer covered by the Motorola warranty; in other words, please don't blame us if things go wrong, even if they appear unrelated to unlocking the bootloader."
This tells me all are unlockable, but only developer is warrantied once unlocked...
and this...
"Still undaunted? If you are ready to accept all the implications of unlocking the bootloader, which -except for Developer Edition devices- includes completely voiding your device's warranty, then let's get started."
nismopc said:
I thought the same until I saw under the warnings...
"You have only yourself to blame. Unless you have a Developer Edition device, once you get the unlock code, your device is no longer covered by the Motorola warranty; in other words, please don't blame us if things go wrong, even if they appear unrelated to unlocking the bootloader."
This tells me all are unlockable, but only developer is warrantied once unlocked...
and this...
"Still undaunted? If you are ready to accept all the implications of unlocking the bootloader, which -except for Developer Edition devices- includes completely voiding your device's warranty, then let's get started."
Click to expand...
Click to collapse
Some Motorola devices can be that are not developer editions, such as ones sold off-contract like the Moto X Pure Edition or the Moto G. However, since the M is a VZW device it cannot be. If you go through the process it just says that it cannot be unlocked.
Sent from my RAZR M on BlissPop Lollipop 5.0.2 from Tapatalk
it depends on what version of the razr your running OP.
i think the latest version, cannot be.
but if you havent updated you might be in luck
Hello,
My Moto X Play is linked with Nextel, how do I leave Retail?
I tried to install the ROM at retail RSD, but remains bound.
It's possible?
Thank you. :laugh:
Is your model XT1564? If yes you might search the forum under that number & LRA ("L"TE in "R"ural "A"merica) sometimes wrongly written as RLA. Don't know much about the whole thing, just trying to give you a starting point.
Sent from my XT1563 using Tapatalk
Mine is the XT1563.
PaganBlood said:
Hello,
My Moto X Play is linked with Nextel, how do I leave Retail?
I tried to install the ROM at retail RSD, but remains bound.
It's possible?
Thank you. :laugh:
Click to expand...
Click to collapse
you can flash another firmware just check the cid its form your country, you say you have nextel then you are from mexico like me then the cid you need its cid 12
no mather if its dual sim(ds) the firmware, in settings will appear the option for the dual sim but the sim 2 not working only 1 sim will detect
Hello.
I'm from Brazil . Already Unlock the Bootloader , and made the downgrade to 5.1.1 retail , and still got bond .
It looks like there's no way to remove .
of course you need to unlock the bootloader first if you want to install another firmware via fastboot
just remember your model and your area cid
I just tried it and I can actually request the unlock code, I won't unlock it until we get a functional TWRP but I just wanted to let you guys know. If the Mexican version is bl unlockable then the other international non-Verizon variants should be as well.
I have the Mexican AT&T Z Play too (XT1635-02) and I can confirm that the bootloader is unlockeable
Everything Motorola puts out is unlockable unless it's some scumbag carrier (Verizon) exclusive. Hopefully this device gets some attention from devs.
como puedo desbloquearlo amigo??
diegochiva95 said:
como puedo desbloquearlo amigo??
Click to expand...
Click to collapse
English only bro.
You can find the instructions on how to do it pretty much anywhere, just Google "Motorola bootloader unlock" and you'll find tutorial videos in Spanish on how to do it in a better way than I ever could.
Canadian Telus XT1635-02 unlockable bootloader confirm
next1989 said:
I have the Mexican AT&T Z Play too (XT1635-02) and I can confirm that the bootloader is unlockeable
Click to expand...
Click to collapse
How do you know? Can you see the button "Request unlock key" in the page or not?
I have it and can't unlock it please help
Sent from my XT1635-02 using XDA-Developers mobile app
I can confirm, I succesfully unlocked my Mexican att xt1635-02 without any trouble.
unlocked bootloader without a problem, MX AT&T variant
And everything's still working after that? Camera, telephone, etc.?
The bootloader is unlockable. I want to unlock the Network, can you recommend what to do? I have tried 4 unlocking services with no luck. Regards
weetz said:
The bootloader is unlockable. I want to unlock the Network, can you recommend what to do? I have tried 4 unlocking services with no luck. Regards
Click to expand...
Click to collapse
I would suggest you start a new thread with this (MZP Q&A), including phone ID (-02) and locked carrier - give this topic more visibility and hopefully someone will see it and give you a fix.
Hello everyone, for those in Mexico that still have the att version for moto z play, it's the oreo ota already available?
oMss said:
Hello everyone, for those in Mexico that still have the att version for moto z play, it's the oreo ota already available?
Click to expand...
Click to collapse
Yes it is. Actually since 2 months ago.
oMss said:
Hello everyone, for those in Mexico that still have the att version for moto z play, it's the oreo ota already available?
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
I adquired moto e4 Verizon variant, I know that this one can't be rooted cuz the bootloader is locked and can't flash customs roms too. BUT I want to flash retail rom, U know, I want my moto e4 without Verizon boot animation and vzn bloatware.
I'm usign this one: PERRY_VERIZON_NDQ26.69-23-2_cid2_subsidy-VZW_regulatory-DEFAULT_CFC.xml.zip
I want flash this: PERRY_RETAIL_7.1.1_NPQ26.69-41_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Regards
Whitchers said:
I adquired moto e4 Verizon variant, I know that this one can't be rooted cuz the bootloader is locked and can't flash customs roms too. BUT I want to flash retail rom, U know, I want my moto e4 without Verizon boot animation and vzn bloatware.
I'm usign this one: PERRY_VERIZON_NDQ26.69-23-2_cid2_subsidy-VZW_regulatory-DEFAULT_CFC.xml.zip
I want flash this: PERRY_RETAIL_7.1.1_NPQ26.69-41_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Regards
Click to expand...
Click to collapse
The bootloader probably won't let you flash anything other than the Verizon version
If anyone tried this please report back I'd really like to know the answer to this myself.