yashsingh1/xdaforums huggingface dataset:
[Moto X Original Android Development] sfetaz:
When I did this method I figured out that when it comes to triggering bluetooth, it needs to be triggered when bluetooth is on. You trigger bluetooth off to do the reboot. If bluetooth is already off, then the phone will reboot automatically without having to trigger it. Just to let anyone know in case they are confused, I figured it out by accident, but had no trouble rooting.
[Moto X Original Android Development] bongostl:
figured it out!
[Moto X Original Android Development] jimmiet:
I used this thread HERE to help me out using Windows and the Telnet parts.
[Moto X Original Android Development] jimmiet:
This is the newest version and MIGHT not be another one.
[Moto X Original Android Development] SubliminalME:
This worked great for me, and thanks JCase! Although, I must admit, it took me 2 tries. There's a lot going on here for the layman. For example, I had to grab the 4.2.2 files from the factory images to push them, which wasn't mentioned, although in retrospect was obvious.

But thanks...ads are gone and battery bar is up and running. :)
[Moto X Original Android Development] jcase:
This is not correct. Triggering bluetooth isnt actually needed, but in some cases will speed up the reboot. We are writing to uevent_helper, and use that to execute scripts as root. uevent helper executes them on each hotplug event, which is generally every few seconds. Bluetooth toggling also causes a hotplug event. I only advise people to do it because I don't want to deal with people saying "omg i waited 30seconds and it didnt reboot)". Most of the time a hotplug event will occur every few seconds.
[Moto X Original Android Development] auTONYmous:
Yah, I just tried it for the first time, and it worked first try. In my case, my screen was off whenever it was time to trigger uevent_helper, and simply turning on the screen and unlocking was enough to trigger reboot.

Thanks for this amazing piece of engineering!
[Moto X Original Android Development] grifforama:
I have a question regarding root, and busybox, and system folders.

In order to be able to use an app called GSAM Battery Monitor (to enable me to analyse some wakelocks), I've been told to drop an apk on system/priv-app

I've tried copying the apk to this folder numerous times, but it keeps failing. I am rooted.

It also recommends installing busybox, which I've tried, but that keeps failing also.

As I'm rooted, shouldn't I have unfettered access to /system ?
[Moto X Original Android Development] eyc:
I think (and I am sure I'll be corrected if I'm wrong) you need to disable write protection first by booting into recovery. To do so, turn the phone off, then press and hold power and vol+down at the same time. Release after 3 seconds. Click down to highlight recovery, and up to select it. You've now booted into recovery. Give that a shot.
[Moto X Original Android Development] grifforama:
That did it.

Now if I could get WPNOMO to work.....
[Moto X Original Android Development] bongostl:
I have an unbranded, unlocked xt1058.... any clue which firmware I should use from here to return to stock? http://sbf.droid-developers.org/ghost/list.php
[Moto X Original Android Development] lowvolt1:
What issue are you having?

via my slapped KIT KAT moto X
[Moto X Original Android Development] juancaperez2000:
just a quick question im already rooted using slap my phone, my question is what could be happen if i select factory reset
[Moto X Original Android Development] mercado79:
I haven't tried it but I did see that there's an Xposed Framework module available that apparently will make all battery stats apps compatible with Kit Kat (without moving anything into /system. It's called Enable Battery_Stats for KitKat (very creative name, I know).

Side note, I'm kind of blown away by all the available modules for Xposed Framework. So very cool. And it's not making my phone lag like it did on 4.2.2.

Link to the official thread in case anyone's interested.

http://xdaforums.com/showthread.php?t=1574401

Oh, last question, does anyone know if enabling a module in requires a standard reboot or a recovery (write protection off) reboot? I've been doing the latter just in case, but I'm not certain if anything actually needs to write to /system.

Sorry for the off-topic post!
[Moto X Original Android Development] jra89027:
root

i am running 4.4 stock, i accidently deleted pictues off my phone via gallery app. only way to fix it seems to root and use an app like diskdigger. this tutorial is so confusing though. i know you eventually revert to 4.2.2, would that erase any potentiall i may have to recover the images? is it possible at all , that there might be a different root message sometime soon
[Moto X Original Android Development] mattyv316:
Is there a way to get this to work with a T-Mobile version? I have successfully unlocked the bootloader, but searching for a root method that will work w/ 4.4. I just received a 32GB Moto Maker, T-Mobile version. Will this work, or does a method exist yet for this scenario?
[Moto X Original Android Development] bliu:
Thanks to [MENTION=2376614]jcase[/MENTION] for this root method - it's been running well so far. Something I'm still confused about - is there anything we're 'missing' using the 4.2.2 recovery and boot on 4.4 ROM? If we have root and also WP off (using WPnomo), will we break root (or patch a vulnerability) by flashing the 4.4 recovery/boot images? I guess I'm trying to understand why we needed to downgrade those two parts and whether having WP off changes anything.

Thanks!
[Moto X Original Android Development] d14gvn:
Can I use slapmymoto to get root on 4.2.2 and just keep with that version?
[Moto X Original Android Development] diehardbattery:
I don't understand why this is needed? I was able to install GSAM with no problems and appears to be working fine.

Speaking of battery, I'm trying to pin down an issue with Android OS using an abnormal amount of CPU time. I have location services set to device only and it does not matter if I'm on WiFi or 4g. I've had to fully charge twice today.... Top screenshot is current from last charge. The bottom one is from before the first charge...

UPDATE: I think I found the issue. Either the SuperSU binaries updated and didn't go fully through or did not update at all (I can't remember if it initially asked to update). I ran the cleanup tool within the app, uninstalled and reinstalled. It then prompted me to update, but kept failing. Using grifforama's GSAM post as a reference I booted into recovery and appempted the update again. This time it went through. I rebooted again and am seeing much more "normal" stats and the battery doesn't seem to be draining anymore.
[Moto X Original Android Development] forumsid987:
Great question! I'd really like to be able to have a normal recovery even at the cost of writing to the system. This is why I'm still at 4.2.

Is there any way to do this??
[Moto X Original Android Development] lowvolt1:
No. But you could use RockMyMoto on 4.2.2

via my slapped KIT KAT moto X
[Moto X Original Android Development] enjoimadcow:
kinda scared

I just got my moto x. I really wanna root it, but am kinda afraid. How hard is this to mess up?
[Moto X Original Android Development] MaddHatt3r:
Its not difficult to do this, you just need to make sure all your stuff is working before you start. Fastboot, adb, telnet. If you don't have any of those working you will run into a wall in the middle of the process.

Sent from my XT1060
[Moto X Original Android Development] enjoimadcow:
I have telnet installed in my command prompt and i have adb installed also. I am not sure what you mean by fastboot.
[Moto X Original Android Development] GandalfTehGray:
You also need the latest version of RSD lite, the drivers for the Moto X, and the sbf files. Do you have prior experience with ADB? It is a simple process if you have all your files in the correct places, everything up to date, and can read.
[Moto X Original Android Development] lowvolt1:
Fastboot is the mode you put the phone in for some of the steps.

via my slapped KIT KAT moto X
[Moto X Original Android Development] enjoimadcow:
I've ran a few push commands for my aria back in the day but nothing too much more than that.

---------- Post added at 12:44 AM ---------- Previous post was at 12:40 AM ----------

Wait I'm confused. Where does the instructions say I need RSD lite?
[Moto X Original Android Development] MaddHatt3r:
That's what you use to get back to the 4.2.2 stock system

Sent from my XT1060
[Moto X Original Android Development] enjoimadcow:
ahhhh makes sense.:good:

---------- Post added at 01:23 AM ---------- Previous post was at 01:07 AM ----------

I guess my next question is about that. Is there a specific place I have to put them? Or can I cd and then run a adb command in that directory?
[Moto X Original Android Development] mercado79:
You can also just use the Moto X toolkit to install drivers, return to stock, etc. Easy as pie.

As for all the files you need to push or flash via Fastboot, just make sure you have them in the same directory as fastboot.exe and adb.exe. This is assuming you haven't added these to your system path (if you don't know what I mean, ignore this).

Lastly Fastboot is simply the bootloader mode. You can reach it by booting while holding volume down and power or via the "adb reboot bootloader" command.

Good luck!

Sent from my Moto X
[Moto X Original Android Development] goose71:
Bootloader

Has anyone answered this question? Are we stuck with the 4.2.2 bootloader on the 4.4 system? How does that affect the phone/system?
[Moto X Original Android Development] anirudh412:
So if I am on 4.2.2 (.54) rooted with rockmymoto, do I have to reflash 4.2.2 to get to stock, or can I just go ahead from step 2 onwards?
[Moto X Original Android Development] goose71:
After it reboot's on it's own allow it to sit undisturbed for 1-2 minutes, then install SuperSu[/QUOTE]

Ok so I've done everything on this post and when I install supersu and open it, it tells me that there's no su binary installed. Did I miss something? I still don't have root...:confused:
[Moto X Original Android Development] Fadelight:
I am having an issue with Impactor... searching turned up a couple of suggestions, but nothing that worked for me.

Step 1) "# start telnetd as system on port 2222"

It appears to go through all of the steps, I see a "Delivering payload" and black box on my phone, Impactor ends on the box where I started, No errors.

Step 2) telnet 192.168.1.68 2222

Looks idential to results from step 1. Impactor cycles through, phone says "Delivering payload", Impactor returns an error "Link failed file exists".

Phone -

Fresh install, 4.2.2 139.15.1

ADB is enabled

Install from unknown sources is enabled

Connected to same wifi network as computer

Computer - Telnet is enabled (client and server both)

Wifi - AP Isolation is OFF. (DD-WRT)

What am I missing / doing wrong?

EDIT: Holy crap, I am a complete moron when I get too tired. Disregard this whole insanely stupid line of questioning, please. (Or mods/admin can just delete it.)
[Moto X Original Android Development] jcase:
Ill be updating slap my moto when time allows, to keep recovery and the 4.4 boot loaders. My only warning is, if you are on hte 4.2.2 bootloaders, and 4.4 rom, dont take any future OTAs without returning to stock
[Moto X Original Android Development] mercado79:
Ok so I've done everything on this post and when I install supersu and open it, it tells me that there's no su binary installed. Did I miss something? I still don't have root...:confused:[/QUOTE]

possibly. try rebooting into recovery (write protection mode disabled) and then install supersu again. if you get the same message, then you might need to start all over again. as in all the way back to stock 4.2.2. bummer, i know.
[Moto X Original Android Development] emerica243:
So im confused with Step 1. The thread is for gaining root on 4.4. However step 1 says we need to start with a stock RSDed phone of 4.2.2(camera update). What if our phone came shipped from motorola WITH 4.4 already on it? How do we downgrade RSD flash to 4.2.2?
[Moto X Original Android Development] danman421:
I am in need of some help. This may not be the right place but if not, I apologize. I have plenty of experience rooting Android, I have had about 6 or 7 of them, all rooted. I am having a hell of a time getting ADB to work with the Moto X. I purchased one yesterday off CL (its new), it was still running 4.2.2 so I took the OTA to 4.4 and did nothing before that. Now I cannot get ADB to recognize the phone at all. I have tried manually installing the drivers, using the Toolkit, etc. I am putting USB debugging on and connecting as a media device. Any help?
[Moto X Original Android Development] :
Have you installed Motorola Device Manager? Also, is your phone unlocked when you connect it, so you can accept the security prompt?
[Moto X Original Android Development] danman421:
Yes and yes but thank you for the help.
[Moto X Original Android Development] MaddHatt3r:
What kind of feedback are you getting when you issue a command such as adb devices?

Sent from my XT1060
[Moto X Original Android Development] goose71:
Step 4)

After the device has fully rebooted, we need to restore the recovery from the 4.2.2 camera update firmware using fastboot:

adb reboot bootloader

Wait for the bootlaoder screen to appear

fastboot flash recovery recovery.img
fastboot reboot

Once the device has rebooted, go ahead and take the OTA, once 4.4 is up and running continue.

A little confused here. When I finish step 3, telnet tells me to "attempt to apply the 4.4 ota", but in step 4 it says we need to restore the recovery from 4.2.2 and at the end it says to take the 4.4 ota. What gives?
[Moto X Original Android Development] danman421:
If it helps anyone to diagnose my problem; in the device manager I have "XT1060" under "Portable Devices" and I do not see any "ADB Device". I have installed, uninstalled and reinstalled the Motorola Device manager several times. Posts like this typically really annoy me in threads like these but I do not know where to go and I think something is legitimately wrong as I am not a noob asking how to install SDK or something like that.

There is nothing listed when I type adb devices. Here is my output:

"C:\Android\sdk\platform-tools>adb devices

List of devices attached"
[Moto X Original Android Development] stillthisguy:
Make sure you are using a USB 2.0 port and try toggling between MTP and PTP. Settings>Storage>Menu/USB computer connection.
[Moto X Original Android Development] danman421:
I do not understand but that worked. I toggled FROM MPT to PTP, the phone asked me if I wanted to allow the computer to use USB debugging and I hit yes then it worked! Thank you for your help and I hope this helps someone in the future!
[Moto X Original Android Development] mx828:
Also the easiest thing anyone without prior experience can do is simply install the android SDK, copy any files they need into the platform-tools folder, and always run terminal as admin for whatever reason. Those two steps alone can prevent alot of errors during install.
[Moto X Original Android Development] eyc:
Look at posts #123 and onward, which include my posts (and answers) concerning the same question.
[Moto X Original Android Development] emerica243:
Eyc, i know how to flash the rsd lite images. But i thought you couldnt DOWNGRADE because to a older bootloader? Aka going from 4.4 to 4.2.2 via rsdlite
[Moto X Original Android Development] shane1:
normally you cant but moto gave us a gift so jcase could enable us to root
[Moto X Original Android Development] lowvolt1:
I was on 4.4 and downgraded to 4.2.2 to gain root on 4.4.

Just download the XML delete the getvar line and go for it.

via my slapped KIT KAT moto X
[Moto X Original Android Development] icase81:
Hmm... I followed the instructions, but before I could toggle bluetooth, the phone rebooted on both rec.sh and install.sh. Theres also no su binary and SuperSU won't install it (obviously).
[Moto X Original Android Development] lowvolt1:
Toggling Bluetooth isn't necessary. I had to do this process a few times in order to make it work. Some people had luck starting over at step 6.

via my slapped KIT KAT moto X
[Moto X Original Android Development] anirudh412:
any idea which lines are those in the XML file? I remember reading it somewhere, but cannot seem to find it
[Moto X Original Android Development] kolyan:
+1

wondering is this method is for tmobile as well ?
[Moto X Original Android Development] goose71:
[MENTION=1800033]anirudh412[/MENTION]: "any idea which lines are those in the XML file? I remember reading it somewhere, but cannot seem to find it"

Step #4 of this post: http://xdaforums.com/showpost.php?p=45634726&postcount=1
[Moto X Original Android Development] jcase:
I will update slap my moto as soon as time allows to work with devices who have no write protection.
[Moto X Original Android Development] anirudh412:
Not really. Deleting the getvar line just ensures that you can successfully flash the firmware. It still deletes everything.
[Moto X Original Android Development] goose71:
correct, I didn't read the entire post and just saw where you asked about deleting lines and automatically my brain went to that post. :o
[Moto X Original Android Development] quickstang:
I got the cyber codes for $150 off & I'll be buying a tmo version soon. I've been reading this thread to get an idea what I'm facing for unrooting. I'll be coming from the Galaxy Nexus so it's all new to me. I could pretty much unlock & root in my sleep however this looks like more of a challenge.

I would like to see down the road this possibly integrated in a toolkit or maybe even a video.

I watched qbking77s video for unlocking & then this will be next. Well... As soon as I cancel Verizon & customize the X. :)

I'll miss the Nexus & almost got an N5, but I've heard good things on this phone so I'll take the plunge & hopefully not regret it.
[Moto X Original Android Development] mattyv316:
I have been digging around for a while and found it was much easier than I thought. This method is not for my scenario.

If you have/get a t-Mobile version and unlock your bootloader, just use this thread:

[GUIDE] 4.4 Custom-ROM *LIKE* Experience

If you are on the 4.4 build, and are unlocked, I just had to flash TWRP (twrp-2.6.3.1-ghost-4.4.img) and install/flash SuperSU.

That is all I did and I have root and recovery. Doing much better.

Now my issue is finding a ROM that is 4.4 based. The CM and AOKP nightlies are still 4.3
[Moto X Original Android Development] anirudh412:
All you guys who are having errors after step 4, just let the phone sit for a few hours. I know it sounds wonky, but I had the nab error and even jumping to step 6 didnt work. I installed SuperSu and Root checker and confirmed I did not have root access. Annoyed with the process :D I just left my phone sitting for a few hours. I come back redo step 5 (even though I had the nab error before) and voila! Everything proceeded smoothly.
[Moto X Original Android Development] Sharkeyd:
The method that worked for me after several failed attempts was to let the phone sit for 5 minutes after every reboot. When I did that everything went smoothly.
[Moto X Original Android Development] redhonker:
Hi,

I just got my device and it's on 4.2.2.

Step 1. mentioned "You need to get the camera update from http://sbf.droid-developers.org/ghost/list.php and flashing back to it. You must be 100% stock before continuing.". Is there any action to do withe phone or just download the file?

Step 4. Is this flashing back to 4.2.2 and then update via OTA to 4.4?

Since my device is still on 4.2.2, what would be best path?

Or is the below possible?

1. Root with RockMyMoto

2. Run MotoWpNoMo. This remove the write protection on /system

3. Install SuperSU Pro and turn on survive mode

4. Upgrade OTA

5. Since there is WP, SuperSU will recover after the reboot.

Thanks
[Moto X Original Android Development] mpetruzz:
I took the ota update and would like to downgrade in order to get root back.

A bunch of thongs I've read state that Motorola said once you took the ota for kitkat you couldn't downgrade.

Can I rsd back to the camera ota or am I truly stuck??
[Moto X Original Android Development] hecantbreathe:
The first step is to go back to the camera update.
[Moto X Original Android Development] redhonker:
I have build 13.9.0Q2.X-116-X-17-51. Is this the version after the camera update?

I guess my confusion is whether I can skip step 1, if it's to downgrade to 4.2.2, which is where I am right now.

Thanks
[Moto X Original Android Development] somerandomname1:
The steps are in the OP.
[Moto X Original Android Development] redhonker:
OP link has 17-54. http://sbfdownload.droid-developers..._4.2.2-13.9.0Q2.X-116-X-17-54_CFC_1FF.xml.zip

I have version 13.9.0Q2.X-116-X-17-51.

What should I do here?

1. Download and flash to 17-54 from 17-51?

2. first OTA update to 4.4, and then start at step 1

3. Start at step 2 since I am at 4.2.2 (a version that's older than camera patch)?

4. Other way?

Thanks
[Moto X Original Android Development] somerandomname1:
You have to be on the camera update just like the OP says.
[Moto X Original Android Development] evandena:
I agree, without your question and answer I would likely have gone on.

Thanks for asking, and thanks to the person who answered.
[Moto X Original Android Development] zgroten:
Will this method work with the upcoming Sprint update, or will changes need to be made?
[Moto X Original Android Development] redhonker:
OK. Which one of the following should I do?

1. Download and flash to 17-54 from 17-51?

2. first OTA update to 4.4, and then start at step 1

Thanks
[Moto X Original Android Development] scsi_2k:
Can this be used for thr Moto X T-mobile version?
[Moto X Original Android Development] lowvolt1:
What are you on now?

via my slapped KIT KAT moto X
[Moto X Original Android Development] redhonker:
17-51, pre-camera-patch.

It can be rooted by PwnMyMoto.
[Moto X Original Android Development] lowvolt1:
If you want 4.4 and root. You need to take the camera update. I believe in order to do that you need to be unrooted. Once on 4.2.2 camera update. Start at step 2

via my slapped KIT KAT moto X
[Moto X Original Android Development] redhonker:
Is there an way to un-root? I am thinking of root on 4.2.2-51 and wait for jcase to wrap this one up. Ideally, I'd want to get to 54 if I can keep root. By the name, I assume the patch improve the camera which I will use a lot.

Thanks!
[Moto X Original Android Development] lowvolt1:
I'm assuming your not on Verizon. Your numbers don't mean much to me. I know things as 4.2.2 before camera update, after camera update and 4.4. Lol.

I believe if you use rsdlite and flash the XML for the version your on you will lose root. I am however unclear if you would receive OTAs in stages. Ie: 4.2.2 camera update then 4.4. Or if it would just update you to 4.4. Maybe someone could chime in on that. I would however think that even if you went straight to 4.4 you could sbf to 4.2.2 and then start slapmymoto at step 2.

via my slapped KIT KAT moto X
[Moto X Original Android Development] redhonker:
Yeah, I am on AT&T

I guess my best bet is to remain on 4.2.2 before camera update since it needs minimal efforts. Then wait for jcase to wrap this one up.

Then maybe I can try root keeper before trying jacase's new method. Does anyone if the below will brick the phone? If it ends in boot loop, any way to recover?

Thanks

1. Root

2. Run MotoWpNoMo to get rid of WP

3. Install a Root Keeper, temp de-root

4. OTA Update

5. Run Root Keeper to restore root.
[Moto X Original Android Development] lowvolt1:
Okay. There are multiple threads that will answer this in detail. I will to sum it up.

If you root and run motowpnomo jcases 4.4 root method slapmymoto won't work right now. Also if you root on 4.2.2 using a root keeper won't help you retain root.

via my slapped KIT KAT moto X