yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] kcirtap420:
Finally worked! I am s-off now, not sure what was going on I didn't do anything different besides flashing 1-12 cm11. I got to pouring 2 and got a screen of dots so I ended the program in a bootloop, went to bootloader and saw s-off. Wouldn't boot until I switched to cwm and fresh flashed.
[HTC Rezound] jrat69:
acejavlin, do we have to re-lock ? I tried to run this and I am un-locked Rooted, S-off. It got part of the way through and error-ed, said couldn't find install files, I had renamed to PH98IMG.zip and had it in the main directory of my SD card.
[HTC Rezound] acejavelin:
Ummm... Guess i am not sure what your asking. This thread is about getting S-OFF with rumrunner, if you are already S-OFF you do not need to do anything.
[HTC Rezound] Master VD:
As I understood, this programm will make me S-OFF?

(Sorry for broken English)
[HTC Rezound] Uncleheff:
Yes this will make you s-off. If you follow the instructions it will work. It worked for me.
[HTC Rezound] pball52998:
Well I'm s-off the exploit finished...... but now won't boot. Trying to reflash my backups.... I'm s-off or at least it says I am. So those two little words just change everything. No having to fastboot flash the boot.img anymore? Restore backups with a swipe? Correct?
[HTC Rezound] Icyman:
my attempt failed multiple times. is the stock rom the problem?

it never says "fail" only press enter to exit.
[HTC Rezound] acejavelin:
Yes, the stock ROM is the problem... A basic requirement that is repeated over and over is that an UNSECURE KERNEL is required, in other words, a custom kernel (typically included with a custom ROM).

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

On another note, Has anyone tried the Firewater S-OFF tool yet?

http://www.androidpolice.com/2014/0...f-tool-will-unlock-any-htc-device-in-moments/

It is supposed to work with any "modern" Qualcomm based HTC phone, I would think the Rezound should fit that description.
[HTC Rezound] pball52998:
With the firewater thing I think its called. I would love to try it. But this being my only phone... Now if I had another Rezound I would gladly try it :) just happy with my phone now xD glad everything is set. but if I had another Rezound I would go right for it

Sent from my Rezound. CyanogenMod 11. S-off
[HTC Rezound] Icyman:
you are very correct. 3rd line.

I updated to 4.4 and tried again. after rows and rows of dots, I realized I didn't turn off my firewall. multitasking leads to this. oddly this did fine with my DNA.

now I'm stuck in a boot loop.

Any solutions?
[HTC Rezound] acejavelin:
Does it say S-Off in hboot? If so, just reflash ROM.
[HTC Rezound] Icyman:
yes it does.

I did that but still in boot loop.

I then flashed CM recovery and reflashed rom but still in recovery.

what do you suggest?

Edit: I'm on hboot 2.25
[HTC Rezound] acejavelin:
RUU
[HTC Rezound] Icyman:
I have no experience with RUU. can you point me in the right direction. a link to directions would be great or tell me here. thanks.
[HTC Rezound] acejavelin:
Look in Q&A section for [MENTION=5037435]REV3NT3CH[/MENTION] downgrade upgrade guide, might as well go through the process but you can probably just start at the one for 3.14.605.12 if in a hurry.

Dont worry, if you are S-OFF and can get to hboot, you'll come out of this ok
[HTC Rezound] Icyman:
Sweet worked perfectly.

I started with 3.14.605.12 without any problems.

Thanks!
[HTC Rezound] Chillerman:
From my understanding Firewater is a modified/updated version of Rumrunner because HTC/Verizon figured out how to patch the exploit it uses with newer releases. Both are made by the same Devs. I'm sure it works much like Rumrunner does for the Rezound.
[HTC Rezound] scotty1223:
Has anyone gotten it to work? I tried firewater on the rezound right after its release,and could not get it to work. I used the same rom/kernel that worked with rumrunner on a 32 bit unbuntu 12.04 laptop

If someone had success I'd be pretty interested in hearing their details :)
[HTC Rezound] Huachipato:
It just worked for me. Got the screen of dots - let it go for about 20 minutes - but the screen now says "VIGOR PVT SHIP S-OFF RL". :)

I did have the firewall and Antivirus running. I'm on my work PC - so I didn't have the ability to to turn either off and realized after the screen of dots that I had done so.

S-Off anyways! :) Stuck in boot load screen - but about to install a fresh rom - so hopefully it won't be an issue.
[HTC Rezound] CoolJourney:
I was able to achieve S-OFF via this method. I was prepared to try the wire method and thought I would give this one a try first. I was on Nil's Business ICS 4.0.3 Sense 3.6 (ver 6.4) ROM (now am on Evervolv--boy is it ever sweet). I found that Rumrunner program didn't like my data connection being on wireless. When I switched to a regular 4G data connection it seemed to be happy. Also, the first time I ran it the program unpacked some files and put them in a "file" directory. The next time I ran it it saw the "file" directory and errored out. I deleted the "file" directory, reran the program and all was good. Thanks to the original poster for bringing this program to our attention!
[HTC Rezound] Chucktr:
64-bit openSuSE Linux -- not quite

Well, we used it... with half-assed success!! Probably more our fault than yours -but- the two things good about it were;

#1) We got S-Off without a wire trick.

#2) We both learned, and found out, how much we know, and don't know, about these Smartphones.

What we used was probably our reason for our "mishaps". In the beginning it is stated, unfortunately like the 'wired' version, that a 32-bit Ubuntu Linux -is preferred. Well, we bullheadedly, went ahead and used our openSuSE 64-bit Linux. We had/have 32-bit libs installed -- as they said that 'may' work. On top of that we had CM11.0 installed on our ReZound.

We followed the instructions on the WebPage -and- it was looking good... until it got to pouring (2). Then we started getting HTC White Screen and CyanogenMod Wheel... alternating on the phone in a mini boot loop, with repeated rows of dots on our PC. After an hour plus, I killed it. Then the fun started... trying to "Restore our Phone"!!

We could not, successfully, get anything to Re-Load on our phone. Finally, as a last resort, we decided to use the RUU from Android Police. It changed our hBoot back to 2.27 and our radios back to 2.22 -BUT- it Re-Stored our phone! We then used the Global Firmware Update to get back to 2.28 hBoot and 2.23 radios.

Oh... did we forget to mention that we got S-Off!! Without a wire. Probably would have been much cleaner and smoother had we just broke down and used 32-bit Ubuntu Linux in the first place. -But- we like our openSuSE and "try" to use it for everything... that we can. Possibly we didn't get 'all' of the 32-bit libs installed -or- something like that. IF there is a next time we will probably try again. Till then we will just enjoy our ReZound 'with' S-Off.

Ah, the SD card It got wiped!! Now please notice that we were NOT using the correct system and that could be the reason. At any rate, it got wiped. Wiped so bad that my PC, neither one, would recognize it!! AFTER I got my phone back in operation, on a whim, I put the SD card back in my phone and tried to format it. It did!! I was then able to take it out of the phone, place it in my PC and copy over the saved version. All is well... now.

Thanks to the devs... never liked poking a wire around in my phone. It was great and kudos to the developers of the wire trick. -But- this way, PERFORMED CORRECTLY (Use 32-bit Ubuntu), seems to be safer.

Thanks,

Chuck

P.S.

Forgot to mention that it completely wiped my SD card. Fortunately I had just made a recent backup.
[HTC Rezound] DroidFiend:
Just used and it works flawlessly! Took 10-15 mins. and was done! Great work! Life just got alot easier. One of the best threads for the Rezound.
[HTC Rezound] magwua:
boot loop fixed!

OMG, Thank you! Mine was stuck on pouring (2) as well for 30+ minutes so i just closed the CMD window. Then I could not install any ROM same as you (boot loop not matter what ROM or trying to flashboot a new boot.img). I had to do what you did to get my phone usable operational again. THANKS!
[HTC Rezound] nerdyessence:
I can confirm this works with Neo's Tron 2.2 ROM. It did take a bit but I let it run its course. Below is the screen from cmd prompt.

==================== rumrunner S-OFF 0.5.0 ==============================

rumrunner S-OFF comes with NO WARRANTY (express or implied)

and NO GUARANTEE OF FITNESS for any particular task.

We have made every effort we can to make this a safe process for users

however the authors disclaim any liability for damage to your phone

or other materials or devices used during this process.

The entire risk of running rumrunner S-OFF lies with you, the user.

By using this software you acknowledge and accept that the authors

are not liable for any loss, material or otherwise howsoever caused.

Do you understand the implications of this warning?

(Yes/No)

Yes

Dear User: We will expect that YOU:

(1) Know how to use ADB and FASTBOOT binaries

---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----

(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world

(3) Understand that irc support IS NOT A GENERAL HELPDESK

(4) Are able to identify and download the CORRECT package for YOUR device

(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)

(6) Understand that you may NOT repack or redistribute rumrunner S-OFF

Ok?

(Yes/No)

Yes

!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!

Please wait....

..........

Checking for updates......

Test 1: Rebooting into bootloader

Waiting for fastboot (10/120)

Waiting

Test 2: Booting device

Waiting for ADB (18/120)

must ferment longer...

must sanitize, skunky rum is nasty

hold please..............................................

[------------------------------------------------------------]

Rebooting into bootloader (again)

Waiting for fastboot (5/120)

Waiting for ADB (29/120)

must ferment longer...

chilling..................

smells lovely in here....

heh, just a shot glass for this one....

bottles are packed, here we go, shhhhhh....

pouring (1).............

pouring (2)...........

.

.......................

.........

.......

........

........

.

........................

.

.

...................

..................

....................

.

..

.........

.

........

.

..........

.................

pouring (3).....

Waiting for ADB (16/120)

must ferment longer...

what's that in the bottle still? rum foul, sloppy, real sloppy...

wait for it.........

yep, done. Hope you enjoyed the rum!

Don't forget to send us all your money - rumrunnerdevs@gmail.com

Press ENTER to exit
[HTC Rezound] pball52998:
How long did you get stuck on pouring 2? I was stuck for about 30 min.... Then bootlooped....had to clean flash a different rom then back to Cyanogenmod :/

Sent from my crappy Jailbroken apple iPad.....

Freedoms just another word for nothing left to do... Nothin' ain't worth nothing but it's free.....
[HTC Rezound] Vindicate:
Sticky

STICKY THIS NOW. Lol please XDA Gods
[HTC Rezound] Vindicate:
What..

Kay so no s-off for me. heres what I get. I'm on CM10.1 on Funky Kernel
[HTC Rezound] Neo:
You should try again.
[HTC Rezound] LinuxBeatsApple:
Dint work

!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!

Please wait....

Checking for updates......

Test 1: Rebooting into bootloader

Waiting for fastboot (17/120)

Waiting

Test 2: Booting device

Waiting for ADB (20/120)

must ferment longer...

must sanitize, skunky rum is nasty

hold please..............................................

[************************************************************]

Rebooting into bootloader (again)

Waiting for fastboot (17/120)

Waiting for ADB (22/120)

must ferment longer...

chilling..................

it's a little stinky here, hmm....

bottles are packed, here we go, shhhhhh....

hmm, cap is on tighter than I expected........

pouring (1)...

WTF: What are you doing?
[HTC Rezound] pball52998:
What ROM are you using? Kernel? Radios? Please provide more information.

Sent from my Rezound running Sense 5. s-off
[HTC Rezound] LinuxBeatsApple:
**** Tampered****

****Unlocked****

VIGOR PVT SHIP S-ON RL

HBOOT-2.25.0000

RADIO-1.22.10.0421r/1.22.10.0424r

OpenDSP-v13.6.0.7611.00.0104

eMMC-boot

Apr 12 2012,16:47:46

im on vzw update 1.3 something.

And Im using amon ra
[HTC Rezound] acejavelin:
Must be on an unsecure kernel, stock VZW kernels won't work... Flash Funky or a custom ROM then use rumrunner
[HTC Rezound] pball52998:
I thought you couldn't be on sense at all???

Sent from my Rezound running Sense 5. s-off
[HTC Rezound] acejavelin:
It has been noted several times that on the Rezound all that is required is an insecure kernel (even though the official says says it might not be). I did it once on EclipticRez Revamped (Sense ROM) and it worked fine.

Make sure you read the instructions carefully on do EVERYTHING it says on http://rumrunner.us/instructions/
[HTC Rezound] pball52998:
Yeah, unsecured kernel is a big one. But dang could've sworn it couldn't be sense, eh o well whatever works :p I did mine on cm 11 and was in a never ending bootloop :D and none of my backups worked :D but yes all lord mighty read the instructions!! Good luck!!!

Sent from my Rezound running Sense 5. s-off
[HTC Rezound] acejavelin:
Yeah, bootloop is pretty common, messes up the /boot partition... usually just reflash the boot.img or restore a backup are all that is needed. Worst comes to worse, you would then be S-OFF, you can flash about anything. :)
[HTC Rezound] pball52998:
I must be one messed up apple then. I tried flashing boot.img tried doing 4 backups, tried flashing CM 11, 10.2, Ecliptic, sense 5 -,,,,,,,,,,,- nothing worked -,,,,,,,- somehow PAC saved me... Urgh #(+#!%(@%+$!2+'+$+ -.-

Sent from my ARTified OG HTC Incredible running Cyanogenmod 11
[HTC Rezound] thablackphoenix:
I ran this last night with Evervolv on my phone. Once I got ADB working it ran until "pouring (2) ...(...)" then filled my screen with dots. I lost patience somewhere past 30 minutes and pulled the battery. Bootloader says s-off! I'm not sure if it messed up my current ROM because I planned on changing it anyway, but I've been able to flash other ROMs with no issues.
[HTC Rezound] acejavelin:
Pretty common on the Rezound actually when using rumrunner... There is no kind of or partial S-Off.
[HTC Rezound] needtoride:
Does anyone know how to disable fast boot in INFECTION-2.9.1? I can't find "Power" under Settings. Only "Battery."

Thanks!
[HTC Rezound] acejavelin:
Pretty sure it doesn't have FastBoot, that is an HTC Sense thing...
[HTC Rezound] needtoride:
Does that mean it's safe to do the S-off?
[HTC Rezound] acejavelin:
Yes... Just remember to backup and be ready to restore or flash a new ROM. It is common for rumrunner on the Rezound to corrupt the ROM and it may require a wipe or reflash/RUU, but S-Off is still achieved so all is well.

If it fails, it will just fail... I have not heard of rumrunner bricking a Rezound.
[HTC Rezound] TecMan45:
Hi Friends:

I have my HTC Rezound with the following:

PhoneROM: ConROMV6

Baseband version: 0.95.00.1017_2r, 0.95.1013r

Build Number: 3.14.605.12

UNLOCKED

VIGOR PVT SHIP S-ON RL

HBOOT-2.10.0000

I would like to have my HTC Rezound with S-OFF.

Can you help me please with rumrunner.us?

Thanks

TecMan
[HTC Rezound] acejavelin:
What help do you need? Just backup current ROM in recovery and run rumrunner, if it fails let us know and well see what we can do.
[HTC Rezound] Master VD:
It doesn't work

It doesn't work on Windows 8.1:crying:
[HTC Rezound] fuzzynco:
I just got a refurb from VZW. it came with the last OTA that was released.

I did HTCDEV unlock. installed TWRP2, rooted. tried to run firewater

and was told the exploit had been fixed in the version.

Is there an older RUU I can run to get a stock version that would work

for rumrunner?

I'm guessing the universal version is the right one since

the Rezound can be HTCDEV unlocked?
[HTC Rezound] acejavelin:
Firewater and rumrunner don't work on stock kernel, and it wasn't "fixed" in this version, those exploits launched almost a year after the last ROM update for the Rezound. You need to be on an unsecure kernel, the stock one won't work, best bet is to flash a custom ROM like OmniROM or something and try the exploit again, it is plainly laid out in the instructions for each exploit and if you didn't understand that you could have just asked.
[HTC Rezound] Rezinator:
Just a quick update to anyone finding this thread. I would like to second another person's post that mentioned running a 64 bit OS.

I tried several times last night to get Rumrunner working on one of my Rez's. After 4 attempts (All stopping with the WTF error), i realized my main OS is Windows 7 64. I booted into my 32 bit version of windows (that I setup purely for the JuopunutBear s-off trick a year+ ago)....and it ran perfectly the first time. So now both my Rez's are S-Off.

So if you're having issues / errors - double check your OS.....Hope this helps (someone....) :)
[HTC Rezound] fuzzynco:
Worked fine after I installed a custom rom.

Thanks.... Much easier then controlbear,

since they don't support windows.
[HTC Rezound] Chillerman:
Worked fine on my Windows 7 64 bit machine once I figured out what the program required.
[HTC Rezound] Lodingi:
Can you elaborate? Thanks.
[HTC Rezound] Chillerman:
I just meant that Rumrunner doesn't necessarily have a problem with Windows 7 64 bit machines. If you follow the instructions in the op and have everything set up correctly on your computer, it should work just fine with 64 bit. It did for me and many others.
[Moto G Q&A, Help & Troubleshooting] xcharliemx:
Anyone else? My call volume (both speakerphone and ear) are extremely low yet the sounds come through the speaker loud and clear for games, music, etc. I can't seem to find any mention of this anywhere other than a tiny thread on Reddit in the Moto G subreddit but no mention on how to fix it. Any ideas how to fix this?

Edit: Just restarted and it resolved itself. I had restarted after upgrade but it seems a 2nd one would've been required. Disregard.
[Moto G Q&A, Help & Troubleshooting] macoman:
Hello, i have the same problem but a restart doesn't resolve....the volume is very low. I tried a factory reset but nothing changed
[Moto G Q&A, Help & Troubleshooting] p5x:
having the same problem after updating to 4.4.2
[Moto G Q&A, Help & Troubleshooting] ekabon:
Motorola's advise: lower the incall volume to min, switch the phone off and then on again.

Worked for me, permanent fix.

Sent from my smooth Moto G
[Moto G Q&A, Help & Troubleshooting] zippov3:
Just turning volume down and the up during call will fix it, It's a known bug in KitKat on our devices
[Moto G Q&A, Help & Troubleshooting] vshl85:
I have the same problem but the said workaround doesn't seem to be working. Is this using the rocker all the way? The moto forums all give different solutions but none of them seem to be working.
[Moto G Q&A, Help & Troubleshooting] flashsam:
I agree with zippo, just turn the volume down a notch during the call and it increases the volume.

Strange but it works!
[Moto G Q&A, Help & Troubleshooting] JetVoz:
Hello! Do you know any way to increase volume of voice speaker? It's too low for me. Device runs with root, CWM and CM11.
[Moto G Q&A, Help & Troubleshooting] dmlmidi:
Fix the call volume in 4.4.2

The fix is the same for internal or external earpiece or speaker.

While in a call,

turn the volume to 0, then turn back up to your desired output level.
[Moto G Q&A, Help & Troubleshooting] Tony L1:
Fix moto g volume

I have been helped a lot by this forum so i thought i would give back! You can fix this problem with es file explorer And root access. First turn on root explorer in es file explorer, go to menu, local, device, find folder etc. Click on the file named mixer_paths.xml. click the top right menu button and select edit then scroll down and find the line <ctl name="RX1 Digital Volume" value="84" /> ( your number may not be 84) and change that number to 94. Do the same for the next two lines (lines should look the same except with RX2 and RX3). Save and exit, then reboot and it should be fixed. You can try different numbers but much over 94 and my speakers distorted. All volumes will be increased including in call volumes. This may work for other phones but no guarantees
[Motorola Triumph] javapop:
Hi all, I'm running CyanogenMod 7 ROM on my Triumph, and a few months back Instagram did an update and when I try to load a photo to Instagram, the phone reboots. Could this be a ROM issue? or a hardware issue. I want to stick with this phone as long as possible, as I use it with a grandfathered $25 Virgin Mobile plan.

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] afrobull:
I'm running SlimBean 4.3 (curse my luck, I'm stuck on 4.3 thanks Samsung) and after doing a lot of research, I've found that since 4.2, there's been an update to the file system on internal memory cards where you can have multiple users - my main issue with this is that it duplicates all files I transfer to the internal SD card (I've only added music at this point) and it's taking up unnecessary space - is there a way to remove these files without actually removing the original files in my regular storage?

I've been searching the forums and I've found some things that touch on it but I can't find a straightforward guide to removing the legacy folder/files etc. I just don't like how I transfer 3 GB of music and I actually take up 6GB of space.

Edit: More research has shown that the issue is because my Recovery might not be up to date, (which I'm pretty sure it is, I'm running CWM 6.0.4.3) and I've completely formatted my internal about 3 times and reinstalled everything but it's still showing up in my drive - so that method is a bust. Is there any other option?
[Nexus 7 (2013) Android Development] mar5hal:
One for cavaties
[Nexus 7 (2013) Android Development] mar5hal:
And just in case
[Nexus 7 (2013) Android Development] MRobbo80:
Thanks looks like a late Christmas present
[Nexus 7 (2013) Android Development] MidnightDevil:
It has some interesting features. Does the fact that is cm based, means that a caf kernel is necessary?

Thanks for bringing us this rom :) I'll be sure to experience it.

Sent using a walkie talkie.
[Nexus 7 (2013) Android Development] mar5hal:
Since cm made their changes this would require a kernel that supports 4.4 cm :good:
[Nexus 7 (2013) Android Development] Maurice5813:
great rom dude, I see your progress at N4 forums:good:
[Nexus 7 (2013) Android Development] matthew0776:
I need to check this forum more often...lol

Welcome to the N7flo community!!!!
[Nexus 7 (2013) Android Development] mar5hal:
Cheers! Glad to finally be here :victory:
[Nexus 7 (2013) Android Development] Maurice5813:
I'm glad too! Your work is simply AWESOME!
[Nexus 7 (2013) Android Development] madhartigan:
could anyone help me with what kernels are compatible with this?
[Nexus 7 (2013) Android Development] jaybizza:
Any Issues??

Thanks for bringing us this new Rom and welcome to the Flo community!! Gonna give this a try as I do with EVERY ROM that's put out!!Thanks again and was just wondering if any one is having any issues! I'm on Illusions 4.4.2 right now and really not to happy with the battery life! Cheers!! :highfive:
[Nexus 7 (2013) Android Development] mar5hal:
Just posted the build a couple hours ago. Not expecting any battery opinions just yet :P