[One (M7) Original Android Development] Delgra:
Gaining root access (thanks to Dan's motochopper)...Segmentation fault (core dumped)

So here we are. I'm going to post my experience with last OTA update (JB 4.2.2) and S-Off, Bootloader and Root, with related solution.

[Disclaimer: I'm not responsible of the problems this can get to your device. This is my experience and so I tested it on my European HTC ONE.]

At my first attempt to get the OTA I did the following procedure:

1) Changed my CID to HTC__001 (or whatever was compatible with the RUU of my region) through command "fastboot oem writecid HTC__001"

2) Flashed stock recovery

3) Checked to have a stock hboot

4) Relocked my device through adb shell command "./revone -l " (this will keep your device S-Off even after OTA, but will lock the bootloader)

5) Downloaded an appropriate RUU from http://xdaforums.com/showthread.php?p=39588860

6) Flashed RUU

7) Rebooted the phone

8) Updated to 1.29

From here be careful because I made the mistake I will fix later. Do not proceed forward before reading the full post

9) Changed my CID to HTC__Y13 (or whatever had already received the official OTA through command "fastboot oem writecid HTC__Y13")

10) Got the OTA (one small + the 400 Mb one)

11) Tried to unlock bootloader again through revone (./revone -u) and got the error "Gaining root access (thanks to Dan's motochopper)...Segmentation fault (core dumped)"

12) No unlocked bootloader = No Custom Recovery = No Root = No Fun :\

The problem is that revone will work on the new hboot (that comes with the new firmware) only if you have already root permissions (and so that is the reason I could relock bootloader before flashing RUU even if I were already on the new hboot (1.54)). With the old hboot Root permissions are not required to use revone and due to this fact you can use the solution B that I'm going to explain forward.

How to proceed?

Here are the solutions:

Solution A:

This is really simple. Just Unlock it again throught HTCDev and (once you have your root permissions back) just remove "tampered" through revone.

This method is very easy but has also a downside. HTC will know you have requested the code to unlock your bootloader so you can have some warranty issues (it is difficult because you can always relock bootloader and go back to S-On through revone before returning your device and also they do not check those things very often as a lot of users reported on XDA, but not impossible)

Solution B:

First of all unlock your bootloader again at 1.28 or 1.29 before going forward (at Step 7 or 8) with the other steps (so if you made my mistake and you forgot to unlock bootloader before the installation of the OTA update you have to redo steps from 1 to 7 (I know it is a pain, but it will help you to pay attention next time). Even with bootloader unlocked you will receive the last OTA and this one won't erase your S-Off state and bootloader unlocked.

Solution C:

Wait for a possible revone update. No ETA yet.

Well.. you fixed that. Now you can flash a Custom Recovery, flash SU in order to get Root permissions and enjoy your Stock 4.2.2 S-Off Unlocked Rooted Device.

If you want to keep getting OTA updates change again your CID to the one you prefer and reflash stock recovery (stock recovery is necessary in order to get and install future OTAs). Cheers! :good: