Related
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.
Okay, I am just wanting to clear things up for myself with this question. I've seen it similarly asked on other threads, but I have yet to find answer to them.
Currently, I am Stock + camera update + rooted with RockMyMoto. I haven't frozen or uninstalled or otherwise done anything to system apps or files (I disabled a few through Android itself before root, but never touched them since) I do use Permissions Denied; an app that does what it says for any app I chose, however I only use it for non-system apps. My phone is essentially stock, with root (bootloader locked). Thats all I want for whenever I update to 4.4 at the moment. Speaking of which...
I am trying to determine the best way to go about this. Since I havent done much to my phone, I am curious to know if I can just install the OTA (since I've altered no system files, but I know this isn't usually advised) then apply the latest root method done by jcase. Can it be as straight forward as that? Or do I absolutely need to flash back to STOCK stock, apply the camera update, the apply the 4.4 update, THEN use his method?
Trying to find a method that is at least safe. Preferably safe, quick and easy. But I know these methods aren't always quick .
NameLessThugZero said:
Okay, I am just wanting to clear things up for myself with this question. I've seen it similarly asked on other threads, but I have yet to find answer to them.
Currently, I am Stock + camera update + rooted with RockMyMoto. I haven't frozen or uninstalled or otherwise done anything to system apps or files (I disabled a few through Android itself before root, but never touched them since) I do use Permissions Denied; an app that does what it says for any app I chose, however I only use it for non-system apps. My phone is essentially stock, with root (bootloader locked). Thats all I want for whenever I update to 4.4 at the moment. Speaking of which...
I am trying to determine the best way to go about this. Since I havent done much to my phone, I am curious to know if I can just install the OTA (since I've altered no system files, but I know this isn't usually advised) then apply the latest root method done by jcase. Can it be as straight forward as that? Or do I absolutely need to flash back to STOCK stock, apply the camera update, the apply the 4.4 update, THEN use his method?
Trying to find a method that is at least safe. Preferably safe, quick and easy. But I know these methods aren't always quick .
Click to expand...
Click to collapse
Pawnymoto hijacks the stock recovery so you won't be able to install the update, you need to flash the stick recovery at the least
Sent on my Moto X
flashallthetime said:
Pawnymoto hijacks the stock recovery so you won't be able to install the update, you need to flash the stick recovery at the least
Sent on my Moto X
Click to expand...
Click to collapse
What do I need in order to do that, or should I just RSD lite back to a stock Moto X?
NameLessThugZero said:
What do I need in order to do that, or should I just RSD lite back to a stock Moto X?
Click to expand...
Click to collapse
I would say its safer to rsdlite back to 100% stock, that way you know everything is ready to accept the ota and you won't end up in a bootloop
Sent on my Moto X
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).
Hello all,
Hopefully this is not considered a useless post and is deleted! I have previously owned the OG Droid and GNex, both rooted and have run custom ROMs so, I am not a COMPLETE noob, but I'm also not an expert.
In any event, I purchased a Verizon DE phone so I could easily unlock and root. I have yet to even activate it, so it is FRESH! It has come with 4.2.2, 139.10.53-ghost, which seems like the original image. I want to upgrade this ONLY to the point of still being able to run my standard tethering app (which I am not sure which 4.4 upgrade breaks this functionality), and root. I also want to be able to run custom ROMs if desired.
I am also confused by whether or not there is a potential downgrade "bricking" of the device. There are threads out there which seem like it can be done, (see http://forum.xda-developers.com/moto-x/general/ref-how-to-root-4-4-links-guides-t2603358), and many other threads that say that regardless of being a DE, it cannot be downgraded. If someone can clarify this for me, that would be great.
Three other questions at this point. One, the thread referenced above discussed using TWRP or CWM for recovery. I have only used CWM in the past. Are there pros and cons to either one? Seems like most everyone uses TWRP for the Moto X.
Two, are there ROMs for the Moto X that have all of the rooted functionality of 4.4.2, with none of the drawbacks of stock, rooted 4.4.2? Would I be better off using one of those?
Finally, will I be able to prevent OTA notifications if I stay with stock, rooted, and upgrade only to certain point?
Sorry for all the questions, and yes, I have been searching and reading, but I have not found enough clear information to feel comfortable not asking directly.
Thank you all in ADVANCE!
There are currently 4 Moto or Stock ROMs for the Verizon Moto X XT1060
139.10.53 = Initial Shipping 4.2.2
139.15.1 = 4.2.2 w/camera update or 1st OTA
140.45.5 = 4.4 or 2nd OTA
164.55.2 = 4.4.2 or 3rd OTA.
The Developer Edition, once the bootloader is unlocked, can be rooted no matter what Moto ROM is on your phone.
Due to changes in parts that are included with 4.4.2, under certain circumstances when trying to downgrade from 4.4.2 to 4.4 or lower, you could either brick your phone, or set it up to brick in the future when you take an upgrade. So it is suggested you just stick with what is on your phone once you get on 4.4.2. Besides, you wont need to downgrade to gain root once you unlock your bootloader.
If you haven't had 4.4.2 on your phone yet, you are perfectly welcome to upgrade from 4.2.2 to 4.4, then downgrade to 4.2 w/camera update (4.2.2 with camera update is Blur_Version.139.15.1.ghost_verizon.Verizon.en.US aka VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-57-X-1_CFC_1FF.xml). which is pretty much what the "Downgrading the bootloader" section of -> http://forum.xda-developers.com/moto-x/general/ref-how-to-root-4-4-links-guides-t2603358 says.
Why worry about downgrading? Well, Locked bootloader users needed to downgrade to take advantage of an exploit in the older rom to gain root and disable write protection. This is not needed on the Dev Edition once the bootloader is unlocked.
As for custom roms, or 3rd party roms. Once your bootloader is unlocked you can flash them.
As for tethering. If you stick on a Stock Moto ROM, On 4.2.2 I used the Wifi Tether for Root from the Play Store.
For 4.4 and 4.4.2 I Use the wifi_tether_v3_4-experimental1.apk from https://code.google.com/p/android-wifi-tether/
change device profile to galaxy nexus (cdma/lte)
check box: wifi-driver reload
check box: enabled routing fix
If you have troubles, its also suggested to...
check box: wifi-driver reload 2
Doing this, I can set the SSID and WPA key. And it doesn't touch any system files or anything, so it is one less thing to get in the way of taking future OTA updates.
Oh, and the Dev Edition XT1060 and the retail/motomaker XT1060 use the same roms, radios, etc.
To root the dev edition see -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738
KidJoe said:
If you haven't had 4.4.2 on your phone yet, you are perfectly welcome to upgrade from 4.2.2 to 4.4, then downgrade to 4.2 w/camera update (4.2.2 with camera update is Blur_Version.139.15.1.ghost_verizon.Verizon.en.US aka VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-57-X-1_CFC_1FF.xml). which is pretty much what the "Downgrading the bootloader" section of -> http://forum.xda-developers.com/moto-x/general/ref-how-to-root-4-4-links-guides-t2603358 says.
Click to expand...
Click to collapse
Thanks KidJoe! So I gather there would really not be a reason to downgrade a DE device anyway, since you can root it regardless of what stock ROM you are running. And since there are ways to wifi tether on 4.4.2, that is a non-issue.
I am still a bit confused regarding your quote above about the "upgrade from 4.2.2 to 4.4, then downgrade to 4.2 w/camera update..." Do you have to follow that path to get to 4.2 w/camera update, or can you just flash that ROM (139.15.1) once unlocked?
I currently use FoxFi on my GNex (paid for it!) and was hoping to use on Moto X. That's really why I didn't want to upgrade too far. Not sure that it works on it though.
Thanks again!
amajamar said:
I am still a bit confused regarding your quote above about the "upgrade from 4.2.2 to 4.4, then downgrade to 4.2 w/camera update..." Do you have to follow that path to get to 4.2 w/camera update, or can you just flash that ROM (139.15.1) once unlocked?
Click to expand...
Click to collapse
No. Was just saying that if you never had 4.4.2 on your phone, wanted to upgrade to 4.4, and later wanted to go back to 4.2.2 w/camera, you could.
amajamar said:
I currently use FoxFi on my GNex (paid for it!) and was hoping to use on Moto X. That's really why I didn't want to upgrade too far. Not sure that it works on it though.
Thanks again!
Click to expand...
Click to collapse
As far as I know, FoxFi still doesn't work on 4.4.2 on the X even when rooted. I don't recall if it works on 4.4. But I never used it.
If you have a DE there is absolutely no reason to downgrade. Ever. If you want to be able to tether here's the easiest way to do it.
Activate your phone.
Take all the updates.
Go to this site: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Follow those directions to a "T". Once that's done, download Xposed Framework, then download MotoTether.
The only time you'll need to worry about being rooted is if you delete bloatware and go to take the next OTA. You'll either need to reinstall all the apps you deleted manually or go to Motorola and request the factory image to reflash it.
The Tallest said:
If you have a DE there is absolutely no reason to downgrade. Ever. If you want to be able to tether here's the easiest way to do it.
Activate your phone.
Take all the updates.
Go to this site:
Follow those directions to a "T". Once that's done, download Xposed Framework, then download MotoTether.
The only time you'll need to worry about being rooted is if you delete bloatware and go to take the next OTA. You'll either need to reinstall all the apps you deleted manually or go to Motorola and request the factory image to reflash it.
Click to expand...
Click to collapse
So I should take the updates BEFORE unlocking? I was assuming it was the other way around. OK. Regarding "bloatware", if you just "freeze" it, does that prevent future OTAs? If you attempt to take an OTA with those apps either frozen or deleted, will you be risking bricking?
amajamar said:
So I should take the updates BEFORE unlocking? I was assuming it was the other way around. OK. Regarding "bloatware", if you just "freeze" it, does that prevent future OTAs? If you attempt to take an OTA with those apps either frozen or deleted, will you be risking bricking?
Click to expand...
Click to collapse
Rather than retyping.. please see -> http://mark.cdmaforums.com/MotoX-Unlock1.htm
while written due to the 3rd party supplier of bootloader unlock codes, the info applies equally to Dev Edition phones (other than the source of your unlock code)
The Tallest said:
If you have a DE there is absolutely no reason to downgrade. Ever. If you want to be able to tether here's the easiest way to do it.
Activate your phone.
Take all the updates.
Go to this site: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Follow those directions to a "T". Once that's done, download Xposed Framework, then download MotoTether.
The only time you'll need to worry about being rooted is if you delete bloatware and go to take the next OTA. You'll either need to reinstall all the apps you deleted manually or go to Motorola and request the factory image to reflash it.
Click to expand...
Click to collapse
I whole-heartedly agree with everything written in this post. You also have to make sure you are on stock recovery if you want to take an OTA. There are plenty of guides around here about taking an OTA, so just make sure you read some of those before you accept an OTA.
I have a suggestion for the OP:
1 - take all the updates on the phone. This will update the radios, boot loader; recovery, and the main ROM (system).
(The boot loader can not be downgraded, but as mentioned above, there really isn't any reason why you would want to try and downgrade your bootloader because you have a DE device)
2 - unlock the bootloader. you can google the steps in the process. Basically you get the unlock key from Motorola. The toughest part of the process is getting the fastboot and device drivers set up properly on your computer. This step will all of the userdata (pictures, apps etc.)
3 - use Fastboot to flash a custom recovery (I use TWRP ver 2.7). then boot into TWRP recovery w/o rebooting. Note that the volume down button is used in the bootloader to highlight your desired option, then volume up is used to select the option. When you are in TWRP and then exit, I believe it will prompt you to install the superuser binaries, which you will want to do.
At this point you can choose do flash a custom 4.4.2 ROM from the Dev section here (the Krypton rom is very good), or you can run stock w/ root. If you choose stock, I recommend the following steps for wifi and customization:
4 - boot up device normally and set it up. you will have be on the stock 4.4.2 rom with root.
5 - install Xposed from here on XDA.
6 then install the xposed module from the moto x apps section (it may also be available to download from within xposed) that enables wifi tethering. This will allow you to use the built in tethering without subscription issues.
7 - install the GravityBox xposed module (you can download this from within Xposed). This allows many of the customizations that you would normally find only in a custom rom (custom quicksettings, reboot options etc).
8 - install rootcloak module for xposed (download within xposed). This will let you run Isis or other apps that don't like root (it comes preconfigured for many apps).
jasoraso said:
I have a suggestion for the OP:
1 - take all the updates on the phone. This will update the radios, boot loader; recovery, and the main ROM (system).
(The boot loader can not be downgraded, but as mentioned above, there really isn't any reason why you would want to try and downgrade your bootloader because you have a DE device)
2 - unlock the bootloader. you can google the steps in the process. Basically you get the unlock key from Motorola. The toughest part of the process is getting the fastboot and device drivers set up properly on your computer. This step will all of the userdata (pictures, apps etc.)
3 - use Fastboot to flash a custom recovery (I use TWRP ver 2.7). then boot into TWRP recovery w/o rebooting. Note that the volume down button is used in the bootloader to highlight your desired option, then volume up is used to select the option. When you are in TWRP and then exit, I believe it will prompt you to install the superuser binaries, which you will want to do.
At this point you can choose do flash a custom 4.4.2 ROM from the Dev section here (the Krypton rom is very good), or you can run stock w/ root. If you choose stock, I recommend the following steps for wifi and customization:
4 - boot up device normally and set it up. you will have be on the stock 4.4.2 rom with root.
5 - install Xposed from here on XDA.
6 then install the xposed module from the moto x apps section (it may also be available to download from within xposed) that enables wifi tethering. This will allow you to use the built in tethering without subscription issues.
7 - install the GravityBox xposed module (you can download this from within Xposed). This allows many of the customizations that you would normally find only in a custom rom (custom quicksettings, reboot options etc).
8 - install rootcloak module for xposed (download within xposed). This will let you run Isis or other apps that don't like root (it comes preconfigured for many apps).
Click to expand...
Click to collapse
After reading the link Kidjoe supplied earlier (That was a FANTASTIC, MUST READ reference for noobs who want to understand the complexities of the Moto X), I may stay off KitKat, as I am not a fan of the white icons in the notification bar, however I do think this is the route (root??) I will take.
I recently upgraded my phone to an AT&T S5 (I decided I didn't like the S6 specs). Currently, the phone is 100% stock, unrooted. I know that previous Samsung phones had problems with OTA updates when they were rooted. Now, with the possibility that the Lollipop OTA is coming soon, I'm hesitant to root until the OTA comes out. Here are my questions:
1. Should I wait to root until after the OTA hits the streets, or is there a strategy to root and still safely apply the OTA?
2. I don't want to be one of the first to get the OTA since it may be buggy. Is there a way to delay the OTA if I'm not rooted?
So, nobody has any thoughts about this?
I can't tell you what you should do but I can tell you what I would do. I would root now, load Titanium backup, and wait for 5.0 to come out. With TBU I freeze the OTA so it's not pushed without my permission. Additionally TBU will backup everything going forward so I can easily move up and restore my apps.
I believe the current process to root will work so be patient.
woody1 said:
So, nobody has any thoughts about this?
Click to expand...
Click to collapse
I wouldn't even take the OTA. Lots of issues with it. I am pretty sure LP will be the same.
I rooted mine, installed SafeStrap, and installed the XDK ROM, which eliminates all updates. My phone works great, does everything I want it to. Don't need problematic upgrades to downgrade my system.
cmerlyn said:
I wouldn't even take the OTA. Lots of issues with it. I am pretty sure LP will be the same.
I rooted mine, installed SafeStrap, and installed the XDK ROM, which eliminates all updates. My phone works great, does everything I want it to. Don't need problematic upgrades to downgrade my system.
Click to expand...
Click to collapse
Thanks to both of you for your suggestions. I think I'm going to go ahead and root and stay on the stock rom for a while. If the OTA shows up soon and looks worthwhile, I'll give it a try. Otherwise, I'll install SafeStrap and try a custom ROM.
Sure. Here's an easy answer: if you search for S5 AT&T and lolipop, you'll find lots of things that will say that AT&T will be taking its SWEET time putting an ota upgrade for lolipop out.
It is available from Samsung thru Kies, and I think I am personally going to take a new rom, and try and upgrade and unlock this piece of junque (and I upgraded from a Galaxy SII! )
Sigh