yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] RPelham:
Just tried again, I did ./revone -s 0 -u ... it stated successful. I rebooted the device using the device's power button, help vol down to get into bootloader and still states S-ON
[One (M7) Original Android Development] mugetsu666:
Try wiping cache and then retry if no luck then I don't know. My first one took a couple of tries, but the next phone flawless.

Team-Noctural.com /androidtechy.com /droidnow.com
[One (M7) Original Android Development] :
Yeah that happened to me yesterday too.
[One (M7) Original Android Development] thekalby:
Getting the phone next week and just curious, can I s off as an alternative to bootloader unlocking from htcdev? Or should I bootloader unlock first and then s off.
[One (M7) Original Android Development] :
He can't do that because if his signature is correct then he has stock recovery. Unless there's a way to do it with adb shell.

---------- Post added at 11:54 AM ---------- Previous post was at 11:51 AM ----------

Again... there has been cases where people got S-OFF with fully stock handsets (meaning unlocked and S-OFF when they used the revone method).
[One (M7) Original Android Development] emanon:
You don't have to unlock with htcdev this should do it
[One (M7) Original Android Development] Anon9mouz:
golden and no more tampered and s-off thank u guys and i thanked OP
[One (M7) Original Android Development] RPelham:
My signature is correct, but you can erase cache using "fastboot erase cache". I'm trying it now and I'll report back. =)
[One (M7) Original Android Development] cschmitt:
For those who have changed CID following s-off, what do the system properties ro.boot.cid and ro.boot.carrier show? I switched from CWS__001 to HTC__001 and these properties still showed ro.boot.cid=CWS__001 and ro.boot.carrier-ATT until I hex edited mmcblk0p19 and changed the first 8 bytes HTC__001 and pushed it back, then it showed ro.boot.cid=HTC__001 and ro.boot.carrier=HTC-WWE

Also, there are a couple of occurrences of the CID in mmcblk0p6, along with a few ATT MMC-MNC pairs. This kind of likes like the sim lock stuff to me. Anyone with a dev edition care to dump their mmcblk0p6 and share so that we can confirm?

Edit : I'm NOT suggesting that anyone hex edit mmcblk0p19
[One (M7) Original Android Development] zinder33:
Please help guys stuck at this cant execute chmod 755 revone command ..TE shows read only file ..i have changed permisssion in root explorer thou

sent from HTC One aka M7
[One (M7) Original Android Development] mugetsu666:
Or even go into recovery and press power & volume up to get into stock recovery menu & wipe cache from there.

Team-Noctural.com /androidtechy.com /droidnow.com
[One (M7) Original Android Development] hawknest:
Done and s-off thanks guys

Was wondering what happened to the crew now I know
[One (M7) Original Android Development] ntt2006:
You can follow this way to S-OFF. Sure 100% OK.

* S -OFF

- download revone.bin, change name to revone by delete .bin

- install root explore

- install terminal emulator (google play)

- use root exploer, copy revone file to path /data/local/tmp

- open terminal

- type su => enter

- type cd /data/local/tmp => enter

- type chmod 755 revone => enter

- type ./revone -P => enter, if show revone successful => reboot phone.

- open terminal

- type su => enter

- type cd /data/local/tmp => enter

- type chmod 755 revone => enter

- type ./revone -s 0 -u => enter. if show revone successful => reboot phone to bootloader ==> S-OFF

* Remove TAMPERED

- open terminal

- type su => enter

- type cd /data/local/tmp => enter

- type chmod 755 revone => enter

- type ./revone -t rồi enter, if show revone successful => reboot phone to bootloader ==> TAMPERED REMOVED
[One (M7) Original Android Development] jumpup:
Another happy and successful S-OFF user here. I began the process with a TMOUS HTC One, rooted and running Android Revolution 10.1.

I followed the on-device command process posted by [MENTION=2648822]floppy22[/MENTION] at Post 1111 of this thread. I performed the steps to gain S-OFF and to remove the messages regarding tampering. I *did not* make any changes to the CID, so I cannot speak to that option. Everything else worked exactly as [MENTION=2648822]floppy22[/MENTION] laid it out. Thank you very much!
[One (M7) Original Android Development] zinder33:
Tnx mate it is aheading to s- off but i am getting error -6:confused:

sent from HTC One aka M7
[One (M7) Original Android Development] mugetsu666:
U need to put the space in cd /data/local/tmp. The space is between cd & / normally if u forget the space u get error 6

Team-Noctural.com /androidtechy.com /droidnow.com
[One (M7) Original Android Development] cheetah2k:
I have a Telstra Black 32gb HTC1. Get thru the whole process no errors but still S-ON... Confused. :(

My HTC1 is ***LOCKED*** and not rooted..
[One (M7) Original Android Development] stephen2282:
Just one quick question, since it involves changing the HBOOT. Will the data get wiped?? Thanks
[One (M7) Original Android Development] :
Don't worry mate. I spent a few hours on it yesterday. I ended up using terminal emulator and root explorer
[One (M7) Original Android Development] pablo11:
Doesn't change HBOOT
[One (M7) Original Android Development] mugetsu666:
Data doesn't get wiped and HBOOT doesn't change either

Team-Noctural.com /androidtechy.com /droidnow.com
[One (M7) Original Android Development] pablo11:
You would need root to execute the revone code

^^^ yeah it doesn't wipe anything - too quick to submit my earlier post - thanks mugetsu666
[One (M7) Original Android Development] For_itembine:
EDIT: thank you, it worked. wasnt working with romtoolbox pro even though it said it was successful, so i downloaded the terminal emulator from the playstore, or perhaps i just had to try it several times, cheers :D
[One (M7) Original Android Development] stephen2282:
Oh, uh so the data is safe?
[One (M7) Original Android Development] zinder33:
Yeaaaaaahhh thanks alot mate for your guide finally $-off :D

And i removed tampered but still on boot under htc quitely brilliant it shows in red the long message for development process is that normal ??

sent from HTC One aka M7
[One (M7) Original Android Development] cheetah2k:
I thought this method didn't require root or an unlocked bootloader????
[One (M7) Original Android Development] pablo11:
Yes. Didn't effect mine at all. If you are worried back it up..........................
[One (M7) Original Android Development] zinder33:
Tnx tonne mate s off:D:D:D

sent from HTC One aka M7
[One (M7) Original Android Development] cheetah2k:
Same... something is missing from the tutorial...
[One (M7) Original Android Development] pablo11:
Looks like you need to issue an su command - I know I did..............

* S -OFF

- download revone.bin, change name to revone by delete .bin

- install root explore

- install terminal emulator (google play)

- use root exploer, copy revone file to path /data/local/tmp

- open terminal

- type su => enter

- type cd /data/local/tmp => enter

- type chmod 755 revone => enter

- type ./revone -P => enter, if show revone successful => reboot phone.

- open terminal

- type su => enter

- type cd /data/local/tmp => enter

- type chmod 755 revone => enter

- type ./revone -s 0 -u => enter. if show revone successful => reboot phone to bootloader ==> S-OFF

Might be able to use adb in root mode though without rooting the device..........
[One (M7) Original Android Development] mugetsu666:
Yeah that's normal. It's now time to start working on new splash screens to get rid of that crap, but it's all normal.

Team-Noctural.com /androidtechy.com /droidnow.com
[One (M7) Original Android Development] stephen2282:
okay thanks ;)
[One (M7) Original Android Development] :
Okay so I have been trying to get rid of the red writing in the "Tell HTC" section. So far I have no success. I have used the 1.28.401.7 RUU and my bootloader is locked (not RELOCKED) with SuperCID. The red writing is still there. So I thought it could be because I have SuperCID so I changed my CID to HTC__001 and ran the 1.28.401.7 RUU I then get an error 130 MODEL ID ERROR.

Not really worried about it but it is making me think how can someone get rid of that red witing?
[One (M7) Original Android Development] cheetah2k:
On the first page under instructions it says this:

Where is SU mentioned?????
[One (M7) Original Android Development] zinder33:
type su -

sent from HTC One aka M7
[One (M7) Original Android Development] :
Option 3
[One (M7) Original Android Development] pablo11:
Yeah, I just edited my post - you can probably issue commands through adb - I thought you were using the terminal method I quoted.

Sorry for any confusion.

I used the adb method but I was rooted anyway.
[One (M7) Original Android Development] MOEHEET:
i habe been tryin like hell..still no sucess..
[One (M7) Original Android Development] Dragonis2345:
thanks

Thanks alot worked great first try no problems
[One (M7) Original Android Development] cheetah2k:
Don't worry mate, same boat for a lot of us..
[One (M7) Original Android Development] guitarpager:
I had trouble too at first. My issue was that when I pushed the revone.bin file to my phone it didn't keep the extension and the file only read revone .

I downloaded the file using the xda app and then using ES File explorer I moved the file to the data/local/tmp folder.

After doing that I was able to use all the commands and it worked perfectly.
[One (M7) Original Android Development] For_itembine:
Example

Remove TAMPERED

+open terminal emulator+

su (enter)

cd /data/local/tmp (enter) *cdspace/data/local/tmp*

chmod 755 revone (enter)

./revone -t (enter)

*note

Stupid android copy/paste still broken on forums, won't post URL/image below lol
[One (M7) Original Android Development] :
That's exactly what I had to go through. I was ready to through the freakin' phone against a brick wall. I was so frustrated.
[One (M7) Original Android Development] MOEHEET:
i m gna give a last try.................n thats it......
[One (M7) Original Android Development] cheetah2k:
I thought the .bin extension had to be removed before pushing to the HTC1??????????????????????????:confused:
[One (M7) Original Android Development] cheetah2k:
Shadowboy did you eventually work it out???? Or same like us, everything saying Success, but no dice?
[One (M7) Original Android Development] guitarpager:
Well I can't tell you for sure about that. I just know what worked for me.
[One (M7) Original Android Development] :
Have you tried using terminal emulator and root explorer? Also I had put the revone file in /system/bin also try renaming it as revone.bin whenyou place it in the /system/bin folder.
[One (M7) Original Android Development] emanon:
You don't have to, I used it as it is just type the whole file name redone.bin
[One (M7) Original Android Development] :
Yeah I manage to get S-OFF at around 4:45PM and I started at around 11AM. But I did place the revone in the /system/bin folder and used TE and RE which I think helped me. I think I even renamed the revone file to revone.bin. I tried so many many many times using the PC, TE and RE worked for me.
[One (M7) Original Android Development] MOEHEET:
i tredi putin to data/local/tmp
[One (M7) Original Android Development] emanon:
Sorry meant to say revone.bin
[One (M7) Original Android Development] :
Try a different folder and place it in the /system/bin and try TE and RE and rename revone to revone.bin when you put in their. Even that I had to try 4 or 5 times before I got S-OFF.
[One (M7) Original Android Development] dseries60:
I am using terminal emulator and everything says successful, but it still shows S ON. Do you just keeping doing it over and over until it works?

---------- Post added at 10:40 PM ---------- Previous post was at 10:39 PM ----------
[One (M7) Original Android Development] milander:
Followed the instructions and managed to get my S-OFF....thanks!
[One (M7) Original Android Development] branjgsclb:
Thank you so much for this, have 2 HTC One's and they both got S-Off on the second try. Awesome!!!
[One (M7) Original Android Development] NOFSBIGE:
Thank You still trying to figure this out... this is what I get when beginning

Erics-iMac:platform-tools Eric$ ./adb devices

adb server is out of date. killing...

* daemon started successfully *

List of devices attached

Erics-iMac:platform-tools Eric$ adb push revone /data/local/tmp

-bash: adb: command not found

Erics-iMac:platform-tools Eric$
[One (M7) Original Android Development] tommykwan222:
still got fail.

Is it any different between in 1.28 and 1.29?
[One (M7) Original Android Development] deol 4ever:
FINALLY, after an hour and half of continuous trying :crying: i literally jumped when i saw it was s off lol
[One (M7) Original Android Development] mugetsu666:
Congrats man

Team-Noctural.com /androidtechy.com /droidnow.com
[One (M7) Original Android Development] Becool0130:
What so you guys think of my chances doing adb on my phone?

Downloading it from the market instead of on pc?
[One (M7) Original Android Development] DrAgKurt:
using terminal emulator is the easiest way.
[One (M7) Original Android Development] RPelham:
Okay, so I tried erasing cache, and am having the same problem. When I tried doing a different method of S-OFF, also posted here on XDA, which requires me to unlock my bootloader first, my bootloader now will not unlock, I ran through the steps on HTCDev.com exactly, and no matter which computer I have tried, each time I get past the "Yes unlock bootloader (May void warranty)" screen, the device is rebooted and wiped, but the status still shows **** LOCKED ****. Another user posted in QA is in the same boat and tried revone first, so I believe it has somehow corrupted something in my phone prohibiting me from unlocking anything or messing with my bootloader....

Any help would be very much appreciated.
[One (M7) Original Android Development] :
Not good.
[One (M7) Original Android Development] jdgreat4:
S-Off'ed my device like a boss.!
[One (M7) Original Android Development] Becool0130:
Not even using terminal emulator?
[One (M7) Original Android Development] gemini002:
Lol not helpful but hilarious...use Terminal if possible very easy...just do some reading I'm sure u will be able to do it...grab the htc one all in one zip follow the instructions try the commands from there....read up man
[One (M7) Original Android Development] LuigiBull23:
Maybe your SDK tools are out of date?
[One (M7) Original Android Development] Simba501:
Terminal emulator works perfectly fine. I did it - as well as many other people in this thread.
[One (M7) Original Android Development] :
This is weird... This morning I ran the 1.28.401.7 RUU and also tried the 1.20.401.1 RUU and my CID in adb shell getprop "ro.cid" was this:

which is my original CID.

Now I checked again after flashing different ROMs/RUUs I get this:

Don't know how that changed. I have a few guesses but have no definitive conclusion.
[One (M7) Original Android Development] Becool0130:
Thanks so much for the confirmation! Working on it now then ^^
[One (M7) Original Android Development] lokicat:
This happened to me a while back on my Mac. I uninstalled HTC Sync and that resolved the first issue you are having. On the second issue, you left out the "./" prefix on adb command. Got it right on your first command.
[One (M7) Original Android Development] NOFSBIGE:
You are a god amongst men sire... may I suggest posting this as a mac tutorial... I was able to get s-off no tamper and supercid... WOW thank you so much!
[One (M7) Original Android Development] maurydes:
i confirm working awesome with terminal emulator Great great Work mate:):): Cool:
[One (M7) Original Android Development] gianton:
Is flashing the RUU done in fastboot mode and just run the .exe file?
[One (M7) Original Android Development] :
Just run the .exe That's what I did.

EDIT:

This morning I changed my CID to HTC__001 and HTC__Y13 (trying to get rid of the Tell HTC red writing:

and I ran the RUU 1.28.401.7 and RUU 1.20.401.1 and I got ERROR 130 Model ID error. So my comments before about having the right CID might be wrong. However having SuperCID had no issues using those RUUs

But maybe when I tried it before my original CID (HTC__039) was affecting it. But now since my CID has changed in adb shell I wonder if I would get the same error?
[One (M7) Original Android Development] RPelham:
Wanted to post a reply... I started this process at 9pm Eastern Standard Time. It is now 1:19 AM. After, quite literally, 4 hours of trying, I finally got it to work. S-OFF and unlocked bootloader! =D

Steps I took:

1.) adb push revone /data/local/tmp

2.) adb shell

3.) cd /data/local/tmp

4.) chmod 755 revone

5.) ./revone -P

At this point I kept getting all sorts of failures. It kept spamming about "Unable to map memory." I stayed within the SAME adb console, pressed the UP arrow to repeat the last command, and just kept repeating this process. Sometimes it would crash and just reboot the phone, sometimes it would give an error message saying I needed to reboot the phone.

This went on for literally 2 hours straight. I had to have repeated step 5, at least,without exaggerating, 40-50 timesm maybe even more. Finally, it said Success, Reboot phone to continue. I then followed the following:

6.) Rebooted phone.

7.) Closed my command prompt and opened a new prompt once phone was rebooted.

8.) adb shell

9.) cd /data/local/tmp

10.) ./revone -s 0 -u

It reported a success instantly. I pressed the power button on my phone and pressed restart. I held volume down and low and behold I was finally granted the S-OFF and Unlocked status!!!!! I'm ecstatic!

Thank you Revone!!!
[One (M7) Original Android Development] Squirrel1620:
Please tell me your gonna have a rom for the one!

Sent from my Tricked out HTC One
[One (M7) Original Android Development] rodreb:
After an hour .. nothing!

i flashed arhd 9.1

and after 1 minute got the s-off

Mine is an O2___102
[One (M7) Original Android Development] gianton:
So it does get changed after flashing an RUU, maybe you have to be on a specific CID and not super CID.
[One (M7) Original Android Development] dseries60:
It finally worked! I now have S OFF and CID-11111111

Thanks to everyone who contributed to this project and to everyone who posted their steps and results.

I tried this about 20+ times before it worked. The only thing I did slightly different (not sure if this helped or not).

After running ./revone -P from terminal emulator , I opened another emulator window and ran the ./revone -s 0 -u command and then rebooted. I then had S OFF. Then I ran the ./revone -t to remove the tampered with statement. Then from fastboot ran fastboot oem writecid 11111111

Bring on the Google Edition!
[One (M7) Original Android Development] Becool0130:
Omg, I'm a Linux noob.

When i downloaded revone it went into the download directory. Now, idk how to "PUSH" or copy this to data/local/temp. Any quick Linux code tips? Thanks
[One (M7) Original Android Development] RPelham:
Wanted to post a reply... After 4 hours of trying (started at 9:00pm ended at 1:10am), I finally got it to work. S-OFF and unlocked bootloader! =D

Steps I took:

1.) adb push revone /data/local/tmp

2.) adb shell

3.) cd /data/local/tmp

4.) chmod 755 revone

5.) ./revone -P

At this point I kept getting all sorts of failures. It kept spamming about "Unable to map memory." I stayed within the SAME adb console, pressed the UP arrow to repeat the last command, and just kept repeating this process. Sometimes it would crash and just reboot the phone, sometimes it would give an error message saying I needed to reboot the phone.

I had to have repeated step 5, at least,without exaggerating, 40-50 times maybe even more. Finally, it said Success, Reboot phone to continue. I then followed the following:

6.) Rebooted phone.

7.) Closed my command prompt and opened a new prompt once phone was rebooted.

8.) adb shell

9.) cd /data/local/tmp

10.) ./revone -s 0 -u

It reported a success instantly. I pressed the power button on my phone and pressed restart. I held volume down and low and behold I was finally granted the S-OFF and Unlocked status!!!!! I'm ecstatic!

Thanks Revone!
[One (M7) Original Android Development] :
Honestly I don't know what happened. This morning I changed my CID to a specific one for the 1.28.401.7 RUU and I got an error 130. So I just thought stuff it I will just go back to having SuperCID and go back to mike1986. stock 2.17.401.1 odexed ROM. After doing so I flashed the stock recovery and used revone to lock the bootloader and changed my CID back to HTC__001 and the last time I checked in adb shell my CID is now HTC__001. Beats me how it got changed. I'm not complaining though, just wondering what the hell happened.
[One (M7) Original Android Development] gianton:
Thanks for the testing mate. At least we know that it can be changed with a flash of an RUU or ROM. I'm holding off from flashing an RUU till the 4.2.2 OTA is available.
[One (M7) Original Android Development] hawknest:
Already do

Sent From My EclipticONE
[One (M7) Original Android Development] oneslow5oh:
ive tried for literally hours and i cannot achieve s-off. everything says successful and i reboot into bootloader and it still says s-on. im getting really frustrated. can anyone help? will the moonshine s-off method work on windows vista 32 bit? please let me know. thank you
[One (M7) Original Android Development] :
Moonshine requires Linux so either from a CD or USB stick. Plus you have to have the right ROM for it too work. I was gonna use moonshine but my ROM version was not in his list so I went for revone instead.
[One (M7) Original Android Development] baste07:
but yet the end target is the same right?
[One (M7) Original Android Development] RPelham:
That is something that should be asked in the moonshine thread. I can tell you now, that the developer of moonshine posted clearly and concisely what operating system you need.

It took me several hours (see lost above) and it finally worked. At one point it looked like it worked, but didn't actually give me s-off, similar to your problem. I repeated every step as posted in the OP and finally got it to work after a couple more hours (this was after a couple hours already invested.)
[One (M7) Original Android Development] :
Yes it is but Moonshine has a different hboot. I think his is modified (I'm not sure). Don't have aclue what benefits moonshine has over revone. Probably and I mean probably moonshine will work 100% if you have the right firmware version.

But I wouldn't know what are the differences. between the 2 methods.
[One (M7) Original Android Development] oneslow5oh:
is there any specific rom or firmware im supposed to be on for revone? im on the revolt jb m7ul nightly 20130605.. not too sure how to check firmware
[One (M7) Original Android Development] sand1303:
Something isn't right for me. I pushed the file but when I try to open the directory in shell it keeps telling me not found
[One (M7) Original Android Development] baste07:
but that would mean revone would be better? since it doesn't look for a specific model only?
[One (M7) Original Android Development] :
Not as far as I can recall. Reading the OP it did not say you have to a specific ROM/firmware.
[One (M7) Original Android Development] katmad:
One experienced guy from Russian forum was trying for 2 days. And after ./revone -P it said successful and to do reboot. He didn't reboot, run ./revone -P again. The phone rebooted itself. Then "chmod 755 revone" and finally "./revone -s 0 -u" . Well done.
[One (M7) Original Android Development] rvajuggalo:
Indeed terminal is easier
[One (M7) Original Android Development] :
Yeah it would be in that sense because:

A: you can use any OS you want just have to use adb

B: no specific ROM/firmware is needed.

But many people including me had to try many many many times to get S-OFF. But maybe with moonshine it's a sure thing when you have the right combinations (ROM version and Linux).
[One (M7) Original Android Development] baste07:
yeah, i personally had just 1 go and i got s-off and supercid. although i do see alot having errors.