[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.
Related
Is it possible to unlock flipout from this website ? https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
Also is there any custom rom for it ?
No, the Unlock My Device program at the moment supports only one new device, the Photon Q 4G LTE.
I really hope that the masterminds at Motorola will soon add many more devices, especially older ones like the Flipout. Many of these devices are out of warranty by now anyway.
As for custom ROMs, there are none. Unfortunately the Flipout was not very popular with the modders. However, with an unlocked bootloader this could change.
So... how does one 'SIM unlock' this phone?
Do I understand right, that it needs to be rooted first?
Do I need to also CID unlock it, or is that only needed for flashing a custom ROM?
DylanKeyne said:
So... how does one 'SIM unlock' this phone?
Do I understand right, that it needs to be rooted first?
Do I need to also CID unlock it, or is that only needed for flashing a custom ROM?
Click to expand...
Click to collapse
Only way for BF/Charm is by code, does not require root. Check ebay: search for "unlock mb511" or "unlock mb502" - fairly cheap these days,
Actually, bootloader unlock and carrier/sim unlock are two different things, so we're rather off-topic here.
I'm sure Moto has no interest in unlocking bootloaders of phones they've already sold, so in response to the OP I should say, "No; absolutely not; not ever."
Hey guys, so I'm looking to get the Droid RAZR M for use on AT&T, but before I do that, I had a few questions.
1) What is the process for rooting + unlocking bands + unlocking bootloader? Mainly, should the bootloader be unlocked before performing the band unlock? Does it matter? I'm not used to having a Moto device with an unlockable bootloader.
2) Since I plan on buying the device used, I'm assuming the previous owner would have updated to the latest OTA. Is it still possible to unlock the bootloader with the latest OTA updates? I searched around and didn't see anything saying otherwise, but I figure I should ask anyways.
3) Are there any problems with UMTS/HSPA+ on AT&T? I ask because I currently have a Droid 2 Global and it's got some weird signal dropping issues when on HSPA (but not EDGE) so I wanted to make sure the RAZR M doesn't have any similar bugs.
Thanks in advance!
phantomsniper773 said:
2) Since I plan on buying the device used, I'm assuming the previous owner would have updated to the latest OTA. Is it still possible to unlock the bootloader with the latest OTA updates? I searched around and didn't see anything saying otherwise, but I figure I should ask anyways.
Click to expand...
Click to collapse
Rooting and unlocking the latest OTA update is pretty easy, especially now that there's the Razr M Utility. It's in this thread: http://forum.xda-developers.com/showthread.php?t=2249773 and it handles rooting and unlocking the bootloader.
DjeserDjeseru said:
Rooting and unlocking the latest OTA update is pretty easy, especially now that there's the Razr M Utility. It's in this thread: http://forum.xda-developers.com/showthread.php?t=2249773 and it handles rooting and unlocking the bootloader.
Click to expand...
Click to collapse
Ok, that's good to know. Thanks!
(my browser spazzed and I lost my last post if it shows up as a double ignore the other one!)
I'm new to Android and finding it confusing so thanks for the help so far!
I have a 910F Note 4 on Lollipop and want to root it to get rid of bloatware and possibly stop ads (if I can convince myself it's ethical) btu I *may* want to custom ROM it later.
So far your help and my reading have taught me this:
-- I can root using chainfire in order to get rid of bloat and block ads
-- If after rooting I later want a custom ROM or Xposed I'll need to get custom recovery in which case I'll be able to add CWM or TWRP later to my rooted phone
Assuming the above are true (if not please tell me!!) my question is this:
What on earth is oem unlock/bootloader unlock? In my reading I've come across people talking about this and it wiping the phone. I can't find an easy answer online. If I root +/- do CWM/TWRP will that automatically do OEM unlock or are they different things? Is bootloader unlock a different thing too? I'm confused! Will I need to root AND custom recovery AND oem unlock AND unlock bootloader?
Thanks in advance!!!
Some devices come with a locked bootloader, where you may be able to root the device via an exploit, but you can't change lower level software (ie kernel and/or recovery)... unless there is an unlock method for the bootloader.
The devices that do have a locked bootloader can be locked by the manufacturer, or by the carrier. That's the difference between the two. Either way the bootloader is still locked, only difference is who called for the locking.
For example, note 4 on tmobile does not have a locked bootloader, however, note 4 on at&t does. That decision was made by at&t, not Samsung. As far as I know, the at&t variant does not have a method for unlocking the bootloader yet so there's not much development for the device.
Compare to nexus devices, where Google automatically has the manufacturer lock the bootloader, but it being a development device, it's the easiest bootloader to unlock. It's literally a one line command in adb. HTC devices are locked but you can get an HTC dev code to unlock it from HTC.
I hope that makes sense. The best way to determine if your device has a locked bootloader is to visit the development forum or the general/Q&A forums for your device. If you have a locked bootloader and there is an unlock method, you only have to do it once (until you update or relock your bootloader). Some locked devices never get an unlock method. It designed to maintain the security and integrity of the device, but it also prevents user tampering.
Thank you for your thorough reply absinthesummer, very helpful.
However I'm still a little confused. My reading suggests to me that T-Mobile (910T) is *rootable* and the AT&T version (910S?) is not *rootable* but I'm in the UK and don't use these providers I use EE. And so I have the international variant of the Note 4 which is the 910F. I don't see a subforum or help for the UK EE version of the note 4 but as it's the 910F I assume that's the one I need to search for and not worry that EE will have put their own lock onto the 910F??
Now, because this happens to coincide with what you are saying has a locked bootloader or not, am I to assume that whether or not something is rootable is the same as whether or not it has an unlockable bootloader? i.e. is something only rootable or not because its bootloader is unlockable or not? If so therefore am I correct to assume that as the 910F which I have is rootable that it is also bootloadunlockable? And furthermore am I correct to assume that the very process of rooting itself unlocks the bootloader? Or perhaps in the case of the 910F it doesn't need to be so is even easier than Nexus devices? i.e. I just simply root and that in itself mean bootloader is already unlocked (and I am assuming that oem unlock is the same thing?)
I'm getting myself in a muddle I think!
Hehe it's totally cool, and yes your carrier could put a lock on it but that's incredibly rare in Europe due to frequent traveling between countries and the need to change Sims and carriers often... or at least that's what I've been told. The US carriers who lock their bootloaders are typically GSM carriers who do not expect you to need to root/carrier unlock/whatever. It's a control thing imo.
Anyway, your note 4 does not have a locked bootloader. If you check the development forum for your device you will see plenty of roms and guides and directions for rooting. That's usually a good indication that a device is unlocked (and those anticipating the release of new devices tend to get lock information prior to release, so they know which device they intend to buy).
Anyway, since you don't have a locked bootloader I wouldn't worry about it... that reminds me of a device I had for about a week, the LG L9. It had an oem bootloader lock but the international variant did not. We could root it & use a specially designed recovery with the bootloader locked but we couldn't flash a custom kernel (with a custom rom). They figured out that we could flash the international firmware and unlock that way, but it would make our display backwards (mirrored) and while that could be fixed, we would never be able to revert the boot screen. Now that's way too much trouble to go through just to unlock a bootloader and I did end up returning it and getting an s3 instead.
Bootloader locks are no fun, but they are not often placed on international devices for various reasons, so really I wouldn't worry about it too much.
If you get a device like a Google nexus, or an HTC that has a known locked bootloader, the bootloader and unlock method will be specifically mentioned in the routing guide. I hope that helps.
One more thing: rootability and locked bootloaders are not mutually exclusive, sometimes you can root devices with locked bootloaders and sometimes people will come up with ways around them (ie note 3 has safe strap recovery that runs parallel to stock recovery) to be able to use custom roms. However, if no exploit is found and there is no workaround, development will stall until one or both of those things is found. You may be able to root a device with a locked BL, but you may not be able to flash custom roms/kernels without a workaround. What I meant though is if you see a popular device with very little development, that's probably due to a locked bootloader and not having found a way around it yet. Most guides will explicitly mention the BL though if it's something you need to do
Yet another thoroughly helpful and detailed reply. Thank you very much indeed. You're a star!
I have a verizon samsung galaxy note 3 as many already know after 4.4.4 was released verizon locked the note 3 boot loader so users cannot down grade back to 4.4.2 and the only successful root process that works is on 4.4.2 at this time as far as I've researched so my question is if I were to pay verizon the sim unlocking fee and switch to a carrier that has a known properly working root process, in theory would this work. ? Any feed back would be great. Hoping this will work??!! If any thing I've said is confusing please reply and I'll try my best to reword it.
You're assuming that when you pay the fee that verizon will flash you with an unlocked boot chain. Don't think it's possible. If I'm not mistaken, some of the trust zones are flashed then locked with a physical fuse.
....
So paying the unlocking fee then say you buy a BYOD (bring your own device) kit from t-mobile, straight talk etc, activate the phone with the new carrier (preferably a carrier that currently has a root method that works) then proceed with rooting said device?
Again I'm new to the forum as well as new to the concert of rooting, flashing custom roms etc so please respond in laymens terms
Idk if it could work, I'm just trying to explore any possible solutions to the problem of when android 4.4.4 was released (verizon released theirs with a locked bootloader and if my reseach is correct, there are root processes working for android versions after 4.4.2 on other cell carriers.
So what I'm trying to figure out is if I found a root process that is known to be working on for example (a root process that works on t-mobile, sprint, at&t etc)if I paid to unlock the damn sim and activate the SM-N900V on a cell carrier that so happens to have a working root process, what is the likely hood of it working?
Or
Will it be a complete waste of time, effort, and money to atempt?
Riwd98 said:
So paying the unlocking fee then say you buy a BYOD (bring your own device) kit from t-mobile, straight talk etc, activate the phone with the new carrier (preferably a carrier that currently has a root method that works) then proceed with rooting said device?
Again I'm new to the forum as well as new to the concert of rooting, flashing custom roms etc so please respond in laymens terms
Idk if it could work, I'm just trying to explore any possible solutions to the problem of when android 4.4.4 was released (verizon released theirs with a locked bootloader and if my reseach is correct, there are root processes working for android versions after 4.4.2 on other cell carriers.
So what I'm trying to figure out is if I found a root process that is known to be working on for example (a root process that works on t-mobile, sprint, at&t etc)if I paid to unlock the damn sim and activate the SM-N900V on a cell carrier that so happens to have a working root process, what is the likely hood of it working?
Or
Will it be a complete waste of time, effort, and money to atempt?
Click to expand...
Click to collapse
You are confusing 2 different types of "unlocking".
Sim unlocking is not the same as unlocking a bootloader.
The locked bootloader will not be unlocked by Verizon.
The locked bootloader will not allow you to flash a custom kernel or system and prevents the easy rooting methods. Unless someone finds a root method, you will not get root on that device.
Sent from my SM-N900V using Tapatalk
So I just got an Amazon G4 32GB w/Ads running 6.0.1 (XT1625 ). Out of curiosity, considering everything I've seen that says they're locked anymore, I went to the Moto site & submitted my data strings and evidently I have been sent a unique boot loader unlock code. Should I unlock and see about installing another ROM, or should I just go with the Amazon variation of the software? I get that the general consensus of this site is for flashing alternate ROMS...but I'm just concerned about bricking this phone since it is the Amazon subsidized version.
Granwoltz said:
So I just got an Amazon G4 32GB w/Ads running 6.0.1 (XT1625 ). Out of curiosity, considering everything I've seen that says they're locked anymore, I went to the Moto site & submitted my data strings and evidently I have been sent a unique boot loader unlock code. Should I unlock and see about installing another ROM, or should I just go with the Amazon variation of the software? I get that the general consensus of this site is for flashing alternate ROMS...but I'm just concerned about bricking this phone since it is the Amazon subsidized version.
Click to expand...
Click to collapse
Definitely unlock it if you can. It's generally very hard to brick this phone unless you break a bootloader/fastboot flash.
Custom ROMs are leagues better than insecure Amazon firmware and ads.
Can the Amazon subsidized G4 be unlocked if it's been upgraded to Nougat? If not, is it possible to roll back the version?