3711 replies to this topic

[SamuriHL]

What is it with the AP fast boot problems you guys have? Read the faq and do exactly what it says.

Sent from my Xoom using Tapatalk 2

[avlambo21]

odd... my chrome is showing all my apps as still installed... great i have to do it manually from my phone now :/

[gjsimunovich]

I have gotten past my fastboot problem. I uninstalled house of bionic, deleted the remainder of the directory, redownloaded all of the files and reinstalled house of bionic. I then did the house of bionic AP fastboot fix and then reinstalling 246 and have gotten past the original issue. Got into the recovery menu finally and updated. Still waiting on the reboot/install to finish after updating via the recovery menu and wiping.

I didn't think about that until I stepped away for a while. I had reinstalled the drivers, several different usb cables and ports, etc. Not sure what I could have done wrong originally. Uninstall/reinstalling house of bionic might make a decent addition to that FAQ question.

Thanks for the help and it is great the work you have put into it.

[DrJay]

If you mean the NORSD file I did that already. Heres what it does:


* Flashing will take about 10-20 minutes
[NOTE: Your phone must be in AP Fastboot]
Continue when ready to start flashing
Press any key to continue . . .
sending 'mbm' (256 KB)... OKAY [ 0.031s]
writing 'mbm'... OKAY [ 0.469s]
rebooting into bootloader... OKAY [ 0.266s]
Press any key to continue . . .
error: cannot load '.\905_FXZ\mbmloader_hs.bin'
sending 'mbm' (256 KB)... OKAY [ 0.031s]
writing 'mbm'... OKAY [ 0.453s]
rebooting into bootloader... OKAY [ 0.281s]
Press any key to continue . . .
sending 'cdt.bin' (16 KB)... OKAY [ 0.000s]
writing 'cdt.bin'... INFOPreflash validation failure
FAILED (remote: )
erasing 'cache'... OKAY [ 0.297s]
erasing 'userdata'... OKAY [ 0.969s]
sending 'lbl' (16 KB)... OKAY [ 0.000s]
writing 'lbl'... OKAY [ 1.125s]
sending 'ebr' (16 KB)... OKAY [ 0.234s]
writing 'ebr'... OKAY [ 0.438s]
sending 'devtree' (512 KB)... OKAY [ 0.281s]
writing 'devtree'... INFOPreflash validation failure
FAILED (remote: )
sending 'system' (262144 KB)...



The failed remote happens throughout the script. What does that mean?!?

[unbesorgt]

I flashed 246 with hob this am and everything went perfectly. Thx Sam.
So I went home to do the wife's bionic and have nothing but problems. Everything went fine until apfastboot mode comes up and hob says one file copied, rsd comes on my laptop for a second, goes off and hob thinks it finished. When I reboot the phone nothing changed, it booted fine. Then I tried the repair apfastboot and hob said no errors found. But then rebooting the phone goes straight into apfastboot with a boot error. No longer will it boot. What did I f. u.? She's gonna kill me....

Sent from my ICS DROID BIONIC using my fingers

I had a similar problem when HoBing my wife's phone. My theory is that when I plugged it in, it launched my installed version of RSD as part of the autodetect process. When HoB tries to launch its version of RSD, it fails because a conflicting version is already in memory. That's my theory anyway.

To fix it, I just rebooted my PC and tried again. After that, HoB worked flawlessly.

[DrJay]

Why is it always the wives phones... LOL

Sent from my ICS DROID BIONIC using my fingers

[Ekf028]

Why is it always the wives phones... LOL

Sent from my ICS DROID BIONIC using my fingers

Hey, been there before lol

Sent from my DROID BIONIC using Tapatalk 2

[DrJay]

When phone goes into apfastboot, the error at the bottom is:

Invalid CG Version (CG:devtree)

[Wheelz]

Thanks Sam for all your hard work. I have downgraded to 246 without any issues. The HoB is great. I cant even Imagine the amount of work that was involved. Thanks again

[DrJay]

When phone goes into apfastboot, the error at the bottom is:

Invalid CG Version (CG:devtree)

Saw your post in xda concerning this error and tried all the recommendations without luck. After attempting to repair the cdt.bin file with the install 246 option and repair apfastboot, 2 other errors occur trying to get to recovery:
invalid cg version (CG recovery) and invalid cg. Version (CG? Don't remember)
This phone was eclipse 3.0 over 905 with bootstrap. Never had safe strap on her phone. Man, I am lost. Even tried rsd back to 902 and it fails on file 6/22 cdt bin as all attempts at rsd have.
What's the best way to get the correct cdt.bin file back on the phone?
I even tried pushing the cdt.bin file from 902 and 905 into the xml and reran the apfastboot repair with no luck.

Originally I was trying to fxz the 905 file in prep for 946 when the errors occurred in apfastboot with norsd file and then tried to repair apfastboot when all this happened.

Sent from my ICS DROID BIONIC using my fingers

[Kach474]

Hello. I have run in to an issue. I was running 232 on my bionic and with the release of the update I used this thread to try and upgrade to 246. I have read it and the FAQ several times prior to trying it (not saying I didnt miss something). I downloaded all the required items. I choose the first option to on the first screen and then the first on teh second (install 246). Installed update to sd-ext card manully and followed all steps up to installing the update. It continued but errored at that point. Aborted error in sideload package. Now the phone will not boot. Wont boot into anything but AP fast boot. I tried to reinstall and repair with no luck. Any help would be appreciated. I am sure it was something I did wrong. Thanks again.

[tmyinc]

Hello. I have run in to an issue. I was running 232 on my bionic and with the release of the update I used this thread to try and upgrade to 246. I have read it and the FAQ several times prior to trying it (not saying I didnt miss something). I downloaded all the required items. I choose the first option to on the first screen and then the first on teh second (install 246). Installed update to sd-ext card manully and followed all steps up to installing the update. It continued but errored at that point. Aborted error in sideload package. Now the phone will not boot. Wont boot into anything but AP fast boot. I tried to reinstall and repair with no luck. Any help would be appreciated. I am sure it was something I did wrong. Thanks again.

Can you post the swdl file from inside the hob folder? I'm sure Sam will want to see it. Sounds like rsd might not have flashed correctly.

Sent from my DROID BIONIC using Tapatalk 2

[bzbionic]

Im having the same exact problem as DrJay, I was previously running Eclipse 2.x and disabled then uninstalled safestrap to stock 902 before I ran the install of 246 through HOB

[SamuriHL]

I'm going to nuke rsd as default. I've had about enough of this ap fastboot bull$#!7. Finally, however, someone posted me some useful information I can work with. Whoever posted the output from the reinstall flash errors THANK YOU. I'll look into it and figure out wtf is going on. But from 8.2 forward rsd is going to be disabled by default.

Sent from my Xoom using Tapatalk 2

[ketansoni]

I was having the same problem as tmyinc.
I tried the install from my Mac and followed all the instructions.
However, during installation, said E: signature verification failed, installation aborted. I tried a few more times, but then gave up and tried rebooting just to have the phone working. Now, I get a black screen. I can still do AP Fastboot and also recovery.

I *was* running 223 from back in July. I'm no phone genius but I managed to get that working just fine with no problems. This time, I can tell I'm now over my head.
I still had that 223 package on my sd card, so I tried installing that. Error was assert failed: Mount ("ext3", "MTD", "system", "/system") Error in /tmp/sideload/package.zip (Status 7).

So, my plan was to borrow my friends microSD card reader, re-download 246 and 905, stick them on the card, and try again. Any other suggestions?

[SamuriHL]

There are multiple issues going on. First, PEOPLE ARE NOT FOLLOWING DIRECTIONS. And that is going to piss me off as it's wasting my time now. That "reinstall" output I was praising? NOT SO MUCH. That was from a 905 FXZ FULL. REALLY people? Come on! PAY ATTENTION.

Second, RSD is failing in an abnormally high number of cases. I'm changing that. However, due to a bug in the non-rsd flashing, when the RSD flash failed, and I had people switch to non-rsd flashing, it would make the situation worse. That is being fixed.

[soocold]

Just out of my own curiosity, what would cause rsd to fail in the newer versions? Isn't hob using the same version of rsd and modified fxz as previous versions? I thought the only thing that changed was not flashing webtop?

ICS Droid Bionic
.24...........6! courtesy of HoB
OC @ 1.333Ghz

[soocold]

Just out of my own curiosity, what would cause rsd to fail in the newer versions? Isn't hob using the same version of rsd and modified fxz as previous versions? I thought the only thing that changed was not flashing webtop?

ICS Droid Bionic
.24...........6! courtesy of HoB
OC @ 1.333Ghz

[SamuriHL]

8.2 WINDOWS RELEASE

PLEASE PAY ATTENTION TO THE CHANGES!!!

o) RSD is NO LONGER the default. See the FAQ on how to enable it if you wish to continue using it
o) Fixed a bug in the REINSTALL option that would lead to an AP Fastboot flash failed error
o) Fixed a bug in the FXZ FULL option that would lead to an AP Fastboot flash failed error
o) Added new utility menu
o) Added wipe cache option (WARNING: NOT TESTED)
o) Added factory reset option (WARNING: NOT TESTED)
o) Moved root to utility menu
o) Moved show processor info to utility menu

Those with all the AP Fastboot errors, install 8.2, then do the following:

With your phone in AP Fastboot mode:
o) Select 246
o) Select REINSTALL
o) Select N to transfer, N to check hash, N to reboot to AP Fastboot
o) Select Y at flash option
o) Continue to follow directions

IF the flash step fails, COPY the output from the HoB CMD prompt window and paste it into a post here for me to see it.

[SamuriHL]

I have no idea what's causing the RSD issues for people. It's never failed for me. I don't have time or patience to debug every single person's machine to try to figure out why it doesn't work on their machine. It's drop dead simple as hundreds of people have done it successfully with *NO PROBLEM*. But, you know how it goes....the more idiot proof you make something........