[Q] C-Spire releases Moto X. Any root love? - Moto X Q&A

Hello
Hopefully this isn't a duplicate thread. C-spire released its version of the Moto X this week. I noticed this fact on their website yesterday and picked up what the sales-people claimed to be the first one they have sold in my town.
I have been reading through the root threads and have tried to educate myself with Jcase's work. Unfortunately it seems that his tools (well at least pwnmymoto) are carrier specific and there are no specific c-spire tools.
My Moto X is running Jellybean 4.2.2. I have not accepted any OTA updates (although I guess its possible they pre-installed the camera update before shipping (any way to verify?)). I believe I'll need to use pwnmymoto or rockmymoto as I would be happy with just a rooted jellybean (mainly rooting for tethering). While pwnmymoto has carrier specific downloads, rockmymoto does not. Does this mean that rockmymoto is generic enough to root any moto x regardless of carrier?
Any help is appreciated!
halfspec

A little more info.
Turns out a stock firmware dump has been created for my device:
ghost_acg_lte-user-4.2.2-13.9.0Q2.X-191-TA-3-14-release-keys-cid9.xml.zip
That was found in the ghost rcica list
(Sorry, I'm too much of a newb to post links apparently haha)
It is listed as Cellular South, which is Cspire's old brand, but it matches my build number / system version exactly so I expect it's the correct firmware dump.
Perhaps more has been done root wise than I'm aware of?
halfspec

I guess I should just ask if anyone knows if rockmymoto is compatible with a 4.2.2 cspire / cellular south moto x?
I'd ask in Jcase's thread but I can't because I'm a sub 10 post newb!
Any help would be greatly appreciated!
halfspec

Bump! Still looking for answers. Any help?
Lane

Hoping I can snag me a dev that can answer my questions
Lane

Is the bootloader unlockable?

natezire71 said:
Is the bootloader unlockable?
Click to expand...
Click to collapse
Thank you for replying! I've been feeling like a one man army here!
I'm not 100% sure but previous phones from cspire / cellular south have had locked boot loaders and they will not unlock it with requests
I'm thinking the only way to do it is using one of jcase's methods, but I can't get a solid answer on if all of his tools are carrier specific and/or build on each other or if it's just pwnmymoto that's carrier specific.
Lane

halfspec said:
Thank you for replying! I've been feeling like a one man army here!
I'm not 100% sure but previous phones from cspire / cellular south have had locked boot loaders and they will not unlock it with requests
I'm thinking the only way to do it is using one of jcase's methods, but I can't get a solid answer on if all of his tools are carrier specific and/or build on each other or if it's just pwnmymoto that's carrier specific.
Lane
Click to expand...
Click to collapse
If you're on 4.2.2 (Jelly Bean), then RockMyMoto should work fine for you. I'm assuming you're on Windows... so here: RockMyMoto Windows (NEWB PROOF). Don't use PwnMyMoto. RockMyMoto will work on any form of Android v4.2.2 for the MotoX--use it just to be safe.
Okay, well... Hm. I'm very certain Jcase's SlapMyMoto would work (if you're on KitKat). You just need to use this file instead of the one's he linked: CellularSouth_4.2.2. You'll have to return back to stock using this and you'll need a few files out of this file. Just follow Jcase's instructions and you'll be fine.

natezire71 said:
If you're on 4.2.2 (Jelly Bean), then RockMyMoto should work fine for you. I'm assuming you're on Windows... so here: RockMyMoto Windows (NEWB PROOF). Don't use PwnMyMoto. RockMyMoto will work on any form of Android v4.2.2 for the MotoX--use it just to be safe.
Okay, well... Hm. I'm very certain Jcase's SlapMyMoto would work (if you're on KitKat). You just need to use this file instead of the one's he linked: CellularSouth_4.2.2. You'll have to return back to stock using this and you'll need a few files out of this file. Just follow Jcase's instructions and you'll be fine.
Click to expand...
Click to collapse
Good info. Again, thank you for helping. I do really appreciate it.
I'd like to stick with jellybean 4.2.2 if possible. I've heard that there are still issues with the kit kat Roms and tethering. 99% of my reason for rooting is to tether.
I'm not opposed to going with kitkat if I can work out the root issues but I'm not as familiar with the process. For one, cspire hadn't released the 4.4 ota update so I don't know if there's a ROM out there that would work with my network. Just a little info about cspire, they are historically a CDMA service like Verizon. I don't know if that's an issue with 4g / LTE (I noticed cspire is using Sim cards and they never have before) but I'm still wary. If anyone has info that helps clarify a safe upgrade path to kitkat for a cspire phone + a tethering solution i'd LOVE to hear it. Otherwise I'd like a little more reassurance that rockmymoto is a viable solution for my jellybean phone
Thanks again for any help
Lane

halfspec said:
Good info. Again, thank you for helping. I do really appreciate it.
I'd like to stick with jellybean 4.2.2 if possible. I've heard that there are still issues with the kit kat Roms and tethering. 99% of my reason for rooting is to tether.
I'm not opposed to going with kitkat if I can work out the root issues but I'm not as familiar with the process. For one, cspire hadn't released the 4.4 ota update so I don't know if there's a ROM out there that would work with my network. Just a little info about cspire, they are historically a CDMA service like Verizon. I don't know if that's an issue with 4g / LTE (I noticed cspire is using Sim cards and they never have before) but I'm still wary. If anyone has info that helps clarify a safe upgrade path to kitkat for a cspire phone + a tethering solution i'd LOVE to hear it. Otherwise I'd like a little more reassurance that rockmymoto is a viable solution for my jellybean phone
Thanks again for any help
Lane
Click to expand...
Click to collapse
The safe upgrade path to Kitkat is how Jcase gives the instructions to root. It's going to work for your phone. I'm not up to speed on the tethering issues, however, if it's a major issue for you, just wait on 4.2.2. Otherwise, I'd go ahead and get on KitKat. You'll have to factory reset your phone--so, it would suck to have to work on setting everything back up again if you didn't have to.

natezire71 said:
The safe upgrade path to Kitkat is how Jcase gives the instructions to root. It's going to work for your phone. I'm not up to speed on the tethering issues, however, if it's a major issue for you, just wait on 4.2.2. Otherwise, I'd go ahead and get on KitKat. You'll have to factory reset your phone--so, it would suck to have to work on setting everything back up again if you didn't have to.
Click to expand...
Click to collapse
Thank you for clearing up the kitkat questions. I guess I'll start reading up on tethering solutions for kitkat Roms.
In the meantime, if anyone runs across this thread that knows rockmymoto will work on a 4.2.2 cspire motox, please let me know.
Lane

halfspec said:
Thank you for clearing up the kitkat questions. I guess I'll start reading up on tethering solutions for kitkat Roms.
In the meantime, if anyone runs across this thread that knows rockmymoto will work on a 4.2.2 cspire motox, please let me know.
Lane
Click to expand...
Click to collapse
Just try the RockMyMoto. It WILL work; if it doesn't, then something won't work and that will be it. It's not going to brick your phone or anything. Hold me to it.

natezire71 said:
Just try the RockMyMoto. It WILL work; if it doesn't, then something won't work and that will be it. It's not going to brick your phone or anything. Hold me to it.
Click to expand...
Click to collapse
You were right. I finally grew a pair and tried RockMyMoto. Worked like a champ. I can now confirm that RockMyMoto will work for C-Spire / Cellular South MotoX phones running 4.2.2 jellybean.
Thanks
halfspec

Is tethering solved?
halfspec said:
You were right. I finally grew a pair and tried RockMyMoto. Worked like a champ. I can now confirm that RockMyMoto will work for C-Spire / Cellular South MotoX phones running 4.2.2 jellybean.
Thanks
halfspec
Click to expand...
Click to collapse
I am scared to take the plunge with another c spire phone/contract. I want to be assured I can still tether.

Related

[Q] Can I update? Confused by so many unclear posts.

Background information:
Bought the AT&T version when it came out right away
Got root the first time it was released
Updated root when next update came out ( Didn't know if I need to )
OTA has been Frozen since I got the phone
Is it safe for me? Should I go back to the first version and then update?
Trust me I've read the posts and since I know there have been some issues on the Verizon side I wasn't sure if that was something that was effecting AT&T too. If some one could please give me an explain of that to it would be extremely helpful as I like to know my **** so I can help others.
Thanks
Icon000 said:
Background information:
Bought the AT&T version when it came out right away
Got root the first time it was released
Updated root when next update came out ( Didn't know if I need to )
OTA has been Frozen since I got the phone
Is it safe for me? Should I go back to the first version and then update?
Trust me I've read the posts and since I know there have been some issues on the Verizon side I wasn't sure if that was something that was effecting AT&T too. If some one could please give me an explain of that to it would be extremely helpful as I like to know my **** so I can help others.
Thanks
Click to expand...
Click to collapse
Flash back to stock via RSDLite. Let it boot up. Get your gmail setup.
When the prompt comes up, DL the .54 update. Install.
Root with jcase's new root method.
Or you could just install safestrap. Install a ROM with the camera update and not worry about it until kitkat comes around.
Sent from non rooted motoX :'(
I'm not really interested in updating to another Rom unless it has the touchless controls or something really interesting. Touchless Controls is one of the main reasons I got this phone next to battery life.
Is Safestrap finally settled down? I feel like last time I check there were still messages about bugs and other issues?
matt99017d said:
Flash back to stock via RSDLite. Let it boot up. Get your gmail setup.
When the prompt comes up, DL the .54 update. Install.
Root with jcase's new root method.
Or you could just install safestrap. Install a ROM with the camera update and not worry about it until kitkat comes around.
Sent from non rooted motoX :'(
Click to expand...
Click to collapse
Icon000 said:
I'm not really interested in updating to another Rom unless it has the touchless controls or something really interesting. Touchless Controls is one of the main reasons I got this phone next to battery life.
Is Safestrap finally settled down? I feel like last time I check there were still messages about bugs and other issues?
Click to expand...
Click to collapse
the only rom out for SS that i am aware of is just a ported tmobile rom for vzw phones that has the update built in. Basically it is just the OTA stock rom running on SS. This is what I am using currently. Not sure if it flashable for ATT phones, but I'm sure there is some workaround there. Or maybe the OP on that thread can make a ATT one if you asked him. SS is stable as of now. Haven't had any new updates to it because no one is having any problems currently (at least with moto x devices).
For your question pertaining to options for taking the OTA. There are 4 methods now.
1. SS method described above
2. use the thread called something like "keep root through the OTA." It basically takes the ota without updating the BL so you can still downgrade to your stock original FW that you are on now. It's the same thing as the SS method because SS also does not udpate the BL, but you won't be using SS for this method obviously.
3. you can flash recovery.img (and system.img if you need to) or just RSD, then install pwnmymoto without running it, then take the ota and pwnmymoto will root the phone automatically after the ota is taken. you won't be able to downgrade your FW anymore with this method.
4. you can just take the ota (also must flash or use rsd to take it obviously) and then use jcase's rockmymoto root exploit. This uses adb commands and telnet stuff. Not too difficult but if you are unfamiliar with all of that then it will take at least some reading. There is also a thread out there for windows users that simplifies it pretty well.
For future Kit kat root. it is still up in the air what will happen with that. I chose to use SS because it was easy. quick. and allows me to make nandroids. I also like knowing that I can still flash to original stock FW in case that might be necessarry for getting root on kit kat. This seems less likely now that jcase created a root method for the OTA that is out, but I'm still just playing it safe personally, even if it might be pointless now.

Moto X Kit Kat Verizon Root Question

I just got the Moto X for Verizon. I'm either blind or cannot find root instructions. I updated to Kit Kat also. I came from a rooted S4 and used Eclipse as my ROM and the Tether worked great. Tether is key as I use it for work quite often. Any help is greatly appreciated.
Thanks in advance!
igdawgi said:
I just got the Moto X for Verizon. I'm either blind or cannot find root instructions. I updated to Kit Kat also. I came from a rooted S4 and used Eclipse as my ROM and the Tether worked great. Tether is key as I use it for work quite often. Any help is greatly appreciated.
Thanks in advance!
Click to expand...
Click to collapse
Rooting...
Unlock your bootloader, flash TWRP and then flash Supersu. Very simple to root a dev device.
Tether...
http://forum.xda-developers.com/showthread.php?t=2536166
I don't think the OP has a dev device. Must be regular one from VZW website
Go here http://forum.xda-developers.com/showthread.php?t=2538896
FOLLOW the directions. You'll have to go back to 4.2.2 and lose your data, but that's what it takes. It's not that difficult, all the ?'s you may have are probably answered several times in that thread.
This is for the initial rooting of your phone.

A really stupid question...

Why can't those of us who have locked phones just flash the developer's edition OS? By the time I learned of the Developer's edition phone, I had already passed my 14 business days return of my phone. The long root process is a bit much for me... If there is no other way, I'll give it a try though...
I'm not exactly sure how Motorola's bootloader works, but I'm pretty sure the Developer Edition is signed with different keys and will possibly be a different size. Motorola's bootloader I'm sure checks these things and will deny it.
The bootloader is not part of the OS, it's a different thing all on its own.
It really does seem as simple as you said OP but there's been plenty of phones with locked bootloaders, if it was as simple as that, there wouldn't need to be SafeStrap and other bypasses / exploits.
If you haven't looked at JCase's new SlapMyMoto 1.0 root method, it is more simple than the previous versions. It still requires going back to 4.2.2 camera OTA and losing all your data, but some of the ADB/Fastboot steps were removed and simplified, from what I've seen.
OK after a lot of sweat, I was able to get back to 4.2.2. How do I know if I have the camera patch?
jideay said:
OK after a lot of sweat, I was able to get back to 4.2.2. How do I know if I have the camera patch?
Click to expand...
Click to collapse
If you followed the instructions in the root guide and used the proper SBF to get back to 4.2.2, you should have the update. It links directly to the correct SBF for the root process.
http://forum.xda-developers.com/showthread.php?t=2538896
jideay said:
Why can't those of us who have locked phones just flash the developer's edition OS? By the time I learned of the Developer's edition phone, I had already passed my 14 business days return of my phone. The long root process is a bit much for me... If there is no other way, I'll give it a try though...
Click to expand...
Click to collapse
Depending on the model of you phone you can flash the developer edition rom,
XT1060, Verizon Retail, Moto Maker or Developer edition can flash the same Developer Edition recovery images direct from Moto's web site.
XT1053, GSM Developer or T-Mobile USA can use the GSM Developer recovery images direct from Moto's web site.
BUT this won't impact your ability to unlock your phone's bootloader.
(If you don't believe me that the rom is the same, Do a FC /B of all files contained inside the developer edition recovery images requested from Moto's web site with those inside the roms/images downloaded from http://sbf.droid-developers.org/phone.php?device=0 and you will see other than the XML, all files are identical. And the XML just tells RSDLite what to flash. Also when you request the GSM Developer Edition recovery files, you get a file named.. TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_1FF.xml.zip )
Well, after a day and half of sweating, and a few hours there where I thought I bricked it, it's rooted on 4.4. I have rooted every android phone I've ever had, and this was by far the hardest... But i'm really happy with it. Got the wifi tether going and life is good. Thanks everyone for your replies...
jideay said:
Well, after a day and half of sweating, and a few hours there where I thought I bricked it, it's rooted on 4.4. I have rooted every android phone I've ever had, and this was by far the hardest... But i'm really happy with it. Got the wifi tether going and life is good. Thanks everyone for your replies...
Click to expand...
Click to collapse
This was surely the most involved root I've done. I think it's partially because I got this phone much close to launch than my previous devices. They all had one click root methods available by the time I tried.
fury683 said:
This was surely the most involved root I've done. I think it's partially because I got this phone much close to launch than my previous devices. They all had one click root methods available by the time I tried.
Click to expand...
Click to collapse
True the X hasn't been out long, and to complicate that more, 3 roms have been there for it... release, first OTA with camera fix, and Kit Kat...
Combine that with newer phones being harder to root... and yeah, one click root method isn't a reality at this point.

Receiving Moto X DE (GSM) soon, should I stay with JB?

Does new phone come with JB? If so should I stay with it and not to accept OTA?
It seems that Kitkat update introduced several issues (problem with email syncing, bluetooth incompatibility wit some cars, etc). Is there anything else? I am fine with not having the latest and greatest.
Also: is it possible to downgrade Moto X DE (GSM) back to JB? I am not 100% sure from reading this forum.
The kit Kat update had issues but nothing on the scale of the Samsung galaxy family's 4.3 update. I haven't noticed any issue on mine nor any on customers. Totally worth upgrading it.
Sent from my Lumia 928
The only issue I am having with mine is that while it says its connected to web (either lte or wifi) it won't actually connect. A reboot fixes the issue until it comes back.
texanman said:
The only issue I am having with mine is that while it says its connected to web (either lte or wifi) it won't actually connect. A reboot fixes the issue until it comes back.
Click to expand...
Click to collapse
Did you have this issue while on JB?
Dont know as mine came with 4.4 which did not have this weird issue. It may be something I installed so a wipe may be in order.
Go to KK, no question
tapped out via XT1053 DE
The only issue I had was Google maps not showing my direct location with high accuracy on. It was hard for me to distinguish if I needed to go right or left then it has a hard time rerouting. Which pissed my wife off lol.
MOTO X Slapped
It will come with KitKat, and good luck not bricking the phone trying to downgrade it.
sent via tapatalk
Don't forget text reflow has been deprecated. Major loss in browsers and reading apps.
Sent from my XT1053 using HoFo mobile app.
---------- Post added at 07:45 AM ---------- Previous post was at 07:36 AM ----------
@rbiter said:
Don't forget text reflow has been deprecated. Major loss in browsers and reading apps. Blink is in web view. Also means invert lost.
Sent from my XT1053 using HoFo mobile app.
Click to expand...
Click to collapse
Sent from my XT1053 using HoFo mobile app.
eksasol said:
It will come with KitKat, and good luck not bricking the phone trying to downgrade it.
sent via tapatalk
Click to expand...
Click to collapse
Mine arrived with 4.2.2 installed, (2 weeks ago) and it took two updates to get to 4.4, 1'st 4.2.2 then 4.4. No regrets on the update for me, but then again I let the updates fly when I turned on the phone.
eksasol said:
It will come with KitKat, and good luck not bricking the phone trying to downgrade it.
sent via tapatalk
Click to expand...
Click to collapse
Just got my vzw DE wednesday, 2/12/2014. Came with 4.2.2 pre-camera update. soon as it booted it took the 4.2.2 camera update, then shortly after that came 4.4. did all the updates then unlocked the bootloader, installed twrp and rooted. happy as a clam!
Teksu said:
Just got my vzw DE wednesday, 2/12/2014. Came with 4.2.2 pre-camera update. soon as it booted it took the 4.2.2 camera update, then shortly after that came 4.4. did all the updates then unlocked the bootloader, installed twrp and rooted. happy as a clam!
Click to expand...
Click to collapse
let me make this blunt before you even get your phone
your phone is a DE so you can root any version
is you come with 4.2.2 camera update or 4.4 you can upgrade and downgrade between thouse two versions only
if your phone comes with 4.4.2 you can not downgrade at all so just root it and enjoy because most people are trying to get there and bricking there phones half the time.
if you have any other question please post or PM me
dray_jr said:
let me make this blunt before you even get your phone
your phone is a DE so you can root any version
is you come with 4.2.2 camera update or 4.4 you can upgrade and downgrade between thouse two versions only
if your phone comes with 4.4.2 you can not downgrade at all so just root it and enjoy because most people are trying to get there and bricking there phones half the time.
if you have any other question please post or PM me
Click to expand...
Click to collapse
That makes it very clear. But can you elaborate on why downgrade from 4.4.2 is not possible? I currently use rooted Droid Incredible on Verizon with CM 7.1 and if I am not mistaken I can flash pretty much any previous ROM I want (I really haven't tinkered with it for last couple of years, so I may be wrong).
JoeSchmoe007 said:
That makes it very clear. But can you elaborate on why downgrade from 4.4.2 is not possible? I currently use rooted Droid Incredible on Verizon with CM 7.1 and if I am not mistaken I can flash pretty much any previous ROM I want (I really haven't tinkered with it for last couple of years, so I may be wrong).
Click to expand...
Click to collapse
Moto changed the bootloader in 4.4.2 and they dont allow you to downgrade
Moto X DE - mine coming soon as well - some questions
dray_jr said:
Moto changed the bootloader in 4.4.2 and they dont allow you to downgrade
Click to expand...
Click to collapse
My VZW Moto X DE is on its way to me, and I've spent a bunch of time on the forums yet still have the following questions and hope you can help. My current phone is an original Droid Incredible, which I rooted, mostly for recovery, backups, tethering, and system monitoring. This site was a great resource back when I did that and I greatly appreciated the information.
RE: the Moto X, I've read the steps for unlocking the bootloader and which paths for upgrading/downgrading are safe given the release shipped with the phone. That information was for the standard Moto X. If the DE is unlocked, can I just go straight to rooting the phone? If the OTA updates won't work with root, is it best to accept the latest OTA pushes once my phone is online and then root? I want to be clear about what I've gained by getting the DE edition. Why go back to 4.4.2 if it ships with a later release?
I have no plans in the near future for changing ROM's. I'd just like to initially install what I am using on the Incredible - the clockworkmod recovery app (or current equivalent), titanium backuip, and a good tethering program. I currently use android wifi tether.
Thanks for any help.
dmm108 said:
My VZW Moto X DE is on its way to me, and I've spent a bunch of time on the forums yet still have the following questions and hope you can help. My current phone is an original Droid Incredible, which I rooted, mostly for recovery, backups, tethering, and system monitoring. This site was a great resource back when I did that and I greatly appreciated the information.
RE: the Moto X, I've read the steps for unlocking the bootloader and which paths for upgrading/downgrading are safe given the release shipped with the phone. That information was for the standard Moto X. If the DE is unlocked, can I just go straight to rooting the phone? If the OTA updates won't work with root, is it best to accept the latest OTA pushes once my phone is online and then root? I want to be clear about what I've gained by getting the DE edition.
I have no plans in the near future for changing ROM's. I'd just like to initially install what I am using on the Incredible - the clockworkmod recovery app (or current equivalent), titanium backuip, and a good tethering program. I currently use android wifi tether.
Thanks for any help.
Click to expand...
Click to collapse
I have a dev ed and keep mine the same way you intend... What I've gleaned so far is that the each update includes a new bootloader version that cannot be downgraded, i.e. if you take 4.4.2 you cannot downgrade to 4.4. At this point the VZW version only has 4.4.
As far as getting the phone to how you want it after you take the upgrades the material in the following two links should get you right where you want to be...
Custom recovery...
http://forum.xda-developers.com/showthread.php?t=2424110
Verizon boot animation and tether hack...
http://forum.xda-developers.com/showthread.php?t=2645343
He kind of muddied it up by adding other cleanup tools that I'm not interested in, if you're like me and only want the tether hack you will need to go to the 140.45.5 folder in his link and download xt1060-140.45.5-vzw-removal-s.zip He also has an undo zip that you might want to download and stash away just in case.
This part is speculative and potentially dangerous so take with a grain of salt and correct me if I'm wrong.
My understanding is that the big issue from the downgrade is that there will be a partition table mismatch if one takes an OTA upgrade and the phone will be bricked, though I can find nothing solid on this. Being that I plan on keeping a custom recovery I don't have to worry about accidentally taking an OTA and for some reason prefer to have the ability to downgrade, when 4.4.2 comes out I'm going to try to flash everything but the bootloader and I believe the partition table, (I need to read more and understand more before I speak with authority) to see if I can get away with it.
Also, on a side note, I found that freezing pre installed apps/bloat destroyed the wonderful battery life I was getting so I would suggest you keep your phone stock for a few days to get a feel for how the phone behaves before you begin freezing bloat.
Enjoy your new toy!
edthesped said:
I have a dev ed and keep mine the same way you intend... What I've gleaned so far is that the each update includes a new bootloader version that cannot be downgraded, i.e. if you take 4.4.2 you cannot downgrade to 4.4. At this point the VZW version only has 4.4.
As far as getting the phone to how you want it after you take the upgrades the material in the following two links should get you right where you want to be...
Custom recovery...
http://forum.xda-developers.com/showthread.php?t=2424110
Verizon boot animation and tether hack...
http://forum.xda-developers.com/showthread.php?t=2645343
He kind of muddied it up by adding other cleanup tools that I'm not interested in, if you're like me and only want the tether hack you will need to go to the 140.45.5 folder in his link and download xt1060-140.45.5-vzw-removal-s.zip He also has an undo zip that you might want to download and stash away just in case.
This part is speculative and potentially dangerous so take with a grain of salt and correct me if I'm wrong.
My understanding is that the big issue from the downgrade is that there will be a partition table mismatch if one takes an OTA upgrade and the phone will be bricked, though I can find nothing solid on this. Being that I plan on keeping a custom recovery I don't have to worry about accidentally taking an OTA and for some reason prefer to have the ability to downgrade, when 4.4.2 comes out I'm going to try to flash everything but the bootloader and I believe the partition table, (I need to read more and understand more before I speak with authority) to see if I can get away with it.
Also, on a side note, I found that freezing pre installed apps/bloat destroyed the wonderful battery life I was getting so I would suggest you keep your phone stock for a few days to get a feel for how the phone behaves before you begin freezing bloat.
Enjoy your new toy!
Click to expand...
Click to collapse
Thanks for that information. The last paragrapht seems counter-intuitive. I froze apps on the incredible so that it would reduce battery drain, why would freezing apps increase battery drain?
dmm108 said:
Thanks for that information. The last paragrapht seems counter-intuitive. I froze apps on the incredible so that it would reduce battery drain, why would freezing apps increase battery drain?
Click to expand...
Click to collapse
No idea, but freezing moto apps killed the battery. I haven't figured out what the culprit is yet as I'll be travelling this week and I don't want to jack up the phone while I'm on the road. I suspect another system app was spending effort looking for a missing app. Had I not ran my phone stock for a week I may have assumed that was just the phone as the high battery use was about the same as what I typically got on my S3. However, once I started freezing apps battery life went way down. Battery is good again after defrosting all Moto stuff that I assumed to be garbage. Once I get off the road I'll start freezing apps one at a time to see if I can isolate the culprit.
My thought is if you run it stock for a week you'll have a pretty good feel as to how the phone performs so you'll know whether your tweaks are helping or hurting you.
edthesped said:
Verizon boot animation and tether hack...
http://forum.xda-developers.com/showthread.php?t=2645343
Click to expand...
Click to collapse
Now that I'm looking at a full size computer I see that you are not getting a VZW version, The link above is not good! Sorry
edthesped said:
Now that I'm looking at a full size computer I see that you are not getting a VZW version, The link above is not good! Sorry
Click to expand...
Click to collapse
Yes, I am getting the Verizon DE. (VZW, 1st post).

Is this for real?

I was just Google searching hoping for some good news... And came across this posted yesterday...
http://www.youmobile.org/blogs/entry/Root-Moto-X-KitKat
... Any truth to that? And is it for any carrier, i.e att?
Sent from my XT1058 using Tapatalk
Links to a thread on here.
Yea I saw that, but they are not the same...
Sent from my XT1058 using Tapatalk
They want you to dl this http://www.cydiaimpactor.com/
Anyone know what it is?
Maybe it works for root....but write protection will be enabled. So all root changes will be lost on reboot or power down.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
kj2112 said:
Maybe it works for root....but write protection will be enabled. So all root changes will be lost on reboot or power down.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
Click to expand...
Click to collapse
So here's my "dumb" question? Would apps like Greenify and Ti backup still possibly work since they just need root permissions, where as Xposed and other apps that need a reboot would be basically worthless?
jbaumert said:
So here's my "dumb" question? Would apps like Greenify and Ti backup still possibly work since they just need root permissions, where as Xposed and other apps that need a reboot would be basically worthless?
Click to expand...
Click to collapse
There's other threads where this stuff gets talked about, but im pretty sure for things like that it would probably work. But any actual changes to anything would get reversed.
I've always been unlocked....so I don't have firsthand experience though.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
I'm not too sure about that root method.
Step 11 tells you to downgrade the Bootloader (MOTOBOOT.IMG) and GPT.BIN which is part of the security stuff. Correct me if I'm wrong, but aren't those the main components involved with bricking when trying to downgrade from 4.4.2 to 4.4 and lower?
But again, with a locked bootloader, as @kj2112 said, Write Protection will still be enabled.
KidJoe said:
I'm not too sure about that root method.
Step 11 tells you to downgrade the Bootloader (MOTOBOOT.IMG) and GPT.BIN which is part of the security stuff. Correct me if I'm wrong, but aren't those the main components involved with bricking when trying to downgrade from 4.4.2 to 4.4 and lower?
But again, with a locked bootloader, as @kj2112 said, Write Protection will still be enabled.
Click to expand...
Click to collapse
I've been a bit confused by allusions to rooting without write protection. Everyone says similar stuff to what you guys have said--well, without write protection disabled you'll lose root on reboot. I'd be okay with that, just avoid rebooting my phone and using stuff that requires a reboot to take effect. The only thing I really want root for is to see my partial wakelocks to be able to properly troubleshoot battery issues. I really like the stock Moto X ux. If I could, I'd probably use some Xposed modules too, but all I really really want is to get better insight into my wakelock situation. Elsewhere, though, I read that root is totally impossible on 4.4.2, unless you have an unlocked bootloader (which I obviously don't). So, is it possible to get root, even if it doesn't survive a soft reset?
Jumnhy said:
I've been a bit confused by allusions to rooting without write protection. Everyone says similar stuff to what you guys have said--well, without write protection disabled you'll lose root on reboot. I'd be okay with that, just avoid rebooting my phone and using stuff that requires a reboot to take effect. The only thing I really want root for is to see my partial wakelocks to be able to properly troubleshoot battery issues. I really like the stock Moto X ux. If I could, I'd probably use some Xposed modules too, but all I really really want is to get better insight into my wakelock situation. Elsewhere, though, I read that root is totally impossible on 4.4.2, unless you have an unlocked bootloader (which I obviously don't). So, is it possible to get root, even if it doesn't survive a soft reset?
Click to expand...
Click to collapse
Please see my response to you in the 4.2.2 to 4.4.2 thread.
kj2112 said:
Please see my response to you in the 4.2.2 to 4.4.2 thread.
Click to expand...
Click to collapse
Thanks, didn't realize until afterward it was the same voice in both threads.
Jumnhy said:
I've been a bit confused by allusions to rooting without write protection. Everyone says similar stuff to what you guys have said--well, without write protection disabled you'll lose root on reboot. I'd be okay with that, just avoid rebooting my phone and using stuff that requires a reboot to take effect. The only thing I really want root for is to see my partial wakelocks to be able to properly troubleshoot battery issues. I really like the stock Moto X ux. If I could, I'd probably use some Xposed modules too, but all I really really want is to get better insight into my wakelock situation. Elsewhere, though, I read that root is totally impossible on 4.4.2, unless you have an unlocked bootloader (which I obviously don't). So, is it possible to get root, even if it doesn't survive a soft reset?
Click to expand...
Click to collapse
take a read of -> http://mark.cdmaforums.com/MotoX-LockedRoot.html
Root itself is not lost on reboot, only changes done to the /system folder and other protected places.
But yes, if you already have 4.4.2 on your phone, and can't unlock your bootloader, you won't be able to root.
Jumnhy said:
Thanks, didn't realize until afterward it was the same voice in both threads.
Click to expand...
Click to collapse
Where you found another same threads ?
DANIEL AMBRUSO said:
Where you found another same threads ?
Click to expand...
Click to collapse
It was just kj2112 explaining a similar issue to me. Check it out, but essentially my understanding is that there's no root for 4.4.2 if the phone never had root previously (ie, if you naively took the OTA like me without thnking about implications for root.
---------- Post added at 10:01 PM ---------- Previous post was at 09:56 PM ----------
KidJoe said:
take a read of -> http://mark.cdmaforums.com/MotoX-LockedRoot.html
Root itself is not lost on reboot, only changes done to the /system folder and other protected places.
But yes, if you already have 4.4.2 on your phone, and can't unlock your bootloader, you won't be able to root.
Click to expand...
Click to collapse
Solid, thanks for the concise summary. I'd read jcase's posts a while back about a potential exploit--something about using it in a teaching session at BlackHat? He even says though, that the exploit he has will probably never be useful for the average user insofar as it would be too hard to implement and n00bz like myself would end up bricking our phones. So I'm not holding my breath on that one. Ugh. Sad I missed the window for the Chinese connection. Should have jumped on it.
The Tallest said:
Links to a thread on here.
Click to expand...
Click to collapse
Works with 4.4 and post-camera 4.2.2, but if you take the OTA to 4.-4-.2 it upgrades your bootloader and you lose the ability to turn write protection off ; root is pretty much useless at that point.
I have the Republic Wireless XT1049 and did the upgrade shown here and have 4.4.2 with write protect off.
Do not attempt this if you are already running 4.4.2!!!!!!!!!!!!!!! Your bootloader is already changed and you run a big risk of bricking if you try to downgrade to the 4.2.2 bootloader!!!
http://forum.xda-developers.com/mot...ireless-moto-x-kitkat-4-t2738233/post52348028
As usual, read the instructions carefully.
Then read through the posts! Different rooters had different issues!
AFAIK no one bricked though.
glarepate said:
Works with 4.4 and post-camera 4.2.2, but if you take the OTA to 4.-4-.2 it upgrades your bootloader and you lose the ability to turn write protection off ; root is pretty much useless at that point.
I have the Republic Wireless XT1049 and did the upgrade shown here and have 4.4.2 with write protect off.
Do not attempt this if you are already running 4.4.2!!!!!!!!!!!!!!! Your bootloader is already changed and you run a big risk of bricking if you try to downgrade to the 4.2.2 bootloader!!!
http://forum.xda-developers.com/mot...ireless-moto-x-kitkat-4-t2738233/post52348028
As usual, read the instructions carefully.
Then read through the posts! Different rooters had different issues!
AFAIK no one bricked though.
Click to expand...
Click to collapse
The steps in the thread you link to are how to use use 4.4.2 via Safestrap, which does add a layer of complexity. It is the only option to take 4.4.2 IF you have a locked bootloader and are rooted and write protection disabled. And many do have good luck with it, so it is an option IF your phone is still on 4.4.
If I understand correctly, each safestrap rom is unique for the carrier.. in other words, you can't use the Republic Wireless SS rom if you are on Verizon. You can't use the Verizon SS rom if you are on ATT, etc. (for example, they were waiting on the ATT 4.4.2 SBF to create a SS Rom for the ATT X).
KidJoe said:
The steps in the thread you link to are how to use use 4.4.2 via Safestrap, which does add a layer of complexity. It is the only option to take 4.4.2 IF you have a locked bootloader and are rooted and write protection disabled. And many do have good luck with it, so it is an option IF your phone is still on 4.4.
If I understand correctly, each safestrap rom is unique for the carrier.. in other words, you can't use the Republic Wireless SS rom if you are on Verizon. You can't use the Verizon SS rom if you are on ATT, etc. (for example, they were waiting on the ATT 4.4.2 SBF to create a SS Rom for the ATT X).
Click to expand...
Click to collapse
Yes, if you have already gone to 4.4.2 you are out of luck.
I'm using the T-Mobile SafeStrap Recovery with my RW Moto X. This was done by a Franken-ROM process that uses the 4.4.2 ROM without using the 4.4.2 bootloader and using the SS recovery to flash a zip file with some components of the 4.4.2 ROM and then flashing SuperSU. Whether or not it should be working, it is. Nothing I can, or want to, do about that.
But I am sure you are right that this resultant ROM would not work on phones from other carriers. Versions for other carriers are being developed though. It may simply be a matter of time and interest by motivated individuals until this is available for just about everyone.

Categories

Resources