I just took a look at what you said and what I am wondering is that if when you performed the wire trick (and it worked), did it say waiting for device as soon as the wire trick worked and rebooted the phone?
That is the last thing I see before it reboots. Once it boots back up it talks about drinking beers and beers and buddies and all that good stuff then it just says S-OFF failed with that error code and still sober message. I get literally the same exact thing EVERY time I do it.
That is why I think it might be something else. My timing can't be that bad. Like I said, using that metronome file for the timing, I pretty much hit it right on the nose and like clockwork, Control Bear says waiting for device, it reboots the phone and then I get that stupid error.
Yes, as soon as I did the wire trick, the very next bit of text said "waiting device" and a moment or so later it said "fastboot found" or something to that effect. then kept going on about beers while the phone continued to the black juopunutbear screen. Then another reboot, briefly again "waiting device" then more beer talk, another reboot, and then it actually booted into my ROM when juopunutbear said Success!
---------- Post added at 01:47 AM ---------- Previous post was at 01:45 AM ----------
Originally Posted by james_pnut
Using the process re locks your hboot so fastboot command don't work. Either flash the modified hboot or unlock your phone using the htcdev tool.
Sent from my ADR6425LVW using Tapatalk 2 Beta-5
Yes, this is the correct steps. S-OFF on the Rezound still has limitations not in place on previous devices. If HBOOT is locked, as it is after the S-OFF process, you must either flash the ENG HBOOT, unlock your stock HBOOT again, or use juopunutbears modified HBOOT. Those are the options. research carefully before making your selection.
Im running on rez rom 3.4 on the original post it says you need to be on a stock rom rooted..In these instructions it doesnt say that..So, do you really need to be on stock rom rooted? Also in this thread it says v.02 is that referring to controlbear?
Okay, got it after about 45 minutes of fighting with it.
I'm on stock GB btw.
What worked for me, was to leave the phone plugged in. Run ControlBear. It would tell me to 'do the wire trick', which I would do. Then it would reboot, 'waiting' while the counter shows 8/45 or 10/45 or whatever (this would always change). The ControlBear would just sit on the screen, like the process froze. After around 3 minutes of nothing but 'waiting', I would close the terminal and restart ControlBear, leaving the phone plugged in. Sometimes it would say 'fail, quit'. I would simply run it again, still leaving the phone plugged in. It would still seem to freeze on the last two processes, making me restart the ControlBear. Only it eventually said success, s-off, and gave me the option to install hboot.
So, by no means did this feel like a successful mod, but it worked for me
Right after hboot installed, put me into hboot, s-off noted. I rebooted, and all seems well. Be patient, really patient.
So, my issue with getting controlbear to recognize my phone was fixed by formatting my "replacement" sd card. I didnt need to reinstall adb, or flash an hboot, or anything else. It found my device immediately afterwards, and once it did it only took me one try!! S-off and stoked! Thanks to everyone with the thorough updated FAQ's... Im good with fastboot/adb, and I would never have thought of formatting my blank "mock" sd card! Figured I would throw this out there if any one else was having "waiting for device ....1......2, check adb and drivers" - this fixed my issue.
EDIT: Also disabled threatfire/avg in the process of debugging this issue, as well as completely uninstalling HTC sync (left other two htc drivers, etc on) - didnt think these were as significant, as sync was always thoroughly shut down, and I have never had issues with virus protection. These definitely may have played a part, or all of the issue.
======== ControlBear version 0.2.2 for JuopunutBear S-OFF ==========
Connecting to device...
adb server is out of date. killing...
* daemon started successfully *
Press ENTER to exit.....
This is all I can get when running controlbear 2.2
Removed htc sync, ran as admin, no antivirus, fresh sd card
Icc firmware with controlbear ics windows, Fresh ruu
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?