yashsingh1/xdaforums huggingface dataset:
[Moto X General] xpsychox:
like i said, skimmed, guess i missed that one... whoops!!!
[Moto X General] stonesaber:
It doesn't makeroot useless. The only thing I rooted for was xposed and it still works. You just have to reinstall the framework and do a soft reboot after you've done a normal boot up for it to stick. We had to do the same thing before motowpnomo was released. Tethering works fine as well.
[Moto X General] syntrix:
Interesting. I'll try xposed again for manyth time. The first thing the installer does is (incorrectly) mount /system rw. Again, we are in the LOCKED bootloader thread :)

edit: and it works! Thanks!

edit edit: and it's gone after a reboot! Looks like you need to install it, then ONLY soft reboot it. Any other boots, and it appears that you'll have to reinstall and soft reboot.

Here's what mine is doing:

4.4.2 verfied working root, xposed previously installed.

Power off

Power on (full boot)

Install xposed framework

soft reboot from framework menu.

Gravity box mods active, ok it's working!

Choose reboot from the normal menu.

No GB mods active, xposed isn't installed warning in the installer.

So it appears that you can have it until reboot, or keep reinstalling it.
[Moto X General] akhenax:
There is conflicting information regarding having r/w to the system, and having root.

If you have 4.4, are rooted, non Dev phone on Verizon, can you accept the OTA for 4.4.2?

If so, then what do you have to do to protect root (Xposed works, tethering works, everything that requires root, works?

If you need to restore your phone, will you be able to do so, and still keep root?

I would like this information in plain easy to understand steps, so that users don't have to read all the replies to get this one answer.
[Moto X General] KidJoe:
Correct. Because Write Protection is enabled, anything done to /system or the like will be lost after you power the phone off/on, or "hard reboot."

---------- Post added at 11:15 AM ---------- Previous post was at 10:52 AM ----------

Conflicting? maybe, but I'd sooner say that it can be confusing and difficult to follow. Especially since initially all the talk about the OTA was in a thread consisting of those with both locked and unlocked bootloaders (which does impact what works and what doesn't).

See Post #1 and 2 of this thread. You will need your phone back to stock, with modifications removed, etc. or the OTA update will fail to install.

To protect root, nothing. Root survives, however Write Protection, for the system folders and the like, becomes re-enabled. So the effects of MotoWpNoMo (which was said to be permanent) are lost. This means any changes you manage to make to /system after you get onto 4.4.2 will be lost on a hard reboot.

I can't tell you which apps/mods this will impact because I have an UNLOCKED bootloader which behaves differently and doesn't limit me the same ways.

But you can see that syntrix has posted about Xposed working, but being lost after hard boot (power on/off).

Not sure what you mean here. If you are talking about downgrading to 4.4 or lower, that wont be possible. The updated bootloader included in the 4.4.2 OTA prevents downgrading.

There is speculation that a locked bootloader user who uses mfastboot to flash system, modems, etc one at a time, leaving out boot, gpt.bin and such might allow you to retain WP Disable and root, and be on 4.4.2 along with leaving the ability to downgrade to 4.4. (this would be instead of using RSDLite to flash the entire SBF/XML file) But I've been away for a little, so I've not seen posts proving its true yet.

The one true statement from all of the posting that can be made...

If you have a LOCKED bootloader, and want to keep root and write protection disabled, do NOT take the 4.4.2 update. Instead wait. Stay with what you have. While Jcase and beaups have stated they won't have a root nor WP Disable for 4.4.2 with locked bootloader, you never know if someone will find a way to upgrade and retain root/WPdisable. And once you are on 4.4.2, there is no way back.
[Moto X General] mercado79:
KrYpToNiTe came through. His stock Safestrap-flashable 4.4.2 ROM is up on Rootzwiki and even if you're not interested in the ROM itself, he includes a script that can be used to update the baseband and kernel of Moto X's with locked bootloaders. Go get 'em!

http://rootzwiki.com/topic/116025-romsafestrapxt1060-stock-rooted-vzw-164552-kitkat-442/

Sent from my Moto X
[Moto X General] chevyrado14:
i have tried manually flashing the stock 4.4 recovery to my wifes x and it fails every single time. i used rockmymoto to root it originally so i have the fake recovery on there now. the error that fastboot shows when i try to flash the 4.4 recovery is failed to hab check recovery 0x56 or something similar i dont have access to the phone now to try it again. how would i get the stock recovery back on there if i wanted to try to take the ota?
[Moto X General] akhenax:
I would use RSD Lite to reflash, then start from scratch using the SlapMyMoto method.
[Moto X General] sonic1675:
so technically we CAN still use rsd to downgrade??
[Moto X General] sonic1675:
How in the world is you guys battery better?? For me it's been worse with each update and I was never rooted to begin with and I disabled all the bloatware and turned off everything with brightness to the lowest and i even factory reset and i still have the same problems and I can't down grade now so I'm kinda pissed off about this and this is average for me and I don't even get 2 hours sot :(
[Moto X General] KidJoe:
If you are on 4.4.2 already, no. The new bootloader in the 4.4.2 OTA prevents downgrading.

If you are on 4.4, its bootloader lets you downgrade to the 4.2.2 w/camera fix, but not the initial shipping 4.2.2 version.

Oh, and that applies to both locked and unlocked bootloader phones.
[Moto X General] :
Get Gsam, and root companion if your rooted and so a full cycle and post some screens of it. The stock battery screen shows little info. ;)

Sent from my N5 cell phone telephone....
[Moto X General] virginmoto:
I just got my Moto X for Verizon (locked bootloader) and wanted some clarifications on all the rooting business going over all the forums, here is what I have learnt.

It is possible to root 4.4 but you would need to go to 4.2.2 to do so. And this is the best and current guide to do so: http://xdaforums.com/moto-x/general/ref-how-to-root-4-4-links-guides-t2603358

Currently updating to 4.4.2 with root is possible but the write access is lost which will render most applications that utilize root useless.

My questions are as follows:

1) I normally use the Adfree or AdAway app that requires root and my understanding is that it changes the /system/etc/hosts file so would it mean that upgrading to 4.4.2 on a rooted 4.4 render these apps useless? What about Tasker or Greenify that have the option of using root can they still utilize root function?

2) Will 4.4.2 ever be rooted in the future?

3) If I root my 4.4 how easy/safe is it to go back to "stock" and then go to 4.4.2? (if rooting future releases would be impossible to root)
[Moto X General] sorullo_xgrx:
1) adaway will certainly be useless in a rooted 4.4.2 because it requires you to reboot device after updating the system files so changes won't stick after reboot without RW privileges. I think greenify now works without root so it means you might really don't need RW privileged to run the app. Tasker it doesn't requires you to reboot for changes to be take off what I know so that should work too.

2) No one knows but I think at this moment knowing that a successor for the Moto X is coming later this summer I don't someone will invest time to find a root method now.

3) If you are rooted on 4.4 is not hard you can simply use this tool http://xdaforums.com/showthread.ph.../Restore,Drivers,Return to stock,Root,Bootani. You might still be able to go back to 4.2.2 if you ever would need to. If you are rooted on 4.4.2 you might go back to stock but won't be able to downgrade to either 4.4 or 4.2.2. If I'm wrong in something please someone correct me. That's my understanding
[Moto X General] yumms:
So my new Maxx came with 4.4 preinstalled (not 4.4.2), what can I do, obviously not root but can I downgrade?
[Moto X General] KidJoe:
Correct... and the "Rooting Locked Bootloader" section of the guide you link does a good job at summarizing the RockMyMoto/SlapMyMoto/MotoWpNoMp processes.

sorullo_xgrx already did a great job of answering, but I want to expand a little..

1. When it comes to 4.4.2 and Write Protection being Enabled... Like the example of Adaway, for any app that makes changes to /system or protected folders, those changes will be lost at power off/on. So any of those apps would be useless once write protection is enabled again. (Note: Write Protection Enabled is the default status for locked bootloader phones. If you can unlock your bootloader, WP is disabled and will stay disabled).

2. Like sorullo_xgrx, I too don't have any faith in 4.4.2 or future updates being rooted, but for different reasons. Remember the Moto X is really close to stock Android. Any vulnerability or exploit in the android base will likely be plugged quickly after a root process is published. More important is finding a way to disable Write Protection on an X with locked bootloader. This will be unique to the X's bootloader version (and possibly the Droid Maxx since they are similar). It will be way more difficult than trying to root. Even if they manage to find an exploit to allow rooting, without disabling write protection, its worthless.

3. Getting back to stock really depends on how much you've messed with or changed /system files. For me, I just rooted, installed Wifi Tether for Root, renamed some of the Backup Assist APK's, and since I have an unlocked bootloader, I installed TWRP recovery. To take the OTA, I had to flash stock recovery back on my phone, and rename the Backup Assist APK's back to normal. If you mess with the Build.Prop, verizon wifi tether entitlement apk hack, or other modifications, you have to undo them all. In many cases, flashing system.img via mfastboot (which would return the system files back to stock without losing data) is enough. If you have safestrap setup, it could be even more work to get back to "stock". In reality, since the 4.4.2 SBF is out, if you want to go to 4.4.2, its probably best if you just use RSDLite and flash to get there.
[Moto X General] 530farm:
I have been having trouble updating to 4.4.2. I have a locked bootloader, Rooted 4.4. I tried disabling the 3 xposed modules I have installed and when I try to update I get a "failed" as it tries to update, then it just reboots. Any help would be appreciated.

Thanks
[Moto X General] sonic1675:
This is what I have according to gsamView attachment 2622370
[Moto X General] mastarifla:
If the person already has a custom recovery installed then wouldn't it be possible to update the hosts file in the recovery since it is WP disabled? Or does the locked bootloader prevent flashing recovery images?

Edit: Turns out that locked bootloaders cant flash any modified images with fastboot

If they are rooted and they are on a <=4.4.0 bootloader, isn't it possible to just use the Safestrap recovery to flash files? This would nullify WP woes/concerns, because they would just boot to recovery and flash everything in there.

According to a thread in the Dev section there is no need to flash stock recovery to get the OTA to work ;)
[Moto X General] :
If any of that were possible, it would be common knowledge and practice by now. No? :)

Sent from my N5 cell phone telephone....
[Moto X General] KidJoe:
Locked bootloaders can flash parts with fastboot, assuming they are properly signed by Moto. So, for example, you could unzip an SBF and flash system.img from it onto a locked bootloader phone, but you can't replace (flash over) the stock recovery "partition" with a custom recovery onto a locked bootloader phone.

Safestrap is different than natively flashing. Think of it as Host/Guest type sytem... the rom in the slot being the "guest" is stored on the phone's internal storage, so while WP might not apply, its taking up space on your storage. Have a 16gig phone and use safestrap, how much storage is left for music, movies, apps, etc...

Its not the same as just using RockMyMoto, SlapyMyMoto and MotoWpNoMo with 4.4 and lower... where you are using those tools to root and disable write protection, without adding complexity, or using up "user storage"

This applies to dev edition or unlocked bootloader only. Once you edit the OTA Zip, as explained in that thread, and re-zip it, you break the moto signature and it wont load on phone with a lock bootloader. The locked bootloader only allows files properly signed by Moto to be flashed. If you could do this on locked bootloader phone (i.e. edit the OTA zip, rezip it and flash), you could possibly remove flashing the updated bootloader and other parts that re-enable Write Protection that are included in the OTA file.

Now, throw safestrap in there, and try updating a safestrap rom this way might be possible. But I'll let someone who is more familiar with Safestrap comment on it.
[Moto X General] mastarifla:
So is it still possible? Even though you have to sacrifice space, I'm sure many would give that up in order to have a functional root and be on the latest version of android, granted you would have to wait for a Safestrap ROM.

Very true, and thanks again for taking the time to answer my questions.

If Moto were to only give updates as one file inside a zip instead of a zip composed of many files, would this prevent users from flashing only specific files? So they would HAVE to update the bootloader version etc. if they wanted to update via Moto.
[Moto X General] KidJoe:
There is a thread on Rootzwiki.com about safestrap and 4.4.2. You can take a look and see whats possible. I don't use safe strap since I have Dev Edition and unlocked bootloader.

Not sure what you are asking.

No matter how Moto delivers it, with a locked bootloader you are stuck being able to flash only signed Moto files. Be it an OTA zip containing multiple files, an IMG inside an SBF that you unzip (and flash via fastboot), or whatever.

Having an unlocked bootloader doesn't limit you like that. You can flash unsigned files.
[Moto X General] mastarifla:
I guess I should have prefaced the question before asking, I was considering what Moto could do to prevent people from only flashing certain files with a locked bootloader, thus forcing users to update in order to be on the latest version of android instead of using workarounds like Safestrap that depends on flashing a few SBF files.
[Moto X General] sorullo_xgrx:
I believe you have to fastboot flash back to stock recovery to update since when you for using slapmymoto it flash a modify recovery. Just extract recovery.img from the XML Verizon file for the 4.4 update.
[Moto X General] :
The Android recovery isn't designed to work like that.

Moto could probably do some software development to allow them to, say, encrypt the zip file and only their software would be able to decrypt and write the contents, but it'd probably be more trouble than it's worth.
[Moto X General] KidJoe:
There could always be dependencies in a given rom... like this system.img requires particular modem files (that has happened on past devices), maybe they could make it that a system.img needs a particular bootloader be installed on the device or such?

The OTA's do include a manifest file and check it before it installs. The manifest is a list of files expected to be on your phone, along with a hash for each. If the expected file is missing or doesn't match the hash, the OTA will fail.
[Moto X General] 530farm:
So if i can find the stock 4.4 recovery.img, can I just flash it via my mac with the below commands?

./fastboot flash recovery stock_4.4_recovery.img

Then after doing that, just disable xposed modules and then apply update?
[Moto X General] sorullo_xgrx:
Yes, just don't forget to rename it to just recovery.img
[Moto X General] akhenax:
Installing Rom

Just so that I am clear, the only way to install a 4.4.2 ROM, on a Moto X with a locked bootloader (Verizon), is to use Safestrap?
[Moto X General] tekhna:
At this point, yes.

Edit: I should clarify--the only way to have 4.4.2 with root and /system RW is with Safestrap. You can have 4.4.2 w/o root, or 4.4.2 w/root and no /system writing, but not 4.4.2 with root and /system RW unless you use Safestrap.
[Moto X General] KidJoe:
If you want to keep root and WP Disable, yes.

If you don't care about root, then as long as you have stock recovery on your phone, and haven't altered system files on your phone, you can install the OTA.
[Moto X General] akhenax:
Yes, I meant having 4.4.2 ROM rooted, with /system RW. Thank you.

I don't like the idea of Safestrap. This is perhaps because all the previous Android devices I have owned allowed me to flash Rom's to the system directly (Droid, GNex).

I believe Safestrap just creates a slot, and allows me to send an image to that slot, and then boot from that particular slot. Doesn't seem complete for some reason, also it's like I'm wasting system resources.

I have no issues with 4.4, as it works smoothly. I have all the mods that I want/need installed. No need to go to 4.4.2 at this time; I'll wait a bit longer to see if a better method is developed.
[Moto X General] iKrYpToNiTe:
Safestrap was originally created for older Motorola devices that had external sd cards, this allowed the internal storage space to be used for creating virtual rom slots to install roms on, to keep the /system partition safe from bricks. But there has been issues with installing to virtual slots since 4.2.2, and most people have 16gb versions which fills up quick if you create a virtual slot. So to get 4.4.2 via Safestrap you have to flash to the stock slot which is exactly what twrp does on unlocked devices. The only difference is you have to flash the kernel and baseband via fastboot since Safestrap can't flash kernels.

So I don't understand why you don't like Safestrap or why you think it is wasting system resources lol!
[Moto X General] akhenax:
OH. So you don't flash to a virtual slot, you flash to the stock slot?

Safestrap is basically an external TWRP or CWM, that cannot flash the kernel or baseband?

Are you the same KrYpToNiTe from here: http://rootzwiki.com/topic/116025-romsafestrapxt1060-stock-rooted-vzw-164552-kitkat-442/
[Moto X General] iKrYpToNiTe:
Yes you flash to the stock slot, virtual slots never worked for me on the Moto X, and didn't work that great on my Razr Maxx either I've always flashed to the stock slot. Safestrap is based on TWRP it is a bootstrapped recovery for locked devices that allows you to flash anything you want to the /system partition.

Yes that is my rom on rootz.
[Moto X General] tejaskary:
Dumb question...after installing 4.4.2 to the stock slot using safestrap, is it possible to rsd lite to 4.4 (downgrade is blocked if we directly ota to 4.4.2)...I am guessing yes since the boot loader is not touched?
[Moto X General] akhenax:
That's my thinking as well. Since we have downgraded to the 4.2 bootloader already, Safestrap does not touch the bootloader. The only way the bootloader is upgraded (and thus locks us from rooting) is by taking the OTA.
[Moto X General] grhomes:
Um... https://twitter.com/TeamAndIRC/status/443850349678321664
[Moto X General] :
Not sure if I misread it, but he has root now....but is releasing it in August? LOL

Don't hold your breaths. ;)

Sent from my N5 cell phone telephone....
[Moto X General] KidJoe:
Encouraging. But no mention of write protect disable which is a very important part.
[Moto X General] 640k:
this comment:

[MENTION=5734172]camerony[/MENTION]eager details released in Aug

makes me think it was already released. to me the message interprets as, he just rooted a Sony and the same method works for the HTC and the X.

---------- Post added at 10:39 AM ---------- Previous post was at 10:19 AM ----------

FWIW - i found this:

http://xdaforums.com/showthread.php?t=2644946&page=10

root user granted on Xperia Z1, but still no system r/w. unknown if this is related to his twitter.
[Moto X General] :
Still not very useful, but a step forward. I still think best solution is device replacement with a different model....for those who can't unlock. :)

Sent from my N5 cell phone telephone....
[One (M7) Q&A, Help & Troubleshooting] GauthamD:
Hello there !!!

Please assist !!

It was htc one !!

It was running on 4.3 stock !!

Then I flashed miui v5 without backup through cmw !!

Miui had a base version of 4.2.1 !!

Then after a few hours I figured out that camera isn't working !!

So downloaded htc one stock google nexus 4.4.2 version !!

Flashed !!

Boot loop !!

No external sd card !!

Can only boot in recovery and in HBoot!!

Boot screen reaches to language selection and reboots !!

Badly in need of help !!

I should fix it before I'm deprived off new phones !!

Waiting for replies !!

Now I'm downloading stock 4.3 !!
[One (M7) Q&A, Help & Troubleshooting] alray:
Give a link to this rom please !!

and link to this rom also please !!

post your fastboot getvar all output!!

Minus IMEI/SN!!
[One (M7) Q&A, Help & Troubleshooting] GauthamD:
It's the last rom in the cad rom page !! Nexus edition for htc one !!

And these technical things ! I'm sorry , I really don't understand !!

I think I should push a stock rom in sd card somehow and flash through cmw !!

Can you please help me out !!

Regards ,

Gautham !!
[One (M7) Q&A, Help & Troubleshooting] alray:
Do you have adb/fastboot (android sdk) on your computer with latest htc drivers? You will need that to push a rom to your phone.
[Galaxy S III Q&A, Help & Troubleshooting] Shadowspsp:
Hello,

long time no see!

Just want to confirm if it's still the same case or anything changed.

I have a Galaxy S3 GT-I9300 ( I9300XXUGMK6 "4.3 Android" ) from Germany. Now i want to flash a firmware from another country for example "I9300XXUGML3" 4.3 Android for GT-I9300 from Singapore. Is it possible or has SAMSUNG changed anything in their policies that makes it impossible? Used to be possible with Odin.

thanks mates ! :)
[Galaxy S III Q&A, Help & Troubleshooting] SlimSnoopOS:
I'll see about getting a mod to move this for you. You want the i9300 Q/A forums, these are the sch-i535 Verizon S3 forums. We have an entirely different model than you.
[Galaxy S III Q&A, Help & Troubleshooting] chrismast:
Should still be possible. I wouldn't know why not.
[Galaxy S III Q&A, Help & Troubleshooting] hierarchy666:
Yes you can im using rom from India but im from Singapore
[Nokia Lumia 920] kus234:
Hi,

I want to know if you can re-install a ROM on Nokia Lumia 920, if yes how, is there a thread which details that out.

Also if i flash a ROM will that unlock my Phone? My Phone is currently locked to AT&T?

Please advice.
[Nokia Lumia 920] dxdy:
lock/unlock dont have anything with flashing....

for simple reflashing you can use NSU

http://mynokiablog.com/2013/10/11/how-to-easily-fix-the-lumia-reset-spinning-cogs-at-home/

or Software Recovery tool

http://www.nokia.com/us-en/support/software-recovery/
[Nvidia Tegra Note 7] CLB-NL:
Are there any people here that have problems with the AOSP-browser which is pre-installed on the Tegra Note (I have an Advent Vega edition)

YouTube-movie of my problems: https://www.youtube.com/watch?v=f-T3R7E4s20

1. The browser-bar isn't functioning as a Google searchbar? Nothing happens when I type something

When I try another search-engine like Bing! my browser automatically stops working when trying to search for something

2. The browser-bar is allways flickering / refreshing / not going to the 100% and fully loads

3. Flash isn't incluced anymore in 4.4? But I think that's a 4.4 'feature' (which I think is crap)

So can I fix this with an .apk-file for flash, or isn't it going to work anymore on KitKat?

4. How can I make a local bookmark? Can't do it in the browser? Do I need a third party-app?

I haven't got root-acces and I'm running on the KitKat 4.4.2 Android-version, buildnumber KOT49H.16492_340.8117
[Nvidia Tegra Note 7] madasalizard:
Yes the Google search bar problem is really annoying.