Alright I cant seem to update my Moto x from 4.2.2 to 4.4 with the ota in order to get slapmymoto to work, it says "an unexpected error has occurred." in system updates. I also tried to update through recovery by putting the zip into the sdcard. but I get "installation aborted" What gives?
I was rooted before on 4.4 and safestraped to 4.4.2 but then went back to 4.2.2. my bootloader is still the 4.2.2 version and write protection is disabled with MotoWpNoMo.
I am able to update to 4.4 in bootloadermode but this gets rid of all the slapmymoto files that are needed once on 4.4 so im assuming i need to either sideload or take the ota which i cant do.
Any help would be appreciated, Thanks
quaddles said:
Alright I cant seem to update my Moto x from 4.2.2 to 4.4 with the ota in order to get slapmymoto to work, it says "an unexpected error has occurred." in system updates. I also tried to update through recovery by putting the zip into the sdcard. but I get "installation aborted" What gives?
I was rooted before on 4.4 and safestraped to 4.4.2 but then went back to 4.2.2. my bootloader is still the 4.2.2 version and write protection is disabled with MotoWpNoMo.
I am able to update to 4.4 in bootloadermode but this gets rid of all the slapmymoto files that are needed once on 4.4 so im assuming i need to either sideload or take the ota which i cant do.
Any help would be appreciated, Thanks
Click to expand...
Click to collapse
If you updated to 4.4 in BL mode (unless you just skipped gpt.bin and motoboot.img) you are now on the 4.4 bootloader. Not that important though, as wp-off will still work. If you had skipped the command "fastboot erase userdata", it wouldn't have deleted all your files. Plus you could have found the 4.4 OTA and applied it via stock recovery....
If you can't follow jcase's SlapMyMoto thread for some reason (really not understanding why its not working for you), you can search the forum. There is another NEW way of doing this that doesn't require downgrading to 4.2.2. Basically it involves using PIE + MotoWpNoMo to achieve root/wp-off on 4.4 without having to downgrade. Many users reported success. I don't have the link - so just search. If I find it, I'll edit the link in here.
Good Luck
EDIT: Most of the relevant info regarding this is in the Droid Ultra forum here: http://forum.xda-developers.com/droid-ultra/general/root-guide-4-4-t2822032
Although I have seen reports of users successfully doing this on the Moto X. Good Luck
EDIT 2: Also HERE, in the Moto X section: http://forum.xda-developers.com/showpost.php?p=54337535&postcount=252
You won't find much else on this, because hardly anyone is still on 4.4....though it DOES have its reasons....(namely safestrap)
samwathegreat said:
If you updated to 4.4 in BL mode (unless you just skipped gpt.bin and motoboot.img) you are now on the 4.4 bootloader. Not that important though, as wp-off will still work. If you had skipped the command "fastboot erase userdata", it wouldn't have deleted all your files. Plus you could have found the 4.4 OTA and applied it via stock recovery....
If you can't follow jcase's SlapMyMoto thread for some reason (really not understanding why its not working for you), you can search the forum. There is another NEW way of doing this that doesn't require downgrading to 4.2.2. Basically it involves using PIE + MotoWpNoMo to achieve root/wp-off on 4.4 without having to downgrade. Many users reported success. I don't have the link - so just search. If I find it, I'll edit the link in here.
Good Luck
EDIT: Most of the relevant info regarding this is in the Droid Ultra forum here: http://forum.xda-developers.com/droid-ultra/general/root-guide-4-4-t2822032
Although I have seen reports of users successfully doing this on the Moto X. Good Luck
Click to expand...
Click to collapse
"Plus you could have found the 4.4 OTA and applied it via stock recovery...." that is where it is saying "installation aborted"
Im going to try to pie root right now. I knew about it and thought it was tethered only but with wp-off its a full root. right?
Thanks for the help
quaddles said:
"Plus you could have found the 4.4 OTA and applied it via stock recovery...." that is where it is saying "installation aborted"
Im going to try to pie root right now. I knew about it and thought it was tethered only but with wp-off its a full root. right?
Thanks for the help
Click to expand...
Click to collapse
^^ did you try flashing stock recovery again? I'm not -exactly- sure how Safestrap works, but I believe it modifies stock recovery, hence making it impossible to apply an OTA without flashing Stock recovery back...Nevermind that...I see you already SBF'd to stock 4.4, which SHOULD have written stock recovery back, assuming you did it properly..
Right...see the #2 edit above for more info. PIE + WpMotoNoMo (ON 4.4 ONLY!!!) = root + wp-off
Let me know how it works out for you.
samwathegreat said:
^^ did you try flashing stock recovery again? I'm not -exactly- sure how Safestrap works, but I believe it modifies stock recovery, hence making it impossible to apply an OTA without flashing Stock recovery back...Nevermind that...I see you already SBF'd to stock 4.4, which SHOULD have written stock recovery back, assuming you did it properly..
Right...see the #2 edit above for more info. PIE + WpMotoNoMo (ON 4.4 ONLY!!!) = root + wp-off
Let me know how it works out for you.
Click to expand...
Click to collapse
Ughhhh this is a nightmare
C:\Users\P\Desktop\android\sdk\platform-tools>adb shell /data/local/atvc/root
.sh
rm failed for /data/local/atvc/blop.asec, No such file or directory
mkdir failed for /data/local/atvc/dalvik-cache, File exists
pie by jcase
want to buy me pie? paypal-> [email protected]
C:\Users\Paul\Desktop\android\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # id
id
uid=0(root) gid=0(root) context=u:r:kernel:s0
[email protected]:/ #
This is what i get with pie then i try to install supersu but it says installation failed.
btw this is what i used to get to 4.2.2 and it is also only way i can update to 4.4 because from 4.2.2 i cant receive the ota or use recovery to get to 4.4 to use slapmymoto. im not sure why i cant get the ota, maybe this method doesn't completely go back to stock not sure...
http://forum.xda-developers.com/moto-x/development/kit-restore-moto-x-to-stock-rsd-lite-t2560571
Have you tried the toolkit ? I did this a couple months ago and easy http://forum.xda-developers.com/moto-x/development/tool-moto-x-toolkit-v1-4-0-t2477132
quaddles said:
Ughhhh this is a nightmare
C:\Users\P\Desktop\android\sdk\platform-tools>adb shell /data/local/atvc/root
.sh
rm failed for /data/local/atvc/blop.asec, No such file or directory
mkdir failed for /data/local/atvc/dalvik-cache, File exists
pie by jcase
want to buy me pie? paypal-> [email protected]
C:\Users\Paul\Desktop\android\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # id
id
uid=0(root) gid=0(root) context=u:r:kernel:s0
[email protected]:/ #
This is what i get with pie then i try to install supersu but it says installation failed.
btw this is what i used to get to 4.2.2 and it is also only way i can update to 4.4 because from 4.2.2 i cant receive the ota or use recovery to get to 4.4 to use slapmymoto. im not sure why i cant get the ota, maybe this method doesn't completely go back to stock not sure...
http://forum.xda-developers.com/moto-x/development/kit-restore-moto-x-to-stock-rsd-lite-t2560571
Click to expand...
Click to collapse
Did you read the posts I linked you to? You obviously didn't re-run MotoWpNoMo and apply PIE during each reboot. It's clearly listed in the posts I linked. Timing is CRITICAL with this. Looks like you just ran PIE once and expected it to work....not the case. Write protection is still applied, hence the reason you can't install SuperSU. And the output from PIE is normal.
EDIT: @quaddles : Yeah...you SHOULD be following the instructions in the "Return to Stock" thread in the General Sub-forum. I don't know anything about that guide you linked above. Here is the correct one: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 The one you are using probably DOESN'T flash back to 100% stock...
G-Rock13 said:
Here's what I did:
First, I used PIE to root then used MotoWpNoMo to disable write-protect. Then I used PIE to root a second time after MotoWpNoMo reboot #1 and finally used PIE again to root a third time after MotoWpNoMo reboot #2. After five attempts I got it to finally work. Twinkyz1979 post was dead-on. Timing the execution of PIE root is CRITICAL after the reboots! Now I'm enjoying persistent root without having to SlapMyMoto! Yay!
Click to expand...
Click to collapse
You might try @doitinthedirt 's suggestion (using the toolkit) with option 12 (although this is the same as what you have been trying with SlapMyMoto - only automated...)
I have a Republic Wireless Moto x (XT1049) with an unlocked bootloader, and knowing how rare it is (literally 0 support on any thread/site/country), I'm still going to ask a few questions, maybe start a band of RWers with unlocked Moto Xs that will only survive by sticking together/cuddling for warmth.
Before anyone starts to disbelieve me, I do have an xt1049 (not confusing it) with an unlocked bootloader (not confusing it with simply being rooted). I achieved this by purchasing a $25 license for SunShine by the jcase crew, and it worked wonderfully for whoever is out there, looking to unlock you xt1049. Why did I want to fork out 25 bucks for this? I started to hate the grind with towelpieroot+xposed every time I turned my device on, plus things like Viper4Android (among others) don't work well with temp roots, plus no write protection off, which has its purposes.
So on to my questions, (1) are there any custom ROMs designed for XT1049? (Probably no, so before you tell me no, (1a) are there any that work with my model?)
(2) If no one knows 1 or 1a, theoretically, what would happen if I flashed a ROM, say, CM 11/12, onto my phone? Please, to avoid a clutter of responses that consist of "idk probs no," have some level of confidence before answering.
For the theorists, Republic has a bunch of republic things going on in the background for the plural wifis to work correctly, how would these services (wifi calling/stuff) be affected, but also how would more universal things (moto x line specifically, but universal across carriers)? I don't know a whole lot about carriers because I have a serious phobia of letter combinations like CDMA and LTE, but to help understanding the "universal things" I mentioned, looking at the CM11 download page, one ZIP file can be used to flash the XT1053, XT1056, XT1058, XT1060, XT1055, you get the point. OK you got me, to refine it down,(3) I'm just trying to get a complete understanding of what would happen without trying it. I might/probably/would try it some other day, I have a load of college on my plate so if I have to undo anything (another question: (4) would I be able to revert to republic stuff if I have the correct zip, or what would have to go wrong so that I wouldn't be able to get to my bootloader/recovery?) I don't pay my phone bill, and my pops would be pissed if he read this so that's why I might not want to test it, but if there is a way to return I will be ballsy anyway.
(5) A question that I've had for a while but I never needed it answered, bootloaders remain unlocked after an update, right? My old phone (RIP HTC design 4g ) lost support at 4.2 and I never updated it the entire time it was rooted/unlocked. My moto on the other hand has 4.4.4 coming out soon and yeah I don't know the answer to it. I think it's implied it stays unlocked, but no one ever says it directly...
Well, thanks if you made it this far! And I would link whatever I could but I am a new user to this site and I'm restricted, you can just look up Sunshine jcase if interested.
Hi, this is my first time posting on xda, so I apologize ahead of time if I don't do it correctly. I'm also very interested in what can be done with a Republic Wireless Moto X (2013) in order to update to 4.4.4 and still be able to use TowelPieRoot and Xposed. I also looked at the SunShine unlocker but have not tried it yet. I'm currently on 4.4.2 and I just go the update notification today for 4.4.4 (much later than my wife's phone, which does not have TowelPieRoot or Xposed). Just wondering if you had any success with updating and still remaining unlocked and able to use TowelPieRoot and Xposed. Thanks for any feedback!
Unlocked boot loader...
Today I unlocked the boot loader on my Republic Wireless XT1049, since they were trying to force me to upgrade to android 4.4.4 from 4.4.2, and I realized that running Sunshine on 4.4.2 would be my last opportunity for unlocking the boot loader, before upgrading. I haven't yet rooted or updated to 4.4.4. Have either of you upgraded to 4.4.4 android with an uplocked boot loader, and re-rooted? Is there anything different about root in 4.4.4 vs 4.4.2, if you have an unlocked boot loader? Would the "Rooting Unlocked Bootloader" instructions in this guide work in android 4.4.2 and/or 4.4.4? Or, would Sunshine SUInstaller make that unnecessary? (Hopefully SUInstaller would work in 4.4.4...)
I'm on 4.4.2 with an unlocked bootloader from when the china man was giving out unlock codes. Having my code guarantees that I can unlock my bootloader even after locking it again for an update. I'm not sure how Sunshine works but be careful before taking the 4.4.4. update and do lots of research before doing anything to your device.
To answer some questions:
CM11 and CM12 will flash fine. The problem you'll have is a loss of phone functionality. With Republic, their app is baked into their custom ROM. But you can use it like a tablet and get a feel for what lollipop will look like on our phone. Make sure you have a nandroid backup or you'll lose everything. CM11 requires a wipe before it will install and CM12 requires you have CM11 (at least it did the last I checked) so you'll want to make sure you have a backup so you can get your working RW ROM back. Otherwise you'll have to flash the Stock RW ROM and start from scratch.
I've done lots of digging and have been able to get the Republic app working on CM11 and CM12 but the functionality is still missing. My tweaks allow texts on CM11 but it's from the "hidden number" not the RW number and the formatting is messed up upon receiving a message. Calls don't work at all on either ROM.
I posted a thread in General with my instructions to get the app working. I'm hoping someone with more ROM knowledge than myself can take a look at the RW Stock ROM and see what else needs to be moved into a CM ROM to give us functionality. I tried moving everything over and skipping duplicates and now I've seriously messed my phone up and will likely have to relock, unlock, flash TWRP and hope I can restore from my TWRP backup.
I've only tried CM11 and CM12, I have no idea how another ROM will affect our phone. Chances are you'll end up in an endless boot after flashing. You could brick the phone though, or end up in a situation like I'm currently in.
bstevens23 said:
I'm on 4.4.2 with an unlocked bootloader from when the china man was giving out unlock codes. Having my code guarantees that I can unlock my bootloader even after locking it again for an update. I'm not sure how Sunshine works but be careful before taking the 4.4.4. update and do lots of research before doing anything to your device.
Click to expand...
Click to collapse
Thanks for the warning about upgrading. I still haven't decided to allow my phone to upgrade to 4.4.4 android, but the most immediate issue I face with not upgrading is that my phone automatically downloaded the update, and now it is incessantly prompting me to install it. I have found any way to stop the annoying prompting. I would rather wait before updating, because there are always details you don't know about such upgrades, and I have no pressing need for the upgrade, except that ultimately I would like to be able to root my phone, also allow for writing to the system partition, so that recording calls would be possible.
You raise a good point in mentioning your capability to lock and unlock the boot loader. As far as I know Sunshine only unlocks the boot loader. I haven't seen that it provides any code or other means for re-locking it. It is also my understanding that technically there are 3 possible locking states of the boot loader. The factory state not only being locked but also indicating that it was never unlocked. It's my understanding that once a boot loader is unlocked, it can be re-locked, but never restored to the factory locked state that indicates it was never unlocked. That said, I don't know whether it matters if the boot loader is unlocked when running the Republic Wireless upgrade. In other threads I had read claims that once a boot loader is unlocked, that it should remain unlocked after OS upgrades, and as such, in a state that would allow for rooting. But, I am far from an expert on that.
bstevens23 said:
To answer some questions:
CM11 and CM12 will flash fine. The problem you'll have is a loss of phone functionality. With Republic, their app is baked into their custom ROM. But you can use it like a tablet and get a feel for what lollipop will look like on our phone. Make sure you have a nandroid backup or you'll lose everything. CM11 requires a wipe before it will install and CM12 requires you have CM11 (at least it did the last I checked) so you'll want to make sure you have a backup so you can get your working RW ROM back. Otherwise you'll have to flash the Stock RW ROM and start from scratch.
I've done lots of digging and have been able to get the Republic app working on CM11 and CM12 but the functionality is still missing. My tweaks allow texts on CM11 but it's from the "hidden number" not the RW number and the formatting is messed up upon receiving a message. Calls don't work at all on either ROM.
I posted a thread in General with my instructions to get the app working. I'm hoping someone with more ROM knowledge than myself can take a look at the RW Stock ROM and see what else needs to be moved into a CM ROM to give us functionality. I tried moving everything over and skipping duplicates and now I've seriously messed my phone up and will likely have to relock, unlock, flash TWRP and hope I can restore from my TWRP backup.
I've only tried CM11 and CM12, I have no idea how another ROM will affect our phone. Chances are you'll end up in an endless boot after flashing. You could brick the phone though, or end up in a situation like I'm currently in.
Click to expand...
Click to collapse
I hope there will be others who are willing to collaborate in your endeavors to reverse engineer the ROM that you are working on. Are you pursuing that because nobody has been able to root a Republic Wireless XT1049 on android 4.4.2 with a ROM? It seems that the original poster found some way to root 4.4.2 with his unlocked boot loader. I would be interest to know how he did that.
gxdaspark said:
Thanks for the warning about upgrading. I still haven't decided to allow my phone to upgrade to 4.4.4 android, but the most immediate issue I face with not upgrading is that my phone automatically downloaded the update, and now it is incessantly prompting me to install it. I have found any way to stop the annoying prompting. I would rather wait before updating, because there are always details you don't know about such upgrades, and I have no pressing need for the upgrade, except that ultimately I would like to be able to root my phone, also allow for writing to the system partition, so that recording calls would be possible.
You raise a good point in mentioning your capability to lock and unlock the boot loader. As far as I know Sunshine only unlocks the boot loader. I haven't seen that it provides any code or other means for re-locking it. It is also my understanding that technically there are 3 possible locking states of the boot loader. The factory state not only being locked but also indicating that it was never unlocked. It's my understanding that once a boot loader is unlocked, it can be re-locked, but never restored to the factory locked state that indicates it was never unlocked. That said, I don't know whether it matters if the boot loader is unlocked when running the Republic Wireless upgrade. In other threads I had read claims that once a boot loader is unlocked, that it should remain unlocked after OS upgrades, and as such, in a state that would allow for rooting. But, I am far from an expert on that.
Click to expand...
Click to collapse
I have yet to update to 4.4.4 because I've heard of people having problems with Messenger after the update. I'm waiting to see how my wife's phone functions on it before I make the leap and get the stock recovery back to take the OTA. Until then, I get the obnoxious update warning constantly as well. I could probably freeze the app with Titanium, we'll see if it bothers me enough in the next few days. I'm not sure if the bootloader will need to change for the update as I've only ever had 4.4.2 since I was bootloader unlocked. I know flashing the stock recovery is needed and I feel like that may require a relocked bootloader. As far as I know, from a software/OTA side at least, relocked and locked are equal. Republic/Moto would care about relocked but I don't think the system throws any flags for taking stock software updates because of it.
I hope there will be others who are willing to collaborate in your endeavors to reverse engineer the ROM that you are working on. Are you pursuing that because nobody has been able to root a Republic Wireless XT1049 on android 4.4.2 with a ROM? It seems that the original poster found some way to root 4.4.2 with his unlocked boot loader. I would be interest to know how he did that.
Click to expand...
Click to collapse
I'm pursuing this because I want CM12 to test out Lollipop since I have no idea when Republic is going to push it out to us. I haven't heard of Sprint getting soak tests yet and we're typically 2-3 months behind Sprint. Waiting until May when Google I/O takes place will be difficult for me, especially if they break their current trend and announce the next version of Android.
My goal is much more ambitious than just CM12 though. I got the Republic app to recognize CM11 as native, meaning if someone can figure out which radio portions I'm missing and get the phone functioning as if it were the Republic ROM, we would not be restricted to just the stock ROM/software anymore. I've been an Android user for a few years now and I've always had the ability to flash whatever I wanted if it was available for my device. Since joining RW, I'm extremely restricted. I have 1 ROM option, which is only helpful because it allows Xposed. But I no longer have the ability to test the newest version of Android whenever I please, or to give a custom ROM a spin if I feel like it. If we can figure out what makes the RW ROM function properly, that wouldn't be a restriction anymore. That's my goal.
Unfortunately, I have no idea what I'm doing. The best I can do is compare files and try pulling random things. I'm hoping someone with more ROM knowledge will be able to take a look at the RW ROM and see which pieces I'm missing. I feel like CM12 is going to be a bit more complicated though, and might not be possible at this time. We'll see though. I know something is getting screwed up with the MEID because the Republic app doesn't recognize an MEID at all. How to go about fixing that? Beyond me.
step-by-step, 4.4.4 root
I think the steps would be: first Sunshine, then 4.4.4 OTA, then root, then Xposed. Is that correct? After I unlock with Sunshine, will my phone still prompt me to update to 4.4.4? Or do I need to need to download 4.4.4 and then flash it? After Sunshine, do I FIRST need to flash 4.4.2 custom recovery? If so, where can I get that? I should probably get a copy of that anyway, even if I don't need it now.
It seems pretty easy overall, but I think I need to refer to a step-by-step guide to make sure I do all of this correctly. If I start the guide below, can you please be so kind as to make corrections for me? Add, remove, or change steps? Thanks!!! Here it goes, this is my best guess at the steps I need to take:
1. Go to theroot.ninja and complete the unlock process.
2. Download and install Android SDK on PC (installer_r24.1.2-windows.exe).
3. Download and install Motorola Device Manager on PC.
4. Get mfastboot.exe and place it in the same directory as fastboot (fastboot is in the \sdk\platform-tools subdirectory of the Android SDK).
***Do I just drag this .exe to the said folder on my PC?***
5. Get the TWRP for Moto X 4.4 custom recovery for kit kat and place it in the same directory as fastboot.
6. Enable USB debugging and download SuperSU
7. 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.
8. Open a command prompt on your PC and change directory to the folder where mfastboot.exe is.
9. 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.
***Is this the version of TWRP I need to root 4.4.2? What about 4.4.4? Or do I just flash the 4.4.4 OTA on top of 4.4.2?***
10. After the custom recovery has been flashed to your Moto X, at the command prompt type: fastboot reboot-bootloader to reboot into the bootloader.
11. 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.
12. 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.
*** I also saw this:
"For new users who have only unlocked their bootloaders, flashed TWRP and rooted, then only make use of apps like RootExplorer, QuickBoot(reboot), Adfree, Wifi Tether for Root, etc.. that do NOT modify /System, the easiest way to take the OTA is to...
download the SBF/FXZ for your carrier and the Software Version currently on your phone. Do NOT use a lower Software Version, or the SBF/FXZ for another carrier or you will risk bricking your phone!!!
unzip it.
boot the phone into fastbootAP/bootloader mode
use mfastboot to flash the recovery.img to your phone - mfastboot flash recovery recovery.img
immediately reboot into fastbootAP/bootloader - mfastboot reboot-bootloader
select recovery.
once you've entered stock recovery, you can reboot back into normal system.
take the OTA when it gets to your phone.
you will likely remain rooted, and its optional to flash your custom recovery back on there via mFastboot
However, if you are running Xposed, did a wifi tethering hack, edited build.prop, DELETED bloat from your phone, your phone will fail the OTA Update's validation checks and it will fail. In that case, you can boot back into fasbootAP/Bootloader mode, use mfastboot to flash system.img (mfastboot flash system.img ) from the SBF/FXZ you already downloaded and unzipped. then reboot ( mfastboot reboot ), and try the OTA again. You will need to re-root by flashing custom recovery (like twrp), and re-install SuperSU."
***Is there any way to break down the whole thing into simpler steps???*** THANKS!!!
PackerDroid said:
I think the steps would be: first Sunshine, then 4.4.4 OTA, then root, then Xposed. Is that correct? After I unlock with Sunshine, will my phone still prompt me to update to 4.4.4? Or do I need to need to download 4.4.4 and then flash it? After Sunshine, do I FIRST need to flash 4.4.2 custom recovery? If so, where can I get that? I should probably get a copy of that anyway, even if I don't need it now.
It seems pretty easy overall, but I think I need to refer to a step-by-step guide to make sure I do all of this correctly. If I start the guide below, can you please be so kind as to make corrections for me? Add, remove, or change steps? Thanks!!! Here it goes, this is my best guess at the steps I need to take:
1. Go to theroot.ninja and complete the unlock process.
2. Download and install Android SDK on PC (installer_r24.1.2-windows.exe).
3. Download and install Motorola Device Manager on PC.
4. Get mfastboot.exe and place it in the same directory as fastboot (fastboot is in the \sdk\platform-tools subdirectory of the Android SDK).
***Do I just drag this .exe to the said folder on my PC?***
5. Get the TWRP for Moto X 4.4 custom recovery for kit kat and place it in the same directory as fastboot.
6. Enable USB debugging and download SuperSU
7. 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.
8. Open a command prompt on your PC and change directory to the folder where mfastboot.exe is.
9. 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.
***Is this the version of TWRP I need to root 4.4.2? What about 4.4.4? Or do I just flash the 4.4.4 OTA on top of 4.4.2?***
10. After the custom recovery has been flashed to your Moto X, at the command prompt type: fastboot reboot-bootloader to reboot into the bootloader.
11. 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.
12. 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.
*** I also saw this:
"For new users who have only unlocked their bootloaders, flashed TWRP and rooted, then only make use of apps like RootExplorer, QuickBoot(reboot), Adfree, Wifi Tether for Root, etc.. that do NOT modify /System, the easiest way to take the OTA is to...
download the SBF/FXZ for your carrier and the Software Version currently on your phone. Do NOT use a lower Software Version, or the SBF/FXZ for another carrier or you will risk bricking your phone!!!
unzip it.
boot the phone into fastbootAP/bootloader mode
use mfastboot to flash the recovery.img to your phone - mfastboot flash recovery recovery.img
immediately reboot into fastbootAP/bootloader - mfastboot reboot-bootloader
select recovery.
once you've entered stock recovery, you can reboot back into normal system.
take the OTA when it gets to your phone.
you will likely remain rooted, and its optional to flash your custom recovery back on there via mFastboot
However, if you are running Xposed, did a wifi tethering hack, edited build.prop, DELETED bloat from your phone, your phone will fail the OTA Update's validation checks and it will fail. In that case, you can boot back into fasbootAP/Bootloader mode, use mfastboot to flash system.img (mfastboot flash system.img ) from the SBF/FXZ you already downloaded and unzipped. then reboot ( mfastboot reboot ), and try the OTA again. You will need to re-root by flashing custom recovery (like twrp), and re-install SuperSU."
***Is there any way to break down the whole thing into simpler steps???*** THANKS!!!
Click to expand...
Click to collapse
Were you able to break this down into simpler steps? Did the steps work for you?
Dear all,
I'm new to xda and to ROM tweaking and changing, but I am a developer and I know Linux very well.
I'm trying to restore the factory 4.4.4 ROM on my XT1068 because I can't live with Lollipop even if I tried for weeks.
The factory images are posted in this thread http://forum.xda-developers.com/mot...riginal-motorola-firmware-collection-t3153533 and I followed the instructions there and other instructions as well with no success so far.
What I tried, after rooting the phone and unlocking the bootloader has been:
- flashing according to http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657 using fastboot commandline from my laptop
- trying to install with TWRP
Attempts with fastboot commands were a total failure and only lead me to bricking the system multiple times. Apparently the signature is not accepted so some of the fastboot flash steps miserably fail and brick the system.
Attempts with TWRP to install or wipe and install (also disabling the signature check otherwise it gets stopped by that) bring nowhere, with TWRP just telling that there was an error flashing right after checking the md5sum. By the way: there was no md5sum on the files in the original thread, so I created my own one (with the risk of having wrong md5 if the download was corrupted).
After hours spent on this the only thing I think I figured out is that lollipop bootloader is a nightmare and prevents me from installing 4.4.4. I can't figure out how you guys managed to install without complaints the 4.4.4 images. BTW: the 5.0 image I had on the smartphone was the RETGB one and it was bought over amazon, originally shipped with 4.4.4
P.S: the error I get with fastboot is: preflash verification failed
must have unlocked bootloader via motorla page and try my 4.4.4 easy installer http://forum.xda-developers.com/moto-g-2014/general/windows-tool-moto-g-2014-xt1068-dual-t2983295- read the README for instructions -firmware d in list for GB from amazon UK
leonardo186 said:
Admin Note: This is a special Q&A-formatted thread. Please follow this link to view it in your browser: http://xda.tv/post61937805[/QUOTE
Click to expand...
Click to collapse
My friend, if you wanna upgrade your Android OS, please do it NOT(!!!), then flash a Factory Image from XDA on your phone.
It results in a hard brick if you upgrade via OTA.