yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] mrrogers1:
No, you run ./revone -l to change that banner.

See, here's the thing, it has always, in the past and obviously still should be, advisable to NEVER TAKE OTA's because 1) There is no reason to and 2) It can create some serious headaches.

The way it has always been "advisable" to do (I'm speaking from person HTC experience over the last 4 or 5yr) is WAIT for the OTA to be made root friendly as well as wait for the Firmware package to be stripped of all the stuff we don't want/nor do we need. These include but are not limited to the HBOOT which folks are finding has blocked the exploit for gaining S-Off with Revone.

Now let it be known/said, I'm in the US, I have a Sprint HTC One and we have not received the 4.2.2 update yet BUT in the past, it's usually, literally a matter of hours (we'll say half a day a most) before the new OTA is ripped apart and made ready to simply flash in Recovery. Same with the firmware, usually the same day/next day we have the bare min to update ONLY if we want. Firmware is typically not required (though on the EVO LTE there was a touch panel update in the firmware that was a bit of fun dealing with and on the EVO 3D firmware was actually required to flash up to ICS) to move up but maybe it is, maybe I missed something here but I don't think so.

Bottom line, relocking once you are S-off just to take an OTA has never been advisable and even though some people have done this with some "fiddling" and trial and error, the rush to get the 4.2.2 update at the possible expense of losing S-off is silly. Maybe things are that much different for our GSM brothren and if so, I apologize for my ignorance but it just is crazy to see people begging for OTA's and then messing up a good thing to get it. :silly:
[One (M7) Original Android Development] iElvis:
http://xdaforums.com/showthread.php?t=2182823

Read carefully and be sure you understand everything before proceeding. Read the last 20 pages in the thread particularly. Note that the instructions are a bit outdated. You don't need to relock; you do need to be s-off (and SuperCID for best results).
[One (M7) Original Android Development] mrrogers1:
There is ALWAYS a Stock Rooted version of the base roms that is the stock rom available.
[One (M7) Original Android Development] steljwaxd:
Succesfull s-off gained with revone :good:
[One (M7) Original Android Development] Toxicoblivion:
Im aware. Im saying adb doesnt work in os or recov. But fastboot commands work in fastboot.

AT&T HTC One

ARHD 12.0

Tbalden Perf Kernel 2.1.4 UV/OC/UC
[One (M7) Original Android Development] mrrogers1:
What rom? I heard secure ADB on AOSP roms can be finicky.
[One (M7) Original Android Development] Mash23:
Not asking about any ETA but has someone heard for sure that team Revolution is looking into breaking new hboot? :)
[One (M7) Original Android Development] russel5:
On new hboot or firmware 2.24.401.1 revone NOT working

Allways get error = -6

Bootloader unlocked

Have root

Any chance to fix it?
[One (M7) Original Android Development] gee2012:
Check on the Freenode IRC channel #revolutionary in the OP.
[One (M7) Original Android Development] nteeb:
You have to wait for the next update of revone. HTC has patched the exploit in the firmware, need to find a new one.
[One (M7) Original Android Development] samflorin:
Actually the only "fix" HTC did was the root exploit. As i have stated before it is perfectly possible to use revone if you are already rooted.
[One (M7) Original Android Development] gee2012:
Could you give us the correct procedure, tried everything and still get the -6 error every time. I`am not so familiar with HTC phones, so this is kind of new to me :) BTW i have root and will it also give me S-Off on Hboot 1.54.000?
[One (M7) Original Android Development] mrrogers1:
You quote the wrong person? I'm not sure what you are talking about. :confused:
[One (M7) Original Android Development] samflorin:
What i meant is that your statement that the hboot update prevents root is wrong.

---------- Post added at 10:52 PM ---------- Previous post was at 10:50 PM ----------

I already shared my small testcase 1 page back. I only played with the bl lock/unlock , not with soff.
[One (M7) Original Android Development] gianton:
You did that with Terminal Emulator app or with adb?
[One (M7) Original Android Development] samflorin:
adb
[One (M7) Original Android Development] gianton:
Good to know, I'm already S-OFF/unlocked since 4.1.2 base and still the status with 4.2.2 and latest 2.24 firmware/hboot. Not in a mood to try to re-lock/unlock my bootloader but it's good to know it works.
[One (M7) Original Android Development] gee2012:
How did you get past ./revone -P ? I always get a error -6 message even with root.
[One (M7) Original Android Development] Elemenopee:
Thank you guys. Gained S-OFF on the first attempt on my Mac. T-MO version. Now, is there a way to get rid of the red "this build is for blah blah blah" message?
[One (M7) Original Android Development] lmerega:
Nice to know, I will try asap.

Which TWRP did you install?

Could you see update available even when you were rooted?

Did you have any mod installed?
[One (M7) Original Android Development] mrrogers1:
Just want to start with, I'm not talking about (and we shouldn't really be) "root", I'm talking about s-off. Achieving s-off and gaining root are, well, 2 different things. Revone has graciously given us the ability to s-off without dealing with HTCDev unlock to root our devices. Why people are risking it with OTA's, I don't know. *Your locking/unlocking your bootloader with revone did nothing in essence because you were s-off the whole time. It's just a flag that changes the banner in bootloader and the flag itself isn't even respected because you are s-off.

I will continue to say, Hboot updates (while this one has definitely changed something to do with the exploit Revolutionary is using) can and have in the past completely shut down the ability to s-off, forcing users to use HTCDev to unlock the bootloader to "root" their device. It can then take months/year to find a new s-off and sometimes wild methods like using a paper clip. Worst case with hboot updates, as seen on the EVO LTE was the first 2 Hboot versions s-off OR HTCDev unlock allowed access to the boot partition. HTC realized they messed up and the 3rd hboot version blocked s-off (for awhile) but it also blocked the boot partition if only Dev unlocked so people got royally screwed... that was painful. Then came s-off methods that required one OS version or another and the pain continued for new users, it was ugly.

1) There is no reason to update hboot

2) When s-off, there is not a single reason (unless someone can enlighten me) outside of returning to HTC/Sprint etc that you should relock your bootloader, flash a stock recovery or s-on.

3) It's better to error on the side of caution rather than be impatient only to kick yourself in the rear when the solution is usually available within hours/days.

As I said before, if the GSM folks have to do this differently (ie, stock rooted roms and firmware packages aren't made available quickly or at all) then I appologize... maybe the Sprint/CDMA community has been spoiled but I swear all I ever hear is how large the GSM community is and how much more support they have so I doubt this is the case.

YMMV and to each their own :)
[One (M7) Original Android Development] io53:
Thank you for this magical binary. I somehow feel more comfortable with my One now with S-OFF ;).
[One (M7) Original Android Development] donmarkoni:
Very well said! :good: Full quote deserved. :highfive:

Once you go "dark side" I see no reason for turning S-ON and/or relocked/locked, but never had time or patience to discuss it.

Well, I even left tampered flag and red warning text cause I like it. :D Reminds me how restricted we were before.

Only reason would be for repair under warranty, but if hardware failed, no one cannot dispute your warranty claim cause of custom software.
[One (M7) Original Android Development] adamlee011:
Very well said indeed. That's exactly right. I never understood why people are trying to get ota's. I avoid them at all costs. I was lucky enough that I never went up from hboot 1.12 on my evo until I used dirty raccoon for soff and used ruu with hboot1.19. I recently updated all firmware on it but NEVER with an ota or ruu. That would be counter productive!
[One (M7) Original Android Development] iElvis:
Just as a point of clarification, it's safe to manually update your firmware (and usually a good idea) if you're already s-off.

But I agree 100% that I don't understand all these people going back and forth between s-off and s-on and locked and unlocked, then complaining that they've got problems or can no longer get root.
[One (M7) Original Android Development] mrrogers1:
Thanks guys, it has baffled me as to the wanting to take OTA's so I figured I would try to lay it all out, for better or worst because sometimes I feel oldschool, like I'm missing something and everyone is laughing at me but alas, tried and trued methods are just that, tried and trued... I have s-off't (even done it over Remote Desktop) probably 50 devices between OG EVO/EVO 3D/EVO LTE/HTC One and never have seen the back and forth as I've seen here, especially just to get an OTA. :eek:

On that firmware, yes, definitely, 150% if you are s-off, manual update of the needed firmware bits is advisable! I tell you what, I'm going to miss [MENTION=1162986]Captain_Throwback[/MENTION] blazing the trail (and helping tell people to 500 times how to do it, Lol) when we get our first firmware update. :crying:

*Stay Calm, Revone On :good: :good:
[One (M7) Original Android Development] adamlee011:
agreed the captain has been invaluable.
[One (M7) Original Android Development] gorle:
Just reading last pages and saw a couple of posts saying "No reason to go unlocked/relocked/locked once you have s-off.

My question is not related to s-off but to bootloaders: Is it possible to regain Locked and not Relocked once you have Unlocked?

Because on any other brands you have the possibility to hide the fact that you achieved root access and return COMPLETELY stock.

But with my latest HTC One X i had to spend 30€ more to have my phone back from repair because they said I had ruined the warranty (bootloader was relocked)
[One (M7) Original Android Development] Toxicoblivion:
ARHD 12 :P (problem existed for me on 11 (when i gained soff) + 11.5 also)

AT&T HTC One

ARHD 12.0

Tbalden Perf Kernel 2.1.4 UV/OC/UC
[One (M7) Original Android Development] adamlee011:
Deleted
[One (M7) Original Android Development] mrrogers1:
Deleted.... FU TAPATALK! Sorry there buddy.
[One (M7) Original Android Development] carlos67:
OK so it's been convincingly established that staying s-off and unlocked is the way to stay, and I agree.

However, on that dark day when your phone has to go back to HTC repair centre and your heart beats fast and your wallet sits nervously in your pocket, is it easy to get completely back to stock. I mean s-on, bootloader "locked" no sign of root, stock rom that came out the box.

If the answer is yes, then I'm taking the plunge and going s-off! F**k it!

If the answer is yes (and I really hope it is yes) then can someone link to a guide on how to get completely back to stock. In what order to do the steps.

Cheers dudes.
[One (M7) Original Android Development] carlos67:
So by flashing the official RUU your phone goes back to s-on automatically?? And does the bootloader go back to "locked" when you flash the RUU? And the red warning text disappears too?

All of this just by flashing the RUU without any additional manual steps?
[One (M7) Original Android Development] carlos67:
WOW :eek:

Didn't realise it was that easy.

Thanks buddy.
[One (M7) Original Android Development] gorle:
I think I got what adamlee said a couple of posts earlier:

with a simple command (revone/ -I) you can show locked instead of relocked, but we still don't know if HTC has the possibility to see if we were unlocked or hasn't.

Anyway, the steps would be (I may be wrong, just wondering):

- you got s-off, custom Rom, custom recovery

- flash latest ruu from your carrier or latest official update compatible with 1.44 hboot (write down your stock CID)

- you now have s-off, stock Rom, stock recovery

- return s-on

- (don't know if there are steps related to the CID number)

- show locked instead of relocked

Please please don't quote me, don't follow my steps, I'm just wondering
[One (M7) Original Android Development] carlos67:
Ok, reading in another thread, some dudes were saying that flashing the RUU does not return to s-on. So, I think maybe after running RUU you still need to run revone to go s-on and then delete the revone binary from /data/local/tmp
[One (M7) Original Android Development] adamlee011:
Delete
[One (M7) Original Android Development] DeSaint2:
No. A Ruu just puts you back to stock everything but it does not bring s-on back. It may lock the bootloader(that on not sure on) but it just brings everything back to when you got it. So it would be Ruu, lock bootloader, then revert to s-on. Returning to s-on is always last to ensure you have stock signed hboot because with a modified hboot, reverting to s-on is an instant unrecoverable brick.
[One (M7) Original Android Development] Toxicoblivion:
"Bad" at this? Thank you for being disrespectful, and not helping at all.

AT&T HTC One

ARHD 12.0

Tbalden Perf Kernel 2.1.4 UV/OC/UC
[One (M7) Original Android Development] adamlee011:
Oh ok thanks. I just figured since you can ruu whole s-on you could save that for last. Definitely locked bootloader on evolte

Good call though. At least then you're sure you have sock signed hboot. I don't and yes that could be disasterous.
[One (M7) Original Android Development] iElvis:
No, no, and no. Please refrain from answering these kinds of questions unless you know what you're talking about.

Running a RUU does not make you s-on. The only way to go back is to do it manually.

You cannot run a RUU with an unlocked bootloader unless you're s-off. But if you are, it won't relock.

The red warning text is there when you are unlocked. It goes away when you relock. It has nothing to do with the RUU.

Also, if you ever flashed a custom rom, HTC apparently has ways of knowing. So if you're concerned with hiding it from them somehow, forget it.
[One (M7) Original Android Development] DeSaint2:
From my readings that is what I remember. I would definitely seek more experienced advice before ever attempting to go s-on.
[One (M7) Original Android Development] adamlee011:
I'm not and luckily it's not something I envision myself ever doing. Sorry to cause confusion. I was under the impression that locking the bootloader was part of the process of running the ruu and that any instructions on flashing it would include that in the process. Apparently the experience I have with these processes is a bit more lacking then I thought. I thought I had a better idea of what was happening from the context of the things that I have done. I'll certainly be more careful with my advice. I will edit out my posts. Thanks.

---------- Post added at 08:55 PM ---------- Previous post was at 08:52 PM ----------

Sorry bud, listen to this guy :)
[One (M7) Original Android Development] samflorin:
I installed the touch-fixed version of TWRP. The latest version (2.6) should work by default with the new firmware (haven't tested it yet though).

I unrooted before i ota'ed

I had no mods installed (except root which i removed before taking the OTA).

One of the reasons i took the OTA was for the firmware update (which has been confirmed that it kept S-OFF / BL unlocked by other people in the 4.2.2 thread in general).
[One (M7) Original Android Development] godutch:
I s-offed on 4.1.2 but even then got this error a few times. I needed to reboot my device a couple of times (and needed to disable fastboot in power options too)
[One (M7) Original Android Development] flamechamp:
ah, I forgot to give my review! This thing has succesfully provided me S-OFF after some breathtaking moments :P
[One (M7) Original Android Development] gee2012:
Well i have tried Revone both with adb and terminal emulator and nothing worked to get S-Off. Always getting an error -6 after ./revone -P on Hboot 1.54.000.
[One (M7) Original Android Development] willumpie82:
Hi all,

I successfuly applied S-OFF with this method (after two retries)

But now my question is how to apply the 4.2.2 stock update,

What procedure should I follow to safely apply OTA without loosing S-OFF and custom recovery (or the abillity to)

I've seen a few methods passing by in this thread, but all significantly different. which is the One?

my config:

HTC One CID-HTC__102

HBOOT 1.44.0000

RADIO-4A.14.3250.13
[One (M7) Original Android Development] lmerega:
Totally agree but: the new firmware posted in the thread in the dev forum does have old HBOOT?

All the new UI customizations are still present?

It is only 40 Mbyte VS the 400 Mbyte of the OTA.
[One (M7) Original Android Development] samflorin:
The OTA has the firmware update AND the Android update. Firmware is 40 MB, the remaining 360 is the actual Android update from 4.1.2 to 4.2.2 .

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

!!!! Take a nandroid before !!!!

Here's how i did it (S-OFF/Unlocked):

1. Unrooted the phone (not sure if required, you could try to enable OTA rootkeeper)

2. Flashed stock recovery (search for the version corresponding to your current sw)

3. Installed the small OTA (around 2 MB if i remember correctly)

4. Rebooted and installed the big OTA (here i had some issues, first the upgrade hanged at 25%, then at 50%, had to force a restart every time by unplugging/pressed power+vol down under a bright light).

5. After OTA finally completed i flashed TWRP and rooted

6. Using adb shell i moved my DCIM folder from /data/media to /data/media/0 (i believe that the data was not moved due to me rebooting the phone mid-way):

- adb shell

- su

- cd /data/media

- ls (read the output, make sure that there is a folder there called 0) -> That is a zero not a capital o

- mv DCIM 0 -> Again a zero not a capital o

- move whatever other folders you wish such as music,videos using mv folder 0/

Rebooted just in case. Everything was there. Took a while though before all my zoes appeared in the gallery. You can also force a rescan using Rescan SD app in Store.

Also i believe that all the hidden folders (the ones starting with a .) are safe to remove from /data/media (or can be simply moved under /data/media/0 using either mv or ES File Explorer in root mode)
[One (M7) Original Android Development] donmarkoni:
Listen guys! You either have the balls to be S-OFF or you don't. ;)

When S-OFF, you can brick your device very, very easy. Stock phones are S-ON and locked cause of your protection.

If you play with fire, you

will

get burned, but question is how much, and can you tolerate the pain (in your wallet) ;)

If shiat hits the fan, then you try go stock, lock and S-ON for the warranty purposes. If fails, then you pay for the repairs, or buy a new phone. It's that simple. :cowboy:
[One (M7) Original Android Development] willumpie82:
thanks for the elaboration,

If i understand you right, there is no risk of loosing S-off by the OTA. and can flash custom recovery after OTA

Unfortunatly i'll have to wait for my update or modify my CID

---------- Post added at 08:32 AM ---------- Previous post was at 08:28 AM ----------

Ofcource, I agree. I like to play with fire, but thats exactly where this forum is ment for, help your fellow pyro's not getting burned because you already did it ;), eg not making the same mistake as others
[One (M7) Original Android Development] gee2012:
Let everyone decide for themselves what to do with their device. S-Off is a very handy option that enables possibilities you didn`t have before :)

BTW I see in your sig you have S-Off yourself ;)
[One (M7) Original Android Development] gartner83:
Yeah, me too. After two days I've given up. The irony is that I already had S-OFF but I wanted to go completely stock(I just needed to flash something and I played around a little:laugh:) so I RUU-ed back to 4.1.2, got all the OTAS and the party was over. I could lock the bootloader but once I did S-ON, I couldn't get pass the error 6.

I guess I learned my lesson, never to S-ON after you're S-OFF just for the fun of it.
[One (M7) Original Android Development] donmarkoni:
Well said, my fellow pyro. :highfive:

But my comment was not meant for you, but for the "children" running around screaming "I bricked", "I lost S-ON", "Help, help", or those that especially pi$$ me off with "not working" and no logs, no procedure description, no nothing.

I'm not pushing anyone either way, just stating what could happen. ;)

Cheers! :)
[One (M7) Original Android Development] sanusweetsmile:
Microsoft Windows [Version 6.1.7601]

Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Sandeep>cd documents

C:\Users\Sandeep\Documents>cd htc

C:\Users\Sandeep\Documents\HTC>adb push revone /data/local/tmp/

3118 KB/s (648208 bytes in 0.203s)

C:\Users\Sandeep\Documents\HTC>adb shell

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

cd /data/local/tmp

shell@android:/data/local/tmp $ chmod 755 revone

chmod 755 revone

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

./revone -P

revone v0.2.1

Gaining root access (thanks to Dan's motochopper)...[-] Failed to map memory.

[-] Failed to map memory.

[-] Failed to map memory.

[-] Failed to map memory.

[-] Failed to map memory.

[-] Failed to map memory.

[-] Failed to map memory.

[-] Failed to map memory.

[-] Failed to map memory.

[-] Failed to map memory.

[-] Failed to map memory.

[-] Failed to map memory.

[-] Failed to map memory.

[-] Failed to map memory.

[-] Failed to map memory.

[-] Failed to map memory.

[-] Failed to map memory.

[-] Failed to map memory.

251|shell@android:/data/local/tmp $

C:\Users\Sandeep\Documents\HTC>adb push revone /data/local/tmp/

2594 KB/s (648208 bytes in 0.244s)

C:\Users\Sandeep\Documents\HTC>adb shell

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

cd /data/local/tmp

shell@android:/data/local/tmp $ chmod 755 revone

chmod 755 revone

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

./revone -P

revone v0.2.1

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

revone successful - please reboot to continue.

shell@android:/data/local/tmp $

C:\Users\Sandeep\Documents\HTC>adb shell

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

cd /data/local/tmp

shell@android:/data/local/tmp $ ./revone -s 0 -u

./revone -s 0 -u

revone v0.2.1

Gaining root access (thanks to Dan's motochopper)...[-] Failed to map memory.

[-] Failed to map memory.

[-] Failed to map memory.

[-] Failed to map memory.

[-] Failed to map memory.

[-] Failed to map memory.

[-] Failed to map memory.

[-] Failed to map memory.

[-] Failed to map memory.

[-] Failed to map memory.

[-] Failed to map memory.

[-] Failed to map memory.

[-] Failed to map memory.

[-] Failed to map memory.

[-] Failed to map memory.

[-] Failed to map memory.

[-] Failed to map memory.

[-] Failed to map memory.

251|shell@android:/data/local/tmp $ ./revone -s 0 -u

./revone -s 0 -u

revone v0.2.1

revone failed (error code = -1)

255|shell@android:/data/local/tmp $

this is the error i m getting again and again pls help me i have developer edition htc one which is not rooted
[One (M7) Original Android Development] prunzzz:
hey, thats all right

i dont know the reason for it but i do know the solution

disconnect phone from pc

Power down

reboot in bootloader

select fastboot

select reboot

once fully booted, connect to pc

If not done in one shot, do it again and you are good to go

HIT THANKS BUTTON IF I HELPED YOU
[One (M7) Original Android Development] irenic:
successfully unlock and s-off my htc one.

but why i didnt see tampered?

or the tampered only appear once i relock the phone?
[One (M7) Original Android Development] gartner83:
Tampered appears when you flash custom recovery, maybe if you only root it, that I don't know, but I'm sure about the recovery.