Related
I have a us cellular version Moto X. I unlocked bootloader using motorola website and flashed clockwork mod and SU. When a future OTA comes up do I just accept it, or do i need to do something special.
It won't install if you have a custom recovery. Just wait till someone comes out with a flashable version.
Sent from my XT1058 using XDA Premium 4 mobile app
charlie-n said:
I have a us cellular version Moto X. I unlocked bootloader using motorola website and flashed clockwork mod and SU. When a future OTA comes up do I just accept it, or do i need to do something special.
Click to expand...
Click to collapse
On my Nexus 7 you could create a backup right after unlocking the bootloader and flashing recovery, but before rooting. When the OTA is available, flash back to that backup, then take the OTA. It would flash in TWRP, after flashing it would ask you if you wanted to remove the recovery.sh file......or you could manually remove it via TWRP by mounting system, and removing the file. That file re-flashes stock recovery on boot. You could then reboot, go to play and download SuperSU, then root. Seemed to work pretty well. I am setup and ready to try it that way.
I just ordered a new Moto X Developer Edition VZN
Can I get native tethering? I know I can probably use FoxFi, but wondered if there is a way that I can use native and if I need to root to do it?
If you've installed Xposed framework (which you definitely should) there's a module called Moto Tether. Been using it for a while, it uses native tethering.
gencode said:
I just ordered a new Moto X Developer Edition VZN
Can I get native tethering? I know I can probably use FoxFi, but wondered if there is a way that I can use native and if I need to root to do it?
Click to expand...
Click to collapse
this is a xposed app that will help you
http://forum.xda-developers.com/showthread.php?t=2601859
and this is a mod you can do but alot more difficult
http://forum.xda-developers.com/showthread.php?t=2536166
enjoy
gencode said:
I just ordered a new Moto X Developer Edition VZN
Can I get native tethering? I know I can probably use FoxFi, but wondered if there is a way that I can use native and if I need to root to do it?
Click to expand...
Click to collapse
Kit Kat broke FoxFi Wifi tether but bluetooth and USB tether still work.
I rooted after I unlocked, which was not at all hard to do. Then I tried the adb commands in this link:
Native Tether for VZW DE 4.4
but my PC won't recognize my Moto X when it is in bootloader mode, and so the adb commands don't work for me although I can use fastboot commands. I have a driver problem that I need to debug.
Anyhow, later on in that thread another poster gave instructions that don't require adb commands, and I did that and it works great:
Native Tether for VZW DE 4.4 Using Root Browser
I used the Root Browser by Jrummy in the Play Store to do it.
The popup that the phone is checking for your subscription comes up but it never does the check and just enables the WiFi Tether.
Thanks guys Ill probably try the Exposed one since it looks like the APK one requires root.
Correct me if I'm wrong.
gencode said:
Thanks guys Ill probably try the Exposed one since it looks like the APK one requires root.
Click to expand...
Click to collapse
Correct, it requires root.
That Xposed module has been working flawlessly for me as well
Sent from my Nexus 7 using Tapatalk
YankInDaSouth said:
That Xposed module has been working flawlessly for me as well
Click to expand...
Click to collapse
Does Xposed require root?
Cozume said:
Does Xposed require root?
Click to expand...
Click to collapse
Yes
gencode said:
Thanks guys Ill probably try the Exposed one since it looks like the APK one requires root.
Correct me if I'm wrong.
Click to expand...
Click to collapse
Xposed requires root, too.
Xposed requires root, but rooting the dev edition is simple
Sent from my Nexus 7 using Tapatalk
gencode said:
Thanks guys Ill probably try the Exposed one since it looks like the APK one requires root.
Correct me if I'm wrong.
Click to expand...
Click to collapse
Is root an obstacle for you for some reason? I'm curious because you possess a developer edition yet ask about root as if it's not something you desire.
nhizzat said:
Is root an obstacle for you for some reason?
Click to expand...
Click to collapse
seriously, it was so easy. But not everyone realizes that.
nhizzat said:
Is root an obstacle for you for some reason? I'm curious because you possess a developer edition yet ask about root as if it's not something you desire.
Click to expand...
Click to collapse
Nope not at all, my GS3 is rooted, just wondered.
Thanks again, now just gotta wait for it to ship out, took advantage of this sale going on with the MotoX.
nhizzat said:
Is root an obstacle for you for some reason? I'm curious because you possess a developer edition yet ask about root as if it's not something you desire.
Click to expand...
Click to collapse
Cozume said:
seriously, it was so easy. But not everyone realizes that.
Click to expand...
Click to collapse
I saw this link
http://forum.xda-developers.com/showthread.php?p=45598679
Is there an easer one? Im getting the developer edition.
gencode said:
I saw this link
http://forum.xda-developers.com/showthread.php?p=45598679
Is there an easer one? Im getting the developer edition.
Click to expand...
Click to collapse
yes there is an easier method if you get the developer edition and unlock the bootloader.
To root the developer edition:
1) Get the unlock code from Motorola and unlock the bootloader by following the directions in this link, including downloading the Android SDK and installing Motorola Device Manager:
Unlock Moto X Bootloader
2) Get mfastboot.exe here:
mfastboot.exe
and place it in the same directory as fastboot (fastboot is in the \sdk\platform-tools subdirectory of the Android SDK).
3) Get the TWRP custom recovery for kit kat here:
TWRP for Moto X 4.4
and place it in the same directory as fastboot.
4) On your unlocked Moto X, enable USB debugging and download SuperSU here:
SuperSU 1.93
5) Double check to make sure USB debugging has been enabled! Put your unlocked Moto X into bootloader mode by pressing the volume down key and then the power key. Hold for about 3 seconds and release and you should be in bootloader mode. Connect your Moto X to your PC via a USB cable.
6) Open a command prompt on your PC and change directory to the folder where mfastboot.exe is.
7) At the command prompt type:
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
to flash the custom recovery to your Moto X.
8) After the custom recovery has been flashed to your Moto X, at the command prompt type:
fastboot reboot-bootloader
to reboot into the bootloader (I am not sure if this step is necessary but I read somewhere it was necessary and I did it and it worked).
9) Then get into recovery mode by pressing the Volume Down button to highlight recovery mode and pressing the Volume Up button to select the recovery mode.
10) You should now have booted into the Team Win Recovery Project custom recovery. Click on Install to install SuperSu. Scroll down to find the sdcard and select it. Then scroll down to download and select it. Select the SuperSU zip file and swipe to install.
If you want to check to see if you successfully rooted, you can download Root Checker Basic from the playstore and it will tell you if you are rooted.
Remember, to take an OTA, you have to revert back to stock recovery!
Thanks man, x100
Now I'm ready, just waiting for the FedX guy to get here
gencode said:
Thanks man, x100
Now I'm ready, just waiting for the FedX guy to get here
Click to expand...
Click to collapse
My friend just got a Verizon DE and it shipped with 4.2.2. If you are on 4.2.2, you need to update it to 4.4 before you root with that version of TWRP I linked to. That version of TWRP I linked to is for 4.4 only. Verizon should push the 4.4 update to you pretty soon after turning your phone on.
They haven't even started the soak test on Verizon yet for 4.4.2. so don't worry about that now. But once they do start to push it to us, you have to revert back to stock recovery before you take the 4.4.2 OTA. And then I think we have to wait to root until someone updates the TWRP to be compatible with 4.4.2.
Here is the link on this if you need more info:
Unlocked Recovery for Moto X on Android 4.4
ETA - on another thread another poster said the same version of TWRP that I linked to above works for 4.4.2
http://forum.xda-developers.com/showthread.php?t=2646361
Cozume said:
My friend just got a Verizon DE and it shipped with 4.2.2. If you are on 4.2.2, you need to update it to 4.4 before you root with that version of TWRP I linked to. That version of TWRP I linked to is for 4.4 only. Verizon should push the 4.4 update to you pretty soon after turning your phone on.
They haven't even started the soak test on Verizon yet for 4.4.2. so don't worry about that now. But once they do start to push it to us, you have to revert back to stock recovery before you take the 4.4.2 OTA. And then I think we have to wait to root until someone updates the TWRP to be compatible with 4.4.2.
Here is the link on this if you need more info:
Unlocked Recovery for Moto X on Android 4.4
ETA - on another thread another poster said the same version of TWRP that I linked to above works for 4.4.2
http://forum.xda-developers.com/showthread.php?t=2646361
Click to expand...
Click to collapse
Updated to 4.4, unlocked boot loader steps waiting for email from Motorola. Wondering, if all I want to do is root and I don't want to put a custom ROM in do I need a custom recovery? Or is that just part of the necessary step to get the SU on.
Thanks, Ed,
gencode said:
Updated to 4.4, unlocked boot loader steps waiting for email from Motorola. Wondering, if all I want to do is root and I don't want to put a custom ROM in do I need a custom recovery? Or is that just part of the necessary step to get the SU on.
Click to expand...
Click to collapse
As I understand it, you can root without installing a custom recovery, but you do have to boot into a custom recovery to install SU.
See this thread for instructions:
http://forum.xda-developers.com/showthread.php?t=2439536
I am not sure of the benefits of actually installing the custom recovery other than ROMing, but there may be other benefits that I don't know about.
After installing TWRP and SuperSU (not sure if they are relevant, but I'd figure I'd include all the steps), I notice that my phone has a firmware update. Now, first of all, I thought dev phones don't get updates? Also, if this is a legitimate update, how can I pull the ota to post?
Also, I'm already on 4.4, so could this be 4.4.2?
There's a bunch of ota threads my friend. Read up. Some are stickies...like the complete Moto x guide thread.
Sent from my Moto X cellular telephone...
SwiftLeeO said:
After installing TWRP and SuperSU (not sure if they are relevant, but I'd figure I'd include all the steps), I notice that my phone has a firmware update. Now, first of all, I thought dev phones don't get updates? Also, if this is a legitimate update, how can I pull the ota to post?
Also, I'm already on 4.4, so could this be 4.4.2?
Click to expand...
Click to collapse
If you downloaded the update it's in the cache folder.
Ryno77 said:
If you downloaded the update it's in the cache folder.
Click to expand...
Click to collapse
Well, it just says install. I don't want to install it because I'm rooted with custom recovery and it might brick my phone. I checked the cache folder and there are 3 folders: backup, lost+found, and recovery
SwiftLeeO said:
After installing TWRP and SuperSU (not sure if they are relevant, but I'd figure I'd include all the steps), I notice that my phone has a firmware update. Now, first of all, I thought dev phones don't get updates? Also, if this is a legitimate update, how can I pull the ota to post?
Also, I'm already on 4.4, so could this be 4.4.2?
Click to expand...
Click to collapse
Developer Editions get OTAs the same as any other Moto X. But that is odd as there have been no reports of the soak test even being started for the Verizon Moto X. Sounds like the OTA got pushed to you by mistake.
Anyhow, what is clear is that you can't take an OTA when you are rooted but you already know that.
What root explorer/browser are you using?
Cozume said:
Developer Editions get OTAs the same as any other Moto X. But that is odd as there have been no reports of the soak test even being started for the Verizon Moto X. Sounds like the OTA got pushed to you by mistake.
Anyhow, what is clear is that you can't take an OTA when you are rooted.
What root explorer/browser are you using?
Click to expand...
Click to collapse
Root Browser by JRummy. I normally use ES, but i stopped after it wouldnt let me edit permissions.
Its just a glitch. In your cache it'd have its own folder named after the current os. Wipe cache and dalvic and you should be free of the glitch.
SwiftLeeO said:
Root Browser by JRummy. I normally use ES, but i stopped after it wouldnt let me edit permissions.
Click to expand...
Click to collapse
that is what I am using and I see the exact same subfolders you are seeing in the cache. I take it you don't see the OTA file in any of the subfolders?
Cozume said:
that is what I am using and I see the exact same subfolders you are seeing in the cache. I take it you don't see the OTA file in any of the subfolders?
Click to expand...
Click to collapse
No ota file. Might be a glitch as shane suggested.
False alarm. Went into Software Update to check and I'm up-to-date .-.
Cozume said:
Developer Editions get OTAs the same as any other Moto X. But that is odd as there have been no reports of the soak test even being started for the Verizon Moto X. Sounds like the OTA got pushed to you by mistake.
Anyhow, what is clear is that you can't take an OTA when you are rooted but you already know that.
What root explorer/browser are you using?
Click to expand...
Click to collapse
If you are rooted and want to take the OTA, you can flash the stock recovery and the system.img file with mfastboot.exe, and the OTA should install. i.e. if you are on 4.2.2, rooted with a custom recovery, then you should download the factory 4.2.2 image FOR YOUR DEVICE. Then extract it and use mfastboot to flash recovery.img and system. img. When you reboot, the phone will download the 4.4 OTA and it should install no problem. After it installs, just use mfastboot to flash TWRP and let TWRP root your device and you should be good as new with 4.4.
The stock recovery and an unaltered system folder are the key ingredients to a successful upgrade.
Mr. Orange 645 said:
You can absolutely take an OTA while rooted. The only thing that would prevent you from taking an OTA is if you have altered any system files (such as deleting system apps), or if you have messed and around and flashed a bootloader that doesn't match.
If you flash the factory recovery, you can take the OTA no problem even if rooted. You will of course lose root, but that's easily solved with an unlocked bootloader.
Click to expand...
Click to collapse
Ok, this is the kind of stuff that makes it so hard on noobs. On the thread about the OTA it says you have to get rid of root:
[NOOBS][WARNING][OTA]how to accept an ota
I know if the Moto X were a Nexus you could take the OTA while rooted but would lose root. But with the Moto X, it seems like you can't do that.
Cozume said:
Ok, this is the kind of stuff that makes it so hard on noobs. On the thread about the OTA it says you have to get rid of root:
[NOOBS][WARNING][OTA]how to accept an ota
I know if the Moto X were a Nexus you could take the OTA while rooted but would lose root. But with the Moto X, it seems like you can't do that.
Click to expand...
Click to collapse
Ok, so I just downgraded to 4.2.2, rooted, and tried to take the OTA and it failed. So, I stand corrected. You are right, you can not take the OTA if you are rooted. Well, you CAN take it, but it will fail to install. It sees the su app as an alteration to the system folder (which it is).
Easiest fix is to to use mfastboot to flash the stock recovery and flash the system.img file so it is back to stock. Reboot then let the OTA install and you should be good to go.
Sorry for the misinformation, and I will correct my earlier post so as not to confuse the "noobs." LOL.
Thank you, Cozume
OK ,its simple. 1 moto is no nexus device
2 where does the su binary flash to?xbin folder, is that not part of the system? The only reason why some folks on T-Mobile have root afterwards is, the 4.4.2 is a partial update for them as they received 4.4 , it only replaces some files,If you have a carrier such as Rogers that's going from 4.2.2 directly to 4.4.2 then all the system folders are replaced and you need to remove root along with the binary file, there are other carriers as well that are going from 4.2.2 to 4.4.2 directly
Sent on my Gummy running Lenoto X
flashallthetime said:
OK ,its simple. 1 moto is no nexus device
2 where does the su binary flash to?xbin folder, is that not part of the system? The only reason why some folks on T-Mobile have root afterwards is, the 4.4.2 is a partial update for them as they received 4.4 , it only replaces some files,If you have a carrier such as Rogers that's going from 4.2.2 directly to 4.4.2 then all the system folders are replaced and you need to remove root along with the binary file, there are other carriers as well that are going from 4.2.2 to 4.4.2 directly
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
Yup, sorry for the misinformation. I was mistaken and corrected it. Likely while you were typing up your response.
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
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?