CM7 Cannot boot into recovery after flashing Droid X (2nd Init)

[noonex]

I installed CM7 and got everything working. I then wanted to update from RC0 to a nightly build so I flashed Droid X (2nd init) from RM. After that I can no longer boot into recovery. I have tried flashing back to Motorola Droid X, reflashing Droid X (2nd init), fixing permissions after both, rebooting to recovery from RM, holding down power and volume down. If I attempt to go into recovery my phone just sits at the M logo. The current version of CM7 is running great and I'd rather not have to spf just to be able to get to recovery. Is there anything I can do?

[Ads]

[popcenator]

What version of superuser do you have? Open su and hit settings at the top, then scroll all the way down. Hit su binary to check for updates.

on the move..

[noonex]

I have Superuser v2.3.6 Database version 5. The Su binary is v2.3.1-ef. The Update check didn't seem to do anything so I assume it is up to date.

[popcenator]

Go into the market and search for superuser and download it. If I remember correctly the latest version is 2.3.6.3

on the move..

[noonex]

Done. I'm now on v2.3.6.3 su binary v2.3.2-efgh. I'll try to reflash the recovery now.
...
Still stuck at the M after telling it to reboot to recovery from RM.

[noonex]

I just realized i should reply so you get notified the thread is updated.

Flashing both "Motorola Droid X" and "Droid X (2nd Init)" and trying to boot into recovery still just sit on the M.

[jwalz]

Which bootstrapper are you using

[popcenator]

What were you on before CM7 and what steps dis you take to get there?

on the move..

[noonex]

Which bootstrapper are you using

I don't think I'm using any now. Originally I was using the D2 bootstrapper. After you install CM7 you cannot run a bootstrapper or bad things happen. Or so I have read.

[noonex]

What were you on before CM7 and what steps dis you take to get there?

I was on .596 rooted. I installed the MonsterCM7 All in 1 Update.Zip. Booted CM7. Went back to recovery and ran the Monster update again (to fix the radio). Then I ran RM and flashed the Droid X (2nd init) recovery and that is what appears to have started this mess.