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!
Downgrade to 902 - No app or data loss
- Thread starter SamuriHL
- Start date
Let me pass on my experiences from last evening and 0330 this morning for everyones edification. I had my Bionic commit suicide this weekend so I had to do an insurance claim. Once my new one arrived last night, I grabbed Mr. S's great utility (version 2.1) and figured I would have everything done in a few hours, WRONG! I ran through the utility and everything appeared to work great (or maybe the hard cider and mojito just made it appear that way). I went through each step exactly as Mr. S so lovingly crafted them and after the install of .232 and system reboot, I tried to get the script to apply root but it kept failing. I tried using the Droid Razor stand alone and it still failed, I kept getting the dreaded "daemon not running, starting daemon, waiting on phone" error. I rechecked the drivers, reinstalled the drivers, redownloaded the drivers (on a friggin 1X connectiion) and just couldn't get root. All the other functions of the phone seemed to work great, I could download from the Play store, setup my email accounts, etc. I even uninstalled/redownloaded/reinstalled the utility and started again. Then I noticed that when rebooting into recovery the little droid was dead (long live the droid!). So I basically said "f it" and grabbed a meal, fed the mutts and started over again at 3:30. After one more attempt with the utility and no better luck, I decided to fall back on my DX training and booted up FXZ and flashed the .905. After that, I rooted 905 using Motofail (along the way figuring out the DRZR only works for ICS) after succeding that, I booted back into recovery (this time the droid lives) and flashed the .232 file from Mr. S's utility. This time I was able to get root, just in time to head out for work.
Now, please don't think I'm complaining about HOB, far from it, just wanted to point out what Mr. S has said about 1,000,000 times - automation is great but not a replacement for knowledge (so I paraphrased a bit, sue me!). It would have been easy to come over here and start complaining about HOB and taking up the Samuri's time while he tried to fix the issue, I learned a lot more by digging in and returning to basics. So please folks, before blaming HOB or complaining that things dont work, spend a bit of time reading this thread and the multitude of others on this site and others and trying to fix stuff yourself. Mr. S only provides a tool, it's up to us to use it correctly! Of course, I've been known to use a knife as a screwdriver, but that's me! Thanks again to Mr. S and all the others that so selflessly help us out and only complain a smidgen!!
Cheers
Thanks for the post. We were able to get him rooted fortunately. But yes, I agree that knowledge can go a long way. In his case he did everything right and everything I told him to do and it still didn't work. Good times! Darn phones can be, um, troubling at times. 
I'm glad you both are up and running now.
I'm glad you both are up and running now.Thanks for the post. We were able to get him rooted fortunately. But yes, I agree that knowledge can go a long way. In his case he did everything right and everything I told him to do and it still didn't work. Good times! Darn phones can be, um, troubling at times.
nope, wasnt trying to imply the other fellow/fellowette had done anything wrong, just wanted to reinforce your point about people wanting to just push a button and everything works and then complaining when it doesn't. Besides, if we can get people to leave you alone for a while, maybe we can get you to crank out another great utility!!!!
:biggrin::biggrin::hail::hail:
It's in testing as we speak.
HoB 4.0 will be the last major version of the HoB. The reason is simple....I made it dynamic enough that I won't have to touch it anymore. Basically as new updates are leaked/released, there'll be a process that you can follow to add support for it to the HoB. Or you can wait for a small patch that includes the update for you. Unless bugs are found or I get some creative idea on how to improve it, this should be the last HoB release we need. Also, it should be noted that if other moto phone users get ambitious, it could in fact be used to support their releases, as well. I'll post the links and update the OP within a few hours. I want to give my private testers time to take a peek at it.House of Bionic 4.0
You guys will really need to pay attention on this one as a LOT has changed.
1) What to install...
o) If you are on 3.x, get the 4.0 PATCH and it will update you to a FULL instance of 4.0 (more on that in a moment)
o) If you're just now starting with the HoB, you need the 4.0 FULL installer, the 1.0 COMPONENTS, and any of the SamuriHL_HouseOfBionic_(###).exe installers that you want support for. Currently I have them for 232, 235, and 238. Install 4.0, 1.0 COMPONENTS, and then each ### installer than you want support for in that order. Only download what you need support for!
NOTE: Those coming from 3.x using the 4.0 patch, you'll have support for 232, 235, and 238 by default.
2) What's new...
o) Dynamic support for updates
o) boot.img creation for ADVANCED USERS to allow adding your own updates to the HoB!
o) automated md5 hash verification of pushed updates
o) Minor script improvements
ADVANCED USERS:
To add your own update, let's say 6.7.241, follow this procedure:
o) Create a 241 directory in the HoB directory
o) Copy your Blur_Version update zip to the 241 directory
o) Append 241 somewhere to the end of the filename. e.g. Blur_Version.5.9.905.XT875.Verizon.en.US(67241).zip
o) Connect your phone to USB, set Charge Only or MTP mode, enable USB debugging
o) Run AddUpdate.bat
That's it. New update fully supported.
Now you can see why I said this will be the last major version of the HoB.
As this was a major rewrite, I expect a few bumps in the road. I'll fix issues as they come up. Be warned, this may not be 100% working right now. I hope it is, but, there's always a risk of issues with this kind of rewrite.
Enjoy!
You guys will really need to pay attention on this one as a LOT has changed.
1) What to install...
o) If you are on 3.x, get the 4.0 PATCH and it will update you to a FULL instance of 4.0 (more on that in a moment)
o) If you're just now starting with the HoB, you need the 4.0 FULL installer, the 1.0 COMPONENTS, and any of the SamuriHL_HouseOfBionic_(###).exe installers that you want support for. Currently I have them for 232, 235, and 238. Install 4.0, 1.0 COMPONENTS, and then each ### installer than you want support for in that order. Only download what you need support for!
NOTE: Those coming from 3.x using the 4.0 patch, you'll have support for 232, 235, and 238 by default.
2) What's new...
o) Dynamic support for updates
o) boot.img creation for ADVANCED USERS to allow adding your own updates to the HoB!
o) automated md5 hash verification of pushed updates
o) Minor script improvements
ADVANCED USERS:
To add your own update, let's say 6.7.241, follow this procedure:
o) Create a 241 directory in the HoB directory
o) Copy your Blur_Version update zip to the 241 directory
o) Append 241 somewhere to the end of the filename. e.g. Blur_Version.5.9.905.XT875.Verizon.en.US(67241).zip
o) Connect your phone to USB, set Charge Only or MTP mode, enable USB debugging
o) Run AddUpdate.bat
That's it. New update fully supported.
Now you can see why I said this will be the last major version of the HoB.
As this was a major rewrite, I expect a few bumps in the road. I'll fix issues as they come up. Be warned, this may not be 100% working right now. I hope it is, but, there's always a risk of issues with this kind of rewrite.
Enjoy!
Last edited:
master0fursinz
Member
Awesome work Sam. This will make it real easy to update and never lose data again. Unless you fry your phone. If thats the case is there a program or app to copy your phone and save it on the computer like that ugly idevice
I can explain to the class so everyone knows.
1) we scan all the directories for a Blur_Version update zip that doesn't have a corresponding boot.img
2) we extract the patch/boot.img.p and the recovery/etc/install-recovery.cfg files
3) we read in the install-recovery.cfg file to get the sha1 hash and the size of the boot.img that we're creating
4) we push 905's boot.img and the boot.img.p to the /data/local/tmp folder on your phone
5) using the sha1 and boot img size we got from the cfg combined with the known sha1 hash for the 905 boot img, we run the applypatch command to create the new boot img
6) we pull it from the /data/local/tmp folder
7) clean up the /data/local/tmp folder and the boot.img.p and install-recovery.cfg files
8) done
Is there anything that checks the security level to make sure it is the same? I am brave but I think ill wait till the experts verify the security level.( I was one of the first who found 235 and installed it before anyone had a chance to check it out). Thankfully we have a dev community that rescued us!
Yes. In the utils dir you'll find Skrilax_CZ's CDTParser.exe. What you do for that is extract the cdt.bin from the version you're on (let's say 235) and then extract the cdt.bin from the version you're going to (let's say 238), open 2 instances of CDTParser.exe, and open each cdt.bin. Now compare. You want to not only check the cdt.bin version at the top, but, also the security on each partition. If they match, good. If there is an increase, bad.
Oh for sure it was my decision to jump ahead...my eagerness got the best of me...you have certainly covered all the bases! I really find all this fascinating.. if I were much younger id probably pursue further education. Probably wouldnt mind getting into the developer area except never enough time as there is(wife already jealous of time i spend on it!)