Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,732,073 Members 40,966 Now Online
XDA Developers Android and Mobile Development Forum

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

Tip us?
 
whirleyes
Old
#1  
whirleyes's Avatar
Retired Recognized Developer - OP
Thanks Meter 1825
Posts: 832
Join Date: Aug 2007

 
DONATE TO ME
Default [RECOVERY] BMM - Boot Menu Manager Q&A, Support thread

reserved....

Please make a post if you encounter a problem while using BMM
those were the days...
The Following 7 Users Say Thank You to whirleyes For This Useful Post: [ Click to Expand ]
 
frankfurts
Old
#2  
Senior Member
Thanks Meter 10
Posts: 152
Join Date: Dec 2011
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!
 
metalhead_rulz
Old
#3  
Member
Thanks Meter 5
Posts: 75
Join Date: Dec 2012
Default complete erase the slot

As most ROM requires clean slot to work, how can we completely erase the slot?
 
Vatazhka
Old
(Last edited by Vatazhka; 16th February 2013 at 07:49 AM.)
#4  
Vatazhka's Avatar
Senior Member
Thanks Meter 265
Posts: 527
Join Date: Jul 2010
Quote:
Originally Posted by metalhead_rulz View Post
As most ROM requires clean slot to work, how can we completely erase the slot?
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.
The Following User Says Thank You to Vatazhka For This Useful Post: [ Click to Expand ]
 
romdroid.
Old
#5  
Senior Member
Thanks Meter 194
Posts: 1,972
Join Date: Jul 2010
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?
 
frankfurts
Old
#6  
Senior Member
Thanks Meter 10
Posts: 152
Join Date: Dec 2011
Default Re: [RECOVERY] BMM - Boot Menu Manager Q&A, Support thread

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
 
whirleyes
Old
#7  
whirleyes's Avatar
Retired Recognized Developer - OP
Thanks Meter 1825
Posts: 832
Join Date: Aug 2007

 
DONATE TO ME
Quote:
Originally Posted by romdroid. View Post
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?
I believe it was caused by this commit :
https://github.com/STS-Dev-Team/andr...94176acc4cf526

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???
Attached Files
File Type: zip why_we_have_to_skip_devfs_setup_myth.zip - [Click for QR Code] (202.7 KB, 1103 views)
those were the days...
The Following 11 Users Say Thank You to whirleyes For This Useful Post: [ Click to Expand ]
 
SAJdroid
Old
(Last edited by SAJdroid; 17th February 2013 at 05:32 PM.)
#8  
SAJdroid's Avatar
Senior Member
Thanks Meter 89
Posts: 246
Join Date: Apr 2012
Default Help on system 3

Thanks for this great project

My ANDROIDS

Galaxy Note 2 GT-N7100 KitKat 4.4
MOTO X - 4.4 KitKat
Razr MAXX XT910 Jelly Bean 4.1.2 Official EU[Stock]

Asus Transformer Prime TF201 Hairy Bean 2.31
 
frankfurts
Old
#9  
Senior Member
Thanks Meter 10
Posts: 152
Join Date: Dec 2011
Default Re: [RECOVERY] BMM - Boot Menu Manager Q&A, Support thread

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
 
blackhawk_LA
Old
#10  
Senior Member
Thanks Meter 127
Posts: 564
Join Date: Dec 2010
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/show....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/show....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.

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes