yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] daleski75:
You could do a nandroid backup, downgrade to 4.1.2, gain s-off and then restore your nandroid backup.

It looks like revone does not like 4.2.2 (2.24.x.x base) and refuses to work full stop with hboot 1.54
[One (M7) Original Android Development] broffy:
Can you tell me if I can do a nand back up to change my hboot I was 1.54 n downgraded to 1.44 to s- off I was but I mistake and s- on now no command don't work
[One (M7) Original Android Development] daleski75:
Are you running 4.2.2 (2.24.x base) with s-on and hboot 1.44??
[One (M7) Original Android Development] broffy:
Yes I am right now at this moment
[One (M7) Original Android Development] daleski75:
Are you getting segmentation faults when running revone -u or it runs and does not work?
[One (M7) Original Android Development] broffy:
It runs but don't work I am still able to change my cid to anything

---------- Post added at 03:40 PM ---------- Previous post was at 03:33 PM ----------

It runs but don't work I am still able to change my cid to anything I mean all the command say success but nothing happens
[One (M7) Original Android Development] BB88:
Got S-OFF on my first try. Thanks!
[One (M7) Original Android Development] Gerton:
I have hboot 1.54 s-off,

How my phone has to go back for warrenty repair, is it possible to use revone to s-on hboot 1.54?
[One (M7) Original Android Development] gee2012:
Nope,you have to relock the bootloader in fastboot ( fastboot oem lock) but it will say RELOCKED and possibly TAMPERED. Then flash a 4.1.2 RUU in fastboot and use revone again. That`s all you can do atm.
[One (M7) Original Android Development] tiho5:
No, but you can downgrade and flash older firmware with hboot 1.44

That's where revone will work again and you can use it to S-Off and lock the bootloader.
[One (M7) Original Android Development] Gerton:
If it says relocked, i also could do nothing. Its the same...
[One (M7) Original Android Development] gee2012:
Lock the BL, flash a 4.1.2 RUU and use revone afterwards to remove the relocked and tampered sign and go S-On.
[One (M7) Original Android Development] rwilco12:
I have just finished cleaning up this thread.

It is obvious to me that some of us have not read the XDA Forum Rules or have conveniently forgotten them. So let me put up a few reminders here.

Further failure to comply with these rules will result in additional disciplinary action being taken.

Let's all remember this is a public forum of people trying to help each other.

Thank you,

Rwilco12
[One (M7) Original Android Development] broffy:
When I do u is give me and error yes
[One (M7) Original Android Development] FitAmp:
Wut

When you do who?!
[One (M7) Original Android Development] maverick1103:
Ok so this is kinda on topic, but it doesn't relate to the HTC One but the HTC One X, but the reason why I wanted to share is it's regarding warranty issues when phones have been s-off'd etc.

I work at Carphone Warehouse and the other day a customers phone came back to store from repair where HTC sent the phone back un-repaired, they put in the description that it had been tampered with (s-off) so said the warranty was void. Now the customer said he new nothing about s-off etc(not sure if he was simply playing dumb) but the phone wasn't turning on so I couldn't check the BL, we sent it back for a 2nd check so I will keep an eye on it.

Now I got my phone from my Carphone and I have s-off'd my One and I assume if I get a fault with mine and I cannot get it on to get it back to stock I will have the same problem, so I will end up claiming on my insurance, but I'm mainly intrigued that HTC have found out if it was S-off if it didn't turn on...they must check HTC Dev I can only imagine?

Has anyone else successfully sent their phone back and got it repaired?

Again sorry if it's slightly off topic.
[One (M7) Original Android Development] gee2012:
If you are S-Off you can lock the bootloader and downgrade from 4.2.2 to 4.1.2 RUU and you get S-On again and return to full stock without any message (RELOCKED or TAMPERED or S-Off) in the bootloader. See the OP for how to.
[One (M7) Original Android Development] maverick1103:
Yeah I know that, my worry is if the screen failed or something that prevented it booting up and then I sent it back more than likely HTC would refuse my warranty as they would find out it's been S-Off'd....obviously if I can revert back to stock I will and I will be fine.
[One (M7) Original Android Development] gee2012:
Can`t you get into fastboot mode? If yes, type fastboot oem lock. Reboot bootloader and flash a 4.1.2 WWE or Euro RUU in fastboot mode. Afterwards use revone to remove all the messages. BTW S-Off itself isn`t a reason to deny warranty.
[One (M7) Original Android Development] maverick1103:
It's not for me mate, I'm hypothetically thinking if I can't get into the BL.
[One (M7) Original Android Development] gee2012:
Do you have the correct Hboot? Just look in bootloader if you can and type in cmd: fastboot getvar all. If you have the Hboot 1.44.000 you can flash a RUU even without S-Off.
[One (M7) Original Android Development] Black-FR:
The best is, that you first flash the right RUU for your One.

After that, you could use revone to lock your Bootloader and to remove tamperd.

At last step you can go back to s-on again.

But be advised, don't relock or lock your Bootloader, while you are at hboot 1.54.

And also don't got to s-on, while you are at hboot 1.54.

Make sure, that you are on hboot 1.44.

Gesendet von meinem HTC One mit Tapatalk 4 Beta
[One (M7) Original Android Development] gee2012:
You have to lock the bootloader to be able to flash a RUU. Just don`t go S-On.
[One (M7) Original Android Development] Black-FR:
Thats wrong.

With S-OFF you could flash a RUU, while the Bootloader is unlocked.

There is no need to lock the Bootloader for flashing anything, while you are S-OFF.

Gesendet von meinem HTC One mit Tapatalk 4 Beta
[One (M7) Original Android Development] gee2012:
Are you sure? Didn`t know that :D

Yup, you`re right.
[One (M7) Original Android Development] Black-FR:
Yes, I'm sure about it.

Gesendet von meinem HTC One mit Tapatalk 4 Beta
[One (M7) Original Android Development] maverick1103:
I was hypothetically thinking, after experiencing that One X coming back un-repaired...I know what to do if I have to send mine off.
[One (M7) Original Android Development] maxal:
I have done it and it worked just fine for me.
[One (M7) Original Android Development] iElvis:
The "must lock before RUU" restriction is one of the many security checks that going s-off turns off.
[One (M7) Original Android Development] tim.waitt:
Revone for hboot 1.54

Please, please, please work out how to s-off the new hboot that gets updated with the 4.2.2 update. I'm desperate to get back to official stock:mad:
[One (M7) Original Android Development] leon sprouse:
Should i try it?

It has been a few weeks since I read about Revone and installed ADB on my computer. Here is my question. I have been waiting for a "one click" unlock/root/s-off and am getting antsy wanting to root my HTC One and install a custom rom. I am not entirely sure if the ADB is installed correctly and am afraid I could damage my phone trying to install Revone using ADB. What would happen if ADB is not installed correctly? Would it just not install Revone or not make Revone work? Or what I fear would this damage my phone by using ADB without any real knowledge of what I am doing ?
[One (M7) Original Android Development] Sloth:
If adb is not installed correctly revone won't work also make sure you have the latest drivers installed

Sent from? :p
[One (M7) Original Android Development] iElvis:
If you are this nervous and lacking in confidence, you should not s-off your phone.

Going s-off carries risks and is only for people who understand what it means and are able to mod their phones without getting into trouble. Doing it removes important safety checks and allows you to do things that can seriously mess up your phone if you don't know what you're doing.

The reason there are no one-click s-off solutions is that people who need one-click solutions shouldn't go s-off. Start with rooting--manually--and get comfortable with the process before you think about s-off. It's really not that hard and this is knowledge you need if you're modding your phone.

Depend on one-click tools and sooner or later you will get into trouble you have no idea how to get out of.
[One (M7) Original Android Development] leon sprouse:
Thank you for your quick reply. the only reason I would want s-off is that I read that without it you cannot do a nandroid backup and restore. This is something I used many times with my EVO4G after installing something that "froze" the phone. If I install a recovery app while having s-on will I be able to backup and restore my phone ?
[One (M7) Original Android Development] iElvis:
Whoever told you that is wrong. Be careful what you read; there is a lot of bad information flying around because of the number of noobs who have gone s-off.

All you need for a nandroid is root and unlock. S-off affects deeper system functions; it has nothing to do with backups.
[One (M7) Original Android Development] rajackar:
Since we are on the topic of s-off and backing up.

Do I understand correctly that after going s-off I will be able to install a custom recovery and thus bypassing htcdev unlock and the complete wipe that will do?
[One (M7) Original Android Development] daleski75:
Yes you can unlock without wiping your phone and bypassing htcdev
[One (M7) Original Android Development] rajackar:
Thanks! That's exactly what I wanted to hear. On a side not, is the revone method compatible with hboot above 1.44?
[One (M7) Original Android Development] daleski75:
Revone is only fully working and tested with Android 4.1.2 and hboot 1.44 also revone does NOT work whatsoever with hboot 1.54 so stick to 1.44 and you should have zero problems.
[One (M7) Original Android Development] rajackar:
Thanks again!

I've already updated to 4.2.2 with hboot 1.54 so I'll just wait a while then.
[One (M7) Original Android Development] daleski75:
If you have s-off still you can downgrade the hboot to 1.44.
[One (M7) Original Android Development] rajackar:
Thanks, Since I needed revone to get s-off downgrading is not an option for me right now.
[One (M7) Original Android Development] seanicca:
I got s-off then for some reason but not sure why locked my BL. I updated to 1.54 so obviously revone won't work but could I downgrade using ruu and basically start again?
[One (M7) Original Android Development] tiho5:
You can as long you are s-off.

Flash hboot 1.44 and there it would work.

No need to lock your bootloader with s-off as all operations are OK with unlocked BL.
[One (M7) Original Android Development] seanicca:
Cheers.

I've spent the last few days reading different threads and some say bootloader should be locked some say not so thought I'd better ask first and double check before doing anything.
[One (M7) Original Android Development] Gerton:
Could u point me to the RUU's?
[One (M7) Original Android Development] angusc:
Her you go

http://xdaforums.com/showthread.php?p=39588860

Sent with desire from My One
[One (M7) Original Android Development] Black-FR:
Here is the Link, for the RUU topic:

http://xdaforums.com/showthread.php?p=39243968

Gesendet von meinem HTC One mit Tapatalk 4 Beta
[One (M7) Original Android Development] erider:
today i reverted to stock and locked boot loader and flipped back to S-on in order to grab the new tmo update (great signal upgrade BTW) but now when i try to run revone to get S-off i'm getting Segmentation Fault <core dumped> running either the -P or the -s 0 -u commands. I'm still on HBOOT 1.44 and the tmobile CID and stock 4.1.2. anyone have any idea what this may be? or perhaps there's another route i need to take to redo s-off and unlock because i already ran revone once? is perhaps the new build number causing this? (1.27.531.11 CL21101)

any help is much appreciated,

Thanks,

Erider
[One (M7) Original Android Development] daleski75:
That is interesting can you try running su first and then try it again? Also do a fastboot getvar all and post the output here
[One (M7) Original Android Development] erider:
\mini-sdk>fastboot getvar all

< waiting for device >

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.44.0000

(bootloader) version-baseband: 4A.17.3250.20

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 1.27.531.11

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno: REMOVED

(bootloader) imei: REMOVED

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0713000

(bootloader) cidnum: T-MOB010

(bootloader) battery-status: good

(bootloader) battery-voltage: 4329mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

getvar:all FAILED (status read failed (Too many links))

finished. total time: 0.045s

SU returns not found

i was thinking of running the RUU but dont want to lose 1.44 (not sure if it will upgrade it)
[One (M7) Original Android Development] daleski75:
Have you tried revone-wlj out of curiosity?
[One (M7) Original Android Development] erider:
no. should i try that?
[One (M7) Original Android Development] daleski75:
Sometimes that one can work and if not it won't do any harm at all
[One (M7) Original Android Development] erider:
same error with the wlj version :-/
[One (M7) Original Android Development] daleski75:
I think you need to root your phone run su first and then try and see if it works.
[One (M7) Original Android Development] iElvis:
The T-Mo update may have patched some things. It probably closed the motochopper root method revone relies on. So you need to root first.
[One (M7) Original Android Development] erider:
and just to clarify, the only root i can use now would be htc dev? hope that dont come across as a stupid question. lol
[One (M7) Original Android Development] iElvis:
You can always use that. It's not been closed as it's an official method. But it will let HTC know that you unlocked, and some people don't want that.
[One (M7) Original Android Development] greatmagician:
after I apply this command ./revone -P

i got error :

revone failed (error code = -6)

what I can do ..?

Im using " Android Revolution HD 12.1 | 4.2.2 " Rom
[One (M7) Original Android Development] mysdavey:
Thanks a lot for this. Used it successfully to get S-OFF and remove the tampered-flag. Worked like a charm!
[One (M7) Original Android Development] Gerton:
What is your hboot version?

If its 1.44 how many times did u try? For mine it Worked after 20.

If its 1.54 stop trying it isnt gonna work.
[One (M7) Original Android Development] boroboy69r:
Im on on the modded 1.54 hboot with red warning gone, am i right to say to go back to stock i need to flash unmodded 1.54 hboot then what do i do s-on lock bootloader and flash ruu for cid htc__001

Sent from my Renovated Faux powered 1
[One (M7) Original Android Development] greatmagician:
My hboot version is ( 1.54.0000 ) :rolleyes:

So there is no solution ؟
[One (M7) Original Android Development] Gerton:
Look a few posts back maybe 2 pages, there it is explained what to do.

S-on is the last thing to do!

---------- Post added at 10:31 PM ---------- Previous post was at 10:31 PM ----------

Nope its not working (yet) for 1.54
[One (M7) Original Android Development] formula84:
If I have TMobile Device with SOFF already (done before 1.54), and flash an official RUU.exe will I lose SOFF?
[One (M7) Original Android Development] iElvis:
No.

Only two known ways to revert s-off: Manually changing the setting (via fastboot writesecureflag or revone), or by copying over the partition containing the secureflag from an s-on phone (not easy, but I know of someone who did).
[One (M7) Original Android Development] boroboy69r:
Thanks seen the post just want to double check i run ruu then lock bootloader then s-on, what are the full commands for the two steps do i type

* ./revone -l to lock bootloader

* fastboot oem writesecureflag 3 to s-on

all this with adb with the revone file in my adb folder dont want to mess my phone up going back to stock for factory defect.

Sent from my Renovated Faux powered 1
[One (M7) Original Android Development] leon sprouse:
error?

after working on this I think I have it down. But I think I may be getting an error.is this normal? After #4 I get this on the command window "Gaining root access (thanks to Dan's motochopper).....Segmentation fault (core dumped) this same message comes up on /#5 also.
[One (M7) Original Android Development] :
hboot 1.54 revone

hello ,same problem ,you have 1.54 hboot ? is that it ? i think we have to wait for revone update
[One (M7) Original Android Development] leon sprouse:
NO I have hboot 1.44
[One (M7) Original Android Development] Sloth:
Try running it from your PC
[One (M7) Original Android Development] leon sprouse:
what do you mean try running what from my computer. if you mean a command window it wont recognize adb unless you open it in the adb program
[One (M7) Original Android Development] Sloth:
Open a command window from your android-sdk/platform-tools folder

Also copy the revone file to that folder
[One (M7) Original Android Development] guy4jesuschrist:
Pretty pissed at HTC right now, as my phone was just forced to update, thereby preventing me from S-offing my phone. That is, at least until a new solution to S-off hboot 1.54 is released. Had planned to S-Off my phone when I got home this evening, but the final 8 hour postpone time limit was reached. :/

EDIT: Correction...I'm pissed at AT&T for forcing the update upon me.
[One (M7) Original Android Development] iElvis:
AT&T already pushed out the 4.2.2 update? Are you sure you're on 1.54?
[One (M7) Original Android Development] guy4jesuschrist:
My bad, I jumped the gun based on some forum reading that I had done yesterday, that made me believe the most recent non 4.2.2 update that AT&T pushed out. Just checked, still on 1.44, thankfully! For anyone else who read my last post, sorry about the confusion. Should have checked first, especially based on other's experiences on here in not researching enough.
[One (M7) Original Android Development] leon sprouse:
did this got same segmentation fault
[One (M7) Original Android Development] Sloth:
hmmm IDK then sorry :(

I did mine on the PC it took about 3 minutes
[One (M7) Original Android Development] jorceshaman:
Instructions weren't clear enough, got my **** caught in a ceiling fan.
[One (M7) Original Android Development] leon sprouse:
my phone is still locked . Could I maybe try using revone to unlock the phone first then try the -P and then s-off? ......... never mind I tried this and got the same segmentation fault
[One (M7) Original Android Development] Sloth:
Hmmm I believe unlocking is part of the process I have seen folks post that they were able to get revone to work even though they were locked
[One (M7) Original Android Development] comnam90:
Hi all,

Finally got round to doing this and having a small issue.

Running hboot 1.44 before you ask, completely stock (no root).

Now I ran 'revone -P' and got a success and rebooted.

Next ran 'revone -s 0 -u' and again got success and rebooted (this time to bootloader)

However, in bootloader, i notice at the top it still says locked and s-on?

I turned the phone off and left it for a few minutes then started the whole process again from scratch but got the same results :( success but no real change to s-off

Model is an m7_ul - 714000
[One (M7) Original Android Development] leon sprouse:
Segmentation Fault

After getting this every time I try to use Revone at install #4 and #5 I tried reading to find a fix. there are about 10 people ( I found) who experienced this 'Fault" but there is not one reply telling how to get around it and get revone to work. I hope the devs who made this tool will find a fix. If there is someone who experienced this and got Revone to work please post the repair.
[One (M7) Original Android Development] mcg:
revone worked flawlessly the first time I tried to restore S-ON after removing the tamper and unlocked flags... now whenever I do S-ON, it causes the phone to boot up, but then immediately restart, and loop from there.

My steps:

Flash TWRP stock image, install SuperSU

Flash Rogers stock recovery image

Boot up, uncheck fast boot, push revone to phone, chmod, revone P, reboot, revone -l -t etc. etc.

Reboot into bootloader, check for flags... sometimes I have to restart revone process to get the tamper flag off

Once all done, fastboot oem writesecureflag 3 --> factory reset, reboot, and the phone boots up but then immediately restarts... and so on.

I reboot the phone into bootloader... **TAMPERED** flag returns.

Wondering if it has to do with the root I installed through TWRP onto the stock TWRP image. Funny thing is it worked previously, but now S-ON causes a restart loop. I've just left the phone on S-OFF after removing all the flags (after rebooting the phone and using it into bootloader, the flags remain removed)... the phone starts up as normal, no reboots.
[One (M7) Original Android Development] hotpointdave:
Spot on and well said sir.
[One (M7) Original Android Development] Sneakyghost:
Are you running a modified splash screen? Any other modified partition?

Tampered will go away once root is removed i believe.

Best way: run a RUU while S-OFF. It will reset all images to stock and then you can go S-ON.
[One (M7) Original Android Development] robot1000:
I'm having real trouble getting my HTC ONE to S-ON

I've followed the instructions and after 'locking' it states revone successful, however in the bootloader it still shows as :

M7_UL PVT SHIP S-OFF RH

Any ideas?
[One (M7) Original Android Development] monkeypaws:
error -6

I have been at this all ngiht. tried different methods, even tried doing the no pc method i found on youtube. still nothing

I am thinking its either commands I am not getting right or what? I followed the instructions on this thread. Before though i used the toolbox AIO from the developers thread, to gain unlock bootloader, load TWRP, and flash SU. I was reading that this was okay and I did not need to relock and unroot to gain s-off. I then downloaded the latest? From the OP and placed it in my C:/adb folder

I opened a CM prompt within that window and followed all the steps:

after pushing i do adb shell

then cd /data/local/tmp

chmod 755 revone

su (since i am rooted)

then ./revone -P

I immediately get "revone failed (error code = -)

250:root@android:/data/local/tmp

I am not as advanced with these commands as others are. I have been spoiled for years with samsung devices and easy programs.

Please advce

also my device is a tmobile USA htc one 32gb

bootloader says ***tampered*** // ***unlocked***

S-on

HBoot: 1.44.0000 >>>>I thought that this was okay since i didnt have 1.54

any help would be nice. Ive tried gaining S-ff with the toolbox but when I hit set permissions CMD does nothing,

then when I hit prepare for S-off I get core dumped and nothing.
[One (M7) Original Android Development] Matt:
fastboot oem writesecure flag 3 in fastboot mode
[One (M7) Original Android Development] monkeypaws:
okay so afer it failed i just retyped the command and it said successful. followed the rest, but when checking in bootloader it still says s-on
[One (M7) Original Android Development] BenPope:
Anybody having the success message without success should try rebooting it by holding the power button down, not adb reboot.
[One (M7) Original Android Development] monkeypaws:
okay, there must be something wrong with what ive done. I even tried the commands on my mac and still the same error 6. im stumped. Is soff required to flash roms or flash a different ruu or change CID?
[One (M7) Original Android Development] LorD ClockaN:
Soff is for changing Cid mainly.. And it removes some other restrictions but not really mandatory ones
[One (M7) Original Android Development] nabzilla1990:
after installing the T-mobile .11 ota i can't s-off getting error -6 and error -2