[Motorola Droid RAZR] Ohmster:
Ohhhh. Screenshots in safe strap? No. You do not have an operating system to run apps like camera in safe strap. It is a recovery environment. To capture this you would need another camera, very steady, no flash and it will be blurry unless held rock solid like a tripod or something. But I understand what you are saying now, it shows up during the flash on the black screen, or if you tap the terminal button to show only the black screen, you see all of it, real good. An error like that is not a big deal, you are right. Like I get, "cannot open MD5 file". Of course not, I did not provide an MD5 file, we get that information on the download page, can use an MD5 checker to be sure the file is not corrupt. But the flash works well. I think that "unable to mount /osh" is part up an update script running and finding something unexpected but not an issue. I see in many downloads there are sometimes 5 slightly different files for the same update, install on a razr phone. I always look for "spyder" when I grab one.

Maybe the wrong version of Safe Strap. Let's go see. No, XT912 on crackflasher shows 5 files, just different versions. To me it just sounds like a script file running to mount /osh and it is not necessary or possible on this phone. I wouldn't worry about it too much. Not worth formatting the internal card and starting over from scratch to find out. Just for kicks, I am going to unzip 06/13 and see if I can read the scripts or are they compiled binary. Wow, the file_contexts lists every file in the bunch and where they go, but no osh. These zip files are really neat, the entire system is there, everything where it should be. We have the superuser files. The updater-script is also neat, complete instructions for the machine where to put everything, how to do it, what permissions and ownership everything will have. Amazing, but no osh.

Hmmm, just thought of something. I just went through the whole rom, packing list and updater script and no mention of osh. Could be Safe Strap creates it and cm11 does not use it. Then why would Safe Strap complain about it? Could be it's modified or locked down by the cm installer so Safe Strap cannot mount it. Safe Strap was not written for cm11, it was written for all roms. We just don't know enough about it to do anything with it and it does not hurt anything.

You know, everyone who said it doesn't hurt anything is right. This is a no big deal thing. Like Mr. Chen was curious about an error he was getting in the logs. Man, I have a Linux (Android IS Linux, just stripped down and modified for the device.) computer and the logs are filled with errors. The OS is built to accommodate almost any kind of PC there is and that is good. Tries to configure for a multicore CPU and there is none, then you see an error. But not a serious error. "A just in case you have such a device we have you covered" error. Or anything, installing a different rom at one time, it creates an osh directory or partition that cm11 cannot mount and maybe should not mount, it may not be used in cm11 as I don't see anything in it, ever. Could be the installer mounts all the partitions it finds and osh is not part of it or has permissions set wrong so, it fails to mount something it does not need. Again, "If it ain't broke, don't fix it". :laugh:

I know one way to maybe find out. Check first if it is only one rom slot with the issue. If so or cannot try another to tell, easy way is to delete the slot, recreate it, and restore backup or flash new. Then see if the error is there anymore.

Newbies do not try the following!

To experiment more, I would go into recovery and use the tools in there like file manager or terminal and delete the osh directory. Then flash a build and see if it works, recreates it, and if any errors. If that messes it up and flashing does not work on the slot, delete and recreate it. Then flash or restore backup. If I had time to kill I would actually do it, but since I do not have the error, I cannot confirm if that "solves it". osh seems to be a directory, not a partition but it is not visible in cm11. I should have used fdisk to see for sure but I didn't think of it at the time and too tired now to play with it like that.

Oh you actually have the error! Is it on one particular slot? Try the easy experiment and make a good Safe Strap backup, delete the rom slot, recreate it, then restore your backup. Bump up the size of your user data partition while you are at it. Then when you flash an update, try OTA, something simple, and see if you still have it. Hey, one does not get to see much of the Safe Strap window in an OTA update. You are doing this manually. Still, that is an easy experiment to perform and it is safe.

Nice talking to you sonomazr. Since I don't have the error, I cannot perform any of the experiments. Deleting a rom slot and recreating it is easy and I have done it many times to go "really clean". Okay I think we beat this horse to death, my friend. Appreciate your help and the conversation was pleasant. Good night buddy. :cool: