Database Users

Looking to buy Moto X, need some clarifications.

[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.

Samsung Galaxy S5 unlock bootloader Verizon to come eventually

Ive had the S5 since October and i just got around to rooting the Verizon version and putting safestrap on it i know there is rom for the verizon Galaxy S5 but my question is will there ever be a bootloader unlock method for the verizon and at&t versions of the S5 any thoughts because i dont feel safe flashing a rom on a locked bootloader i had a droid razr m before this phone i had the bootloader unlocked and was running cm11 i just wish i could flash a well know rom on my Galaxy S5

Most likely not. Verizon do sell a dev version of the phone with an unlocked bootloader and it's got CM thanks to albinoman and ktoonsez
Sent from my SM-G900F using Tapatalk

if ur not comfortable flashing roms on a locked BL (is safer) than buy a dev ed s5 or another device thats unlocked or just stay stock lol

ROMs? Mods? Where are the devs?

Just got this phone as a gift, and I love it.. but where is the community for this device? The development section is basically empty.
Sent from my XT1650 using XDA-Developers Legacy app

neh4pres said:
Just got this phone as a gift, and I love it.. but where is the community for this device? The development section is basically empty.
Sent from my XT1650 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Moto Z Force (Droid) has a LOCKED BOOTLOADER. Can't be rooted. It's a Verizon phone. No dev work possible.
Whereas the Moto Z (unlocked edition) has bootloader unlock on request and there's tons of ROMs and kernels, etc for it. You got the wrong phone, IF you wanted dev stuff... You need a phone where the bootloader can be unlocked and the phone rooted. Some Verizon phones' bootloaders can be unlocked through Sunshine exploits, but not that many. You have to do research here on XDA before you get the phone.
Now some people may have this Droid Moto Z Force phone and LOVE it, but yeah the dev sections are basically empty. No ROMs, no kernels. And there won't be any until the bootloader is unlocked -- IF ever.
The 2015 Droid Turbo 2 (Verizon's Kinzie variant) is in the same condition -- bootloader locked down, no dev work, while the sibling 2015 Moto X Force (unlocked Kinzie) has ROMs, etc. They both share the same XDA forum, so the Droid Turbo 2 owners can only look enviously at the Moto X Force dev work.
Blame Verizon for locking down the bootloader!

ChazzMatt said:
Moto Z Force (Droid) has a LOCKED BOOTLOADER. Can't be rooted. It's a Verizon phone. No dev work possible.
Whereas the Moto Z (unlocked edition) has bootloader unlock on request and there's tons of ROMs and kernels, etc for it. You got the wrong phone, IF you wanted dev stuff... You need a phone where the bootloader can be unlocked and the phone rooted. Some Verizon phones' bootloaders can be unlocked through Sunshine exploits, but not that many. You have to do research here on XDA before you get the phone.
Now some people may have this Droid Moto Z Force phone and LOVE it, but yeah the dev sections are basically empty. No ROMs, no kernels. And there won't be any until the bootloader is unlocked -- IF ever.
The 2015 Droid Turbo 2 (Verizon's Kinzie variant) is in the same condition -- bootloader locked down, no dev work, while the sibling 2015 Moto X Force (unlocked Kinzie) has ROMs, etc. They both share the same XDA forum, so the Droid Turbo 2 owners can only look enviously at the Moto X Force dev work.
Blame Verizon for locking down the bootloader!
Click to expand...
Click to collapse
...which is a damn shame and craps right on the original intent of Android, back when amateur development was taken seriously and many mods that the folks here and other sites created were incorporated into official Android releases...
Z Force is a fine phone and if rootable would have an explosive Dev community. Really sucks....

ChazzMatt said:
Moto Z Force (Droid) has a LOCKED BOOTLOADER. Can't be rooted. It's a Verizon phone. No dev work possible.
Whereas the Moto Z (unlocked edition) has bootloader unlock on request and there's tons of ROMs and kernels, etc for it. You got the wrong phone, IF you wanted dev stuff... You need a phone where the bootloader can be unlocked and the phone rooted. Some Verizon phones' bootloaders can be unlocked through Sunshine exploits, but not that many. You have to do research here on XDA before you get the phone.
Now some people may have this Droid Moto Z Force phone and LOVE it, but yeah the dev sections are basically empty. No ROMs, no kernels. And there won't be any until the bootloader is unlocked -- IF ever.
The 2015 Droid Turbo 2 (Verizon's Kinzie variant) is in the same condition -- bootloader locked down, no dev work, while the sibling 2015 Moto X Force (unlocked Kinzie) has ROMs, etc. They both share the same XDA forum, so the Droid Turbo 2 owners can only look enviously at the Moto X Force dev work.
Blame Verizon for locking down the bootloader!
Click to expand...
Click to collapse
I won't like to think so. There are Samsung phones with locked bootloaders. But still get custom roms based off stock. With improvements and tweaks made on the rom. I think it's the popularity that matters. The more people use the device the more likely there is an exploit like the Samsung s7 and edge series. Where kernel exploits were used to obtain root.

jazzdglass said:
I won't like to think so. There are Samsung phones with locked bootloaders. But still get custom roms based off stock. With improvements and tweaks made on the rom. I think it's the popularity that matters. The more people use the device the more likely there is an exploit like the Samsung s7 and edge series. Where kernel exploits were used to obtain root.
Click to expand...
Click to collapse
Motorola phones are different. You need to unlock the bootloader.
Trust me on this.
With LG G2 and LG G3, you could also root and install custom recovery and ROMs without bootloader unlock .
Motorola phones are different. Luckily, Motorola will unlock your bootloader on request -- unless it's a Verizon phone.

ChazzMatt said:
Motorola phones are different. You need to unlock the bootloader.
Trust me on this.
With LG G2 and LG G3, you could also root and install custom recovery and ROMs without bootloader unlock .
Motorola phones are different. Luckily, Motorola will unlock your bootloader on request -- unless it's a Verizon phone.
Click to expand...
Click to collapse
I'm holding my moto z Droid force now and "Allow bootloader unlock" is an option in the developer menu...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 02:10 AM ---------- Previous post was at 02:08 AM ----------

mdsinger2 said:
I'm holding my moto z Droid force now and "Allow bootloader unlock" is an option in the developer menu... ]
Click to expand...
Click to collapse
So what? That's been an "option" on everybody's Android phone since Lollipop. Verizon carrier demand to manufacturer overrides that consumer option. They demand their bootloaders remain locked down.
Toggle that switch all you want, it won't do any good. With a Motorola phone you still need a bootloader unlock code. This is from my guide on how to unlock Motorola bootloaders:
Section 1: UNLOCK YOUR BOOTLOADER
Before anything, go to the Motorola website and unlock your bootloader.
Unlocking the is FREE, via the Motorola website.
UNLOCK YOUR BOOTLOADER
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
You release Motorola from any liability, get a code and unlock your bootloader.
If you get an error message at this step that your phone is not eligible, then you have typed in something wrong or you have a Verizon phone. Helps if you Google how to copy and paste from Windows command window. There's a LOT of alphanumeric characters you have to type. First time I tried to unlock my bootloader I mis-typed something. :crying: Copying and pasting from the Windows command window fixed that problem! :good:
You'll get an email with the bootloader unlock code. The email will also have a link back to the instructions. But the code is what's important.
You will receive this fairly instantly. If you don't get it, make sure you checkmarked you agree to all the conditions. Also check your spam folder.
Click to expand...
Click to collapse
However, IF you go to that website with a Verizon phone, it will say you do not qualify. WHY? Verizon won't let Motorola give customers the unlock code. So, with Verizon Motorola phones you need someone like Sunshine team to find an exploit.
I got codes from Motorola for my phones because they are NOT Verizon branded Motorola phones.
This is why the NON-Verizon Moto Z has lots of development, but none of the Verizon Droid Z phones (Droid Z or Droid Z Force) have any development. Blame Verizon.
Go here and take a look:
Moto Z
https://forum.xda-developers.com/moto-z
Unbranded Moto Z phone, not the Droid branded Z or Z Force. Lots of ROMs, kernels, etc.
You bought a Verizon phone. Yes, it's frustrating when you pay hundreds of dollars for a phone and the carrier or manufacturer still thinks they own your phone. So, I don't give carriers or manufacturers like that my money. I never buy a phone I can't root, install custom ROMs. And with Motorola phones that means you have to unlock the bootloader. So, that means no Verizon Motorola phones UNLESS you know there's an exploit available, like from Sunshine team.
Rumor is the 2017 Moto Z2 Force (successor the Z Force) will NOT be a Verizon exclusive. In which case, I'll wait to see if bootloader codes will be available from for either T-mobile branded phone or even "international". I have the Moto XT1225 which is the unbranded "international" version of the Droid Turbo XT1254, but has all the AT&T LTE bands. But there was also a U.S. Moto Maxx XT1250 which was the exact clone of the Droid Turbo XT1254, sold by regional CDMA/LTE carriers in the U.S.A. and it has all the Verizon bands and has FREE bootloader unlock. You could stick in a Verizon sim card and it would run on Verizon just like a non-Verizon Nexus 6.
Before Sunshine found exploits for the Droid Turbo, Verizon users who wanted an unlocked bootloader went and bought the U.S. Moto XT1250 -- same FCC ID, same bands, exact same phone as the Droid Turbo XT1254, but with an easily unlocked bootloader with free code from Motorola. The Moto XT1250 was basically the "dev" version of the Verizon Droid Turbo XT1254.

Moto Z Force unlocked bootloader
Hello XDA experts (IMHO), I am new to this site as I just registered; however, I have read multiple threads and found the vast majority to be knowledgeable and definitely informative. Thank you for that.
I bought an unlocked Moto Z Force off of eBay in March of last year, and until the forced updates I really enjoyed using it. Then came the forced updates that I had no choice in even blocking the download since they have always happened in the background without any notification of the process requesting access or anything close. I really really hate that some hump hidden away in some stupid little cubicle is writing code to essentially hi-jack my phone. And this is coming from a used to be decent company.
Anyways, in the summer I was messing with the phone and kept hitting the boot unlocker button until finally it stayed on. It has been unlocked since, but unfortunately my home computer is dead until I replace the power supply so I haven't hooked up to a computer with the phone.
I did try Kingoroot but that was unsuccessful so I quit messing with it until last month I decided to see what, if any, info was to be had on rooting it. Nothing seems to have changed except when I read that no one appeared to have an unlocked Verizon Moto Z Force with an unlocked bootloader. I then thought that armed with what I was able to do that someone from this site would be able to run with it and push this into the box of done that.
I only probably know enough to screw up my phone but I was looking at using the fastboot and recovery tool areas as possible ins for breaking the wall that stupid a$$ Verizon builds.
Am I on the right track maybe? I'm sure that these areas & ideas have probably been looked at 6 ways from Sunday but just in case I wanted to throw the info in of what I had done & that it might help out somehow.
If someone is able to then get these Moto Z Force phones "fixed" I would really love to be able to follow the instructions and finish mine.
Again, thanks for all that has been done on everything else & I hope this helps.

Verizon Moto E4 XT1767 fashed with stock XT176 rom?

Hi Guys.
Is it possible to flash the Verizon Moto E4 Xt1767 with the stock XT176 rom? I was able to years ago able to flash the Verizon Droid 3 with a unbranded carrier stock rom.
Regard
Sebb

cyri22 said:
Hi Guys.
Is it possible to flash the Verizon Moto E4 Xt1767 with the stock XT176 rom? I was able to years ago able to flash the Verizon Droid 3 with a unbranded carrier stock rom.
Regard
Sebb
Click to expand...
Click to collapse
How might you accomplish this given locked bootloader, no root and no ability to boot a custom recovery. There is little/no chance ADB sideload would allow such a swap as it would stop any semblance of device security.

SM-G975U (T-Mobile Galaxy S10+) Rooting, etc

It's been so long since I last rooted my phones, maybe 6 or 7 years now... I don't even know where to start. Is TWRP still the go-to method for rooting these Android devices?
I couldn't find anything specifically for the T-Mobile variants, dunno if that's been done yet.
Thanks,
Nick

Your bootloader is locked and cannot be unlocked. No root or TWRP available.

StoneyJSG said:
Your bootloader is locked and cannot be unlocked. No root or TWRP available.
Click to expand...
Click to collapse
Thanks

No problem!

Is this device always going to have a locked bootloader? Flashing an unlocked firmware wouldn't change anything? Im new to samsung and have been out of the rom game a long time.

PunkUnity said:
Is this device always going to have a locked bootloader? Flashing an unlocked firmware wouldn't change anything? Im new to samsung and have been out of the rom game a long time.
Click to expand...
Click to collapse
These devices will always be locked down. The last U.S. Samsung phone to get root was the S9, the S10 line are locked up tight. Flashing unlocked firmware just makes your phone carrier free so you can use it with any carrier, it doesn't unlock the bootloader.

What phones are best for modding these days then? Just came from a Pixel 4 XL and it had a locked bootloader plus tons of hardware issues that ended in me getting this phone

I would say a One Plus phone is probably the most versatile as far as modding goes these days. You could also get an exynos S10 variant which can be rooted and custom recovery installed.