yashsingh1/xdaforums huggingface dataset:
[Moto X General] KidJoe:
If you have a locked bootloader, not that I know of. There is no root process for 4.4.2 with locked bootloader. And their likely wont be one as JCASE already posted he doesn't have time to look at root for 4.4.2. So unless another developer steps up, there won't be root for 4.4.2 anytime soon.

Yes, those with Dev Edition can still root and bypass write protection on 4.4.2 like before. (unlock bootloader, flash custom recovery, and install SuperSU via customer recovery).

---------- Post added at 09:29 AM ---------- Previous post was at 09:13 AM ----------

I can't speak to the SlapMyMoto part as I didn't use it because I have an unlocked bootloader on my Developer Edition VZW X...

BUT you definitely need to un-do that vzw entitlement trick for fee tethering (where you replaced the original APK with a hacked one). If the thread you followed to apply the hack had you MANUALLY replace the APK, then you should be able to look at those instructions and figure out how to undo. If you read THIS thread from the start, then the second part of Post #83 might also help you.

The OTA updates have a manifest file inside that includes a list of files and their check sums. It verifies every file on that list against those on your phone. If even one doesn't match, the OTA either fails, or puts you in a boot-loop trying to reboot and retry. This is why many suggest you get back to 100% stock before trying to accept an OTA update.

---------- Post added at 09:37 AM ---------- Previous post was at 09:29 AM ----------

I'm curious too as I have a friend who ended up getting two Moto Maker X's rather than Dev Editions due to a Moto mess up during those promotions. He's holding off upgrading to not lose root/WP Disable.

I wonder how those who say they still have WP Disabled on non-Dev Edition X after the 4.4.2 update have tested/verified WP is still disabled, and that they can still write to /system, its sub folders, etc.
[Moto X General] anotherfiz:
Has anyone tried this with Safestrap yet?

I was going to download the SBF, strip out the bootloader, and force load the 4.4.2 kernel / baseband in the stock slot, should take since they are moto signed right? Im running 4.4 on 4.2.2 BL, so i dont see why i could not run 4.4.2 also? What do ya'll think
[Moto X General] jideay:
Locked, rooted, un-writable... Bummer. If I hard reboot, I have to reset everything, If I do a soft reboot, everything stays intact.
[Moto X General] iifuzz:
im confused why some people are saying they are fine and some not!

What does it mean if you are un-writable?
[Moto X General] hehfahq:
I have the VZW Dev Edition unlocked, rooted, xposed fw with GB tweaks. Coming from a Galaxy S3 we would just flash a pre-rooted ota zip in TWRP and wipe our data to insure a nice clean install. Why is this not possible on a Moto Dev Edition?
[Moto X General] Mayze23:
I spoke too soon when I thought WP was disabled. I soft rebooted after I reinstalled xposed. Meh... as long ad I can run gravity box after a soft reboot I'm still happy.
[Moto X General] AaronCompNetSys:
OP [MENTION=1014155]a1exus[/MENTION], if this is true then you need to update first post to point it out. Here is a quote blob to get you started, take it if you think its useful. I'm not writing this from personal experience, just impressions from others, so I have no way of verifying it myself.

Non-dev users: If you have root currently, you can take on the OTA as long as the list of system files it checks have not been modified. (Ex, uninstall Xposed) You will retain root and the su binary.

Non-dev users: If you have write protection off currently, you will permanently loose it if you take on the 4.4.2 OTA. There is no going back at this time.

The only hope to my knowledge is a custom update that applies 4.4.2 without replacing recovery, which can be done but it is not easy yet.
[Moto X General] tu3218:
So I'm just holding out for the OTA, but is it confirmed that it's been released? Or is it still just the soak test? I'm completely stock on Verizon, non dev.
[Moto X General] vipergts450:
Same here... Are they doing a staged rollout?
[Moto X General] theshadow62:
cannot get past dead android..

"To get into stock recovery, you power down, then hold Volume Down + Power for about 3 seconds to get into fastboot/bootloader mode. Then you hit Volume Down to highlight recovery and then Volume Up to select recovery. Then if you have a stock recovery, you get the dead android with a red triangle coming out of its abdomen. Then you press Volume Down + Volume Up together and hold for about 5 seconds and then hit Power once to get into stock recovery."

I have downloaded the 4.4.2 update to my SD card and have followed the directions above several times but cannot get past the dead android with the red triangle. I press Volume Down + Volume Up together and hold for about 5 seconds and then hit Power but nothing ever happens. what am i doing wrong?

BTW I have a stock moto X, no modifications.
[Moto X General] tu3218:
No idea. Usually that's how it works. Not sure if the deleting data for the Google services works on this phone or not. I do that on my nexus 7 to help get the ota. Not sure if it really works or not.
[Moto X General] jjlangen:
The quote is wrong, you need to hold Volume Up and press power to get to recovery.
[Moto X General] somerandomname1:
Thanks for mentioning this, I didn't realize you could do this. Phone is almost back to normal now. Do you know if there's a way to change the dpi and survive a soft reboot along with xposed? Can't edit build.prop and the "App Settings" module goes app-by-app. I use that module to change Active Notifications to 320 so there's no issues, but I'm looking for a global way to change to 270 everywhere else. Just figured I'd ask if you know of anything since you're in a similar situation as I am.
[Moto X General] Mayze23:
AFAIK any module setting is applied after you soft reboot. I click the install/update framework button in xposed after each hard reboot. Then soft reboot.

I changed my nav bar size in gravity box. It sticks, along with all my other module settings after each soft reboot.
[Moto X General] theshadow62:
thanks jjlangen. that did it!!! update complete.
[Moto X General] Cozume:
Hmm, don't know what to tell you but that gets me into stock recovery every time on my locked, unrooted, stock Moto X with no modifications running 4.4.

I just did it again and it worked. Idk what to tell you why it works for me and not you.

---------- Post added at 08:03 PM ---------- Previous post was at 07:58 PM ----------

Both ways work for me, but your way is easier. I will ask OP to edit since your way is easier. Idk why both ways work for me and not you.
[Moto X General] iifuzz:
What is write protection for if we already have Root?
[Moto X General] AaronCompNetSys:
Write protection reverts changes to system on hard reboot.
[Moto X General] Cozume:
But if you have root, can't you make those changes in recovery and have them "stick"? I thought I read that somewhere. Someone was saying why the prefer to have write protection disabled because it prevents them from making any unintentional changes if they have to boot into recovery to make a change stick.
[Moto X General] AaronCompNetSys:
That may be the case for Dev users but us non Dev can't use custom recovery or unlock.
[Moto X General] Cozume:
I will try to find the post I am talking about. I believe the guy was talking about locked, rooted devices.
[Moto X General] easyxtarget:
Has anyone been able to see if the bug that prevented users from adding an APN is gone? Basically just put in a non-verizon SIM in and try adding a new APN setting.
[Moto X General] Cozume:
Here is the thread where I thought what nhizzat was saying is that write protection is disabled in recovery if you are rooted but locked:

Boot into Recovery
[Moto X General] flacco40:
4.2 .2 camera update

This question is kind of relevant but not, I'm on a locked bootloader Verizon Moto X on 4.2.2 camera update stock rooted. Can I accept the first 4.4.1 ota without affecting root or bricking the phone or does anyone know?

---------- Post added at 04:14 PM ---------- Previous post was at 04:09 PM ----------

I'm rooted through Jcases on the camera update4.2.2, I try the foresaid method to go into stock recovery but when I press volume up button it just reboots my phone. How can I fix?
[Moto X General] tekhna:
Just to clarify--locked and rooted, taking the OTA does in fact kill writing to the system, although root is retained?
[Moto X General] dkoon1987:
Hey guys... I am trying to prepare my device for OTA and am having troubles getting the stock recovery flashed. The command that I want to use is mfastboot flash recovery recovery.img, correct? I am doing this and it sends 'recovery', but when I go to boot into recovery I get Mr. Droid on his side with the red triangle. If I go back in and flash TWRP twrp works fine. Not sure where I am going wrong. Any advice?
[Moto X General] jideay:
I've read this thread several times and I don't think I understand how this will help make my phone writable...
[Moto X General] Cozume:
So just to clarify, disconnected from any power source including your computer, you boot into bootloader mode by holding Volume Down and Power together for about 3 seconds and then releasing. Then you scroll down to highlight Recovery by pressing Volume Down then you select Recovery by pressing Volume Up. Then you get the dead android with the red triangle. Then you hold Volume Up and press Power once to get into stock recovery.

---------- Post added at 10:44 PM ---------- Previous post was at 10:43 PM ----------

OK, good to know. I haven't rooted my locked Moto X yet.

---------- Post added at 10:45 PM ---------- Previous post was at 10:44 PM ----------

Some say it did, some say it didn't. Not sure why it would be different.

---------- Post added at 10:46 PM ---------- Previous post was at 10:45 PM ----------

Once you flash stock recovery, you get the dead android instead of going directly into recovery. Then at that screen you hold Volume Up and then press Power once to get into stock recovery. It is different for stock recovery and custom recovery.

So flash stock recovery again and then when you get the dead android hold Volume Up and then press Power once to get into stock recovery
[Moto X General] Rebel908:
Are you on a Verizon DE? I would imagine that it would be fine to flash the SBF manually without wiping UserData, and then simply updating and then reflashing TWRP after everything is said and done.
[Moto X General] bigv5150:
I think why you are getting people saying they have write protection off is because you can make system changes. They just haven't figured out yet that when they reboot the changes don't stick. So basically you can run exposed and the entitlement hack until reboot then you just have to restart exposed every time you turn the phone off and on or hard reboot.
[Moto X General] Flexia32:
So if I ever want to root I need to do it before I get 4.4.2? It may make my root decision easier
[Moto X General] dkoon1987:
Ahhhh, so I had successfully flashed the stock recovery. Thank you, sir! Sorry for the noob question!
[Moto X General] Mr. Orange 645:
The Droid with the red triangle IS the stock recovery. This has actually been discussed in several threads including this one. When you get to the droid and red triangle, press and hold volume up. Then while still holding volume up, press and release the power button. That brings up the stock recovery menu.
[Moto X General] lowvolt1:
How were you able to keep R/W on locked boot loader?
[Moto X General] aFancyTickler:
Nvm i lossed it. no R/W access . welp that sucks D;
[Moto X General] Cozume:
yes. then when the sbf firmware for 4.4.2 is out, you can selectively flash parts of 4.4.2 without flashing the 4.4.2 bootloader and keep root and keep write protection disabled.
[Moto X General] KidJoe:
So....

those with locked bootloader who rooted and used MotoWPNoMo that took OTA, *kept root, but it was useless because they lost the Write access (aka write protect disable) that MotoWPNoMo gave them. Losing write access means any changes made to /system and the like are not retained after reboot.

And those with unlocked bootloader who take OTA update, retain root and R/W abilities.. * (and if they loose it, they can re-root anyway)
[Moto X General] T-Keith:
Can anyone tell me if app opps is gone?
[Moto X General] Flexia32:
So I should root and then NOT flash the OTA if I want to keep root? I was hoping to get the update and keep root.
[Moto X General] Cozume:
That is correct if you have an unlockable bootloader. Then when the 4.4.2 OTA comes out, you freeze MotorolaOTA using an app, I am going to use Titanium B/U paid version, but I am sure you can find a free app.

You keep root but lose the ability to disable write protection.
[Moto X General] edthesped:
What specific files need to be left out to allow a downgrade?
[Moto X General] triton302:
So just for clarification... those with the DE can install 4.4.2, reroot using the original method and everything is good to go?

Also, because I'm rooted means I'm not getting the OTA, correct?
[Moto X General] Teksu:
1 flash xposed disabler (also disable native tether if you didnt use the xposed method)

2 flash stock bootloader

3 flash 442 ota

4 see that you are still rooted

5 install xposed "framework"

6 ???

7 Profit!!!

If you do return to stock, and take the ota while stock you can just root again with TWRP, this is correct.
[Moto X General] Cozume:
All that I know about this I learned here:

Page 150 of Slap My Moto Thread

And here:

Page 15 of WARNING Thread
[Moto X General] edthesped:
I'll be the first to try it when the full sbf comes out untilthe it's 4.4 for me.
[Moto X General] Cozume:
That's what I am going to do with my locked bootloader 4.4 Moto X once I root it - freeze MotorolaOTA and wait for the sbf of 4.4.2.
[Moto X General] edthesped:
Then good luck to the both of us!
[Moto X General] Flexia32:
Lets hope some one makes SBF and doesn't take as long as Verizon does to push updates
[Moto X General] _litz:
Has anyone verified the bootloader version after this update is applied?

I've looked through the update script (and this IS an update *script*, not a SBF style flash partition images setup) and don't see it ...

for those interested, here's the script : http://pastebin.com/VDgUF5uQ

Edit :

I think this is the boot image patch ...

ui_print("Patching boot image...");
assert(apply_patch("EMMC:boot:10485760:9b3cd4c78eff46c43b1a27b040e91a207847e52e:10485760:cb9b595490a90382d06dfd58b4297e9051fdc4c9",
"-", cb9b595490a90382d06dfd58b4297e9051fdc4c9, 10485760,
9b3cd4c78eff46c43b1a27b040e91a207847e52e, package_extract_file("patch/boot.img.p")));

And this is the partition table patch ...

ui_print("Updating gpt.bin...");
assert(package_extract_file("gpt.bin", "/tmp/gpt.bin"),
motorola.update_gpt("/tmp/gpt.bin"),
delete("/tmp/gpt.bin"));

In theory, removing those two items from the updater script should (again, in theory) update the system, and not change either bootloader OR the partition mapping.
[Moto X General] tejaskary:
I am on locked bootlader and rooted on non de verizon moto x ....If we have to flash system.IMG from the SBF, how will we not lose root?
[Moto X General] _litz:
Has anyone tried editing the updater-script file within the .zip, and removing the lines that update boot.img and gpt.bin?

That should prevent a 4.4 upgrade to 4.4.2 from changing the bootloader/partition map ... in theory preserving the ability to downgrade, and rw /system ...

(or does the moto zip sign prevent changing the contents of the zip file?)
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] egomaster:
I am rooted running Stock ish rom v1 and this morning woke up to system update downloaded, touch to install. Is this the 4.4 kit kat upgrade? Any way to get rid of the prompt. I plan on updating to stock ish rom v6. Will this remove the prompt?
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] jzebrahockey:
Press and hold down on notification. Click on app info and uncheck notifications.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] egomaster:
Thank you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zhangla:
Hi All,

I attempted to flash my I747 to the latest 4.3 ROMs (I first flashed to I747UCUEMJB modem and bootloader) from 4.2.2 ROM. However, no matter which 4.3 ROM I use, I am always asked to enter PIN or password used to encrypt memory after the new ROM boots up. Some ROMs will show "Unfortunately the UI has stopped working", but others will simply ask me to enter PIN or password over and over and over. It does not matter what I enter, it just won't work.

Does anyone else experience this issue?

I think this is caused by my company email requiring encryption on my phone in my 4.2.2 ROM. However, I thought factory reset and data wipe will erase all encryption, or not?

Can anyone help me? Seems the only way to unbrick my phone is to use ODIN to flash stock 4.3 ROM. However, there is no 4.3 stock firmware to download... Only custom ROMs out there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Are you doing a wipe of the cache, data, Dalvik, and system before installing a new ROM? Try a KK ROM instead of a 4.3 ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zhangla:
Yes I wipe cache, data, system, dalvik all of them before each flash.

Can you please point me to "KK ROM"? What exactly is a KK ROM? I have tried many 4.3 ROMS, and all of them will bring me back to the "Enter your PIN or password" screen on the initial boot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Try something like Validus release version 4.3. It is based on 4.4.2 KTOH.

I also recommend using the latest CWM. I had problems using TWRP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MaxGQC:
Hi Xda

I had a problem with my phone due to a invalid bootloader installed.

I took my phone to a repair shop for a Jtag service which unbricked it (yay!) but now I have no IMEI.

In phone info it says: baseband version: unknown

Is there a way to restore it ? I have a TWRP backup from before the JTag and bootloader installation

It's a Rogers phone

Thanks for help !
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MaxGQC:
Resolved by installing stock firmware from sammobile
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] redpilleatr:
tread lightly here

Be careful about asking to repair your IMEI number around here. The moderator of this forum ("zelendel") believes that it is illegal to fix IMEI numbers.

He wrong (analysis here), but of course it's his opinion (and false facts) that will get a thread closed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shortydoggg:
I think the mod feels that it is not illegal to fix your broken IMEI. It is illegal to change or spoof an IMEI. The moderator chooses to avoid the subject because where you have one who wants to fix, you will have another who wants to change.

In other words, a thread whose purpose is to fix a broken IMEI is likely going to be abused illegally, which is why the moderator chooses to avoid the subject altogether.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theramsey3:
Baseband = modem, modem reads imei, try to install a modem via custom recovery if you're on AT&T or just feel like it. or if you have an I747M use Odin to flash a stock firmware of the appropriate bootloader (if you're on 4.3 use 4.3 for your carrier)

I put the AT&T part in there incase other people use the search function and find your thread.

Sent from my SAMSUNG-SGH-I747 running S3Rx MJ2 bootloader MJB modem and it is smooth
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] redpilleatr:
No, actually the mod jailed a thread that did not state any reason whatsoever behind setting an IMEI number. Be it repair, or privacy.

Nonsense. We are not in Latvia, or the UK, where it actually is illegal, because IMEI blacklisting is the only tool they have against phone theft in those countries. XDA claims California as its legal jurisdiction and servers are on US soil.

Changing is "fixing". You must change it to fix it.

Someone's underlying reason for changing the number setting could be to get back to the original number, or to get around their phone service being locked to an IMEI, or privacy. But intent is moot, because there is no such law to speak of in the US. We have people making up phantom laws, and moderators being fooled into believing it because they read it in google.

The thread I pointed to made a fool of the mod. The reason the thread was closed was to stop the embarrassment. Normally if someone wants to claim that something is illegal, there is a prohibition on the Cornell law site that they can point to. The absence of a prohibition means something is legal, so normally the opposition can't show proof that something is legal. But in this case, they can, because proposals for a prohibition were raised, and then dropped. There is proof that senate bill 3186 was dropped. The creator of that bill is making another attempt, but that's all it is.. an attempt. Yet another proposal just rotting away. Senators tend not to propose prohibitions that already exist.

After s.3186 died, they tried to recycle it in s.1070. Senate bill 1070 has been sitting idle for 3/4 of a year now.

---------- Post added at 05:07 PM ---------- Previous post was at 04:30 PM ----------

I should point out that people might want to write to their Congress person and ask them to kill senate bill 1070 (even though it looks like it's going nowhere).

At the moment, some phone providers in the US lock service plans to IMEI number, creating a need to be able to change IMEI numbers - not just for repair, but to use the phone service that's paid for. s.1070 seems to only allow changing IMEIs for "repair". And forget about privacy.. s.1070 makes no exception for those who need privacy, not to mention the environmental impact and cost of buying a new phone every time someone wants a different IMEI.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shortydoggg:
OK, redpilleatr

When I said that it is illegal to change or spoof an IMEI, I meant the moderator felt that way. I didn't say I did. I also read the bill. I see that I didn't make that clear.

That's subjective to opinion.

Since a possible repair was not stated, and the possibility of changing existed, then yes, I see why he closed it. Not that it was necessarily the best option.

and finally,

That might be true because at least one thread that hard to miss, showing how to inject (or fix or change) the IMEI is still open, including links to the needed files, but no talk of it or tools were allowed in that other thread.

That's all I'm going to post here in this thread, because we'll be going back and forth forever. But you did make some very good points, despite forcing me to defend myself here. And yes, those related threads "are" very interesting.