yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] daleski75:
If you only want to lock then fastboot oem lock would suffice but you will need to wait for a new exploit to run revone on hboot 1.54
[One (M7) Original Android Development] DeSaint2:
Why are you wanting to lock the bootloader?
[One (M7) Original Android Development] Ronaldo_9:
If I do fastboot oem lock will I see the tampered message?

Thanks

I did updated to 4.2.2 http://xdaforums.com/showthread.php?t=2363384

Just in case something goes wrong and I need warranty.

Thanks
[One (M7) Original Android Development] daleski75:
The second you relock/lock I am pretty certain it will say tampered as I did the same to see if I could get my phone back to 100% stock and it said locked until I rebooted or something like that and then it said relocked and tampered and now there is no way to s-off again with revone or moonshine.

Why must you lock it again if you don't have to?
[One (M7) Original Android Development] alekz2604:
I had 4.1.2 stock, soff, unlocked and i did a nandroid backup with twrp. After this i locked back , s-on and i took the 4.2.2 ota. Is there any way to use my nandroid backup to revert to 4.1.2 with older hboot ?
[One (M7) Original Android Development] Ronaldo_9:
When you did the re-lock did your phone erase everything?
[One (M7) Original Android Development] tiho5:
re-lock isn't going to erase anything.

But why do it. I advice you not to.
[One (M7) Original Android Development] daleski75:
It never erased anything but you cannot unlock it again.
[One (M7) Original Android Development] maverick1103:
Am I correct in saying you would only re-lock when you need to send your phone back off for repair?
[One (M7) Original Android Development] Ronaldo_9:
That's right. I'm not rushing as I am sure when every one gets 4.2.2 the dev team will find a way.

Cheers
[One (M7) Original Android Development] maverick1103:
Hmm so not quite sure why people are mad about relocking it! Strange.
[One (M7) Original Android Development] Brodad:
Hey guys, quick question. I'm on a GE one here (purchased it from Google so it shipped with HBOOT 1.54). If I use an exploit to gain S-OFF, will I lose the ability to receive OTA updates?
[One (M7) Original Android Development] io53:
Revone does not support 1.54 yet. But no, you do not lose the ability to get and install OTA with S-OFF and/or unlock.
[One (M7) Original Android Development] Ronaldo_9:
People want to put the phone back to stock so if there was a problem they can send it off without worrying .

Say my BL is unlocked and s-off but my phone suddenly turned off I couldn't boot it up. I'd be glad if was locked /s on. I could then send it for repair
[One (M7) Original Android Development] gee2012:
Or if you want to flash a official RUU (for warranty reasons or whatever reason) or you want to sell the phone, even then don`t Relock but Lock.
[One (M7) Original Android Development] Magpir:
hey guys i have to warn u do not flash the custom firmware 2.24.401.1. it upgrades yr hboot

flash the one 2.24.709.1 - custom zip
[One (M7) Original Android Development] gee2012:
Your problem is imo not related to the unlocked bootloader or S-Off. Probably app related, try to do a data factory reset in recovery or settings/backup and restore. Can you boot the phone now?

---------- Post added at 06:32 PM ---------- Previous post was at 06:29 PM ----------

Is that a fact or an asumption. Can`t you go from relocked to unlocked to locked ( ./revone -l)?

Its astounding to see how many people can realy read!
[One (M7) Original Android Development] Magpir:
I am currently S-off and super CID

when i flashed one of the new modified firmware files of 4.2.2, i got updated to 1.54

still S-off and super CId all intact

now my qn is

Does revone commands work on the Hboot 1.54 to go back to "locked"

I mean "locked" not relock

OR is it those who want to revone S-off after updating to 1.54 Hboot is affected?

what about those who already on S-off and 1.54 Hboot who want to go back to "locked" status?
[One (M7) Original Android Development] tiho5:
Absolutely, yes

If this is the case and you keep your BL locked and S-on, then how would you exxplain to them why you have a custom ROM or recovery? :)

Or if you have a stock ROM, why is it updated when there was no update for that region?

Or if you simply use stock ROM an you have the normal updates why unlock and s-off it in the first place?

You either keep it stock all the way or custom all the way. That's what I think
[One (M7) Original Android Development] Ronaldo_9:
I have no issue.

I am just looking for a way to lock BL and S-off without tampered message. I already now it is no possible until revone is updated.
[One (M7) Original Android Development] daleski75:
If they have 1.54 is it worth the risk?
[One (M7) Original Android Development] Magpir:
U dont have to be glad

if yr phone cant turn on, then its hardware fault and u bring to HTC , they cant turn it on too. probably they will replace it for u and u are off the service centre with a new one . HTC will not ever know u have S-off tampered or watever crap in bootloader because they cant turn on the phone and will not waste time on yr device after they issued a new one to u.

it is those whose phone have some poblems like touchscreen or battery but phone is still functional need to worry about returning to "stock" for warranty purposes
[One (M7) Original Android Development] maverick1103:
Sorry been I hard day, I understand why they want it locked for those purposes.
[One (M7) Original Android Development] gee2012:
Quote>Say my BL is unlocked and s-off but my phone suddenly turned off I couldn't boot it up. I'd be glad if was locked /s on. I could then send it for repair

Sure looked like an issue getting fc and talking repair :D

---------- Post added at 06:47 PM ---------- Previous post was at 06:40 PM ----------

Hey [MENTION=4136711]maverick1103[/MENTION], know you from the Note 2 or S3 ARHD thread ;)
[One (M7) Original Android Development] maverick1103:
Hey Gee, yes that's right, how's things? Are you rocking ARHD on your One?
[One (M7) Original Android Development] gee2012:
Yup, ARHD 12.0 running great and good batterylife. BL unlocked but was so stupid to go back S-On ( will never happen again though) :p
[One (M7) Original Android Development] maverick1103:
Cool I might give it a try, I'm running Viper 1.2.1 love the tweaks. I haven't gone s-off yet I just unlocked my BL through HTC Dev, I should've just came here first...still I assume if I s-off with revone I still go back to s-on, lock the Bl and remove the tamper tag incase I need to send phone away. Then it's just my word against HTC on if I used the Token ;)
[One (M7) Original Android Development] gee2012:
If you turn in the phone fully stock they can`t deny warranty.
[One (M7) Original Android Development] Jon2555:
I keep getting error code 1, not -1 but 1. Anyone else have same problem?
[One (M7) Original Android Development] gee2012:
Is usb debugging enabled, unchecked fastboot in settings/energy and used the correct revone name in cmd as it is stored in sdk/platform-tools.
[One (M7) Original Android Development] daleski75:
Here is what happened to me.

I had s-off and hboot 1.44 went to 4.22 with the ota and then got hboot 1.54...

Decided to lock my phone with revone -l to see if I could go back to stock factory

Tried to unlock with revone -u and then got the segmentation fault

Made a further bad decision by then doing fastboot oem writesecureflag 3 to see if I could start from scratch

Answer is no.

So yes for me it is a fact that I could not even unlock the phone with s-off on 4.2.2 with hboot 1.54.
[One (M7) Original Android Development] maverick1103:
That's what I thought, my Hboot is 1.44 so I will s-off soon. If I s off then update my firmware I will stay s off won't I, just want to confirm.
[One (M7) Original Android Development] gee2012:
Off course, we ( the ones with S-On) are all in that same situation, but once we get a fix we can fix the relocked to locked status.
[One (M7) Original Android Development] bgcngm:
Couldn't you downgrade your hboot while S-OFF? If you did so you could continue using revone.
[One (M7) Original Android Development] Jon2555:
Yes, I did all that but still getting it.
[One (M7) Original Android Development] gee2012:
Yes, S-Off will stay as is after an update. You maight also change the CID version to HTC__001 or SuperCID 11111111, this way you can flash almost any RUU you want. CMD command: fastboot oem writecid HTC__001 or 11111111.
[One (M7) Original Android Development] maverick1103:
Cool thanks for that info! I'm sure you will be able to go back to s-off soon enough, these guys are geniuses it won't take them long to crack the new hboot!
[One (M7) Original Android Development] gee2012:
Lets hope so bro :) But whatever you do, don`t ever go back to S-On.
[One (M7) Original Android Development] Grooov3:
Worked in first try =) thx 4 this mod ^^

another question is it possible to remove to stupid simlock with s off when yes how?

thats to only thing i dont know...

greeetings
[One (M7) Original Android Development] daleski75:
Good point that thought did not even cross my mind doh! Would a down grade worked with a locked boot loader then?
[One (M7) Original Android Development] maverick1103:
I won't do!
[One (M7) Original Android Development] broffy:
i think i have a very big problem looking for some help i had s -off how ever i did the hboot removal red warning on hboot and some how that put back on s-on i tried everything these are my phone details

c:\adb>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.44.0000

(bootloader) version-baseband: 4A.14.3250.13

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main:

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

(bootloader) serialno:

(bootloader) imei:

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0712000

(bootloader) cidnum: 11111111

(bootloader) battery-status: good

(bootloader) battery-voltage: 4203mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: RUU

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

i change the hboot to

modelid: PN0712000

cidnum: 11111111

cidnum: HTC__E11

cidnum: HTC__102

cidnum: HTC__203

cidnum: HTC__405

cidnum: HTC__Y13

cidnum: HTC__304

cidnum: HTC__032

cidnum: HTC__A07

cidnum: HTC__J15

cidnum: HTC__016

mainver: 1.29.401.12

btype:1

aareport:1

hbootpreupdate:3

need help with error

i am how ever able to change my bootloader from locked to unlock and back again but tampered is not moving are s-on not going s-off
[One (M7) Original Android Development] alekz2604:
I hope i am not right but i think you have a bigger problem.... No imei.. at least so it shows
[One (M7) Original Android Development] tiho5:
IMEI and Serial no are not good to be posted and he hid them in purpose

:)

---------- Post added at 09:11 PM ---------- Previous post was at 09:08 PM ----------

Indeed you did everything we are telling here not to... :)

And yes, with locked BL you can go to custom recovery, but I guess you know this already..

I hope all of you who locked and/or s-on'ed get a fix from revone team! This sucks!
[One (M7) Original Android Development] broffy:
lol thanks again just really wanted to know how screwed i was

i wanted to know if i would be possible for me to change my radio and test some way if it is really s-off
[One (M7) Original Android Development] tiho5:
Well, radio is possible to flash with s-on

Check if you are s-off by using "fastboot getvar all" and look for line [FONT=&quot]"version-misc" in the outut, or simply boot to bootloader and see the screen [/FONT]
[One (M7) Original Android Development] daleski75:
The biggest problem I have is me.... I like to play around and see what works or does not work and cannot leave my phone alone, always flashing roms, trying out tweaks but this time it bit me on my ass.... I had no reason to go back to stock but I had to try lol...

Word of advise if you do NOT need to return your phone for repair etc then do NOT go back to s-on!
[One (M7) Original Android Development] broffy:
still s-on i guess i got to wait this one out then
[One (M7) Original Android Development] daleski75:
Yup I am sure the dev's are on the case.
[One (M7) Original Android Development] jmkhenka:
Not unless you got S-OFF, wich you don't have. relocking should be enough to install OTA and update hboot. S-ON'ing once s-off is no use, hboot updates but you have the option to revert.. wich you dont have now unless revone gets a 4.2.2/1.54 s-off exploit.
[One (M7) Original Android Development] lmerega:
Ok, please let me know if I have understood everything.

I have Revone on my HTC Onewich is on original CID, unlocked, S-Offed and rooted.

I'm on old HBOOT.

I would like to upgrade the firmware.

The upgrade will update the HBOOT.

The new HBOOT (1.54 or 1.55 I haven't found the right versione yet) is not compatible with revone UNLESS you are root.

I am root, so I could:

1 - Flash new firmware

2 - Have Revone working with my SuperSU app

If everything is correct: what cannot I do with revone now?

Can I lock?

Can I S-On?

Can I S-Off again?

Can I unlock again?

Please, correct me if I am wrong... and correct my English too if it's needed :)

Thx

.luca
[One (M7) Original Android Development] DeSaint2:
In most cases /revone does not work at all on 1.54 even with root. The best thing you can do is just update firmware by using a custom zip. It didn't use a custom hboot. It just had dzdata, boot.img, and recovery.img removed. So no need to lock bootloader or go s-on. Then if you need to send in to repair you can downgrade firmware with a Ruu to get back to the 1.44 hboot lock the bl and go s-on. This way you still have the option when you receive it back.
[One (M7) Original Android Development] jmkhenka:
Stay s-off, lock and restore stock and update. Afterwards you can unlock with revone again (as long as you are s-off), or just fastboot oem unlock or whatever, s-off will not affected by a upgrade.

BUT DONT S-ON THIS WILL NOT LET YOU S-OFF AGAIN!
[One (M7) Original Android Development] lmerega:
Can you advice me a good fw?

Thx :D
[One (M7) Original Android Development] gee2012:
If you flash a RUU and update to 4.2.2 (Hboot 1.54/1.55) you cannot unlock the bootloader again with revone, it doesn`t work atm for the new bootloader. You can only unlock the bootloader on htcdev.com with a unlock key. You will however stay S-Off after the RUU and update. Fastboot oem unlock doesn`t work with HTC`s.
[One (M7) Original Android Development] srqt:
trying to regain s-on. Followed the instructions but got the following and am still marked s-off

D:\android>fastboot oem writesecureflag 3

...

(bootloader) partition hboot signature error

(bootloader) writesecureflag: partitions siganture failed

OKAY [ 1.570s]

finished. total time: 1.570s

any idea what I am doing wrong?
[One (M7) Original Android Development] rufolo:
device not found

impossible for me to pass this step... "error:device not found" is always shown. i had the terminal connected, debugged mode,... any other method in order to push renove please?

i am stuck in this step...

thanks!
[One (M7) Original Android Development] gee2012:
What Hboot version do you have? 1.44 or 1.54/55

---------- Post added at 10:11 PM ---------- Previous post was at 10:07 PM ----------

Correct usb-drivers installed?

Disabled fastboot in settings/energy?

Copy revone yourself to the phone and then with Root Explorer in /data/local/tmp/ and do the revone procedure with a terminal emulator on the phone in su mode.
[One (M7) Original Android Development] RaptorMD:
I will most likely update to the latest stock version of 4.2.2 that goes with 2.24.4010.1 initially and make a backup of that. Then figure out which ROM to go with. I will use adb sideload so I can format and insure a super clean install.
[One (M7) Original Android Development] daleski75:
Do you have a custom hboot?
[One (M7) Original Android Development] broffy:
i have the same problem
[One (M7) Original Android Development] donmarkoni:
That's what I'm talking about. :highfive:

There is nothing to be gained by upgrading HBOOT. I personally tried, had 1.44, updated to 1.54, gained nothing, flashed back 1.44.

People get S-OFF, then loose it by their mistake and come whining here. That could irritate the developers, couldn't it?

Did anyone thought of possibility that there won't be S-OFF again?
[One (M7) Original Android Development] Mash23:
I have and I've been pissed off to myself of not s-offing before update! :'(
[One (M7) Original Android Development] DeSaint2:
Check this thread. Only use the stuff on the second thread and do not lock bl or go s-on. It is mitt needed to update firmware from the second post. (I think I linked directly to the second post.)

http://xdaforums.com/showthread.php?p=39225672
[One (M7) Original Android Development] rufolo:
I think correct usb drivers are crrectly installed

Disabled fastboot ok

I do not have that local and tmp folders created... Not su yet...

Thanks!
[One (M7) Original Android Development] alanzo27:
I am hoping that S-off comes to HBOOT 1.54/JB 4.2.2. If and when it does, I will be flashing an RUU to go back to stock. Then I will make sure I am S-off forever and never revert back. I will also do each step very carefully so that I don't make another mistake. :) I am very curious and rushed into it head first, so it's my own fault :P I really enjoy all of this though, it's a learning curve and although I am not a dev, I find it fun. Maybe I will be a dev some day (Doubtful TBH.) Wishful thinking. :)

Right back on topic.
[One (M7) Original Android Development] ttocs99:
Still cant soff with this im doin it by phone and p.c but just gets stuck after ive type ./revone -s 0 -u then just reboots on its own still dont get why i cant soff
[One (M7) Original Android Development] alanzo27:
What output do you get after ./revone -s 0 -u before the reboot?
[One (M7) Original Android Development] ttocs99:
Nothing it doesnt even say sucsesfull
[One (M7) Original Android Development] TubeShaped:
With hboot 1.54 i was able to lock my device with -l command, then went S-ON again. From then on I was not able to do anything with revone, not even removing the tampered flag.
[One (M7) Original Android Development] ttocs99:
Done it now :D well chuffed
[One (M7) Original Android Development] graffixnyc:
There will be, maybe not tomorrow or next week but eventually someone will figure out a way. I remember with the EVO 3d it was the same way. Revolutionary got it s-offed but then a bootloader patch fixed it. The eventually got that bootloader s-offed after some time. So there is a very good possibility s-off will be achieved. The only question is when. It might be in a couple of weeks, it might be in a couple of months but it will eventually happen
[One (M7) Original Android Development] simonbarsinistr:
Successfully gained S off and removed the tamper flag on a BL unlocked Sprint HTC One. Very easy to use, thanks for your work revolutionary team, a small donation has been made to your device fund.
[One (M7) Original Android Development] scifitrekkie:
So waht did you do to correct it?
[One (M7) Original Android Development] cc999:
Big Mistake

You cannot go S-ON on 1.54. you will then be stuck. This Revone only works on 1.44.

When you achieve S-off KEEP IT FOREVER.

CC
[One (M7) Original Android Development] jumi1174:
Has there been any definitive answer to error code = -1 and error code = -2?

Every time I issue the "revone -s 0 -u" command, I get error code = -1. I reboot and try to switch it up with the "revone -s 0 -u -t" command instead, but every time on that one I get error code = -2.

I keep seeing the question getting brushed over or people saying, "Retry, retry, retry".

Do I reboot every time I retry? Or can I just issue the same command in the terminal? Do I have to do the "revone -P" step too every time I retry?

Thanks in advance.

I'm on ATT Stock, Rooted, Bootload Unlocked, HBoot - 1.44.0000.
[One (M7) Original Android Development] DeSaint2:
Don't do the -t be yes just start from the beginning. and do manual restarts through the instructions. Once to the s-off stage just keep running the command until it goes through. If doing it in adb restart your pc before beginning.
[One (M7) Original Android Development] jumi1174:
Thanks! Restarting my computer did the trick. Never would have tried that...

EDIT: I'm getting a "success" reading for the Tampered flag, but when I reboot in bootloader, it's still showing tampered. Any ideas?

EDIT 2: Figured it out. Have to:

> adb shell

> cd data/local/tmp

> chmod 755 revone

> ./revone -t
[One (M7) Original Android Development] techeretic:
EDIT: Never Mind, My lazy ass decided to search in the Thread after posting, screen needs to be unlocked, solved it
[One (M7) Original Android Development] DJ 1:
It did that to me the 1st try, no error msg,just a reboot.

2nd try it was all fine.(i did mine through terminal emulator (Rom toolbox))
[One (M7) Original Android Development] steljwaxd:
Aaaaah it never stops...

I had some reasons to revert back to stock, so I used my cwm backup to restore my HTC one, downgraded the hboot to 1.44, so far so good...

Now, my touch is not working anymore, device boots up normally but does not register any touching! What is the appropriate step to make my touch work again?:confused:
[One (M7) Original Android Development] io53:
Probably to flash a RUU. Not sure, have you changed MID and flashed another RUU or the Google Edition zip?
[One (M7) Original Android Development] steljwaxd:
No, changed nothing... did loaded a firmware package...

Trying a RUU now, does it lock the phone again?
[One (M7) Original Android Development] killerduck:
Easy Job

A BIG shout out to the developer for this great tool . I didnt want to bother with drivers on the computer, so I went ahead with the commands in Android Terminal . The first time , it said Revone Successful , but i was still S-ON. I just repeated the same steps again , and this time it was S-OFF. Thanks a bunch.
[One (M7) Original Android Development] io53:
S-OFF does not got away unless you tell it to :). Could be the touchscreen drivers from the new firmware that is not compatible with your older rom/kernel.
[One (M7) Original Android Development] steljwaxd:
Thank, everything works again with the RUU, unfortunately it is not how I got the phone, but it's stock again.
[One (M7) Original Android Development] Spartn:
any news on getting s off again for hboot 1.54?

Hello,

does anyone have any info about getting s off again for hboot 1.54? If even planned? if any devs working on it, any info would be great voice for everybody here waiting patiently :)

please don't consider this question asking for exact time ;)

thanks to all developers for all work they have done so far
[One (M7) Original Android Development] io53:
No one knows, asking the devs on IRC seem to lead to a kick + ban. Time will tell.
[One (M7) Original Android Development] mathrania:
If the REV team got S OFF for our HTC ONE on previous bootloaders, they would surely be working on it for the new versions.....

Our Requests wont help...they developed it before too, and might do it again...so everyone should keep calm on it :)
[One (M7) Original Android Development] tfouto:
One question...

I have s-off and bootloader unlock. From what i have read from this thread, if i update to stock 4.2.2 ROM via OTA i will gain an new hboot and that way s-off will not work. Altough i will stay with s-off active. If i relock, i cannot unlock again via revone, is this right?

Can i update with bootloader unlocked via OTA to stock 4.2.2 and remain with s-off and unlock with no problem?

Thanks
[One (M7) Original Android Development] mathrania:
well, i was S OFF, i got the 4.2.2 Update....installed it.... then I am still S off and relocked, but when i try to Unlock bootloader via revone, It gives me a segmentation error...... tried restarting my Mobile and PC both... didnt work, tried a lots and lots of time...