58 replies to this topic

[ltdan]

Ok think i figured out what might actually be causing this, i think it's an incomplete fastboot command, coz at the end of rsd lite and Matt's utility, where the phone is supposed to reboot, it just blanks out then brings the "recipe failure" up, i'll look at another xml file like from the bionic, see if there's a difference, if anyone knows a possible fix or xml edit for this be really nice, it sorta makes sense to me, coz it's only at that point of the flashing where it errors, right where it's supposed to reboot, hence the boot looping then, rsd says "PASS" coz the command initiates but don't think it knows that it didn't complete, any ideas on this or other ones lemme know, and thanx John for your input on the boot lock, i'll leave that alone, right now got the phone up and running with eclipse, but see what i can figure out today on this with a possible xml edit, thanx again to all, really appreciate your time, sincerely, rod

 

here's a copy of the xml code from my bionic xml file and the xt912 file, can't tell if anything is out of order on the xt912...

 

this is the cdma_spyder_9.8.20-72_VZW-16_1ff

<?xml version="1.0" encoding="UTF-8"?>
<flashing>
  <header>
    <phone_model model="SPYDER" />
    <software_version version="9.8.2O-72_VZW-16" />
    <interfaces>
      <interface name="AP" />
    </interfaces>
  </header>
  <steps interface="AP">
    <step operation="flash" partition="mbm" filename="allow-mbmloader-flashing-mbm.bin" MD5="55d703d1d8d8631f31be89a6069ad68e" />
    <step operation="reboot-bootloader" />
    <step operation="flash" partition="mbmloader" filename="mbmloader.bin" MD5="42f7110de49d6d28ea0540f1c02f9f1b" />
    <step operation="flash" partition="mbm" filename="mbm.bin" MD5="f541f64f56739d65c19557e33f8aef3c" />
    <step operation="reboot-bootloader" />
    <step operation="flash" partition="motoboot" filename="motoboot.img" MD5="a2517202dd87b95e63bc52f092449c10" />
    <step operation="reboot-bootloader" />
    <step operation="erase" partition="cache" />
    <step operation="flash" partition="logo.bin" filename="logo.bin" MD5="cd111cc7b675e62a7d85a50632fb88e8" />
    <step operation="flash" partition="devtree" filename="device_tree.bin" MD5="04e2f24447783a0ff32e86e0dca1d0c0" />
    <step operation="flash" partition="system" filename="system.img" MD5="b2b52f5917990ee52b5ec78bdbbc5167" />
    <step operation="flash" partition="boot" filename="boot.img" MD5="4b041e7af8bd8ed30610d7c6eb18df39" />
    <step operation="flash" partition="recovery" filename="recovery.img" MD5="9a73f1b364990cf326324db1f856fe50" />
    <step operation="flash" partition="cdrom" filename="cdrom" MD5="fd1d40c2b40f0222eb8ef98aeb3aa87c" />
    <step operation="flash" partition="preinstall" filename="preinstall.img" MD5="fb0c510d318004120ea3269e39de1c1d" />
    <step operation="flash" partition="radio" filename="radio.img" MD5="e68433c86794d0439363baf7bcf303f5" />
  </steps>
</flashing>

this is the VRZ_XT875_5.9.905.Verizon.en.US_CFC

<?xml version="1.0" encoding="UTF-8"?>
<flashing>
  <header>
    <phone_model model="TARGA" />
    <software_version version="5.5.1_84_DBN-74" />
    <interfaces>
      <interface name="AP" />
    </interfaces>
  </header>
  <steps interface="AP">
    <step operation="flash" partition="mbm" filename="allow-mbmloader-flashing-mbm.bin" MD5="f6102e4b34c74cfefd5e80151a6913ff" />
    <step operation="reboot-bootloader" />
    <step operation="flash" partition="mbmloader" filename="mbmloader.bin" MD5="b0c30799c8509c4d66599550e3fbdd82" />
    <step operation="flash" partition="mbm" filename="mbm.bin" MD5="da0b9ae7f38048a2987e0ae24593fb4b" />
    <step operation="reboot-bootloader" />
    <step operation="flash" partition="cdt.bin" filename="cdt.bin" MD5="fd8c44b060415dfd963fa870ae7a4f35" />
    <step operation="erase" partition="cache" />
    <step operation="erase" partition="userdata" />
    <step operation="erase" partition="emstorage" />
    <step operation="flash" partition="lbl" filename="lbl" MD5="239bbc49a9cdb329577074ba60bbf1e5" />
    <step operation="flash" partition="logo.bin" filename="logo.bin" MD5="06c07c2970460a4e656a3206859a3617" />
    <step operation="flash" partition="ebr" filename="ebr" MD5="4c6df9afcd64661036a982e03eb1aa1a" />
    <step operation="flash" partition="mbr" filename="mbr" MD5="712e3e3757219ecfd925eb43be14f944" />
    <step operation="flash" partition="devtree" filename="device_tree.bin" MD5="2404a4f245f1da389d3422d0d59be24a" />
    <step operation="flash" partition="system" filename="system.img" MD5="8e306ac58dd4fcf01566c517eabc098d" />
    <step operation="flash" partition="boot" filename="boot.img" MD5="b64b38a48897c51fe229cf80a095d235" />
    <step operation="flash" partition="recovery" filename="recovery.img" MD5="ce9ee505c7fc708f7394617907ae5694" />
    <step operation="flash" partition="cdrom" filename="cdrom" MD5="6bdf130ecaa5183c0e463d2f3fa5d966" />
    <step operation="flash" partition="preinstall" filename="preinstall.img" MD5="f7f2ff434d2b0c819c1e28744d1b4d01" />
    <step operation="flash" partition="emstorage" filename="emstorage.img" MD5="953494fd0d356f25a58842f1a41b132d" />
    <step operation="flash" partition="webtop" filename="grfs.img" MD5="c9502cd8fd6fa7206c64e4dae3ed9b50" />
    <step operation="flash" partition="radio" filename="radio.img" MD5="683184cc2522ba00e6a0c38d321a8806" />
  </steps>
</flashing>

 

 

09.24.13 update

ok, called motorola, they glazed over on this, so gonna just let this phone go and move into the xt926 model, that's the fix for the recipe failure 





 

[brob8576]

I believe the repair was found here: 

Please Login or Register to see this Hidden Content

 

I had the same problem, and this resolved it in less than a minute!

[Memnoch73]

I believe the repair was found here: 

Please Login or Register to see this Hidden Content

 

I had the same problem, and this resolved it in less than a minute!

 

Appreciate the input man but the recipe failure is different than just a standard flash failure and is not fixed but just flashing a boot logo.

[cmh714]

I for one have never ever seen a fix for recipe failure, and I have searched long and hard trying to assist others.

[ang]

I was able to recover from the Recipe error on my Droid RAZR MAXX.  After trying everything I've read on every post out there and almost quitting after the last post from a trusted moderator, I succeeded with the following steps:

 

1) Fully charged phone

2) Used Motorola cable

3) Upgraded driver to latest version 2.4.5

4) Used VRZ_XT912_9.8.2O-72_VZW-16-5_CFC.xml

5) Used RSDLite 5.7 with the following settings:

1. Flash options: Restart after flexing and TI Blank flash
2. Use image files and delete files on exit

 

Phone connects/disconnects multiple time on flash and then finally does a full reset where you will see droid with "blue electrical work animation."  RSDLite waits for phone to come back but it never will because after the animation the phone does a last reboot into the new image instead of into fastboot.  I've done multiple boots since and every time it works fine.

[cmh714]

Glad youre back, and yes this is the first I have ever seen someone recover from that error message. I hope it works for others. Thanks for posting.

[livinginkaos]

Should this info end up in its own thread so the fix can be found in a thread op.??

Sent From My DEV X

[cmh714]

at the very least I marked it Solved.....

[johnthehillbilly]

Should this info end up in its own thread so the fix can be found in a thread op.??

Sent From My DEV X

Yes it should!!!! ..... Recovering from that error has proven to be next to impossible ..... So this is a major breakthru !!!!!

"No more training do you require...... already know you, that which you need...."

[livinginkaos]

Ang, wanna do the honors?

Sent From My DEV X

[ang]

I'm a "noob" on this forum.  I would like someone to be able to replicate.  I obviously can't get it back to the recipe error to retest the process as we don't really know what causes it.  It's probably some combination of root method, images applied, software/driver combination and possibly bad cable/low battery flashes.

[jtm2381]

Man what a life saver ,it worked like a charm.my razr maxx is running like new Thanks ANG.

[sonsila]

I was able to recover from the Recipe error on my Droid RAZR MAXX.  After trying everything I've read on every post out there and almost quitting after the last post from a trusted moderator, I succeeded with the following steps:

 

1) Fully charged phone

2) Used Motorola cable

3) Upgraded driver to latest version 2.4.5

4) Used VRZ_XT912_9.8.2O-72_VZW-16-5_CFC.xml

5) Used RSDLite 5.7 with the following settings:

1. Flash options: Restart after flexing and TI Blank flash
2. Use image files and delete files on exit

 

Phone connects/disconnects multiple time on flash and then finally does a full reset where you will see droid with "blue electrical work animation."  RSDLite waits for phone to come back but it never will because after the animation the phone does a last reboot into the new image instead of into fastboot.  I've done multiple boots since and every time it works fine.

I used this on my droid razr and it worked flawlessly...thank you...much KUDOS!!!!!

[icprod]

I tryed and gaveme the same arror so i update the RSD lite to the vertion 6 and worked womderfull

[Drayy]

I was able to recover from the Recipe error on my Droid RAZR MAXX.  After trying everything I've read on every post out there and almost quitting after the last post from a trusted moderator, I succeeded with the following steps:

 

1) Fully charged phone

2) Used Motorola cable

3) Upgraded driver to latest version 2.4.5

4) Used VRZ_XT912_9.8.2O-72_VZW-16-5_CFC.xml

5) Used RSDLite 5.7 with the following settings:

1. Flash options: Restart after flexing and TI Blank flash
2. Use image files and delete files on exit

 

Phone connects/disconnects multiple time on flash and then finally does a full reset where you will see droid with "blue electrical work animation."  RSDLite waits for phone to come back but it never will because after the animation the phone does a last reboot into the new image instead of into fastboot.  I've done multiple boots since and every time it works fine.

 

 

I tried this Multiple times with no success.  Then I decided I better follow directions 100% and let phone fully charge.  The next day I tried and again and worked like a charm!  Great instructions.  Thanks!

[mustang302]

Use the file in the original post (Search on google, it's the very first post) It works great . Thhanks for the info.

[FareakyGeek]

1) Fully charged phone

2) Used Motorola cable

3) Upgraded driver to latest version 2.4.5

4) Used VRZ_XT912_9.8.2O-72_VZW-16-5_CFC.xml 

5) Used RSDLite 5.7 with the following settings:

Flash options: Restart after flexing and TI Blank flash

Use image files and delete files on exit

Guys This Is Realy Work  

[theawesome1]

I was able to recover from the Recipe error on my Droid RAZR MAXX.  After trying everything I've read on every post out there and almost quitting after the last post from a trusted moderator, I succeeded with the following steps:

 

1) Fully charged phone

2) Used Motorola cable

3) Upgraded driver to latest version 2.4.5

4) Used VRZ_XT912_9.8.2O-72_VZW-16-5_CFC.xml

5) Used RSDLite 5.7 with the following settings:

1. Flash options: Restart after flexing and TI Blank flash
2. Use image files and delete files on exit

 

Phone connects/disconnects multiple time on flash and then finally does a full reset where you will see droid with "blue electrical work animation."  RSDLite waits for phone to come back but it never will because after the animation the phone does a last reboot into the new image instead of into fastboot.  I've done multiple boots since and every time it works fine.

 

 

Thank you, thank you, thank you. I have been scouring the web for solution to this, and have tried multiple solutions. This one works perfectly.

 

Thank you again

[Alice_Cooper]

I solve it with this command

Please Login or Register to see this Hidden Content

I think this work like this

 

Please Login or Register to see this Hidden Content

now the device boot in ap fastboot mode

at the end just with

Please Login or Register to see this Hidden Content

go back to normal boot mode