[Motorola Atrix 2] devsk:
The BMM was installed as part of PA install from Apr 26. I tried PA for few days but ended up restoring the wangg's 10.1 from backup because of quirks with PA (like no audio in my bluetooth car, no ringtones etc.).

don't the errors like the following mean that something is not mounted right?

D/AudioMgrAT_ste( 2284): Not able to set socket priority. Errno: 1, Operation not permitted
D/AudioPostProcessor( 2284): Scene 0: gains 12, 16
D/AudioPostProcessor( 2284): Scene 1: gains 14, 14
D/AudioPostProcessor( 2284): Scene 2: gains 11, 11
I/MID ( 2284): Initialized new AT Context!
E/SchedPolicy( 2284): open of /dev/cpuctl/apps/tasks failed: No such file or directory
E/SchedPolicy( 2284): open of /dev/cpuctl/apps/bg_non_interactive/tasks failed: No such file or directory
...

W/InterfaceController( 1865): Warning (Cannot load library: load_library(linker.cpp:771): library "/system/lib/libnetcmdiface.so" not found) while opening the net interface command library
E/SchedPolicy( 149): add_tid_to_cgroup failed; policy=1
E/SchedPolicy( 149): add_tid_to_cgroup failed; policy=1
E/SchedPolicy( 149): add_tid_to_cgroup failed; policy=1
E/SchedPolicy( 149): add_tid_to_cgroup failed; policy=1
E/SchedPolicy( 149): add_tid_to_cgroup failed; policy=1
E/SchedPolicy( 149): add_tid_to_cgroup failed; policy=1
E/SchedPolicy( 149): add_tid_to_cgroup failed; policy=1
E/SchedPolicy( 149): add_tid_to_cgroup failed; policy=1
E/SchedPolicy( 149): add_tid_to_cgroup failed; policy=1
E/SchedPolicy( 149): add_tid_to_cgroup failed; policy=1
E/SchedPolicy( 149): add_tid_to_cgroup failed; policy=1
E/SchedPolicy( 149): add_tid_to_cgroup failed; policy=1
E/SchedPolicy( 149): add_tid_to_cgroup failed; policy=1
E/SchedPolicy( 149): add_tid_to_cgroup failed; policy=1
E/SchedPolicy( 149): add_tid_to_cgroup failed; policy=1
E/SchedPolicy( 149): add_tid_to_cgroup failed; policy=1
I/mediaserver( 1864): ServiceManager: 0x41313e30
I/AudioFlinger( 1864): Using default 3000 mSec as standby time.
I/CameraService( 1864): CameraService started (pid=1864)
E/SchedPolicy( 149): add_tid_to_cgroup failed; policy=1
E/SchedPolicy( 149): add_tid_to_cgroup failed; policy=1
E/SchedPolicy( 149): add_tid_to_cgroup failed; policy=1
E/SchedPolicy( 149): add_tid_to_cgroup failed; policy=1
E/CameraHal( 1864): (401391dc) device/motorola/omap4-kexec-common/camera/OMXCameraAdapter/OMXDCC.cpp:99 initDCC - No DCC files found, switching back to default DCC
E/CameraHal( 1864): (401391dc) device/motorola/omap4-kexec-common/camera/OMXCameraAdapter/OMXDCC.cpp:44 loadDCC - Error in DCC Init

---------- Post added at 10:50 PM ---------- Previous post was at 10:40 PM ----------

In BMM, SYSTEM 1 has Boot Mode settings. I had "kexec" ticked in there. Unticked that. No difference.

All other are ticked off. Do I need to tick any of those? like 2nd-boot or 2nd-init or Insecure ADB.

---------- Post added at 10:54 PM ---------- Previous post was at 10:50 PM ----------

On a hunch, I ticked the 2nd-init and it boots to the Setup....:) Now, I do the dance of restoring the back, and reinstall and see if I can keep my /data.

---------- Post added at 11:09 PM ---------- Previous post was at 10:54 PM ----------

That's about it!

So, an important step is missing for people coming from kexec version of the ROM: you need to untick the kexec in Boot Mode settings, and tick 2nd-init. Then, you don't need to wipe anything. It will just work. All the settings/applications will be kept.

Makes sense now....:)