Wireless Moot

[Dave12308]

The HoB was developed on top of other people's work that came before me. I did some clever tricks to make it work without losing your data. Sarge gave me the method for not rebooting the phone after an RSD flash and that's really opened up some serious power. I've also done a lot of my own development work to make it more powerful and easier to use. The boot img creation is based on the complex manual method that Matt developed. I automated it which was no easy challenge. The mini-fxz was also my idea. John Galt helped me with that one by telling me how to pull certain partitions from the phone such as recovery. It's been an iterative development process to get it where it is today. And through all of the months, it has been COMPLETELY battle tested. Dave and I have bricked numerous times on 235+ and have always been able to recover using the REINSTALL (mini-fxz) option. The dynamic menuing code is something I developed that took a *LOT* of work. It's not nearly as simple as it seems. Even what script to call is done dynamically based upon what option you pick and what files you have available to you. Root is dynamic in that if a new root method comes along, you can throw it in the root dir and as long as it has a run.bat to kick it off, you're golden. The FXZ...that's dynamically discovered. When we get a new one, you'll get a new FXZ installer that'll install it into the HoB. Then you'll delete the 905_FXZ dir and you're fully covered. This project has taken months, but, the results are a tool that is fully dynamic and battle tested.

*LOL* I used to brick my phone PURPOSELY just so I had an excuse to run HoB! The coding in that batch file is ingenious, though. It may go down in history as the "worlds most complex batch file". When I tried the feature to add support for .246 manually last weekend, that's when I went from "impressed" to "amazed".

The most amazing thing about it is that none of us permabricked during the testing phases *LOL*

 

[Dave12308]

No. Motowatcher is something else entirely. Cheesecake factory is a term Matt created for what he does. It uses the standard cheesecake app in a very unusual manner. It's a pain to do but if you know how, you can force a bionic to find updates for any version of any moto phone.

Now here's a REAL dumb question. Would it be possible to kexec-boot the 2.6.35.7 kernel on top of ICS, and use that method to run .905 on the safe partition and cheesecake that way?

 

[SamuriHL]

That's right - it was in the "how to downgrade to .902" thread, IIRC. But I don't believe you had coined the name "House of Bionic" at that point. That's what had me confused. I thought it became "HoB" once you had it to the point where it was a "swiss army knife", so to speak, of Bionic repair.

No, it became House of Bionic early on. Like after the second or third revision. Even before I started making the installers.

 

[Comiskeybum]

My phones: all motorola

- Startac
-v710
-razr
-RAZR 2
-OG Droid
-Bionic

 

[SamuriHL]

*LOL* I used to brick my phone PURPOSELY just so I had an excuse to run HoB! The coding in that batch file is ingenious, though. It may go down in history as the "worlds most complex batch file". When I tried the feature to add support for .246 manually last weekend, that's when I went from "impressed" to "amazed".

The most amazing thing about it is that none of us permabricked during the testing phases *LOL*

I wasn't too concerned about that happening. Knowing the process, we could have fixed it by hand had we needed to. The script was an evolution. I cleaned it up quite a bit when I moved to a wizard in 7.0. It should be much easier to read and things are named a bit more consistently. Have you run it since I did the wizard stuff? We're talking window title transitions and all to let you know what step you're on.

 

[Dave12308]

No, it became House of Bionic early on. Like after the second or third revision. Even before I started making the installers.

*LOL* Guess I just didn't pay that close attention to it back in the day. Although I do have one of the original versions on my desktop, the version for .235 I believe - which I THINK was your last version sans installer. I have 2.0 on my desktop as well, that one is an installer.

 

[jayrod]

How do you think I *LEARNED* what I know? No one wakes up knowing everything. I was part of the original crew that discovered how to flash boot img's...we did it the hard way back then. But it worked. Now, we're way more advanced and have multiple methods and all that. But all this stuff was born out of the sweat, blood, and tears of those of us that worked on it back then. The community came together to get people back on the OTA path. This is why I feel so strongly about wanting to give back to the community. The HoB is my contribution to the community and payment to those who taught me what I know.

The HoB was developed on top of other people's work that came before me. I did some clever tricks to make it work without losing your data. Sarge gave me the method for not rebooting the phone after an RSD flash and that's really opened up some serious power. I've also done a lot of my own development work to make it more powerful and easier to use. The boot img creation is based on the complex manual method that Matt developed. I automated it which was no easy challenge. The mini-fxz was also my idea. John Galt helped me with that one by telling me how to pull certain partitions from the phone such as recovery. It's been an iterative development process to get it where it is today. And through all of the months, it has been COMPLETELY battle tested. Dave and I have bricked numerous times on 235+ and have always been able to recover using the REINSTALL (mini-fxz) option. The dynamic menuing code is something I developed that took a *LOT* of work. It's not nearly as simple as it seems. Even what script to call is done dynamically based upon what option you pick and what files you have available to you. Root is dynamic in that if a new root method comes along, you can throw it in the root dir and as long as it has a run.bat to kick it off, you're golden. The FXZ...that's dynamically discovered. When we get a new one, you'll get a new FXZ installer that'll install it into the HoB. Then you'll delete the 905_FXZ dir and you're fully covered. This project has taken months, but, the results are a tool that is fully dynamic and battle tested.

That's how I first found this site because a whopping week I after I got my Bionic last September I softbricked it by doing something verrry stupid ...this video was a life saver!(even if it took 4 times for RSD to work [video=youtube;tAd7XzL76CA]http://www.youtube.com/watch?v=tAd7XzL76CA&feature=relmfu[/video]
...stayed up all night swearing I would never do anything to my phone if it worked)*not long after I was flashing my first leaked update..then my first Rom
I have much respect for everyone who has done anything dev for the Android community !

 

[SamuriHL]

Now here's a REAL dumb question. Would it be possible to kexec-boot the 2.6.35.7 kernel on top of ICS, and use that method to run .905 on the safe partition and cheesecake that way?

I doubt it. Not 100% sure TBH. But my gut tells me no, that it wouldn't work.

 

[Dave12308]

I wasn't too concerned about that happening. Knowing the process, we could have fixed it by hand had we needed to. The script was an evolution. I cleaned it up quite a bit when I moved to a wizard in 7.0. It should be much easier to read and things are named a bit more consistently. Have you run it since I did the wizard stuff? We're talking window title transitions and all to let you know what step you're on.

No, last I used was the one you released from NHMS (6.7). I haven't messed my phone up since then, i'm happily running .246/CM10 (solid JB build, by the way- absolutely no data issues since I put it on there last night).

 

[hAHAha Halo]

Like I said, even 1.0GHz was NOTHING for the OMAP3430. Crap between the screen and bezel is what kills D1 touchscreens. I never did say that it was EASY to fix. I just would have attempted it had I known. But take it from a guy that CREATED custom kernels for the damn thing - 1.0GHz was totally safe. Most of my 1.0GHz kernels actually ran stock 600MHz voltages to hit that speed, and my 1.2GHz kernels were very SLIGHTLY raised. I've never heard of any cases where 1.0GHz would kill an OMAP3430.

I tried flashing some of the higher kernels as well, but became too unstable at one point. But keep in mind I was putting heavy use on my phone, and had my overclocking app set to Maximum Performance", and running it at 1Ghz all the time couldn't have been good. Considering 1Ghz is how fast the stock processor is on my Bionic, and the phones were about 2 years apart from each other, that says at least something. This might be the key piece of information that I left out: Although in a post on another thread that I had flashed around 30 roms on my D1, I know that couldn't have been right because I was flashing new roms every 3-4 days. I was rooted for a year, that kinda tells you my phone went through a lot of software changes, maybe went through 50 or more roms. That, plus the hard usage on the processor, slowed it down.

 

[SamuriHL]

*LOL* Guess I just didn't pay that close attention to it back in the day. Although I do have one of the original versions on my desktop, the version for .235 I believe - which I THINK was your last version sans installer. I have 2.0 on my desktop as well, that one is an installer.

I don't even bother keeping the old crap. I keep iterating the same directory on my laptop. My installer scripts are in there as is my DIST directory where the installer products get output to. I did forget to copy it back from my netbook when I did that 6.7 fix for you. That's how we had the regression bug. Easy to fix though.

 

[Dave12308]

I doubt it. Not 100% sure TBH. But my gut tells me no, that it wouldn't work.

*LOL* Thinking about it, even if it WOULD work in theory, it wouldn't work in practice. From what I understand (and forgot about, but it dawned on me) there isn't enough room in the preinstall partition to support safestrap booting a stock Moto build from the safe side.

 

[SamuriHL]

No, last I used was the one you released from NHMS (6.7). I haven't messed my phone up since then, i'm happily running .246/CM10 (solid JB build, by the way- absolutely no data issues since I put it on there last night).

Run it without the phone connected. Pick the following:

246
INSTALL

Then select N at every prompt that comes up. Just so you can see what I've done.

 

[SamuriHL]

*LOL* Thinking about it, even if it WOULD work in theory, it wouldn't work in practice. From what I understand (and forgot about, but it dawned on me) there isn't enough room in the preinstall partition to support safestrap booting a stock Moto build from the safe side.

That's one of the issues, yea.

 

[BIONICPREDATOR]

On 244/246 with a couple of smart actions (one that kills WIFI from 7a-7p mon thru fri and one that kills data totally from 11p-5a sun thru thurs) I get about 20-22 hrs

You get that kind of life with the standard battery?

Sent from my DROID BIONIC using Droid Forums