[Motorola Atrix 2] ri4naire:
So I tried wiping everything, right?

I flashed to 2.3.5

Formatted my SD card (I'm pretty sure it was a MSDOS Partition Table I wanted, btw, which Partition Wizard doesn't do, it only does GPT)

Updated to 2.3.6

Rooted with [HOWTO] Root the Atrix 2(Updated for 2.3.6 FINALLY)

Installed JRummy's Busybox from PlayMarket, installed busybox 1.19.4 in /system/bin

Then I started to run into issues. I pushed the tarball over and when I adb'd in I got "tar: not found"... Ok, fixed this by using stericson's and explicitly installing tar. What was that all about? I get things going again, run the shell script, it chugs along until I see this...

....

./etc/mtab
./etc/resolv.conf
./etc/shadow
./etc/passwd
We are done and your phone will now reboot, go visit the xda-developers thread a
nd perform the next steps when your phone starts back up.
link_image[1964]: 9253 could not load needed library 'liblog.so' for '/system/b
in/reboot' (link_image[1964]: 9253 could not load needed library 'libgcc_s.so.1
' for 'liblog.so' (load_library[1106]: Library 'libgcc_s.so.1' not found))CANNOT
LINK EXECUTABLE
root@edison:/data/local#

... and the phone does not actually reboot. Webtop is working up until this point so I reboot the phone manually, "mount -o remount, rw /", pop it in the lapdock and it doesn't work. I got the pulsing Motorola "M" and then the screen glows but is black, phone's screen is off. If I close the screen the phone thinks it gets disconnected from charge for a second and then tells me it's in a Standard Dock.

I pulled the webtop_setup.log but it's a bunch of directory names as to be expected except for the bit near the end where it says:

...
./proc/13892/oom_adj
./proc/13892/coredump_filter
unmounting your sdcard from the temp mount, now that we are done copying all the files.

Now we will mount the sdcard with webtop copied over to it, to the correct place, so we can patch it, and remove the FACLs and MACLs. These are what prevent you accessing application and making changes in the ubuntu install.

No FACLs or MACLs running here, skipping to the next step

Now that we don't have any MACLs or FACLs in place, I will add synaptic and a terminal to the install with a patch. After this go thank mbm on the xda-developers forum for this patch!
./
./sbin/
...

I see you've asked for this information from others, I don't know if it will help but I appreciate any assistance and so I don't want you to have to go back and forth.

adb shell
su
id
which busybox
busybox df -h
which su
exit
sexitu
id
which busybox
busybox df -h
which su
shell@edison:/$ su
exit
root@edison:/# id
uid=0(root) gid=0(root)
root@edison:/# which busybox
/system/bin/busybox
root@edison:/# busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 464.7M 344.0K 464.3M 0% /dev
tmpfs 464.7M 0 464.7M 0% /mnt/asec
tmpfs 464.7M 0 464.7M 0% /mnt/obb
/dev/block/system 477.5M 330.4M 147.1M 69% /system
/dev/block/userdata 4.5G 331.1M 4.2G 7% /data
/dev/block/cache 688.6M 16.8M 671.8M 2% /cache
/dev/block/webtop 4.0G 891.1M 3.0G 23% /osh
/dev/block/mmcblk0p2 4.0G 891.1M 3.0G 23% /osh
/dev/block/pds 3.9M 1.1M 2.8M 28% /pds
/dev/block/preinstall 274.7M 29.8M 245.0M 11% /preinstall
/dev/block/vold/179:1 10.7G 550.6M 10.2G 5% /mnt/sdcard
/dev/block/vold/179:1 10.7G 550.6M 10.2G 5% /mnt/secure/asec
df: /mnt/sdcard/.android_secure: Invalid cross-device link
/mnt/sdcard 10.7G 550.6M 10.2G 5% /mnt/sdcard
root@edison:/# which su
/system/bin/su
root@edison:/# exit
shell@edison:/$

What's that "Invalid cross-device link" all about? I feel like that's something I've seen when trying to transfer from internal to mounted memory.