yashsingh1/xdaforums huggingface dataset:
[Moto X Original Android Development] nrune:
Almost gave up, but persisted and now rooted!!

Thanks!
[Moto X Original Android Development] hawkdown77:
We lost Android recovery?

Enviado de meu XT1058 usando o Tapatalk 2
[Moto X Original Android Development] agent2099:
I've been reading this forum for hours and still can't get the grasp of unlocking my verizon dev edition moto x on android 4.4.

Is rockmymoto the only way to root this device?
[Moto X Original Android Development] Gilly Monster:
You must go back to 4.2.2 Camera update for one.

Then use this tool here

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

And then run the last step in the OP of this forum. There is also a ROM you can use to install over your stock that is already rooted. It in fact is the most easiest way of obtaining root on your 1060. I had to do the same on my 1058 and mine is a non-dev model.

VZW ROM

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

It's stock with extras (keeping the talk function as well).

I hope this helps!!!!
[Moto X Original Android Development] addictedhacks:
I can't figure out the math problem... Maybe if I donate $$ they'll take out the pointless math.
[Moto X Original Android Development] Dark9781:
The math is simple. Take c divide by a to get b.

Sent from my Moto X on KitKat
[Moto X Original Android Development] Psychlone:
I purchased 2 x xt1030 (Droid Mini) for each of my kids.

I just saw the new 4.4 update that's ready to download, but I stopped them from doing it as I really wanted to root both phones so I could install tracking software on them first.

I followed the instructions, got root correctly and verified by installing SuperSU from Chainfire, and double-verified it works.

I then took the update on one phone, but it just keeps rebooting. It will boot all the way in normally, stays on the lock screen for about 30 seconds, and then reboots - it hasn't stopped doing this for about 30 minutes now.

Something I've missed?

The phone successfully took RockMyMoto, telnet and all - EVERYTHING worked just like it was supposed to - but after taking the update, it just keeps rebooting.

Now I don't dare do it on the other phone that I've already rooted and is just waiting to take the update!

EDIT: I ended up using fastboot (since I can't boot into anything but AP Fastboot anyway), and have flashed boot.img, motoboot.img, recovery.img (but there is no recovery present even though it flashed without error), and system.img. System.img failed with several errors, so now I'm sure that the problem exists in the system that's on the phone.

I picked up the correct download (12.15.15) from here: http://sbf.droid-developers.org/phone.php?device=2 and unzipped all the files to be able to fastboot them to the phone.

As mentioned, all flashed correctly except system.img.

**EDIT: I found that I needed to use mfastboot instead of the standard fastboot to flash the system.img because it's apparently too big - mfastboot breaks it into smaller chunks and pushes them correctly, however, the phone still reboots.

This isn't considered a bootloop, it will boot all the way into the homescreen, stay active and live for around 20 seconds and then reboot.

I didn't erase ANYTHING AT ALL because I can't lose her data, so I need to know if I erase any of those before trying to fastboot flash them (specifically system.img), will I lose her data?

I'm already going to be in big trouble tomorrow morning when she finds out that I've screwed up her phone. PLEASE help a Brother out!!

Help please?

********** FINAL EDIT **********

I figured it out on my own.

While fastbooting and mfastbooting files to the phone, I realized that it wasn't working because I was missing something somewhere, so I opened the XML file in the original 12.15.15 zip and went through it line by line.

The one thing that I had neglected to do while in fastboot was to ERASE CACHE.

Once I had erased cache via fastboot (and obviously after pushing all the proper img files), it all worked correctly after reboot - the phone no longer reboots on it's own and immediately started the download of the OTA 4.4.

I hope that this post helps anyone else that happens across this problem.
[Moto X Original Android Development] lowvolt1:
But you will not be rooted.

Slapped the sh*t out of my X
[Moto X Original Android Development] Psychlone:
You're right - I checked after it was done and it wasn't rooted.

I i guess I'll have to wait until there's a new exploit. BUT, you spotted something that I didn't - what is it??
[Moto X Original Android Development] lowvolt1:
Rockmymoto is the root method for 4.2.2. Root will not survive the OTA. your booting issue was common when 4.4 rolled out. Slapmymoto is the 4.4 root method. But you have to start on 4.2.2 root with rockmymoto. Run motowpnomo. Then flash back to 4.2.2. Then run slapmymoto. In that process you will be prompted to take 4.4 OTA. Sorry you will lose data. You have to in order for it to work.

Slapped the sh*t out of my X
[Moto X Original Android Development] Psychlone:
LOL, what happened?

From waaay back on the OG D1, there's been some really great modding - and some awesome devs that created easy, one-click root methods, or at least comprehensive guides that show everything that needed to be done - in this specific case, we're talking about 3 completely different guides (each of which are written well and explain most of what's necessary, but none of which seem to tell you that they're only meant for "this or the other")

I've been rooting and modding since the OG Droid, and I'm obviously not afraid to fastboot files one by one, but why is it that ALL of the required information is scattered among several posts instead of in a single easy to read format that's stickied?? This should be common practice by now IMO.

I read all those posts you're speaking of, and because none of them were very clear on what was necessary for what, I had no idea that you have to jump through so many hoops just to get this job done.

Gaining root on the Droid Mini (XT1030) is harder than any other Android device I've ever rooted (and that's quite a lot - I do computer repairs for a living and get asked to root devices all the time, so I've rooted no less than 2 dozen different kinds of devices from phones to tablets) -- but in that, I really feel like blaming the lack of a single-click program like what is available for most other devices, or AT LEAST a comprehensive guide that explains in detail exactly what needs to happen, and which encompasses ALL the required material.

------------

Enough complaining - I suppose that maybe I should take it upon myself to create the guide that is clearly needed so as to help others avoid the pitfalls that I encountered just trying to gain root before taking the 4.4 update. I've written guides before (not here, but in several computer forums) and maybe I should just try to contribute more around here.

FWIW, I used RockMyMoto, which ended up working to gain root on 4.2.2, and then I tried SlapMyMoto, but it said that it didn't work on 4.2.2. I saw the motowpnomo thread, but didn't realize it was an integral part of a single equation because it seemed to have nothing to do with everything else (pwnmymoto was supposed to open write access, but that didn't work either due to some random error that I can't remember now), so in my mind, all of those separate threads just lead me around in circles. I'm just glad that I've used fastboot in the past and have some experience in this - I would have been crazy by the end. ;)

I DO thank you for your input, LowVolt. Without your single, informative post, it would not have been clear to me that you have to do ALL of those things to gain root and maintain it through the 4.4 update.
[Moto X Original Android Development] lowvolt1:
Here is a link that was put together by a user.

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

Slapped the sh*t out of my X

---------- Post added at 09:53 AM ---------- Previous post was at 09:50 AM ----------

Here is another with a script. I think it will work for mini.

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

Slapped the sh*t out of my X
[Moto X Original Android Development] Psychlone:
Thank you! I have no idea how I didn't see this before, this is EXACTLY what I needed.

Take care.
[Moto X Original Android Development] Danzoman:
So I picked up a new moto x from Vzw and it still has the pre camera patch firmware. What's the best direction to take from here?
[Moto X Original Android Development] lowvolt1:
I see a couple different options.

First you could root using pwnmymoto, then run motowpnomo, then you would have to flash back to 4.2.2 before camera patch. Take the OTA which would probably bring you to 4.4, the you would downgrade to 4.2.2 after camera update, so you could run slapmymoto.

Or

You could take OTA which would probably bring you to 4.4, then downgrade to 4.2.2 after camera update, root using rockmymoto, run motowpnomo, flash back to 4.2.2 camera update, then run slapmymoto.

There, I think that's it. Whooo!

Slapped the sh*t out of my X
[Moto X Original Android Development] Danzoman:
Am I not on the pre camera patch firmware now? The popup keeps saying the update is going to improve the camera. I guess I'm getting confused because it seems silly to root than update than come back.
[Moto X Original Android Development] lowvolt1:
Yes you are. I would think that the update would bring you all the way to 4.4, but it may only bring you to 4.2.2 camera update. That would be silly to me, but it may update in stages.

If you want to end up on 4.4 kitkat you will have to root, then downgrade regardless of how you go about it. Its just how this root process is.

You could always take the update, see what version your on, and go from there. You will not be able to root from any version without going backwards at least once anyway.

Slapped the sh*t out of my X
[Moto X Original Android Development] Danzoman:
OK that makes a little more sense now. I was reading it like anybody that has bought a moto x since Kit Kat was out opened the box updated. I thought I was lucky. Thanks.
[Moto X Original Android Development] vega dawgg:
Next Step

After

Quote:

telnet {your phone's ipaddress} 2222

Run the exploit through telnet

I type in

Quote:

dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto

Then I get

'dalvikvm' is not recognized as an internal or external command, operable program or batch file

what am I doing wrong?
[Moto X Original Android Development] lowvolt1:
Are you running cydia impactor first?

Slapped the sh*t out of my X
[Moto X Original Android Development] vega dawgg:
Yes, It says running waiting completing then goes back to the drop down with ' "# start telnetd as system on port 2222" [Start]' window

EDIT: skipped a step figured it out
[Moto X Original Android Development] Slarti77:
Loaded up CydiaImpactor...might have problem...

Hey all,

i've been reading up on rooting my Droid Maxx. I've read through multiple threads and and think I have the basic process down. I'm starting with Rock my Motot to gain initial root access. As part of this, the instructions say to load Cydia Impactor. I loaded this, hooked up my phone (which has usb debugging on and is connected as a media device).

I started to review the different options on Cydia. I picked # start telnetd as system on port 2222 then all of a sudden Cydia started talking about downloading someting and "Payload" appreared on the phone. I wasn't trying to do anything other than see if I could communicate with the phone. I closed Cyida. I have not done anything with the phone yet because I'm not sure if I dl'ed something or if I even have a problem. i didn't give Cyida the IP address for the phone so I'm not sure how it was communicating with it.

Is there any way I can find out what "payload" was and if it has done something to the phone?

Edit: one thing that i did notice, Circle Battery widget suddenly turned yellow and was no longer accuratly reflecting the charge on the phone. When I deleted the widget, and tried to re add it, it no longer is visible, but something is there as I can hold it and put it in the trash. Tried reinstall, still same.

Phone is still connected to laptop.

Thx

Mark
[Moto X Original Android Development] lowvolt1:
First I would reboot and try again.

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] Slarti77:
Thx. I'll try again tomorrow.
[Moto X Original Android Development] Blanko6:
after running telnet it says system is not write protected .?
[Moto X Original Android Development] lowvolt1:
That means you successfully ran motowpnomo at some point. Now you can just flash back to clean 4.2.2 and run slapmymoto

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] Blanko6:
Yes, i have had some issues rooting and at some point i had already rooed 4.2.2 and done the WP but had issues with slapmymoto and step 4(after i too the 4.4 update, adb would show device offline ) now im back on 4.2.2 so should i go ahead with slapmymoto ?

thank, been "rooting" since 6pm yesterday ....
[Moto X Original Android Development] lowvolt1:
Yes. Run slapmymoto. Tag me and I will help if you get stuck

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] sebadamus:
That answer seems a command prompt (DOS) answer, when you enter a bad command. So I think you are not running that command inside telnet of your phone.
[Moto X Original Android Development] Blanko6:
[MENTION=4520932]lowvolt1[/MENTION] THANK YOU!!!!!!

i didnt all the slapmymoto steps and now taking the 4.4 update (since this is what got messed up before should i unplug the device and plug it again once im about to start step 4 ?) im just thinking of any lil thing ....... :silly:

thanks again
[Moto X Original Android Development] lowvolt1:
Unplugging the device is not necessary. After the OTA finishes you will do the initial set up. You will have to re enable USB debugging. And you most likely will need to unlock the screen and grant USB debugging.

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] Blanko6:
[MENTION=4520932]lowvolt1[/MENTION] same issue from before .... this is the last step

Step4)

Now that we are on 4.4, we can finish the process with adb shell:

Code:

adb shell

cp /sdcard/install.sh /data/local/tmp/install.sh

chmod 755 /data/local/tmp/install.sh

echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper

well, when i type "adb shell" on command prompt it says error: device offline ....

is there any other way to finish that last step ?
[Moto X Original Android Development] lowvolt1:
You have to enable USB debugging again, which I am sure you have done. Slide the unlock of the phone. There should be a prompt. Grant it. If you have done this, unplug the USB cable and plug it back in. You should hear the connect sound.

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.

---------- Post added at 09:59 PM ---------- Previous post was at 09:58 PM ----------

If this all fails reboot the device.

Make sure your opening your command prompt from adb.

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.

---------- Post added at 10:01 PM ---------- Previous post was at 09:59 PM ----------

Have you tried the command adb devices?

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] Blanko6:
yes, USB debugging was checked off, i did get the prompt and and i granted it.

just rebooted and nothing, still offline.

when i do adb devices it gives me a serial number and in front of the serial number says offline .

i do not know how to open command prompt from adb.

doing some research before some mention that maybe my adb needed to be updated ?

Thanks man, thanks for your time [MENTION=4520932]lowvolt1[/MENTION]
[Moto X Original Android Development] lowvolt1:
You should have been opening command prompt all along from adb. Go to your SDK folder platform tools adb. Shift, right click and select open command prompt here.

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.

---------- Post added at 10:17 PM ---------- Previous post was at 10:16 PM ----------

Did you unplug USB and plug back in? Did you get the connect sound? Does it show in the notification bar that USB debugging is on?

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.

---------- Post added at 10:20 PM ---------- Previous post was at 10:17 PM ----------

Its been awhile since I have rooted. But when you pull down the notification bar, does it give you the option to click on the USB connection type? You could toggle between MTP and the other one. Don't remember what it is. And see if that helps.

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.

---------- Post added at 10:25 PM ---------- Previous post was at 10:20 PM ----------

So when your connected to USB pull down the notification bar. You will see connected as media device or connected as camera. Click that and if media device is selected, click camera and then back to media device. See if that does it.

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] Blanko6:
lowvolt1

**** !!!! yes, it seem to be working when opening from SDK folder . now, i ran all the commands but nothing seem to happen, it says toggle your bluetooth to reboot but nothing happened, should i do i manually ?? also one more thing, the only thing on my placed on my sdcard was the SlapMyMoto.jar file, the rest of the files that were on the zip are left on my desktop. is that ok?
[Moto X Original Android Development] lowvolt1:
Yes. Reboot manually. The files should be in your fast boot directory. Try the reboot and see what happens. You may be okay. If you didn't get errors along the way.

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] Blanko6:
[MENTION=4520932]lowvolt1[/MENTION]

Damn bro, after 2 days i just installed superSu on 4.4 so my best guess is that im rooted !!!!!!!!!!!

THANK YOU for your time, do you take donations !!

thank you again bro, not all of us take the time to help sometime .
[Moto X Original Android Development] lowvolt1:
What supersu did you install? The one by chainfire? Did it ask you to update the binaries? Was that installation successful?

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] Blanko6:
Yes, the chainfire and the binaries installed successfully !? ??
[Moto X Original Android Development] lowvolt1:
Good job! Glad you got it.

Enjoy your slapped phone!

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] Slarti77:
Hey Lowvolt1,

I got through the entire install and all looks good. I went to install SuperSU and got the following:

1. The SU binary needs to be updated. Continue? I hit Continue.

2. If you have a custom recovery like TWRP or CWM, that can be used to (try to) install the SU binary.

this is recommened for HTC devices. How would you like to install the SU binary?

choices are Normal or TWRP/CWM.

I got this far with no screw ups and don't want to blow something. Which to I choose?

Thx

Mark
[Moto X Original Android Development] lowvolt1:
Sorry it took so long for a reply. Choose normal. You don't have a custom recovery.

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] Slarti77:
Thanks dude....worked (I think).

How do I now verify that I have root.

After that (sometime tonight or this weekend) I will be on to MOTOWPNOMO (to remove write protection) and then last step to prep for move to 4.4 and root which is, I believe, running house of Moto and flashing back to 2.15.15 camera update (which I believe will remove root access in prep for next steps of SlapMyMoto). I will likely need some verification help on this. If I have questions on that is it ok to keep them in this thread or is there a House of Moto thread that should ask them in? I have never flashed/restored before.

Thx

Mark
[Moto X Original Android Development] lowvolt1:
Download root checker from the play store I have never used house if moto. I am pretty sure you will have better luck using rsdlite. You need a clean install of 4.2.2 to root 4.4. I would ask questions in the particular thread for the program you are using. If you tag me, I will help.

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] sipjca:
deleted for now.
[Moto X Original Android Development] lowvolt1:
Since you have disabled write protection. You can use slapmymoto to root. In the process you will be prompted to take the 4.4 OTA. You bootlooped because you were rooted on 4.2.2 and root will not survive the update. Not to mention you changed the phone in the process.

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] sipjca:
Haha thanks man, I was just doing a quick search and found that out, and promptly deleted my post ahahah. But after slapmymoto there should be su installed and working on 4.2.2? And then that should just continue to 4.4 or no? No su in 4.2.2 at all? Either way surging forward. Thanks for the help and confirmation!
[Moto X Original Android Development] lowvolt1:
Do you want to end up on 4.4? Or just root 4.2.2?

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] sipjca:
4.4
[Moto X Original Android Development] lowvolt1:
Okay. Since you already rooted with rockmymoto, and ran motowpnomo, from there you flash back to 4.2.2 camera update. Then start with the slapmymoto steps. You will be prompted to take 4.4 OTA.

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] peters4n6:
when i turn on telnet do i turn on client, server, or both?
[Moto X Original Android Development] lowvolt1:
Hmmmmmm. I used puttytel it works awesome! Try that.

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] peters4n6:
what i meant was when , in Win7, I turn on telnet services (control panel) do i turn on client, server, or both?
[Moto X Original Android Development] lowvolt1:
I am well aware of what you meant. I am trying to save you some headache. A lot of users had trouble using telnet on win7 machines. Do yourself a favor and download puttytel. You won't regret it.

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] johnnywayne28:
I use nothing but putty at work its awesome and hasn't failed me yet
[Moto X Original Android Development] peters4n6:
Thanks. Since I have been reading (and re-reading) the the steps to root my moto x 4.4 using Puttytel is a new step I need to read about and learn. What steps am I omitting (or substituting) using puttytel? Is it the "telnet [ipaddress]..." command? or is it also the commands after acheiving that connection? I think I recall someone saying it's in the rockmymoto video earlier, but i'm at work now and can't access youtube.
[Moto X Original Android Development] lowvolt1:
Your not ommiting anything. Still do all steps. Just use puttytel instead of telnet.

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] peters4n6:
So when it's "time to telnet" just open puttytel to establish telnet connect on 2222 and then enter following commands in puttytel?
[Moto X Original Android Development] lowvolt1:
You will still use cydia impactor to establish connection. Then you use putty tel to enter commands. Instead of telnet

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.