yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] zipsnet:
did I say anything about screwing up the phone? And yes If I can not get S-off on my phone because already came with .11 or OTA won't allow me, then I'd rather get other phone where my $600 allow me to do what ever I please with my phone and in other to exchange my phone it had to be within the first 14 days you bought it.

I don't feel like I have to explain my self here, but since you guys need to know ....
[One (M7) Original Android Development] leon sprouse:
I gave up

As much as I hate to admit it I know that Revone won't work on my phone. I continue coming to this site in the hopes someone finds a way for me to unlock etc without HTCDev. It seems many keep trying (as in the above post) and when they screw up their phone expect the carriers or the manufacturer to replace it. This is just wrong. FYI , I am sure HTC reads these posts! IMO if you can't afford to replace a $100 phone stop messing with it!
[One (M7) Original Android Development] harlenm:
Here is what I did. I have 2 phones in front of me. It worked perfectly on one phone, won't work on the other.

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

2531 KB/s (648208 bytes in 0.250s)

C:\android>adb shell

shell@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: invalid option -- 'p'

revone v0.2.1

revone successful.

root@android:/data/local/tmp #

C:\android>adb shell

shell@android:/ $ su

su

root@android:/ # cd /data/local/tmp

cd /data/local/tmp

root@android:/data/local/tmp # ./revone -s 0 -u

./revone -s 0 -u

revone v0.2.1

revone failed (error code = -1)

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

Finally got s-off on this device. Now to remove tamper flag, reinstall factory rom, flash stock recovery, and then s-on and lock bootloader. Pain in the butt!

---------- Post added at 12:06 PM ---------- Previous post was at 11:51 AM ----------

finally
[One (M7) Original Android Development] daleski75:
From the posts I thought you was the guy who needed help after changing the CID so please accept my apologies for the misunderstanding no harm was meant
[One (M7) Original Android Development] iElvis:
I have seen other people have MID/CID conflicts after flashing GE and 4.3 firmware, then going s-on and flashing other roms. Unfortunately, having gone s-on, there is no way to fix it since there is no way to change MID or CID anymore.

This is yet another example of why going back to s-on after modding your phone is a VERY bad idea.
[One (M7) Original Android Development] Theshawty:
It's always stupid to go S-ON once you're S-OFF. I realized that a tad too late, though. (with a phone switch in between, though, and a whole month on a Crapsung S4)
[One (M7) Original Android Development] JONBOY345:
I accidentally hot rebooted after s-off.

Locked at boot animation for 7 hours now... Holding power button only makes the lights flash, never actually powers down... I've held it up to 2 minutes several times.

Any help would be great....
[One (M7) Original Android Development] DeSaint2:
Hold it under a bright light. The sensors in the top left of the device specifically then hold down the power button.
[One (M7) Original Android Development] JONBOY345:
THANK YOU SO MUCH.

I searched every key word I could think of to try and find the solution and I couldn't. Thank you.
[One (M7) Original Android Development] murtezahu:
did you try with a 'P' instead of 'p'

I tried with with 'P" a bunch of times, then did lower case and it worked.

i am also on an at&t htc one
[One (M7) Original Android Development] harlenm:
This is how I got it to finally work.

First off, it seems to work better if the phone is rooted, so i took the stock rom and flashed twrp to it, let twrp root the phone. then pushed revone, set permissions and ran -P. Hard rebooted the phone, then ran s-off. After that, shut the phone off for >30 seconds. Ran -P again, hard rebooted phone, and then ran -t to remove tamper flag. Restored nandroid of stock unrooted rom, flashed stock recovery, and shut off phone for >30 seconds. Booted it up, ran -P, hard rebooted phone, then ran -l and fastboot command to lock and s-on.

Worked flawlessly.
[One (M7) Original Android Development] donmarkoni:
Good example how it's supposed to be done! :good: Read and learn, then read some more, then do it in one shot, no mistakes! :highfive:
[One (M7) Original Android Development] sokoko:
No way to go stock

As of Htcdev unlock and on 2.24 you can not even go back to stock.Even with relocked bootloafer,because there is no 2.24 ruu..I think im stuck here with tampered.I dont care for the "relocked".But tampered there is no way to revert it if you are s-on and in 2.24.401.1. If anybody can help to remove tampered i would appreciate.
[One (M7) Original Android Development] tiho5:
No, not for now. Many wait, so must you. Sorry
[One (M7) Original Android Development] pet4a:
I managed to s-off.

how do i continue to unlock the bootloader? just use ./revone -u?
[One (M7) Original Android Development] GalaxyUser50:
Are you sure you aren't already? Did you lock after you did it? Because the command "revone -s 0 - u" I think that's the right one from the instructions, already unlocks it.
[One (M7) Original Android Development] zFayZz:
cmoooooon hboot 1.54 at least maybe an update on progress.... :(
[One (M7) Original Android Development] wckong:
When I S-OFF'd my One using the "revone -s 0 -u" (by the way, there is no space between the dash an the 'u' character), S-OFF was achieved, but the boot loader remained locked. I was also puzzled by this and was worried that the process may have only been partially completed. But then I ran "revone -u" and that unlocked my boot loader. I don't think I've ran into any issues, yet, fingers crossed.

What has kept me puzzled was that even after I flashed a custom recovery (TWRP) and custom rom (ARHD), my boot loader did not display the TAMPERED sign. I initially flashed my custom rom by booting into TWRP via fastboot instead of a flashed version of TWRP, but I have since flashed TWRP.

Can anyone enlighten me on what would cause the boot loader to display the TAMPERED sign? Hopefully I can avoid it from being tampered.

Thanks.
[One (M7) Original Android Development] GalaxyUser50:
Sorry I was typing from a phone didn't mean to put the space. Anyways it seems like you can install roms and a recovery. But for tampered don't you just run "revone -t" or did you try that already?
[One (M7) Original Android Development] wckong:
Currently, my phone doesn't show the tampered sign which was contrary to what I have read on the forums - ie. after installing a custom recovery/rom, people had noticed the tampered sign. I just wanted to know exactly what causes the tampered scenario so I can try and avoid it in the future.

Thanks.
[One (M7) Original Android Development] beaups:
Tampered flag is really no big deal. Ruu will remove it. Anyways, if you want it to never show up again, just build your own kernel ramdisk and remove /sbin/tpd. You'll never trip the flag again.
[One (M7) Original Android Development] ilal2ielli:
Unlocking bootloader using revone prevents tampered from appearing. Normally unlocking bootloader using HTC-Dev and flashing custom recovery causes bootloader to show tampered.
[One (M7) Original Android Development] GalaxyUser50:
Oh I see now, we'll my phone didn't do it either but it's fine. So I'm pretty sure yours is fine too.
[One (M7) Original Android Development] iElvis:
Tampered only shows up if you've modified system files and are s-on. It's part of the signature check with s-on. Since you went s-off first, Tampered never had a chance to show up.

But if it's there when you s-off, it will stay there after s-off until you change your firmware.
[One (M7) Original Android Development] beaups:
It actually shows up much easier than that. As simple as mounting partitions rw.
[One (M7) Original Android Development] iElvis:
Should have said system settings. I knew it was something like that.
[One (M7) Original Android Development] :
Had some issues with this initially, totally my fault - as mentioned I should have read everything 2-3 times before attempting. The process quoted above worked 100% without issues.
[One (M7) Original Android Development] PillowMetal:
S-Off is enough... you do NOT need to be unlocked.

Incorrect, I am fully locked with S-Off (only ran "revone -s 0", never ran "revone -u"), You can take the custom recovery image (or any other image for that matter) and place it in a zip file with "android_info.txt" and flash it through

fastboot oem rebootRUU
fastboot flash zip <nameof.zip>
fastboot reboot

In the old days of SD Cards you could name this same zip file as your model name (PJ75IMG.zip for example) and it would prompt you to flash automatically when the bootloader started. The above method is the replacement way of doing a similar thing without unlocking the bootloader. This has three huge advantages in my mind:

1) You do not ever have to unlock with HTCDev and be in their database.

2) You do not ever have to worry about a future hboot as part of an OTA or RUU not working with revone to unlock again.

3) You will never be UNLOCKED, RELOCKED, or TAMPERED on your phone.

You can then hide S-OFF with a modified hboot if you care to, and noone would ever know your phone has been modified, except for the red test device text in "Settings->About->Tell HTC and error reporting" that can only be somewhat dealt with by deleting udove.apk

When you flash custom recovery this will cause red text in the recovery startup splash screen, and if you flash a custom kernel, this will cause red text in the phone startup splash. Both of these can be addressed with the same hex edited hboot that hid S-OFF.
[One (M7) Original Android Development] InflatedTitan:
Why does revone keep telling me "segmentation fault" when it tries to gain root access. All I'm trying to do is make it say "locked". I'm already s-off
[One (M7) Original Android Development] DeSaint2:
Are you on 1.54 hboot? If so that is probably why
[One (M7) Original Android Development] iElvis:
Does Sprint care that much about modding? I've seen people get warranty replacements from AT&T with phones that were modded out the wazoo. The guys at the store never check that kind of stuff and I doubt even know how to. I've never heard of anyone having issues sending a modded phone to the AT&T warranty department.

It's a different story if you have to send your phone to HTC, but AT&T seems more concerned with keeping its customers happy than with rooting.
[One (M7) Original Android Development] AlbertoSONIC:
Hi guys, i need to come back to stock (bootloader locked) to send my phone to assistance. So can i do that:

1)S-Off with Revone

2)Change CID to 1111111

3)Lock Bootloader with Revone

4)Install 1.28 RUU

5)Write my original CID (HTC__405)

6)Come back to S-ON

Right? And what happends if i write a wrong CID? Can i brick my phone following this steps?
[One (M7) Original Android Development] iElvis:
What bootloader version are you on? If you are still on 1.44, you can probably still do it.

And yes, you can screw up your phone by going back to s-on the wrong way. Haven't seen any hardbricks, but several unstable ones that can't be fixed because they can't s-off again. Putting in the wrong CID can definitely cause problems.
[One (M7) Original Android Development] AlbertoSONIC:
Please help me with a step by step.... I don't want to destroy my phone!
[One (M7) Original Android Development] iElvis:
This is the best place to start:

http://xdaforums.com/showthread.php?t=2358738
[One (M7) Original Android Development] godutch:
good to know you don't need to unlock and there are alternative ways but really when you are s-off you don't really need to worry about hboot upgrades because you can always downgrade to a working version
[One (M7) Original Android Development] Theshawty:
Unless an OTA you take replaces the partition that stores the security flag info..

NEVER TAKE OTA'S! Take this from a guy who stupidly accepted the 4.2.2 OTA before knowing I was still S-ON..
[One (M7) Original Android Development] Indirect:
An OTA won't replace the secuflag. I have no idea where this nonsense is coming from but HTC is not going to switch the [MENTION=983917]secu[/MENTION]flag. Just wait for another exploit if you're on 1.54

Sent from my One true love.
[One (M7) Original Android Development] pet4a:
i managed to successfully run ./revone -u.

when checked the bootloader screen the tampered sign didn't show.

how can i check if my bootloader is unlocked?

can i install custom recovery only with s-off?
[One (M7) Original Android Development] smartanks:
1.54 Hboot S-off now possible!!!!

Hi Guys just saw this on youtube, i guy was able to s-off his ONE using a "JAVA CARD". Dont know how to contact that person , but i guess we can finally have s-off on 1.54 hboot

Please check the below link:

http://www.youtube.com/watch?v=AVSGqXn4wX0
[One (M7) Original Android Development] haruryu:
Thank you Revone!!!

I changed from T-MOB101 to SuperCID then to HTC__E11 and flashed europe RUU, now i receive OTA's and my hboot says LOCKED and S-ON with no trace or unlocking. only weird thing is, i dont see my CID anymore :P

but it does read it when i type: fastboot read cid
[One (M7) Original Android Development] InflatedTitan:
I have hboot 1.44 coming fresh from the att ruu. Segmentation fault again. I've tried rooted and unrooted... I need to send this phone into warranty so I really want to get it back to say locked. Anyone have any ideas?
[One (M7) Original Android Development] DeSaint2:
Which Ruu did you run?
[One (M7) Original Android Development] InflatedTitan:
The ATT 1.26 ruu.... It's the only one for att.. I have s-off already. I don't know what the heck. I'll try to flash Scott's stock root att odex and try again
[One (M7) Original Android Development] crit71:
Finally got it to work after numerous 'Failed to map memory' messages.....nice one...thanks.

Persistence is a virtue :good:
[One (M7) Original Android Development] KillerBeaver:
Would it be possible to get the jet toolkit http://xdaforums.com/showthread.php?t=1982442 to work for the one, so we can just downgrade Hboot and use the original exploit?
[One (M7) Original Android Development] Theshawty:
I'm pretty sure OTA's could flash the image (whatever it's called) to mmcblk0p3 if HTC wanted that.
[One (M7) Original Android Development] smartanks:
would it be possible to get smething like the misctool from below to work for our phones? we would be able to write the main version of the phone ourselves and flash older RUU and gain S-OFF.

http://xdaforums.com/showthread.php?t=1526316

i tried it on my phone but it failed.
[One (M7) Original Android Development] TechSavvy2:
Did anyone else watch this? How did nobody comment on it?
[One (M7) Original Android Development] Mash23:
Cause there had always been firms that offer you unlocking and s-off. Java Card is mentioned that is nothing as easy or inexpensive as revOne exploit. Keep hopes up but me thinks this won't help us :(
[One (M7) Original Android Development] tiho5:
Make sure while you do it that your screen doesn't go off. If so you'll be OK and not get that error. :)
[One (M7) Original Android Development] donmarkoni:
I concur. :highfive:

When you are S-OFF, HTC don't even need anything special to S-ON you again, cause S-OFF overrides any security check and mmcblk0p3 can probably be flashed with a simple dd command.

That is the main reason for people [highlight]NOT TO TAKE OTA UPDATES WHILE S-OFF[/highlight]

EDIT:

by request, let me rephrase that: [highlight]NEVER TAKE OTA EVER[/highlight] :D
[One (M7) Original Android Development] runganwt:
Re-phrase NEVER TAKE OTA EVER.

Custom update always come out before OTA. :D
[One (M7) Original Android Development] donmarkoni:
Done! ;) Cheers!
[One (M7) Original Android Development] runganwt:
Thank you...:good: :D
[One (M7) Original Android Development] zipsnet:
all this does is change your main version.

You coull pull your mmcblk0p19 and user a hex editor to change your version to 1.00.000

---------- Post added at 10:46 AM ---------- Previous post was at 10:10 AM ----------

Turkish guy, sell the java card for around $1000 , wanna buy it ? ;)
[One (M7) Original Android Development] runganwt:
With that, Can it be used to edit CID on S-on device?

Sent from my HTC One
[One (M7) Original Android Development] grim489:
It didn't work to change my CID. It shows as supercid but any command to get CID shows tmobile still. It is the backup CID in mmcblk0p19. I think the CID is stored in mmcblk0p4.
[One (M7) Original Android Development] tiho5:
did you reboot bootloader?
[One (M7) Original Android Development] grim489:
Yes. It doesnt change the real CID IF you alter p19, the actual CID is in p4 I'm pretty sure. The change sticks but doesn't mean anything if that makes sense. Multiple Rom flashes and it stays but CID better and getprop ro.cid return T-MOB010
[One (M7) Original Android Development] iElvis:
Old tools like this have usually been patched on newer devices. This won't work because when you flash the RUU, it checks hboot version, which is write-protected.
[One (M7) Original Android Development] RuckusDecay:
Those who try always find succeeded, you will find nay sayers on here. There's always steps or procedures you have to follow but like always it's up to you to figure it out.
[One (M7) Original Android Development] TabascoJoe:
Tried MiscTool, no go as well:

255|root@android:/data/local/tmp # ./misctool w 1.00.000.0

./misctool w 1.00.000.0

=== misctool v1.0

=== Read/Write HTC Main Version

=== (c)2012 Getitnowmarketing Inc

Error opening misc partition... must be run as root

Error opening misc partition... must be run as root
[One (M7) Original Android Development] russel5:
I try MiscTool, change main ver to 1.00.000.0, but when i run RUU it fails on hboot version check
[One (M7) Original Android Development] succe:
on segmentation fault error

Looks like i cannot move from there

Hboot 1.44

HD Revolution 13

did the root as suggest on some post but stack here
[One (M7) Original Android Development] PillowMetal:
I'm afraid I have to side with [MENTION=3854041]Indirect[/MENTION] on this one. Both he and I have documented why this will probably never happen, but even if it could happen, it can be spotted with a simple examination of the OTA firmware.zip and updater_script.

The partition name for mmcblk0p3 is pg1fs, but I have yet to see what the .img file name is in rebootRUU or bootloader flash mode, because it has simply never happened through an OTA in the years that people have been warning about this. Plenty of people bork themselves by taking an OTA while S-ON that updates hboot and prevents them from getting S-OFF, but I have never seen the converse; taking an OTA while S-OFF that makes them S-ON.

So I would like to re-re-phrase the warning "never take an OTA ever" to "never take an OTA ever, unless you know what you are doing". I will continue to logcat the OTA url and download it, inspect what images are being flashed from it, read the code in the updater-script, and flash away from stock recovery. I'll get back to you if I ever get automatic S-ON, and invite anyone to please do the same.
[One (M7) Original Android Development] donmarkoni:
You said it yourself, "probably". ;) Of course it can be spotted, you know how, I know how, he knows how, but many people don't. Also, they don't read, don't learn and don't even think. Hell, many that think do not think logically. :eek:

Warning should not be rephrased, cause many people are over-confident and many think that they know what are they doing. I have seen very few that said "I'm not doing that, it's over my head"

Cheers! :)
[One (M7) Original Android Development] Indirect:
Accidently thanked you. Actually want to tell you that HTC won't replace the flag because A it will brick some devices and B it will also remove their test devices s-off flag which will make it kind of pointless as a test device. I can say confidently it will never happen. If it does, I'll pay everyone that says otherwise 5 dollars.

Sent from my One true love.
[One (M7) Original Android Development] TechSavvy2:
Well in that case......OTHERWISE.... ;);)
[One (M7) Original Android Development] donmarkoni:
No worries. Just remember to remove it when you are at PC/Mac.

I get your point and it stands firmly. Never intended to make an argument of this. :) But as a paranoid I am, I would always be on a safe side. I've done my share of sh1t and never regretted cause I took precautions. ;)

So, the moral of this story is: noobs should stay scared, until they are noobs no more. :laugh:

Cheers mate! :highfive:

Oh, and BTW... OTHERWISE! Now give me my five bucks. ;)
[One (M7) Original Android Development] iElvis:
^^ This

An OTA s-off would result in a lot of bricks and consequent warranty returns. The hassle of dealing with that would likely far exceed the hassle of dealing with people who accidentally brick after going s-off.
[One (M7) Original Android Development] TechSavvy2:
Lol, does it come with lube? ;)
[One (M7) Original Android Development] :
Sure, as long as he can refill it.
[One (M7) Original Android Development] reservin:
Just quick question. I used revone to unlock bootloader and s-off with 4.1.2

Now I flashed stock 4.2.2 and stock recovery. Only thing left is s-on and lock bootloader and I have 1.54 hboot.

I need this HTC One get repaired at service center. Is there way to s-on and lock bootloader for 1.54 hboot?

Thanks..
[One (M7) Original Android Development] godutch:
leave it s-off but lock the bootloader, they will never notice, besides if they do s-off devices are shipped sometimes too. Anyway I sent mine of with to the repair center s-off but locked with hboot 1.44 and 1.29.401.12 and got it back with 2.24.401.1 and hboot 1.54 but still s-off and a repair done completely under warranty
[One (M7) Original Android Development] reservin:
I tried ./revone -s 3 -l but it says segmentation fault <core dumped> and I rebooted into bootloader still shows unlocked.
[One (M7) Original Android Development] AlbertoSONIC:
Try fastboot oem writesecureflag 3

A little question: can i S-OFF and lock bootloader at the same time? Typing ./revone -s 0 -l. I will get bootloop since i'm on custom rom, recovery and kernel?
[One (M7) Original Android Development] DeSaint2:
Do /revone -l command to lock bootloader. All these instructions are in the op. I wouldn't s-on. Just make sure it's all stock and lock the bootloader. No reason to go s-on
[One (M7) Original Android Development] reservin:
I tried ./revone -l as well but still segmentation fault<core dumped>

maybe I cant even relock with hboot 1.54..
[One (M7) Original Android Development] AlbertoSONIC:
I need to send my phone in assistance... Another little question: to flash RUU i need to be in Fastboot USB or Power Off or with Android booted or in Bootloader?
[One (M7) Original Android Development] DeSaint2:
Never done a Ruu but I believe you will be in fastboot with either the exe or just the Ruu file. If you use the exe just go into fastboot and run it. If that doesn't work try Ruu mode.

---------- Post added at 11:29 AM ---------- Previous post was at 11:27 AM ----------

Did you try while in root mode? It is known and well documented on this thread that revone after s-off is still sketchy at best on 1.54
[One (M7) Original Android Development] reservin:
What do you mean by root mode? Also do you mean that s-on is not working on 1.54 right?
[One (M7) Original Android Development] BenPope:
fastboot oem lock

Or

su

. /revone -l
[One (M7) Original Android Development] DeSaint2:
From terminal did you run su?
[One (M7) Original Android Development] reservin:
I was doing it from computer. Also my phone runs pure stock 4.2.2 with stock recovery, so I do not have superuser..
[One (M7) Original Android Development] Sloth:
You don't need superuser to run revone.

After you type adb shell

Type su