[Disclaimer-this is my first android device, thus i will be a total newbie at this stuff, second, this is my second time posting on a forum-type website so excuse me if this has already been asked and answered, plz just link the thread then]
So. Is this possible?
Detailed explanations would be much appreciated.
(I am also using a MAC, so if that affects anything....)
How about looking around a little bit. Come on man
uncalex said:
[Disclaimer-this is my first android device, thus i will be a total newbie at this stuff, second, this is my second time posting on a forum-type website so excuse me if this has already been asked and answered, plz just link the thread then]
So. Is this possible?
Detailed explanations would be much appreciated.
(I am also using a MAC, so if that affects anything....)
Click to expand...
Click to collapse
The Moto X have locked bootloader that prevent you from making changes to the "system" partition. So generally you need to unlock the bootloader first, which is a separate process.
Just a note, that generally when you unlock a phone's bootloader, you void the warranty. Some person here claimed that a Motorola manager confirmed with him that you will not void it with the Moto X Pure edition, however, I do not believe it. The best thing to do is read the fine print and warnings when you goes to unlocked your bootloader from Motorola website.
Another warning, is it easier to permanently brick a Motorola than a some other phones if you flash things incorrectly, such as corrupting the CID partition. With the Moto X 2013 it is possible to brick the phone by downgrading the phone to a too old version. I have never tried this with Moto X, but with Nexus devices, you could softbrick the phone if you root it and then do an over the air update, it generally required to use TWRP recovery to apply the over the air update zip for it to work, or reflash the "system" partition of the phone to stock before doing the update. I don't know if this is the same for the Moto X, but I would take the same precaution.
To unlock the bootloader, you can do it at the website here: https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth. Read through this guide to help you: http://forum.xda-developers.com/moto-x-2014/general/guide-unlock-bootloader-moto-x-2014-t2876773
For step 2 and 3 from that guide, it linked to files required by Windows. Instead, you can get the Moto X driver for Mac here: https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/94931/p/30,6720,8696
You will also need "fastboot" and "mfastboot" for Mac. Fastboot is the program used to lock/unlock bootloader and flash images for (stock based) Android phones. The ADB/Fastboot link in my signature have the mac/linux/windows version included (adb_fastboot.zip file). I think you only need to use the regular fastboot to unlock the phone, but to flash the phone images you will need mfastboot.
To root the phone, check in the Development sections of this device forum: http://forum.xda-developers.com/moto-x-2014
Also, you DO NOT need to unlock the phone bootloader to reflash the factory images.
eksasol said:
For rooting the Moto X it is a bit difficult compared to the Nexus. You need to realize that the Moto X have locked bootloader that prevent you from making changes to the "system" partition. So generally you need to unlock the bootloader first, which is a separate process.
Just a note, that generally when you unlock a phone's bootloader, you void the warranty. Some person here claimed that a Motorola manager confirmed with him that you will not void it with the Moto X Pure edition, however, I do not believe it. The best thing to do is read the fine print and warnings when you goes to unlocked your bootloader from Motorola website.
Another warning, is it easier to permanently (hardware) brick a Motorola than a some other phones if you flash things incorrectly, such as corrupting the CID partition. When I had the Moto X 2013 version, it is possible to brick the phone by downgrading the phone to an older version. I have never tried this with Moto X, but with Nexus devices, you could softbrick the phone if you root it and then do an over the air update, it generally required to use TWRP recovery to apply the over the air update patch for it to work, or reflash the "system" partition of the phone to stock before doing the update. I don't know if this is the same for the Moto X, but I would take the same precaution.
To unlock the bootloader, you can do it at the website here: https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth. Read through this guide to help you: http://forum.xda-developers.com/moto-x-2014/general/guide-unlock-bootloader-moto-x-2014-t2876773
For step 2 and 3 from that guide, it linked to files required by Windows. Instead, you can get the Moto X driver for Mac here: https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/94931/p/30,6720,8696
You will also need "fastboot" and "mfastboot" for Mac. Fastboot is the program used to lock/unlock bootloader and flash images for (stock based) Android phones. The ADB/Fastboot link in my signature have the mac/linux/windows version included (adb_fastboot.zip file). I think you only need to use the regular fastboot to unlock the phone, but to flash the phone image you will need mfastboot.
To root the phone, check in the Development sections of this device forum: http://forum.xda-developers.com/moto-x-2014
Also, you DO NOT need to unlock the phone bootloader to reflash the factory image of the phone.
Click to expand...
Click to collapse
Thank you for being so nice and providing this information
eksasol said:
The Moto X have locked bootloader that prevent you from making changes to the "system" partition. So generally you need to unlock the bootloader first, which is a separate process.
Just a note, that generally when you unlock a phone's bootloader, you void the warranty. Some person here claimed that a Motorola manager confirmed with him that you will not void it with the Moto X Pure edition, however, I do not believe it. The best thing to do is read the fine print and warnings when you goes to unlocked your bootloader from Motorola website.
Another warning, is it easier to permanently brick a Motorola than a some other phones if you flash things incorrectly, such as corrupting the CID partition. With the Moto X 2013 it is possible to brick the phone by downgrading the phone to a too old version. I have never tried this with Moto X, but with Nexus devices, you could softbrick the phone if you root it and then do an over the air update, it generally required to use TWRP recovery to apply the over the air update zip for it to work, or reflash the "system" partition of the phone to stock before doing the update. I don't know if this is the same for the Moto X, but I would take the same precaution.
To unlock the bootloader, you can do it at the website here: https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth. Read through this guide to help you: http://forum.xda-developers.com/moto-x-2014/general/guide-unlock-bootloader-moto-x-2014-t2876773
For step 2 and 3 from that guide, it linked to files required by Windows. Instead, you can get the Moto X driver for Mac here: https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/94931/p/30,6720,8696
You will also need "fastboot" and "mfastboot" for Mac. Fastboot is the program used to lock/unlock bootloader and flash images for (stock based) Android phones. The ADB/Fastboot link in my signature have the mac/linux/windows version included (adb_fastboot.zip file). I think you only need to use the regular fastboot to unlock the phone, but to flash the phone images you will need mfastboot.
To root the phone, check in the Development sections of this device forum: http://forum.xda-developers.com/moto-x-2014
Also, you DO NOT need to unlock the phone bootloader to reflash the factory images.
Click to expand...
Click to collapse
Quick question,
I've seen people use towelroot to root any android device. Will towelroot work with the Moto X? I'm just really hesitant now since you said it was easier to permanently brick and Moto device.
uncalex said:
Quick question,
I've seen people use towelroot to root any android device. Will towelroot work with the Moto X? I'm just really hesitant now since you said it was easier to permanently brick and Moto device.
Click to expand...
Click to collapse
I never use that. The safest thing is to do what is tested and available for that device, so use the current available method here:
http://forum.xda-developers.com/mot...e-edition-superboot-style-root-motox-t2889264
Generally. I don't do any of these, because I do the default Nexus root method which is:
1. Unlocking bootloader
2. Flash TWRP recovery: fastboot flash recovery twrp.img (not yet available for this phone, but soon will be, check the development sections.)
3. Then copy the Chainfire's SuperSU.zip (link in my signature) into the phone and flash while in TWRP recovery.
You shouldn't worry about bricking the device provided if you don't mess around, just stick with rooting and flashing factory firmware if you are new. As long as you don't flash a rom / firmware made for a different phone, or mess with the CID partition or something like that. Or downgrading the firmware after you've already update, which should be fine with a Nexus, but it did kill some Moto X when they downgraded to a firmware that is too old.
If you ever run into issues, you can flash the factory firmware, which is not available yet, but will eventually show up here: http://sbf.droid-developers.org/phone.php?device=37
You will have to download the correct version since there are different variations, but flashing incorrect ones should not brick your device. You can use these instruction to flash the firmware, this is for the Moto G, but the steps are the same: http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657. After you install stock firmware, depend on if you were having issues, you can access the phone's Recovery and do a factory reset, this will wipe all your data, but also clear all the settings which may be required for the phone to boot correctly.
Normally, if your phone is rooted, when you received an over the air update, the first thing I would do before applying that update is to flash the system.img and recovery.img partition of the device back to stock, this will ensure the OTA gets updated successfully, afterward you can re-root the phone. Some people avoid this and flash the OTA's zip file using TWRP recovery, but it is not the official way and not guarantee to work all the time.
Related
Getting confused with the different variations and unlock processes with the X. Let me see if I somewhat understand this? Get a Sprint X.
1. I don't care about warranty and see the moto bootloader unlock much less of a hassle down the road. I unlock my X the moto way. I then fastboot flash recovery recovery.img like normal. Then reboot and go to play and install SuperSU. Now I'm unlocked (can flash roms, updates, or etc via recovery...like normal), and rooted (Titanium Backup, Android WiFi Tether, the usual goods). I assume radios, firmware, kernels, and bootloaders aren't flashable.
2. I want my warranty. I do jcases Pwn with write protection....but now I can't flash anything. If safestrap gets a sprit version, then I can use that to essentially multi boot. I assume this is mainly for Verizon and AT&T users?
1) they are if someone makes them into flashable formats for ya
2) correct
Okay, got a strange question here. I plan on going from the N5 to the unlocked GSM MotoMaker Moto X version. All I want is root with stock recovery (don't really care for a custom recovery, plus I'd like to still receive OTAs). Can I unlock the Moto X bootloader, load TWRP recovery (instead of flash), and then install SuperSU? Or do I *have* to flash TWRP to achieve root?
correct me if im wrong, but I think you can "unlock the Moto X bootloader, load TWRP recovery (instead of flash), and then install SuperSU".
or
use one of the methods in the original android development section to achieve root.
c19932 said:
correct me if im wrong, but I think you can "unlock the Moto X bootloader, load TWRP recovery (instead of flash), and then install SuperSU".
or
use one of the methods in the original android development section to achieve root.
Click to expand...
Click to collapse
Yes, I've looked at those threads. However, in 4.4, a backdoor needs to be introduced in order to maintain root. I'd rather not have to do that and I don't mind unlocking bootloaders. This will be my first, non-Nexus device in awhile, so I just wanted to make sure I can just unlocked the bootloader, load a custom recovery, flash SuperSU and then just have root.
TheCuban said:
Yes, I've looked at those threads. However, in 4.4, a backdoor needs to be introduced in order to maintain root. I'd rather not have to do that and I don't mind unlocking bootloaders. This will be my first, non-Nexus device in awhile, so I just wanted to make sure I can just unlocked the bootloader, load a custom recovery, flash SuperSU and then just have root.
Click to expand...
Click to collapse
Just unlock your boot loader, flash twrp recovery and finally flash supersu and you're good to go. Ota's can not be accepted and flashed with root or custom recovery on the moto
Sent on my Moto X
flashallthetime said:
Just unlock your boot loader, flash twrp recovery and finally flash supersu and you're good to go. Ota's can not be accepted and flashed with root or custom recovery on the moto
Sent on my Moto X
Click to expand...
Click to collapse
Thanks! That's what I thought! I didn't know that root removed the ability to accept OTAs?
TheCuban said:
Thanks! That's what I thought! I didn't know that root removed the ability to accept OTAs?
Click to expand...
Click to collapse
On the moto yes, nexus devices are a different beast
Sent on my Moto X
Hi I am planing my first root and I am honestly a little confused. I am on TMobile with 4.4 KitKat (Moto X).
I understand how to unlock the Bootloader and that I need to install TWRP before I can activate SU.
I am just not sure about the bugs (if any) with TWRP and what version to use.
The reason for my concern is on the TWRP website the Moto X is not listed as a supported device.
Is this video Tutorial still valid - is this how to do it with 4.4 KitKat?
And is this the latest version that works (what are the known bugs)?
I posted these step-by-step instructions in another thread but thought others might like to see them in their own thread. This works for Dev Ed Moto X's running either 4.4 or 4.4.2. If you have a non-Dev Ed with an unlockable bootloader, it works for those, too, but of course you void your warranty if you unlock your bootloader if you have a non-Dev Ed.
To unlock and root the developer edition:
1) Get the unlock code from Motorola and unlock the bootloader by following the directions in this link, including downloading the Android SDK and installing Motorola Device Manager:
Unlock Moto X Bootloader
2) Get mfastboot.exe here:
mfastboot.exe
and place it in the same directory as fastboot (fastboot is in the \sdk\platform-tools subdirectory of the Android SDK).
3) Get the TWRP custom recovery for kit kat here:
TWRP for Moto X 4.4
and place it in the same directory as fastboot.
4) On your unlocked Moto X, enable USB debugging and download SuperSU here:
SuperSU 1.93
5) Double check to make sure USB debugging has been enabled! Put your unlocked Moto X into bootloader mode by pressing the Volume Down button and then the Power button. Hold for about 3 seconds and release and you should be in bootloader mode. Connect your Moto X to your PC via a USB cable.
6) Open a command prompt on your PC and change directory to the folder where mfastboot.exe is.
7) At the command prompt type:
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
to flash the custom recovery to your Moto X.
8) After the custom recovery has been flashed to your Moto X, at the command prompt type:
fastboot reboot-bootloader
to reboot into the bootloader.
(I am not sure if this step is necessary but I read somewhere it was necessary and I did it and it worked).
9) Unplug your device from your PC. Then get into recovery mode by pressing the Volume Down button to highlight recovery mode and pressing the Volume Up button to select the recovery mode.
10) You should now have booted into the Team Win Recovery Project custom recovery. Click on Install to install SuperSu. Scroll down to find the sdcard and select it. Then scroll down to download and select it. Select the SuperSU zip file and swipe to install.
If you want to check to see if you successfully rooted, you can download Root Checker Basic from the playstore and it will tell you if you are rooted.
From what I have read you can use the version of TWRP I linked to above to root 4.4.2.
Remember, to take an OTA, you have to revert back to stock!
bumping this.
+1
Sent from my XT1060 using Tapatalk
Thx
Sent from my XT1058 using Tapatalk
I assume this is the same process regardless of Android build # (ie. After updating to 4.4.2) ...
Tapatalked via my moto x
YankInDaSouth said:
I assume this is the same process regardless of Android build # (ie. After updating to 4.4.2) ...
Click to expand...
Click to collapse
It works for both 4.4 and 4.4.2.
Can anyone post the steps to flash stock recovery to accept the OTA TO 4.4.2? Thanks.
Sent from my XT1060 using Tapatalk
ragingd said:
Can anyone post the steps to flash stock recovery to accept the OTA TO 4.4.2? Thanks.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Grab the firmware for your model here: http://sbf.droid-developers.org/phone.php?device=0
Then you can follow the steps from here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images ... Of course if you don't have flash every component, only what you need. Recovery of course and perhaps system...
Tapatalked via my moto x
Assistance
Perhaps someone could shed some light on this for me. I have a T-Mobile (XT1053) with an unlocked bootloader (I'm certain it's unlocked as I get the unlocked bootloader warning). I unlocked via Motorolas site. I then attempted to install TWRP with mfastboot, which it says it has done, but then when I attempt to reboot into recovery, it just ends up at a black screen (off essentially) and I can only power up as normal. Any one have any ideas?
Tuse0708 said:
Perhaps someone could shed some light on this for me. I have a T-Mobile (XT1053) with an unlocked bootloader (I'm certain it's unlocked as I get the unlocked bootloader warning). I unlocked via Motorolas site. I then attempted to install TWRP with mfastboot, which it says it has done, but then when I attempt to reboot into recovery, it just ends up at a black screen (off essentially) and I can only power up as normal. Any one have any ideas?
Click to expand...
Click to collapse
First, with your device disconnected from any power source, boot into bootloader mode and verify that it says Device is UNLOCKED. Status Code: 3. BTW - the bootloader unlocked warning logo stays even if you relock the bootloader unless you flash a new logo.
Then if it does say device is unlocked, hit Volume Down to highlight Recovery and Volume Up to select recovery. Is that when you see a black screen? It takes TWRP a little while to load.
Cozume said:
First, with your device disconnected from any power source, boot into bootloader mode and verify that it says Device is UNLOCKED. Status Code: 3. BTW - the bootloader unlocked warning logo stays even if you relock the bootloader unless you flash a new logo.
Then if it does say device is unlocked, hit Volume Down to highlight Recovery and Volume Up to select recovery. Is that when you see a black screen? It takes TWRP a little while to load.
Click to expand...
Click to collapse
Nevermind....Thanks for the help, got it going.
thanks!
jodaboda said:
thanks!
Click to expand...
Click to collapse
You are welcome!
So I'm getting an unlock code. I am currently on 4.4.2, and if I read the posts right, I don't have to downgrade to 4.4 to root, TWRP will still root 4.4.2 without issue, right?
EDIT
Nevermind. I've slapped my Moto, so I'm going to SBF back to 4.4.2 to make sure there aren't any... issues...
I'm currently rooted on 4.4. I have made changes to /system, so I can't take the OTA. I got an unlock code today. I understand that unlocking the bootloader will induce a Factory Data Reset. Do I need to SBF to stock 4.4 (or 4.2.2) before I do this? Will the FDR clear up the changes I made?
Furthermore, what order should I do these steps in? If I have 4.4 and unlock/root it, I can't take the OTA with non-stock recovery, correct? I would need a flashable ZIP for TWRP/CWM? Would it be better to unlock, FDR, take OTA to 4.4.2, then do TWRP and root?
Hopefully this isn't too silly of a question, I appreciate any advice for the best path to take on this.
Hey all, just ordered a Dev Edition to go along with my N5 and had a question regarding mfastboot. I downloaded mfastboot from one of the stickies, it was only one file and placed it in my sdk platform tools folder. I was reading on Motorola website about flashing factory images and seen this note-"NOTE: You must use the Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory). Please do NOT use the Android fastboot utility.". First of all, what does it mean included in Windows directory? And I'm guessing about not using the Android fastboot utility, they want you to use "mfastboot flash...." instead of "fastboot flash...."? Just trying to get some research in before I receive the device. I'm used to using fastboot on my Galaxy Nexus and now my N5. I used to have alot of Moto devices before this and using the SBF files in Moto's flashing tool, but never had an unlockable bootloader Moto device that can use some form of fastboot.
t1.8matt said:
Hey all, just ordered a Dev Edition to go along with my N5 and had a question regarding mfastboot. I downloaded mfastboot from one of the stickies, it was only one file and placed it in my sdk platform tools folder. I was reading on Motorola website about flashing factory images and seen this note-"NOTE: You must use the Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory). Please do NOT use the Android fastboot utility.". First of all, what does it mean included in Windows directory? And I'm guessing about not using the Android fastboot utility, they want you to use "mfastboot flash...." instead of "fastboot flash...."? Just trying to get some research in before I receive the device. I'm used to using fastboot on my Galaxy Nexus and now my N5. I used to have alot of Moto devices before this and using the SBF files in Moto's flashing tool, but never had an unlockable bootloader Moto device that can use some form of fastboot.
Click to expand...
Click to collapse
Fastboot can't handle the file sizes. So Motorola made mfastboot. You have to use it when flashing the Moto x.
Sent from my cell phone telephone....
kj2112 said:
Fastboot can't handle the file sizes. So Motorola made mfastboot. You have to use it when flashing the Moto x.
Sent from my cell phone telephone....
Click to expand...
Click to collapse
Ok, gotcha. And I've been reading a little about people wanting to downgrade from 4.4.2, but if you have a locked bootloader and upgraded to the latest bootloader, they can't without bricking. I assume this won't be an issue with an unlocked bootloader, even though I'm not sure of why you would want to downgrade. Edit: I see, for root reasons, but this shouldn't be an issue if you're flashing SuperSU in TWRP?
Edit again: I should read more. Rooting 4.4.2 with an unlocked bootloader isn't an issue if I follow this guide in this thread. Thanks for your help. Looking forward to getting this device.
t1.8matt said:
Ok, gotcha. And I've been reading a little about people wanting to downgrade from 4.4.2, but if you have a locked bootloader and upgraded to the latest bootloader, they can't without bricking. I assume this won't be an issue with an unlocked bootloader, even though I'm not sure of why you would want to downgrade. Edit: I see, for root reasons, but this shouldn't be an issue if you're flashing SuperSU in TWRP?
Edit again: I should read more. Rooting 4.4.2 with an unlocked bootloader isn't an issue if I follow this guide in this thread. Thanks for your help. Looking forward to getting this device.
Click to expand...
Click to collapse
Root will be easy. Same as a nexus. Unlock bootloader, flash custom recovery....root. install superSU if needed.
As far as what's NOT like a nexus....yes, you can still brick downgrading an unlocked device....even the dev edition...which is no different than any other unlocked Moto x. Without going into all the details, you can read about it all over....there is a specific way to downgrade. And you cannot take an ota after....that MAY brick any Moto x...locked or unlocked. There is tonnes of conflicting opinions on this....so read as much as you can, and decide from there. There's very specific ways to downgrade and upgrade after. In my opinion....there's risk involved in all of it.
Just Google "Moto x brick downgrade xda" to read the stories.
If you find you must downgrade from 4.4.2.....study hard before you do.
Sent from my N5, N7, Moto X,G Tab 3 or S2.....
kj2112 said:
Root will be easy. Same as a nexus. Unlock bootloader, flash custom recovery....root. install superSU if needed.
As far as what's NOT like a nexus....yes, you can still brick downgrading an unlocked device....even the dev edition...which is no different than any other unlocked Moto x. Without going into all the details, you can read about it all over....there is a specific way to downgrade. And you cannot take an ota after....that MAY brick any Moto x...locked or unlocked.
If you find you must downgrade from 4.4.2.....study hard before you do.
Sent from my N5, N7, Moto X,G Tab 3 or S2.....
Click to expand...
Click to collapse
Great info. But the only reason people are downgrading from 4.4.2 is if they have a locked bootloader and want to retain root?
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.
Hello,
I got my Moto X few days back from America, its Verizon model (I live in Europe)
its not developer edition and bootloader is locked
...and first issue i noticed is when i try to reset to factory with power UP + DOWN volume i couldnt get recovery.. when i go to recovery settings i see moto logo and then verizon picture.. there is no "dead android" and phone boots normaly.
...second thing there was android 4.4 on it and i got notifications to update it, so i was like why not, lets do it... and after i decided to update, phone keeps rebooting itself, and i dont know what to do it stays awake like 10-20sec and reboot again. Cant belive i bricked it that way!
Phone seems that its not rooted or anything, but idk maybe it was and then back to stock.. Is there any solution?
Thanks in advance to any1 who can help me slove the problem
Cheers
Resurrecting A Bricked Moto X
drvoje said:
Hello,
I got my Moto X few days back from America, its Verizon model (I live in Europe)
its not developer edition and bootloader is locked
...and first issue i noticed is when i try to reset to factory with power UP + DOWN volume i couldnt get recovery.. when i go to recovery settings i see moto logo and then verizon picture.. there is no "dead android" and phone boots normaly.
...second thing there was android 4.4 on it and i got notifications to update it, so i was like why not, lets do it... and after i decided to update, phone keeps rebooting itself, and i dont know what to do it stays awake like 10-20sec and reboot again. Cant belive i bricked it that way!
Phone seems that its not rooted or anything, but idk maybe it was and then back to stock.. Is there any solution?
Thanks in advance to any1 who can help me slove the problem
Cheers
Click to expand...
Click to collapse
Try this http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
Is there any way to try to delete chache or factory reset before flashing to stock rom
drvoje said:
Is there any way to try to delete chache or factory reset before flashing to custom rom
Click to expand...
Click to collapse
If its not the developer edition for Verizon, the bootloader is likely locked, so you can NOT flash custom roms (unless you, or a previous owner, got a bootloader unlock code from the China Middleman and used it)
Did you buy the phone used, or new? If used, then it is possible that it was rooted using RockMyMoto, SlapMyMoto or the like... and the boot loop while trying to install an update could be due to that. If so, erasing cache will stop the boot loop. This can be done from stock recovery, or when in Bootloader/FastbootAP mode.
How to Boot into recovery -> http://mark.cdmaforums.com/MotoX-EnterStockRecovery.htm
If that doesn't work, try bootloader/fastboot....
How to get a working AndroidSDK/PlatformTools/ADB/Mfastboot setup -> http://mark.cdmaforums.com/ADB.htm
How to boot the phone into fastboot mode -> http://mark.cdmaforums.com/MotoX-BootloaderMode.htm
from your PC, do a mfastboot erase cache
to reboot the phone, mfastboot reboot
Optionally, you could do a mfastboot erase userdata before rebooting, to remove all data, apps, etc.
If erasing cache fixes the boot loop, you might just want to try using RSDLite and reflashing the STOCK rom, recovery, etc. (Download the Verizon 4.4.4 SBF from -> http://sbf.droid-developers.org/phone.php?device=0 then follow -> http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 ) It would undo anything that was done to root your device, and put you back to factory fresh. The only reason not to, would be if you care about rooting and disabling write protection..
With a locked bootloader, If your phone is still on 4.4 (aka 4.4.0), and still has that older bootloader and gpt.bin, you could use SlapMyMoto to root, and MotoWpNoMo to disable write protection. Just don't take any updates. You could cause a bootloop, but more importantly it will re-enable write protection with no way to disable it again (unless you can unlock the bootloader).
Once your phone is on 4.4.2 or above, you can't properly downgrade the ROM, bootloader and gpt.bin to use the exploits used by SlapMyMoto/MotoWpNoMo. There is a TowelPieRoot which is a temp root that works on 4.4.2. Temp root in the fact that it doesn't survive power off/on, so it needs to be redone each time. Also it doesn't disable write protection, so any changes made to /system or the like are also lost at power off/on (aka hard boot).
Once on 4.4.4, you can't properly downgrade the ROM, bootloader and gpt.bin, and there are no exploits to root, and no way to disable write protection.
If you can use the China Middleman thread to get a bootloader unlock code, then you don't need to worry about the exploits, and you can then root and disable write protection just as if you had a developer edition. Also JCASE may be updating their Sunshine tool to use the exploit found by Dan Rosenberg to unlock the bootloader on the Moto X, but there is no exact date yet of when it will be available (so far "next few weeks" has been said, but nothing more specific), and there is discussion around will it work for those who took the 4.4.4 update or not (no confirmation yet either way).
KidJoe;55503494
If that doesn't work said:
[*]How to get a working AndroidSDK/PlatformTools/ADB/Mfastboot setup ->
[*]How to boot the phone into fastboot mode ->
[*]from your PC, do a mfastboot erase cache
[*]to reboot the phone, mfastboot reboot
[/list]
Click to expand...
Click to collapse
did this with mfastboot image and worked like charm
bdw now i will need some time reading what is best to do with my unlockable bootloader verizon phone, if u have any sugestions please let me know.
and tnx for the help again mate
drvoje said:
bdw now i will need some time reading what is best to do with my unlockable bootloader verizon phone, if u have any sugestions please let me know.
Click to expand...
Click to collapse
You said its a verizon phone, but not the developer edition..
So at this point, the only way to unlock the bootloader is the China Middleman thread (in the general section). When JCASE updates Sunshine for the X (in the coming week or two), you can try that.
Otherwise, there isn't anything you can do.
and for stock android update? which one is the best for moto x? now it is 4.4.0
shall i rsd lite it to 4.4.2 or 4.4.4 or just stay current one?
bdw i need to rsd lite frimware anyway if i plan to use OTA update again perhaps when android L come? For now i just keep ignoring them
and yes its NOT developer edition phone
drvoje said:
and for stock android update? which one is the best for moto x? now it is 4.4.0
shall i rsd lite it to 4.4.2 or 4.4.4 or just stay current one?
bdw i need to rsd lite frimware anyway if i plan to use OTA update again perhaps when android L come? For now i just keep ignoring them
and yes its NOT developer edition phone
Click to expand...
Click to collapse
THe best depends on what you want to do.
Like I said before. IF you have 4.4 (aka 4.4.0) on the phone, and NEVER had anything newer on there (not 4.4.2 or 4.4.4), then stay there, look at SlapMyMoto and MotoWpNoMo to root and disable write protection.
Once you get 4.4.2 on there, you can root, but its temp root, and write protection can NOT be disabled.
4.4.4 you can't root.
Other than that, I can't say I really find too much difference. The camera is better in 4.4.4, but the battery isn't performing as well lately (could be a recent app update).
can i do this on my phone now - without fear of bricking it:
from my pc to run mfastboot again
then to clear chache
then to delete all user data
then to use rsd lite and flash Android 4.4
Blur_Version.140.45.5.ghost_verizon.Verizon.en.US even i alrdy have 4.4 now?
..because i dont know what is done to my phone before and i want to make sure its like "new" device
i know i can not downgrade, but can i flash same frimware? just to make sure thats all stock again
bdw Im stll unable to enter recovery after fastboot :/ is it that because of locked bootloeader? or because it was rooted with any method? i cant find superuser
and then to wait for solution to unlock bootleader?
Thanks in advance
You can always re-flash the same rom that is on your phone.
You just never want to down grade, or flash something older than what is on your phone.
As for not being able to enter Stock Recovery... early versions of the RockMyMoto and such did a trick which made it so that when you picked boot to recovery, it booted to regular system with write protection disabled. If that was used on your phone before you purchased it, that could be the issue. Using RSDLite and flashing back to 100% stock will undo that.
But You never answered if you got the phone new or used.
IF new, then you have some other issue (either you're not doing it right, or there is something wrong with the phone).
If used, you don't know what was done before you received it. Someone might have rooted, etc.. then just removed SuperSU to appear non-rooted when selling, rather than flashing back to stock.
thanks for the reply...
yes phone is used before but same like new... and what i found that phone was rooted by some method.. i made this screenshots, look in attachment..
bdw i dont see super su anywhere in apps? how to remove?
and i got everything rdy to flash it, i was just waiting you to conform if its doable...
and what did u mean by this:
"With a locked bootloader, If your phone is still on 4.4 (aka 4.4.0), and still has that older bootloader and gpt.bin, you could use SlapMyMoto to root, and MotoWpNoMo to disable write protection. Just don't take any updates. You could cause a bootloop, but more importantly it will re-enable write protection with no way to disable it again (unless you can unlock the bootloader)."
is that what happened to me?
and have question about one more thing
my country does not support lte and in my region 3g is bad... i have stable signal all the time but i would like to use edge only (GSM), can i do that using some widgets and if can which ones?
drvoje said:
thanks for the reply...
yes phone is used before but same like new... and what i found that phone was rooted by some method.. i found this screenshot in phone, look in attachment..
bdw i dont see super su anywhere in apps? how to remove?
and i got everything rdy to flash it, i was just waiting you to conform if its doable...
Click to expand...
Click to collapse
If you mean you don't see a SuperSU icon in the app drawer, then they probably un-installed SuperSU before selling it rather than completely unrooting. If you mean you have an icon in the app drawer, but don't see it to uninstall under Settings -> Apps.. I don't know why that would be.
drvoje said:
and what did u mean by this:
"With a locked bootloader, If your phone is still on 4.4 (aka 4.4.0), and still has that older bootloader and gpt.bin, you could use SlapMyMoto to root, and MotoWpNoMo to disable write protection. Just don't take any updates. You could cause a bootloop, but more importantly it will re-enable write protection with no way to disable it again (unless you can unlock the bootloader)."
is that what happened to me?
Click to expand...
Click to collapse
Yes, that could be what happened to you. There are many reports of locked bootloader users who used those older root processes who then upgraded using the OTA from 4.4 to 4.4.2 that encountered bootloops and other issues. It was often recomended to reflash to 100% stock.
And what I meant is that if you are on 4.4 (aka 4.4.0) with all its parts, it is vulnerable and the older exploits can still be used to root and disable write protection without unlocking your bootloader. Search for SlapMyMoto for more details. Some people tried to be cute and mix/match parts which caused issues. Mostly the issues around downgrading are caused by GPT.BIN and Motoboot.IMG parts, their versions, if they've been upgraded and no longer match the rest of the rom on the phone, etc. (and that is a LONG story...)
drvoje said:
and have question about one more thing
my country does not support lte and in my region 3g is bad... i have stable signal all the time but i would like to use edge only (GSM), can i do that using some widgets and if can which ones?
Click to expand...
Click to collapse
You can TRY using something like LTE On/Off to open the hidden menu and set for GSM Auto (PRL) or LTE GSM Auto(PRL). I'm not sure which would work best.
Oh, and as for unlocking the bootloader, I've mentioned the China Middleman and JCASE's Sunshine so there are the links to read up if you want to do it.
The China Middleman is just like if you got the code directly from Moto. I don't know what the Jcase tool is like yet.
thanks again!
so i dont see a SuperSU icon in the app drawer - uninstalled probably and that is why i can not enter stock recovery
I am still on android 4.4 didnt do anything yet...
what u recommend me to do? to rsd lite it to 4.4 again? right?
than i will root my device
and about bootloader, my device is 9.2013, so i will wait JCASE's Sunshine and support him
ps. wiget works gr8 :good:
Just want to write some words, i just took jcase tool which is very easy to setup (made for noobs like me) and i got bootloader UNLOCKED on my verizon NON developer edition phone
and now i RSD lite to 4.4 stock rom
would like to hear from KidJoe what is best to do with my moto x now thanks
Now you can update to 4.4.4,whichever methods you want, and still root it. Done. ?
drvoje said:
Just want to write some words, i just took jcase tool which is very easy to setup (made for noobs like me) and i got bootloader UNLOCKED on my verizon NON developer edition phone
and now i RSD lite to 4.4 stock rom
would like to hear from KidJoe what is best to do with my moto x now thanks
Click to expand...
Click to collapse
Follow [mention]@KJ[/mention] 's advice and update to 4.4.4, and follow the Dev Edition or Unlocked Bootloader guides to rooting (flash the latest TWRP and root.)