Thank you Samuri. You have been so helpful during all of this. I appreciate all of your hard work.
Thank you Samuri. You have been so helpful during all of this. I appreciate all of your hard work.
No problem. Just make sure to get the latest files from the HoB thread. 5.5 is the current version of the HoB scripts, 1.0 COMPONENTS you already have, and the 242 support installer. Then just do the install 242 option and you should be good to go.
I first tried installing 242 thinking i didnt need 5.5 just 3.0. I was confused as to why the msdos bat thing wasnt giving me the option for 242. Pretty noobish i admit but i figured it out.Originally Posted by SamuriHL
While I agree with that, I was referring to the point you made about having to upgrade to 5.5 in order to "add support for 242". That is highly wrong. The HoB uses a dynamic menuing structure. The only thing needed to add a new release is the update and the boot img. And the boot img can be created with addupdate so you really only need the update itself.
Sent from my Xoom using Tapatalk 2
All that is necessary for an update to show up on the menu is an xxx dir that contains the update with xxx somewhere in the filename and the boot img which can be created with addupdate. Meaning that I don't even have to release any new versions for it to just simply work. The person that discovered 242 used the HoB to install it before I even knew it was out. Once I get an update I create the boot img for it and then extract the recovery img after installing it. I then point my update install creation script at it and create a new support installer. All that does is put the new dir in place with the update, boot img, and recovery img. The HoB menu detects it and dynamically adds it to the menu.
Sent from my Xoom using Tapatalk 2