[Verizon HTC One (M7)] xenacick:
So I am completely out of ideas. I hope someone else’s input can solve whatever is going on here.

I am trying to gain permanent root, meaning getting s-off and unlocking the bootloader. I have a HTC One M7 from Verizon, so already have an uphill battle. I had a previous rooted phone, but the sound card died and I had to exchange and get a replacement. Hence, I am not rooted anymore.

Here are my current phone spec’s:

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.56.0000

(bootloader) version-baseband: 1.13.41.0109_2

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 3.11.605.1

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno: XXXX

(bootloader) imei: XXXX

(bootloader) meid: XXXX

(bootloader) product: m7_wlv

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0731000

(bootloader) cidnum: VZW__001

(bootloader) battery-status: good

(bootloader) battery-voltage: 4247mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-4dab9d12

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

Now I have tried pretty much every which way I have found to try and gain S-off without using HTCDev. The most promising method it seems from other’s posts on the subject has been the weaksauce and firewater method. However, when I try this method, I get nowhere. I gain temp root with weaksauce no problem. It automatically re-temp-roots after a system reboot, that part works great. It’s the firewater aspect which is the issue.

Since I haven’t taken the most recent update to Sense 6.0 my thought was firewater would still work on my device. Is this wrong?

If it isn’t, then

after issuing these commands in my command prompt

(with a completely fresh version of ADB/Fastboot and HTC Drivers without HTC Sync):

adb reboot

adb wait-for-device push firewater /data/local/tmp

adb shell

chmod 755 /data/local/tmp/firewater

su

/data/local/tmp/firewater

I get this as the response:

Do you understand the implications of these warnings?

(Yes/No)

Yes

Yes

!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho

!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho

!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho

ld power for 60 seconds !!

=========================================================================

preparing, one moment

The first bottle is open

chugging..........

C:\Program Files (x86)\Minimal ADB and Fastboot>

This occurs every time

, and the only thing which differs is my phone will either reboot itself after it stops running firewater, or will hang and need to be manually rebooted.

On other people’s posts with issues gaining S-off with this method they usually are about opening numerous bottles and such, and having to run firewater a number of times before getting the exploit to work. At this point I have probably run the firewater scenario about 50 times. I am at my wits end.

I HATE blinkfeed, even seeing anything about it pisses me off…this is reason #1 why I want to root, to get rid of it, but also I am very particular about how efficient my phone runs, because some days I need it to be fully functional for more than 16 hours, and at stock that’s a pipe dream.

So ideas anyone???

Please……