[RECOVERY] BMM - Boot Menu Manager Q&A, Support thread - Motorola Droid RAZR

reserved....
Please make a post if you encounter a problem while using BMM

---

Whirly, just to make sure I'm doing things correctly, to create a virtual system on say system 3. All I have to do in the settings is create, the system, data and cache.img files
In root explorer I go into sdcard-ext and I can see the folder Virtual>System 3>then all the image files inside, then flash the zip yet when I try to boot it gets stuck on booting with the green droid
I'm trying to flash Dwiz ROM that I had working before on my number 1 system, also I unchecked 2nd boot and kexec.
Also I know you haven't got full Razr V yet support so it may just be a bug
Thanks for being so helpful!

---

complete erase the slot
As most ROM requires clean slot to work, how can we completely erase the slot?

---

metalhead_rulz said:
As most ROM requires clean slot to work, how can we completely erase the slot?
Click to expand...
Click to collapse
A properly designed ZIP installer should take care of cleaning by itself. In order to start afresh you can destroy old image and create a new one - this is not possible for real partitions. These can be reflashed from FXZ and then "formatted" by removing all files and directories.

---

will u upgrade bmm to be compatible with cm 10.1 from hashcode? thanks. if yes, will it be possible to install cm 10.1 as stock rom?

---

For some reason I cant restore any back ups. I have tried both formats and I have been doing the quick backup.
When I restore it goes through the process then finishes with an error "there was an error writing to system" or something similar. I have tried mounting and formatting system etc but no good.
Can someone tell me the best way to take a log so I can better see were it is going wrong.
Cheers

---

romdroid. said:
will u upgrade bmm to be compatible with cm 10.1 from hashcode? thanks. if yes, will it be possible to install cm 10.1 as stock rom?
Click to expand...
Click to collapse
I believe it was caused by this commit :
https://github.com/STS-Dev-Team/android_system_core/commit/e15eebac61d22edbe8d4aee1e794176acc4cf526
Code:
#ifndef NO_DEVFS_SETUP
mkdir("/dev", 0755);
mkdir("/proc", 0755);
mkdir("/sys", 0755);
mount("tmpfs", "/dev", "tmpfs", MS_NOSUID, "mode=0755");
mkdir("/dev/pts", 0755);
mkdir("/dev/socket", 0755);
mount("devpts", "/dev/pts", "devpts", 0, NULL);
mount("proc", "/proc", "proc", 0, NULL);
mount("sysfs", "/sys", "sysfs", 0, NULL);
/* indicate that booting is in progress to background fw loaders, etc */
close(open("/dev/.booting", O_WRONLY | O_CREAT, 0000));
/* We must have some place other than / to create the
* device nodes for kmsg and null, otherwise we won't
* be able to remount / read-only later on.
* Now that tmpfs is mounted on /dev, we can actually
* talk to the outside world.
*/
open_devnull_stdio();
klog_init();
#endif
BMM always clean all tmpfs partition before 2nd-init, so that init can do a fresh start.
But since this commit, some devfs is not recreated, thus ROM can't be booted.
If you want to boot newer build, you have to build your own init. (undefine BOARD_USE_NO_DEVFS_SETUP)
or take init binary from 24012013 build. (Not recommended)
Attached is init binary taken from 24012013 build for testing.
Flash this zip after flashing STS CM zip file.
Why we have to skip devfs creation??? anybody????
Should I fix this in BMM boot script???

---

Help on system 3
Thanks for this great project

---

Whirleyes I'm having trouble extracting the log from BMM I hit report error but cant see where it is saved.
Anyway I viewed the flash log in recovery mode after doing a backup and got these errors. It sounds like its an issue with the wrong directory being mounted or something.
W: failed to mount /dev/block/mmcblk1p25 (no such file or directory)
No /into/.android_secure found skipping backup of applications on external storage.
I'm assuming this is also why I'm having travel restoring the backups.
Cheers
Sent from my Nexus 7 using Tapatalk 2

---

I'm not sure if this is caused by BMM, but I'm going to explain, just in case.
It's the second time that I habe a "boot failure flash" problem, as described here
http://forum.xda-developers.com/showthread.php?t=1893347
The first time it happened I was trying to come back from JB kernel, but now I just reboot from a completely working ROM (JellyWiz) and it went to that AP boot failure flash.
It seems like webtop partition gets corrupted or something, because I'm always able to fix it flashing a webtop image, as described here http://forum.xda-developers.com/showthread.php?t=1792955, in "Fastboot for the webtop_signed"
As BMM uses webtop partition, maybe it can be related to the problem...
I'm sorry I don't have more precise or technical information but I don't have much knowledge, also that problem appeared in two different situations, apparently it was not related to a specific situation.

---

blackhawk_LA said:
I'm not sure if this is caused by BMM, but I'm going to explain, just in case.
It's the second time that I habe a "boot failure flash" problem, as described here
http://forum.xda-developers.com/showthread.php?t=1893347
The first time it happened I was trying to come back from JB kernel, but now I just reboot from a completely working ROM (JellyWiz) and it went to that AP boot failure flash.
It seems like webtop partition gets corrupted or something, because I'm always able to fix it flashing a webtop image, as described here http://forum.xda-developers.com/showthread.php?t=1792955, in "Fastboot for the webtop_signed"
As BMM uses webtop partition, maybe it can be related to the problem...
I'm sorry I don't have more precise or technical information but I don't have much knowledge, also that problem appeared in two different situations, apparently it was not related to a specific situation.
Click to expand...
Click to collapse
Because BMM 0.3.4 format webtop partition without asking cdt for safe region.
It should be no problem with 0A7* bootloader... but not everybody is using it. [Lesson learned]
Here's a bootloader updater tools. (razr_bl_mbm_*.zip)
http://dl.projectlense.com/download.php?file=spyder/razr_bl_mbm_0a77.zip

---

Thanks! It worked perfectly but I had to copy AdbWinApi.dll to the tools folder. :good:

---

whirleyes said:
Attached is init binary taken from 24012013 build for testing.
Flash this zip after flashing STS CM zip file.
Why we have to skip devfs creation??? anybody????
Should I fix this in BMM boot script???
Click to expand...
Click to collapse
confirmed as working, also with newer build versions.
thanks whirley! if its not too much hassle for you it would be nice to have it added to bmm, but then again its just flashing one more zip file...doesn't really hurt much
i just think integrating the ability to flash these new roms would take away the one last reason to use ss3 and not bmm^^ so you would probably win over a few more users that are not switching because they want to test the newer cm10.1 roms.
btw whats up with project kaizen? im still interested in checking that out
also i'm glad to see you back on xda!!!

---

Maybe I'm a stupid boy but it's possible to speak with Hashcode to solve this problem?

---

hello, I have a problem. When I open my BMM 0.2.6, it said Application Corrupted and It need redownload from Google Play.
And when I want to uninstall it, the installation was unsuccessful. How to uninstall the corrupted BMM?

---

pseudoheld said:
confirmed as working, also with newer build versions.
thanks whirley! if its not too much hassle for you it would be nice to have it added to bmm, but then again its just flashing one more zip file...doesn't really hurt much
i just think integrating the ability to flash these new roms would take away the one last reason to use ss3 and not bmm^^ so you would probably win over a few more users that are not switching because they want to test the newer cm10.1 roms.
btw whats up with project kaizen? im still interested in checking that out
also i'm glad to see you back on xda!!!
Click to expand...
Click to collapse
thanks, does stock flashing also work?:fingers-crossed:

---

romdroid. said:
thanks, does stock flashing also work?:fingers-crossed:
Click to expand...
Click to collapse
What do you mean? Flashing to the first (stock) system has always worked on bmm!

---

txdvil said:
hello, I have a problem. When I open my BMM 0.2.6, it said Application Corrupted and It need redownload from Google Play.
And when I want to uninstall it, the installation was unsuccessful. How to uninstall the corrupted BMM?
Click to expand...
Click to collapse
It's outdated. Just download the latest available version (current is 034).
I want to remove all older BMM file from download server soon.
pseudoheld said:
ss3 and not bmm^^ so you would probably win over a few more users that are not switching because they want to test the newer cm10.1 roms.
Click to expand...
Click to collapse
It's not about lose or win. No benefit at all. I just want something that works for me.
For efficiency, I think I won't add support for CM10.1 (with skip devfs on)
(extra code for ROM detection = extra boot delay)
pseudoheld said:
btw whats up with project kaizen? im still interested in checking that out
Click to expand...
Click to collapse
It's only good for personal use. Don't count on me.

---

I've noticed using 0.3.4 with bootloader 0A7 that I cannot backup my CID. I did it with terminal emulator. Erase it was possible. Maybe it's not related with hmm, but I've tried many times, also I've installed it a few times to be sure.
It is something that I did wrong?
Also thanks A LOT for this

---

pseudoheld said:
What do you mean? Flashing to the first (stock) system has always worked on bmm!
Click to expand...
Click to collapse
yes, I was refering to installing cm10.1 to stock system. thanks for the answer :good: