yashsingh1/xdaforums huggingface dataset:
[Droid Ultra General] Caseyk621:
This maybe?

OK here it goes. A fix for the bricked. This is not a sbf or fxz file. I do not have permission to release yet. Can not loose my privilages

http://d-h.st/RR4

Try it and let me know the results

Sent From My KitKat Ultra

---------- Post added at 06:16 PM ---------- Previous post was at 06:15 PM ----------

Got that from this post....

Sent From My KitKat Ultra
[Droid Ultra General] ks2332:
Yeah the file works for both and its the link link above justbfollow his and mine instructions
[Droid Ultra General] wallace342:
Glad to see you got yours working. For those of you who can't access recovery then flashing the recovery.img using fastboot will fix your problem.

If you have the problem with "Partition (boot) security version downgraded" or "install-recovery.sh has unexpected contents", then flashing the recovery.img will likely not fix your problem. The latter can be fixed if you can still get into the system with root access and replace install-recovery.sh with the factory version.
[Droid Ultra General] pj1980:
the force update file for the ultra will work for the maxx too? just want to confirm although i don't see how i could mess up my phone any worse than it is now.
[Droid Ultra General] wallace342:
The recovery.img file will work for both phones (just restores stock recovery, which is the same on Ultra and Maxx), but I'm not sure that the zipped up update package works for both phones.
[Droid Ultra General] rmoney:
Tried that fix (that r00st3r9109 posted) on my Maxx and got this error on the first step.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
error: cannot load 'recovery.img': No error

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.902s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.147s

C:\Program Files (x86)\Minimal ADB and Fastboot>

So I decided to push on with the instructions anyway and this seemed to work.

Anyone know of any possible side affects? Looks like I'll be waiting a bit for root as well.
[Droid Ultra General] Caseyk621:
Which fix are you trying? What recovery are you trying to flash?

Sent From My KitKat Ultra
[Droid Ultra General] wallace342:
Can you currently get into recovery? If so, flashing this will likely not help anyways. If not, then you do need to do this.

Two things:

1. Make sure you are running "Minimal ADB and Fastboot" as administrator, as I have seen strange issues surface if you don't.

2. More importantly, try to use your Motorola microUSB cable if you aren't already. I have encountered strange errors using RSD, fastboot, etc. I the past when using third party, lower quality cables.

3. You could also try flashing the recovery.img that is inside the Kit Kat OTA zip file.
[Droid Ultra General] rmoney:
Sorry, edited my old post a bunch of times as things slowly started working.

But I used this fix http://xdaforums.com/showpost.php?p=48692779&postcount=220. Got the error on the first step, continued into Recovery anyway and the rest worked according to the instructions. Not sure if that error is expected, but it seemed to work.
[Droid Ultra General] Bam_thwok:
Can you elaborate on the fix to the "Partition security version downgraded" problem?

edit: ah, nevermind. Looks like all I had to do was get back into recovery (vol up + power from the "!" droid) and apply the update a from zip a second time. Looks like it's patching.

And now we wait for a root.
[Droid Ultra General] wallace342:
I think the only fix to that problem is to reflash boot.img from KitKat to the boot partition. I don't know of a copy of that floating around at the moment, but if we can get the FXZ/SBF files, it will have the boot.img in it that is needed. The update zip has a boot.img.p in it, but that is only a patch file, rather than an entire partition image so that won't work.
[Droid Ultra General] Bam_thwok:
Didn't seem to matter. I just needed to get back into recovery from fastboot - which was not very straightforward - to run the update.zip from SD card again. Android updated to 4.4 without a hitch after that.
[Droid Ultra General] brianmagicr:
When do you guys thing the fxz/sbf file will be up on Sunday?
[Droid Ultra General] r00st3r9109:
Well i am glad my fix is kinda working on some devices. I will be posting the sbf tomorrow night. I'm sorry I posted the wrong recovery file in my file but I posted the new recovery in this forum. Try pushing the new recovery instead of the one included and go from there. Everything should be fine.
[Droid Ultra General] Jay_P11:
So we use your fix for the Ultra instead of the original link for the Maxx one? I'm a bit confused. This is my only phone I have right now, and I won't be able to get a new one if something goes wrong in the update process. Stock and unrooted, should I attempt the update.zip process for your Ultra fix? I don't want to wipe any user data as well.
[Droid Ultra General] Brenardo:
If your phone is currently working I would highly suggest waiting til a confirmed fix has been uploaded and available to all.
[Droid Ultra General] Jay_P11:
I became impatient and used the "Droid Maxx KitKat OTA.zip" by going about the steps that so many here have confirmed.. Happily on KitKat, smooth as ever. One thing that tripped me up for a good half hour was the fact that the update zip was inside of the downloaded zip, while I was trying to flash the downloaded one for so long. I can confirm that the Maxx file works on a 100% stock unrooted Droid Ultra.
[Droid Ultra General] r00st3r9109:
The ultra and maxx are the same phones. This fix will work. The ota update that is included is for either phone. Its all the same.

If you have a working phone, do not take an update or try to update.
[Droid Ultra General] lkevinl:
I have a Maxx with the latest update and I'm rooted with the original root method that doesn't change recovery, just makes system Read/Write. What do I need to do to update? Can I just unroot and accept the update or update via the ZIP file? If so, after updating, can root be restored or will I need to wait for a new exploit?

P.S. I'm really only interested in mobile hotspot, so the original root method was fine for me. Seems like the newer recovery method makes updating more of a pain, no?
[Droid Ultra General] jfriend33:
I am glad you have been posting about the test. Makes me very paranoid to accept any updates as I've read nothing but problems across forums. Also due to lack of development on this device I've read so many people begging and whining for kit kat. I'm like seriously, you need a Nexus 5 if you want that privilege....
[Droid Ultra General] Topsnake:
I wouldn't take the chance. Just FXZ, run rockmymoto, then motowpnomo, fxz, slapmymoto, ota, run the hotspot exploit i posted in development

Maxx'd out Kit Kat
[Droid Ultra General] wallace342:
SBF coming in the next few hours then?
[Droid Ultra General] brianmagicr:
One can only hope!
[Droid Ultra General] lkevinl:
Clarification, when I said "latest update", I meant 4.2.2, but I think you understood that.

So, isn't the phone basically back to stock without root when I remove the original root method by JCase? When you remove that root method, you're back to read only system and no root/SU. That's all I had to do when I upgraded to 4.2.2 and it worked fine... no need to do anything with Recovery.

So, I'm thinking unrooting this root method should allow me to take the 4.4 update, BUT, I'm guessing root will no longer work.
[Droid Ultra General] Topsnake:
Well heres your option, if your theory is wrong, youll brick. If y use the method i said, you wont. Your choice

Maxx'd out Kit Kat
[Droid Ultra General] Metfanant:
Basically...if you update to 4.4 without using the JCase method root is gone...

And for the time being there is no direct root exploit for 4.4 so you will lose the ability to root
[Droid Ultra General] wallace342:
All I want for Christmas is a KitKat SBF....
[Droid Ultra General] brianmagicr:
You and me both.
[Droid Ultra General] wallace342:
...then I could have a working Droid Maxx!
[Droid Ultra General] coronanlime:
Glad I found this thread, or at least this current discussion. Unfortunately I tried JCases method root and for the first time since the OG droid I bricked the phone. I can get recovery, but after the first failed sideload, it now will just abort. Desperatly awaiting SBF or FXZ.
[Droid Ultra General] brianmagicr:
Is it time to bestow upon to us the secret contents of your treasure chest, that shall grant us safe passage to the wondrous world of Kit Kat?
[Droid Ultra General] wallace342:
Still waiting for that SBF. Tomorrow afternoon has passed....
[Droid Ultra General] nocaldawg:
What is SBF?
[Droid Ultra General] brianmagicr:
It is a file that contains the image files to restore the phone.
[Droid Ultra General] nocaldawg:
So this is for those who bricked going to 4.4 and allows them to go back to 4.2
[Droid Ultra General] Jaocagomez:
Don't get anxious that sbf is coming, to taste kit kat sweetness before Christmas (please white theme and kit Kat dialer)
[Droid Ultra General] wallace342:
No, it is for those who bricked during the update to get a completely clean Kit Kat install
[Droid Ultra General] brianmagicr:
There is an sbf/fxz file for 4.2.2, but the one we are looking for is for 4.4. My phone partially took the update meaning I can't EVER go back to 4.2.2.
[Droid Ultra General] nocaldawg:
Thanks...appreciate the insight and help in learning about this.
[Droid Ultra General] coronanlime:
Once the SBF is out, we flash it through HouseOfMoto and select RSD instead of fastboot right?
[Droid Ultra General] brianmagicr:
I'm not sure. I've only ever flashed them manually from fastboot on my mac.
[Droid Ultra General] wallace342:
Or you can just use RSD Lite directly
[Droid Ultra General] brianmagicr:
I think you can do that.
[Droid Ultra General] wallace342:
I know you can with the 12.15.15 update
[Droid Ultra General] brianmagicr:
My thought was that so far nothing about kit kat on the Ultra/Maxx has been that easy. Fingers crossed it will be.
[Droid Ultra General] wallace342:
I'm just crossing my fingers that we get the file
[Droid Ultra General] brianmagicr:
We will....EVENTUALLY!
[Droid Ultra General] coronanlime:
Figured. It has been a long time since I used an SBF. Can't even remember what phone I used it for. It wipes everything right? No chance of keeping data? (not like I will have a choice if it does a full wipe).
[Droid Ultra General] wallace342:
If you take the line out of the XML file that wipes the userdata partition, it should keep your apps, etc.
[Droid Ultra General] jrgilbert79:
Friggan FIXED!!!!

Was getting Security Downgraded! Fastboot reason: boot failure!

I used the files that the supposed MOTO guy released. I finally unpacked the update.zip in his files and did a fastboot flash recovery recovery.img. from within it instead of the one that was outside of the update.zip directly into the minimal adb fastboot directory and when I flashed it and booted into recovery it finally worked. Granted I cant sideload adb anything so as long as you have the original update.zip in your sd card your fine....luckily the same file that EFF'ed my world update.zip on the sdcard so I pushed it again. and it worked flawlessly. SO ...

1. download http://d-h.st/RR4

2. unzip the update.zip inside...or copy out the recovery.img (inside the update.zip) to the minimal adb directory,

3.fastboot flash recovery recovery.img

4.fastboot reboot-bootloader

5.highlight recovery and hit Vol up

6. hold vol up for 10-15 seconds and tap the power button. If you see a real recovery your feelin' pretty sexy bout right now!

7.try to apply the same update.zip from sd card (poop that broke it to begin with.)

8. If you are lucky like me 4.4 - 3 days later

9. As a precautionary measure I booted back into fastboot and reflashed the good recovery.img just so future OTA didn't blow up since the update.zip form inside this forum was what broke recovery to begin with, (that's the same thing we have to re-flash)

10. Drink heavily and brag about this to your spouse who doesn't care.

P.S. I did not delete any of the partitions or wipe user data or cache...didn't lose a single picture or text.

:highfive:
[Droid Ultra General] cj2566:
THIS WAS AWESOME!!!

Thanks bro!
[Droid Ultra General] coronanlime:
Ughh, I wish I had the file on my phone. Can't get the update onto the phone because I can't boot up. Fastboot doesnt have a method to push the file onto the sdcard partition. And sideloading fails everytime.
[Droid Ultra General] fenixjr:
Does anyone have access to the DROID MINI update.zip? my wife's mini has been bricked since friday.
[Droid Ultra General] wallace342:
I gather then that this won't work if you don't have a copy of the update already somewhere on the phone? I can't boot my phone so I can't access the file system to put a copy of the update on the phone, so adb sideload is my only option.

I wish we could just get the damn SBF we were promised by yesterday afternoon. I would love to know what the hold up is. Then we could all just give this thing a rest.
[Droid Ultra General] jrgilbert79:
Yes sir you are correct...If you wiped all the data through fastboot I have no idea how to get the update.zip on the phone. I would check on pushing things with fastboot. Technically fastboot has some adb interface...I just do not have tons of expertise using it. I also do not know if you can use an otg cable with the stock recovery. GL and apologies to anyone who listened to the guy who said to format user data :( sorry guys. My goal was to fix it without losing everything.
[Droid Ultra General] jrgilbert79:
OK guys try this...

Follow my post above until you get back in recovery.

Whle in recovery try to run:

1. adb devices (hopefully you see serial # recovery)

2. adb sideload update.zip \sdcard or adb sideload update.zip \sdcard\update.zip (thanks for pointing out sideload)

3. if that works follow the guide to rerun the update.zip (at this point you can use the update.zip provided by the link in my post above.

Note. This assumes that the MOTO stock recovery can interface with ADB.you cannot do this from fastboot until you get the recovery working first.

let me know:good:
[Droid Ultra General] chevyrado14:
stock recovery only allows adb sideload. which you can use to flash the udate.zip using command

adb sideload update.zip
[Droid Ultra General] jrgilbert79:
Sorry yes in the first line of my post I stated that this was working for Security Downgraded borks...I dont know what to tell you since I was stock I got this error and not the recovery.sh
[Droid Ultra General] wallace342:
I agree, for someone who was never rooted, if you are getting the "Partition (boot) security version downgraded" error, sideloading the update using ADB sideload from stock recovery should work. This is because the update actually patches the boot.img anyway to upgrade it, hence is why there is a boot.img.p file inside the update.zip.

For someone who was rooted, if you can still boot into the OS with root access and system r/w, you can replace the install-recovery.sh with the stock version of the file and you should be able to accept the update if you were previously getting the "install-recovery.sh has unexpected contents" error. If you can't boot into the OS anymore (or have lost root or system r/w), then I think your only fix is to wait for an SBF which will replace the entire contents of the system partiton, regardless of what it currently holds. The SBF would also replace the recovery partition, so as long as you can still get to the bootloader menu, the SBF should fix any problems with recovery as well, once it arrives.
[Droid Ultra General] jrgilbert79:
Thanks! Between this and my instructions on the other error no one except those rooted who lost root r/w should be without a phone this christmas. On a side note those who were rooted without great knowledge of prepping their device should have ever tried an OTA. Its no joke to bork your device because you didnt wait for a safe zip or instructions on the official OTA.

Sorry for sounding harsh but you shouldnt try this in your first rodeo.
[Droid Ultra General] luisdev:
I have a similar problem with the droid maxx (caused by 'upgrade kitkat 4.4 ota) the error message is as follows "partion(boot) security version downgraded"

the recovery will not start and gives me error on partition. I tried with rslite with the stock version 4.2.2 but I could not flash. Give me instructions how to solve?
[Droid Ultra General] jrgilbert79:
you cant really make it any worse did you install minimal adb and fastboot? did you try to run the command fastboot flash recovery recovery.img (you must copy the recovery.img into the minimal adb fastboot directory on your computer; where you are running the commands)?

if you can get back into recovery you have a shot especially if you have not formated your user and cache partitions yet. I have detailed instructions a page or so back.
[Droid Ultra General] papercut19:
tried it all

I've tried every fix on here and can't get this thing to go. In a fit of anger not thinking about the update.zip still being on the phone i wiped all data so that option is gone. When I try to fastboot flash the recovery.img inside the update.zip file from the droid ultra force update download it returns with an error <bootloader> preflash validation failed. I have no problem flashing the recovery.img on the outside of the update.zip file and I also have no problem flashing the recovery.img from an old 4.2.2 fxz file I had laying around. Once I get into the recovery i can not sideload anything through adb. Am i missing something? Am i totally screwed till the fxz comes out?
[Droid Ultra General] wallace342:
Not sure if you were directing your comments towards me, but if you are, it is far from my first rodeo. I went through the unroot process just like I do on all of my devices before taking the OTA, but in this instance I apparently didn't go far enough (probably because of my install-recovery.sh contents). Regardless, that's what keeping old phones is for in the meantime. Comments like yours above do nothing to help anyone having problems. I think anyone who goes about rooting their phone, etc. is well aware that sometimes things aren't going to be smooth sailing as a result. Besides, screwing up a device and figuring out how to bring it back from the dead (and why that specific method worked) is one of the best ways to learn the ins and outs of Android.
[Droid Ultra General] edon82:
I installed the updat.zip and have a little different problem than most stuck on moto screen like everyone. But when i boot into fast boot and hit recovery it says " Failed to hab check for recovery : 0x56 boot up failed ...any ideas?
[Droid Ultra General] socobandit:
This is where i got stuck too...had to use rsd to flash back to 4.2.2. if you're using slapmymoto to get and keep root, you will have to follow all the slap my moto steps again after the rsd. I couldnt get house of moto to work, so i used rsd, didnt even think about slapmymoto since i already did it, and now im on 4.4 with no root.
[Droid Ultra General] ks2332:
I knew we weren't getting that sbf
[Droid Ultra General] jrgilbert79:
I had the same thing when I tried recovery. On normal boot I had fastboot reason: boot failed. Security Downgraded. I was still successful with the recovery.img from the zip posted from the Motorola guy as a fix. He didn't really give instructions on how to make it successful though so that's what I tried to do.
[Droid Ultra General] wallace342:
What do you mean "fastboot flash the recovery.img inside the update.zip" vs "flashing the recovery.img on the outside of the update.zip"? If you are trying to just flash the recovery, the easiest way is to pull the recovery.img out of the update.zip file, put it in the same place as your fastboot.exe, and run "fastboot flash recovery recovery.img".

In regards to sideloading through ADB, you should be doing the following:

1. In the bootloader menu, select "Recovery".

2. When the picture of Andy comes up, hold on the volume up button and press the power button, then release both. This should give you the recovery menu.

3. Select "apply update from ADB".

4. At this point, if ADB is installed correctly (as well as the device drivers), you should be able to run the command "adb devices" and see one device in the list called "recovery". If you don't see this, you likely have an ADB or a driver problem, but mostly likely drivers. Check device manager to make sure you don't have an unknown device in there, which would indicate the drivers were not installed.

Are you seeing your device when you follow the above instructions and run "adb devices", or not? If not, you will not be able to sideload until you get this resolved. Let us know.

---------- Post added at 01:45 PM ---------- Previous post was at 01:42 PM ----------

I guess we will have to wait on someone else to leak the SBF...
[Droid Ultra General] jrgilbert79:
I wasn't directing them toward anyone in particular. Just a reaffirmation for everyone in the future to hold off using official files particularly beta equivalent. No disrespect it just blows my mind that the OTA doesn't have a precheck that stops if it isn't 100% ready to rock. This is more Moto and VZN's fault than anyone's seeing that it Eff'ed up completely stock phones as well.
[Droid Ultra General] papercut19:
I am not seeing my device listed at all havent been able to since I started this I can only do fastboot commands. I knew the drivers were going to be an issue so I downloaded the most recent one from the moto website but apparently thats not working for me. can some one point me in the direction of where to get the "correct" drivers and we'll see where that gets me. ( and about the different recovery.img 's when you download the droid ultar force update.zip from a few pages back the first thing you come to inside that zip is a recovery.img and and update.zip file. the first recovery.img works but if you go inside the update.zip file and pull out the recovery.img file in there it will give me an error)
[Droid Ultra General] wallace342:
I would agree. You would think at the very least these updates could roll back their changes if the update is successful, rather than leaving a device in a half updated state.

---------- Post added at 02:29 PM ---------- Previous post was at 02:27 PM ----------

Once you enter adb mode from recovery (using "apply update from ADB") per my previous instructions, with the phone plugged in, if you go to Windows Device Manager, do you have any unknown devices? If so, I can walk you through having it use the correct driver. You should have downloaded the latest version of Motorola Device Manager prior to doing this, which will install the latest Motorola USB drivers.
[Droid Ultra General] danman7:
More than likely, no. There does not appear to be any way to go back to 4.2.2 once the upgrade has started. There is a security check that will not allow you to flash an older version of the img files.
[Droid Ultra General] luisdev:
the fastboot command to reinstall the 4.2.2 recovery fails, are not practical thing wrong? I must have (the file recovery I took what I had to take the OTA 4.2.2 or 4.4 is irrelevant!?)

fastboot boot recovery.img (remote failure)
[Droid Ultra General] ks2332:
Try fastboot flash recovery recovery.img should do the trick