yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] sourcecodepoet:
I had a similar problem when I tried the htcdev.com unlock.

After many times it finally did work.

I think I also did factory reset from the bootloader menu a few times and requested the unlock code more than once.

Keep trying - you may succeed. I can't remember how often I tried, but it was many times.
[One (M7) Original Android Development] Tetsumi06:
Well, after weeks of cajoling I finally convinced my wife to allow me to mess with her phone (its H3G__001 so she had no chance of timely updates.) Even on a completely stock, locked phone it went like a hot knife through butter!

So, all I now need to do is set it to HTC__001, leave it s-off and bootloader unlocked and it will start to receive OTA updates?

Also, will the 4.2.2 OTA factory reset and full wipe her phone or will she barely notice that it happened?

Thanks guys.

----------------------o('_')o----------------------

Sent from an HTC One using xda app and Bulletproof TrickDroid ROM 8.0
[One (M7) Original Android Development] mrrogers1:
You do not want to nor should you EVER accept OTA updates. Flash a stock rooted rom and the accompanying firmware (minus the bad bits that the devs will strip out) after the OTA has been released.
[One (M7) Original Android Development] Tetsumi06:
I never do but my wife only let me touch her phone long enough to get it ready to take OTA. Once it's able to get timely OTA she'll never let me touch it again so I couldn't keep it up-to-date with custom ROMs

----------------------o('_')o----------------------

Sent from an HTC One using xda app and Bulletproof TrickDroid ROM 8.0
[One (M7) Original Android Development] flamechamp:
I am terribly sorry, I just saw your message. It's not often for me to get a PM.

Here's the answer to the questions:

1. after I installed new firmware, if I remember correctly, it was still S-OFF that time but RELOCKED. Then I tried running the revone again from the start to achieve UNLOCKED, but the revone shows error all the time. Then after several reboot attempts suddenly it's S-ON again.

2. I came from the 1.44 HBOOT before having this. I flashed the new firmware and try to use revone without SU several times then use SU several times. I hope it reproduces the same result.

3. modelid: PN0714000

cidnum: HTC_044

hboot: 1.44

I hope this helps. Once again I'm sorry that I jsut saw your message.:(
[One (M7) Original Android Development] BernddasTost:
When locking my bootloader it says LOCKED and S-ON, after rebooting the phone it says TAMPERED LOCKED S-ON.

Removing the TAMPERED flag with revone -t does not effect at all. I'd like to stay S-ON and LOCKED, without the TAMPERED flag.

Is there any possibility for me to remove the flag and stay S-ON and LOCKED?

This may has been asked before, then please link the post or answere although.

Thanks, kind regards.
[One (M7) Original Android Development] Sneakyghost:
No worries. I told HTC already that there was no answer and your case a pretty isolated incident - there were maybe two more if at all. Probably just a random thing.

Mobile post
[One (M7) Original Android Development] angusc:
That's not right. As long as you are S-Off already you can accept the 2.24 OTA updates without fear. I know because I did it and I'm still S-Off. It's when you accept the latest OTA without being S-Off that you get in to problems.

Sent with desire from My One
[One (M7) Original Android Development] mrrogers1:
The safest and smartest way to never, ever have issues is to NEVER TAKE OTA's, period.

People relock (not s-on though many people did that here too....) to take the OTA only to find out that you can't unlock the bootloader with Revone then they have to use HTCDev unlock. It makes no sense, never has, to except an OTA when there are stock rooted versions of the exact same thing you are taking (for no reason) available. There are also firmware packages available to flash without the bootloader update that is what usually screws people.

You may have successfully taken the OTA, but it's not advisable nor logical to take the risks when there is no reason to do so.

If people had of said this, more, MUCH more often here, many people wouldn't have gotten in trouble like they did they'd be happily s-off still. Sure, it's not the end of the world one way or the other but one way is completely safe and the other, is an unnecessary gamble.

Just my 2c and what has been working for years... Do not take OTA and never worry about blocked exploits and issues that come along with OTA's.
[One (M7) Original Android Development] tiho5:
Angusc, true that this is possible, but mate with S-Off your signature verification is off.

So if for instance you have a bad download of your OTA it is still going to be allowed to flash.

This way you might end up with a broken image of some part of the firmware package which could do serious damage.
[One (M7) Original Android Development] Fatelord:
Isn't true for every android in existence with an unlocked bootloader except HTC ?
[One (M7) Original Android Development] kiwiandy:
thanks.. fixed now

I went to the HTC dev website again, got another token, and when i reflashed it it worked!
[One (M7) Original Android Development] Tetsumi06:
Colour me stunned! 8 hours after I set wife's phone to s-off H3G rolled out the 4.2.2 upgrade. That was a narrow escape!

----------------------o('_')o----------------------

Sent from an HTC One using xda app and Bulletproof TrickDroid ROM 8.0
[One (M7) Original Android Development] Spartn:
just an idea

Hello all,

Few days ago, I was playing with HTC ONE again and was able to downgrade to 1.29.401.x by loading 1.29.401.x odexed rom and stock recovery for that version, then I used OTA to get update and it did download the update, after that the device updated to version 2.24.401.x.

I was thinking if there is odexed rom 1.28.401.x and stock recovery for that version, we could try to downgrade to that version and try to use OTA if it does not downgrade the hboot to 1.44. automatically while updating to 1.29.401. as the OTA file which i found includes an hboot, not sure which version it's, but it should be 1.44..

Unfortunately I can't find the odexed rom 1.28.401.x and stock recovery..
[One (M7) Original Android Development] daleski75:
I did have the stock odexed 1.28.401.7 rom and stock recovery for it as well and from my testing the hboot will ALWAYS remain at 1.54 irrespective of what you flash and the OTA will not downgrade the hboot as it's a one way street only without s-off.

Until the dev's give us a new version which works with hboot 1.54 it's a waiting game.
[One (M7) Original Android Development] Gandalf Greyhelm:
Absolutely.

It's a sign how desperate people are to regain either s-off and/or downgrade that @&*^%$ 1.54 hboot that so many well-meant theories are popping up.

Am I right in thinking the only way the hboot can be downgraded ATM if you're s-on is to run the correct RUU for your phones's CID - which must also contain the desired hboot (e.g. 1.44) - if I'm wrong please remonstrate - as I'm not certain as to whether s-off is still required in that instance in order to allow the downgrade?

If I'm right, it's unfortunate that RUU's for the One (especially mine - O2UK :crying:) are almost as rare as as the proverbial excreta from a celluloid based, rider agitated equine.
[One (M7) Original Android Development] daleski75:
If you are on hboot 1.54 and you try to run an older RUU 1.29.x then you will get two errors one for mainver and the other for hboot pre-update which basically means this from the phone "I am not going to let you install this as your firmware version and hboot are older than the version which is installed"

So to summarise if you have s-off you can downgrade firmware and the hboot if you are s-on you cannot downgrade the hboot however you can downgrade the firmware to 1.29.x (with an odexed zip) but your touch screen will not function due to missing drivers and even if you manage to downgrade through an odexed zip revone and moonshine will still refuse to work on hboot 1.54.
[One (M7) Original Android Development] Gandalf Greyhelm:
Thank you - that's a lot clearer now. It also perfectly summarizes why my original nandroid of stock 4.2.1 will install but refuse to respond to touch.
[One (M7) Original Android Development] daleski75:
No worries glad I could help.
[One (M7) Original Android Development] harlenm:
I've run this like a dozen time, I have s-on and locked, but I can't get rid of tampered.

very frustrating

edit, says it works, but doesn't.

C:\android>adb shell

adb server is out of date. killing...

* daemon started successfully *

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

cd data/local/tmp

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

./revone -t

revone v0.2.1

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

revone successful.

shell@android:/data/local/tmp $

C:\android>
[One (M7) Original Android Development] Tetsumi06:
You need to -P first to Prepare the phone, then you -s 0 to get s-off before you can -t

----------------------o('_')o----------------------

Sent from an HTC One using xda app and Bulletproof TrickDroid ROM 8.0
[One (M7) Original Android Development] harlenm:
According to the directions, after I lock the bootloader, I then run it again and - t to remove tampered. Shouldn't have to s off first. I've done it a bunch of times.

Edit, someone told me earlier in the thread that I do not need to s-off first before locking bootloader and removing tampered.

Are you saying that I need to be s-off to do those things, and then s-on after I'm done?
[One (M7) Original Android Development] Spartn:
Just one correction, you're able to downgrade with s on and touch screen will work if you use boot.img of hd12.0 or higher, but it is not proper way
[One (M7) Original Android Development] harlenm:
So, I am now S-off, and I still can't get rid of "tampered".

I'm at a loss at what to try now. The last few times I've gotten the -2 error.
[One (M7) Original Android Development] daleski75:
Down grade hboot???

---------- Post added at 08:45 PM ---------- Previous post was at 08:43 PM ----------

Ahh got ya and yeah that is not the proper way
[One (M7) Original Android Development] Spartn:
no hboot ;) if that would be possible, then many people woule be much more than happy

just rom, you can downgrade to 1.29.401.x and touch will work if you use boot.img of hd12.0 rom

i believe it's possible to downgrade to 1.28.401. if boot of that hd room is used and touch screen will work as i had already downgraded to 1.29... and it was fully working

can you please upload the odexed 1.28.401. and stock recovery of that rom, i would give it a try if ota doesn't make any magic with hboot;)
[One (M7) Original Android Development] daleski75:
Let me see if I can find them as I have probably deleted them by now but if I have not I will PM you the links when uploaded.
[One (M7) Original Android Development] harlenm:
Finally got it to work, yay!!!!!

Thank you very much for this tool!
[One (M7) Original Android Development] tip2tail:
Hi,

First off - I'm not new to HTC, Android or Rooting - not a n00b.

That said, I will put my hads up and I jumped in feet first without reading!

I have HBOOT 1.54 installed and tried to use revone. In su shell I got the -6 error and in standard shell the data error message.

I know this is because of the HBOOT version and I am patiently waiting on this being resolved. My bootloader however now shows ** TAMPERED ** - is there a way to remove this flag with being on HBOOT 1.54?

Thanks,
[One (M7) Original Android Development] laegunum:
In order to get rid of the "tampered" message, you need to run revone. And to run revone, you need hboot 1.44. So no, you can't get rid of the message until an updated revone is available.
[One (M7) Original Android Development] phekno:
Tried running revone -P on my HBOOT 1.44 TMOUS phone a couple times, all the time getting error code = -6, so I decided to reboot. Now the phone won't come on at all, and doesn't appear to charge. I did a little digging and found references to QHSUSB_DLOAD, so I checked and according to Windows I'm in that mode. Is that something that can be fixed with the unlimited.io tool, or is this something else entirely?

Edit: I see there is another process here. At this point, I'm not sure what I should do.
[One (M7) Original Android Development] Sloth:
That usually indicates you're bricked :(

Sent from? :p
[One (M7) Original Android Development] phekno:
Oh my.

So, none of the "tools" out there to "unbrick" will work in this case? If not, should I just take it in to T-Mo (obviously I broke it, but...)?
[One (M7) Original Android Development] Sloth:
Go on their IRC channel and see if they can help

Sent from? :p
[One (M7) Original Android Development] phekno:
Thanks.

I'm in there now. No one is responding. I'm not expecting immediate support, but if possible, I'd like to figure this out before my battery dies. I'll just wait and see.
[One (M7) Original Android Development] manups4e:
hi :) is there any update for s-off on 1.54 hboot?
[One (M7) Original Android Development] daleski75:
No
[One (M7) Original Android Development] mrrogers1:
HELL....
[One (M7) Original Android Development] Spartn:
try to pull out the sim card if it's inserted and then hold power button plus volume down together more than 30 secs, if nothing happens, then try to retouch these 2 buttons and hold it again if nothing happens, then you can try to hold just power button for more than 30 secs.... not sure if it helps

hopefully it will help

i thought there is no way to brick HTC device, or it's really hard even if you want to do that -was mentioned somewhere on xda...
[One (M7) Original Android Development] manups4e:
ahahahahah thanks =P
[One (M7) Original Android Development] saeedmashref:
Ihave HTC one 801n ,s-off , super Cid ,unlo
[One (M7) Original Android Development] daleski75:
Well done :)
[One (M7) Original Android Development] saeedmashref:
I have HTC one 801n , s _off , supercid ,unlocked , stock rom 2.29.401.1 , HBoot 1.54 , stock recovery and I want to have root ! How I do it to get perfect root ?
[One (M7) Original Android Development] donmarkoni:
Yes, it's very hard to brick while being S-ON, although you can do it while upgrading firmware, manually or via OTA update, actually if you disrupt HBOOT flashing. Someone correct me if I'm wrong.

But, with S-OFF it's another story. It's a piece of cake, gingerbread, ice cream sandwich, jelly bean, or another sweet... ;)
[One (M7) Original Android Development] DeSaint2:
Put it on the charger and let it sit for a little while. Then put it under a bright light(make sure sensors aren't covered) and hold the power button for 15-30 seconds.
[One (M7) Original Android Development] stevedebi:
It is pretty much impossible to brick an HTC One unless it is S-Off, which is what he was trying to do. It is unknown how much of it worked. But he is probably OK.
[One (M7) Original Android Development] mrrogers1:
What? :what:
[One (M7) Original Android Development] phekno:
Thanks everyone for your input. The guys in the Revolutionary IRC basically said that it probably wasn't their fault, but couldn't really figure out why exactly it did what it did. Unfortunately, I was unable to get the phone back up and running. I took it in to a T-Mo store (I had only had the phone for about 10 days) and after doing pretty much everything everyone had recommended (holding power, holding power + volume, charging it, etc.) they ended up doing a warranty exchange. They would have done a full exchange, but apparently since I had thrown the box away, they couldn't do that, so I'm phoneless and feeling pretty naked until tomorrow night.

Again, this wasn't caused by revone, and so far, no one else can figure out what happened given the circumstances.
[One (M7) Original Android Development] dozybolox13:
Just for anyone looking to do the same as me that is on T-Mobile US and is trying to revert from the GPe rom to Stock T-Mobile sense, if you run into issues with revone after running the RUU (I got segmentation fault), flash a custom recovery and then run (while in the custom recovery)

./revone -s 0 -l

adb reboot bootloader

fastboot oem writesecureflag 3

and then rerun the RUU
[One (M7) Original Android Development] gabriel925fm:
I have a tmobile htc one on 1.44. It has been dev unlock. I have tried 5 different rooms. Did all the s-off steps manually on a mac and pc and also use the all in one tool kit and i keep getting error codes.

iMac:android gabrielcastro$ ./adb-mac push revone /data/local/tmp

4569 KB/s (648208 bytes in 0.138s)

iMac:android gabrielcastro$ ./adb-mac shell

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

root@android:/data/local/tmp # chmod 755 revone

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

revone v0.2.1

revone failed (error code = -6)

any thoughts?
[One (M7) Original Android Development] DeSaint2:
Are you on the latest update rolled out by t-mo? If so that is your problem. Something was patched in that hboot that coincides with a patch in the 1.54 hboot that stops revone from working.
[One (M7) Original Android Development] iriijo:
Only unlock

My question is if I can only unlock the bootloader without s-off? :)

Br

Iriijo
[One (M7) Original Android Development] Sloth:
Yes www.htcdev.com
[One (M7) Original Android Development] tiho5:
If you mean if it is possible to do this with revone, yes it's possible to only unlock without S-Off'ing or anything else. Just use the normal procedure and use the command -u.

Just remember you have to be on hboot 1.44 for revone to work.
[One (M7) Original Android Development] iriijo:
Ok thanks :)

First I need to do is:

./revone -p

than

./revone -u?

br

iriijo
[One (M7) Original Android Development] tiho5:
Correct
[One (M7) Original Android Development] MindlessLeadership:
They patched the root exploit that revone is using. So I imagine if you unlock your bootloader via HTCDev, root and then run run revone, you might have success.
[One (M7) Original Android Development] iriijo:
Sorry for the many questions i have hboot 1.44 now and android 4.1 the question is when i make a ota update to 4.2 now will my hboot updated to a newer Version?

Br

Iriijo
[One (M7) Original Android Development] Ivixmax:
Something new to make renove works on hboot 1.54 ?
[One (M7) Original Android Development] tiho5:
It will be updated. But if you S-Off now you're going to keep it through the update.

Revone doesn't work with hboot 1.55, so I advise you to S-Off now, while you're still on 1.44
[One (M7) Original Android Development] iriijo:
Bootloader must be locked for ota?
[One (M7) Original Android Development] mj084:
nope
[One (M7) Original Android Development] tiho5:
You must have stock recovery too.

BUT I strongly advise you not to take OTAs with S-Off:

http://xdaforums.com/showpost.php?p=44049473&postcount=4221

http://xdaforums.com/showpost.php?p=43683593&postcount=3871

Better be completely custom or full stock, mate.
[One (M7) Original Android Development] mj084:
;)

no problems with s-off and OTA to 4.2.2

now on hboot 1.54 and still s-off:D

no risk no fun
[One (M7) Original Android Development] gabriel925fm:
Do i need to have stock recovery for revone to work?
[One (M7) Original Android Development] tiho5:
No. It doesn't matter

It is for the OTA :)
[One (M7) Original Android Development] iriijo:
Thanks I have unlocked bootloader and s-off now :) Will do the ota now ;D

br

iriijo
[One (M7) Original Android Development] vengadorhq:
question

It is necesary to run:

6. Instruct revone to grant you S-OFF and unlock status by running the command: ./revone -s 0 -u

with flag -u if the bootloader is already unlocked with the htcdev method?
[One (M7) Original Android Development] arcs_porwal:
is there any hope to work on 4.2.2

mat i m struck at 4.2.2 1.54 hboot..... is there any hope to get it s off... plzzz help

i updated with s off

but my freind executed writesecureflag 3... plzzz reply
[One (M7) Original Android Development] C-4Nati:
Constantly getting this error while attempting the first part of the process. http://imgur.com/xwbNDe1.jpg
[One (M7) Original Android Development] kdan8888:
+1 :crying:
[One (M7) Original Android Development] NTree45:
i have been trying to get this to work for me

everytime i get to "4. Prepare to gain S-OFF by running the command: ./revone -P"

it reboots my phone with no changes at all

i do have a T-mobile One, just got it on saturday(July 27th) and like an idiot i did the ota update hoping it was the 4.2 update

rooted and romed it the same day too

also, what is my firmware version?

M7-UL PVT SHIP S-ON RH

HBOOT-1.44.0000

RADIO-4A.17.3250.20

OpenDSP-v31.120.274.0617

eMMC-boot

Jun 21 2013,20:19:45:-1
[One (M7) Original Android Development] skulldreamz:
S-off your phone if that is the correct info above. Hboot 1.44.000- means you can s-off

Your firmware is listed in settings under about phone. Like 2.17 or 2.19 or 2.24 or may start w/ a 1.xx
[One (M7) Original Android Development] NTree45:
so i switched to TrickDroid and now instead of a reboot i get an revone failed (error code = -6)

also, i tried the "chmod root:root revone" trick and that says bad mode
[One (M7) Original Android Development] skulldreamz:
There's a bunch of you tube videos floating around that will probably answer people's questions easier then we can explain sometimes. There a bunch showing the revone s-off method. You don't even need a computer, it's easier to do it in terminal emulator for some people and you won't get the errors if you dd it.

DD=data disk (or data to disk)
[One (M7) Original Android Development] sumpf2:
also error -6

hboot 1.54

version 2.24 (stock 4.2.2 ota)

cid htc__102

device is rooted and unlocked...
[One (M7) Original Android Development] Sloth:
won't work on hboot 1.54
[One (M7) Original Android Development] uthmani:
I have just updated my firmware to 2.24 using the instructions in the following thread.. http://xdaforums.com/showthread.php?t=2182823

Now that my phone is 'RELOCKED', how do I unlock again and install custom recovery? I have tried repeating the revone steps that I used originally, but I keep getting a segmentation fault.
[One (M7) Original Android Development] scifitrekkie:
You may have to use the HTC dev unlock.bin code to unlock bootloader then once unlocked you can then flash back a custom recovery.

If you were s-off prioir to 4.2 upgarde you should be able to remove tampered flag that you will get when you install custom recovery.
[One (M7) Original Android Development] erklat:
BAM, *UNLOCKED*

Combined this with the instructions from the first post, 7-8 attempts and it worked. Hope some straightforward solution will emerge like we had on HTC Desire for the less profficient users.

Many thanks.
[One (M7) Original Android Development] Tetsumi06:
Easier? This was one of the most painless s-off I've experienced. Mine was htc__001 and wife was h3g__001 Managed to s-off hers a few hours before h3g got the 4.2.2 update.

----------------------o('_')o----------------------

Sent from an HTC One using xda app and Bulletproof TrickDroid ROM 8.0
[One (M7) Original Android Development] erklat:
The fact that most users give a couple of tries before they succeed I think speaks for itself how straightforward it is.
[One (M7) Original Android Development] Sloth:
Took me less then 5 minutes the first day it came out :D
[One (M7) Original Android Development] phillipm:
I'm using the guide and get the following error message...

Segmentation fault (core dumped)

Help :)
[One (M7) Original Android Development] leon sprouse:
If you had read all the posts about the segmentation fault (core dumped) you would know there is NO solution for this. For you , me , and others who get this "fault" there is no help. Bottom line is Revone wont work for us. I'm hoping when the regular version is posted this will be fixed.
[One (M7) Original Android Development] tiho5:
I think that actually some reported this for this segmentation fault error:

Go back to a 4.1.2 rom and it would work

(Provided you are on hboot 1.44)
[One (M7) Original Android Development] 144saint:
Very Simple and Easy s-off and I've rooted almost every htc out there on any carrier us.

Rom 4.1.2

1.31.651.2

Amazing! thanks guys!:good: