Database Develop

[Q] Can't boot to recovery, can't s-off

Hi,
two weeks ago I sent in my HTC One (O2 Germany branded) because it had a stuck pixel and today I got a brand new replacement phone.
I wanted to get back on to my old ROM etc pretty fast and thought I'd use the AIO Toolkit to unlock/s-off/etc this time instead of doing all on my own.
First thing I did was getting a new unlock token and then unlock the phone, use AIO to flash recovery (bootloader still showed unlocked which I didn't notice at that time of the process) and directly went to s-off to convert my phone to a google edition phone afterwards.
Then things started to visibly not work. Revone was granted root for the preparation process, everything went fine, I rebooted. Then, s-off failed. Now root started to drop errors (was something with memory can't be allocated) and revone gave me -1 and -6 errors.
Then I thought about using recovery and just flash a custom ROM for now and do the firmware part later, when I noticed that recovery isn't working, too.
I'm pretty clueless now, I have relocked and unlocked my phone again, tried to flash all sorts of recoveries (both CWM and TWRP, newest and older versions), tried to revone again (still the above mentioned errors). I also searched a bit on the forums here and found nothing of value (few things which were said to help - still no success).
Fastboot getvar all also drops an error:
C:\Android SDK\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.206.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34VW908233
(bootloader) imei: 354436054362833
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4222mV
(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.057s
I'm not a noob, I read carefully what to do when I get a new device, I know where to look for everything here and I've been flashing ROMs and doing all this stuff on my HTC devices for quite some time now. And yes, I have upgraded my HTC drivers.
It's possible that I missed something though. Nobody is perfect. I'm gratefull for every piece of help I get from you people.

eisteh said:
Hi,
two weeks ago I sent in my HTC One (O2 Germany branded) because it had a stuck pixel and today I got a brand new replacement phone.
I wanted to get back on to my old ROM etc pretty fast and thought I'd use the AIO Toolkit to unlock/s-off/etc this time instead of doing all on my own.
First thing I did was getting a new unlock token and then unlock the phone, use AIO to flash recovery (bootloader still showed unlocked which I didn't notice at that time of the process) and directly went to s-off to convert my phone to a google edition phone afterwards.
Then things started to visibly not work. Revone was granted root for the preparation process, everything went fine, I rebooted. Then, s-off failed. Now root started to drop errors (was something with memory can't be allocated) and revone gave me -1 and -6 errors.
Then I thought about using recovery and just flash a custom ROM for now and do the firmware part later, when I noticed that recovery isn't working, too.
I'm pretty clueless now, I have relocked and unlocked my phone again, tried to flash all sorts of recoveries (both CWM and TWRP, newest and older versions), tried to revone again (still the above mentioned errors). I also searched a bit on the forums here and found nothing of value (few things which were said to help - still no success).
Fastboot getvar all also drops an error:
C:\Android SDK\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.206.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34VW908233
(bootloader) imei: 354436054362833
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4222mV
(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.057s
I'm not a noob, I read carefully what to do when I get a new device, I know where to look for everything here and I've been flashing ROMs and doing all this stuff on my HTC devices for quite some time now. And yes, I have upgraded my HTC drivers.
It's possible that I missed something though. Nobody is perfect. I'm gratefull for every piece of help I get from you people.
Click to expand...
Click to collapse
Strange.. all i can see here is that in getvar all is no error, this "failed"message appears everytime.
So basically now the only thing you can access is the bootloader?

herwegan said:
Strange.. all i can see here is that in getvar all is no error, this "failed"message appears everytime.
So basically now the only thing you can access is the bootloader?
Click to expand...
Click to collapse
Ok, then I don't have to be worried about the getvar all..
No, I can also boot the Stock ROM fine. I'm just not able to go custom at all.
Also, which might be of interest: Selecting factory reset in the recovery does NOTHING. Phone reboots, everything is still there. Software reset (from the ROM) works fine.

eisteh said:
Ok, then I don't have to be worried about the getvar all..
No, I can also boot the Stock ROM fine. I'm just not able to go custom at all.
Also, which might be of interest: Selecting factory reset in the recovery does NOTHING. Phone reboots, everything is still there. Software reset (from the ROM) works fine.
Click to expand...
Click to collapse
I suspect revone borked something. It's a hack; it happens. You probably need to RUU back to stock, as it sounds like you've messed up something important in your system settings.

iElvis said:
I suspect revone borked something. It's a hack; it happens. You probably need to RUU back to stock, as it sounds like you've messed up something important in your system settings.
Click to expand...
Click to collapse
And as there seems to be no RUU for HTC One O2 Germany.. I'm doomed?
EDIT: As recovery wasn't working before revone, maybe there already was a problem with the phone? I was so happy to get my phone back and now it's even worse than before...

eisteh said:
And as there seems to be no RUU for HTC One O2 Germany.. I'm doomed?
EDIT: As recovery wasn't working before revone, maybe there already was a problem with the phone? I was so happy to get my phone back and now it's even worse than before...
Click to expand...
Click to collapse
You couldchange your cid to htc___001 and flash the open europe RUU 1.28 and at least see if it helps. Then change cid back to O2 germany (not 100% sure if this is possible).

herwegan said:
You couldchange your cid to htc___001 and flash the open europe RUU 1.28 and at least see if it helps. Then change cid back to O2 germany (not 100% sure if this is possible).
Click to expand...
Click to collapse
Which would require s-off which doesn't work.

eisteh said:
Revone was granted root for the preparation process, everything went fine, I rebooted. Then, s-off failed. Now root started to drop errors (was something with memory can't be allocated) and revone gave me -1 and -6 errors.
Click to expand...
Click to collapse
After you ran revone -P, did you reboot with a manual hold of the power button or with adb command? Should use the power button.
I have found that the revone process works better when you don't change to su before ANY of the commands.
Also I have found that a lot of revone issues were adb related and changing to a different USB port or PC helped. On a few systems it worked much better to do all the commands with a terminal emulator on the device rather than an ADB shell session.
Perhaps see if any of those tips helps with a successful s-off.
Regarding your SU app issues, try to clear data from whatever SU app you are using and then reboot and then open the app and make sure it doesn't need the SU binaries updated.
Sometimes it can take 15-20 attempts to get revone to work. How much did you try?

crushalot said:
After you ran revone -P, did you reboot with a manual hold of the power button or with adb command? Should use the power button.
I have found that the revone process works better when you don't change to su before ANY of the commands.
Also I have found that a lot of revone issues were adb related and changing to a different USB port or PC helped. On a few systems it worked much better to do all the commands with a terminal emulator on the device rather than an ADB shell session.
Perhaps see if any of those tips helps with a successful s-off.
Regarding your SU app issues, try to clear data from whatever SU app you are using and then reboot and then open the app and make sure it doesn't need the SU binaries updated.
Sometimes it can take 15-20 attempts to get revone to work. How much did you try?
Click to expand...
Click to collapse
Yes, I did a manual reboot.
Revone is said to work without SU and therefore uses it's integrated rooting process. I'm not rooted otherwise, I'd rather have my recovery working and flash a custom ROM then
I tried to run revone like 10 times (on my old device it took me exactly one try), I will consider your tipps and try again.

[Q] Custom Rom/Recovery w/o tampered message?

Hello.
I just got my One, upgraded from the One X
I am very skilled regarding rooting, flashing custom roms, recoveries, etc. I just have a quick question.
Is it possible to install custom rom, custom recovery and turn the phone S-OFF - WITHOUT getting the tampered message?
- If no, tell me that
- If yes, read on
Second case: Does this RRU match my M7?
First of all, what have i done myself:
- Unlocked bootloader
- Installed TWRP
- Made a nandroid backup
- Relocked bootloader because i want to flash [ROM] Android Revolution HD 3.2 Google Edition | High Quality & Performance | Android 4.3 Jelly Bean | 2.14.1700.15
- Flashed latest firmware for my phone - 2.24.401.1 (the thread above states that its not needed but recommended)
- Got the TAMPERED message and wants to get rid of that (and return from HBOOT 1.54 to original HBOOT 1.44)
In order to get rid of that message, this guide state i must use "method 2", and as part of that method 2, i must find the correct RRU.
The following is the output of getvar all before firmware update:
(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: 1.29.401.16
(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: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 3980mV
(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.043s
Click to expand...
Click to collapse
And this is getvar all after firmware update:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(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: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4010mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
Click to expand...
Click to collapse
Will this RRU be for my phone: RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe
- I found it here: http://www.androidruu.com/index.php?developer=M7
I chose it as its the RRU for the M7 Europe model that gets closest to my original main version (1.29.401.16 vs 1.28.401.7), also the radio in that RRU is just a tad older than my own original radio.
Also, is it possible to downgrade like that (im quite certain it is, just want to be sure).
Kind Regards
TwinAdk

Wait, you was in 1.44 hboot and now you're on 1.54?
If yes, you can't get the s-off.
The tools for the S-OFF are working only in 1.44 hboot, and, i if read right, now you have the 1.54 and you can do nothing...

****, you are kidding me, right? And RUU downgrade is not an option? That will downgrade my RUU too.
Aside from S-OFF being down the toilet, are there any other downsides to Hboot 1.54?

TwinAdk said:
****, you are kidding me, right? And RUU downgrade is not an option? That will downgrade my RUU too.
Aside from S-OFF being down the toilet, are there any other downsides to Hboot 1.54?
Click to expand...
Click to collapse
You can't downgrade with any ruu if you don't have the S-OFF...
Nope, but now you can't remove the ****Tampered**** line and you can't get the S-OFF...

Guich said:
You can't downgrade with any ruu if you don't have the S-OFF...
Nope, but now you can't remove the ****Tampered**** line and you can't get the S-OFF...
Click to expand...
Click to collapse
God dammit.. Well, are there any downsides regarding custom roms, to having the 1.54 hboot? Also, is it likely S-OFF will ever be avail. with 1.54?

TwinAdk said:
God dammit.. Well, are there any downsides regarding custom roms, to having the 1.54 hboot? Also, is it likely S-OFF will ever be avail. with 1.54?
Click to expand...
Click to collapse
No, you can flash all rom, kernel, mod, theme that you want.
For the S-OFF, no, devs said that they will work on the tool for the S-OFF when the new update form htc will come with the 1.55 hboot

Guich said:
No, you can flash all rom, kernel, mod, theme that you want.
For the S-OFF, no, devs said that they will work on the tool for the S-OFF when the new update form htc will come with the 1.55 hboot
Click to expand...
Click to collapse
So when 1.55 hboot arrives, work will start for S-OFF for that HBOOT? Any ETA on 1.55?

TwinAdk said:
So when 1.55 hboot arrives, work will start for S-OFF for that HBOOT? Any ETA on 1.55?
Click to expand...
Click to collapse
Atm there are some leaks of android 4.3 and new hboot 1.55, but this isn't the update that we will get.
For the question, yes

Guich said:
Atm there are some leaks of android 4.3 and new hboot 1.55, but this isn't the update that we will get.
For the question, yes
Click to expand...
Click to collapse
Okay, thanks
Now that i booted the phone, my storage is not available and wifi does not turn on (it says enabling, but thats all) - great start! Any idea why?
Ill look into it tomorrow my self, im off to bed now... Guess the One X will be in service for a few more days...
EDIT: Im on a firmware thats NOT for the android version i have, i think thats the problem. I guess ill have to sideload the custom rom running 4.3, and get it running that way.
Freaking hell, no S-OFF!

You relocked your bootloader after the flash of the rom?
If yes, you have to unlock this, reflash the rom and the kernel, and do a wipe of cache and dalvik-cache...

Guich said:
You relocked your bootloader after the flash of the rom?
If yes, you have to unlock this, reflash the rom and the kernel, and do a wipe of cache and dalvik-cache...
Click to expand...
Click to collapse
I cannot flash the rom as my SD is unavail... Is it an option to sideload the ROM?

TwinAdk said:
I cannot flash the rom as my SD is unavail... Is it an option to sideload the ROM?
Click to expand...
Click to collapse
Flash the stock recovery and then do a factory reset in bootloader, this will fix your sd.
After flash a custom recovery and try to use the sideload

Guich said:
Flash the stock recovery and then do a factory reset in bootloader, this will fix your sd.
After flash a custom recovery and try to use the sideload
Click to expand...
Click to collapse
Hello.
I flashed the stock recovery, and factory reset the phone. It rebooted during factory reset (of course), and booted normally afterwards. Wifi and storage did however still not work.. From within android im told that the storage is "Unavailable" (ill post screenshots later) - and from TWRP, i am told that i have "Internal storage" of 28xxx mb available (not sure about the excact size, around 28 gb) - but i cannot mount it and make it available from windows.
I can see the phone in windows, as a HTC media unit, and browse the content (storage -> legacy -> more folders -> root of SD card with folders like "downloaded" etc - default folders). But when i get there i cannot create folders or files, i can only view the content.....?
1. I cannot downgrade with RRU, since im S-ON
2. My Wifi and storage SEEMS broke (i suspect its because i flashed the firmware mentioned earlier, and my android version is not happy with that firmware - someone with more insight are welcome to comment on my guessing here)
3. Sideloading the rom i want to use (based on android 4.3) seems to be the only option - but can i sideload when my SD is not available in recovery?
Starting to worry a bit here
And thank you for all your help so far :good: I didnt get to say that last evening.. Appriciate!
Kind Regards

Hello sir,
first of all, let me say you screwed up already when not researching XDA before doing an update. Since i have done so myself numerous times, let me advise you to make it a habit, when buying a new phone to specifically research downsides of updates before accepting any.
Particularly in the HTC world, it has become a common thing to only gain S-OFF while the phone is in early software states and loose this ability towards later releases. Until now, many HTC phones i have had to deal with, had issues with disabling security on later firmwares.
Then, the storage problem you describe could possibly be related to something i have seen a fair few times. What Guich told you to do is usually the ultimate trick to get it back working. But let me ask this first: were you able to access storage from windows normally before the update? Or could you also face a driver issue?
OK. Guich's comment did not help. You flashed the stock recovery from the firmware you run. Then you ran Factory Reset from within Bootloader? Or from within android? If the latter, try the first...
I will be putting up stock recoveries from different RUU's soon on my thread here: http://forum.xda-developers.com/showthread.php?t=2316726 but you also find them on the forum already by searching. Try different stock recoveries and factory reset from Bootloader.
Then, if that doesn't help, try to run the OTA 2.24 (which already runs on your phone!) again by booting into bootloader, then picking "Fastboot" there (use volume down and up to navigate and power to confirm) and then going to your adb/fastboot with a command window. Oh, connect phone to PC of course
Lets say you have adb and fastboot plus the dll files in C:\Android. Open a CMD window and do "CD C:\Android" to go there.
there, run "fastboot oem rebootRUU" (type exactly as i do here, omit the quotes though).
then, copy and paste the OTA file (obtain HERE) to the same folder (C:\Android).
For easier typing in CMD, rename the OTA to something short and simple like test.zip or whatever.
then go back to your CMD Window and type in "fastboot flash zip test.zip"
Since its the same hboot and firmware in the OTA like you have on phone and since this package is official and signed, your phone ---should--- accept the flash. If not (maybe because you got the wrong model ID or wrong CID) i wouldn't really know how to proceed. But you DID accept that OTA before so it MUST be for your phone or else it wouldn't have flashed in the first place.
If it flashes fine, boot your phone up and check if it fixed everything.
If not, run the check for software update in Settings/Info/ and see if there is already an official OTA for your phone available that brings you past the 2.24. If not, download one of the inofficial OTA's and --- hope --- that you can flash it. Like 3.18 or 3.22. The first is for Asia/Taiwan though and will almost certainly NOT flash on your phone and the second is BrightstarUS and for the DEV edition and will also almost certainly not flash. But its worth a try.
beyond that, i have no more valuable tips. Only thing I would try is to flash CWM and do a clear storage, wipe data, wipe everything there. But be sure to have your nandroid ready if you do that. CWM uses a slightly different formatting method so it could possibly correct issues. In the past, i have read about screwed up SDcards related to CWM formatting more often than those that got screwed up by TWRP though. So its not exactly ideal to play with CWM on a phone that has already issues with its partition. But if i was desperate, i would do it anyway.
If that doesnt help or make it worse, do the very same thing on TWRP, pick the "wipe Data" option which prompts you to type "yes" into an input line. This will once again format your SD with a different method. It could possible correct this problem.
DO NOT attempt to screw around with the SD Partition using tools like MiniTool or EASUS if you can access the sd from them at all!
The SD Card is an EXT4 file system and cannot be formatted with FAT or NTFS from windows. If you do that, the phone wont work at all anymore. The exact parameters to format the partition externally are not known to me and i doubt you can address the partition from within windows at all. Maybe it works under linux...
Sorry. Cant be much help here. If that all doesnt work, just flash stock recovery back and restore your stock nandroid and send it in for repair. Them service dudes will have the right RUU and fix it for you.
[EDIT]
Oh and before i forget: if you can fix it with these tips, you owe me one
You have to flash Team Venom's ViperOne then instead of ARHD! :laugh:

Aroma installer is running now!! So excited to see the result! I sideloaded the zip, via adb sideload Nice short article on it here: http://teamw.in/ADBSideload
Will return with outcome :highfive::fingers-crossed::fingers-crossed::fingers-crossed:
EDIT: Its back! Running custom rom with sd card avail and wifi working! Pew, saved by adb sideload, increddible!

[Q] [HTC One] Bricked after 4.4 update

I'm the next one in line with the same question, but no other answers helped me yet. What I did wrong was adb sideloading the OTA file using CWM recovery. That part I understand, so completely my own fault.
However, the update is still on the SD card and I tried to load stock recovery via fastboot so that I can install OTA from the SD card. What I get is something I find a lot of others have as well; the recovery fails to mount sd card 5 times. When I try to "Apply from SD card" I get an error "Check cid failed! --invalid operation--" and the phone reboots. The same error happens to users in many places, an example here: androidcentral . com/how-manually-update-your-google-play-edition-htc-one-android-44-kitkat
I think I can recover the phone with instructions (I can't post URLs yet) that will install a different recovery and uses adb sideload. But it also erases the sdcard which I try to avoid.
So, Is there anyone who can advice me what to do? If it cannot be avoided that my sdcard will be wiped; so be it. But I will manage doing that, I'm looking for an alternative at the moment. I suspect that if I find the correct recovery version that it will "mount" the "sdcard" (which I think is an emulation because the HTC One has no sdcard??) will also allow me to recover my phone with sdcard intact. But I find it difficult to find the correct recovery.img. I've tried two versions *can't find numbers back right now, will post if needed*.
HTC One, converted into GPe (so tampered and unlocked)
HBOOT 1.44

ruud.walraven said:
I'm the next one in line with the same question, but no other answers helped me yet. What I did wrong was adb sideloading the OTA file using CWM recovery. That part I understand, so completely my own fault.
However, the update is still on the SD card and I tried to load stock recovery via fastboot so that I can install OTA from the SD card. What I get is something I find a lot of others have as well; the recovery fails to mount sd card 5 times. When I try to "Apply from SD card" I get an error "Check cid failed! --invalid operation--" and the phone reboots. The same error happens to users in many places, an example here: androidcentral . com/how-manually-update-your-google-play-edition-htc-one-android-44-kitkat
...
HTC One, converted into GPe (so tampered and unlocked)
HBOOT 1.44
Click to expand...
Click to collapse
Ruud, I don't know if I completely understand your story, but you are able to get into stock recovery right? If so, do not choose 'Apply from SD card', but 'Apply from phone'. I got the same error messages (fails to mount SD card...), but if the OTA file is on your phone, you have to choose phone storage.

mbroeders said:
Ruud, I don't know if I completely understand your story, but you are able to get into stock recovery right? If so, do not choose 'Apply from SD card', but 'Apply from phone'. I got the same error messages (fails to mount SD card...), but if the OTA file is on your phone, you have to choose phone storage.
Click to expand...
Click to collapse
I should have mentioned that the other options (apply from phone and apply from cache) don't work either. One thing I am unsure about is if this is indeed the stock recovery.img I put back on. Is there a single recovery.img for HTC One, or a list where I can find which one came standard so I can put it back. My suspicion is that that recovery will work, although the guy I bought the phone from may have installed recovery/images that may have reformatted everything in a way that stock won't work any longer...

I noticed most people need to post fastboot getvars all. Makes sense to figure out what software I need so here it is:
(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: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: 1234567890AB
(bootloader) imei: 123456789000000
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4295mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))

ruud.walraven said:
I noticed most people need to post fastboot getvars all. Makes sense to figure out what software I need so here it is:
(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: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: 1234567890AB
(bootloader) imei: 123456789000000
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4295mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
Click to expand...
Click to collapse
Are you sure this is the GPe version? I get a feeling that you have the Sense version and then it won't work of course. (sorry if I'm wrong)
Sent from my HTC One using XDA Premium 4 mobile app

I've tried a whole range of things that didn't help. Don't want to preserve the sd card any longer.
Flashed recovery versions: 1.29.401.12, 2.24.401.8, 3.07.1700.1 and 3.58.1700.5.
Neither version was able to reinstall from sdcard. But I found out later that I may have done *something* to the sdcard (see CWM below)
Next I flashed CWM to try flashing a nandroid. However during the process I couldn't browse my sdcard anymore. Before flashing above recoveries I had CWM and then I could see all files. May have done something wrong.
After trying the mentioned nandroid a few times I realized that I am S-ON.
I have been trying to get S-OFF for the last few hours because I found a file I want to use on my phone (See htc1guru . com/2013/11/android-4-4-kit-kat-google-edition-3-58-1700-5-ruu-ota-files/). I've looked at Moonshine, but my phone is not in the list of supported rom versions (1.29.401.12). I tried Revone, but get error = 1.
So now I'm not sure what to do next!!

mbroeders said:
Are you sure this is the GPe version? I get a feeling that you have the Sense version and then it won't work of course. (sorry if I'm wrong)
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am absolutely sure I have a Sense version originally. I bought it from someone who unlocked the bootloader and replaced the sense firmware with GPe. OTA was working because I OTA-ed to 4.3. I've contacted him this morning, but he says to have no idea what files he used.

you bought it from an idiot.
you can't properly convert to GPE with s-on. That's why your hboot, mainver and cid are all wrong for a GPE conversion.
I assume you're boot-loader unlocked? flash cwm or TWRP. Then restore this nandroid: http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-htc__102-1-29-401-12-2013-05-16-zip/
after restoring that nandroid try to s-off with revone and or rumrunner.
Revone: http://forum.xda-developers.com/showthread.php?t=2314582
Rumrunner: http://forum.xda-developers.com/showthread.php?t=2488772
once your s-off you can properly convert your phone to GPE. The problem wasn't just that you flashed it with a custom recovery but that the phone was never in a proper state to receive OTA for GPE!
use the RUU from here once your s-off to convert to GPE 4.4 : http://forum.xda-developers.com/showthread.php?t=2358781
you'll also want to go supercid with fastboot oem writecid 11111111
ruud.walraven said:
I am absolutely sure I have a Sense version originally. I bought it from someone who unlocked the bootloader and replaced the sense firmware with GPe. OTA was working because I OTA-ed to 4.3. I've contacted him this morning, but he says to have no idea what files he used.
Click to expand...
Click to collapse

I'm downloading all required files right now. In the meantime looking into everything to make sure to not further brick it once S-OFF. Tricky business!
ipfreelytech said:
you'll also want to go supercid with fastboot oem writecid 11111111
Click to expand...
Click to collapse
There's one question I found: according to this thread SuperCid 11111111 doesn't get OTA and the best bet for me would be HTC__001. Is that correct, or can I also choose from HTC_001 or GOOGL001? (the latter I remember reading is supposed to be good too). In any case ... I suppose I can best follow your instructions and I can change the cid to whatever needed afterwards anyway.
edit: It took 1.5 hours to download the nandroid, but something must have gone wrong because the file cannot be opened by winzip nor 7z. After the failed opening of the file I've md5-ed the entire zip file and it doesn't match the checksum on the download link. So started download again...

I have a problem; the download stops at different points, never completing. Must be a problem in the connection or at htc1guru. Is there an alternative file/download/mirror I can use as well? Have searched google for the same file with no results.

I was finally able to download the file through FF. Every time the download failed I started again, but paused and replaced the .part file with the failed download. When you resume FF detects the last bit and resumes from there. Best part was that I got my Chrome 900+MB download and used that as .part file. So I could resume nearly finished. Ran the checksum to be sure nothing funny had happened because of my tinkering. To quote Borat: great success.
However, after restoring the nandroid through CWM I tried both Revone and Rumrunner. Revone fails error = 1 and Rumrunner assumes I start from my homescreen (which I can't). A bit unwise, but I tried anyway from both fastboot and CWM but in neither case will Rumrunner continue. It claims there is no ADB connection (even though the phone shows up in adb devices).
So I am stuck for now. Still looking at as many posts about S-OFF as I can to see if I find some vital piece of inof I missed or something I can still try. But for now I'd like some idea's how to achieve S-OFF..

What is the date in your hboot version? If after June, then revone won't work. Have you tried moonshine?

SaHiLzZ said:
What is the date in your hboot version? If after June, then revone won't work. Have you tried moonshine?
Click to expand...
Click to collapse
hboot has a date? Hboot is 1.44 and bootloader start screen says apr 12 2013, is that what you mean?
My version (1.29.401.12) is not supported by moonshine for as far as I can tell.
I also notice now that fastboot getvars bootmode says: fastboot. Shouldn't this be disabled for revone and/or rumrunner?
ruud.walraven said:
...
(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: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: 1234567890AB
(bootloader) imei: 123456789000000
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4295mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
...
Click to expand...
Click to collapse

Just a question: In a sense I can't have messed anything up that bad because I'm S-ON. So if I would install the 4.3 release that was on the device before I sideloaded the 4.4 OTA through CWM, wouldn't it just work because all things point to the correct places? Since I broke it with adb sideloading, I could restore the device probably just as well, right?
In any case; I still would want to S-OFF my device to go through ipfreelytech's steps and get a functioning 4.4 GPe. But So far I found that Moonshine doesn't support my device and for both rumrunner and revone I need to start from a booted up android homescreen. So all three options don't seem to work. Did I really brick my phone, or is there still hope??

I had same problem on my device. I decided to install CWM instead of TWRM, downloaded RUU 4.2.2 and flashed it. Next I get update to 4.3 and 4,4 later and now everytning works perfect.

ziolooo said:
I had same problem on my device. I decided to install CWM instead of TWRM, downloaded RUU 4.2.2 and flashed it. Next I get update to 4.3 and 4,4 later and now everytning works perfect.
Click to expand...
Click to collapse
Willing to try, but I don't see the RUU file needed on http://forum.xda-developers.com/showthread.php?t=2428276 nor on htc1guru.com. This should be done through fastboot oem rebootRUU, right? If everything works I'm don. if OTA or some functions don't wrok I maybe able to S-OFF and follow previous instructions till the end. And if it doesn't work I'm back to where I am now anyway.

ruud.walraven said:
Willing to try, but I don't see the RUU file needed on http://forum.xda-developers.com/showthread.php?t=2428276 nor on htc1guru.com. This should be done through fastboot oem rebootRUU, right? If everything works I'm don. if OTA or some functions don't wrok I maybe able to S-OFF and follow previous instructions till the end. And if it doesn't work I'm back to where I am now anyway.
Click to expand...
Click to collapse
Here you have good tutorial how to install RUU:
http://htc-one.wonderhowto.com/how-...with-bootloader-recovery-ota-updates-0148068/
Download and flash RUU from this site.

ziolooo said:
Here you have good tutorial how to install RUU:
http://htc-one.wonderhowto.com/how-...with-bootloader-recovery-ota-updates-0148068/
Download and flash RUU from this site.
Click to expand...
Click to collapse
Thanks for the link. That won't work though because I'm still trying to achieve S-OFF which is a prerequisite to follow that guide.

ruud.walraven said:
Thanks for the link. That won't work though because I'm still trying to achieve S-OFF which is a prerequisite to follow that guide.
Click to expand...
Click to collapse
http://htc-one.wonderhowto.com/how-to/set-your-htc-one-s-off-using-moonshine-windows-0147992/

ziolooo said:
http://htc-one.wonderhowto.com/how-to/set-your-htc-one-s-off-using-moonshine-windows-0147992/
Click to expand...
Click to collapse
I already tried that.
ruud.walraven said:
...
In any case; I still would want to S-OFF my device to go through ipfreelytech's steps and get a functioning 4.4 GPe. But So far I found that Moonshine doesn't support my device and for both rumrunner and revone I need to start from a booted up android homescreen. So all three options don't seem to work. Did I really brick my phone, or is there still hope??
Click to expand...
Click to collapse

[Q] One bricked when attempting a return to stock

Hello there everyone, sorry to add another 'bricked' thread to the first page but it seems the more I try to fix my phone on my own, the deeper the hole I'm digging becomes.
About a week ago I installed Cyanogenmod via their installer. It was nice and straightforward but I soon began to miss Sense 5.5 so I set out to return my phone to stock. This was a few days ago and since then I have learned about flashing, rooting, fastboot etc., but I am now stuck where I cannot make it past the Cyanogenmod logo and I have absolutely no idea where to start fixing things. I can't make any progress as I do not have USB debugging mode enabled (nor can I enable it now) and I have no backup other than the automatic backup to Dropbox.
Below is my getvar output. Phone is 'TAMPERED' and 'UNLOCKED'. Oh, the phone is not rooted and was bought in Hong Kong but I use o2 in England. Please let me know If there is any more information I need to include.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.63.708.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Oops
(bootloader) imei: nothing to see here
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__622
(bootloader) battery-status: good
(bootloader) battery-voltage: 4300mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-14eb688c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Thanks for taking the time to read this, any pointers would be very much appreciated

I'm no expert, but maybe this can help.
Here's what I did with mine when I thought I bricked it. Keep in mind that I had a micro-USB to USB OTG cable. (costs less than $5)
Mine was bootloader unlocked, s-on but with hboot 1.55 or 1.54.
1. install TWRP recovery (openrecovery-twrp-2.6.3.3-m7.img) using fastboot.
2. Boot into TWRP recovery, then using OTG cable, mount a USB flash drive that has a installable zip image of the whole thing. I just used one from here:
http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
I got the "Download stock odexed 4.19.401.8" since I wanted to return it to stock like so I can return it.
I flashed it with that, and it would reboot into stock-like Android. I still had a bootloader from GoogleExperience version, and I accidentally did S-on before fixing these so I was screwed.
Anyways, that's how I got mine back to working state. After that, I couldn't get S-off (hboot 1.54) no matter what even using Rumrunner. Trying to get S-off again, I had to reflash the kernel with some other custom kernel, and then was able to do rumrunner to get s-off again. From that point, everything was easy, and I was able to reinstall real AT&T stock android using their RUU exe file. After that it installs OTA updates too.

kelvov said:
Hello there everyone, sorry to add another 'bricked' thread to the first page but it seems the more I try to fix my phone on my own, the deeper the hole I'm digging becomes.
About a week ago I installed Cyanogenmod via their installer. It was nice and straightforward but I soon began to miss Sense 5.5 so I set out to return my phone to stock. This was a few days ago and since then I have learned about flashing, rooting, fastboot etc., but I am now stuck where I cannot make it past the Cyanogenmod logo and I have absolutely no idea where to start fixing things. I can't make any progress as I do not have USB debugging mode enabled (nor can I enable it now) and I have no backup other than the automatic backup to Dropbox.
Below is my getvar output. Phone is 'TAMPERED' and 'UNLOCKED'. Oh, the phone is not rooted and was bought in Hong Kong but I use o2 in England. Please let me know If there is any more information I need to include.
Thanks for taking the time to read this, any pointers would be very much appreciated
Click to expand...
Click to collapse
Do you have a nandroid backup of your phone? Remove IMEI and S/N from your last post!!

hp79 said:
I'm no expert, but maybe this can help.
Here's what I did with mine when I thought I bricked it. Keep in mind that I had a micro-USB to USB OTG cable. (costs less than $5)
Mine was bootloader unlocked, s-on but with hboot 1.55 or 1.54.
1. install TWRP recovery (openrecovery-twrp-2.6.3.3-m7.img) using fastboot.
2. Boot into TWRP recovery, then using OTG cable, mount a USB flash drive that has a installable zip image of the whole thing. I just used one from here:...
I got the "Download stock odexed 4.19.401.8" since I wanted to return it to stock like so I can return it.
I flashed it with that, and it would reboot into stock-like Android. I still had a bootloader from GoogleExperience version, and I accidentally did S-on before fixing these so I was screwed.
Anyways, that's how I got mine back to working state. After that, I couldn't get S-off (hboot 1.54) no matter what even using Rumrunner. Trying to get S-off again, I had to reflash the kernel with some other custom kernel, and then was able to do rumrunner to get s-off again. From that point, everything was easy, and I was able to reinstall real AT&T stock android using their RUU exe file. After that it installs OTA updates too.
Click to expand...
Click to collapse
Thanks for the info, will have to try it tomorrow after buying a cable
alray said:
Do you have a nandroid backup of your phone? Remove IMEI and S/N from your last post!!
Click to expand...
Click to collapse
Unfortunately no, I wrongly assumed a simple backup would have sufficed in the event anything went wrong. Never again. Oops, that for the heads up on that

You should be able to push ARHD 31.6 and be ok
sent from my mobile device

[Q] Restoring 100% to stock, not working as it should...

Hi guys,
First of all, I did read all the topics conserning to RUU, S-On/S-Off, rumrunner, moonshine, firewater, revone, and so on but I can't seem to figure out how to properly do this.
Currently the HTC is running MIUI v5 4.5.16 JB4.2. But for warranty it has to go back to the store and I want to restore it to completly stock ROM etc. without any evidence I had a custom ROM running.
What I did was, follow the steps to unlock the bootloader, flash a custom recover (TWRP v2.6.3.0) and finally root it after MIUI was flashed.
The info you guys prolly need are as followed:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.26.3263.05
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.161.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: .................
(bootloader) imei: ................
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-09ff2ded
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.038s
Click to expand...
Click to collapse
I tried to get S-Off but I keep getting strange errors on all of the given methods. This should work somehow I guess but how? Can somebody give me some kind of "roadmap" how to do it properly?
Currently fastboot shows:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4A.26.3263.05
OpenDSP-v32.120.274.0909
OS-4.19.161.11
eMMC-boot 2048MB
Mar 5 2014,15:58:33.0
Click to expand...
Click to collapse
At the moment I'm downloading "RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe". But I already noticed that if I turn S-On (fastboot oem lock) then the phone is stuck in fast boot mode...
Thanks!

I think S-off is danger may u brick ur phone, it's better to leave it

ahmed blue said:
I think S-off is danger may u brick ur phone, it's better to leave it
Click to expand...
Click to collapse
Yeah but what if I need it to go back to stock ROM?
Now it's running stock ROM but I still get "TAMPERED" and "UNLOCKED" in the bootloader. I once went into the stock recovery, and once rebooted it reset itself and everything was back factory install -again- ...?
This is the fastboot output right now after flashing Guru Reset M7 2.24.161.1.zip :
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.161.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ...................
(bootloader) imei: ....................
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4185mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-09ff2ded
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
The OTA update to 4.3 even fails once it reboots itself for installation. Something wrong or normal?
EDIT:
I've done "fastboot oem lock" and now it's showing (as expected) "RELOCKED".

BETA911 said:
Yeah but what if I need it to go back to stock ROM?
Now it's running stock ROM but I still get "TAMPERED" and "UNLOCKED" in the bootloader. I once went into the stock recovery, and once rebooted it reset itself and everything was back factory install -again- ...?
This is the fastboot output right now after flashing Guru Reset M7 2.24.161.1.zip :
The OTA update to 4.3 even fails once it reboots itself for installation. Something wrong or normal?
EDIT:
I've done "fastboot oem lock" and now it's showing (as expected) "RELOCKED".
Click to expand...
Click to collapse
Yup it will do, the only way to get rid of those flags tampered and unlocked / relocked is to go s-off, which strange messages are you getting whilst trying to s-off ?
I have a backup of the Vodafone Rom which you can restore through twrp, I'll send a link when I get home in a couple of hours, but it won't get rid of those flags, 401.RUU is the wrong RUU, you need 161.
---------- Post added at 05:43 PM ---------- Previous post was at 05:34 PM ----------
Ps there is no danger going s-off, as long as your flashing the correct software for your phone, the only danger is when you don't know what your doing and try to flash something wrong, it won't warn you, won't error and won't fail to flash, but at reboot it also won't come back on again.

Seanie280672 said:
Yup it will do, the only way to get rid of those flags tampered and unlocked / relocked is to go s-off, which strange messages are you getting whilst trying to s-off ?
I have a backup of the Vodafone Rom which you can restore through twrp, I'll send a link when I get home in a couple of hours, but it won't get rid of those flags, 401.RUU is the wrong RUU, you need 161.
---------- Post added at 05:43 PM ---------- Previous post was at 05:34 PM ----------
Ps there is no danger going s-off, as long as your flashing the correct software for your phone, the only danger is when you don't know what your doing and try to flash something wrong, it won't warn you, won't error and won't fail to flash, but at reboot it also won't come back on again.
Click to expand...
Click to collapse
Well... It said it had a OTA update (like before) to 4.3 and I downloaded it. Reboot, installed, reboot --> bootloop. Now it's "HTC - quietly brilliant", black screen for couple of seconds and reboot to start from HTC logo again...
It's really beginning to piss me of.
But anyway, thanks for the help! A TWRP backup of 161 would be nice, then I'll install that one. The servers at htc1guru are giving me headache, speed is only between 50 and 250 kb/sec! I tried to download more then once but they keep failing on me when they reach bigger sizes and at this speed it's really really annoying to start over again...
Does "M7 CWM Nandroid Backup CID VODAP102 1.29.161.7" work for me? I guess not because it's 1.29 and I already have a higher version so it will give me the touchscreen issues?
To be honest, if this phone finally makes it to the store for repair I hope they can't repair it and let me choose an other phone. I had multiple Android phones the past years (with sometimes more then 2-3 different roms per week) and never had any of these long stretching problems!

The problem your having with the ota sounds like whilst you were installing the guru reset file, you must select to wipe data and also install stock recovery, it will fail without stock recovery.

Well, I did select to install the stock recovery and stock radio in the aroma installer. So I'm out of clues why it's giving me so much problems...
EDIT:
I unlocked the bootloader again and flashed TWRP. I'll try with your Vodafone image once you have time to share it with me. Already big thanks for the help!

here's the backup, you will need to extract the zip file and put the folder named backup into SDCARD/TWRP/BACKUPS/"your device serial number/
https://drive.google.com/uc?export=download&confirm=5940&id=0B_nEcSZr5peRZnpMSHRPRjlzX2c
This will put you on Vodafone 4.4.2 with sense 5.5, however you cant send your phone back until you have got rid of those 2 flags in the bootloader, only way to do that is s-off.
Ignore the folder called recovery, its just TWRP recovery to flash.
After installing, download the stock recovery from the link below and flash it to get OTAs
http://d-h.st/Cyq
Hit the thanks button please.

Just finished installing it! It works so far, although it came up with a new 5.16.161.2 update right now (already has been downloaded...). What should I do?
Currently it's still in TAMPERED and UNLOCKED state with TWRP installed.

BETA911 said:
Just finished installing it! It works so far, although it came up with a new 5.16.161.2 update right now (already has been downloaded...). What should I do?
Currently it's still in TAMPERED and UNLOCKED state with TWRP installed.
Click to expand...
Click to collapse
there is no way out of this without s-off, I don't even understand why you are putting efforts on installing ota/guru reset/nandroid backup at this point.
you are on hboot 1.56 means you should try to s-off using firewater.
then you'll be able to remove the tampered flag and set the bootload back to "LOCKED" (not RE-LOCKED)
follow guide linked in my signature for going back to stock
try to s-off using firewater + arhd 31.6 rom

alray said:
there is no way out of this without s-off, I don't even understand why you are putting efforts on installing ota/guru reset/nandroid backup at this point.
you are on hboot 1.56 means you should try to s-off using firewater.
then you'll be able to remove the tampered flag and set the bootload back to "LOCKED" (not RE-LOCKED)
follow guide linked in my signature for going back to stock
try to s-off using firewater + arhd 31.6 rom
Click to expand...
Click to collapse
I know. I tried to get s-off but none of the given tools succeeded. They all complete their full cycle and eventually after the last reboot I go and check the state and it still says s-on... Then I did read I need a proper ROM so the tools can work (better). I tried to install ARHD like you mention, but after flashing it was stuck in a bootloop again. Clearing the cache and davlik didn't solve it.
At the moment I only need to know if it's safe to update to the new 5.16.161.2 update while it's unlocked... I got TWRP installed but I know I have to flash the stock recovery in order to make the update work. But I'm afraid I'm going to brick it again if I lock it again, as I don't know if it's needed to let the update complete without any errors.