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.
Ok so I rooted my galaxy note3(about a month ago), but today when I turned it on the phone instantly installs a new update without my permission and takes away my root. This would be fine, but now my phone says "custom" when booting up and it is not rooted anymore. How would I be able to take away the "custom" boot image? I am seriously considering selling att GN3 at this point(tired with ATT bs and lack of any info on updates) and opting for a nexus 5. My only problem is that people will be turned off by my previous evidence of rooting my device because it says "custom". I essentially would like to return my phone to all stock settings.
nigerson said:
Ok so I rooted my galaxy note3(about a month ago), but today when I turned it on the phone instantly installs a new update without my permission and takes away my root. This would be fine, but now my phone says "custom" when booting up and it is not rooted anymore. How would I be able to take away the "custom" boot image? I am seriously considering selling att GN3 at this point(tired with ATT bs and lack of any info on updates) and opting for a nexus 5. My only problem is that people will be turned off by my previous evidence of rooting my device because it says "custom". I essentially would like to return my phone to all stock settings.
Click to expand...
Click to collapse
Try simply rebooting. That worked for me after unrooting via odin one click on mi9. The first boot showed custom wich confused me but after just a reboot it went away. I think it softbooted after odin and didnt run through the whole process.
If not then the only option currently to remove custom is to re root using kingo then use xposed to fake custom system status. The latter would be shady however if you plan to sell the device.
powdered_donuts said:
Try simply rebooting. That worked for me after unrooting via odin one click on mi9. The first boot showed custom wich confused me but after just a reboot it went away. I think it softbooted after odin and didnt run through the whole process.
If not then the only option currently to remove custom is to re root using kingo then use xposed to fake custom system status. The latter would be shady however if you plan to sell the device.
Click to expand...
Click to collapse
Sorry to bother you, but I am not too familiar with how to do this. Would you be able to show me some sort of step-by-step guide which I would be able to use? Also how do I check if I'm on mi9 and not something else(because I currently have the most updated firmware on my phone)
http://forum.xda-developers.com/showthread.php?t=1574401QUOTE=nigerson;47504941]Sorry to bother you, but I am not too familiar with how to do this. Would you be able to show me some sort of step-by-step guide which I would be able to use? Also how do I check if I'm on mi9 and not something else(because I currently have the most updated firmware on my phone)[/QUOTE]
The most updated is mj5 if you took the ota update that hit recently. You can check by going to settings then about phone then look at the last 3 digits of the baseband.
To install xposed go to the link at the top it pasted there on my tablet for some reason. Instructions are there for installation.
download the xposed installer apk. You must be rooted. Use kingoapp for that if necessary. Open xposed installer and go to framework. Install the most recent framework. Then go to download. Download cosmetic device status normal modification. Use that to remove the custom padlock. Reboot. Hit thanx
powdered_donuts said:
http://forum.xda-developers.com/showthread.php?t=1574401QUOTE=nigerson;47504941]Sorry to bother you, but I am not too familiar with how to do this. Would you be able to show me some sort of step-by-step guide which I would be able to use? Also how do I check if I'm on mi9 and not something else(because I currently have the most updated firmware on my phone)
Click to expand...
Click to collapse
The most updated is mj5 if you took the ota update that hit recently. You can check by going to settings then about phone then look at the last 3 digits of the baseband.
To install xposed go to the link at the top it pasted there on my tablet for some reason. Instructions are there for installation.
download the xposed installer apk. You must be rooted. Use kingoapp for that if necessary. Open xposed installer and go to framework. Install the most recent framework. Then go to download. Download cosmetic device status normal modification. Use that to remove the custom padlock. Reboot. Hit thanx [/QUOTE]
So, I am on mj5 right now since I got the OTA update and I am no longer rooted because of this. How can I flash to stock or reroot and install xposed? Or am I ****ed?
*EDIT USED KINGO INSTALLED FRAMEWORK ALL IS GOOD IN THE HOOD *
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 am on T-Mobile Nexus 6 with 5.0.1, rooted with NRT (used Chainfire + TWRP Recovery). I have been expecting to get a notification to update to 5.1 within the device, but haven't gotten anything, even when I manually check for updates from the device (Settings > About > Update). Do I need to do something manually since I am rooted? I also looked for the 5.1 M build on Google's repository and couldn't find it. Thanks for the help!!
Over the air will not apply with a custom recovery. you can be patient and wait for M (NRT will update < 12 hours after Google does) or you could flash a stock recovery and OTA.
If you wait and use NRT there will be an option for the M version and then you can just do a flash to that version with the retain user option
Sent from my Google N6 on VZ
theres a stock, rooted T-Mobile build in the development section. Just flash that
I too have been waiting of the factory image to show up. Is there any reason why the TMo version hasn't been posted yet by Google? I'd like to use the stock image as it seems the easiest way to retain my data. I know there are other methods but they all seem to wipe your phone.
OGMCVilleTC said:
I too have been waiting of the factory image to show up. Is there any reason why the TMo version hasn't been posted yet by Google? I'd like to use the stock image as it seems the easiest way to retain my data. I know there are other methods but they all seem to wipe your phone.
Click to expand...
Click to collapse
Except the method posted immediately before your post.
I'll look for it. Thanks for the info.
I am looking to update to lollipop but I can not use the built in updater because im on cricket and not ATT.
Can anyone help me with a guide or a safe way I can get the update? Please and thank you
Trem Fantasma said:
I am looking to update to lollipop but I can not use the built in updater because im on cricket and not ATT.
Can anyone help me with a guide or a safe way I can get the update? Please and thank you
Click to expand...
Click to collapse
Is your phone the SGH-i537 (AT&T USA version) or the GT-i9295 (international version)? If it's the former I can most likely give you the file you need, but I'd need to know what firmware version you're currently on: settings > about device > baseband version. If it's the latter I can still probably point you in the right direction.
Oh, also, if you do have the i537 let me know if you're rooted or not currently and if you wish to be rooted once on lollipop
I have the SGH-i537 one and i am at I537UCUCNE3 4.4.2
Trem Fantasma said:
I have the SGH-i537 one and i am at I537UCUCNE3 4.4.2
Click to expand...
Click to collapse
If you just want to update and don't want root (and aren't already rooted), download this file and save to your external SD card (not internal storage):
https://www.androidfilehost.com/?fid=24052804347793671
Power your phone off. Boot into stock recovery (hold vol+ and power), choose install update from external storage, and navigate to where you saved that file and select it. It will probably take up to five minutes to install, so make sure you have plenty of battery (50%+)
When that is finished, repeat the exact same process with the following file (it's the version of lollipop with the stagefright patch, i.e. an important security fix), but has to be installed after the preceding file:
https://www.androidfilehost.com/?fid=24052804347793660
If you're already rooted, the above process will not work. Even if you're not already rooted, but think you might want to be once on lollipop, there is no way to root lollipop directly, so a different update method is required. If you're at all thinking about messing around with root, and especially if you are already rooted, you need to use the following method to update:
http://forum.xda-developers.com/galaxy-s4-active/general/how-to-update-to-i537oc6-5-0-1-t3089355
Thank you so much