yashsingh1/xdaforums huggingface dataset:
[Moto X Original Android Development] ecetim:
Quick question folks: on a 4.4 rooted phone, will I keep root if I do a factory restore? I presume so, but just wanted to make sure. Thanks!
[Moto X Original Android Development] :
so im on 4.4 , how do i downgrade, this is all so confusing
[Moto X Original Android Development] ManHands:
Yes, you'll keep root.
[Moto X Original Android Development] NightThyme:
Use RSD Lite to flash the 4.2.2 sbf firmware.
[Moto X Original Android Development] :
OK and then I root that and fix the r/w issue then upgrade to 4.4 and root that?
[Moto X Original Android Development] NightThyme:
yes, MotoWPNoMo requires root. So first you downgrade to 4.2.2, then you root with RockMyMoto then you disable write protect with MotoWPNoMo. Then you take the 4.4. OTA then you use SlapMyMoto to root 4.4.
[Moto X Original Android Development] :
OK then how can I flash custom rooms and recovery?, sorry for so many questions but I just want as much info as possible
[Moto X Original Android Development] NightThyme:
you can't flash a custom recovery or ROM if your bootloader is locked. And if your bootloader is unlocked/unlockable, you shouldn't be using SlapMyMoto to root.
[Moto X Original Android Development] mschumacher69:
Flash the post-camera OTA 4.2.2 SBF using this guide:

http://xdaforums.com/showthread.php?t=2446515
[Moto X Original Android Development] :
Damnit, well looks like I'll be getting a tmo version soon
[Moto X Original Android Development] mschumacher69:
Which carrier edition do u currently have??
[Moto X Original Android Development] :
I personally have the S4 but I bought my girlfriend the AT&T Moto X
[Moto X Original Android Development] mercado79:
Only if you create other ROM slots. I rather hold on to my internal storage space and so I simply flash over stock (no problems when flashing Eclipse or Stock ROMs). Make sure you make a Nandroid backup, of course.

Sent from my Moto X
[Moto X Original Android Development] Toys Samurai:
I just want to report back my adventure ... I finally decide to say WTF. It's just 40 bucks. I begged my wife to ask her friend in HK to ask her friend in China to pay for it for me. FYI, taobao does not link to your PayPal account -- it f*cking doesn't use PayPal at all. I tried to do it myself w/o asking my wife, but even though the site says it supports international VISA, none of my cards work. I thought my bank declined it because it's a transaction from China, but when I called them, none of them had received a transaction. It's Taobao declining me, not the bank -- Anyway, long story short. It F*CKING WORKS, period. I didn't even restore to the original firmware (I was root using SlapMyMoto's earlier method, which left me no bootloader.) I just backed up all my apps using Helium, and fastboot em unlock with the key that guy sent me. It then said Unlock completed! Wait to reboot. But then I got a "FAILED (status read failed (Too many links))", but it did no harm. My Moto X was rebooted, showed a warning saying an unlooked bootloader is unsafe blah blah blah. And my phone was wiped clean (just like it should be.)
[Moto X Original Android Development] mschumacher69:
Now I would flash back to 100% stock and flash TWRP and SuperSU to root the proper way on an unlocked bootloader.

You can also flash 4.4.2 (or take the 4.4.2 OTA after going back to stock and before you root) ;)
[Moto X Original Android Development] Toys Samurai:
I am still thinking whether I should flash TWRP or just RSD-lite back to the stock ROM. Does Android's remote wipe depend on the manufacturer's bootloader?
[Moto X Original Android Development] mschumacher69:
RSD Lite back to stock and then flash TWRP. I'm not sure about remote wipe by I don't see why it wouldn't work with TWRP.

Also, I think you can always re-install stock recovery and keep root after installing SuperSU with TWRP.
[Moto X Original Android Development] Toys Samurai:
I flashed TWRP and root. Now, how I can update to 4.4.2 w/o the stock recoery? Can I just flash using the following commands:

fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot oem config carrier vzw
fastboot oem fb_mode_clear

I got the above commands from http://xdaforums.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515, and removed the lines that removes motomaker customization and my userdata. Would that work? Did I miss anything that would erase my own data?
[Moto X Original Android Development] mschumacher69:
Maaaan I told u take the 4.4.2 OTA and then install TWRP and Root.

U can update to 4.4.2 using the method above but this takes u back to stock so u would have to re-flash TWRP and Root after u do it...
[Moto X Original Android Development] Toys Samurai:
Gotcha. Thanks!
[Moto X Original Android Development] TheDave1022:
If I used slap .5c and want to revert back to stock, what should i do? Is it the same process as using 1.0?
[Moto X Original Android Development] mschumacher69:
Yes, just flash the stock SBF using RSD Lite or fastboot...
[Moto X Original Android Development] TheDave1022:
Would I use 4.4 (current version), can I flash 4.4.2, or should I go back to 4.2.2?

Thanks
[Moto X Original Android Development] mschumacher69:
It depends on what you want to do.

If you don't want to root anymore and never plan to root again, you can flash 4.4.2 which cannot be rooted yet unless you manage to unlock your bootloader.

If you will root again after going back to stock, flash post-camera OTA 4.2.2 and follow the guide in the OP to end up on rooted 4.4.

If you will not root after going to stock but still plan to root in the future, flash 4.4 and don't take the 4.4.2 OTA.
[Moto X Original Android Development] theregkid:
I am confused by the instructions, I just want to make sure I do not brick my device.

I am on the latest 4.4 update.

I know I need to downgrade to 4.2.2

Could I use this method herehttp://www.android.gs/downgrade-restore-moto-x-stock-android-os/ to do so?

He explains using motopwn, then slap, then motopwn again. And Then he says to restore to 4.2.2

I am assuming the link I included would allow me to skip this? Or maybe it's a method that would result in a brick and I should do what op said?

I greatly appreciate and help.
[Moto X Original Android Development] ManHands:
By "latest 4.4 update," do you mean 4.4.2?
[Moto X Original Android Development] mschumacher69:
U don't have to use motowpnomo twice. Just use the method that u linked to downgrade to 4.2.2 post-camera ota, root with rockmymoto, run motowpnomo, restore back to stock post-camera ota 4.2.2 by following the method that u linked to again then start the slapmymoto process to end up on rooted 4.4.
[Moto X Original Android Development] jideay:
This may have been answered somewhere in these 169 pages, but I took the 4.4.2 OTA. How do I get rid of the slapmymoto root? I want a completely stock 4.4.2.
[Moto X Original Android Development] _litz:
Get the SBF and RSD-Lite, and flash the 4.4.2 full SBF ... it'll overwrite the system partition, and restore everything to "stock"

---------- Post added at 06:59 PM ---------- Previous post was at 06:56 PM ----------

Actually, you can do the following safely :

Downgrade via RSD to 4.2.2.

rockmymoto to gain root, then wpnomo

Downgrade via RSD to 4.2.2 again

slapmymoto to gain root, but DO NOT TAKE THE OTA ... just skip that step.

when slap's done, you'll have 4.2.2 rooted w/the write protection on /system removed.

This is the platform from which you then install the safestrap apk, and apply safestrap's 4.4.2 zip, to bring a locked bootloader X to 4.4.2 w/no write protection, and root.
[Moto X Original Android Development] redhonker:
Any link to safestrap instruction? Thanks
[Moto X Original Android Development] JGoN86:
Ok so I'm screwed I think... I was going through the slap my moto process and during so I took the 4.4 update via Ota. When I did I got to the final step and didn't have root and tried starting over but was never able to gain root. So if I follow this method http://www.android.gs/downgrade-restore-moto-x-stock-android-os/ I'm pretty much still screwed right., since I took the OTA
[Moto X Original Android Development] lowvolt1:
If you took 4.4 update your fine. If you took 4.4.2 update your screwed. But only if on AT&T or VZW.
[Moto X Original Android Development] JGoN86:
I'm on 4.4 att.. Do I need to follow the link in my previous post or can I use the moto x tool kit on this forum to downgrade and go back to 4.2.2 and start the process all over?
[Moto X Original Android Development] lowvolt1:
You can downgrade either way. I have always just used rsdlite. Have you already disabled write protection?
[Moto X Original Android Development] JGoN86:
No after my failed attempt I flash stock 4.4 via the tool kit and kept it stock
[Moto X Original Android Development] lowvolt1:
So did you ever run motowpnomo?
[Moto X Original Android Development] JGoN86:
Yes multiple times. What happened was after I took the 4.4 Ota my phone when into a bootloop it would reboot and reboot over and over and I got worried after 15 minutes (kind of long i know ) then I just use the toolkit to flash me back to 4.2.2 and none of the process were working so I felt I possibly broke something. The I just took the 4.4 Ota
[Moto X Original Android Development] lowvolt1:
Did you root 4.2.2 with rockmymoto?

Then run motowpnomo.

Then flash back to 4.2.2

Then root using slapmymoto.
[Moto X Original Android Development] hovax615@hotmail.com:
Yeah but at&t never received 4.4.2 yet so we're not screwed
[Moto X Original Android Development] ReadyMadeFire:
After rooting with SlapMyMoto, instead of taking the OTA to 4.4 could I use RSD Lite to flash 4.4 like I did 4.2.2?

Ok, I flashed 4.4 using RSD Lite. Ran through the last line of code from SlapMyMoto. On the last line (echo "/sdcard/local/tmp/install.sh" > /sys/kernel/uevent_helper) returns a permission denied. What is up with this? If I check for write protect, it returns a 0. Shouldn't I be able to write to system?
[Moto X Original Android Development] kg6zvp:
I don't see the download for the T-mobile one. I have gone to the sbf site and downloaded this update: "TMO_XT1053_4.2.2-13.9.0Q2.X-116-X-17-6_CFC" (which is the latest 4.2.2 I could find on the site) and it won't downgrade. The bootloader is locked and it will stay that way, so as to keep the warranty. Also, I removed the getvar line in the XML file. I have tried RSD Lite and manual modes of downgrading. What do I do?
[Moto X Original Android Development] mschumacher69:
If you took the 4.4.2 OTA, you can't downgrade anymore...

Moreover, there's no point in not unlocking your bootloader if you're going to root because rooting would also void your warranty. So you might as well unlock it and root the easy way ;)
[Moto X Original Android Development] JGoN86:
You're a god, IT WORKED!
[Moto X Original Android Development] _litz:
You flashed 4.4 with RSD Lite, which overwrites all the changes SlapMyMoto has made to /system in 4.2.2.

You need to sideload the 4.4 update instead of use RSD Lite.

Just go back to 4.2.2 w/RSD, run slapmymoto, and apply the update, not flash the SBF.
[Moto X Original Android Development] ReadyMadeFire:
Ok when I run SlapMyMoto in 4.2.2, on the first run, I get the message that it is executing step 3 and I need to apply the update. Should I reboot and run again and then apply the update? I read somewhere that this is showing up because of the MotoWPNoMo that I have used previously.
[Moto X Original Android Development] _litz:
When it's time to apply the update, you have two choices ....

1) wait for the OTA to download, then use the system to apply the update

2) download the OTA zip file, and apply it as a sideload (google for those instructions)

*or* ... if, let's say, your intention is to install safestrap and then 4.4.2, you can simply skip the OTA entirely, root 4.2.2, then install safestrap.
[Moto X Original Android Development] atomicspaceindian:
I am trying to work this with my AT&T Moto X. I have gotten to the part when you input "dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto", and it says "Please root using RockMyMoto, then remove write protection...". The issue is, I have already removed write protection, and have flashed back to 4.2.2.
[Moto X Original Android Development] lowvolt1:
Have you double checked and made sure write protection is disabled?

In the motowpnomo thread it will explain how to check this.
[Moto X Original Android Development] atomicspaceindian:
Yeah, I think youre the guy whos helping me on the other thread. Write protection isnt disabled, thats an issue im running into
[Moto X Original Android Development] erikwervo:
Anyone know if this is working with 4.4.2? Thanks
[Moto X Original Android Development] hovax615@hotmail.com:
You need to disable any firewall or security on your computer to get it going.

---------- Post added at 11:54 PM ---------- Previous post was at 11:52 PM ----------

No does not work with 4.4.2. Only 2 ways I know of is if you had root and accepted the ota and kept root but write protection is disabled or if you get the BL unlock code and unlock your BL
[Moto X Original Android Development] atomicspaceindian:
Ugh, i just went to stock 4.4.2... I need to back everything up again...

---------- Post added at 01:50 PM ---------- Previous post was at 01:04 PM ----------

I disabled all firewall, Defender, etc. No go. Is it because I am ussing windows 8.1?
[Moto X Original Android Development] lowvolt1:
I had no issues using windows 7.

If you are on 4.4.2 and currently not rooted and currently do not have write protection disabled. You are probably done.
[Moto X Original Android Development] atomicspaceindian:
derp, not 4.4.2, just 4.4. .2 hasnt come out yet for the AT&T variant.

I am on 4.2.2 w/ root. adb shell getprop ro.boot.write_protect still keeps returning 1 after the motowpnomo

Even with Firewall and windows defender disabled
[Moto X Original Android Development] lowvolt1:
I'm telling you. Use a different PC.

---------- Post added at 01:56 PM ---------- Previous post was at 01:55 PM ----------

Make sure your drivers are up to date.
[Moto X Original Android Development] atomicspaceindian:
All drivers, etc are up to date. I will setup my other PC later today. i am trying to run this in compatibility mode, will let know if it worked..
[Moto X Original Android Development] KidJoe:
You sure 4.4.2 isn't out for ATT X yet? See -> https://plus.google.com/102838570385793445288/posts/C333jZ1xLjq apparently it has started
[Moto X Original Android Development] atomicspaceindian:
Oh, didnt know, not going to upgrade...
[Moto X Original Android Development] hovax615@hotmail.com:
I don't know what's going on with yours but here's an instruction to disable the firewall http://windows.microsoft.com/en-us/windows-8/windows-firewall-from-start-to-finish . I was getting that error too also until I completely disabled the firewall but then again I was using my old laptop that has windows vista.
[Moto X Original Android Development] atomicspaceindian:
Actually the issue was Windows 8.1. I ran it in compatibility mode for Windows 7 and it worked!
[Moto X Original Android Development] atomicspaceindian:
Only with Windows 8... I actually installed it for Visual Studio 2013... a week later Microsoft released it for Windows 7... I have no way to go back :'(
[Moto X Original Android Development] mschumacher69:
LOL!
[Moto X Original Android Development] BrokenWall:
Used the ebay middleman, now have an unlocked bootloader for my AT&T Moto X, was totally worth the $44
[Moto X Original Android Development] JGoN86:
How did that work out for you? Mind sharing the info? Message me
[Moto X Original Android Development] crakedparrot:
Works great, read the thread
[Moto X Original Android Development] wctaylor79:
Over in the general section the is thread about Chinese middle man. Read it. It works. I skipped ebay all together. Sent directly through paypal.. $40. One day later (today) i have unlocked Verizon moto maker X. All the info is in that thread.
[Moto X Original Android Development] kpoverdorf:
Sooo... Where we currently stand is...

- If you have a Rooted AT&T Moto X using SlapMyMoto is not suggested to apply the 4.4.2 update because it can break root if not do worse. Correct?

Questions:

- Is there anything in sight that could preserve root in 4.4.2?

- If I was to accept the 4.4.2 update, are there any recommended steps that I should complete prior to applying to ensure a smooth update?

- Is anyone willing to trade me for an AT&T Dev Edition Moto X? lol :p​

I love the MotoX but I might love having root more... This is a bummer. Decisions decisions.
[Moto X Original Android Development] mschumacher69:
Once on 4.4.2, the only way to root is to unlock your bootloader, more info here:

http://xdaforums.com/moto-x/general/verizon-moto-maker-bootloader-unlock-t2680651
[Moto X Original Android Development] theregkid:
I'm with you there. I just got the option to update 4.4.2 but I don't want to risk breaking my device.

The update said it would fix problems with battery life so that may be worth it for me.

To unroot I guess I just rsd?

Anyone know of a quicker way to make the update safe without rsd?
[Moto X Original Android Development] kpoverdorf:
I think thats only for VZW. I'm on AT&T. Luckily I have not accepted the update yet.

Does anyone know anything about the following?

http://www.idroidspace.com/how-to-unlock-moto-x-bootloader-officially-all-carriers/

It says all carriers but there is no mention of AT&T. Does anyone know if this works for AT&T?
[Moto X Original Android Development] mschumacher69:
This works for ATT as well...

The official unlock method doesn't work for VZW, ATT and RW... For those 3, you'll have to purchase an unlock code from a 3rd party as per the thread that I linked you to earlier...
[Moto X Original Android Development] kpoverdorf:
Ahh ok. That Moto page is very misleading. Thanks. I will try that other method.
[Moto X Original Android Development] KidJoe:
Sort of... let me correct you (see RED in the quote above...)

As for your questions.

Keeping root isn't an issue with 4.4 to 4.4.2 update, its keeping write protection DISABLED if you have a locked bootloader. Unfortunately that is not possible.

If you want the OTA and don't care about root, see the options in this thread -> [FAQ] for Kit kat and How to prepare for it (All Carriers) while it was written for when 4.4 came out, the 5 options listed for returning to stock are still applicable.
[Moto X Original Android Development] kpoverdorf:
LOL you are too helpful today hah!

I am opting to use the bootloader unlock code from the other thread. You more than answered my questions today. I will return to stock using RSDlite, apply updates, unlock bootloader, root, flash stock recovery, be on my way.
[Moto X Original Android Development] drago10029:
Was on the last step thought I was done then this -__-

I have adb drivers confirmed installed correctly and all other ADB commands work properly, also my write protection check brings back a 0 so I know it's not WP. SDK is up to date.

Anyone got some answers? please!
[Moto X Original Android Development] KidJoe:
Wait. Your signature says UNLOCKED. So why not just root via the process for unlocked bootloaders -> http://xdaforums.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738

Or does your "unlocked" mean SIM unlocked?
[Moto X Original Android Development] drago10029:
You were right the second time, I copped a SIM Unlocked - Tmobile - fake dev edition one lol

and I got 4.4 root.

It turned out everything worked right the first time. I think what confused me and what's may have confused some people are some of the steps don't have any sort of UI confirmation. So when I , followed the commands and rooted on 4.4 the first time it didn't reboot (the bluetooth toggle didn't work) nor did I sew any root/su prompts.

So I went back to 4.2.2 and started over and again when I input the commands to finalize root on 4.4 no prompts or reboots again :/ So i decided to wait a few minutes and just reboot. then went to the market, installed supersu and root was installed! Just didn't get any type of confirmation.

Would never have known had I not just rebooted and checked.

Maybe this can help someone.
[Moto X Original Android Development] KidJoe:
T-mobile? Their XT1053 can unlock its bootloader (moto web site has codes). Yeah, it voids the warranty if its not the DEV Edition, but still... its sure easier to root :D
[Moto X Original Android Development] drago10029:
An XDA'ers pride says keep the warranty

Bear the road less traversed

and root that Son of a Gun!!

but seriously, I wanna keep my warranty. and I want a dev ed, I want my warranty and I want my custom moto. So Motorola made me do it the hard way :cool: #itstheprincipal
[Moto X Original Android Development] KidJoe:
I can totally respect wanting to keep the warranty. When I got my Dev Edition, unlocking its bootloader voided the warranty. I waited to unlock/root to make sure the phone had no issues, etc. I was nervous having spent so much money on the phone. Then 4.4. came out and no new root process, with no eta, so I bit the bullet. Lucky for me, it wasn't long after that, that moto reversed their decision, and unlocking the bootloader on the DEV Edition didn't void the warranty, and the warranty was re-instated on all dev editions who had previously unlocked.

I only got the dev edition because at the time, there was no moto maker for verizon yet, and it was the only way to get 32gig. Ok, I knew I always wanted to be able to root too, and that unlocked bootloader was the only way to guarantee that.
[Moto X Original Android Development] lucfig:
I have root on 4.4.2. I am thinking in unlocking the bootloader but I use Google Play movies frequently.

Do anyone knows if I will still be able to watch movies on the app?

Check this thread: http://xdaforums.com/showthread.php?t=2695995

Unlocked bootloader and DRM keys.

Enviado de meu XT1058 usando Tapatalk
[Moto X Original Android Development] drago10029:
yeah, fortunately for us sometimes companies care enough to change. glad you got what you needed & really don't like being that guy mouthing off in a development thread so i'll respect the rules & stop here! lol
[Moto X Original Android Development] Dark9781:
Google Play movies works fine on rooted devices. Been using it since my Atrix 4G. At one point it did not work with rooted devices, but Google fixed that a few years ago.

Sent from my Moto X.
[Moto X Original Android Development] lucfig:
Thanks, but

I know it works on rooted devices. I want to know if anyone with unlocked bootloader can rent movies at Google Play movies.

Enviado de meu XT1058 usando Tapatalk
[Moto X Original Android Development] Dark9781:
My bootloader is unlocked and I have no issues playing movies.

Sent from my Moto X.
[Moto X Original Android Development] krazzyvishal:
My Moto X came with KitKat pre-installed and it was Android 4.4.2. When I powered it up, there was still a 15 MB OTA update available which was meant only for India, Australia and New Zealand.

I have got the device only 2 days ago. My question is, is there any way to root this? I can't revert back to 4.2.2 as required by this method as I got KitKat pre-installed, or if I am wrong here, how can I get back to that?

Please suggest anyone. If any more details are needed, here is the about phone: http://i.imgur.com/0mgN32R.png

Goddamn I think this is the most difficult one to root! >_<
[Moto X Original Android Development] KidJoe:
The only way to root and disable write protection once you have 4.4.2 on your Moto X is to unlock the bootloader.

If you can't, or wont due to wanting to keep the warranty on a Non-Developer Edition, then you are stuck.