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?
Related
Hello,
I searched for the answer and didn't find it so... I need to upgrade OS on my phone to the latest OTA.
I have a VZW Dev. ed. MotoX, unlocked, rooted, running TWRP. It is stock, aside from the tethering hack.
Given that I managed to unlock, root and install TWRP, I'm sure I could manage it again, if I have to install a stock recovery again (yuck), but I;m hoping there may be an easier way, perhaps one that involves simply clicking a link on my phone or some such similar. I recall with the GNex, these usually popped up shortly after the OTA became available. Is something similar for the MotoX likely to show up, or is our community just too small?
Is there a 1 click upgrade yet? Is there likely to be one, or do I need to roll up my sleeves with this device and revert to stock, apply OTA, then re-install TWRP and root? What a PITA. What's the easiest way?
Thanks!
vespadaddy said:
Hello,
I searched for the answer and didn't find it so... I need to upgrade OS on my phone to the latest OTA.
I have a VZW Dev. ed. MotoX, unlocked, rooted, running TWRP. It is stock, aside from the tethering hack.
Given that I managed to unlock, root and install TWRP, I'm sure I could manage it again, if I have to install a stock recovery again (yuck), but I;m hoping there may be an easier way, perhaps one that involves simply clicking a link on my phone or some such similar. I recall with the GNex, these usually popped up shortly after the OTA became available. Is something similar for the MotoX likely to show up, or is our community just too small?
Is there a 1 click upgrade yet? Is there likely to be one, or do I need to roll up my sleeves with this device and revert to stock, apply OTA, then re-install TWRP and root? What a PITA. What's the easiest way?
Thanks!
Click to expand...
Click to collapse
use fastboot to flash stock recovery on your phone, undo the tethering hack, and take the OTA.
Since you have a Dev Edition with unlocked bootloader, Root and Write Protection Disable survive. You can leave stock recovery on there, unless you really need the features of TWRP like backup, etc. Then you just have to do any NEW hacks for tethering (for 4.4.2 its different than 4.4). Or you can use wifi tether for root app instead of hacks.
There was talk about repackaging the OTA to be installed via TWRP or CWM, but I don't recall the thread containing an actual zip, and think they were mostly talking about what needs to be done. Since its easy enough with the Dev Edition to update, its likely not worth the work repacking it, since it wont work for those with LOCKED bootloaders.
vespadaddy said:
Hello,
I searched for the answer and didn't find it so... I need to upgrade OS on my phone to the latest OTA.
I have a VZW Dev. ed. MotoX, unlocked, rooted, running TWRP. It is stock, aside from the tethering hack.
Given that I managed to unlock, root and install TWRP, I'm sure I could manage it again, if I have to install a stock recovery again (yuck), but I;m hoping there may be an easier way, perhaps one that involves simply clicking a link on my phone or some such similar. I recall with the GNex, these usually popped up shortly after the OTA became available. Is something similar for the MotoX likely to show up, or is our community just too small?
Is there a 1 click upgrade yet? Is there likely to be one, or do I need to roll up my sleeves with this device and revert to stock, apply OTA, then re-install TWRP and root? What a PITA. What's the easiest way?
Thanks!
Click to expand...
Click to collapse
I pretty much did what was described below and maintained TWRP and root. Note: you must enter TWRP and exit after the update to reinstall SU.
http://forum.xda-developers.com/showpost.php?p=50639372&postcount=25
except I chose not to flash the following...
fastboot flash logo logo.bin
fastboot erase customize
fastboot erase clogo
Whether it makes sense or not my goal is to not "upgrade" my bootloader or GPT until absolutely necessary as they can't be downgraded. The risks associated with doing this are hotly debated so understand what you are getting into if you choose to do this to your phone.
Reverted thether hack.
Recovery tool worked for me on moto x dev. flashed stock recovery. Took ota 442. Flashed twrp. kept root and stuff. no need for a computer.
http://forum.xda-developers.com/showthread.php?t=2334554
Hey all,
Sorry for the extremely basic question, I have just been away from Android and flashing ROMs for so long I forgot some really basic stuff. I have a Verizon developer edition with the bootloader unlocked and am currently on Eclipse 3.1.2. I kept getting a Verizon OTA notification and ignoring it, but the other night I accidentally pressed the update button. Now my device keeps rebooting into TWRP. I am kinda glad because I was putting off updating for way too long. So I have a few options as I understand it.
1) Use fastboot files to update to the latest version (4.4.4). I can't find developer edition SBFs (http://sbf.droid-developers.org/phone.php?device=0), do I just use the standard Verizon version?
2) Restore the stock ROM backup I made with TWRP and just use the Verizon OTA.
Is there a downside to either one? Is either one inherently better?
Thanks in advance guys, my life has been pretty heavy recently and I can't believe I lost this basic knowledge.
I_EAT_BABIES said:
Hey all,
Sorry for the extremely basic question, I have just been away from Android and flashing ROMs for so long I forgot some really basic stuff. I have a Verizon developer edition with the bootloader unlocked and am currently on Eclipse 3.1.2. I kept getting a Verizon OTA notification and ignoring it, but the other night I accidentally pressed the update button. Now my device keeps rebooting into TWRP. I am kinda glad because I was putting off updating for way too long. So I have a few options as I understand it.
1) Use fastboot files to update to the latest version (4.4.4). I can't find developer edition SBFs (http://sbf.droid-developers.org/phone.php?device=0), do I just use the standard Verizon version?
2) Restore the stock ROM backup I made with TWRP and just use the Verizon OTA.
Is there a downside to either one? Is either one inherently better?
Thanks in advance guys, my life has been pretty heavy recently and I can't believe I lost this basic knowledge.
Click to expand...
Click to collapse
There is nothing different about the Dev edition SBF vs. the regular XT1060 SBF. Use the standard Verizon version.
Definitely use Option 1. You are at risk of bricking if you choose option 2.
Normally, I would say just SKIP the command "fastboot erase userdata" (to preserve all of your data and apps), but since you are on a custom ROM, you may have issues. You can try it anyways -- if anything goes wrong, just flash the entire SBF again, INCLUDING the fastboot erase userdata command (which will erase everything) and all well be well.
Make sure you use mfastboot instead of regular fastboot.
samwathegreat said:
There is nothing different about the Dev edition SBF vs. the regular XT1060 SBF. Use the standard Verizon version.
Definitely use Option 1. You are at risk of bricking if you choose option 2.
Normally, I would say just SKIP the command "fastboot erase userdata" (to preserve all of your data and apps), but since you are on a custom ROM, you may have issues. You can try it anyways -- if anything goes wrong, just flash the entire SBF again, INCLUDING the fastboot erase userdata command (which will erase everything) and all well be well.
Make sure you use mfastboot instead of regular fastboot.
Click to expand...
Click to collapse
Thanks man! I was going to use RSD for the SBF files, is that not a good idea?
I_EAT_BABIES said:
Thanks man! I was going to use RSD for the SBF files, is that not a good idea?
Click to expand...
Click to collapse
Perfectly fine...but it will erase everything.
Unless, of course you unzip the SBF, edit the XML file with notepad (or similar) and remove the entire line that says "erase userdata".
samwathegreat said:
Perfectly fine...but it will erase everything.
Unless, of course you unzip the SBF, edit the XML file with notepad (or similar) and remove the entire line that says "erase userdata".
Click to expand...
Click to collapse
Hmm, I think I'll just leave it in there and get a perfectly clean install. Thanks for the help man, I cam back in to my room to restore to my old backup and read your response. You potentially saved me from bricking my advice. Thanks!
I_EAT_BABIES said:
Hmm, I think I'll just leave it in there and get a perfectly clean install. Thanks for the help man, I cam back in to my room to restore to my old backup and read your response. You potentially saved me from bricking my advice. Thanks!
Click to expand...
Click to collapse
You are welcome. A few other thoughts: the potential to brick only comes if either the bootloader or partition table are mismatched. This can happen during a failed OTA install.
In addition to that, even if you DID restore the twrp backup successfully, you still couldn't take the OTA. Remember: STOCK recovery is required to accept any OTAs. It would have continued to boot-loop.
Once you finish with RSD Lite, just use fastboot to flash custom recovery back on. Use the latest version of TWRP, find it here: http://techerrata.com/browse/twrp2/ghost
Just: fastboot flash recovery twrp_file_name.img
Then, IMMEDIATELY afterwards, type: fastboot reboot-bootloader
Next, VOL DOWN to highlight recovery, and VOL UP to boot into it.
If you don't immediately boot into TWRP after flashing it, it won't "stick" (we don't know why...but as long as you do this, it will stick permanently, or until you flash something else to recovery).
As you probably already know, as soon as you go to exit TWRP it will offer to root for you.
Good Luck! Update us to success.
P.S. -- Sent you a PM.
I tried this with the VZW imgs and now I get the unlocked bootloader warning. I don't recall getting that before, thoughts?
I assume it's because the imgs are not developer edition ones.
onepoint said:
I tried this with the VZW imgs and now I get the unlocked bootloader warning. I don't recall getting that before, thoughts?
I assume it's because the imgs are not developer edition ones.
Click to expand...
Click to collapse
The unlocked warning is no big deal I get it on my 4.4.3 GSM Developer Edition.
onepoint said:
I tried this with the VZW imgs and now I get the unlocked bootloader warning. I don't recall getting that before, thoughts?
I assume it's because the imgs are not developer edition ones.
Click to expand...
Click to collapse
Nope, it's not. Likely, you had flashed a new logo.bin that "masked" the unlocked bootloader warning. Once again, the images are no different. Not one single byte different. None.
If you dislike (I like it, personally) the unlocked BL message, simply flash a replacement logo.bin.
See here for details: http://forum.xda-developers.com/moto-x/general/4-4-3-remove-unlocked-bootloader-message-t2548566
I realize that it says it is for 4.4.3, but it should be fully compatible with 4.4.4 as well.
And one more time: EVEN THE DEV EDITION shows the "unlocked bootloader message" when unlocked. Completely normal. Only flashing a replacement logo.bin will prevent it from showing up.
I've searched and found variations on these questions in other posts, but I didn't come across any pertaining quite to my situation, so I wanted advice before I do something wrong and brick my phone.
I have a Sprint Moto X, unlocked & rooted, running 4.2.2 (I think pre-camera update). I'd like to upgrade to stock Sprint Lollipop (when it comes out) & stay unlocked & rooted.
My understanding of the steps that need to be taken:
1. Unroot my device
2. Re-lock my device
3. Flash TWRP and boot to recovery
4. Flash stock Sprint Lollipop
5. Unlock, then re-root device
Is any of this extraneous, or am I leaving anything out? Do I need to upgrade to KitKat before going to Lollipop?
I also have Xposed installed and I have tweaked the PRL on my device ... this shouldn't complicate the upgrade, right?
Relocking is useless, and unless you know what you're doing, flashing stock updates in custom recovery shouldn't be done. You don't necessarily need to unroot either, just make sure all stock system files are still in place.
Sent from my Moto X
imnuts said:
Relocking is useless, and unless you know what you're doing, flashing stock updates in custom recovery shouldn't be done. You don't necessarily need to unroot either, just make sure all stock system files are still in place.
Sent from my Moto X
Click to expand...
Click to collapse
i have a sprint X and if i am going to update this is how i have allways done it with no issues at all.
you can leave your bootloader unlocked that is no a issue. but i always take OTA's and you cant take a OTA with a modded system. so i allways just flash my stock firmware package. that way it removes my custom recovery. Root, and all Xposed changes. Then i take the OTA and just reinstall TWRP, then SuperSU then what ever else you want.
this is the safest way i have found to update, the nice thing about Unlocked Sprint phones is we can easily Root are phones via TWRP and SuperSu.
just my .02 you can do it how ever you like but this is how i am going to do it when the OTA finally comes out if it ever does.
Hey guys does anyone have step-by-step guide on how i can root this phone? I am not able to find a guide for XT1053 (T-Mobile) on 4.4.4. Specifically I want to install a 5.0 rom because I'm tired of waiting for the update. Any help will be appreciated;
stuntman2128 said:
Hey guys does anyone have step-by-step guide on how i can root this phone? I am not able to find a guide for XT1053 (T-Mobile) on 4.4.4. Specifically I want to install a 5.0 rom because I'm tired of waiting for the update. Any help will be appreciated;
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x/general/ref-complete-moto-x-guides-information-t2603358
You'll have to unlock the bootloader. No way around it.
Should I be nervous about unlocking the bootloader?
Didn't my Samsung phone come with it already unlocked?
Should you be nervous? Google the pros and cons then decide for yourself.
No phone nor tablet comes with an unlocked bootloader.
I have an XT1053 and just recently unlocked the bootloader through the Motorola site. I waited until now because my original warranty just expired and knew that unlocking the bootloader would void my warranty. I wanted to unlock the bootloader under 4.4.4 because I didn't know if there would be any problems once Lollipop was offered as an update. The unlock process went very smoothly and took only a few minutes. You probably already know that unlocking wipes your phone, so be prepared to reinstall apps and other files. I have not rooted yet because I'll probably wait to do that after the Lollipop OTA comes around. Even then, I may not root because I'm really pretty happy with the phone as it is. For me, unlocking the bootloader was just of way of preserving the future option to root.
stuntman2128 said:
Hey guys does anyone have step-by-step guide on how i can root this phone? I am not able to find a guide for XT1053 (T-Mobile) on 4.4.4. Specifically I want to install a 5.0 rom because I'm tired of waiting for the update. Any help will be appreciated;
Click to expand...
Click to collapse
Go to YouTube and search for qbking77 channel on how to unlock bootloader moto 2013.. Step by step tutorial with video
Sent from my XT1053 using XDA Premium 4 mobile app
mac1996 said:
Go to YouTube and search for qbking77 channel on how to unlock bootloader moto 2013.. Step by step tutorial with video
Sent from my XT1053 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
unlocking bootloader isn't a problem. I mainly want to know how i can put a custom recovery (prefer CWM because i've had it on previous phone). That way i can straight up install a custom rom that is already rooted without rooting stock. I just really want 5.0 really tired of 4.4.4
stuntman2128 said:
unlocking bootloader isn't a problem. I mainly want to know how i can put a custom recovery (prefer CWM because i've had it on previous phone). That way i can straight up install a custom rom that is already rooted without rooting stock. I just really want 5.0 really tired of 4.4.4
Click to expand...
Click to collapse
Do you have fastboot?
if yes, go to your phone bootloader.
Connect to your computer by USB.
Type the following in cmd. (place your recovery img file in fastboot directory)
fastboot flash recovery (your recovery name).img
Sent from my XT1053 using XDA Free mobile app
Check the sticky threads. There's only a year and halfs worth of information available to you here and all over the rest of the internet.
stuntman2128 said:
unlocking bootloader isn't a problem. I mainly want to know how i can put a custom recovery (prefer CWM because i've had it on previous phone). That way i can straight up install a custom rom that is already rooted without rooting stock. I just really want 5.0 really tired of 4.4.4
Click to expand...
Click to collapse
At any point after unlocking the bootloader... To flash recovery, did you do the following...
Start the phone in Fastboot/Bootloader mode.. then from the PC type...
mfastboot flash recovery YourRecovery.img
mfastboot reboot-bootloader
Follow onscreen directions to use vol down key and highlight recovery, then use vol up to select/enter recovery. Once in recovery you can reboot the phone and proceed with whatever you want.
Failure to reboot-bootloader and entering recovery immediately after flashing recovery (i.e. doing something else first) can result in the recovery not sticking.
4.4.4
a year old post by dray_jr says the following:
4.4 to 4.2.2 Pre Cam will Brick
4.2.2 Post Cam to 4.2.2 Pre Cam will Brick.
4.4.2 to to anything will Brick
4.4 to 4.2.2 Post Cam you are ok
Click to expand...
Click to collapse
can someone explain this to me? I got my phone around august 2014, it came with 4.4.3 and right now I'm on 4.4.4.
If I use the motorola website and follow their bootloader unlock steps am I fine? will I have any brick issues stated from the quote above?
Thread
Nevermind guys, found the perfect thread for 4.4.4 root!
Thread: http://forum.xda-developers.com/moto-x/moto-x-qa/step-step-instructions-unlocking-t2649738
Final question: I don't have to install supersu root if i install CM12 once i get into TWRP recovery am i correct? (since cms come rooted)
Would flashing a JB kernel (and only the kernel) work to root it as described here?: http://forum.xda-developers.com/crossdevice-dev/sony/guide-xperia-kitkat-4-4-4-rooting-t3003520
Completely different phone. What works on one does not always apply to another. If it worked on the Moto X, don't you think someone would've tried and documented it s sometime in the last 18 months?
nhizzat said:
Completely different phone. What works on one does not always apply to another. If it worked on the Moto X, don't you think someone would've tried and documented it s sometime in the last 18 months?
Click to expand...
Click to collapse
Of course its a different phone, but since the Moto X also came with JB stock, I was just wondering whether the same method would work for the ones who are stuck with 4.4.4 and no root.
And no, I don't think that every method has been tried already. the Razr I JB root with a locked BL for example only happened, cause I asked jcase nicely if he could code an app that uses an exploit. So, many times, without asking nothing will happen...
dagoban said:
Of course its a different phone, but since the Moto X also came with JB stock, I was just wondering whether the same method would work for the ones who are stuck with 4.4.4 and no root.
And no, I don't think that every method has been tried already. the Razr I JB root with a locked BL for example only happened, cause I asked jcase nicely if he could code an app that uses an exploit. So, many times, without asking nothing will happen...
Click to expand...
Click to collapse
I don't proclaim to know the ins and outs of all things android, but I do know this.. Just because a phone has android 4.4.4 doesn't mean its the same 4.4.4 with the same exact flaws and vulnerabilities, susceptible to the same exact root processes. Its why an exploit to root one phone, often doesn't work to root another.
In the case of the Moto X with a locked bootloader, JCASE has come out with many processes exploiting vulnerabilities for Android and the Apps on the Moto X to not only root it, but disable its write protection. As new OTA's have patched an exploit, he came out with other ways.
Starting wth 4.4.2, the vulnerability in the bootoader to disable write protection has been patched.
Jcase's Sunshine tool works on the X with 4.4.3 and lower, and only SOME with 4.4.4. It needs temp root first, etc. For whatever reason, we don't have a way to even temp root the 2013 X on 4.4.4 enough to allow Sunshine to do its work. And despite being asked many times, Jcase pretty much said in the Sunshine discussion threads that v3.0 wont have Moto X 4.4.4 support (unless he changed his mind and I missed it). Yet sunshine and its root processes, etc work on other phones (HTC) with 4.4.4.
But back to the thread you link...
On the X, due to its security measures, with a locked bootloader, you can only flash the Moto signed ROM for your phone. Nothing else. Because of this, you can't flash a custom recovery. To flash items, we use mFastboot and RSDLite. They need the img files, or bin files. If we make our own, they wont be signed, so they wont flash to a phone with a locked bootloader. And you can't package them into a flashable ZIP because stock recovery looks for the Moto digital signature (which we don't have and can't fake), and you can't install TWRP/CWM/Philz/etc to flash that way. So if you manage to pull the JB kernel out of the Moto SBF file, you wont be able to flash it.
Due to write protection on the 2013 X, any changes made to /System and a few other places, will be lost at power off/on. In other words, if you do manage to flash it (or push via adb), it wont stick due to write protection.
We've seen people try and manipulate their phone by trying to DOWNGRADE their ROM. Well, this doesn't work either. GPT.BIN (partition table), and Motoboot.img (bootloader, TZ, and a few other things) get in the way. Even on an X with an Unlocked bootloader, you can't downgrade these parts. Enough who attempted this have ended up bricking their phone immediately, or with later taking an OTA. Sure you can try to flash just system.img, and while that has less risk for bricking, people who have tried this were still not able to use the older Root Exploits (that worked if you hadn't upgraded already). People have tried flashing everything but GPT.BIN and MotoBoot.img. Again, it didn't help with rooting. Not to mention with a missmatched system.img or other parts, features on the phone may not always work properly (going Settings -> Security comes to mind), and you are at risk of bricking should you take an OTA update.
Since that process exploits a vulnerability, and its out there (so the vulnerability is in the public), I'm sure if it worked or was possible, JCASE, Beaups, or others would have put something together.
Now, back on topic of the XT1053... it has an Unlockable bootloader. Unlocking the bootloader disables write protection, and allows you to flash non-moto stuff. So unlocking the bootloader, flashing TWRP, reboot bootloader, enter TWRP and root, is quick, easy, effective, and doesn't rely on vulnerabilities on the phone to be exploited so patches/updates haven't got in the way. Plus you don't have to wait for someone to find them and create a repeatable process.
Verizon
Moto X 1st Gen
Android 4.2.2 - Stock rooted
Unlocked Boot loader - not DEV edition though
TWRP 2.7.1.1 recovery
Question:
To upgrade to 5.1 do I just need to revert back to stock boot loader and do an OTA update?
Will the OTA re-lock my boot loader?
After the upgrade to 5.1 do I just reload TWRP recovery and flash SU for root access again?
No the new updates do not relock the bootloader. I suggest you first try out the Lollipop by flashing it through latest version of TWRP. If you think you can live with it than just flash complete stock through rsdlite or manually by fastboot. Reason I say that is because once you take the OTA it will update both bootloader version and the partition tables which means you won't be able to revert back to a lower Android version without the risk of bricking your device.
Sent from my Moto X
bushako said:
No the new updates do not relock the bootloader. I suggest you first try out the Lollipop by flashing it through latest version of TWRP. If you think you can live with it than just flash complete stock through rsdlite or manually by fastboot. Reason I say that is because once you take the OTA it will update both bootloader version and the partition tables which means you won't be able to revert back to a lower Android version without the risk of bricking your device.
Sent from my Moto X
Click to expand...
Click to collapse
I don't want to go back to complete stock, I want to keep bootloader unlocked and root. Is there a stock rooted rom out there I can flash w/ TWRP without having to do OTA or flashing the recovery back to stock?
Yes there is its in the development section. You'll read the thread something like xt1053 stock flash-able. It contains only the kernel and system files so you should be good.
Here http://forum.xda-developers.com/showthread.php?t=3155843
Sent from my Moto X
-RanZ- said:
Verizon
Moto X 1st Gen
Android 4.2.2 - Stock rooted
Unlocked Boot loader - not DEV edition though
TWRP 2.7.1.1 recovery
Question:
To upgrade to 5.1 do I just need to revert back to stock boot loader and do an OTA update?
Will the OTA re-lock my boot loader?
After the upgrade to 5.1 do I just reload TWRP recovery and flash SU for root access again?
Click to expand...
Click to collapse
First off, there is no Verizon 5.1 yet. So any 5.1 you try will be for a different model, and if you flash a full rom, it will have different radios (which don't work for CDMA that Verizon still uses for voice/3g data. If you keep your stock VZW radio files, keep in mind they will be on a different version than the rest of the rom which could cause some inconsistencies and issues. IF you do flash a FULL SBF, you will be stuck with no SAFE way to revert to 4.4.4 due to GPT.BIN/Motoboot.img (for more on this, see the link in my signature), and you'll have to wait for the Verizon 5.1 SBF to get back to Verizon's rom.
Next, to install an OTA update, when it becomes available, you need STOCK RECOVERY on your phone. The OTA also does a pre-flash check/validation of your phone before it flashes, so if anything it looks for is not what it expects, the OTA will fail. Because of that you need to be 100% stock, or very near to it.
Finally, NO, an OTA will not relock your bootloader, nor will flashing an SBF.
For more on taking an OTA, see the link in my signature on OTA Updates..
That being said, if you TRY a 5.1 rom that is out there for another model you best bet is to find one that is a TWRP back up of 5.1 installed on someone's phone, since it only updates system.img and boot.img. It may not work 100% (because part of your phone will still have the 4.4.4 files), but it will give you a taste and you could later revert back to the stock 4.4.4 which you currently have on your phone. IF you flash a FULL SBF, you might be stuck with no way to revert to 4.4.4 due to GPT.BIN/Motoboot.img (for more on this, see the link in my signature)
Hi Bushako, I've Moto X Verizon XT1060 and it's struck in 4.2.2 android. When I try to update using setting, about phone and system update it show there is no update available but the android version on it is 4.2.2
5.1 is available for Verizon Moto X 1st gen now isn't it? I am googling for a detailed process on how to update from 4.2.2 to 5.1 and keeping root but not having any luck finding anything. Is it easy to update from 4.2.2 stock rooted to 5.1? The specs of my phone are the same as the original post:
Verizon
Moto X 1st Gen
Android 4.2.2 - Stock rooted
Unlocked Boot loader - not DEV edition though
TWRP 2.7.1.1 recovery
-RanZ- said:
5.1 is available for Verizon Moto X 1st gen now isn't it? I am googling for a detailed process on how to update from 4.2.2 to 5.1 and keeping root but not having any luck finding anything. Is it easy to update from 4.2.2 stock rooted to 5.1? The specs of my phone are the same as the original post:
Verizon
Moto X 1st Gen
Android 4.2.2 - Stock rooted
Unlocked Boot loader - not DEV edition though
TWRP 2.7.1.1 recovery
Click to expand...
Click to collapse
Aug 1, when I last posted in this thread, Verizon 5.1 wasn't available. It is now.
As for updating and keeping root, there are a few ways to do it. Since you say your Bootloader is unlocked, the best way is flash 5.1 SBF, and use the process of flashing TWRP and SuperSU to root and have Write protection Disabled (see -> http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217 ). If you're bootloader isn't unlocked yet, and if you are on 4.4.2 or lower and have NEVER upgraded to 4.4.4 or 5.1, use Sunshine to unlock the bootloader FIRST
If you're bootloader isn't unlocked, there is only one way to root 5.1, but it doesn't disable write protection, and its risky because it intentionally soft bricks the phone back to the Qualcomm HS-USB QDLoader mode.
KidJoe said:
Aug 1, when I last posted in this thread, Verizon 5.1 wasn't available. It is now.
As for updating and keeping root, there are a few ways to do it. Since you say your Bootloader is unlocked, the best way is flash 5.1 SBF, and use the process of flashing TWRP and SuperSU to root and have Write protection Disabled (see -> http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217 ). If you're bootloader isn't unlocked yet, and if you are on 4.4.2 or lower and have NEVER upgraded to 4.4.4 or 5.1, use Sunshine to unlock the bootloader FIRST
If you're bootloader isn't unlocked, there is only one way to root 5.1, but it doesn't disable write protection, and its risky because it intentionally soft bricks the phone back to the Qualcomm HS-USB QDLoader mode.
Click to expand...
Click to collapse
Bootloader is unlocked, I get the warning every time I restart the phone.
Where can I find the SBF files? Every post I find from a search the links do not work.
Are the SBF files stock or from someone else's phone?
Do I flash the files with my currently installed TWRP?
When I flash the SBF does it remove TWRP so I have to re flash it?
Are there any radio upgrades/do they get done w/ the SBF?
Sorry if these are basic questions, I have not done much phone rooting since my old HTC Incredible.
-RanZ- said:
Bootloader is unlocked, I get the warning every time I restart the phone.
Where can I find the SBF files? Every post I find from a search the links do not work.
Are the SBF files stock or from someone else's phone?
Do I flash the files with my currently installed TWRP?
When I flash the SBF does it remove TWRP so I have to re flash it?
Are there any radio upgrades/do they get done w/ the SBF?
Sorry if these are basic questions, I have not done much phone rooting since my old HTC Incredible.
Click to expand...
Click to collapse
There is a link in my signature to a thread containing the known places that were hosting the SBF/FXZ files. That is the only place I can suggest you look.
SBF/FXZ files I'm taking about are stock, and digitally signed by Motorola. They can be flashed on phones with locked or unlocked bootloaders. NOTE: make sure you get the SBF for your device model and carrier!!
You flash these via Mfastboot or RSDLite. When using these tools you are flashing back to stock. After you get the SBF file, see -> http://forum.xda-developers.com/showpost.php?p=61142892&postcount=2 and read the REQUIREMENTS section, and pick either Option 3, 4 or 5 to actually flash (only use one option. which ever you find the easiest. Do NOT use Option 1 or 2 as they would not apply to your situation). I usually recommend option 5.
Yes, the process of flashing the entire SBF will overwrite TWRP with stock recovery. You'll need to flash it later as part of the rooting process.
Yes there are radio updates in the newer SBF files.
So basically, you flash to stock 5.1 by using the SBF files (following the requirements and ONE of the options in http://forum.xda-developers.com/showpost.php?p=61142892&postcount=2 again,I usually recommend option 5), then root by following http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217
One other tip... Make a back up of your phone BEFORE YOU FLASH. copy all data from the /sdcard area to your PC, make a list of all your apps, etc. And seriously consider erasing your UserData while flashing (wipes the phone clear), or doing a factory reset before you flash.
I only say this because 5.1 seems more stable (and less buggy) if a factory reset is done before/during the upgrade process.
EDIT: The 5.1 SBF file you want for a Verizon XT1060 is GHOST_VERIZON_5.1_LPA23.12-39.7_cid2_CFC.xml.zip and is available from -> http://motofirmware.center/files/category/11-moto-x-1st-generation/
KidJoe said:
There is a link in my signature to a thread containing the known places that were hosting the SBF/FXZ files. That is the only place I can suggest you look.
SBF/FXZ files I'm taking about are stock, and digitally signed by Motorola. They can be flashed on phones with locked or unlocked bootloaders. NOTE: make sure you get the SBF for your device model and carrier!!
You flash these via Mfastboot or RSDLite. When using these tools you are flashing back to stock. After you get the SBF file, see -> http://forum.xda-developers.com/showpost.php?p=61142892&postcount=2 and read the REQUIREMENTS section, and pick either Option 3, 4 or 5 to actually flash (only use one option. which ever you find the easiest. Do NOT use Option 1 or 2 as they would not apply to your situation). I usually recommend option 5.
Yes, the process of flashing the entire SBF will overwrite TWRP with stock recovery. You'll need to flash it later as part of the rooting process.
Yes there are radio updates in the newer SBF files.
So basically, you flash to stock 5.1 by using the SBF files (following the requirements and ONE of the options in http://forum.xda-developers.com/showpost.php?p=61142892&postcount=2 again,I usually recommend option 5), then root by following http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217
One other tip... Make a back up of your phone BEFORE YOU FLASH. copy all data from the /sdcard area to your PC, make a list of all your apps, etc. And seriously consider erasing your UserData while flashing (wipes the phone clear), or doing a factory reset before you flash.
I only say this because 5.1 seems more stable (and less buggy) if a factory reset is done before/during the upgrade process.
EDIT: The 5.1 SBF file you want for a Verizon XT1060 is GHOST_VERIZON_5.1_LPA23.12-39.7_cid2_CFC.xml.zip and is available from -> http://motofirmware.center/files/category/11-moto-x-1st-generation/
Click to expand...
Click to collapse
I will give this a try if I can locate the correct SBF files, your information has helped greatly, Thanks!
nevermind, google fixed me.