rocketsaucev2
Member
Sounds good to me, thanks samuri
DroidForums.net | Android Forum & News
This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
Leak .242?
- Thread starter JayBusa102709
- Start date
What kind of nonsense is that? If 242 is not OTA, then of course I'll move to whatever OTA ends up being. My phone has gone through this procession so far:
229->230->232->235->238->242
What does everyone think I wrote the HoB for?
Did you ever have to wipe your data or was it something you just did for good measure?
I think the first time I wiped data was on 238. That should tell you how stable ICS has been.
But the caveat to that is I used the HoB completely. Some people did stupid things and caused themselves some annoying issues and blamed it on the update. Like restoring GB system data into an ICS build. That's just not smart. I completely get it, but still stay on .905. I just don't have the time to mess around... job, girl, kid, etc. Can't chance my phone not working. As much as I want to install a leak, I just don't have the time to dedicate fixing/setting up apps etc/fxz blablahblah
Like I said....absolutely nothing wrong with that at all. It's perfectly understandable.
Geez. I'm really confused. I "installed" HoB 6.7.242 to my desktop(its default) and I got a 242 folder(with a very conspicuous .zip file plus boot.img and recovery.img), an uninstall exe and dat file. I see no house of bionic bat which some guides call for or any "executable" files in the house of bionic folder. Am I missing something?
Since I'm doing a straight install from 905 to 242 I won't need HOB but I'm not sure if the included zip file is modified or not.
Also what backups should I try to make before the upgrade? I was going to run my typical titanium backup script that runs every week on my phone. Should I do anything else for good measure? I used to make a monthly backup using bionic bootstrap, but I haven't installed it since going back to 905 from 2231.
Since I'm doing a straight install from 905 to 242 I won't need HOB but I'm not sure if the included zip file is modified or not.
Also what backups should I try to make before the upgrade? I was going to run my typical titanium backup script that runs every week on my phone. Should I do anything else for good measure? I used to make a monthly backup using bionic bootstrap, but I haven't installed it since going back to 905 from 2231.
Yes, you're missing a lot. I'm only going to say go read the OP and leave it at that...I've been through this 100 times already and don't feel like repeating it all again.
SamuriHL_HouseOfBionic
SamuriHL_HouseOfBionic
Haha. Just found that thread too. It's amazing how many other threads showed up in my search but none directly linked to this thread. It would be really great if everyone would link to that thread instead of posting their own links to the leaks
Oh well. Flashing is about to commence
I prefer that you provided the link. I have to learn more if I read about it than just being told what to do
I'm nobody important around here,but if anyone is confused as to taking a possible gamble by jumping from stock .905 to ICS leak (possible but not guaranteed as final OTA) and are downloading files that you aren't sure about..maybe jumping in on page 20+ of a thread isn't the best or smartest thing to be doing.
Please,don't take this as me being rude,but I have read many posts/threads on this subject that always end in the same way :
Please,don't take this as me being rude,but I have read many posts/threads on this subject that always end in the same way :
I've given up arguing with people about it. I've given all the warnings. I've said my peace 100000 times over. If they wanna go to 242, so be it.
I totally agree with you(and I'm pretty sure the comment was directed at me). I've read through all 20+ pages of this thread actually. Any thread that is 3 days old and has over 20 pages has totally peaked my interest! I had a few posts on page 12 too
I've installed leaks before, even the 2nd or 3rd ICS leak before going back to 905. I'm just very cautious with what I do on my phone. On a desktop if I kill the OS I know how to fix it. It could be FreeBSD, Linux, Windows, whatever. However on the phone I'm not so sure I can fix "anything" that breaks. I just haven't tried to keep up with what leaks have been out, when, how/if you can update from 1 leak to the next because I really was expecting Verizon and Motorola to get on the ball with this. But I've finally given in and I'm going to make the plunge.
Alot of people have threads where they claim to have bricked their phones and often they are able to be fixed. I really don't like the posts/threads that involve people making outlandish claims of their phones being "bricked" when it's only a matter of them not knowing how to fix. When a pro like SamuriHL says it's bricked, then someone can truly say it's bricked. Until then someone with 5 whole posts in the forum should NOT be starting threads with "I bricked my phone".
Also there's alot of conflicting data depending on who is talking so it can be difficult to rule out who actually knows what they're talking about and who thinks they know. I also like to have a deep understanding of what's "going on in the background". While the House of Bionic batch file really simplifies the installation I really like to understand what it is actually doing besides "putting files on your phone". I like the deep understanding so that if I have a problem I'm not posting a thread of "I tried to install it and it broke". I hate those kinds of threads, not to mention the vagueness of the post.
I have too many questions about the actual internal process of updating to have a grasp of what kinds of things can go wrong. For instance, I commented that I'm not sure if my zip file is modified. I did find an MD5 that confirms it is the correct file and unmodified. But wouldn't a leak that's signed by Motorola be protected from little hands modifying things they shouldn't? What files exactly are "protected" by the signing? I like to know ALOT of details before I jump into stuff I don't know, and some of my questions don't have answers I can find in a forum regardless of how many searches I do. Forums won't always give you the nitty gritty internal details of what goes on behind that cool update screen. I like to know that stuff before I update. Can you tell I'm a programmer?
As for the HoB it appears that it does it's "magic" (allows for updating ICS) by installing a signed/valid boot.img and/or recovery.img. Once this is done it will allow for installing 242 as an update because it thinks that 242 is already installed. Of course, I'm only guessing because I couldn't find a thread to validate this.
First, the zip file if modified in ANY way will fail the assertion check in recovery when you go to install it. So, while I rename the zips, you can rest assured they are direct from moto's servers unmodified. I rename them because too many people download "Blur_Version.5.9.905.XT875.Verizon.en.US.zip" and install it. What version is that? 229? 230? 232? 235? 238? 239? 242? From that filename, you have *NO FREAKING IDEA*. So my "suspicious" zip as you call it tells you what version it installs on top of, and what version you will end up on. This is by my design.
As for the inner workings of the House of Bionic, I've been over this all before. It's in my thread. It dynamically builds the menus so that it'll support any FXZ and set of updates without having to be rewritten. Believe me when I say that's challenging in a batch file. Once you select what you want (INSTALL or REINSTALL) then the appropriate RSD script is copied into the FXZ dir, certain files in the FXZ dir are backed up and replaced with files from the update you're installing as needed (i.e. the boot.img for an install, and MANY more files for a reinstall to build a mini-FXZ), and then I command line script calling RSD to flash the files to your phone. We intentionally throw an RSD error as the last command to force the phone to stay in AP Fastboot mode. The reason is we do *NOT* want the phone trying to reboot itself at this point as it will fail and require a battery pull. Next we have you boot into recovery and install the update. A cache wipe, and you're good to go. Then you can root it as needed.
As for the inner workings of the House of Bionic, I've been over this all before. It's in my thread. It dynamically builds the menus so that it'll support any FXZ and set of updates without having to be rewritten. Believe me when I say that's challenging in a batch file. Once you select what you want (INSTALL or REINSTALL) then the appropriate RSD script is copied into the FXZ dir, certain files in the FXZ dir are backed up and replaced with files from the update you're installing as needed (i.e. the boot.img for an install, and MANY more files for a reinstall to build a mini-FXZ), and then I command line script calling RSD to flash the files to your phone. We intentionally throw an RSD error as the last command to force the phone to stay in AP Fastboot mode. The reason is we do *NOT* want the phone trying to reboot itself at this point as it will fail and require a battery pull. Next we have you boot into recovery and install the update. A cache wipe, and you're good to go. Then you can root it as needed.
LaurelRaven
Member
You know what? F it. I'm feeling brazen tonight, and I'm going to install 242. I'm confident in your HoB script to get me where i need to go, and I'm no longer worried about having a gingerbread to go back to.
Plus, 229 is a bit buggy, and I'm tried of waiting.
Sent from my ICS Bionic
Plus, 229 is a bit buggy, and I'm tried of waiting.
Sent from my ICS Bionic
LaurelRaven
Member
All right...everything downloaded, I'm reading and re-reading your post a few times just to be sure I understand what I'm doing. Pushing to the SD-Card; wish me luck!
Everyone installing 242 needs to pay attention to this warning. Keep the update on your sdcard. Do not delete it. If you brick later and tell me the update is not on it you will be responsible for figuring out how to get it back on there.
Sent from my Xoom using Tapatalk 2
Sent from my Xoom using Tapatalk 2