yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] saenz4931:
help please..

i cant get s-off .. this is all i get from many atempts ... am i doing something wrong?

C:\mini-sdk>adb devices

adb server is out of date. killing...

* daemon started successfully *

List of devices attached

FA34PS906796 recovery

C:\mini-sdk>adb push revone /data/local/tmp/

2521 KB/s (648208 bytes in 0.251s)

C:\mini-sdk>adb shell

~ # ←[6ncd /data/local/tmp

cd /data/local/tmp

/data/local/tmp # ←[6nchmod 755 revone

chmod 755 revone

/data/local/tmp # ←[6n/revone -P

/revone -P

/sbin/sh: /revone: not found

/data/local/tmp # ←[6n

thanks ind advance
[One (M7) Original Android Development] g3rm3n:
Please can you confirm that all it is ok in this order ?

First Locked bootloader ./revone -l

Second S-ON fastboot oem writesecureflag 3

And finally ...i must install ruu with your cid
[One (M7) Original Android Development] Theshawty:
I first locked the bootloader, then I installed the RUU and lastly S-OFF
[One (M7) Original Android Development] g3rm3n:
Is it necessary revone file in to the phone to get S-ON ? I think no but I am not sure
[One (M7) Original Android Development] Theshawty:
Nope, S-ON requires a bootloader command not related to revone.
[One (M7) Original Android Development] WarpigtheKiller:
After this step "chmod 755 revone" the cmd do nothing. I can waiting for minutes, but it does happens anything. What can i do?
[One (M7) Original Android Development] :
Okay I have done this and my CID is now 11111111 (in "adb shell getprop ro.cid") but still the OTA update won't install (still S-OFF). I will go back to S-ON and see what happens
[One (M7) Original Android Development] ntt2006:
I was S-OFF my phone at 1st release, so now have update to new version revone-0.2.1 . Please tell me, now I need to S-ON and S-OFF agian with new version?
[One (M7) Original Android Development] :
No need to. What do you want to do?
[One (M7) Original Android Development] ntt2006:
I want to confirm I need to S-OFF again or not because at #1 post has required to update to new version.
[One (M7) Original Android Development] :
UPDATE:

I have S-ON and the update still won't install I still get this:

---------- Post added at 08:51 AM ---------- Previous post was at 08:49 AM ----------

If you already S-OFF you don't need to update. But if you were going back to S-ON and want to S-OFF again then yes use the latest revone-0.2.1
[One (M7) Original Android Development] g3rm3n:
I have wrote my CID original +RUU of my área = I can install ota
[One (M7) Original Android Development] Barsky:
hehe. I did mean S-On. Thanks

---------- Post added at 06:07 PM ---------- Previous post was at 06:00 PM ----------

Guess that means setting yourself back to S-On is now safe. Thanks
[One (M7) Original Android Development] :
Okay guys just a little bit of a WARNING for anyone!!!

Okay this what I've been doing and it's not good! I have followed this tutorial http://xdaforums.com/showpost.php?p=42351491&postcount=35 and it works pretty well.

But I have found out that after doing this mod and going back to S-ON (fastboot oem writesecureflag 3) that you will get a bootloop. If your phone is plugged to your PC you will need to unplug it and let bootloop a couple of times and it will eventually boot up normal. BUT you will also get a "TAMPERED" flag back on your bootloader.

Using revone to get rid of the "TAMPERED" flag does work but that means you need to S-OFF again. And when you think "Oh goodie I have got rid of the "TAMPERED" flag, I can go back to S-ON" think again! As soon as you S-ON you will then go back back from having the bootloop.

So far I can have unlocked bootloader and S-OFF. I have tried this a few times and I can repeat the errors/bootloops so it's not a one off thing. As soon as I get S-ON I have the tampered flag again.

Trying to run RUU again but so far no luck here.
[One (M7) Original Android Development] DigitaL BlisS:
Hopefully a dev sees this:

If you put S-ON back with the CID 11111111, it completely borks things.

S-ON is now back on and the bootloader now locked, but now "./revone -P" gives me the "Failed to map memory" error when trying to turn it off again. "./revone -s 0 -u" still says "revone successful", but booting back into the bootloader S-ON is still on and the bootloader is still locked.

Update/fix (if you're on Telus):

Assuming you've went back to stock recovery to try and get the OTA and are now stuck with S-ON, you can remove it again by

1) Getting a new unlock code from HTC Dev

2) Then unlock your bootloader

3) Change recovery to TWRP/CWM

4) Then restore a backup of the stock rom (or get the one uploaded here)

You should then be able to use revone for S-OFF again. If you're not on Telus, you can try the same steps or flash your RUU (I'm guessing)
[One (M7) Original Android Development] :
I still have SuperCID but changing the mmcblk0p19 file will give anyone a headache if they want S-ON back. I suggest to leave it alone.
[One (M7) Original Android Development] mrrogers1:
Please excuse my ignorance but why on earth are you guys trying to s-on your phones right after Revolutionary gave us s-off? :what:
[One (M7) Original Android Development] :
Just trying to install OTA updates and out of curiosity.

Okay to explain myself more I wanted to use the RUU 1.28.401.7 and get the official OTA updates so when 4.2.2 comes out I will get the updates. So I decided I will have a stock 1.28.401.7 and get the OTA updates and just wait for 4.2.2 to come out (officially). But now this is where I'm trying different things and discovering that some files are not meant to be modified because it breaks the signature and now I can't even use the RUU I used before.
[One (M7) Original Android Development] Barsky:
Good info, guys. Sorry for your troubles, but thanks for sharing so others don't end up here.

---------- Post added at 07:33 PM ---------- Previous post was at 07:30 PM ----------

my thinking was having supercid but being less susceptible to a hard brick. Apparently that logic is flawed given the problems going back to S-On is causing some people
[One (M7) Original Android Development] andyt315:
Quick question, I already have S-OFF and SuperCID from yesterday. Do I need to upgrade to newest revone version? Doesn't matter, right?
[One (M7) Original Android Development] :
Okay just another update. I will push my original mmcblk0p19 back to my phone and see whether that will fix my S-ON. Will give more updates on my adventure.
[One (M7) Original Android Development] Swinkid:
I had to set the CID to the RUU's original CID to get the OTA to work, not 11111111.. Don't know if that helps
[One (M7) Original Android Development] :
I also tried that. But the mmcblk0p19 has the my original CID. When I check my CID in fastboot (fastboot oem readcid) I get 11111111 but if I go to adb shell getprop ro.cid I get HTC__039.

Another weird thing I can't explain is that when I changed my CID to HTC__001 adb shell shows my CID as HTC__001. But when I try to flash the RUU 1.28.401.7 with CID HTC__001 I get error 130 (MODEL ID ERROR) So my guess is that the mmcblk0p19 is the one that the RUU is looking for when flashing the RUU.

Modifying that file breaks the signature and when I tried to flash the RUU with my modified mmcblk0p19 file I get error 155.

---------- Post added at 11:05 AM ---------- Previous post was at 10:59 AM ----------

UPDATE:

I just pushed my original file back to my phone an was able to run the RUU. So all good for now. So just a reminder to anyone that modifying the mmcblk0p19 will not allow you to install OTA updates or flash the RUU. It seems to check for a signature.
[One (M7) Original Android Development] dseries60:
Good info, thanks
[One (M7) Original Android Development] mojolive:
[/COLOR]UPDATE:

I just pushed my original file back to my phone an was able to run the RUU. So all good for now. So just a reminder to anyone that modifying the mmcblk0p19 will not allow you to install OTA updates or flash the RUU. It seems to check for a signature.[/QUOTE]

nice to hear you got it working again .

So what exactly did you do to get the RUU to work. as then I can get back to a stock rom and try to do everything all over again . :)

as I am in the same spot as you . can you detail it please.. please:)
[One (M7) Original Android Development] DigitaL BlisS:
I don't think you need S-ON to get the update. For curiosity sake I reverted back to my stock Telus rom (1.29.661.5) and received an OTA for version .17 and updated successfully (with S-OFF). No idea why I tried turning S-ON back on after figuring this out, but wanted to know why it wasn't working for the 4.2.2 update when I went to stock 401. Even with SuperCID and HTC__001 I couldn't use any RUUs (incorrect model #). Are OTA updates given out through carriers? Or do we connect to HTC's servers? I'm guessing we need the model id PN0710000 and the correct CID... curious to how other people were getting the update though and which steps they took. For now I'm stuck with S-ON, but I'm trying to revert back to stock now to see if I can get it off again (us Telus users don't have a RUU, only for the update, so I might be screwed since I need TELUS001 CID again but can't get S-OFF).

Edit: awesome it worked! S-OFF again. If you're on Telus, you need to unlock the bootloader again with a new code from HTC Dev (your old one won't work since the token ID changes with a new CID), then restore your nandroid/TWRP backup, and you should be able to get S-OFF again (or use your RUU if you're not on Telus I'm guessing).
[One (M7) Original Android Development] mojolive:
great info . i am not on tekus, but iy is a good thing to know about having a new unlock code ..
[One (M7) Original Android Development] zole2112:
After doing all of the steps from the first post over and over and over (at least 20 times) with mostly error -1 and numerous success messages my One remained S-ON. I had tried it in adb shell and in Terminal with no success.

I finally came across this posting and in Root Explorer long pressed the revone-0.2.1 file and clicked on Permissions and checked all of the boxes, the only that were not checked were the Write boxes for Group and Others so I checked these. Then I rebooted and made sure the Permissions stuck, they did. I followed all of the above steps in Terminal, I'm sure that adb shell would work too, with the exception of leaving the .bin off of the end of revone-0.2.1. Success the first time, I am now S-OFF.

Hope this helps someone.

I was already unlocked through HTC with a custom rom, RootBox JB 20130608.
[One (M7) Original Android Development] :
From what I can gather is that the OTA is looking into the mmcblk0p19 and it checks with your CID there if it doesn't match then OTA won't install. But in saying that I modified that file so it says that I have 11111111 as my CID. But I'm pretty sure when you modify that file it breaks the signature and even when I tried to flash the RUU 1.28.401.7 I get error 155.

But now you have me thinking if I modify the mmcblk0p19 file again and not worry about S-ON I night get the update installed.

Okay here we go... I will try that and see what happens next
[One (M7) Original Android Development] V1R3Z:
Victory!!!!!!!

OK for anyone getting errors and when u finally get success successfull u STILL find s-on heres what made it work for me:

#1 its a new hack and the op says its buggy and may/may NOT always work so u need to hae patience and keep trying!

#2 type up your ./revone -P and if it fails, gives you errors just press the up key on the keyboard and keep pressing enter to retry on the same command prompt untill you get a success OR it tells you there was an error and you HAVE to restart if it does go ahead and restart and come back to the command prompt and keep trying your ./revone -P untill it successedes WHEN IT DOES itll tell you success please restart your phone to continue...

listen!

restart your phone by holding the power button for 15 seconds... itll restart back to your home screen

open up a new command prompt and do your thing with step 2 follow all the directions on the OP... the ./revone -s 0 -u... WHEN it works itll say success again and this time do the same thing, restart with holding the power button for 15 seconds, right before it shuts off hold volume down and BAM s-off and unlocked!

if it fails just start over and keep trying NO LIE i promise im not exagerating i had to do this about or over 30 times but it finally worked

AT&T black 64gb HTC one

100% stock

no root

not unlocked

no htc oem unlock either

JUST REVONE = S-OFF

i love it! im so happy now! hehehe
[One (M7) Original Android Development] iamaniff:
I also get this with superCID.. 2x reflash RUU but still same.. system say like that
[One (M7) Original Android Development] :
Okay all I did was push back the original mmcblk0p19 to my phone and rebooted the phone and checked with adb shell to see what my CID was (using "adb shell getprop ro.cid"). Before I modified that file my cid in adb shell shows up as my original cid (HTC__039). So when I pushed the original mmcblk0p19 file back to my phone I checked it again and it shows my cid as HTC__039 even though I still SuperCID in the bootloader.

The RUU just checks the CID in your bootloader and checks for signatures in your phone. So when I modified the mmcblk0p19 file the signature was broken or altered. When I try to run the RUU I get error 155, something to do with image size error.

All I had to do was push the original mmcblk0p19 file back and I got everything working again.

---------- Post added at 11:58 AM ---------- Previous post was at 11:55 AM ----------

Like I said in my other post the OTA update will check your CID in the mmcblk0p19 file in your phone. If the CID in that file and the CID in your bootloader doesn't match then the OTA will see it has been modified.

But I will try again modifying the mmcblk0p19 and this time don't have S-ON and see what happens.
[One (M7) Original Android Development] mojolive:
Thank you so much for the info.. am doing that right now..

qustion GF has an htc one, S-off, i have already suoercid 11111111 should I just leave the mmcblk0p19 in the tel.? and dont touch it..if so will i still have super cid - 11111111?
[One (M7) Original Android Development] mrrogers1:
Well, you really should never take an OTA, it's very likely to take you down a one-way trip to S-On for good because they can push a new Hboot that closes the exploit used. We "usually" see this with each hboot update, we saw this with the LTE and most updates that came to the OG EVO, and EVO 3D. I mean, that's not say you shouldn't satisfy your curiosities but it's a bad idea (taking the gamble) receiving an OTA. Some might say, "well we have access to all the partitions with just HTCDev Unlock now, we don't need s-off" and those people may not remember when the EVO LTE first dropped and our first 2 hboot's were "open" like that and then 3rd, locked it all down. Then s-off was required to flash to the boot partition direct, it sucked and was quite the surprise for some that updated because we didn't have s-off IIRC at that time.

Just remember, we'll get the update, usually before the OTA anyway, so is it worth it? :)

No, does not matter.
[One (M7) Original Android Development] :
Yes you can just leave it alone or make a copy of it so you can always push it back if you have to.
[One (M7) Original Android Development] mojolive:
thank you . great to know this stuff in advance :)
[One (M7) Original Android Development] :
Well for me it is worth it for the sake of knowing things. I'm just a very inquisitive person and I like to find out how things work (to my capacity of couse). If it is too way over my head then I won't touch it. But I actually like this stuff. If I get permanent S-ON after the OTA then so be it. But I'm sure someone will find a way to get s-OFF again.
[One (M7) Original Android Development] iamaniff:
I'm not modified "mmcblk0p19" because when I check with command 'getprop ro.cid' it's shows superCID, bootloader command is shows superCID..
[One (M7) Original Android Development] ambuj:
Mine is HTC__044 and I did superCID without taking backup. Can I go back to my original superCID

Note: I have also flashed nodded hboot afterwards to get rid of red text and everything is working just fine. I have not tried official RRU though.
[One (M7) Original Android Development] :
That's good for you. However since I modified mine the signature was broken and when I got S-ON I got that bootloop. So I will try not having S-ON next time and see what happens.

---------- Post added at 12:14 PM ---------- Previous post was at 12:12 PM ----------

Just write your original CID back.
[One (M7) Original Android Development] iamaniff:
But I have the same issue can't install OTA. So now I'm back to custom ROM
[One (M7) Original Android Development] homer285:
Thanks for update 0.2.1, however, after at least 100 tries I get "success on ./revone -P no need to reboot" whether or not I reboot makes no difference. So after reboot or not I enter ./revone -s 0 -u and always get "Map Memory Failed" and underneath, "error code -1 or sometimes -2.

Exactly as I enter

C:\Android\adb>adb push revone /data/local/tmp/

3121 KB/s (648208 bytes in 0.202s)

C:\Android\adb>adb shell

shell@android:/ $ cd /data/local/tmp

cd /data/local/tmp

shell@android:/data/local/tmp $ chmod 755 revone

chmod 755 revone

shell@android:/data/local/tmp $ ./revone -P

./revone -P

revone v0.2.1

Gaining root access (thanks to Dan's motochopper)...Success.

revone successful - no need to reboot.

10|shell@android:/data/local/tmp $

C:\Android\adb>adb shell

shell@android:/ $ cd /data/local/tmp

cd /data/local/tmp

shell@android:/data/local/tmp $ ./revone -s 0 -u

./revone -s 0 -u

revone v0.2.1

Gaining root access (thanks to Dan's motochopper)...[-] Failed to map memory.

[-] Failed to map memory.

revone failed (error code = -1)

cid: HTC__039

bootloader: 1.44.0000

OS: 1.29.980.2

Kernel: 3.4.10-g42e6c45root@abm015#1 SMP PREEMPT
[One (M7) Original Android Development] cheetah2k:
I think I found my issue with getting S-Off

Disable the HTCMonitorService in msconfig and I found mine worked first go.

I had tried to get S-off for over 300+ times until doing this

:good:
[One (M7) Original Android Development] :
Just modified the mmcblk0p19 again this time I changed to HTC__001 and in my bootloader I still have SuperCID. Downloading update now and see what happens

UPDATE:

No luck. I'm still getting the "Modified" text window..
[One (M7) Original Android Development] iamaniff:
When u change ur CID.. try reflash RUU
[One (M7) Original Android Development] :
I have done that too. But a modified mmcblk0p19 will give you an error 155 when you run the RUU

Okay this time I have changed my CID in bootloader so it shows as HTC__001. Trying update again.
[One (M7) Original Android Development] gianton:
This should be in the OP.

Seriously I fear we will see a lot of bricked devices in the next days.
[One (M7) Original Android Development] kassemja:
Boot screen
[One (M7) Original Android Development] kanemari:
works for Telstra HTC One.

had a few issues getting it to work until i removed HTC Sync off the PC completely, and re-installed HTC standalone USB drivers.

worked first time after that. brilliant!
[One (M7) Original Android Development] wildanw2:
Finally I got S-OFF and removed tampered flag by following this http://xdaforums.com/showthread.php?t=2316832&page=2 posted by designgears :good:
[One (M7) Original Android Development] cheetah2k:
Just disabling the HTCmonitorservice did the job for me..

Seems the HTC Sync Manager gives ADB a headache when entering Shell mode.. :good:
[One (M7) Original Android Development] :
Yeah I have uninstalled that too before I tried doing S-OFF.
[One (M7) Original Android Development] TheMathMan:
So it seems hex editing mmcblk0p19 screws things up a bit...
[One (M7) Original Android Development] homer285:
OMG I finally have SOFF after days of trying, pure stock out of box, thanks again Revolutionary. Also I don't see any red text nor does it mention, "Tampered".

Suck eggs HTC you can go screw yourselves with lack of support for bootloader unlocking!
[One (M7) Original Android Development] adamlee011:
Awesome. That was my intention on my friend's one but I got frustrated and dev unlock first. All I have to do now is get rid of the red txt.

Sent from my S-off Viper One
[One (M7) Original Android Development] Devicecustomizer:
thanks bro. the instruction are much clear now

thanks a lot
[One (M7) Original Android Development] kazemitsui:
with S-Off can we mod the phone to receive LTE from bands in other countries that dont share same bands as the US version of the phone?

Or is that just a dream?!
[One (M7) Original Android Development] :
That's a dream it is hardware related.
[One (M7) Original Android Development] kazemitsui:
damn alright haha
[One (M7) Original Android Development] saenz4931:
Can someone please help me.. I don't know what am I doing wrong.. It keeps telling me the fine doesn't exist..
[One (M7) Original Android Development] emanon:
Red text and Tampered are when you unlock with htcdev.

\Regards
[One (M7) Original Android Development] troly:
Open root explorer, rename files revone.bin ---> revone revone file and copy to the address / data / local / tmp
[One (M7) Original Android Development] spitfire2425:
Love how everyone was so pumped for moonshine and this one is getting more hype. Thanks again for the wonderful exploit.
[One (M7) Original Android Development] MOEHEET:
fianly after one day of tryin ..finally got my hytc one s-off.

any aussies having dificulty ..plz let me know......we can gtalk if u want...

cheers
[One (M7) Original Android Development] mjskraju:
Sprint HTC One & GSM Roms

I've a doubt regarding Sprint HTC One, If I unlocked my Sprint HTC One to be usable with any GSM carrier(of course outside USA and I'm from outside USA) and use only GSM all the time, can I flash any GSM version's Roms as well as RUUs after getting S-OFF?.
[One (M7) Original Android Development] Shadow Samurai:
That's what supercid is for!

Sent from the one and only HTC One
[One (M7) Original Android Development] :
This is weird. I just give up trying to install OTA updates!!
[One (M7) Original Android Development] pablo11:
Anyone notice that quick boot no longer works since using revone?

I mean fastboot in power options. It just gets stuck at the ONE splash screen...............

Could just be me but I've tried several roms now with APM and even from that menu the quick boot option does the same.

Fine with regular reboot.
[One (M7) Original Android Development] ScottSpittle:
S-Off!

Worked Great! Thanks.

HBOOT-1.44.0000

RADIO-4A.14.3250.13

HTC One GSM
[One (M7) Original Android Development] oneslow5oh:
What can s-off do? Could I flash sprint roms now?
[One (M7) Original Android Development] Shadow Samurai:
worked for me...something must have went wrong for you
[One (M7) Original Android Development] :
You can flash any RUU if you want to go back to stock is one thing. I'm not an expert on what more you can do.
[One (M7) Original Android Development] pbedard:
Worked great
[One (M7) Original Android Development] Riyal:
[MENTION=517216]pablo11[/MENTION]

It's working on my device. What doesn't work is the Hot Reboot in APM. Although I'm having doubts S-Off has anything to do with it.
[One (M7) Original Android Development] homer285:
Ah of course, silly me.

Sorry to double post this but do any successful pure stock SOFF'ers have issues now flashing a recovery? I simply cannot get any recovery to stick, manually nor via A-I-O T.

Regards
[One (M7) Original Android Development] pablo11:
Thanks, you are right. It's hot reboot which doesn't work.

Otherwise S-Off is perfect. It's probably a non-related issue.

Cheers.
[One (M7) Original Android Development] allgsmnetwork:
great work

Hi to all,

very the best work for s-off please update for tool simply usage into widows :good:

Plese the procedure simply at moment for windows xp ?

thanks e good work for update :o
[One (M7) Original Android Development] jimanjr:
Worked the 2nd time. Carrier is Vodafone RO.

Thanks!