[Droid Ultra General] wallace342:
To elaborate a little more on my previous post, if the XML file inside the SBF/FXZ looks like this:

<?xml version="1.0"?>

<flashing>

<header>

<phone_model model="PRO_CFC_VZW" />

<software_version version="obake-maxx_verizon-user 4.2.2 SU1-15 3 release-keysMSM8960BP_2323.024.95.00R" />

<interfaces>

<interface name="AP" />

</interfaces>

</header>

<steps interface="AP">

<step operation="getvar" var="max-download-size" />

<step operation="oem" var="fb_mode_set" />

<step operation="flash" partition="partition" filename="gpt.bin" MD5="E032A4F7B5570725DC84E18980E1D5CB" />

<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="6F56591C95C2498B9B73AEB33383B2B4" />

<step operation="flash" partition="logo" filename="logo.bin" MD5="8AD54CC4A69CBA3D58CAA320BB6C8E5B" />

<step operation="flash" partition="boot" filename="boot.img" MD5="3235A29573125C5C0F4C07B982E88BE4" />

<step operation="flash" partition="recovery" filename="recovery.img" MD5="370211976182FCA5D142B560F2B9211D" />

<step operation="flash" partition="system" filename="system.img" MD5="2E9D8737E05297D7AD81ECC1E9E5B82C" />

<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="DFCD1DD58638CF1A53B8225281321E9A" />

<step operation="erase" partition="modemst1" />

<step operation="erase" partition="modemst2" />

<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="38A58E1C1F0503DD12B8AC26B10F2304" />

<step operation="erase" partition="cache" />

<step operation="erase" partition="userdata" />

<step operation="erase" partition="customize" />

<step operation="erase" partition="clogo" />

<step operation="oem" var="config carrier vzw" />

<step operation="oem" var="fb_mode_clear" />

</steps>

</flashing>

Then you just need to remove this line:

<step operation="erase" partition="userdata" />

And it will not erase the "userdata" partition, which should keep your apps.

---------- Post added at 10:57 AM ---------- Previous post was at 10:46 AM ----------

I do not believe you can push files with fastboot, since I don't think you can really "manage files" per se from the fastboot interface. You can go into recovery and go to ADB mode and do some more stuff that way, but I still don't think this will work for my issue because my "install-recovery.sh has unexpected contents" is still going to happen regardless of where the update is installed from. The updater-script in the update.zip checks the MD5 of the install-recovery.sh file and if it doesn't match what it expects, it will abort the update. If you pull the update.zip apart and look at the updater-script file (/META-INF/com/google/android/updater-script), you can see where it does this in updater-script. This is the case regardless of whether the update is sideloaded or installed from an SD card, as it uses the same updater-script either way.

Either way, I'm not too worried about maintaining my data (everything important on my phone has a copy elsewhere as well), I just want to get the device working again so I can start using it. My Maxx was too damn expensive to be functioning as a glorified paperweight. I loathe the idea of getting a replacement device because I have had bad luck with the quality control of Verizon's "certified like new" devices, and I know my current device from a hardware standpoint is flawless. That is why I am waiting on the SBF instead because I know it will fix the problem and I would like to keep my device.

r00st3r9109, where have you gone?