How do you relock a U11 to receive OTA updates?

[mauiblue]

Aloha to all. So after learning the hard way of relocking my U11 and bricking it (it's on its way to HTC in Texas) what would have been the safest way in relocking my phone to get the OTA update?

When I started getting the OTA update nag screen a couple weeks ago I had the phone download the update file and chose the option to install the update. But as you guys know a unlocked phone will not allow the OTA update to install. I then used ADB to relock and that's when I got my phone in trouble.

Before all this drama, my phone was working fine and I had a few apps installed that may have aided me to do the transition from unlock to relock to get the OTA update then back to unlock. I had the official TWRP app and Magisk installed.

Could someone please explain to me what would have been the best course of action I should have undertaken to have smoothly updated my phone going from having an unlocked phone, to installing the OTA update, to relocking the phone? I would love to understand and follow a failsafe bulletproof method of doing this process (installing the OTA update when my phone is in the unlocked state) I really would appreciate it if the senior members could take the time and guide me or at the very least post some links for the specific process. Aloha and mahalo.

Sent from my HTC6545LVW using Tapatalk

 

[mroshaw]

You don't need to "relock" to receive OTA. When I needed to revert my FW to an "official" build, I simply used an RUU to restore and immediately received an OTA to the latest build. I then re-flashed TWRP and Magisk to re-root. At no point did I touch the bootloader after initially unlocking it.

 

[mauiblue]

You don't need to "relock" to receive OTA. When I needed to revert my FW to an "official" build, I simply used an RUU to restore and immediately received an OTA to the latest build.

So no need to relock? I'm sorry for being obtuse but what do you mean to "revert my FW to an "official" build, I simply used an RUU to restore and immediately received an OTA to the latest build"? How do you revert to official build and where do you find the RUU file to be restore?

Then re-flashed TWRP and Magisk to re-root. At no point did I touch the bootloader after initially unlocking it.

How does TWRP and Magisk utilized to reroot? I'm sorry for all the questions and thanks for your reply.



Sent from my HTC6545LVW using Tapatalk

 

[mroshaw]

I think these sorts of challenges and questions are what XDA is all about, and it's often through mistakes that we learn the ins and outs of device modification. Happy to help, as I've been in similar positions during my time tweaking phones and devices.

How do you revert to official build and where do you find the RUU file to be restore?

https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048
The Holy Grail, in forum post form, for all U11 owners who need to recover their devices. From here, you can pretty much recover from any sort of soft brick situation. This has got me out of trouble many, many times. Having an unlocked bootloader does NOT stop you receiving OTA - having a customer recovery, such as TWRP, prevents an OTA from being installed automatically but it's still perfectly possible to manually apply an OTA with unlock and TWRP.

How does TWRP and Magisk utilized to reroot?

TWRP (replacement recovery) and Magisk (systemless root tool) are awesome tools that allow you flash custom ROMs, run root tools and hide root from prying eyes. Fairly typical to install a custom recovery and root, as part of unlocking and preparing a device for a custom ROM or some proper tweaking. Restoring from an RUU puts you "back to square one", in a good way, that requires a fresh installation of these tools if you want to continue to mod your device.
The bottom line is that you REALLY need to have an understanding about what locked / unlocked bootloader, custom recovery and root means to your device. You need to understand the power that ADB gives you and be aware of the risk inherent: ADB is the Android Debugger - it's a developer tool, not typically for normal consumption. As you've unfortunately discovered, Android gives you a lot of flexibility, often at the device manufacturers discretion (I'm looking at you Huawei), to modify your device using powerful Android tools. Without a full understanding of the consequences, it's perfectly possible to irrecoverably brick your device. When it all falls in to place, however, there's a sense of enormous satisfaction in having control over the device you've spent hundreds of bucks on.

 

[mauiblue]

I think these sorts of challenges and questions are what XDA is all about, and it's often through mistakes that we learn the ins and outs of device modification. Happy to help, as I've been in similar positions during my time tweaking phones and devices.

https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048
The Holy Grail, in forum post form, for all U11 owners who need to recover their devices. From here, you can pretty much recover from any sort of soft brick situation. This has got me out of trouble many, many times. Having an unlocked bootloader does NOT stop you receiving OTA - having a customer recovery, such as TWRP, prevents an OTA from being installed automatically but it's still perfectly possible to manually apply an OTA with unlock and TWRP.

TWRP (replacement recovery) and Magisk (systemless root tool) are awesome tools that allow you flash custom ROMs, run root tools and hide root from prying eyes. Fairly typical to install a custom recovery and root, as part of unlocking and preparing a device for a custom ROM or some proper tweaking. Restoring from an RUU puts you "back to square one", in a good way, that requires a fresh installation of these tools if you want to continue to mod your device.
The bottom line is that you REALLY need to have an understanding about what locked / unlocked bootloader, custom recovery and root means to your device. You need to understand the power that ADB gives you and be aware of the risk inherent: ADB is the Android Debugger - it's a developer tool, not typically for normal consumption. As you've unfortunately discovered, Android gives you a lot of flexibility, often at the device manufacturers discretion (I'm looking at you Huawei), to modify your device using powerful Android tools. Without a full understanding of the consequences, it's perfectly possible to irrecoverably brick your device. When it all falls in to place, however, there's a sense of enormous satisfaction in having control over the device you've spent hundreds of bucks on.

Thanks for the post. I also was wondering what happens when a phone is totally bricked. What does HTC do to repair a phone that was relocked and flashed incorrectly? Is a physical part replaced on the phone?

Sent from my HTC6545LVW using Tapatalk

 

[mroshaw]

Thanks for the post. I also was wondering what happens when a phone is totally bricked. What does HTC do to repair a phone that was relocked and flashed incorrectly? Is a physical part replaced on the phone?

I imagine it depends on a case by case basis and on which support center you end up dealing with. I'd be surprised if HTC don't have some sort of toolset to restore a bricked device without a physical part replacement, but who knows. Could be costly if they do insist on a physical repair.

 

[mauiblue]

I imagine it depends on a case by case basis and on which support center you end up dealing with. I'd be surprised if HTC don't have some sort of toolset to restore a bricked device without a physical part replacement, but who knows. Could be costly if they do insist on a physical repair.

Well I could have used my Asurion phone insurance to replace the phone and the deductible would have been $150 but they would have replaced the phone with a Google Pixel. So if repair/replacement would be about that much, I'm fine with that.

 

[mroshaw]

Well I could have used my Asurion phone insurance to replace the phone and the deductible would have been $150 but they would have replaced the phone with a Google Pixel. So if repair/replacement would be about that much, I'm fine with that.

Well, best of luck from me! Keep us posted as to HTCs response!

 

[Kaepernick]

I think these sorts of challenges and questions are what XDA is all about, and it's often through mistakes that we learn the ins and outs of device modification. Happy to help, as I've been in similar positions during my time tweaking phones and devices.

https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048
The Holy Grail, in forum post form, for all U11 owners who need to recover their devices. From here, you can pretty much recover from any sort of soft brick situation. This has got me out of trouble many, many times. Having an unlocked bootloader does NOT stop you receiving OTA - having a customer recovery, such as TWRP, prevents an OTA from being installed automatically but it's still perfectly possible to manually apply an OTA with unlock and TWRP.

TWRP (replacement recovery) and Magisk (systemless root tool) are awesome tools that allow you flash custom ROMs, run root tools and hide root from prying eyes. Fairly typical to install a custom recovery and root, as part of unlocking and preparing a device for a custom ROM or some proper tweaking. Restoring from an RUU puts you "back to square one", in a good way, that requires a fresh installation of these tools if you want to continue to mod your device.
The bottom line is that you REALLY need to have an understanding about what locked / unlocked bootloader, custom recovery and root means to your device. You need to understand the power that ADB gives you and be aware of the risk inherent: ADB is the Android Debugger - it's a developer tool, not typically for normal consumption. As you've unfortunately discovered, Android gives you a lot of flexibility, often at the device manufacturers discretion (I'm looking at you Huawei), to modify your device using powerful Android tools. Without a full understanding of the consequences, it's perfectly possible to irrecoverably brick your device. When it all falls in to place, however, there's a sense of enormous satisfaction in having control over the device you've spent hundreds of bucks on.

I've tried just about everything I can think of. I'm pretty sure mine is completely bricked.

Nothing works. All RUUs I've tried have failed. I have the EU model. I wanted to use the US unlocked ruu so I rooted, achieved s-off, and changed the cid and mid to match it. I thought I had to relock the phone to flash the RUU like in previous htc phones. I tried the RUUs and they failed. I unlocked it again to try something else, which factory reset the phone. Then I foolishly locked it again thinking I'd try a different ruu. That failed too. When I rebooted, the phone went back to s-on. I cannot unlock the bootloader again because I can't access the OS. It opens to a screen I need a password for and I don't have a password for it.

I thought I was fine, though. On previous htc phones, I could still access twrp. If I factory reset, I could access the OS again and unlock the bootloader. This one gave me a screen that the phone is corrupt and won't boot, so I can't access recovery at all.

Stuck between a rock and a hard place. I hope you get your phone in working order Maui.

Sent from my HTC 10 using Tapatalk

 

[mauiblue]

I've tried just about everything I can think of. I'm pretty sure mine is completely bricked.

Nothing works. All RUUs I've tried have failed. I have the EU model. I wanted to use the US unlocked ruu so I rooted, achieved s-off, and changed the cid and mid to match it. I thought I had to relock the phone to flash the RUU like in previous htc phones. I tried the RUUs and they failed. I unlocked it again to try something else, which factory reset the phone. Then I foolishly locked it again thinking I'd try a different ruu. That failed too. When I rebooted, the phone went back to s-on. I cannot unlock the bootloader again because I can't access the OS. It opens to a screen I need a password for and I don't have a password for it.

I thought I was fine, though. On previous htc phones, I could still access twrp. If I factory reset, I could access the OS again and unlock the bootloader. This one gave me a screen that the phone is corrupt and won't boot, so I can't access recovery at all.

Stuck between a rock and a hard place. I hope you get your phone in working order Maui.

Sent from my HTC 10 using Tapatalk

I know that I will get the phone repaired (knock on wood) just as long there isn't any issues of the phone getting lost while being in the repair department. I found another thread regarding U11 owners having a very difficult time communicating with the HTC customer service department. Some members are saying they have to wait months (3, 4, 6 months) to finally find a resolution. One member says it only took 4 weeks from start of the repair to actually receiving the U11 back. I will bite the bullet and see how long I can stay in HTC Purgatory. But I really need a phone so I might just buy the U12+ I got a few discount codes that will make the phone cheaper but not a whole lot. I've got to decide soon because the codes are expiring soon,.

BTW, I wish you all the best with getting your phone repaired or replaced. I like HTC and can't see going with a Samsung or Apple.

 

[MoshPuiu]

Aloha to all. So after learning the hard way of relocking my U11 and bricking it (it's on its way to HTC in Texas) what would have been the safest way in relocking my phone to get the OTA update?

What OTA update? Don't bother for once a year update...

 

[mauiblue]

What OTA update? Don't bother for once a year update...

Well I was getting the OTA update nag screen constantly and to get rid of it I would just allow the update to install. It wouldn't. I obviously didn't do my research enough to understand what I could have, should have, would have done.

So now I hope the phone makes it back to Maui without costing too much money.

Edit: Well I can't wait for my U11 to come back from service and ended up getting the U12+. The HTC phone I'm using is giving up the ghost soon and I need a reliable setup now. So this issue is costing me big time. Oh well...

Sent from my HTC6545LVW using Tapatalk

 

[mauiblue]

You don't need to "relock" to receive OTA. When I needed to revert my FW to an "official" build, I simply used an RUU to restore and immediately received an OTA to the latest build. I then re-flashed TWRP and Magisk to re-root. At no point did I touch the bootloader after initially unlocking it.

So I should have followed these instructions since I already had unlocked the bootloader via the HTC Dev website? See below. I did not flash any custom ROM and I was all stock after I unlocked the bootloader. I hope I am using the correct nomenclature (unlocked the bootloader).

1. reboot to download mode
2. perform

   htc_fastboot getvar all

   and note down your original software version
3. download the latest Stock RUU for your device over here.
4. flash your RUU to revert to stock
   • rename RUU to 2PZCIMG.zip
   • copy 2PZCIMG.zip to root directory of SD card
   • reboot to download mode
   • press Volume Up button to confirm flash of RUU
5. As soon as your RUU has been flashed sucessfully, that's it. Your are now Full Stock again!

 

[shivadow]

Never relock if the phone ain't stock. You don't need to relock anything anyway. S-off and unlocked bootloader don't affect flashing. Just flash a stock firmware, take ota, reroot or leave it as is.

 

[mauiblue]

Never relock if the phone ain't stock. You don't need to relock anything anyway. S-off and unlocked bootloader don't affect flashing. Just flash a stock firmware, take ota, reroot or leave it as is.

So since I unlocked the bootloader and rooted my U11 but didn't flash a custom ROM it is not stock anymore? So I needed to flash it a stock firmware then my phone would have taken the OTA update. Then I could have rooted the device again or leave it as is.

If there is a next time (which I know there will be) I'll do more research and do it right.

Sent from my coconut frond hut using Tapatalk

 

[mauiblue]

Update:

I just got my phone back from HTC repair department. The battery was dead and I had to charge it. I was able to turn it on and it looks like the bootloader is still unlocked. I didn't get a chance to look around in the phone to see if the os was updated.

There was no documentation on what was done to the phone. Fortunately I was not charged for any repair service. All together it was almost five weeks going to Texas and coming back to Hawaii. I'm going to check the phone out and post back again.

BTW, I am a bit more learned about tweaking the phone now after all these weeks. In fact I just unlocked my replacement phone, the U12+, and rooted it the other day. I'm going back to the U11 when I get all my apps installed and use it for a little bit. I'll be more careful tweaking it this time around.

Sent from my coconut frond hut using Tapatalk

 

[mauiblue]

UPDATE:

When I got home the day I received my HTC U11 I was quite excited about getting the phone set up again. When I turned it on it booted up and I decided I wanted to update the software using the software update menu on the phone. I noticed that it had the 2.42.617.6 version. So I let it run its course and when the phone tried to boot up I got the corrupt phone error message. I was disappointed to say the least. The phone was away for 5 weeks and HTC didn't resolve the issue. Well at least they didn't charge me for anything. Thanks for nothing.

I emailed HTC and they were of no help. They sent me an email pertaining to trying to clear the phone cache. I already mentioned that I couldn't even get the phone to boot! So the last several nights (I work a second job) I've been working on figuring out how to resolve the issue with the phone not being able to boot up. As I examined the phone, I found that the phone was still in the "relocked" status. So I decided I would unlock the bootloader first. I got the unlock BIN file after going through the bootloader unlock process on the HTC Dev website and I was able to unlock the phone. I was happy I got that issue resolved. So now I needed to somehow install an OS/firmware that could boot the phone up.

I followed the xda forum guides and I was stumped at first. I used the ADB method and I was met with failure. Either I was not correctly doing the procedure correctly or I was using the wrong files or ??? I then used the SD card method. When I first used the latest OS/firmware version (this is the same version that was on the phone and listed on the download mode) the procedure would produce a couple error messages right at the end. The phone would be stuck in an endless boot loop. So I decided I would use an earlier version of the OS (2.42.617.1) and use the SD method to install the zip file. It was successful in the install and the phone booted up.

I was still pessimistic that the phone issue was resolved until I was able to update the phone completely. I updated the OS using the software update menu on the phone. The phone took a couple OTA updates without issue and booted up and now I am satisfied. I've learned a lot over the past month about my phones (I also have an HTC U12+ that I bought after I sent off the U11). I was also happy to see that there are a few members here on the forum that is considerate to offer their assistance in getting my phone back in order. So no more relocking the bootloader and I will make sure I backup the phone before I do anything to the OS/firmware.

Aloha and mahalo for reading.