S-off is Official!!! With Instructions...

RKight · Apr 25, 2012

I can't help but wonder if my phone is defective or if maybe I've messed it up by trying this too many times. The first few times I attempted this, I would watch the video and touch the contacts exactly when the person in the video would. My phone would restart, controlbear would do its thing, then I'd get the still sober message. Now, if I time it exactly right (whether by the video or the metronome file that was uploaded), my phone never restarts and controlbear sits at "waiting for device". I just get a blank screen, no charge LED, and I get the sound from Windows that indicates that the USB device wasn't recognized. The phone also shows up in device manager as QHSUSB_DLOAD. If I pull the USB cable and battery, I'm able to restart the phone. For what it's worth, I even ran the android police RUU and rooted through Aman-Ra to get as close to stock as possible.

teckels · Apr 25, 2012

I only had access to one sd card, copied it to desktop before procedure and when I put it back I lost my Temple Run stats! Helppppp! JKJK, just a huge thank you post to everyone that worked to get S-off and to the patient folks helping people with issues. I understand it's frustrating but every community has their boneheads and every customization has it's issues. THANK YOU! (If this helps anyone looking for a wire, I used a twisty tie that I stripped with my teeth Ron Swanson style for the wire trick, worked on second pass).

whtciv2k · Apr 25, 2012

RKight said:
I can't help but wonder if my phone is defective or if maybe I've messed it up by trying this too many times. The first few times I attempted this, I would watch the video and touch the contacts exactly when the person in the video would. My phone would restart, controlbear would do its thing, then I'd get the still sober message. Now, if I time it exactly right (whether by the video or the metronome file that was uploaded), my phone never restarts and controlbear sits at "waiting for device". I just get a blank screen, no charge LED, and I get the sound from Windows that indicates that the USB device wasn't recognized. The phone also shows up in device manager as QHSUSB_DLOAD. If I pull the USB cable and battery, I'm able to restart the phone. For what it's worth, I even ran the android police RUU and rooted through Aman-Ra to get as close to stock as possible.

THis is the exact issue i've been having for 72 hours. my buddy got it in 10 minutes and i've been trying to do mine. I know that i'm doing it right 100%....

---------- Post added at 09:27 AM ---------- Previous post was at 09:22 AM ----------

a.mcdear said:
Well if its not your timing, that only leaves your contact with the pin on the second try that is off. The first contact initiates the reboot, so it HAS TO BE either your timing or you just simply fail to make proper contact the second time.

You're probably too frustrated to think straight anyways by now. Drink a few beers, watch some TV, try again later.

I know exactly what these guys speak of. I can't even get the process to the point where it asks to do the wire trick. Is it because i'm doing it wrong? I don't think so.... I've done things like this before and am pretty mechanically inclined.

---------- Post added at 09:30 AM ---------- Previous post was at 09:27 AM ----------

maximus20895 said:
well **** this. It's not worth my time anymore.

Really pissing me off.

I'll just wait until there is a better method..

Took the words right out of my mouth.

---------- Post added at 09:32 AM ---------- Previous post was at 09:30 AM ----------

a.mcdear said:
Its actually quite fascinating to me to see so many varied results and peoples' reactions to the process. I'm also starting to realize that most of the people in here will put pretty much anything on their phone (or do pretty much anything to it..) even when they clearly have no idea what they are even doing it for.

I mean seriously, half the people in here trying to get S-OFF and driving themselves insane probably shouldn't even be worrying about it anyway. But they will do it anyway. And then the next thing they'll do, for no apparent reason and without knowing anything at all about them, is start flashing radios. Then the next thing they will say is they can't make calls anymore and can't figure out why...

Useless rant. It's a learning process. Once they achieve S-OFF they'll figure out how to do some of the other cool things. I know the quickest way I learn how to fix things is to break it first.... Not always but it's true.

graymonkey44 · Apr 25, 2012

For those having issues that are on windows, try Linux. May be a long shot, but download wubi.

Sent from my ADR6425LVW using XDA

derek4484 · Apr 25, 2012

redbean25 said:
Might I suggest solid wire instead of stranded. The stranded wire is difficult to get good contact. If you take a narrow gauge stranded wire and double the strands back on themselves then twist it, that helps, but solid core wire is the way to go...or a paperclip...same type of thing.

I absolutely agree. I used 22AWG hook-up wire, the type of wire used for breadboarding prototype projects. Its fairly stiff and doesnt flex. I think that's why a lot of people are having good success with paperclips. They are easy to keep in contact with the contact points rather than some flimsy flexible soft stranded wire.

whtciv2k · Apr 25, 2012

derek4484 said:
I absolutely agree. I used 22AWG hook-up wire, the type of wire used for breadboarding prototype projects. Its fairly stiff and doesnt flex. I think that's why a lot of people are having good success with paperclips. They are easy to keep in contact with the contact points rather than some flimsy flexible soft stranded wire.

Tried that. I've used a paper clip, speaker wire, solid core wire, stranded wire. If it conducts electricity and fits in the hole, i've tried it.

AndroidGraphix · Apr 25, 2012

For those having problems, you were not alone. It took me a couple hours on one phone and about 2 days on my other. If it helps, here's a thread I made that may help getting that wire trick right.

http://xdaforums.com/showthread.php?t=1613776

Sent from my ADR6425LVW using xda premium

RKight · Apr 25, 2012

graymonkey44 said:
For those having issues that are on windows, try Linux. May be a long shot, but download wubi.

I have Linux Mint installed, which is based on Ubuntu. I tried under Linux and I got the exact same results (minus the sound indicating an unrecognized USB device, of course).

whtciv2k said:
Tried that. I've used a paper clip, speaker wire, solid core wire, stranded wire. If it conducts electricity and fits in the hole, i've tried it.

Same here...tried everything from a tiny twist tie to speaker wire, solid core aluminum wire, solid core copper wire, etc. And the copper wire definitely wasn't flimsy. It was 14g and I had to take my time to file one end of the wire to a taper so it would fit in the hole and touch the pad on the PCB.

derek4484 · Apr 25, 2012

superchaos said:
OK, So don't hold the wire on the contacts for 1.75 seconds. Touch the contacts 1.75 seconds apart. I touched the contacts about 4-5 times about 1.75 seconds apart after the vibration and it finally went through. It just doesn't start until you are done touching the contacts.

If you aren't getting it, keep trying.

Sorry, but I gotta say DUHHHHH!!! The instructions and the video clearly say and show that you touch the two points together then release, wait 1.75 seconds, then touch them again.

---------- Post added at 10:24 AM ---------- Previous post was at 10:18 AM ----------

After reading all the posts in here about people doing it for 2 days and still not getting it, I guess I was lucky, I did it once, it worked, took like 5 minutes. I didnt lose any info from the internal or external SD cards. Overall it went super smooth and easy.

The only problem was my fault, I refused the modified HBoot that ControlBear offered me, so when it rebooted to fastboot, it was still locked. Instead of flashing a modified HBoot through fastboot, I reflashed my unlock .bin and it did a factory reset on the entire phone so I lost every app and all data. So I had to do a restore from titanium backup.

The only "tricky" part are the instructions (or lack thereof) on the ControlBear website. You must pick the GB or ICS version based on which firmware you are running, not which ROM you are running. If you have the old firmware use the GB version. If you are on the new firmware use the ICS version. The controlbear program is the same, what differs is which modified HBoot it flashes when its done. The GB version flashes a modified, unlocked HBoot 2.11. The ICS version flashes a modified, unlocked 2.21. So if you are on an ICS ROM but using the old firmware patch then use the GB version of Controlbear.

Good luck!

Ronn Plae · Apr 25, 2012

Guys it took me FOREVER!! I READ THIS THREAD AND READ THIS THREAD! The trick is once you stick the wire in the ground just tap TWICE 1.5 Seconds each and if you fail reformat your SD Card every time! It took me 100 times, I'm FINALLY S-OFF!! ALso if you are on Hboot 2.11 DO NOT INSTALL JUNOPEBEAR HBOOT!!! Another mistake I made!

redbean25 · Apr 25, 2012

Ronn Plae said:
...ALso if you are on Hboot 2.11 DO NOT INSTALL JUNOPEBEAR HBOOT!!! Another mistake I made!

That just means you downloaded the wrong JuopunutBear version. If you are on 2.11, then you should have run the GB one which comes with a modified 2.11 Hboot. If you put on 2.21, then you used the ICS version which was incorrect...

JeffBea · Apr 25, 2012

For anyone having problems getting s-off that lives in Columbus Ohio area I be more than glad to do it for you. Took me like 10 minutes and 3 attemps to do mine.

Sent from my ADR6425LVW using XDA

Demiurge7 · Apr 25, 2012

I cant get it past this error:

Hmmm, still no device
Open device manager and check adb and/or fastboot drivers!!
Resetting connection....1........2....

At the green arrow screen when receiving this message, everything else seemed fine. Of course, ran as Admin, checked MD5's, followed all instructions to a T, no HTC sync running, etc.

I have tried on two different computers, and am pretty sure I am up to date on drivers, but have re-setup adb just in case. What am I doing wrong here? I have tried many times - have no problem restoring, but frustrated I cant get past this point.

Any ideas?

thisisjaybee · Apr 25, 2012

Demiurge7 said:
I cant get it past this error:

Hmmm, still no device
Open device manager and check adb and/or fastboot drivers!!
Resetting connection....1........2....

At the green arrow screen when receiving this message, everything else seemed fine. Of course, ran as Admin, checked MD5's, followed all instructions to a T, no HTC sync running, etc.

I have tried on two different computers, and am pretty sure I am up to date on drivers, but have re-setup adb just in case. What am I doing wrong here? I have tried many times - have no problem restoring, but frustrated I cant get past this point.

Any ideas?

If your HTC driver is installed, I would delete the C:\Android folder and reinstall adb and fastboot. (I tried to post a link, but I'm new. Google "How to install adb and fastboot". Use the first link and follow the directions)

xceebeex · Apr 25, 2012

Ronn Plae said:
Guys it took me FOREVER!! I READ THIS THREAD AND READ THIS THREAD! The trick is once you stick the wire in the ground just tap TWICE 1.5 Seconds each and if you fail reformat your SD Card every time! It took me 100 times, I'm FINALLY S-OFF!! ALso if you are on Hboot 2.11 DO NOT INSTALL JUNOPEBEAR HBOOT!!! Another mistake I made!

Is reformatting the SD card really necessary if it passes that step that says laoding sixpack on SD card or whatever it is. I would hope that if the card was not in an acceptable state there would be some sort of error or failed attempt to write whatever it is they write to it (which is another thing, why is an external SD card even necessary?).

whtciv2k · Apr 25, 2012

flashing to the stock RUU seems to work.

TO ALL, if you are having issues, just bite the bullet and flash back to the stock RUU. worked for me the very first time once I did this. Thanks all.

morrichad · Apr 25, 2012

whtciv2k said:
THis is the exact issue i've been having for 72 hours. my buddy got it in 10 minutes and i've been trying to do mine. I know that i'm doing it right 100%....

---------- Post added at 09:27 AM ---------- Previous post was at 09:22 AM ----------

I know exactly what these guys speak of. I can't even get the process to the point where it asks to do the wire trick. Is it because i'm doing it wrong? I don't think so.... I've done things like this before and am pretty mechanically inclined.

---------- Post added at 09:30 AM ---------- Previous post was at 09:27 AM ----------

Took the words right out of my mouth.

---------- Post added at 09:32 AM ---------- Previous post was at 09:30 AM ----------

Useless rant. It's a learning process. Once they achieve S-OFF they'll figure out how to do some of the other cool things. I know the quickest way I learn how to fix things is to break it first.... Not always but it's true.

Just let you all know I had everyone of these error messages that I've seen except one or two of them. Especially this message: "QHSUSB_DLOAD" and just disconneted the cable and pulled the battery, then rebooted into Hboot. Open controlbear.exe and begun again.

There really needs to be an all in one tutorial on this citing different events and how to try to handle them each, if possible. GrayMonkey44 has done an exceptional job of trying to pull everything into one place and with additional tips to go with this S-off development

. But I feel in some areas the guide lacks additional needed information?

I want to personal Thank You to team of JuopunutBear, Con for his posts on how to get back into your device in case of semi screw-ups; ie; being stuck @ JuopunutBear screen left being stuck scratching your head trying to figure what to do next, hgoldner for mini How-To helped me get started and to the end of the process and the metronome was very helpful! Their were others as well and will post a personal thank you once I gather all the names.

Trust me I screwed up a lot and was always able to figure my way back out of all my predicaments. Though it was scary & hair raising @ certain times.

I will try to post helpful tips and pull some quotes from other posters to help from both threads together to help out. Yes I wish I would read the other S-Off FAQ thread especially cause there is statements and ideas in there to help too. Noticed was having some the issues in the thread of S-off FAQ that would helped me sooner with some of my problems. If anyone reads that thread start in around page 100 and go from there and there will some additional enlightening information to help.

Some tips I can post now is if using a paper clip wrapped in tape on both ends where bent. Take paper clip and bend the 2 ends and this way Pin1 make that one end long to go in to the hole. On the other end shorten that up that end to touch ground. If the wire trick doesn't work from Pin1 to Ground, reverse the directions and go from Ground to Pin1. I also left on piece of the clip in Pin1.

Using a metronome provided by hgoldner on pg. 95 of this thread listen to beats in between the time pauses one wil be low the next will be high. When doing the wire trick to the beat pop one end in one contact(Pin1), there will a lite clicking sound and right before the next beat pop the other contact(ground) and release and should start the rest of the exploit.

I also got errors of local/data/JuopunutBear: not found and no beer for bear also. Try deleting the files you inserted into your adb/sdk files you inserted and other copies of stuff that shouldn't be in there. Unzip the JuopunutBear zip again and reinstall those files. Go to adb the folder that houses the adb/fastboot files and right click on the root folder for adb.exe file and can open a command window from there as well.

Make sure if needed between any errors if your not sure is to format sdcard via computer in Fat32 format.

****Also remember to have a copy of your recovery.img & boot.img handy.****

****Most important and I can't this stress enough is to make sure you make a copy your of internal & external cards. ****

---------- Post added at 01:09 PM ---------- Previous post was at 01:06 PM ----------

Demiurge7 said:
I cant get it past this error:

Hmmm, still no device
Open device manager and check adb and/or fastboot drivers!!
Resetting connection....1........2....

At the green arrow screen when receiving this message, everything else seemed fine. Of course, ran as Admin, checked MD5's, followed all instructions to a T, no HTC sync running, etc.

I have tried on two different computers, and am pretty sure I am up to date on drivers, but have re-setup adb just in case. What am I doing wrong here? I have tried many times - have no problem restoring, but frustrated I cant get past this point.

Any ideas?

May I ask what mode your are starting in. Are in android(your Rom)mode or Hboot.

graymonkey44 · Apr 25, 2012

Don't worry guys. I'm going to go through every post of this thread and compile everything I can together to make it easy and straight forward as possible.

Sent from my ADR6425LVW using XDA

Blacktruck · Apr 25, 2012

Demiurge7 said:
I cant get it past this error:

Hmmm, still no device
Open device manager and check adb and/or fastboot drivers!!
Resetting connection....1........2....

At the green arrow screen when receiving this message, everything else seemed fine. Of course, ran as Admin, checked MD5's, followed all instructions to a T, no HTC sync running, etc.

I have tried on two different computers, and am pretty sure I am up to date on drivers, but have re-setup adb just in case. What am I doing wrong here? I have tried many times - have no problem restoring, but frustrated I cant get past this point.

Any ideas?

I am having this same problem as well. Reinstalled SDK and drivers, but still cant get past this process. I'm able to get back into fastboot and flash recovery, so its not like my pc cant detect my phone.
FWIW, I'm on GB, using CleanRom 4.3 using old firmware patch.

What appears to be happening is when ControlBear reboots the bootloader and sends the phone into the black screen with green arrows, it breaks connection between the phone and pc and cannot find the device.

maximus20895 · Apr 25, 2012

superchaos said:
OK, So don't hold the wire on the contacts for 1.75 seconds. Touch the contacts 1.75 seconds apart. I touched the contacts about 4-5 times about 1.75 seconds apart after the vibration and it finally went through. It just doesn't start until you are done touching the contacts.

If you aren't getting it, keep trying.

I don't know what this means.

Sent from my ADR6425LVW using Tapatalk 2

S-off is Official!!! With Instructions...

Senior Member

Attachments

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

New member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Similar threads

Top Liked Posts