Originally Posted by Dirk64

I've tested the new Version 2.3 with success on my Defy MB525 today. Thanks for your work!

Thanks you. I've updated the 1st post thread.

Originally Posted by defim

Isn't bootmenu 1.2.0 the latest?

That one is in motorola olympus device tree, I've used the latest from Defy but I guess eventually this one will become 'less latest'. Still 1.1.8 is almost the same as 1.2.0 , and is surely a nice update since the last version. I'll try to keep this up-to-date more often.

Olá Pedro, any chance of an update that restores the original boot logo and removes the dead boot menu entries upon uninstallation?

Of course flashing a stock SBF could do the job too, but this option is not available for everyone.

It would be great if 2nd init would be fully reversible. You never know when you need to bring your phone back to virgin factory state for warranty repairs.

I'm back on bootmenu 1.0.7. With 1.0.8 the device rebooted immediately after starting SetVsel.

Originally Posted by rogier666

Olá Pedro, any chance of an update that restores the original boot logo and removes the dead boot menu entries upon uninstallation?

Of course flashing a stock SBF could do the job too, but this option is not available for everyone.

It would be great if 2nd init would be fully reversible. You never know when you need to bring your phone back to virgin factory state for warranty repairs.

By boot logo you mean the Motorola logo right after you press the power button (not the animated one that comes after) ?

Originally Posted by defim

I'm back on bootmenu 1.0.7. With 1.0.8 the device rebooted immediately after starting SetVsel.

You're on Defy or Defy Plus?

Defy plus, rooted stock Rom

Originally Posted by pedrodh

By boot logo you mean the Motorola logo right after you press the power button (not the animated one that comes after) ?

Exactly. You don't want a blue CM droid surf over your screen when the Motorola repair guy boots up your phone after putting in a new earpiece or some other piece of hardware. Boot logos, boot animations, and boot menus should all revert back to stock after you restore a stock Nandroid and take 2nd init out.

Can u fix that? Obgdo!

i have a question..why do we need to install the latest bootmenu??the older version should work fine right??

PS: i installed bootmenu some 10 months back and havnt updated it since then..how to know which version i am on??

Originally Posted by abysstheking

i have a question..why do we need to install the latest bootmenu??the older version should work fine right??

PS: i installed bootmenu some 10 months back and havnt updated it since then..how to know which version i am on??

when you open the bootmenu, the version is written on the top.
You require to update (not necessarily) the bootmenu to have latest version of recovery and also some other changes. Just an example, bootmenu 2.0 will have touch operation as shown by Epsylon in a preview video.

Originally Posted by rogier666

Exactly. You don't want a blue CM droid surf over your screen when the Motorola repair guy boots up your phone after putting in a new earpiece or some other piece of hardware. Boot logos, boot animations, and boot menus should all revert back to stock after you restore a stock Nandroid and take 2nd init out.

Can u fix that? Obgdo!

I can understand that, I'll work on a easy way to restore the logo to the original one .

For everyone "SetVsel" works with 2.3?