yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] Syn Ack:
Just got a brand new (T-Mobile) HTC One today, due to warranty malfunction. Long story short:

Opened box, booted into Android.

Turned on USB debugging.

Ran through revone steps.

Took 3 times to get success with "./revone -P". All you have to do is tap the up arrow key in command prompt and run it again if it fails.

Took 4 times to get success wit h"./revone -s 0 -u". Same step as above.

Boom success. S-Off with no tamper within 3 minutes of owning the device :)
[One (M7) Original Android Development] iamaniff:
Unlocked, S-Off CID HTC_001, get error when run the Europe RUU
[One (M7) Original Android Development] :
Exactly what I have been posting. However if you use SuperCID you can run the Europe RUU.
[One (M7) Original Android Development] staples101:
success! easiest s-off ever.
[One (M7) Original Android Development] tids2k:
good job a.k.a AUS_KING
[One (M7) Original Android Development] Theshawty:
How are you guys flashing the RUU? I got an error every time I flashed it from being booted up. When I started the RUU when my phone was in fastboot, it flashed fine without a hitch.
[One (M7) Original Android Development] :
Just been running it on my pc.
[One (M7) Original Android Development] NOFSBIGE:
ok so here is a question... I have an at&t version One and I made it s-off and unlocked boot loader... I then changed the CID to BS_US100 for the dev edition here in the US and installed the stock RUU from HTCDEV.COM... Now when I check the build prop it shows my CID as BS_US100 if I go s-on to get rid of the "test device" message will it be like I have a completely stock Dev Edition of will something go wrong?
[One (M7) Original Android Development] Theshawty:
Try running it when your phone's booted to fastboot. That's when the RUU successfully flashed for me, super CID or not. (though locked bootloader and S-OFF)
[One (M7) Original Android Development] ext109:
Remove tampered and let it show *locked* instead of *relocked* before s-on then probably yes (assuming you've got 64GB version)
[One (M7) Original Android Development] tjsooley:
Us dev cid is bs_us001
[One (M7) Original Android Development] NOFSBIGE:
sorry thats what I meant
[One (M7) Original Android Development] Pony Express:
Not true.

With s-on, the attempted unsigned hboot flash will fail.

With s-off, the attempted unsigned hboot flash will succeed- thereby likely causing a hard brick.

ieftm, kmdm and your entire Revolution Dev team - outstanding, thank you !! :)
[One (M7) Original Android Development] :
OTA still will not install. I have tried that method too with same result.
[One (M7) Original Android Development] Theshawty:
Weird. Maybe your One's secretly telling you OTA's aren't for you and that it wants you to be messing with custom roms? :D
[One (M7) Original Android Development] Indirect:
He means if you already flashed it then s-on'd. If you're s-off it won't "likely cause a brick" unless you flashed a wrong file or had a bad md5. Please do your research before making a claim like that.

Sent from my One phone to rule them all
[One (M7) Original Android Development] Pony Express:
Sorry for the misunderstanding.

As you stated flashing a wrong file or a bad md5 are issues just as flashing the incorrect hboot required for specific rom(s) can cause a brick.

My comment comes from personal experience, mine and several others who did so on the Nexus One.
[One (M7) Original Android Development] metzzarn:
Great!

Thanks guys, worked flawlessly on my Scandinavian One :)
[One (M7) Original Android Development] iuly_vn:
Thank you very match again! I did not see it before you post, but I'm informed with your help! Thanks :good:
[One (M7) Original Android Development] :
I think it has something to do with the model ID of the HTC One from UK and the model ID of Asian/Ocenia region. Because I know a member who successfully used the Asian RUU and installed the updates with no problems.

Like I said I have flashed the RUU 1.28.401.7 and I was fully stock locked bootloader and S-ON with CID HTC__001 and the updates won't install. I still get the Variant system window.

And when I try to use the same RUU to flash the 1.28.401.7 again (with CID HTC__001) I get error 130 (MODEL ID ERROR)
[One (M7) Original Android Development] baste07:
How do I check is I have unofficial hboot
[One (M7) Original Android Development] Turets:
Perfect

Flawless On T-MOBILE M7
[One (M7) Original Android Development] legend0fthefall:
This took quite a few tries (about an hour) but finally was able to get it to work.

Stock everything and still locked bootloader (was waiting and hoping for S-Off before unlocking!!)

T-Mobile USA.

I kept receiving "Failed to map memory." errors, Error -1 and Error 2. A lot of rebooting and repeating steps 2 through 4.

Finally worked and now I am unlocked and S-Off and Super CID. Loading custom recovery and roms as we speak!!

Thank you Revolutionary!!!
[One (M7) Original Android Development] jdh10475:
Why S-Off before unlocking?
[One (M7) Original Android Development] --unkown--:
Im unlocked and rooted

nothing happens afte the command r ./revone -P

What im doing wrong

after fastboot devices I see my model and then fastboot su i see some command...but thats all !:crying:
[One (M7) Original Android Development] gunnyman:
you don't unless you put one on there.
[One (M7) Original Android Development] legend0fthefall:
In the early days of the HTC Sensation if you went to HTC Dev and unlocked your phone you would not be able to achieve S-Off. You had to S-Off first before Unlocking. Key words there were "early days". I do not know if that changed later on. So it just kind of stuck with me. I figured I would wait until S-Off was attained again. Superstitious? Prolly.
[One (M7) Original Android Development] cschmitt:
Why so much effort to change cids, etc. in order to take an OTA? HTC is probably going to drop an S-ON bomb in the near future.

Certainly current RUU's are fine since they released before the S-OFF exploits went public, but I'd steer clear of anything newer.

It would be best to to download the OTA, extract the rom updates and manually apply them to /system, bypassing the firmware.zip and any hboot updates it may contain.
[One (M7) Original Android Development] baste07:
Thanks anyways
[One (M7) Original Android Development] bjg020683:
Anybody know T-Mobile developer edition cid
[One (M7) Original Android Development] iamaniff:
With CID__001 install Europe RUU get error.. I try back to my original CID (HTC_044) and run Asian RUU.. no OTA issue with unlocked and s-off

---------- Post added at 03:09 AM ---------- Previous post was at 03:06 AM ----------

BS_US001
[One (M7) Original Android Development] Indirect:
They cant push an OTA to turn S-on for multiple reasons.

First being some of their software engineers have s-on on their devices so they'll kill those and also the second reason being if I have a modified Hboot, then I get that update, they brick my phone so they are held liable atleast in the US for destruction of property.
[One (M7) Original Android Development] baste07:
Did you locked the bootloader before flashing ruu?
[One (M7) Original Android Development] iamaniff:
Nop.. still unlocked with s-off
[One (M7) Original Android Development] cschmitt:
Check out the 1.29.1540.16 dev edition OTA, they pushed an hboot update in that package. If you had s-off and any modified partition signatures it'd be a brick.
[One (M7) Original Android Development] :
That's what I'm gonna try when I get home. The Europe RUU definitely giving me trouble. I think it is the model ID of the phone that's causing the issue.
[One (M7) Original Android Development] zyy757:
so if I go back to s-on, and locked, can I unlock via htcdev again?
[One (M7) Original Android Development] iamaniff:
I unlocked via HTC dev with s-off locked
[One (M7) Original Android Development] swa2k4:
worked great

worked great!! Thank you!!! SOFF and unlocked bootloader, wont have to register the phone with htcdev to prevent any warranty potential issues!
[One (M7) Original Android Development] zyy757:
i know s-off + locked is OK, but I mean s-on +locked
[One (M7) Original Android Development] dizzyraider:
I reflashed the RUU and Hot Reboot still frozen at HTC screen. Hot reboot isn't really a big deal, but just to confirm, Hot reboot is broken AFTER S-Off.

BTW, thank you Revolution dev team for the s-off :)
[One (M7) Original Android Development] cheetah2k:
You're not the only one with this issue. I ended up going with this ROM as the MID must be the same as the Telstra Australia HTC1's.

Works a treat :)

---------- Post added at 01:05 PM ---------- Previous post was at 01:02 PM ----------

Got mine working with OTAs. Anyone with Telstra Australia handsets, the Asia WWE rom is compatible providing you change the CID to HTC__044.

Did that on mine, received the OTA's no problem. Now rocking 1.29.707.16 :D
[One (M7) Original Android Development] joefrank:
Hey guys do you plan on doing a bundle? For some reason my two pc won't find my device one is xp and the other ubuntu. Well I did a search and found the cause for some reason it cant get ubuntu to work for me. Maybe if you guys make something like that It could work???
[One (M7) Original Android Development] jdh10475:
Worked great thanks!
[One (M7) Original Android Development] iamaniff:
Nice!... So any plan for SGS4? :p
[One (M7) Original Android Development] MOEHEET:
delete
[One (M7) Original Android Development] baste07:
Try to erase cache in fastboot
[One (M7) Original Android Development] 4D3:
Hi,

No matter what i do i get error code = -1 when i rum the S-OFF command:

D:\ADB>adb push revone /data/local/tmp/
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
2272 KB/s (648208 bytes in 0.278s)

D:\ADB>adb shell
root@android:/ # su
su
root@android:/ # cd /data/local/tmp
cd /data/local/tmp
root@android:/data/local/tmp # chmod 755 revone
chmod 755 revone
root@android:/data/local/tmp # ./revone -P
./revone -P
revone v0.2.1

revone successful - please reboot to continue.
root@android:/data/local/tmp #
D:\ADB>adb shell
error: device not found

D:\ADB>adb shell
root@android:/ # su
su
root@android:/ # cd /data/local/tmp
cd /data/local/tmp
root@android:/data/local/tmp # chmod 755 revone
chmod 755 revone
root@android:/data/local/tmp # ./revone -s 0 -u
./revone -s 0 -u
revone v0.2.1

revone failed (error code = -1)
255|root@android:/data/local/tmp #
D:\ADB>adb push revone /data/local/tmp/
3577 KB/s (648208 bytes in 0.176s)

revone failed (error code = -1)
255|root@android:/data/local/tmp # ./revone -s 0 -u
./revone -s 0 -u
revone v0.2.1

revone failed (error code = -1)
255|root@android:/data/local/tmp # ./revone -s 0 -u
./revone -s 0 -u
revone v0.2.1

revone failed (error code = -1)
255|root@android:/data/local/tmp # ./revone -s 0 -u
./revone -s 0 -u
revone v0.2.1

please can anyone help with this?
[One (M7) Original Android Development] il Duce:
You're not supposed to run the command in fastboot, read the OP carefully.

Run the -P again, reboot, run the -s 0 (that's a zero not a letter) without the -u, reboot again, then run the -u, reboot again, maybe it work?
[One (M7) Original Android Development] kmdm:
Read post #2.
[One (M7) Original Android Development] hengmy:
thank Revolutionary

glad to see Revolutionary has back to the game, miss Revolutionary S-OFF alot!
[One (M7) Original Android Development] dizzyraider:
I also had the error a couple of times, rebooting the phone and try it again. I had to do it to s-off and again for temper reset (reboot til it works)
[One (M7) Original Android Development] hotaru2k3:
flashing an unsigned hboot (with s-off) might brick your device, but probably won't unless that unsigned hboot has more problems than just being unsigned.

flashing an unsigned hboot (with s-off) and then setting s-on will brick your device.
[One (M7) Original Android Development] joetang97:
Failed to gain S-Off first try. Successful on second.

Thanks a lot, instructions are quite easy once you know what and where to enter the commands.

Full stock, HTCDEV locked, so now they don't have my unlock request on record. Great for if (touch wood) anything should happen.
[One (M7) Original Android Development] retschy:
If this is radio s-off no Problem in updating hboot our?
[One (M7) Original Android Development] cheetah2k:
I already have the i9500 octacore.. Actually prefer the HTC1 as the battery lasts longer and the screen isnt so yellow...
[One (M7) Original Android Development] owenbeals:
Some of you have asked about a video. I have put one together.

This shows the complete process as outlined in the OP. It worked flawlessly for me.

http://www.youtube.com/watch?v=U2qHzqTqdvY
[One (M7) Original Android Development] LenAsh:
Only apples if you already have b/l unlocked and root... which is part-useful.

Video of this already done a few days ago too...
[One (M7) Original Android Development] notown775:
thanks made it super simple

\(*_*\) TAB2 7 (/*_*)/
[One (M7) Original Android Development] SinisterChedda:
This was painless compared to the HTC EVO 3D s-off. Thanks. Took me a few minutes to do. Im S-off and tamper flag removed. Time to put a hex-edited hboot on my one. Props to everyone involved. I will be donating soon. Just gotta figure out who/where to send it.
[One (M7) Original Android Development] ciccio80:
if a revert on s-on after command "fastboot oem writesecureflag 3", i lose all my data?

Regards
[One (M7) Original Android Development] Unoath:
No, data is not lost going back to s-on. :)
[One (M7) Original Android Development] Skizzy034:
Do we need to do anything with the updated binary, like rerun the hack, if we already achieved s-off when revone was first released?
[One (M7) Original Android Development] gusto5:
Nope. My suggestion would be to keep the updated binary on your phone so you can go back and forth from the terminal if you're in a situation to run out from the terminal.
[One (M7) Original Android Development] kmdm:
You just need to donate again, that's all. :D

(You don't.)
[One (M7) Original Android Development] zenneoiv:
I have followed step to step on this clip. Revone work like a charm ! :good:

thanks to revolutionary.io and owenbeals.
[One (M7) Original Android Development] :
Okay I finally found out why I can't install OTA updates on my HTC One when I have a stock 1.28.401.7 ROM. I have been scratching my head since yesterday my phone with a CID HTC__001 still won't install the OTA update 1.29.401.12. The reason I've been having problems is because my model ID is PN0711000 and the 1.29.401.12 OTA update is looking for model ID PN0710000.

From doing more research it seems that the only way I can change my model ID to PN0710000 is to have ENG HBOOT and S-OFF. Being S-OFF alone will not let me change the model ID number. Another thing I discovered is that when we have SuperCID our original CID shows up when you "abd shell getprop ro.cid" but when you actually use any specific CID (HTC_001 or HTC__044 etc etc) then this shows in adb shell as well.
[One (M7) Original Android Development] MaximN97:
I sent you a pm!
[One (M7) Original Android Development] :
Yes I got it. I used the Asian RUU and managed to install the OTA update with no issues.
[One (M7) Original Android Development] Dougi:
worked like perfect....

thanks REV team ;) ;) , i'm now S-OFF :D
[One (M7) Original Android Development] homer285:
Thanks for reply, succeeded with goo manager funnily enough.

Regards
[One (M7) Original Android Development] gianton:
This should be at OP, very explanatory thanks!
[One (M7) Original Android Development] wzu7:
any other way to get "abd shell getprop ro.cid"? i mean not using command prompt...or from others apk etc ..
[One (M7) Original Android Development] Black-FR:
Thanks for the fantastic Tool.

I did needed a few trys and now I'm s-off, without any other unlock before.

Gesendet von meinem HTC One mit Tapatalk 2
[One (M7) Original Android Development] toolhas4degrees:
:good:Thank you rev team this worked great on my one and just used the dna ver to s-off my butterfly:good:
[One (M7) Original Android Development] :
Try CID getter from play store
[One (M7) Original Android Development] wzu7:
it's also from my post here ...

can someone confirm command "abd shell getprop ro.cid" IS THE SAME when we use CID Getter ..

so who get hboot CID : 11111111 AND abd shell getprop ro.cid = 11111111 , can test it !! any different ?! thanks
[One (M7) Original Android Development] gianton:
It's the same, CID getter app and the adb shell command get info from build.prop file. Hboot CID is different.
[One (M7) Original Android Development] iamaniff:
Yes.. I have no issue with OTAs update (model number matching with RUU)
[One (M7) Original Android Development] :
Yeah that's why I was having those issues with the UK OTA update because my model ID number doesn't match the UK ID number. Would be good to be able to change the model ID number so you really can use RUU and be able to install OTA updates.
[One (M7) Original Android Development] cheetah2k:
Fark this is a never ending story!!

I'm happy that mine supports 1.29.707.16 Asia WWE and gets OTA's - anything was better than the bl00dy Telstra FW. This one does everything I want, plus it gets the latest updates :D
[One (M7) Original Android Development] tjsooley:
Ok, that makes sense. The US dev is same model as att
[One (M7) Original Android Development] lucky76:
Any one have same problem like :

After S-OFF my One, I notice a small change.

In the Setting -> About -> Tell HTC and error reporting: I got a new warning message below saying this is a Test Device.

Is this an intended purpose of S-OFF? Anyway to turn off automatic report sending

Thanks
[One (M7) Original Android Development] Bloedwraakje:
Wahoo ..

S-off ... NO Tampered sign ....

Works like a charm ..

ARHD 10.2 ... with help of the video posted in this threat somehow ...

Easy ... understanding nice and quick ...

Thank you very much .... Works like a CHARM!!!!
[One (M7) Original Android Development] s7yler:
Thanks - it worked in the first try! I have a HTC One from T-Mobile Germany.

I had the device HTCDev unlocked, S-ON and rooted, stock ROM 4.2.1 with elementalX kernel before I started. After the guide, I now have S-OFF and Tampered removed.

If I want to be able to recieve OTA, what do I then have to do?

Can I leave S-ON and do I have to lock the bootloader again? should I use ./revone -l or ./revone -r

And do I have to revert back to stock kernel also?
[One (M7) Original Android Development] gray10k:
I'm learning as I'm going and I'm surea a lot of others are as well so please help me archive the correct answer here:

What will modifypartition signatures which would cause a bricked phone were it to be s-off'd or have a new hboot installed?

Will changing cid modify the partition signatures?

Will editing the tamper message with all spaces (not blanks)?

Will replacing the boot animation with custom?

Please add anything that will or even include a general application to what would modify the partition signatures causing a brick.

Everyone has done a GREAT job of warning that it will be bricked, but as a newb to s-off I am not sure I completely understand the difference in which mods (particularly the ones above) modify the area affected by s-off.
[One (M7) Original Android Development] kmdm:
Post #2 updated with alternate revone to support HTC J One.
[One (M7) Original Android Development] fnoji111:
thx kmdm!

HTL22 M7_WLJ HTC J One S-OFF succsess!

https://twitter.com/HTCsoku_dev/status/344426177378783232
[One (M7) Original Android Development] tjsooley:
Thanks for all the work
[One (M7) Original Android Development] bjg020683:
Does my bootlloader need to be locked to get a ota?
[One (M7) Original Android Development] mahesh_9j:
Hi I m on HTC One Dev edition and did s-off and super CID in bootloader and in mbk file also. Now if I'll push back my original file and flash dev edition RUU in S-Off mode will it run and I'll be able to receive OTA?

Thanks
[One (M7) Original Android Development] x017in:
To receive OTA you need to change ur RUU to the dev edition RUU is what I think.

Sent from my HTC One

---------- Post added at 07:15 PM ---------- Previous post was at 07:13 PM ----------

Don't think so. However u need to be on stock recovery to install the OTA

Sent from my HTC One
[One (M7) Original Android Development] adam_wingert:
Worked on AT&T HTC ONE

Worked like a charm. I don't have that much knowledge when it comes to ADB but I've been using it for years. Just follow the instructions and it works just like it is supposed to. I know have SOFF and no more "Tampered" warning. Thanks Devs for all of the hard work. You guys are the chit!!
[One (M7) Original Android Development] eyeisdasteve:
I think doing the revone messed something up.

I believe it has something to do with my getvar all.

Something in it has changed and I can no longer RUU. Can't RUU from fastboot or run the setup.exe.

I'm getting an error that says 'FAILED (remote: 24 parsing android-info fail)' when I try to fastboot RUU.

Setup.exe fails and says 'UNKNOWN ERROR'
[One (M7) Original Android Development] fabricatta:
writing hboot failed , true s-off??

hello ,

I have reached : s-off and supercid

but when I try to flash enghboot

fastboot flash hboot enghboot.nb0

i got an error

sending 'hboot' (2080 KB)...

OKAY [ 0.484s]

writing 'hboot'...

FAILED (remote: not allowed)

I read about a "partial s-off"?

some suggestion?

__

sprint htc one 32 gb

viper-rom 1.1.0

thanks for the help!

fabri
[One (M7) Original Android Development] mindlessbb:
Ugh, I hate when I actually have to post... I've not been able to find much regarding my error at all. I'm getting Error Code = 2, which seems to be largely undocumented. At least as far as searching around XDA and google has shown.

US T-Mobile HTC One. HTC Dev unlocked. Running Stock Rom, pre-OTA.

Downloaded the most recent Revone (0.2.1)

Pushed no problem.

Unable to chmod in $ prompt, but works at # prompt no problem.

root@android:/ # cd /data/local/tmp
cd /data/local/tmp
root@android:/data/local/tmp # ./revone -P
./revone -P
revone v0.2.1

revone failed (error code = 2)
2|root@android:/data/local/tmp #

Any thoughts besides "Use Moonshine"? (I will if I can't get this to work, but now it's personal!)

Thanks!
[One (M7) Original Android Development] emanon:
You will need to be on stock kernel and stock recovery to receive OTA.

\Regards
[One (M7) Original Android Development] DamBadz:
Now I can'use function hot boot anymore any idea ? Before I get s off it alway work thx
[One (M7) Original Android Development] Theshawty:
It's because of S-OFF.
[One (M7) Original Android Development] DamBadz:
For real? Why?
[One (M7) Original Android Development] iuly_vn:
Hi friends! I have 3 very very important questions. I'd like to clarify it to yourself, for which I would be very grateful!

Case 1. There are Stock shiped rom, H-boot and recovery on the pfone, with "revone" Unlock and S-OFF bootloader. It is clear, that if I lock it -S-ON and Lock with the commands from post 2, without re-flash stock rom, or stock img or H-Boot again, no problem. Is it Right?

Case 2. There are stock shiped rom and recovery, with "revone" unlock bootloader - Unlock and S-OFF status, but I've root the rom with program "SU" and uninstalled some not important, but system applications. Then I want to unroot the rom again and lock the bootloader- "S-ON" and "Locked" status, with the "revone" post 2 komands.

Should I re-flash any stock RUU + img + H-bboot and which of the three, or I can to lock and S-ON bootloader directly /with revone post 2/, without dangerous to brick the pfone?

Case 3. There is Unlocked and S-OFF bootloader, with revone S-OFF/Unlock metod and instaled custom rom and rekovery, but I want to lock bootloader again Locked/S-ON, with revone metod post 2. What should I do before, to avoid hard brick?
[One (M7) Original Android Development] Guich:
It's a bug of s-off :)

We don't know why...
[One (M7) Original Android Development] stevedebi:
I have to disagree here. The updates are provided for stock systems. If the user modified the system such that an update killed the device, it is not the fault of HTC.