yashsingh1/xdaforums huggingface dataset:
[Droid Ultra Original Android Development] Topsnake:
Here it is

http://xdaforums.com/showthread.php?t=2616104
[Droid Ultra Original Android Development] GnatGoSplat:
My slow-ass internet... FXZ won't finish downloading for over 2 more hours.

So to make sure I don't screw this up. I have acquired Droid Mini XT1030 already on 12.15.15 out of box.

1. Rooted with RockMyMoto - succeeded.

2. Ran MotoWPNoMo - succeeded.

So next step is:

3. Restore back to 15.15 (camera update) using FXZ.

FXZ is dl'ing now as mentioned. Is it preferable to install this with RSD or HouseOfMoto? I'm familiar with RSD and already have it. In the past, on my other phones it would sometimes do a full factory reset, sometimes it doesn't. I don't care if it does a factory reset since I haven't installed any apps or anything, but if it does, this is okay and won't affect the SlapMyMoto step, correct? I just want to verify that SMM doesn't need anything in /data that may have been left by steps 1 and 2.
[Droid Ultra Original Android Development] toddcouv:
Impactor Telnet Signature Bugs Not Found

Rooted 4.2.2 MotoWpNomo verified Wp disabled

Tried to run Telnet with impactor got error "Signature Bugs Not found" This on both my Ultra and my Wife's Any idea how the bugs go patched or if I can get them back so I can run Telnet
[Droid Ultra Original Android Development] Topsnake:
Need more detail.

Maxx'd out Kit Kat
[Droid Ultra Original Android Development] toddcouv:
Impactor Telnet Signature Bugs Not Found

When I attempt to start Cydia Impactor on # start telnetd as system on port 2222 it gives me error "Signature Bugs Unavailable" according to cydia this means the bugs that allow its exploit have been patched. Not sure what caused it. Will restoring 4.2.2 camera fix trough fxz or HouseofMoto restore these or will I lose root completely?
[Droid Ultra Original Android Development] Topsnake:
So why are you attempting to run cydia if your already rooted w/wp off on 4.2.2?

Maxx'd out Kit Kat
[Droid Ultra Original Android Development] toddcouv:
Impactor Telnet Signature Bugs Not Found

In order to run the next step towards kitkat -- SlapMyMoto
[Droid Ultra Original Android Development] Topsnake:
According to your first post, you are trying to run this on rooted 12.15.15. That is why it fails. You need to be on a fresh unrooted 4.2.2. Read instructions clearly next time instead of trying to cut corners.

Maxx'd out Kit Kat
[Droid Ultra Original Android Development] Khanusma:
What is the 4.2.2 camera update fxz file I should be using? is that the 15.15 or is there a different one?
[Droid Ultra Original Android Development] Topsnake:
15.15
[Droid Ultra Original Android Development] GnatGoSplat:
Success! Droid Mini XT1030 rooted on Kitkat!

Couple things.

1. Had to update adb after the Kitkat update. The phone was showing up in adb devices as "offline" with the version I had. The newer version popped up an authorization prompt on the phone and once I accepted it, I could connect using adb.

2. All adb steps completed successfully and the last one turned the screen off, but it didn't reboot automatically and neither did toggling bluetooth (tried that several times). It was fine after a manual reboot.
[Droid Ultra Original Android Development] cdfjr1975:
MotoWpNoMo kicked my butt. Took forever and wish I could gice good advice on how I was able to overcome but I have none since it was the same thing over and over again (definition of insanity). I had to fastboot and take root many times when MotoWpNoMo kept failing but finally one time it worked and now I'm on 4.4 Rooted. All other steps were as simple as OPs stated.

Thanks everyone and most especially JCase for this awesome root exploit.

I couldn't get the process to work all the way through on one machine so here were my steps

RockMyMoto Ubuntu 12.04

MotoWpNoMo Windows 7

House of Moto Windows 7

SlapMyMoto Ubuntu 12.04
[Droid Ultra Original Android Development] NWKENT:
Look at all the success this community has had, since your instruction document..I'm really tickled someone took the time to help many..you (my friend) will be rewarded for your effort.. :)

sent by my 4.2.2_12.15.15

RockMyMoto Root..SafeStrap v3.65

XT1080M (aka) Droid Maxx

(device #1)

Please donate to: jcase & Hashcode (if you can)
[Droid Ultra Original Android Development] Aaron413:
Thank you!

I am a novice to all this Rooting and stuff. But I am slowly learning.

I just want to say thank you for your efforts and your knowledge!

I have successfully rooted my Moto Ultra 4.4 KitKat, with free Hotspot! Awesome.

Took me forever but it worked! Thank you again Mr. Jcase!

Aaron L.

XT1080 Ultra

KitKat 4.4 -- 19.5.3 Root

MotoWpNoMo Win7

SlapMyMoto Win7

Stock WiFi Hotspot With No Ent. Check! :good::good:
[Droid Ultra Original Android Development] Topsnake:
Glad to see I could help out. I've received a lot of help with modding since the original Droid so I'm glad to be able to give back.

Maxx'd out Kit Kat
[Droid Ultra Original Android Development] cmelby:
Yes! Using HouseOfMoto to flash all the way back to 12.7.7 and let (Verizon) OTA do the update to 12.15.15 was the crucial factor.

Flashing HouseOfMoto 12.15.15, then using RockMyMoto to root, then using WpNoMo to change write protection, then using HouseOfMoto to reflash 12.15.15, and then trying to let (Verizon) OTA to update to 4.4 did not work. The OTA 4.4 update failed every time with 410 error.

The only thing that worked was:

Flashing HouseOfMoto 12.7.7, then letting (Verizon) OTA to 12.15.15, then using RockMyMoto to root, then using WpNoMo to change write protection, then using HouseOfMoto to reflash 12.7.7, then letting (Verizon) OTA to 12.15.15, then using SlapMyMoto (except the last couple of commands that are intended for after 4.4 OTA), then letting (Verizon) OTA update to 4.4 (which did not fail with 410 error), then entering the last couple of commands from SlapMyMoto that are intended for after 4.4 update).
[Droid Ultra Original Android Development] Lemmy Caution:
Slap Me, Slap Me

WARNING - take Jcase's instructions literally except - FZX the 4.4 xml file. Do Not take the OTA 'Over-the-Air'.

Great program, info and comments. I had few issues with implementation until I got to the end.

"Apply the OTA"

Well I took this literally and allowed the phone to download the update from Verizon.

There was a dialog indicating that since my device was 'modified' I should Wipe Data.

Sounds reasonable enough. OK

NOOOOOO too late.

I now have a KitKat Maxx without write permission errors that I can't root.

Oh well - I really prefer my RAZR MAXX HD - it has an external card for one thing. After using the xt1080m for 3 weeks, I reverted to the MAXX HD until I had time to perform this root exploit.. I will put the xt1080m on eBay -it's only a month old. I'm going to miss the reliability of the MAXX and its battery life but, not for long.

A New xt1080m development edition phone should be arriving in the next 7-10 days. I like to mess around with my phones and having a locked bootloader just doesn't cut it for me.
[Droid Ultra Original Android Development] GnatGoSplat:
Droid Mini had no problems taking OTA over-the-air.

Did you try skipping a step? I never got any dialog indicating that my device was modified.
[Droid Ultra Original Android Development] Lemmy Caution:
Slap Me I'm an idiot

Here's the scenario:

I was connected to my phone via USB -

the dialog appeared on my laptop

. It's not a big deal but others should be aware.

The Guide is perfect. It would have worked had I read

and actually contemplated

the dialog from Motorola. I assume that being connected via USB, the Motorola Device Manager produced the dialog. It was late, I was tired.

I'm a skier - You always hear that many accidents occur at the end of the day when people are 'tired and it's late'. Same goes for programming.

:)
[Droid Ultra Original Android Development] Topsnake:
The software update portion of the device manager?
[Droid Ultra Original Android Development] Carrzy:
Link for ADB update? my phone is doing the same
[Droid Ultra Original Android Development] Topsnake:
He is saying that after the update to 4.4, when trying to run adb commands the device will prompt you for authorization(on the device) to ensure that you are the user issuing the commands. He didnt physically update the adb application

Maxx'd out Kit Kat
[Droid Ultra Original Android Development] Carrzy:
ah. my mistake.
[Droid Ultra Original Android Development] grecho:
this sir was money!! thank you!

and BIG thanks to Jcase and all the Dev's Awesome work!!
[Droid Ultra Original Android Development] jaydotelloh:
Whelp, I messed something up. I was ready back through the thread and I cam to the conclusion I am thoroughly stuck on un-rooted 4.4. Does anyone have ANY hope of being able to either

1. Root 4.4

2. Downgrade back to 4.2.2 to try again? Is it possible to create an update.zip that would get us back to stock 4.2.2 (the 12.15.15 version)???

It'd be quite depressing if you literally only have 1 chance at this and a simple typo on an adb command screws you for eternity. So any help on getting back to 4.2.2 would be much appreciated!
[Droid Ultra Original Android Development] GnatGoSplat:
I got it here:

http://xdaforums.com/attachment.php?attachmentid=1724500&d=1360704125

Actually, I did. The version I had was apparently too old to make the authorization prompt come up.
[Droid Ultra Original Android Development] NWKENT:
Gee..word gets out on the net..see the center column, I certainly wish the Dev of this "SlapMyMoto" received at least a $5 royalty / fee, every time his works or ID is mentioned..maybe someday (hopefully).. :)

http://appdev.binaryappdev.com/2014/01/17/q-getting-started-with-rooting/

sent by my MZ617-32 XYBoard 10.1_SafeStrap v3.12_Jelly Bean 4.1.2

Please donate to: jcase & Hashcode (if you can)
[Droid Ultra Original Android Development] ihuntinde:
An exploit does exist for motorola devices on 4.4, JCase has shown it on youtube. However, he has not released it to the public yet, and has hinted that there is a chance he will not.

I think I have a good understanding of why he may not release it. I watched his presentation at XDA-DevCon on youtube and he has a code of ethics that he follows that allows the manufacturer's and telnet's a period of time to respond to vulnerabilities that he finds. If he gets a favorable response from either of those groups, he waits a period of time before he releases. If he gets a negative response, he releases the exploit.

It may be tough for those of us not in his position to understand. We may have to wait up to 60 days from the day he notified the manufacturer of the vulnerability before he releases the exploit. At least, that is what I got out of his presentation.
[Droid Ultra Original Android Development] paypalwithebay:
568488583

So... I've successfully gained root on KitKat. I need to use Isis one last time but of course it's giving me an error saying I can't use it because my phone is rooted. I tried to temp unroot by OTA root keeper and RootCloak plus but they didn't work. So is there a way to unroot my phone? Will re-flashing my phone with KitKat unroot my phone? if so, will it revert the Native Tether Mod?
[Droid Ultra Original Android Development] Topsnake:
You can do a full flash with the 4.4 FXZ however you will lose root and userdata. You will not be able to root after this.

Maxx'd out Kit Kat
[Droid Ultra Original Android Development] livinitwarrior:
Do you mean you did a basic factory reset in the phone's settings on 4.4, and you didn't lose root? Something's gone wonky with my modem, and it appears I'll have to do that, but would rather not lose root.
[Droid Ultra Original Android Development] needshelp101:
That's correct,I did basic reset through settings, and I also did a factory reset through stock recovery and had not lost root both times.
[Droid Ultra Original Android Development] Brenardo:
Pretty much at this time.
[Droid Ultra Original Android Development] SomeoneE1se:
*sadface*

Thanks for the response!
[Droid Ultra Original Android Development] Brenardo:
What are you planning to do with your borked device? How much do you want?
[Droid Ultra Original Android Development] jaydotelloh:
I have to say I understand the logic too. There is a perfectly suitable method to obtain root and have 4.4 using the old exploit, so there really is no rush to get it out. Just sucks that I am going to be stuck without root for a while. Coming from nexus land I am not used to this.

Do you have a link to that video?
[Droid Ultra Original Android Development] ihuntinde:
PM Sent with video link.
[Droid Ultra Original Android Development] needshelp101:
We're you able to get your phone in working order again?
[Droid Ultra Original Android Development] Lemmy Caution:
It's NOT borked. Just upgraded to Just a standard Vanilla XT1080m running KitKat. Works exactly the way a MAXX running Android 4.4 should which unfortunately at this point, means no root and no unlocked bootloader.
[Droid Ultra Original Android Development] livinitwarrior:
No, strangely, it blocked google services. I couldn't connect to any google functions at all, even sign in. Took it to verizon and they'd never seen anything like it, so a replacement gets here tomorrow. Very Weird. But thank you for your help- I'll be re-rooting tomorrow I suppose
[Droid Ultra Original Android Development] needshelp101:
Did you do a factory restore from recovery?
[Droid Ultra Original Android Development] Topsnake:
Why in gods name would you take it to VZ? You could have simply fxz back to 4.4 and had no issues. :thumbdown:

In your other post you said your modem was jacked? Easy to reflash just the modem itself. At any rate vz sucks
[Droid Ultra Original Android Development] livinitwarrior:
If I did FXZ, it was my understanding I lose the root functionality. Tried the modem, but it seems it was actually a google issue with the phone itself- i did 2 resets, one of them from the recovery, and the guy did a third. either way, another will be here tomorrow without having to be patched together.
[Droid Ultra Original Android Development] Topsnake:
Correct you would lose root, but there is a good chance the replacement may come with 4.4 preloaded so you may be SOL at any rate. Lets get to the bottom of this. You still have the device?

Maxx'd out Kit Kat
[Droid Ultra Original Android Development] nubia11:
Lmao TopSnake.... I totally agree with you here..... I had to laugh at you initial shock!.. Lol
[Droid Ultra Original Android Development] Topsnake:
Lol It is more of a disappointment. I don't approve of tinkering with a phone when you are well aware it voids your warranty, then running to VZW when something goes wrong. I feel you must pay to play lol.

Maxx'd out Kit Kat
[Droid Ultra Original Android Development] violaian:
Yay!

Finally, on 4.4 with root. You have to follow directions to a T. I spent the last few days reading and re-reading every post I could find, making sure I knew what to do whatever happened. Thanks again to all the devs responsible for getting us to this point.
[Droid Ultra Original Android Development] Topsnake:
Glad it worked out for you. Did you happen to use the guide?

Maxx'd out Kit Kat
[Droid Ultra Original Android Development] violaian:
No, just the OP
[Droid Ultra Original Android Development] Topsnake:
No big deal, might have cut down your prep time though. Enjoy kit kat

Maxx'd out Kit Kat
[Droid Ultra Original Android Development] Caseyk621:
Was it Google Play Services force closing then not syncing? If so you could've just gone to Settings---apps---selected Google Plays Service and Uninstall update. Shoulda woulda coulda though I guess.

Sent from my KitKat Ultra
[Droid Ultra Original Android Development] livinitwarrior:
Yes, but I just had finished doing the FXZ restore. I thought this was just different since I'd never heard anything like this before. To give a better description, the mobile data 4G never turned blue, and even on wifi you couldn't sign in on ANY Gmail account (the Verizon guy even tried his). Wifi and 4G would allow you to use the internet, but all Google-framework was blocked, and gave a weird error message that the rep couldn't even find, something about getting a secure connection. Sorry if I rushed to solve it with FXZ
[Droid Ultra Original Android Development] Topsnake:
Did you actually reflash the radio? You could have even pulled the services from the 4.4 fxz and flashed it. O well, we will see what the new device comes with

Maxx'd out Kit Kat
[Droid Ultra Original Android Development] livinitwarrior:
It hadn't been updated- this was on a freshly factory reset phone. Had no data changed at all
[Droid Ultra Original Android Development] Topsnake:
Lets be clear. FDRs do nothing to the system itself. They merely delete pictures, settings, messages etc. Hence why your problem persisted. Since you have a replacement coming, run the 4.4 FXZ and see if that fixes it.

Maxx'd out Kit Kat
[Droid Ultra Original Android Development] Caseyk621:
Factory data reset just resets data doesn't change system apps. Do you recall what version of play services you had on there? I'm guessing you no longer have the borked phone?

Sent from my KitKat Ultra
[Droid Ultra Original Android Development] livinitwarrior:
It did indeed. thanks for the help though!
[Droid Ultra Original Android Development] Topsnake:
I bet with a little time l, we could have narrowed down the problem and pulled the correct file from the fxz and flashed that alone to retain root

Maxx'd out Kit Kat
[Droid Ultra Original Android Development] livinitwarrior:
I will definitely take that under advisement as I will likely screw something else up again sometime. Seriously, appreciate the time
[Droid Ultra Original Android Development] paypalwithebay:
If anyone wants to hide root from isis on 4.4, use Hide Rooting. It worked for me.
[Droid Ultra Original Android Development] livinitwarrior:
Quick Question. I have still have write protection off on this phone (just checked to be sure, still comes out 0)... i know that the telnet prompt causes it to store the install.sh somewhere in the data folder before upgrading to 4.4(I think)... so is there a way to utilize this to gain root?
[Droid Ultra Original Android Development] Caseyk621:
I don't think so. You would've had to run the first couple steps of slapmymoto...

Sent from my KitKat Ultra
[Droid Ultra Original Android Development] livinitwarrior:
That's what I figured, but worth a shot
[Droid Ultra Original Android Development] NWKENT:
Can someone please explain this post..mentions downgrading from 4.4 back to 4.2.2..and now has 4.4 w/root..? Is this possible because the device is Moto-X.?

Unlocked bootloader.?

See post #211

http://xdaforums.com/showthread.php?p=49677383

sent by my 4.2.2_12.15.15

RockMyMoto Root..SafeStrap v3.65

XT1080M (aka) Droid Maxx

(device #1)

Please donate to: jcase & Hashcode (if you can)
[Droid Ultra Original Android Development] Topsnake:
Probably. Idk how they are able to do it but if you try to downgrade our phone it will soft brick

Maxx'd out Kit Kat
[Droid Ultra Original Android Development] Caseyk621:
Yes this is because the bootloader on the motox can be downgraded from 4.4 to 4.2. Their(vzw motox) bootloader still hasn't been unlocked. I read somewhere that the security on the 4.4 bootloader for Ultra/Maxx is written so that it can't be downgraded.

Sent from my KitKat Ultra
[Droid Ultra Original Android Development] NWKENT:
Your reply makes perfect since to me.. :). Thanks..wanna learn what I can and questions are a major part of learning..lol

sent by my 4.2.2_12.15.15

RockMyMoto Root..SafeStrap v3.65

XT1080M (aka) Droid Maxx

(device #1)

Please donate to: jcase & Hashcode (if you can)
[Droid Ultra Original Android Development] livinitwarrior:
Here's a thought- based on the fact that the current 4.4 root doesn't cause a change in the bootloader, wouldn't it make sense that the next OTA would work without any issues? Perhaps a "hide root" with an OTA protector app, but... is there any reason to think otherwise?
[Droid Ultra Original Android Development] adildroid29:
Still waiting rooted 4.4 Kitkat ..
[Droid Ultra Original Android Development] NWKENT:
Friend..are you on 4.2.2 (or) 4.4. ?

sent by my 4.3_14.14.14

XT1028 (aka) Moto-G
[Droid Ultra Original Android Development] adildroid29:
Im working 4.4 Kitkat. Before 4.2.2 Rooted but have Problem when I update Kitkat Not root
[Droid Ultra Original Android Development] NWKENT:
PLEASE..I plead with anyone that remains on 4.2.2 (if any)..WAIT..Truly I Say To You..there will be a much simpler way to gain Root from 4.2.2_12.15.15 (to) 4.4_19.5.3

PATIENTS..will be rewarded.

Those that have a device on 4.4 w/o Root..YOUR hope is that someone claims the bounty..or a new device and start over, or an OS update that is Rootable..

sent by my 4.4_19.5.3

SlapMyMoto Root

XT1080M (aka) Droid Maxx PE

(device #2)

Please donate to: jcase & Hashcode (if you can)
[Droid Ultra Original Android Development] adildroid29:
I have done the instructions :

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

My previous position 4.2.2 Rooted by RMM, And Update Manualy 4.4 Kitkat.
[Droid Ultra Original Android Development] Topsnake:
run this command and report result

adb shell getprop ro.boot.write_protect
[Droid Ultra Original Android Development] adildroid29:
adb shell getprop ro.boot.write_protect = (0)

Sent By Droid Maxx 4.4 UnRooted
[Droid Ultra Original Android Development] Topsnake:
Did you run the slap my moto commands TWICE on stock 4.2.2 before taking the OTA
[Droid Ultra Original Android Development] adildroid29:
I only once the SMM, So what should be done ..?

Sent By Droid Maxx 4.4 UnRooted
[Droid Ultra Original Android Development] Lemmy Caution:
Reply to Topsnake

That's correct. Sorry for the late reply. Busy week. I'll probably be posting later - I'm working on my new XT1080m DE as we speak. It's nice to have the unlocked bootloader. I've reflashed 12.15.15 once and have installed Twrp. I'm much more comfortable working with an unlocked bootloader.
[Droid Ultra Original Android Development] Jimmy8881:
Now I read this and got an idea for the people stuck on 4.4 without root..

I remember having a similar problem on a Droid razr a while back, where some people got stuck without root after an OTA and couldn't downgrade, but a developer came up with a solution, if I remember right I think it was flashing everything except for the boot.img , gpt.bin or the motoboot.img, so the Razr was running the latest bootloader, but with an older operating system that had exploits so it could be rooted, could this be done with in our situation? like flash the 4.2.2 OTA except for the bootloader, in other words keep the 4.4 bootloader but flash the 4.2.2 system.img to keep the exploits available? just an idea.
[Droid Ultra Original Android Development] Lemmy Caution:
Success - Got 4.4 - Got Root

Third time - success.

Thanks
[Droid Ultra Original Android Development] porkweasel:
I have a Droid MAXX that is rooted and running 4.4 KitKat.

I would like to do a Factory Reset (from the settings menu) but I am afriad that I would lose root in the process. Would a factory reset maintain root access (because it's only deleting data) or will root be lost in the process?

Thank you in advance!
[Droid Ultra Original Android Development] ReverendYo:
HELP PLEASE --

I do have a fully rooted 4.4 using the methods contained in this thread and others, but in moving things around to fit my preferences, I made an error in the framework-res.apk and am now caught in a bootloop. ADB doesn't have root access even by going in through BP tools, so I can't mount system rw, which means the convenient stock framework-res.apk.bak I have sitting in my /system/framework folder is useless.

Can someone suggest a way to mount system, so I can rename that .bak file, or suggest whether or not a flash of the stock system img will end up just unrooting my phone... leaving me stuck on unrooted 4.4

Thank you!

~Rev
[Droid Ultra Original Android Development] Topsnake:
Sounds like your phone has you in check mate. Im afraid you may have to fxz to repair it

Maxx'd out Kit Kat