if i update my moto x dev edition will it break foxfi. i see they just updated to 4.4 but im scared to do it hate having to use the bluetooth connection.
trinniboy68 said:
if i update my moto x dev edition will it break foxfi. i see they just updated to 4.4 but im scared to do it hate having to use the bluetooth connection.
Click to expand...
Click to collapse
Since you have the developer edition, are you rooted? If so, why not use the stock framework tether? You can use the Xposed module, or the Entitlement Check remover.
Also, if you are rooted, you can use the latest experimental build of WiFi Tether for Root Users.
Is there a specific reason you are wanting to use FoxFi? The only reason I can imagine is that you are not rooted.....but if you aren't rooted, why did you get the Developer Edition?
@trinniboy68,
I agree with @samwathegreat. If you have a Dev Edition, why not unlock your bootloader and root? It doesn't void your warranty on the Dev Edition. And its pretty easy on the Dev Edition.
If you root, and all you want to do is Tether, then to make taking future OTA's easier, I suggest using Wifi Tether For Root app (See my notes about setup at the bootom of THIS PAGE. )
Another option is [APP][MOD][Root]Hotspot Entitlement Bypass v1.1 5/9/2014, but it does make changes to the build.prop, and while it undoes them, I haven't tested to see if it changes the checksum of the build.prop when it reverts its changes(if it does, that would get in the way of future OTA's)
moto x
KidJoe said:
@trinniboy68,
I agree with @samwathegreat. If you have a Dev Edition, why not unlock your bootloader and root? It doesn't void your warranty on the Dev Edition. And its pretty easy on the Dev Edition.
If you root, and all you want to do is Tether, then to make taking future OTA's easier, I suggest using Wifi Tether For Root app (See my notes about setup at the bootom of THIS PAGE. )
Another option is [APP][MOD][Root]Hotspot Entitlement Bypass v1.1 5/9/2014, but it does make changes to the build.prop, and while it undoes them, I haven't tested to see if it changes the checksum of the build.prop when it reverts its changes(if it does, that would get in the way of future OTA's)
Click to expand...
Click to collapse
i have an unlocked bootloader. havent rooted yet cause i like the features of the moto are there roms that will dupl. the stock moto. i have verizon unlimited internet so need the ability to wifi link to my computer. as i am on the road a lot and its more secure to use my own wifi than someone elses. having a mac there arent any hacks for my phone, the one i did find the dev. isnt supporting it yet and bricking my phone i cant take right now as im fairly new to this. i rooted my s3
trinniboy68 said:
i have an unlocked bootloader. havent rooted yet cause i like the features of the moto are there roms that will dupl. the stock moto. i have verizon unlimited internet so need the ability to wifi link to my computer. as i am on the road a lot and its more secure to use my own wifi than someone elses. having a mac there arent any hacks for my phone, the one i did find the dev. isnt supporting it yet and bricking my phone i cant take right now as im fairly new to this. i rooted my s3
Click to expand...
Click to collapse
No 'hacks' for your phone? The entire android SDK is available for MAC. We have several users here who have flashed their phones 100% with MAC.
If you download the MAC Toolkit, it includes everything you need, even though it isn't supported by its devs anymore. You just won't use any of the scripts (that's all that no longer supported). Also, since you have the DEV edition, you WON'T lose your warranty by rooting it. It's HIGHLY unlikely you will brick your phone unless you do something totally stupid that is well documented here (like: you NEVER downgrade or flash older firmwares/versions on your Moto X - this is one of the few ways you can brick it).
Since you have already unlocked the BL, all you would do is fastboot flash TWRP recovery, and it will root for you. Then you can use either method that @KidJoe and I have suggested for you. There honestly isn't much at all you can mess up.
Additionally, once you install TWRP, you can take a full backup that you could restore in the event of a problem. PLUS the SBF images are available, so even without a backup your phone could still be restored back to stock.
trinniboy68 said:
i have an unlocked bootloader. havent rooted yet cause i like the features of the moto are there roms that will dupl. the stock moto. i have verizon unlimited internet so need the ability to wifi link to my computer. as i am on the road a lot and its more secure to use my own wifi than someone elses. having a mac there arent any hacks for my phone, the one i did find the dev. isnt supporting it yet and bricking my phone i cant take right now as im fairly new to this. i rooted my s3
Click to expand...
Click to collapse
Some of these sentences run together, so If I miss anything, I'm sorry.
Rooting wont remove any features of the stock Moto roms. As far as "other roms" duplicating stock, I haven't run anything but the stock rom. While there are "alternates" (like CM) if they are NOT based on stock, they will not have the Moto specific features like active display, always on listening (OK google now....), etc.
I have unlimited data too. I purchased the Dev X since I was going to have to buy an X at full retail because I wanted to keep my Unlimited (and be able to root without waiting on vulnerabilities/exploits).
All I've done is unlocked the bootloader, to root I just flashed TWRP recovery, and installed SuperSU (see -> http://forum.xda-developers.com/moto-x/moto-x-qa/step-step-instructions-unlocking-t2649738 although the TWRP and SuperSU versions linked are a little out of date now, they still work on 4.4 and 4.4.2). Then I use Wifi Tether for Root as mentioned earlier, greenify, Root Explorer, Quick Boot (reboot), Adree and not really much else that needs root, and no extra tweaks/hacks. In other words, I run stock, but rooted, with a few apps that need ROOT access, and nothing else modified on my phone.
The tools to flash the stock SBF files are RSDLite and mFastboot. Rsdlite is a GUI tool that flashes the full SBF/XML file, all commands, in like a batch mode. mFastboot is a command line tool that allows you to flash parts/pieces one at a time. I don't know if there is an RSDlite for Mac OS, but there is an mFastboot. So if you mess your phone up badly enough, you can usually recover with the stock images. (the only note being DO NOT DOWNGRADE your ROM!! for more see -> http://mark.cdmaforums.com/MotoX-Downgrade.htm )
thanks
KidJoe said:
Some of these sentences run together, so If I miss anything, I'm sorry.
Rooting wont remove any features of the stock Moto roms. As far as "other roms" duplicating stock, I haven't run anything but the stock rom. While there are "alternates" (like CM) if they are NOT based on stock, they will not have the Moto specific features like active display, always on listening (OK google now....), etc.
I have unlimited data too. I purchased the Dev X since I was going to have to buy an X at full retail because I wanted to keep my Unlimited (and be able to root without waiting on vulnerabilities/exploits).
All I've done is unlocked the bootloader, to root I just flashed TWRP recovery, and installed SuperSU (see -> http://forum.xda-developers.com/moto-x/moto-x-qa/step-step-instructions-unlocking-t2649738 although the TWRP and SuperSU versions linked are a little out of date now, they still work on 4.4 and 4.4.2). Then I use Wifi Tether for Root as mentioned earlier, greenify, Root Explorer, Quick Boot (reboot), Adree and not really much else that needs root, and no extra tweaks/hacks. In other words, I run stock, but rooted, with a few apps that need ROOT access, and nothing else modified on my phone.
The tools to flash the stock SBF files are RSDLite and mFastboot. Rsdlite is a GUI tool that flashes the full SBF/XML file, all commands, in like a batch mode. mFastboot is a command line tool that allows you to flash parts/pieces one at a time. I don't know if there is an RSDlite for Mac OS, but there is an mFastboot. So if you mess your phone up badly enough, you can usually recover with the stock images. (the only note being DO NOT DOWNGRADE your ROM!! for more see -> http://mark.cdmaforums.com/MotoX-Downgrade.htm )
Click to expand...
Click to collapse
thank you for the info
Related
Hi all!!!
I'm considering to buy the Moto X, I have a couple if questions though:
If I unlock the bootloader through Motorola, does root become easier (I realize that it isn't simple otherwise)
Is the bootloader relockable?
If I unlock a brand new phone, I won't lose anything, correct? You only lose what you install other than stock, is that correct?
Thanx all in advance...
shaya4207 said:
Hi all!!!
I'm considering to buy the Moto X, I have a couple if questions though:
If I unlock the bootloader through Motorola, does root become easier (I realize that it isn't simple otherwise)
Is the bootloader relockable?
If I unlock a brand new phone, I won't lose anything, correct? You only lose what you install other than stock, is that correct?
Thanx all in advance...
Click to expand...
Click to collapse
1. Yes if you unlock all you have to do is flash a custom recovery and supersu. Pwnmymoto is pretty easy too, though.
2. Yes but I don't think that will give you back your warranty
3. Unlocking will basically do a factory reset in the device. So if it's brand new and you haven't used it yet you won't lose anything. But if it's already set up and being used be sure to save anything important before you unlock.
Sent from my HTC One mini
Thanx!!! Isn't there an issue with PwnMyMoto with the camera update? Also it's safe to assume that once rooted WiFi tethering (like with FoxFi) will work, correct?
shaya4207 said:
Thanx!!! Isn't there an issue with PwnMyMoto with the camera update? Also it's safe to assume that once rooted WiFi tethering (like with FoxFi) will work, correct?
Click to expand...
Click to collapse
i would suggest replying to someone if you want them to respond to you otherwise it won't show up in their notifications if they aren't subscribed to the thread.
PwnMyMoto didn't screw up the camera update. It was built for the android OS that came stock on the phone. Maintaining root through the OTA/ camera update is difficult currently. But that is partly because all of the info on the updates haven't been released yet. As time goes on and things develop and those smarter than me decide to get things done we should be able to maintain root through the update and future updates with no problems. Also, safestrap was recently released and is working through bugs but it will be fully functional soon and we will be able to use roms through them and not take the updates.
wifi tethering only matters on vza at least if you have unlimited data. Otherwise, they don't charge to wifi tether anymore. you just can't go above your data limit. But yes, rooting allow those 3rd party tethering apps to work. They may even work without root actually. But with root you can change the stock tethering app and keep your carrier from knowing you are tethering.
@jayboyyyy Thanx!!!
Currently, heres my situation: Moto X, non DE, on VZW. Currently still on 4.4, although I just received the notification for 4.4.2 this afternoon.
I havent rooted yet, because mistakenly, I thought I was already on 4.4.2 since this phone is less than a week old. My mistake.
Id like to root in order to bypass the Exchange PIN requirement, as well as unbloat the phone. But, coming from an unlocked Galaxy Nexus on Verizon, I have to question if its really worth it since the bootloader is locked. i.e. can I stay up to date with AOSP based roms without an unlocked bootloader?
From my understanding, you (we... I'm in the same boat) can only flash stock based ROMs. Some, like Eclipse, are highly customized. I'm rooted and have Safestrap installed. Highly recommend you do the same.
Safestrap is an apk you install after rooting which installs a TWRP-based bootloader for Nandroid backup and flashing ROMs/files.
--Edit--
Here's some info I'd shared with another user:
Safestrap is an apk you install which loads a bootloader of sorts on your phone. When you boot up, you'd get an option to boot into a custom "recovery", even on locked phones. It's a modified version of TWRP. So, you install the app once rooted. I did it while on 4.2.2. Then you just need to find ROMs which devs have created specifically for Safestrap and flash that via recovery. Make sure to create a Nandroid backup (via recovery of course) before messing around with anything. There are two that I know of (both currently based on 4.4, but both devs plan to release 4.4.2 versions soon).
Stock ROM flashable via Safestrap here: http://rootzwiki.com/topic/108826-romsafestrapxt1060-stock-rooted-vzw-140455-kitkat/
Eclipse custom ROM here: http://forum.xda-developers.com/moto-x/development/rom-eclipse-moto-x-blur-based-v2-2-t2521509
You can download the Safestrap 3.65 apk (which should work fine on rooted 4.4, but again.. I installed it while on 4.2.2) here: http://rootzwiki.com/topic/104161-recovery-locked-safestrap-recovery-v365-2013-11-13/
mercado79 said:
From my understanding, you (we... I'm in the same boat) can only flash stock based ROMs. Some, like Eclipse, are highly customized. I'm rooted and have Safestrap installed. Highly recommend you do the same.
Safestrap is an apk you install after rooting which installs a TWRP-based bootloader for Nandroid backup and flashing ROMs/files.
Sent from my Moto X
Click to expand...
Click to collapse
Which root method did you use?
SlapMyMoto, but you can easily downgrade to the camera update version of 4.2.2 (the Moto X Toolkit makes it ridiculously easy), root it, install Safestrap, and go from there.
Sent from my Moto X
"Unbloat" is bit of a misnomer here, I think. It comes with a few VZW apps which can be disabled. Deleting them will not speed up your phone more than disabling them will.
Also, if your sole reason to root is to disable the single security precaution that your company asks of you in order to protect their data and intellectual property, well, as an IT employee myself, I'd suggest against it. You might even open yourself up to legal action if their data or networks were compromised due to you bypassing their security protocols. If you can't deal with the PIN lock, I'd recommend just removing the exchange account entirely - use the web interface if it's available.
Just my $0.02. There are lots of great reasons to root your phone. Just not sure the two you listed are among them.
My setup: 4.4 ATT Moto X, Rooted (by way of latest jcase method), Locked bootloader, and I'm pretty sure write protection is off (though I don't remember how to check)
What I am wanting to know is how would and should I be able to get to 4.4.2, and get my root back (as I'm not confident any method will be able to "keep" my root safely without screwing something else up)? What's the best way based on my setup, and what files or tools would I need(stock 4.4 or 4.4.2 ROM, a new recovery image, etc)?
Since the root method I used hijacks the recovery, I suppose I technically don't have a functional one (other than it maintaining my root). Do I even need a custom recovery? I don't ever plan to flash anything other than basic stock firmware, though I may toy around with Xposed in the future. Also as a sidenote, im currently using ART instead of Dalvik. If any method or technique might conflict with that (other than Xposed), then let me know to the best of your knowledge.
Write protection will be enabled on 4.4.2. You can have root, but a shutdown or hard reboot will erase the changes you make that are root oriented.
As far as getting to 4.4.2.....tonnes of info already here...multiple threads.
Here's a basic guide...and Google can help too. Read any thread related to 4.4.2 and locked bootloaders.
http://forum.xda-developers.com/showthread.php?t=2603358
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
I am using safestrap on my locked AT&T moto to get 4.4.2 + root + r/w on system - works perfectly.
(I modified the OTA to create a flashable zip that patches stock 4.4 up to 4.4.2, without updating the bootloader. I have an untested 4.4.2 flashable zip, and when the official SBF is released, I'll make another and test it myself.)
...
Sent from my XT1058 using XDA Premium 4 mobile app
kj2112 said:
Write protection will be enabled on 4.4.2. You can have root, but a shutdown or hard reboot will erase the changes you make that are root oriented.
As far as getting to 4.4.2.....tonnes of info already here...multiple threads.
Here's a basic guide...and Google can help too. Read any thread related to 4.4.2 and locked bootloaders.
http://forum.xda-developers.com/showthread.php?t=2603358
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
Click to expand...
Click to collapse
Honestly i dont even care to have an unlocked bootloader. I just realy need root after I update. Write protection, so far i think, i've only needed for AdAway to work on my phone, though Im sure I have used or applied it else on my device. And thanks for the thread, but I was already subscribed .
Ctrl-Freak said:
I am using safestrap on my locked AT&T moto to get 4.4.2 + root + r/w on system - works perfectly.
(I modified the OTA to create a flashable zip that patches stock 4.4 up to 4.4.2, without updating the bootloader. I have an untested 4.4.2 flashable zip, and when the official SBF is released, I'll make another and test it myself.)
Click to expand...
Click to collapse
While I would like to test that out further for you, I have only one phone lol. I very lightly looked in safestrap sometime ago when I was trying to find how to root previous versions of my phones software. Back then I didn't feel I needed it, as I was and still am trying to keep things simple this time around with my Android device. I'll look into it again and see if needs have changed, but would reeeeeally like to just find a way to get root after updating. Your way does actually sound enticing however.
NameLessThugZero said:
While I would like to test that out further for you, I have only one phone lol. I very lightly looked in safestrap sometime ago when I was trying to find how to root previous versions of my phones software. Back then I didn't feel I needed it, as I was and still am trying to keep things simple this time around with my Android device. I'll look into it again and see if needs have changed, but would reeeeeally like to just find a way to get root after updating. Your way does actually sound enticing however.
Click to expand...
Click to collapse
The only ways to use 4.4.2 Rooted with Write Protection DISABLED is the Safestrap way, or to unlock your bootloader.
Since you have AT&T, Moto doesn't give out the code to unlock your bootloader (Non-Developer Edition Verizon phones are the same way.) so if you really want to unlock your bootloader, see -> http://forum.xda-developers.com/moto-x/general/verizon-moto-maker-bootloader-unlock-t2680651 I know the thread title says VERIZON but it works for ATT users too.
I see, thanks for the explanation, because I certainly wouldn't have know it was for AT&T users too! I'll check them out.
Sent from my XT1058 using XDA Premium 4 mobile app
Ctrl-Freak said:
I am using safestrap on my locked AT&T moto to get 4.4.2 + root + r/w on system - works perfectly.
(I modified the OTA to create a flashable zip that patches stock 4.4 up to 4.4.2, without updating the bootloader. I have an untested 4.4.2 flashable zip, and when the official SBF is released, I'll make another and test it myself.)[/QUOTE
So essentially, I cant just install Safestrap, then update to 4.4.2, correct? I'd need to do what you did, which is to modify the OTA?
Click to expand...
Click to collapse
NameLessThugZero said:
So essentially, I cant just install Safestrap, then update to 4.4.2, correct? I'd need to do what you did, which is to modify the OTA?
Click to expand...
Click to collapse
Right. You want a modified version of the OTA that does not modify your bootloader and will patch /system from 4.4 to 4.4.2. I also manually patched the kernel up to 4.4.2.
And, my experience is that you also have to downgrade to 4.2.2. I don't quite understand why, but I have never been able to upgrade to 4.4.x (neither from the 4.4 leak or the official 4.4 version) without going back to 4.2.2 first. The eclipse ROM instructions, on the other hand, suggest that a safestrap:twrp factory wipe might be enough, but I remember trying that once, and it didn't work. YMMV
I already made a zip to flash a full copy of 4.4.2 (not a patch) that I made from my system dump, but it hasn't been tested. (I'm waiting for the SBF.)
Alright. Well I guess I'll have to wait a bit for someone to come out or prove there's a safer, surer method to update. Moto always did like to make thing like this difficult, heh.
Sent from my XT1058 using XDA Premium 4 mobile app
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.
Before I update my DevEd to 4.4.4, I want to ensure that I will still be able to root (use recovery tool or something else?) and that there is some way to use tether.
On 4.4.3, I've been happy using WiFi Tether for Root users - would be nice if this continued to work, but am okay using a different method if need be.
Can someone confirm that both root & tether are functional, and if so, what method(s) are working?
With an Unlocked Bootloader, Yes, you can root by flashing TWRP and SuperSU, the same process. Just make sure you have the latest TWRP and SuperSU from their source web sites. That will be true for ALL updates so long as you have an unlocked bootloader. And it can be dev edition or carrier edition, as long as the bootloader is unlocked.
Wifi tether for root still works on my VZW Dev X with 4.4.4 update.
Mercutio5 said:
Before I update my DevEd to 4.4.4, I want to ensure that I will still be able to root (use recovery tool or something else?) and that there is some way to use tether.
On 4.4.3, I've been happy using WiFi Tether for Root users - would be nice if this continued to work, but am okay using a different method if need be.
Can someone confirm that both root & tether are functional, and if so, what method(s) are working?
Click to expand...
Click to collapse
Of course...you're unlocked. Same method - flash TWRP and it will root for you. Since you don't seem to be aware -- you can NOT update unless you flash back stock recovery and un-do any changes you made to /system including installing Xposed (if you did). If all you are using root for is WiFi Tether, nothing to worry about as you probably haven't modified /system. You WILL have to flash back the stock recovery.img before you can accept any OTA. Its always been like this.
WiFi tether should work on 4.4.4, as should the entitlement 'hack'. (I believe both have been confirmed, but check the entitlement hack threads to be sure about it)
And finally......since you mention being on 4.4.3 now, I'm assuming you are using the XT1053 GSM Dev edition (since 4.4.3 was never released for VZW). If so...you do realize that 4.4.4 isn't out yet for the XT1053, right?
It's only out for the VZW XT1060 and soak-tests are just now happening for the AT&T XT1058.
samwathegreat said:
Of course...you're unlocked. Same method - flash TWRP and it will root for you. Since you don't seem to be aware -- you can NOT update unless you flash back stock recovery and un-do any changes you made to /system including installing Xposed (if you did). If all you are using root for is WiFi Tether, nothing to worry about as you probably haven't modified /system. You WILL have to flash back the stock recovery.img before you can accept any OTA. Its always been like this.
WiFi tether should work on 4.4.4, as should the entitlement 'hack'. (I believe both have been confirmed, but check the entitlement hack threads to be sure about it)
And finally......since you mention being on 4.4.3 now, I'm assuming you are using the XT1053 GSM Dev edition (since 4.4.3 was never released for VZW). If so...you do realize that 4.4.4 isn't out yet for the XT1053, right?
It's only out for the VZW XT1060 and soak-tests are just now happening for the AT&T XT1058.
Click to expand...
Click to collapse
I'd just assumed to be on 4.4.3 since it's previous to 4.4.4 - but you're correct, I'm on 4.4.2 VZW. After reading through some update methods discussed on XDA, it seems that using RSDLite w/FXZ is the easiest - no need to undo any changes made to /system (I'm sure I've made some, but have no idea what they might have been) and no need to remove TWRP. Plus it supposedly preserves all the data.
And thank you for assuaging my concerns re: root & tether
Mercutio5 said:
I'd just assumed to be on 4.4.3 since it's previous to 4.4.4 - but you're correct, I'm on 4.4.2 VZW. After reading through some update methods discussed on XDA, it seems that using RSDLite w/FXZ is the easiest - no need to undo any changes made to /system (I'm sure I've made some, but have no idea what they might have been) and no need to remove TWRP. Plus it supposedly preserves all the data.
And thank you for assuaging my concerns re: root & tether
Click to expand...
Click to collapse
Take caution!! The original leaked fxz was indeed a keep data fxz. It's now gone. The new official leaked fxz is NOT a keep data fxz.
All you have to do is edit the XML file and remove the line containing 'erase userdata' and it will preserve your data.
If you don't do this all your data WILL be erased.
Keep that in mind...
Good luck
samwathegreat said:
Take caution!! The original leaked fxz was indeed a keep data fxz. It's now gone. The new official leaked fxz is NOT a keep data fxz.
All you have to do is edit the XML file and remove the line containing 'erase userdata' and it will preserve your data.
If you don't do this all your data WILL be erased.
Keep that in mind...
Good luck
Click to expand...
Click to collapse
Yikes!! Thank you for the heads up.
How did the leaked FXZ disappear? Surely someone's still got it somewhere?
Mercutio5 said:
Yikes!! Thank you for the heads up.
How did the leaked FXZ disappear? Surely someone's still got it somewhere?
Click to expand...
Click to collapse
Its all the same "inside" except the included XML file now contains the "Erase USERDATA" statement. Just remove that line from the XML before flashing with RSDLite and you're good.
No reason for the original leak to stick around.