Sent from my ADR6425LVW using Tapatalk 2
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 ----------
May I ask what mode your are starting in. Are in android(your Rom)mode or Hboot.
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.
I am starting in Rom mode (running scotts cleanrom senseless dev edition). I am reinstalling fastboot and ADB, completely uninstalled anything HTC, starting from scratch - but it seems as though if it got as far as it did, then the drivers and adb should have been working properly - I tested adb beforehand, pushing, pulling, and running various commands... I made sure everything was working and in line. So its a little confusing. Will try re-installing adb and fastboot, maybe will go back to the RUU as well, just to be sure. Will take any idea's though, thanks!
---------- Post added at 03:44 PM ---------- Previous post was at 03:42 PM ----------
Thats exactly what I was thinking... I was able to flash the backup recovery and the ICS kernel from my rom immediately after, in fastboot. So your right, its not as though my computer is not seeing the phone - rather, control bear doesnt seem to be able to see it... I havent seen many with this issue (one I found in the sensation thread for juopnutbear).
|Thread Tools||Search this Thread|