Related
Please anybody who already call Sprint and received GSM Unlock via OTA... do the copy of your all files in root folder (/ folders, files), or just make CWM (TWRP) Backup and upload it to server. I will do my best to unlock MOTO X ...
ysabxe said:
Please anybody who already call Sprint and received GSM Unlock via OTA... do the copy of your all files in root folder (/ folders, files), or just make CWM (TWRP) Backup and upload it to server. I will do my best to unlock MOTO X ...
Click to expand...
Click to collapse
Not sure that I can help, but I'm willing to try, provided you are willing to work with a n00b (who can follow instructions, though).
I've got a XT056 (Sprint Moto X) that I've had active for more than 90days on an account that is several years old. In theory, I should be able to get Sprint to unlock the radios for international GSM. In theory. But I've never (never, EVER) gone to Sprint with a question/concern/request that wasn't made vastly worse for their participation. But I would be willing to try for a worthy project. And this seems to me worthy.
Right now, I am on 4.2.2 rooted (via RockMyMoto). I'm on the verge of unlocking my bootloader so that I can conveniently update to KK and not lose root. Will any of this interfere with the collection of data you require? If not, exactly how do I capture that data? If, as the quoted passage suggests, you basically want the complete file system, then I will grab that when I unlock the bootloader but before I restore my info. I trust that a fresh install prior to signing on will still contain the relevant info?
noregreblem said:
Not sure that I can help, but I'm willing to try, provided you are willing to work with a n00b (who can follow instructions, though).
I've got a XT056 (Sprint Moto X) that I've had active for more than 90days on an account that is several years old. In theory, I should be able to get Sprint to unlock the radios for international GSM. In theory. But I've never (never, EVER) gone to Sprint with a question/concern/request that wasn't made vastly worse for their participation. But I would be willing to try for a worthy project. And this seems to me worthy.
Right now, I am on 4.2.2 rooted (via RockMyMoto). I'm on the verge of unlocking my bootloader so that I can conveniently update to KK and not lose root. Will any of this interfere with the collection of data you require? If not, exactly how do I capture that data? If, as the quoted passage suggests, you basically want the complete file system, then I will grab that when I unlock the bootloader but before I restore my info. I trust that a fresh install prior to signing on will still contain the relevant info?
Click to expand...
Click to collapse
Hello) You don't need to unlock bootloader! When GSM Unlock will be done just copy all files in root system folder ( / ) by X-plore or RootExplorer. It will be normal for start... Thanks!
If you need testers, I volunteer. I've had an ebay-purchased Sprint Moto X sitting on my desk at work for months now that is otherwise useless to me, so I might as well put it to good use!
There will be a great lot of testers, as according to number of topics in this section there are lots of those who made a great choice to buy sprint x
Now just someone with ota unlocked x should help OP
+1, i'm in the same boat.
I can try to help.
ysabxe said:
Please anybody who already call Sprint and received GSM Unlock via OTA... do the copy of your all files in root folder (/ folders, files), or just make CWM (TWRP) Backup and upload it to server. I will do my best to unlock MOTO X ...
Click to expand...
Click to collapse
I believe I have an unlocked phone (although I haven't tested it yet outside the US; in the US a T-Mobile SIM did not work; but that's not surprising), and would be happy to help. I don't have an unlocked bootloader, so I can't do a TWRP backup for you. Could you please tell me exactly which parts of the root folder you need?
ysabxe said:
Hello) You don't need to unlock bootloader! When GSM Unlock will be done just copy all files in root system folder ( / ) by X-plore or RootExplorer. It will be normal for start... Thanks!
Click to expand...
Click to collapse
if you need testers,i would be happy to be one,right now i have a brick in my desk.
pavanmaverick said:
I believe I have an unlocked phone (although I haven't tested it yet outside the US; in the US a T-Mobile SIM did not work; but that's not surprising), and would be happy to help. I don't have an unlocked bootloader, so I can't do a TWRP backup for you. Could you please tell me exactly which parts of the root folder you need?
Click to expand...
Click to collapse
I need all files from start root folder, / , example there is way /system/app... I need all folders and files in / (including system folder), all of them
+1,im wating...thanks.
ysabxe said:
I need all files from start root folder, / , example there is way /system/app... I need all folders and files in / (including system folder), all of them
Click to expand...
Click to collapse
did you have good luck with unlock?
I'm iterested too
Any progress with unlock..
Sent from my XT907 using Tapatalk
nobody want's to send files(
mmm maybe no gsm,but cdma can be used outside sprint do you know any way of getting msl code without calling sprint?
thecj said:
mmm maybe no gsm,but cdma can be used outside sprint do you know any way of getting msl code without calling sprint?
Click to expand...
Click to collapse
I think that will be better to find some user with unlocked sprint gsm on other forums if there is no one here. I will try to find one who is willing to cooperate.
I'm getting my phone sim unlocked, have the request into sprint at the moment. I want to give you a clean dump, so after its sim unlocked, would unlocking the bootloader to wipe it, do anything to the sim lock?
ysabxe said:
I need all files from start root folder, / , example there is way /system/app... I need all folders and files in / (including system folder), all of them
Click to expand...
Click to collapse
OK, cool. Does it matter if the phone is bootloader unlocked?
anks329 said:
I'm getting my phone sim unlocked, have the request into sprint at the moment. I want to give you a clean dump, so after its sim unlocked, would unlocking the bootloader to wipe it, do anything to the sim lock?
Click to expand...
Click to collapse
No, don't wipe it, if it is possible do copy of system files and if your bootloader is unlocked + Recovery Backup
pavanmaverick said:
OK, cool. Does it matter if the phone is bootloader unlocked?
Click to expand...
Click to collapse
No, if it is unlocked do Recovery Backup, it will be fine
if I have already upgraded to kit kat 4.4.2? I take it that since the 4.4.2 OTA hasn't been pushed for my Verizon Dev Ed device, that the factory images I have been given by Motorola are for 4.4.
But once the 4.4.2 OTA is pushed, the factory images I have now would be out of date because those are for 4.4., right? Then will Motorola release 4.4.2 factory images later?
Also, what does it mean when in bootloader mode it says Device is UNLOCKED. Status Code: 3. What is the status code 3?
Cozume said:
if I have already upgraded to kit kat 4.4.2? I take it that since the 4.4.2 OTA hasn't been pushed for my Verizon Dev Ed device, that the factory images I have been given by Motorola are for 4.4.
But once the 4.4.2 OTA is pushed, the factory images I have now would be out of date because those are for 4.4., right? Then will Motorola release 4.4.2 factory images later?
I have a verizon unlocked dev ed. Also, what does it mean when in bootloader mode it says Devide is UNLOCKED. Status Code: 3. What is the status code 3?
Click to expand...
Click to collapse
It gives you the stock recovery, the stock system image with all the applications, and the ability to update over the air (OTA). People re-flash the factory images either when they think they messed up their phone, or when they want the latest update via OTA instead of waiting for a SBF package. In short, it returns the phone to the default/non modded status.
I am fairly certain that a SBF will be made for 4.4.2, it just is taking a bit longer this time, maybe they are busy, especially since there is no new updates around the corner any time soon. Since you have already updated to 4.4.2 (like myself) there is no way to go back to stock unless you have made a recovery image in TWRP/CWM. Then all you have to do to update, is reflash the stock recovery image and then you can take a system OTA.
The bootloader on this phone cannot be downgraded, due to the eFuse system incorporated into it. If you attempt to load a lower bootloader in RSD Lite, it will simply fail to install and nothing else bad will happen, however, if you force the bootloader overwrite then you have a nice new paperweight (aka hard brick), because this trips the eFuse.
Status code 3 is basically the computer flag telling the future firmware updates that your bootloader has already been unlocked, so if you update using that same carrier/firmware, you don't lose your unlocked bootloader status. Another reason why you need to simply stick with your own firmware. As there have been reports that loading another regions/phones firmware can lock your bootloader again because the flag isn't there.
mastarifla said:
In short, it returns the phone to the default/non modded status.
Click to expand...
Click to collapse
It restores everything I modded? I erased the clogo.bin file and then I think I flashed with some other bin file to clogo and of course, didn't save a backup. Now I can't get the Kit Kat easter egg when I tap the build version so clearly it has something to do with the clogo file I messed with. I can live without the easter egg, but I don't want to brick my device. So I guess I should just flash the factory images and see what happens.
mastarifla said:
The bootloader on this phone cannot be downgraded, due to the eFuse system incorporated into it. If you attempt to load a lower bootloader in RSD Lite, it will simply fail to install and nothing else bad will happen, however, if you force the bootloader overwrite then you have a nice new paperweight (aka hard brick), because this trips the eFuse.
Click to expand...
Click to collapse
and even if your bootloader is unlocked, you have a hard brick and there is no way to correct that?
mastarifla said:
Status code 3 is basically the computer flag telling the future firmware updates that your bootloader has already been unlocked, so if you update using that same carrier/firmware, you don't lose your unlocked bootloader status. Another reason why you need to simply stick with your own firmware. As there have been reports that loading another regions/phones firmware can lock your bootloader again because the flag isn't there.
Click to expand...
Click to collapse
If my bootloader were to ever get locked again, can't I use the same 20 digit unlock key that Motorola emailed me to unlock it?
Many thanks again, and sorry I cannot hit the thanks button until tomorrow!
Cozume said:
It restores everything I modded? I erased the clogo.bin file and then I think I flashed with some other bin file to clogo and of course, didn't save a backup. Now I can't get the Kit Kat easter egg when I tap the build version so clearly it has something to do with the clogo file I messed with. I can live without the easter egg, but I don't want to brick my device. So I guess I should just flash the factory images and see what happens.
Click to expand...
Click to collapse
If you are already on 4.4.2 then you can flash the 4.4.2 "factory image" when it is released and it should be fine/back to normal.
Cozume said:
and even if your bootloader is unlocked, you have a hard brick and there is no way to correct that?
Click to expand...
Click to collapse
Correct, all the phones have the same eFuse system, even the developer phones. This "supposedly" prevents people from screwing up their phones more. (Personally I think it's silly, but I also have a Nexus, so it doesn't bother me).
Cozume said:
If my bootloader were to ever get locked again, can't I use the same 20 digit unlock key that Motorola emailed me to unlock it?
Many thanks again, and sorry I cannot hit the thanks button until tomorrow!
Click to expand...
Click to collapse
You should be able to (if you still have your IMEI), however there are reports that some people are losing their IMEI too, if this gets lost and there is no way to recover it then you are out of luck, because in order to unlock the bootloader it has to verify that the code works for your IMEI (which is carrier specific).
mastarifla said:
Correct, all the phones have the same eFuse system, even the developer phones. This "supposedly" prevents people from screwing up their phones more. (Personally I think it's silly, but I also have a Nexus, so it doesn't bother me).
Click to expand...
Click to collapse
It seems like the eFuse is the cause of people screwing up their phones. I suppose they do these sorts of things to satisfy potential corporate customers who want secure devices for their corporate communications.
mastarifla said:
You should be able to (if you still have your IMEI), however there are reports that some people are losing their IMEI too, if this gets lost and there is no way to recover it then you are out of luck, because in order to unlock the bootloader it has to verify that the code works for your IMEI (which is carrier specific).
Click to expand...
Click to collapse
Wow, that is awful but can't an IMEI be restored somehow if you know what it is? I not only have my box, Verizon has all my IMEI's stored on their system.
Cozume said:
It seems like the eFuse is the cause of people screwing up their phones. I suppose they do these sorts of things to satisfy potential corporate customers who want secure devices for their corporate communications.
Click to expand...
Click to collapse
Sadly corporate security is much less of a concern to them and actually something else entirely (see Samsung's encryption protocol for enterprise - SAFE). Motorola doesn't want to bother with supporting people on lower firmwares, and this prevents them from having to worry about it because they will always require you to be on the latest firmware for support, this eFuse system basically prevents people from using exploits in previous versions of the system (aka getting root on a non-unlocked phone, etc).
Cozume said:
Wow, that is awful but can't an IMEI be restored somehow if you know what it is? I not only have my box, Verizon has all my IMEI's stored on their system.
Click to expand...
Click to collapse
If you have your EFS files backed up then you are okay, you can just restore it and you are good to go again. However, the IMEI is a secure file, so you cant make a new one if its gone (nor can your cell company), this system in effect prevents people stealing phones and changing the IMEI in order to not be blacklisted. This system is in place for a very good reason, while not perfect (try selling a used phone to someone who understands this), its the best deterrent against theft currently available.
mastarifla said:
If you have your ESF files backed up then you are okay, you can just restore it and you are good to go again.
Click to expand...
Click to collapse
If I do a nandroid backup does it back those files up? if not, what can I use to back them up?
Also, I will have to come back tomorrow and the next day to hit the thanks button because I will use up all my thanks again tomorrow on you, lol!
Cozume said:
If I do a nandroid backup does it back those files up? if not, what can I use to back them up?
Also, I will have to come back tomorrow and the next day to hit the thanks button because I will use up all my thanks again tomorrow on you, lol!
Click to expand...
Click to collapse
There are tools available to backup your EFS partition in case a nandroid doesn't work correctly. Some CWM/TWRP versions do EFS partition backups, some don't, be sure to read through the threads and make sure. Asking a question goes a long way.
Hey folks. Got a Dev edition here, which as I understand is easy to unlock. Question is must I lose my data when doing so? And if yes, how can I backup before unlocking? If I had root, I would run titanium backup, but given that I can't get root until I unlock, this seems like a chicken and egg problem....
Sent from my XT1053 using XDA Free mobile app
Yes, doing the. Mfastboot oem unlock will factory reset the phone. You will lose apps and data. I am not familiar with a way (while not rooted) to back up everything and restore after unlocking such that everything is the same.
I may be wrong.....just going from memory of what I've read, but I think an app called helium can backup without root. Then you'd need to transfer the backup off the phone, cause everything is gone when you unlock. Pics too.
Hm. Can anyone confirm this happens for sure? On the Galaxy Nexus, people said the same thing but it turned out that if you just typed fastboot oem unlock without flashing any partitions that no data was actually erased. I just can't understand why unlocking would be linked to erasing.
Thanks!
Sent from my XT1053 using XDA Free mobile app
zAlbee said:
Hm. Can anyone confirm this happens for sure? On the Galaxy Nexus, people said the same thing but it turned out that if you just typed fastboot oem unlock without flashing any partitions that no data was actually erased. I just can't understand why unlocking would be linked to erasing.
Thanks!
Sent from my XT1053 using XDA Free mobile app
Click to expand...
Click to collapse
Unlocking erases everything. On any device I've owned. The x for sure.
Why? Dunno. Lol
Unlocking the bootloader will reset the phone back to factory fresh condition as stated. When I unlocked my Moto X it was factory reset. Same for when I unlocked the bootloader in my Nexus 10, Droid Razr M, Incredible and Eris. I think this is the normal behavior.
There are ways to back up your data and apps even without an unlocked or rooted phone. There is a toolkit in this forum somewhere for the Moto X that will do that as well as a market app (Helium?). I used the toolkit here:
http://forum.xda-developers.com/moto-x/development/tool-moto-x-toolkit-v1-2-1-t2477132
But I did that while at 4.4, before the OTA update to 4.4.2.
Any tool to recover files from a recently formatted device by unlocking the bootloader? thanks.
No. "Format" means "Blotto Everything". That's exactly what happens.
IMO seems to be a commercial "feature" more than a technical limitation. The simply want to discourage you to unlock the bootlader. All along the process, there is a warning message telling you that unlocking the bootloader will make the phone less secure. A subliminal message from Xiaomi : Blessed be the freely included uninstallable without root - and by extention unlocking the bootloader... D'oh!- bloatware package ! Or go to hell with your data if you dare to spit on it!
If you are able to install twrp, does that mean that the phone is already unlocked? I've already deleted my stock android and I couldn't see any options there at all of unlocking the oem directly in the settings, but I was able to install twrp itself (2.6).
Hello everybody, I just got my Moto X and I have to say it is a lovely device better than I expected in terms of how it feels in the hand. Really compact device.
I have some questions:
1. My phone has 4.4.2 but OTA fails to update it to 4.4.3. Is there any software that I can use to update the phone?
2. Is there a flashtool software where I can flash different .ftf fies?
3. Root option for 4.4.3 available?
1. There are a few threads discussing the 4.4.3 OTA, and what condition your phone must be in to receive/install the OTA. For example -> [XT1053] 4.4.3 OTA Update Zip and Android™ 4.4.3, KitKat® Rolls Out to Moto Devices I'm sure if you READ it, you'll find information that will solve your issue. Or if you post details of your phone, carrier, any tweaks you've made to it, etc...
2. I do not believe so.
3. If you have an unlocked bootloader, you *can* Root 4.4.3. If you have a LOCKED bootloader, you *can not* root 4.4.3.
asilviug said:
Hello everybody, I just got my Moto X and I have to say it is a lovely device better than I expected in terms of how it feels in the hand. Really compact device.
I have some questions:
1. My phone has 4.4.2 but OTA fails to update it to 4.4.3. Is there any software that I can use to update the phone?
2. Is there a flashtool software where I can flash different .ftf fies?
3. Root option for 4.4.3 available?
Click to expand...
Click to collapse
Locked or unlocked bootloader? What carrier?
I have an unlocked Dev Ed Moto X running TMobile, and it accepted the 4.4.3 OTA update. I first had to revert entirely to stock 4.4.2, though.
varxx said:
Locked or unlocked bootloader? What carrier?
I have an unlocked Dev Ed Moto X running TMobile, and it accepted the 4.4.3 OTA update. I first had to revert entirely to stock 4.4.2, though.
Click to expand...
Click to collapse
My phone is branded with an AT&T logo on the back. Model number is xt1058 and I'm running stock 4.4.2
I don't know about the bootloader though, how can I verify that?
I would really like to update this to 4.4.3 and root it, although it's not that easy I see.
Any help would be highly appreciated. I'm even considering throwing in a bounty
asilviug said:
My phone is branded with an AT&T logo on the back. Model number is xt1058 and I'm running stock 4.4.2
I don't know about the bootloader though, how can I verify that?
I would really like to update this to 4.4.3 and root it, although it's not that easy I see.
Any help would be highly appreciated. I'm even considering throwing in a bounty
Click to expand...
Click to collapse
Ok... here we go...
4.4.3 is not out for the ATT XT1058 yet, so you can't update to it. You need to wait for ATT to start making it available.
ATT XT1058 has a locked bootloader, and Moto doesn't give out the bootloader unlock codes. Your only option to unlock the bootloader is *IF* (or maybe when) the Chinese WebSite/MiddelMan comes back to selling bootloader unlock codes. See -> http://forum.xda-developers.com/moto-x/general/china-middleman-t2751177
There is no option to root 4.4.3 when you have a locked bootloader.
If you want usable root on the X you need two parts 1. Root Exploit, and 2. An Exploit that allows for disabling Write Protection. There is now a Root Exploit for 4.4.2 with a locked bootloader, but there is not an exploit to disable write protection. This means if you'd root, then anytime you power your phone off/on, the changes, root, etc is lost. And Root style apps that need to write to /system and the like, CANT.
there is no root option for 4.4.3 with a locked bootloader
For more details see -> http://mark.cdmaforums.com/MotoX-Locked.html
KidJoe said:
Ok... here we go...
4.4.3 is not out for the ATT XT1058 yet, so you can't update to it. You need to wait for ATT to start making it available.
ATT XT1058 has a locked bootloader, and Moto doesn't give out the bootloader unlock codes. Your only option to unlock the bootloader is *IF* (or maybe when) the Chinese WebSite/MiddelMan comes back to selling bootloader unlock codes. See -> http://forum.xda-developers.com/moto-x/general/china-middleman-t2751177
There is no option to root 4.4.3 when you have a locked bootloader.
If you want usable root on the X you need two parts 1. Root Exploit, and 2. An Exploit that allows for disabling Write Protection. There is now a Root Exploit for 4.4.2 with a locked bootloader, but there is not an exploit to disable write protection. This means if you'd root, then anytime you power your phone off/on, the changes, root, etc is lost. And Root style apps that need to write to /system and the like, CANT.
there is no root option for 4.4.3 with a locked bootloader
For more details see -> http://mark.cdmaforums.com/MotoX-Locked.html
Click to expand...
Click to collapse
Thanks for the info fist of all. Not very good news but it is what it is.
I took a look at that link and apparently the newer models of Moto X are most likely to get an unlock code. My phone is from 2013 most probably but I don't know how to find out exactly. Can you advise on this matter as getting a code from that asian dude seems the next step for me.
asilviug said:
Thanks for the info fist of all. Not very good news but it is what it is.
I took a look at that link and apparently the newer models of Moto X are most likely to get an unlock code. My phone is from 2013 most probably but I don't know how to find out exactly. Can you advise on this matter as getting a code from that asian dude seems the next step for me.
Click to expand...
Click to collapse
There are several ways to find out your date code.. The easiest is to boot the phone in bootloader/fastboot mode, and select the option for Bar Codes. The date displayed there is the build date.
KidJoe said:
There are several ways to find out your date code.. The easiest is to boot the phone in bootloader/fastboot mode, and select the option for Bar Codes. The date displayed there is the build date.
Click to expand...
Click to collapse
Thanks, it appears that my phone is from August 2013. I will try to get a code. Before I do that just want to double check it with you.
Once I get the unlock code, I can root 4.4.2 that I'm currently running and also future updates released by AT&T/Motorola in the near future including the 4.4.3?
asilviug said:
Thanks, it appears that my phone is from August 2013. I will try to get a code. Before I do that just want to double check it with you.
Once I get the unlock code, I can root 4.4.2 that I'm currently running and also future updates released by AT&T/Motorola in the near future including the 4.4.3?
Click to expand...
Click to collapse
Correct. Once you unlock your bootloader (which is DESTRUCTIVE, so BACKUP EVERYTHING To Your PC, or Cloud, before you do the process), you will be able to root any android version by flashing a 3rd party recovery (like TWRP), booting to the 3rd party recovery and installing SuperSU.
For more info, see -> http://mark.cdmaforums.com/MotoX-Unlock1.htm
KidJoe said:
Correct. Once you unlock your bootloader (which is DESTRUCTIVE, so BACKUP EVERYTHING To Your PC, or Cloud, before you do the process), you will be able to root any android version by flashing a 3rd party recovery (like TWRP), booting to the 3rd party recovery and installing SuperSU.
For more info, see -> http://mark.cdmaforums.com/MotoX-Unlock1.htm
Click to expand...
Click to collapse
Unfortunately the Chinese middle man couldn't help me with the unlock code. What about contacting AT&T regarding the unlock code? Do you think it's possible asking them politely?
asilviug said:
Unfortunately the Chinese middle man couldn't help me with the unlock code. What about contacting AT&T regarding the unlock code? Do you think it's possible to ask them politely?
Click to expand...
Click to collapse
Zero chance. Sorry.
I mean...it's certainly possible to ask them politely, but they still won't give it to you....guaranteed.
I'm guessing you have a 2013 variant since the middleman couldn't help you?
samwathegreat said:
Zero chance. Sorry.
I mean...it's certainly possible to ask them politely, but they still won't give it to you....guaranteed.
I'm guessing you have a 2013 variant since the middleman couldn't help you?
Click to expand...
Click to collapse
Yes, a late 2013 model. He said that the database could become available again in the future...
If I want to contact AT&T, what would be the best way? Phone/email? I'm not an US citizen nor living in US.
asilviug said:
Yes, a late 2013 model. He said that the database could become available again in the future...
If I want to contact AT&T, what would be the best way? Phone/email? I'm not an US citizen nor living in US.
Click to expand...
Click to collapse
I'm not an AT&T customer, so I can't advise on contact info, but I can tell you that you will be wasting your time if you even try. The chance that they will give you the code is exactly 0% no matter how nicely you ask them.
You might consider selling your AT&T XT1058 and buying one that can be unlocked, such as the XT1053, or the XT1058 Roger's variant if unlocking the BL is that important to you.
Good Luck
asilviug said:
Unfortunately the Chinese middle man couldn't help me with the unlock code. What about contacting AT&T regarding the unlock code? Do you think it's possible asking them politely?
Click to expand...
Click to collapse
asilviug said:
Yes, a late 2013 model. He said that the database could become available again in the future...
If I want to contact AT&T, what would be the best way? Phone/email? I'm not an US citizen nor living in US.
Click to expand...
Click to collapse
You have zero chance getting a boot loader unlock code from Att or Moto.
And If you are not living in the USA, then you are likely not an ATT customer, so they won't even talk to you.
I am running a Verizon Moto X still on 4.2.2. I am rooted. This is NOT the Dev edition. I have plenty of experience with rooting/flashing these phones so back when I first got it the directions on rooting/flashing roms was VERY vague. No one specified you needed the Dev edition to unlock the boot loader. Well I think this came from at one point when I tried to flash TWRP (maybe). Either way, I want to take the OTA update and cannot. Does anyone know how to fix this without doing the RSD, reflash stock method? Here is a picture of what it looks like (thanks for your help in advance):
You should check out the 'Chinese Middleman' thread. If you get the bootloader unlocked you should be able to fix anything.
I can't unlock the bootloader since this is not a Dev edition. Unless something has changed, I'll check it.
You should be able to unlock the boot loader but will not have warranty.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my XT1053 using Tapatalk
shamelin73 said:
You should be able to unlock the boot loader but will not have warranty.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
Even though it's not a Dev edition?
Yes you should be able too.
Sent from my XT1053 using Tapatalk
danman421 said:
Even though it's not a Dev edition?
Click to expand...
Click to collapse
All XT1053s can be unlocked, yes. Additionally, if you follow my advice, you don't NEED to unlock. If one of the commands fails, simply skip to the next as I previously advised, and TRY flashing with RSD Lite after you have run the commands I listed.
If you want to check and make sure fastboot is working, type:
fastboot devices
if you see your phone and it's serial number listed, you fastboot IS properly communicating with your phone.
You do not need to unlock your BL to do any of this...but if you are interested in ROOTING, you will need to.
All I really want to do is make it so my phone can take the update and any future updates. What do you mean as you previously stated?
shamelin73 said:
You should be able to unlock the boot loader but will not have warranty.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
I tried this as I did before and I get "your device does not qualify for bootloader unlocking". All I need to know is how to fix this from someone.
danman421 said:
All I really want to do is make it so my phone can take the update and any future updates. What do you mean as you previously stated?
Click to expand...
Click to collapse
I confused you with a member I had helped previously - sorry. Please disregard the "previously stated" comment.
danman421 said:
I tried this as I did before and I get "your device does not qualify for bootloader unlocking". All I need to know is how to fix this from someone.
Click to expand...
Click to collapse
It does NOT require unlocking the bootloader to flash your carrier's correct ROM. Simply follow the instructions in the "Return to 100% Stock" thread to flash the XT1053 ROM, and you'll be able to take all future updates.
If you DO unlock the bootloader, flash custom recovery, and root your device, you will have to un-do any modifications made before EVERY OTA. If you don't care about root, don't worry about unlocking.
Additionally, if you DO want to unlock, you could try a different browser and make sure you are inputting the unlock data correctly. It is recommended that you copy the unlock data from the command prompt to notepad, remove all spaces and bootloader messages (you ONLY want the code - as one complete string), then copy from notepad into the Unlock website.
And finally, keep in mind that unless you unlock your BL, you will not be able to root and disable write-protect once you update to the latest version.
The real problem here is that you use an "Exploit" to root your device previously. Now you need to return to full stock to restore your partitions to their factory state.
Simply follow the instructions in the Return to stock thread (in general sub-forum), and be sure to flash the LATEST version for your carrier. It should be 4.4.3.
Good Luck.
samwathegreat said:
I confused you with a member I had helped previously - sorry. Please disregard the "previously stated" comment.
It does NOT require unlocking the bootloader to flash your carrier's correct ROM. Simply follow the instructions in the "Return to 100% Stock" thread to flash the XT1053 ROM, and you'll be able to take all future updates.
If you DO unlock the bootloader, flash custom recovery, and root your device, you will have to un-do any modifications made before EVERY OTA. If you don't care about root, don't worry about unlocking.
Additionally, if you DO want to unlock, you could try a different browser and make sure you are inputting the unlock data correctly. It is recommended that you copy the unlock data from the command prompt to notepad, remove all spaces and bootloader messages (you ONLY want the code - as one complete string), then copy from notepad into the Unlock website.
And finally, keep in mind that unless you unlock your BL, you will not be able to root and disable write-protect once you update to the latest version.
The real problem here is that you use an "Exploit" to root your device previously. Now you need to return to full stock to restore your partitions to their factory state.
Simply follow the instructions in the Return to stock thread (in general sub-forum), and be sure to flash the LATEST version for your carrier. It should be 4.4.3.
Good Luck.
Click to expand...
Click to collapse
So if I am reading this correctly, there is no way to keep all of my data and take the update?
danman421 said:
So if I am reading this correctly, there is no way to keep all of my data and take the update?
Click to expand...
Click to collapse
You can attempt to, by either editing the XML in the SBF and removing the line that says "erase userdata", or by skipping the erase userdata if you use the manual method, but either way CAN mess everything up.
You used an EXPLOIT previously. Any time you use an exploit, you should -expect- to have to wipe everything and re-install from scratch if you want to get back to stock in order to be able to take updates. Keep this in mind if you use any exploits in the future.
Hi! This hasn't seemed to spelled out yet..... But many Moto x's can be unlocked, not just dev editions. However, you stated in the opening post that you have a Verizon Non dev, which can not be unlocked. Only way is to pay the "China middleman" (See thread in general with that name).
And personally.... I would stay on 4.2.2 and do the Slapmymoto method to get root and write protection disabled. That is the best root scenario, aside from unlocking the bootloader.
If you update to 4.4.2 or higher, you will have write protection enabled always, and no root, or sorta root with towelroot and pie. But that will limit what you can do.
See the How do I root my phone sticky thread in general for your options.
I should have posted earlier. I ran RSDLite and put the newest version on. I am unrooted. My Moto X is a Sept '13 version the the middleman probably wont work anyways. Its not worth it with this phone, im tired of the rooting, I guess im at that point in my life... Thanks for all your help though guys!
danman421 said:
I am running a Verizon Moto X still on 4.2.2. I am rooted. This is NOT the Dev edition. I have plenty of experience with rooting/flashing these phones so back when I first got it the directions on rooting/flashing roms was VERY vague. No one specified you needed the Dev edition to unlock the boot loader. Well I think this came from at one point when I tried to flash TWRP (maybe). Either way, I want to take the OTA update and cannot. Does anyone know how to fix this without doing the RSD, reflash stock method? Here is a picture of what it looks like (thanks for your help in advance):
Click to expand...
Click to collapse
Pardon my jumping in here late but..
I see a big issue here.
Based on that screen shot, you have boot loader 30.B4, that is NOT the bootloader that comes wtih 4.2.2. Did you mean to type 4.4.2? or do you really have 4.2.2 on there?
If you really had 4.2.2 on your phone with a 30.B4 bootloader, then you had 4.4.2 on there at one point, and downgraded!! You need to be REALLY CAREFUL or you will brick your phone.
You are correct, I was on 4.4.2. My wife's S4 that I just upgraded was on 4.2.2. Sorry for the confusion.
KidJoe said:
Pardon my jumping in here late but..
I see a big issue here.
Based on that screen shot, you have boot loader 30.B4, that is NOT the bootloader that comes wtih 4.2.2. Did you mean to type 4.4.2? or do you really have 4.2.2 on there?
If you really had 4.2.2 on your phone with a 30.B4 bootloader, then you had 4.4.2 on there at one point, and downgraded!! You need to be REALLY CAREFUL or you will brick your phone.
Click to expand...
Click to collapse
Good catch! ?
OP... Perhaps full disclosure of what you have done on the phone would help.
Or is that how it was?
If it's been downgraded to 4.2.2 after being on 4.4.2... As said above.... You could brick now... Especially if you OTA.
I'd tread lightly at this point.
danman421 said:
You are correct, I was on 4.4.2. My wife's S4 that I just upgraded was on 4.2.2. Sorry for the confusion.
Click to expand...
Click to collapse
so based on post # 14 of this post... it appears you are all good now? is that the case? Or do you still need help?
Oh, and if your bootloader is locked (Verizon non-DE), you can't get code from China Middle man, and you are on 4.4.2, you could try TowelPieRoot for rooting, but write protection is enabled so it will be kind of limited (compared to SlapMyMoto/MotoWPNoMO or if you had an unlocked bootloader), and there is no root for 4.4.4.
Yes, that was a good catch. What I did was RSD Lite to 4.4.4 now which reset all my data.
KidJoe said:
so based on post # 14 of this post... it appears you are all good now? is that the case? Or do you still need help?
Oh, and if your bootloader is locked (Verizon non-DE), you can't get code from China Middle man, and you are on 4.4.2, you could try TowelPieRoot for rooting, but write protection is enabled so it will be kind of limited (compared to SlapMyMoto/MotoWPNoMO or if you had an unlocked bootloader), and there is no root for 4.4.4.
Click to expand...
Click to collapse
Correct, I do not need help anymore but thank you.