Database Develop

[Q] 4.2.2 Root to 4.4 Root on AT&T

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

Help me figure out what to do with my Moto X

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.

[Q] Setting up and rooting a new Verizon Moto X DE

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.

Root

I have been wondering if it is possible to root HTC one without installing any custom recovery. The issue with custom recoveries is that you can't update the phone with official updates. It's quite a pain in the ass to go back completely stock just to install an upgrade and then after updating, root again. It's not much work I know but still, if it's possible to do away with custom recovery and still have a root access, that'd be awesome. I used stock rom reset from another thread which had the option to grant root while going stock, but that didn't seem to do the trick.

[Q] Migration to Android 5.0

Hi,
I have a Motorola Moto G XT1068 - Dualsim, german version. I unlocked the bootloader and installed CWM PhilZ. OTA update does not work so I just skipped it until Android 5.0 is out now.
Questions:
1) I am using Titanium Backup Root for backing up my Apps, SMS, phone lists etc. I did not get any support from them if and how it will work on Android 5.0 due to the rumors that root is harder to enable. Any other update strategies, which programs do you use? ADB?
2) Which Rom (Fullrom?) do i have to flash in order to get Android 5.0 via OTA?
Thx for your answers

AFAIK no flashing of ROM is necessary as long as you're on stock. What you need is a stock recovery. I reckon you flash that ASAP.
Also, you might need to look into your system apps and make sure that you haven't deleted/disabled or converted to user apps.
Besides these steps, you'll be fine and will be able to update.

Androphilius said:
Hi,
I have a Motorola Moto G XT1068 - Dualsim, german version. I unlocked the bootloader and installed CWM PhilZ. OTA update does not work so I just skipped it until Android 5.0 is out now.
Questions:
1) I am using Titanium Backup Root for backing up my Apps, SMS, phone lists etc. I did not get any support from them if and how it will work on Android 5.0 due to the rumors that root is harder to enable. Any other update strategies, which programs do you use? ADB?
2) Which Rom (Fullrom?) do i have to flash in order to get Android 5.0 via OTA?
Thx for your answers
Click to expand...
Click to collapse
You have to install stock firmware and re-lock your bootloader. The guide to install stock firmware is on the general sub-forum and should be here.
I suggest using SMS Backup & Restore to backup your SMS. However, I recommend waiting until root is out to flash Android L. Then you can use Titanium Backup to restore your user apps & data.
I'm running L myself so I have to patiently wait for root. Good news though! The Moto X got a root solution by chainfire for Android L already. This means we could get root soon for Moto G.

Thank you for your answers so far.
I downloaded stock rom yesterday and planning to migrate today, due to the fact that a solution for rooting XT1068 comes near.
I just hope i got the right Stock Rom Version for german version and - always a bit worried that someone has put malware in the roms posted on fileshares.
Now I have to find out the right steps with ADB.
Full wipe, wipe cache, wipe dalvik and restore partition required as I am used to do with Samsung crap due to other mounting of sd card? Always did it with CWM the times before and never had to relock bootloader. But I have also read that locking is not required for flashing 5.0.
Okay, lazy saturday, I am going to find it out myself

Androphilius said:
Thank you for your answers so far.
I downloaded stock rom yesterday and planning to migrate today, due to the fact that a solution for rooting XT1068 comes near.
I just hope i got the right Stock Rom Version for german version and - always a bit worried that someone has put malware in the roms posted on fileshares.
Now I have to find out the right steps with ADB.
Full wipe, wipe cache, wipe dalvik and restore partition required as I am used to do with Samsung crap due to other mounting of sd card? Always did it with CWM the times before and never had to relock bootloader. But I have also read that locking is not required for flashing 5.0.
Okay, lazy saturday, I am going to find it out myself
Click to expand...
Click to collapse
Nope, no re locking required. Just do the samsung needful. I had one of its ****ty mobile too. So hi5 there.
Anyways, I don't understand why are doing this stuff. Most probably a flashable zip would be uploaded on XDA the same day or max the next day. Just chillax and wait for the good news to arrive, which I hope is any day now
P.S Oh and also make sure that you don't lock your bootloader at all. Because then you wouldn't be able to unlock it, at least not right now, hence you wouldn't be able to root.