yashsingh1/xdaforums huggingface dataset:
[Droid Ultra Original Android Development] efdisastet:
wish I'd known before I let the upgrade do its thing that I wouldn't be able to go back... I'm not worried about my data, even a "Factory Reset" won't bring me back at this point, right?
[Droid Ultra Original Android Development] bigv5150:
Factory reset just resets data (factory DATA reset) fxz resets the system it installs the whole system wiping out root etc. So to answer your ? No it won't help at all. At this point if your on 4.4 without root you will need one of two things someone to figure out how to downgrade to 4.2.2 or an exploit that roots 4.4
[Droid Ultra Original Android Development] efdisastet:
guess I'll just have to live without tethering until someone figures out one of those things...
[Droid Ultra Original Android Development] Topsnake:
Ok im going to try and tackle this all at once but the post is a little confusing.

1) DL and extract motowpnomo. You dont need to run a CMD prompt for it as it is self sustaining. Just ensure debugging is enabled on the phone, plug it in, run the .exe in the extracted files and let it do its thing. Note: Keep a look out for a superuser request on the phone after the first reboot. Mine wouldnt continue until I allowed it on the device.

2) When Motowpnomo is dont use RSD light 6.1.5 to FXZ back to stock 12.15.15 (If you need help let me know.

3)Push slap my moto to the phone.

Run cydia/telnet as specified

Reboot

4) Run cydia again/telnet again

5) Run the OTA in stock recovery. Copy it to your SD card and rename as update.zip. Boot into recovery. You can do this by enabling debugging again then using the prompt below. In my case its

cd c:/sdk/platform-tools

adb reboot recovery

Select apply from SD

Will update recovery only

Select Apply from SD again

Will fully update to 4.4

6) Once booted back into 4.4 Run the commands in the OP step 4

7) You can do the toggle thing but mine didnt reboot. I just installed SuperSU from the store and had root.

8) Enjoy root
[Droid Ultra Original Android Development] jcase:
If someone could get me a copy of about, boot, and a dump of system I will look at a better solution for the droid line

Sent from my HTC Two
[Droid Ultra Original Android Development] Topsnake:
PM'd
[Droid Ultra Original Android Development] Metfanant:
So are we in agreement then that we can't downgrade from 4.4 to 4.2.2?...

Shame for those that let the OTA do its thing like I almost did...

Edit: there isn't any reason that the root exploit wouldn't survive a factory reset is there?...

Against better judgement I did a keep data FXZ when rooting and am having a couple wonky issues that I don't think are actual bugs
[Droid Ultra Original Android Development] Collisionc:
I'm possibly mentally deficient, but I can't force my phone to boot into what everyone is calling "recovery mode."

I followed all steps here, except instead of installing the 4.4 update via adb sideload, I copied it over to the phone and just installed it via zip. Old habits.

When I attempt step #4, on the very last line I get

"/system/bin/sh: can't create /sys/kernel/uevent_helper: Permission Denied"

I ran

adb shell getprop ro.boot.write_protect

After I ran that exploit and it came back with a 1, but now when I run it, it flags with a 0.

I noticed that in your other guide you mentioned this would be the case if the phone was booted normally, so I tried to force my phone into recovery mode via

adb reboot recovery

It loads up with the dead android on the ground, I press volume Up + power and it shows:

Android System Recovery <3e>

SU2-3

with the options Reboot system now, apply update from sdcard/adb, wipe data/factory reset, wipe cache partition.

Is there supposed to be a special option here to boot into recovery? I tried reboot system now and still no dice.

The only unique things I can think of that may have messed it up were using the "Complete unroot" option on SuperSU after I ran the write protection, and then after that I ran HouseofMoto with fxz save data to ensure that everything was in place before I ran SlapMyMoto.
[Droid Ultra Original Android Development] livinitwarrior:
Does that mean a fully rootable 4.4 without downgrading? If so, I don't mind waiting for it.
[Droid Ultra Original Android Development] Metfanant:
That IS recovery mode...

Also...I'm not saying this is your issue..but why did you perform the unroot procedure in SuperSU?
[Droid Ultra Original Android Development] Topsnake:
I think you messed it up running the complete unroot script which was not called for at all in the instructions. This is what happens when people deviate from the instructions. The phone is denying the commands. You said you ran the command for WP after the exploit and it came back with a 1? Needed to be a 0. Try installing SuperSU and see what happens. If it doesnt work and it wont take the commands than you may be stuck like that until the FXZ is released.

He did. Said that in his first post. Deviating from instructions kills phones a lot.
[Droid Ultra Original Android Development] bigv5150:
I'm guessing he is going to look into it doesn't mean it will be possible. But I have seen him pull rabbits out of his hat before.
[Droid Ultra Original Android Development] Metfanant:
I'm sure if JCase really wants to put in the time and effort to get a Droid Specific Root method working that he can...

What we REALLY need is for a friendly ninja at Motorola to leak an unlocked bootloader like on the VZW Galaxy S3...
[Droid Ultra Original Android Development] Summersett:
I did everything up to updating to 4.4 (through recovery from sdcard), and then did a full wipe from the 4.4 recovery before booting (just wanting to start fresh)... In hindsight, that was my mistake, right? Because now I can't do step 4, since there is no "install.sh" on my /sdcard/. Any hope for me, or am I waiting this out until there's a way to get root for 4.4? Really kicking myself right now.
[Droid Ultra Original Android Development] ahjee:
Jcase the god does it again. Thank you so much my dude, I needed this
[Droid Ultra Original Android Development] Collisionc:
Ah, ok. For some reason I was thinking it'd be a little more than that.

The phone was required to be unrooted for slapmymoto to be installed, I doubt that the unroot procedure in SuperSU would remove the write protection from MotoWpNoMo.

Ok, so I'm just mixed up in general. This is what I get for not double checking while writing that post.

I currently have "0" showing up when typing in the command. So I actually do have write protection removed, but it won't let me finish the last echo command.

It's not a big deal if I have to wait a little bit, thanks for looking into it.
[Droid Ultra Original Android Development] Metfanant:
The flash back to stock 4.2.2 Camera update would have taken care of that for you...

There is a reason why there is no step that says "unroot your phone using SuperSU" directions for these things are really specific for a reason

At this point it doesn't matter whether you have WP on or off...by unrooting with SuperSU instead of flashing the FXZ file you borked something in the process and the slapmymoto exploit will not run
[Droid Ultra Original Android Development] Summersett:
I'm pretty sure you're in the same boat as myself... and I think it is because we wiped data.

My guess: SlapMyMoto writes "install.sh" to the data partition. You need that there after updating to 4.4 from 4.2.2 for the root path. If you wipe the data partition... root path is gone so the shell commands don't work at the end.

My only question is if this install.sh can't just be uploaded from someone and placed in the proper directory so we can still run those commands? Or is it phone specific?
[Droid Ultra Original Android Development] Ciscokid92:
I'm in the same boat as both of you however I didn't wipe data. But can't run the last adb command..
[Droid Ultra Original Android Development] Optimus812:
You are the man jcase, followed the procedure (a bit long but worth it-- RockMyMoto, MotoWpNoMo, Restore to Stock with HouseofMoto, then SlapMyMoto and finally sideload 4.4KitKat Update) and came out with KitKat with Root!!! Nice work, I'm always amazed how these devs figure these things out...amazing.
[Droid Ultra Original Android Development] Collisionc:
Yeah, it was an idiot decision for me, hopefully someone else will learn from it.
[Droid Ultra Original Android Development] Dragon31337:
Does the same work for mini (XT1030)?
[Droid Ultra Original Android Development] Topsnake:
It may, but without someone testing it, then we aren't sure. I can say that I've seen some things interchangeable between the X, maxx, ultra, and mini
[Droid Ultra Original Android Development] TheWhiteChallenger:
So just to confirm, as of now, once on KitKat you can not downgrade the droids, and therefore can not root. Correct?
[Droid Ultra Original Android Development] christophermx4:
I believe that's the case. How do you start a bounty around here anyway? I'd throw down fifty dollars for a working KitKat root on the Droid Maxx.
[Droid Ultra Original Android Development] TheWhiteChallenger:
I actually started the original bounty for root on the droids. Just stary a new thread with an aproprate title. Being specific about the terms and structure of the bounty is the key.

Here's the thread OG bounty thread for reference.

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

On a related note if root after the fact doesn't pan out and anyone wants to buy a Maxx running KitKat w/root mine will be up for sale shortly.
[Droid Ultra Original Android Development] bigv5150:
Jcase is actually looking at root for 4.4 now he requested a system dump which he received so finger crossed for those of you who don't have root.
[Droid Ultra Original Android Development] TheWhiteChallenger:
Coolness. I guess he has a little more time on his hands now
[Droid Ultra Original Android Development] jphillips.hd88:
Well, I was not as successful as other folks running this.I was on 15.15 unrooted. So I needed to root and give write protection per instructions with RockMyMoto and MotoWpNomo. Success. Then I got all the way through to the SlapMyMoto step 3. When I go to install update through recovery it fails.

"Verifying current system..."/system/etc/install-recovery.sh" has unexpected contents. Installation aborted.

No problem right? just FXZ back to the 15.15 and start over right?

Wrong. In the process of the update it updated enough and RSD Lite won't let me downgrade. I am totally softbricked until the FXZ files come out to KitKat I think.

Unless somebody might have any ideas.
[Droid Ultra Original Android Development] Topsnake:
So let me get this straight. You took the OTA without first FXZ'ing back to stock like the instructions tell you to?
[Droid Ultra Original Android Development] rlmesq:
I can verify that it does. I ran it on both my Maxx and my girlfriend's Mini, using the OTA from http://xdaforums.com/showthread.php?t=2577977

Both are running rooted 4.4.0 without any problems.
[Droid Ultra Original Android Development] Topsnake:
Im more concerned with it being off the OTA path now. My justification for this is the two seperate 12.15.25 fxzs for the maxx and ultra. Unless moto undid that whole thing with kit kat. Need someone to post the actual pulled ultra update for comparison

Maxx'd out Kit Kat
[Droid Ultra Original Android Development] jphillips.hd88:
I did FXZ back to stock...Then the instructions say you have to use RockMyMoto and pwnmotonmo before using SlapMyMoto...Am I wrong?
[Droid Ultra Original Android Development] Topsnake:
Yup. Its Rock then WPnomo then FXZ. Need to FXZ right before ota

Maxx'd out Kit Kat
[Droid Ultra Original Android Development] jphillips.hd88:
Okay, here's my mistake...I was already on the 15.15 (radio update). so I ran Slap
[Droid Ultra Original Android Development] Topsnake:
Yeah your soft bricked until the FXZ comes out. You may be able to flash recovery through fastboot but im not sure the feasibility.
[Droid Ultra Original Android Development] coronanlime:
Damnit. I think I am softbricked as well.

I followed the instructions. Was already rooted, ran the WP off, then I unrooted using HouseOfMoto.

Then I did as the instructions said and used the impactor and connected through telnet. After reboot the second time, I tried to sideload the update, and it wouldnt boot up after that. Said Partition (boot) Security Version Downgraded.

I followed the instructions and dont know why it didnt take.

Any ideas?
[Droid Ultra Original Android Development] Metfanant:
NO...

1. Rock

2. WP off

3. FXZ

4. Start Slap

5. Update

6. Finish Slap
[Droid Ultra Original Android Development] Summersett:
Well... you slap between updating.

"Step3)

Once the device has rebooted, run Impactor again and connect over telnet just like in the previous step, then run the same command

Code:

dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto

Once the device has rebooted, please take the 4.4 OTA. <- Update

Step4)

Now that we are on 4.4, we can finish the process with adb shell:"
[Droid Ultra Original Android Development] Metfanant:
True
[Droid Ultra Original Android Development] coronanlime:
Thats what I did. Or so I thought. Is this going to be fixable?\

Was able to fastboot flash recovery.img so able to access recovery again. In there it says qe 1/1, which apparently means its rooted. I ran house of moto so it should have unrooted. Dont know why it didnt, and now im effed.
[Droid Ultra Original Android Development] Summersett:
I thought I did that as well, but I'm now on 4.4, WP off, and no root (although recovery says qe 1/1 as well, so that's weird...?)

Are you sure you're trying to sideload the 4.4 update? You have to do it twice; once for recovery and once for the boot image.
[Droid Ultra Original Android Development] coronanlime:
I think so. The link from post 22.

Have to sideload it twice? If I can get it sideloaded at this point with no root Ill be happy.
[Droid Ultra Original Android Development] Summersett:
Root Checker Pro says:

Does this mean I have a shot at root still, if /system/xbin/su has root? Anyone have any expertise in this or know where to ask?
[Droid Ultra Original Android Development] coronanlime:
I cant even sideload it now. says installation aborted.
[Droid Ultra Original Android Development] Summersett:
Meaning flash it once and it should do its thing and send you back to the new recovery. Flash it again and that will update you to 4.4. Or try doing it from internal memory if the sideloading is seeming to give issues.
[Droid Ultra Original Android Development] coronanlime:
There a way to push the file to the sdcard from fastboot?
[Droid Ultra Original Android Development] Topsnake:
Not sure. Manually flash the sys, boot, recovery etc. From the update

Maxx'd out Kit Kat
[Droid Ultra Original Android Development] rlmesq:
I just connected my phone to my computer, dragged & dropped update.zip to the SD card, booted to recovery & used "install update from SD card."

---------- Post added at 07:26 PM ---------- Previous post was at 07:15 PM ----------

Did your phone reboot into 4.4? Do you see a superuser app in the drawer?

The OP is a little confusing because it seems to imply your phone will reboot after you run the final Slap commands in ADB shell and toggle Bluetooth.

My Maxx (and girlfriend's Mini) didn't automatically reboot. I rebooted, ran the ADB command to verify WP was still off, then downloaded Super SU from the market.

When I launched Super SU, it prompted me to download & install the binary (as it does with any new installation), and I had root back.
[Droid Ultra Original Android Development] socobandit:
I had to copy install.sh from the slap my moto zip to my sdcard. it let me do adb shell, then the next 2 commands, but when i tried the last command, it says "can't create /sys/kernel/uevent_helper permission denied. tried several times, not sure whats going on here. i also downloaded super su and it says it doesnt have the binaries and cant install them. write protection is still 0. any help?
[Droid Ultra Original Android Development] Topsnake:
you shouldnt of had to copy it to your sd card if you set it up right. Did you run all of the commands in step 4?
[Droid Ultra Original Android Development] Summersett:
You should be able to "adb push update.zip" or whatever the file is called to move it to your phone. I would highly recommend copy/pasting to your phone while plugging it into your computer through USB, but if the computer doesn't recognize it since you're softbricked, you can try through adb.

It rebooted to 4.4, but I have no superuser app. If I go install SuperSU from the play store it tells me I don't have the binary available when I try to run it. I couldn't finish the slap commands in ADB shell, though, because I did a data wipe after flashing 4.4 before rebooting (at least that's what I think messed mine up...)

Welcome to the club! Are you on 4.4 without root now?

Also, I just noticed late tonight that if I try uninstalling an app, my phone reboots! I can only install, not uninstall apps as of right now! Anyone else have this issue?
[Droid Ultra Original Android Development] Caseyk621:
Saw that some had this problem. Here:

https://forums.motorola.com/posts/944892be33?page=16#

Not sure what the fix was. The poster just said he got it fixed and to PM him.

Sent From My KitKat Ultra
[Droid Ultra Original Android Development] Metfanant:
something went wrong, or you skipped a step if you had to copy anything to your sdcard...
[Droid Ultra Original Android Development] coronanlime:
Yeah I'm soft bricked so I can't access adb or boot up for drag and drop. So I guess I'm waiting for the sbf file.
[Droid Ultra Original Android Development] socobandit:
Yep. first line, abd shell, no problem. got the cursor with the $, AFTER I copied install.sh to my sdcard, the next 2 lines went fine, but the last line in step 4, it keeps telling me permission denied. I still have wp off, so I'm hoping I did something right.

---------- Post added at 06:53 AM ---------- Previous post was at 06:41 AM ----------

I followed each step. I was rsd'd back to stock 4.2.2. I then used RockMyMoto, followed by MotoWPNoMo, then rsd'd back to stock 4.2.2. Did step 1 pushing the slapmymoto.jar. DId the next step with telnet, , did step 3 with telnet. then applied the update. I believe the update is where i got my issue. when i tried to update with update.zip, the first time it came up with a 0x56 error, and wouldn't let me back into recovery. sh*t...i rsd'd back to 4.2.2, and didn't do the slapmymoto steps again. Sorry for wasting everyone's time...I should've known to redo those steps, but it was late and i was tired and not paying attention. Looks like i'm stuck w/o root unless jcase comes up with an exploit.
[Droid Ultra Original Android Development] lkevinl:
Droid Maxx, I'm on 4.2.2, 12.15.15.obake-maxx_verizon

I am rooted with the original root method from JCase, MotoRoot1.1, from here:

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

That method worked fine because I was just interested in the hotspot hack. Am I the only one still on that root method?!?

Anyway, how are the OP steps different for me coming from this root method?

Thanks in advance!
[Droid Ultra Original Android Development] BladeRunner:
My guess is you'll need to root with RockMyMoto. I doubt MotoWpNoMo will work with the motoroot
[Droid Ultra Original Android Development] socobandit:
Whats the worst that would happen if i tried to run slapmymoto now that im on 4.4? I know it probably wont work, just curious that since i have the write protection still disabled, maybe it'll work?

NVM...can't connect to the phone with telnet. Pretty sure telnet is absolutely necessary to get root.
[Droid Ultra Original Android Development] allquixotic:
I'm on:

System version 12.7.7.obake-maxx_verizon.Verizon.en.US (this is either the factory fw, or the first mini-OTA before the camera update)

Baseband version MSM8960PRO_BP_2323.020.90.00R (from the camera update)

Hotspot SQL tweak is in place

Custom boot to enable write protect is in place

Rooted with PwnMyMoto

Updater apps frozen by Titanium Backup so I don't get daily OTA prompts

I do NOT have Safestrap

Is there any way for me to get to KitKat without factory resetting with RSD Lite and losing all my apps and data?

I guess I'd have to:

Undoing my changes #1: Un-freeze all the stock apps I've frozen

Undoing my changes #2: Obtain an unmodified copy of the sqlite db (from where?) to replace the one with the entitlement check bit flipped?

Undoing my changes #3: Flash the old radio?

Getting up to date?: Update to the Camera OTA (12.15.15)? (How?)

Run MotoWpNoMo

Run SlapMyMoto

Take the OTA

Do this

Am I missing something from the above list? Has anyone in a similar situation tried it? Does the boot-into-write-protect bootloader modification matter?

Seems like I have a lot of work to do if I want to keep my data. I'd love to try it, if anyone thinks it can be done, but my fallback plan is to back up my data/apps like crazy, RSD to the camera update, then do Rock -> WpNoMo -> Slap -> OTA -> tether. Would prefer to avoid that if possible...

Thanks!
[Droid Ultra Original Android Development] Caseyk621:
You can use House of Moto. Works like RSD to get back to stock with an option to keep data.

You should unfreeze UPDATER apps before using House of Moto w/data save as you'll loose root and one of the apps gets stuck frozen. (Happened to me.) Other apps you can leave frozen.

You can then update to 12.15.15(camera update.) And go about rooting. Also there is a separate thread around here for tethering on KK. The entitlement hack won't work.

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

http://xdaforums.com/showthread.php?t=2578410
[Droid Ultra Original Android Development] fuzzychinsagrero:
So on safestrap 3.65 it will say write protection enabled I can't select install or uninstall recovery. Then it says reboot to recovery and reboot to write protection off mode. Would that be the same as motowpnomo? If so could we just restore the camera update then continue with the exploit?

Edit: I did it and now it says state: installed. And the safe system now says now active, now I can select install or uninstall the recovery.

Anyone has any idea guess I never paid attention to that.
[Droid Ultra Original Android Development] bigv5150:
The reason you didn't see install or uninstall is because you didn't have WP off when you booted to recovery WP is off.
[Droid Ultra Original Android Development] fuzzychinsagrero:
So my question remains do I still have to use motowpnomo? Or can I just run the exploit? Not looking for shortcuts just wouldn't want to do something that I could skip.
[Droid Ultra Original Android Development] bigv5150:
That is answered in the first post didn't think I needed to answer that one.

First you must use MotoWPNoMo, if you haven't then you will need to. Use RockMyMoto to gain root, then use MotoWPNoMo, and then restore to the 4.2.2 Camera update.
[Droid Ultra Original Android Development] fuzzychinsagrero:
Read through it bud but not sure if you read my post #136.
[Droid Ultra Original Android Development] AreOh:
Just from going through a few pages this process to gain root and update to 4.4 seems really confusing and a lot of work. I'm still on 4.2.2 and would like to update and gain root mainly for font installer and xposed framework and gravity box which I just learned about. Don't want to brick my phone in the process, though. Only at a time like this do I miss being on Sprint so I could watch a qbking YouTube for the walkthrough steps for this.