[q] tried every s-off method...

[Crossvxm]

I have LOTS of Android experience, little for HTC specifically. My last One S came S-Off some how and at the time it wasnt much importance to me. Now its different. My new One S (S4 variant) is S-On, bootloader info is at the end of the post. I am trying to get it S-Off via Moonshine but it gives me wonderful dots. Firewater once chugged a bottle but when I flashed an RUU to match the device firmware to be the one required by Moonshine (13.4.531.11, mine has the extra 710RD at the end) now Firewater gives me the dreaded dots as well. I was running Windows XP doing all of this. Reading other peoples experience in other forums I decided to try a linux OS, not in a USB flash drive, I actually partitioned my HDD in order to give it its own side. My current laptop is too old for Mint Linux (I read many suggestions on using that), Ubuntu gives me an ADB error with moonshine, so I installed Lubuntu 13.04 which sadly gives me the same dreaded dots as in Windows. We're talking literally sitting here for half an hour waiting for a miracle. Basically:

Rumrunner, FATAL: Download packages...

Facepalm, requires SuperCID which is no good on HBoot 2.15

Firewater, once AT LEAST got a bottle done, now useless since I RUU'd to match the required Moonshine firmware.

Revone, gets device ready successfully, fails afterwards w/ (-1)

Moonshine, seemed like my last hope, confirmed in many threads to work without issues on linux based OS, FAILS, waiting with the never ending dots...

The one that actually seemed like it was going to work was Rumrunner, but sadly its that FATAL thing that kills it. Tried firewall off, tried it on Lubuntu 13.04 with the same issue. Tried two different wifi connections with no success. My wifi has 11.0Mbps on my PC (seems like a PC limit as it goes faster on my phones.)

WHAT CAN I DO TO S-OFF? I am rooted/BL unlocked, USB debug enabled, I used Ubuntu which requires no drivers/HTC Sync, theres no antivirus or other underlying causes, heck, even installed BusyBox for what its worth, factory reset the phone, etc. On the Windows side. I uninstalled my antivirus, turned firewall off, turned auto updates off, turned off startup programs, no HTC Sync, NOTHING. What I DO have is Samsung drivers installed along with Windows MTK porting kit, which I doubt is a problem... I've done it all...

PS: sorry if this was long to read, I had to get AS MUCH info as possible to ensure that this thread doesnt generate too much back and fourth trial and error. Disabled my signature for this post in order to avoid a super long list of words...

****DEVICE INFO****

version: 0.5
version-bootloader: 2.15.0000
version-baseband: 1.13.50.05.31
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: HT24YW409830
imei: XXXXXXXXXXXXXXX
product: vle
platform: HBOOT-8960
modelid: PJ4011000
cidnum: T-MOB010
battery-status: good
battery-voltage: 4033mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-64bedd38
hbootpreupdate: 11
gencheckpt: 0

****SOFTWARE****

Android 4.1.1
Software Number 3.14.531.11 710RD
(Btw, TMOB10 CID)

 

[Folrot]

[...]SuperCID which is no good on HBoot 2.15

Why is that? I have HBoot 2.15 and SuperCID on my OneS (using these instructions: http://forum.xda-developers.com/showthread.php?p=26516911#post26516911 ) and facepalm s-off worked on my first try.

I don't really know what's going wrong for you, I can only tell you what worked for me. Maybe it's helpful:
On Windows 7, install HTC Drivers (get them here: http://forum.xda-developers.com/showthread.php?t=2217396 ), then follow supercid guide above, then do facepalm s-off.

 

[Crossvxm]

Why is that? I have HBoot 2.15 and SuperCID on my OneS (using these instructions: http://forum.xda-developers.com/showthread.php?p=26516911#post26516911 ) and facepalm s-off worked on my first try.

I don't really know what's going wrong for you, I can only tell you what worked for me. Maybe it's helpful:
On Windows 7, install HTC Drivers (get them here: http://forum.xda-developers.com/showthread.php?t=2217396 ), then follow supercid guide above, then do facepalm s-off.

Lol that's where I first started out when I planned on getting S-Off to then later find out that lots of people have the same issue as me; you do it and when you readcid, it doesn't stick. I even tried the "echo -n" command which gives you the 22222222 supercid suggested by beaups for another user of the 3.16 firmware and it was of no use. I risked bricking my device and tried it on mmcblk4 and 5. No good. It just seems like I have horrible luck with this one specifically...good suggestion though.

 

[808phone]

I was frustrated as well. This worked for me:

http://forum.xda-developers.com/showthread.php?t=2640420

Post #30 may help - but read the entire thread up to that point.

 

[Crossvxm]

I was frustrated as well. This worked for me:

http://forum.xda-developers.com/showthread.php?t=2640420

Post #30 may help - but read the entire thread up to that point.

I tried the indtructions on post 30. And I just get the hanging dots. BUT reading the entire thread from post 1-30, another user posted a link to his success that caught my attention. He mentioned NOT to root and NOT to install BusyBox after RUUing to that firmware version moonshine requires, just unlock the bootloader. As soon as I RUU'd to that verision a few days ago, first thing I did was rooted and installed BusyBox. Why BusyBox? Because at the time I was following the carrier unlock instructions and it would not work without BusyBox. So that might be the culprit of why the firewater method completely changed from actually chugging a bottle to just hanging dots, when I tried firewater the first time, I didnt have BusyBox, just root. Now I have to download that RUU all over again and hope for a miracle. I dont have a clue how to manually unroot and eliminate BusyBox any other way.

 

[808phone]

I had the hanging dots and it was the drivers/windows. As soon as I ran the Ubuntu live from USB stick - it worked and it did it quickly.

 

[Crossvxm]

I had the hanging dots and it was the drivers/windows. As soon as I ran the Ubuntu live from USB stick - it worked and it did it quickly.

Yeah thats what I read everywhere which is why I dedicated space to actually install a linux os. Ununtu gave me some sort of adb error with moonshine which I could not rememdy. Lubuntu, a lighter variant built off of Ubuntu, has been more easier to handle. I had initially installed their 14.04 version 32bit and it came up giving me errors that I needed more 32bit libraries. Confusing as I DID indeed download the standard i386 version. So I used 13.04 and it works without issues but gets to the hanging dots just like on Windows. Right now I am redownloading the RUU I used before since I don't know how to remove BB and SU. And my laptop is so slow that it takes a good 10 minutes for the RUU install sheild to show the actual RUU menu, then a good hour to restore the phone. Then I have to unlock the BL and now ill try without root/busybox. I think its BusyBox which is the perpetrator in this matter, how many people actually remember to install it by normal means? How many people actually remember that there is a TWRP flashable one out there? So I think I was an unlucky person to actually install it and probably there is where my nightmare began.

Its easy to remove BusyBox and its symlimks along with root access on any other device, however, HTC devices are different when its S-On. HTC's Security feature has really just caused bricks left and right in reality. If you havent noticed, they're trying to run down Apple's path in many angles. Notice how its one of the only devices with a magnifying glass feature when dragging the arrow on typed text where most other devices use a regular arrow to drag around. Zero gap aluminum body builds, low spec camera, huge bezel, etc.

 

[808phone]

They may be trying to copy Apple but it goes beyond just build and copying icons.
In any case it must be some sort of driver issue. Is there another machine you can try on?

 

[Crossvxm]

They may be trying to copy Apple but it goes beyond just build and copying icons.
In any case it must be some sort of driver issue. Is there another machine you can try on?

Yeah they really made themselves unique with the whole security thing for android. For a company that started in the late 90s, they came up quick in the smartphone world. My drivers seem to be fine with ADB. All commands issue properly. Linux does the same thats why I swear its as I read on that other thread that it is BusyBox.

And sadly no, I was supposed to get an Asus laptop today with an intel i5, etc, but it got too late me trying to do this RUU thing. Its already been an hour and its just now getting past the bootloader restore part.

EDIT: I'm an idiot I forgot the bootloader must be relocked now Im sitting an extra hour for the restore to complete...

:silly:

 

[808phone]

BTW: all my fastboot and adb commands worked as well. I still got the dreaded dots.....
It never worked until I used the ubuntu live usb. I tried on 3 different computers as well. Very frustrating!

 

[Crossvxm]

BTW: all my fastboot and adb commands worked as well. I still got the dreaded dots.....
It never worked until I used the ubuntu live usb. I tried on 3 different computers as well. Very frustrating!

That sucks. That means I could be sitting here for hours waiting on the RUU to finish and it could be all for nothing. But im hoping that other thread post had a point in not rooting/BusyBox.