Just an update for everyone who's been helping in this thread. I wish I could add [SOLVED] to the title, but it wouldn't be fair to the OP as though his problem is solved, his phone is still broken. I'll explain:
Ok, so after some messing around in the chat room, the realization came up that the OP was already flashed to the latest 4.1.2 system. I didn't know that. At the moment, we only have at our disposal 4.0.4 and 4.1.1 fastboot files. We also found out that this started after wiping all the slots in his safestrap and then accidentally rebooting without any system installed. We were running into all these errors because his secure version updated with 4.1.2, his bootloader was yet to be unlocked and we all know you can't downgrade once your secure version updates.
Our last ditch effort was to flash the 4.1.2 OTA (that
shane1
provided me earlier in the week, thanks for that, btw), but it failed right away at file_getprop: failed to stat "/system/build.prop":no such file or directory So, as there was no system. That option was not going to work.
Sadly, until Razr M 4.1.2 fastboot files leak out, there's very little we can do for the OP at this moment. This is a reason that makes it vital to have your bootloaders unlocked. Had it been done on this phone already, 4.1.1 would have flashed with no problems and we'd have been done last night. The FB files have been leaking rather quickly lately. So hopefully, the OP won't be stuck for too long.
^^This is also shows that if you have a problem, you need to give out all relevant information. A mechanic can't fix your car if you tell him over the phone that your BMW is leaking oil and he can't see it in person, but in reality it's a Pinto with a water leak.
With that being said, these kind of threads show me what a great community this is. I have learned a lot reading all the problem threads in the last couple weeks since the unlock exploit came out. I would take DroidRzr over XDA anytime. It is far more tolerant and friendly here.