Ever do something you shouldn’t have whilst hacking away at your phone, and end up stuck in a bootloop?  Of course you have, because we all have.  That will soon be a thing of the past, thanks to the Team Hydro Bootmanager.  Usually getting to your Android device’s bootloader menu or recovery menu involves mashing and holding buttons, pulling batteries, or in the case of some phone (looking at you LG Optimus Black) a bit of luck because there are no button combinations that work.  This jewel resides in the boot image on your phone, pauses the boot-up, and lets you choose how you want to proceed.  According to lead developer Drew Walton, it works great, it’s stable, will run on just about any phone, and will be ready for public consumption very soon.

*Spoiler alert* Drew is also pretty sure he will be able to expand this, using custom recovery builds (like ClockWorkMod recovery) and create a bootmanager with more options.  This would of course be more device specific and less portable, but offer a new way to manage your device.  You normal, well adjusted users out there may not be as excited as we hacker types are, but all you crack flashers know just how cool this one will be.  I can’t wait!

More: Android Central forums

Google Wallet isn’t there, MyVerizon and contact backup assistant (as well as some network code to assist GPS) is there, and everyone is freaking out.  Verizon has killed the Nexus.  The Verizon Galaxy Nexus isn’t really a Nexus.  Verizon kills kittens!  Let us take a minute and try to put all this in perspective.  Take a deep breath and follow along, and we’ll figure it all out.

Google Wallet isn’t part of AOSP (The Android Open Source Project).  It’s included with the Sprint Nexus S 4G (which is the only phone to offer Google Wallet without hacks) because of some sort of deal between Google and Sprint that we don’t like, understand, or really know anything about.  Come to think of it, the same thing can be said about Google Voice integration.  Why Sprint-only, you ask?  Like I mentioned, we don’t really know, but Google needs somewhere to test these things and Sprint was willing.  Let’s be clear here — no other Nexus device has ever had Google Wallet without hacking it on.  This means the Verizon Galaxy Nexus is just like the penta-band unlocked GSM Galaxy Nexus in this regard. Or any Nexus S that’s not the Sprint Nexus S 4G.

The MyVerizon app and some backup assistant app aren’t part of AOSP either.  They have no business being on a Nexus device, except for one thing — both are “required” for Android devices on the Verizon network.  Them’s the rules, and even Google will follow them.  Contact backup assistant is there because Verizon doesn’t want to be swamped with phone calls about people not being able to migrate their contacts to Android.  It happens more than we think.  Lose backup assistant, and spend thousands in unwarranted tech support.  Verizon is too smart for that (you don’t become the top carrier in the U.S. unless you’re smart and a tiny bit evil) so you bet your ass they are going to cover all the bases they can.

MyVerizon is now needed because we live in a time where unlimited data is slowly phasing out.  Verizon went with tiered plans versus bandwidth throttling, so they are obligated to let you know exactly how much data they say you used.  Remember those class-action suits where Verizon had to pay every person on earth $12?  Verizon doesn’t want anything like that to happen again.  Just as important, current Verizon customers need to be able to have access to apps they purchased through the Verizon area of the Market and Vcast.  MyVerizon helps authenticate those phones so they have access to them.  Just because you will root and remove MyVerizon and never use VCAST doesn’t mean everyone else will. 

Finally, theres the matter of updates and inclusion in AOSP.  Google will write all the updates for the Verizon Galaxy Nexus.  Read it again if you need to, let that sink in for a minute, then we’ll continue.  Yes, there will be a bit of extra testing involved with each to make sure the Verizon apps work and that network specific code works as written, but we’re talking minor differences, not weeks and weeks of delay.  Nobody really thinks Sprint or T-Mobile or AT&T has no hand in network testing on existing Nexus devices do they?  Any delay in updates will be small, and still miles better than the Fascinate fiasco.

About AOSP inclusion — it might not happen.  Apps built into the ROM are closed-source, and Google could say that’s enough to never include it by default.  That will take about 10 minutes to work around if it happens.  AOSP ROMs for the Verizon Galaxy Nexus (that name needs commas and more words) will start cranking out right after the device goes up for sale, so relax.  Enjoy the first (and maybe only) Nexus device on Big Red, and stop stressing yourself and everyone else on the Internet about minor issues.

I’m hard on Verizon, and I don’t agree with most of their business decisions and ethics — but even I think the Verizon Galaxy Nexus will be a damn fine Nexus device.