__________________
The Delivery Guy
If someone has helped you,please click the THANKS button on that post.
Please post questions so others can benefit from the answers. donate to my device fund
The Following 6 Users Say Thank You to scotty85 For This Useful Post:
Is it looking like it really *is* going to happen...ie it's just a matter of time. Or is it still a big "if" that it's possible to be able to do at all? Just curious because if I can root w/o registering my Rezound with HTC Dev, that would be totally awesome. (yeah, I know there are other complications with s-off and it isn't a panacea but neither is "bootloader relocked" )
You can bet that when/if it is achieved. Twitter and all Android Blog sites will be blowing up about it.
__________________
I used to be Android all the way but bought an Iphone 5 in October. Feel free to ask me how it's going via PM.
GO BRONCOS AND ROLLLLLLL TIDE!!!
From what i've read it is a lot of work involved. Not only that but you dont' want an S-Off method released unless you're absolutely sure it's relatively safe to use for users. The last thing you want to do is release a tool that bricks half of the phones it touches.
From what i've read it is a lot of work involved. Not only that but you dont' want an S-Off method released unless you're absolutely sure it's relatively safe to use for users. The last thing you want to do is release a tool that bricks half of the phones it touches.
from what i understand the rezound testing is done and was successful.
Device(s): HTC EVO 3D (Sprint)
Motorola Xoom 32GB Wifi LTE (Verizon)
iPad 1 16GB (Wifi only)
iPod Touch 8GB
Carrier: Not Provided
Thanks: 124
Thanked 88 Times in 65 Posts
Quote:
Originally Posted by fixxxer1022
from what i understand the rezound testing is done and was successful.
But it is very hard telling what all went in to them getting s-off.
Go look over on the xda htc evo 3d forums about downgrading the hboot version. You have to basically brick your phone then bring it back from being bricked.
Just saying that's an example of some of the way these guys figure out how to achieve things.
id like to know whats taking them soo long to release this?
Quote:
Originally Posted by fixxxer1022
from what i understand the rezound testing is done and was successful.
the tool works on multiple devices,and as such will not be released until all testing is finished. there were some not-so-good results with MT4GS,so its hard to say what refinements and retesting that device may need.
in general i suggest being happy that there is light at the end of the tunnel,instead of being impatient and angry its not out yet
The Following 2 Users Say Thank You to scotty85 For This Useful Post:
the tool works on multiple devices,and as such will not be released until all testing is finished. there were some not-so-good results with MT4GS,so its hard to say what refinements and retesting that device may need.
in general i suggest being happy that there is light at the end of the tunnel,instead of being impatient and angry its not out yet
I guess maybe I don't do enough with my phone, but what good does S-off do me? I can unlock, install a ROM, gain Root, etc. etc. What does S-off get me?
I guess maybe I don't do enough with my phone, but what good does S-off do me? I can unlock, install a ROM, gain Root, etc. etc. What does S-off get me?
in a nutshell: it gives you access to all partitions. you can change everything,not just boot/system/recovery,like our current setup.
lots of folks like to change splash images and radios,wich you cannot do with our current unlocked s-on arrangement.
you can also go backwards in build numbers,and run older ruus. so if you were s-off,and flashed the leaked ics RUU and didnt like it,no biggie. you can revert back to gingerbread radios,hboot,software,etc. by simply running an older, GB RUU. you can even go back to original shipping firmware.
because you can flash literally anything,you do have a bigger responsbility to be informed about what your doing,what youre flashing,and why. double and triple check the integrity of anything you flash by verifying md5 sums,as flashing a bad bootloader or radio will leave you with an unrecoverable,hard bricked device.
it will also let "boot" be written from recovery,making the seperate kernel flashes we do now un-neccessary(as soon as devs build their roms to flash the kernel from recovery)
it is my opnion,that s-off is better,as long as caution is used in flashing,as it gives you more options to recover a soft brick. you can easily install an eng hboot(wich will offer extra fastboot commands),install a recovery,or run an older RUU.
s-on or s-off is describing the status of the radio secure flag. basically its "security on" or "security off". since it is housed in a location seperate of all other partitions,you will stay security off no matter what hboots or RUUs are flashed,until you purposely change it.
oh... almost forgot
big thing most folks are excited about(i dont really care,as i have no mfg warranty) is the fact that an s-off phone can change the relocked status back to shipping status of locked and then the security turned back on,thus fooling htc/vzw that any unlocking trickery has occured,and preserving your manufacturer warranty if you need it
last and not least,if none of these things appeal to you,notihng wrong with staying unlocked s-on. it does add a degree of safety,as the s-on hboot will only flash newer,htc signed files,making it nearly impossible to brick by flashing bad firmware.
hope that helps
The Following 5 Users Say Thank You to scotty85 For This Useful Post:
jupunutbear tweeted their website in hexidecimal yesterday,and the irc channel now reads:
JuopunutBear pre-release testing concluded | PMs without permission: 1st time=kick 2nd time=kickban | Asking for future plans or an ETA is a bannable offense | No offtopic chat | English only. | Not JuopunutBear is off topic
Very cool!!!! I didn't see an answer on that site for my questions... So now I can get s-off and flash the gingerbread RUU going back to factory stock? And this will allow me to get the OTA update next month? And finally can I use the same method to s-on again in case the phone ends up with a warranty issue or am I stuck with s-off (which doesn't necessarily seem like a bad thing)?
Location: West edge of the East Texas Piney Woods (Just north of Houston)
Gender: Male
Posts: 762
Device(s): HTC One, Nexus 4, Nexus 7 WiFi
Carrier: AT&T
Thanks: 257
Thanked 105 Times in 99 Posts
Looks kinda Rube Goldberg. Have you tried it out Scotty?
__________________
************************************************** ****** "Any sufficiently advanced technology is indistinguishable from
magic." - Arthur C. Clarke
Location: West edge of the East Texas Piney Woods (Just north of Houston)
Gender: Male
Posts: 762
Device(s): HTC One, Nexus 4, Nexus 7 WiFi
Carrier: AT&T
Thanks: 257
Thanked 105 Times in 99 Posts
Quote:
Originally Posted by pwhoever
Very cool!!!! I didn't see an answer on that site for my questions... So now I can get s-off and flash the gingerbread RUU going back to factory stock? And this will allow me to get the OTA update next month? And finally can I use the same method to s-on again in case the phone ends up with a warranty issue or am I stuck with s-off (which doesn't necessarily seem like a bad thing)?
Reading the XDA thread is kinda confusing, but that looks to be the case. I know it's what I'll try when I get the nerve up to do this.
I totally wanted S-Off, but uh, I'm not doing this.
Yeah I think I'll wait for a more secure way of doing this along with them fixing all the quirks....let the dust settle. But great work to the devs for achieving this. I'm in no hurry...
Location: West edge of the East Texas Piney Woods (Just north of Houston)
Gender: Male
Posts: 762
Device(s): HTC One, Nexus 4, Nexus 7 WiFi
Carrier: AT&T
Thanks: 257
Thanked 105 Times in 99 Posts
Quote:
Originally Posted by scotty85
*high five* welcome to the club,sir jacket and cigar... on the table!
ive done it twice now. first time i hit it on the 2nd wire touch. second time it took me several
it is just a lil scary
It IS a little scary, and it took me about 6 tries with the wire. But afterwards I needed the smoke and a snifter of brandy!
As proof that it worked, I was able to go back from the latest leak to the last official OTA. So, I'm back on the upgrade path now even!
Rooting and installing a new ROM was as easy as ever and was able to make a nandroid - all using Amon RA. In short - everything still works!
Now, time to sit back and offer encouragement to anyone else who wants to try it. I don't recommend that anyone who isn't comfortable with messing with your phone like this try it and there's nothing wrong with not wanting to. (Just like there's nothing wrong with deciding to not do anything you don't want to to your phone). And I hope an easier way comes about.
But, it does work and my hats off to the guys who managed to figure it out. Now, time for lots of coffee!
The Following User Says Thank You to WA_Bob For This Useful Post:
Ihave to say that the timing if the wire trick was tricky. Took me forever to get it right. I finally ended up watching the video and timing it with it. Now though I'm s-off. Already changed my splash screen too
Location: West edge of the East Texas Piney Woods (Just north of Houston)
Gender: Male
Posts: 762
Device(s): HTC One, Nexus 4, Nexus 7 WiFi
Carrier: AT&T
Thanks: 257
Thanked 105 Times in 99 Posts
Quote:
Originally Posted by StillLoading
That's what I did. A paperclip works a little easier though from what I've heard (insulated with electric tape)
Well, I used the paperclip after I read about someone else doing it and it worked but the right sized piece of wire would work better IMO. That would allow you to use two hands and it looks much easier that way.
The Following User Says Thank You to WA_Bob For This Useful Post:
Well, I used the paperclip after I read about someone else doing it and it worked but the right sized piece of wire would work better IMO. That would allow you to use two hands and it looks much easier that way.
i concur. i used a small piece of wire
The Following User Says Thank You to scotty85 For This Useful Post:
I knew I shouldn't have done this - LOL - it failed the first time around. Now I'm stuck at the arrow screen and I cannot get into recovery of any sort. When I pull the battery and restart, it just boots to the arrow and sits there. When I pull the battery and attempt to get into recovery it just keeps booting into fastboot and it sits there.
You need to flashyour boot.IMG again or re run the tool from there. It picks up where it left off
I can rerun the tool from the arrow? I've tried that to no avail
How do I flash my boot.img again - from the command prompt on my PC?
Edit - OK - somehow after all of my fiddling I ended up being able to restart the phone and I'm back on the home screen. I don't know how or why this happened, but it did. Yay. Now it's not seeing my SD card but I think I'm going to try and start over.
Last edited by mtbhk44; April 22nd, 2012 at 04:07 PM.
I must be ******ed (no offense to the mentally ******ed). I wonder if I'm not doing the wire trick right. I cannot get this to take. Do you have to touch the contacts more than once, or just touch both within 1.75 seconds. I'm getting errorcode 66732337. Still sober. GRRRR
Yeah I think I'll wait for a more secure way of doing this along with them fixing all the quirks....let the dust settle. But great work to the devs for achieving this. I'm in no hurry...
Edit: OMG, some powerful, evil, dark force took my body over. It forced me to do it. I didn't want to I swear....I swear. It just took total control of me.
And ladies and gentlemen it made do it...I achieved s-off.
Edit: OMG, some powerful, evil, dark force took my body over. It forced me to do it. I didn't want to I swear....I swear. It just took total control of me.
And ladies and gentlemen it made do it...I achieved s-off.
I have tried seventy five different ways from Tuesday. I cannot, for some reason, get the contacts to receive the wires. I've gone from start to finish and every time I get to the wire trick portion, it fails. I just spent the better part of 10 minutes even getting the phone to accept one wire touch. I think I'm giving up.
Location: West edge of the East Texas Piney Woods (Just north of Houston)
Gender: Male
Posts: 762
Device(s): HTC One, Nexus 4, Nexus 7 WiFi
Carrier: AT&T
Thanks: 257
Thanked 105 Times in 99 Posts
Sounds like it might be time to take a break for a few. But it does indeed work and I can attest that it took a while for me to get my timing down to do it. You can do it!
The Following User Says Thank You to WA_Bob For This Useful Post:
I have tried seventy five different ways from Tuesday. I cannot, for some reason, get the contacts to receive the wires. I've gone from start to finish and every time I get to the wire trick portion, it fails. I just spent the better part of 10 minutes even getting the phone to accept one wire touch. I think I'm giving up.
So from one of your previous posts you cannot re-run the program from your PC.....where it left off? It took me a few minutes to get the wire trick to connect correctly. For a minute it semed like my wire wasn't working. You doing exactly what the ytube video does? What type of wires you're using? Don't give up.
The Following User Says Thank You to imparables For This Useful Post:
I must be ******ed (no offense to the mentally ******ed). I wonder if I'm not doing the wire trick right. I cannot get this to take. Do you have to touch the contacts more than once, or just touch both within 1.75 seconds. I'm getting errorcode 66732337. Still sober. GRRRR
So this means your wire trick is working but you're getting an error message? If so did you extract the zip files from bear, which are 4 files, into the adb file you used to root your phone? Not to be redundant but can you explain from start to finish what you're doing? What firmware and rom you're running?
Sounds like it might be time to take a break for a few. But it does indeed work and I can attest that it took a while for me to get my timing down to do it. You can do it!
It was. I took a break, grabbed some very low grade speaker wire and tried again. SUCCESS!
Last edited by mtbhk44; April 22nd, 2012 at 11:05 PM.
So this means your wire trick is working but you're getting an error message? If so did you extract the zip files from bear, which are 4 files, into the adb file you used to root your phone? Not to be redundant but can you explain from start to finish what you're doing? What firmware and rom you're running?
No, apparently I WAS able to start in the middle, from the arrow. For some reason (probably my own stupidity) I thought I wasn't able to. I probably got impatient. Anyway, I reinstalled recovery and the boot image and I was good to go. I think the missing recovery was the wild card in all of this - just guessing though.
No, apparently I WAS able to start in the middle, from the arrow. For some reason (probably my own stupidity) I thought I wasn't able to. I probably got impatient. Anyway, I reinstalled recovery and the boot image and I was good to go. I think the missing recovery was the wild card in all of this - just guessing though.
So the first time I ran it, it went into fastboot however it stood there, doing nothing. I saw the JuopunutBear boot screen and the computer end was doing nothing. After hours of reapplying my boot/kernel (I needed a working phone) I was done. A few hours later, I decided to give it a shot again so I ran the program but this time, my phone wouldn't even restart at the moment the program said it would. I read a bit more about this and saw that you have to be in the current rom and let the program do it's thing automatically. One thing I didn't want to do was wipe/reinstall my ROM but seeing as nothing else worked, I had to take that route. Despite me wiping the phone, re-installing the ROM (inefabilis 1.4 at the time) the darn thing would still do nothing. Frustration got the best of me and decided I would leave it for tomorrow. I had some time yesterday and decided the last resort would be to RUU back after a few more attempts. While I was RUUin'g I needed a rom of some kind just to get through the program so I went with RezRom 1.6 and had it ready to copy over once the RUU was done. RezRom was installed, I started the program and to my relief, it was finally doing the steps properly. Once I ran that, I was able to get through the whole way through and the wire trick I got working on the first try. I think I had read so much of people's experiences and what to do that I was able to pull it off that quick. Once installed, I wiped the phone and went back to Inefabilis and now I have an S-off rezound . This whole time I wanted to preserve the phone without wiping but I guess I should have RUUed from the get go. Just wanted to give my experience with this and would highly recommend just RUU'ing back. All the time spent on figuring out the problem proved somewhat fruitless since it was on my end rather than the program's end.
Well, I did get S-OFF. It took me two nights (totalled about 8 hours). Required much time at the jBear mIRC chat room for all sorts of things the jBear website doesn't tell you. I was using the original first version of jBear S-OFF, so it is possible things have changed for the better.
jBear's website is
unlimited.io
(no www. )
Here are my pointers:
1. Use a spare SD card. The jBear process will end up wiping it. When you are all done that SD card will need to be totally reformatted. It takes quite some time to format an SD card, so I did it in my PC.
2. Find the kernel boot.img file for the current GB, ICS Leak, or ROM that you are currently using. You also need to know the adb/fastboot commands to flash that kernel file. The jBear process replaces your kernel and reboots to this jBear kernel. If you are not successful at doing S-OFF and want to stop trying and put your phone into a usable state, you will need to flash your saved kernel file. No kernel file equals you can't use your phone.
3. Make a nandroid backup of your entire system (check all boxes in Ramon RA recovery). You might need it - as I certainly did.
4. You download the sBear zip file for your firmware (GB or leaked ICS) and copy the files from the zip file to the directory on your PC where you have the adb/fastboot files stored. (Of course you should have a working adb/fastboot system with the htc drivers installed).
5. Boot up your phone normally, connect phone to PC as charge-only with usb debugging ON, and then run the jBear exe file on your PC. You don't know how much time I wasted trying to run the jBear exe file and getting errors while the phone was in bootloader/fastboot mode. The video on the jBear website shows starting off in hboot/bootloader - probably to show the before picture, but I thought I was supposed to start at that state. Also, the video just shows the starting state and ending state of the bootloader screen and does not show even a single step that one takes to perform the jbear S-OFF process.
6. When the jBear exe file tells you to do the wire trick, keep trying to do the wire trick until the software stops asking you to do it. I used a large insulated paper clip with the insulation stripped off a bit on each end. It is important to keep the paper clip straight in the pin#1 hole to make good electrical contact. You need to touch the other end of the paper clip briefly to the ground pin and then do it again after waiting 1.75 seconds. So this takes alot of trying.
7. I am on GB, and the jBear program installed the ENG hboot. The bootloader screen looks different than other peoples' screen. This is because they were on the ICS leak and received a different hboot program from hBear. My screen said "ENG S-OFF" and did not say Juoblahblahcan'st spell it. So, I naturally got help and repeatedly reflashed the hboot file, but never got the same screen as the other successful S-OFF people - this was another waste of my time due to incomplete directions.
8. I think we should just call it F**KBear until the wonderful developers change the name to something everyone can easily remember and spell.
In general the entire HTC user family is gratefull for this capability. It will probably provide us with valuable capabilities. For example, I have read S-OFF should allow us to RUU backwards to previous versions of official HTC/Verizon released operating systems.
Regards,
Howard
Last edited by howardz2; April 24th, 2012 at 03:01 PM.
The Following 2 Users Say Thank You to howardz2 For This Useful Post:
Well, I did get S-OFF. It took me two nights (totalled about 8 hours). Required much time at the jBear mIRC chat room for all sorts of things the jBear website doesn't tell you. I was using the original first version of jBear S-OFF, so it is possible things have changed for the better.
jBear's website is
unlimited.io
(no www. )
Here are my pointers:
1. Use a spare SD card. The jBear process will end up wiping it. When you are all done that SD card will need to be totally reformatted. It takes quite some time to format an SD card, so I did it in my PC.
Excellent advice, I used an old 2GB sdcard and formatted it prior to starting the process. When it was all said and done though, my sdcard was blank, but did not need reformatting, YMMV.
Quote:
Originally Posted by howardz2
2. Find the kernel boot.img file for the current GB, ICS Leak, or ROM that you are currently using. You also need to know the adb/fastboot commands to flash that kernel file. The jBear process replaces your kernel and reboots to this jBear kernel. If you are not successful at doing S-OFF and want to stop trying and put your phone into a usable state, you will need to flash your saved kernel file. No kernel file equals you can't use your phone.
3. Make a nandroid backup of your entire system (check all boxes in Ramon RA recovery). You might need it - as I certainly did.
Always good advice to CYA
Quote:
Originally Posted by howardz2
4. You download the sBear zip file for your firmware (GB or leaked ICS) and copy the files from the zip file to the directory on your PC where you have the adb/fastboot files stored. (Of course you should have a working adb/fastboot system with the htc drivers installed
5. Boot up your phone normally, connect phone to PC as charge-only with usb debugging ON, and then run the jBear exe file on your PC. You don't know how much time I wasted trying to run the jBear exe file and getting errors while the phone was in bootloader/fastboot mode. The video on the jBear website shows starting off in hboot/bootloader - probably to show the before picture, but I thought I was supposed to start at that state. Also, the video just shows the starting state and ending state of the bootloader screen and does not show even a single step that one takes to perform the jbear S-OFF process.
Note: The file I got was called ControlBear.exe and that you should run the .exe file from the gui (as administrator), not the command line (I was using Windoze). After successfully doing my phone, I went to do another and since I was in a shell already, tried to run it from there and kept getting "Can't find the bar" errors.
Quote:
Originally Posted by howardz2
6. When the jBear exe file tells you to do the wire trick, keep trying to do the wire trick until the software stops asking you to do it. I used a large insulated paper clip with the insulation stripped off a bit on each end. It is important to keep the paper clip straight in the pin#1 hole to make good electrical contact. You need to touch the other end of the paper clip briefly to the ground pin and then do it again after waiting 1.75 seconds. So this takes alot of trying.
If you get the message still sober, all you should need to do to try again is exit the ControlBear.exe and rerun it, do not reboot your phone.
Quote:
Originally Posted by howardz2
7. I am on GB, and the jBear program installed the ENG hboot. The bootloader screen looks different than other peoples' screen. This is because they were on the ICS leak and received a different hboot program from hBear. My screen said "ENG S-OFF" and did not say Juoblahblahcan'st spell it. So, I naturally got help and repeatedly reflashed the hboot file, but never got the same screen as the other successful S-OFF people - this was another waste of my time due to incomplete directions.
Agreed, the directions on the unlimited.io page leaves much to be desired, and wading through pages of posts on the forums can be confusing. The important thing you should see on the bootloader screen is S-off.
I was fortunate in the fact I was able to achieve S-Off on the first attempt.
__________________
"We only need stay diligent and keep watching the stars. And one day there will come a familiar flash, an undulating blue tunnel will appear, and Moya will come racing into our lives once again.I can only imagine the awesome stories our friends will have to tell us then..." - Rockne S. O' Bannon Feb 2003
Last edited by Skorpios1027; April 24th, 2012 at 04:01 PM.
When and where for S-off
(yeah, I know there are other complications with s-off and it isn't a panacea but neither is "bootloader relocked" 
)
