-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
You can't take the OTA with a custom recovery. It requires the stock recovery. Normally to be on the safe side it would be best to lock the bootloader, run the RUU for your device, then take the OTA. Then you can unlock the bootloader, flash recovery and flash super user to root the update.
If you are s-off, you don't even have to lock and unlock the bootloader, and you can flash recovery through the bootloader rather than through fastboot with the PC.
Quills88
Newbie
That's very clear Brian706, thanks.
I have a file called recovery_signed.img backed up on my computer
but I'm not sure if I downloaded it somewhere or it came from my phone.
I'm afraid if I flash it it will mess my phone up.
I haven't found any RUU with my CID which is 622. And there is no way to superCID this phone at least according to the forums. There is also no way to do s-off on the One S.
What is the worst that can happen if I flash this recovery file and it is not meant for this phone?
I have a file called recovery_signed.img backed up on my computer
but I'm not sure if I downloaded it somewhere or it came from my phone.
I'm afraid if I flash it it will mess my phone up.
I haven't found any RUU with my CID which is 622. And there is no way to superCID this phone at least according to the forums. There is also no way to do s-off on the One S.
What is the worst that can happen if I flash this recovery file and it is not meant for this phone?
chong67
Android Expert
I thought there is no s-off on the One S.
Normaly for OTA update, I would just wait 4 the op that cook the ROM to include the update.
Then there is a Radio update which is separate from the cook ROM also.
You may be right about there being no s-off. I don't have any experience with this specific device, but just some htc in general. I know they are making it harder to get s-off. I was just just throwing out if's
razvan06
Android Enthusiast
You have to format EVERYTHING [system/data/cache] before re-locking bootloader, then you have to install latest RUU that you can find for your firmware and for your CID [you may have a branded device, ex. : Vodafone; but network unlocked] !
--Why i say format all ? There is a chance that the RUU will fail if you don't [experienced this with my HOX]
BE CAREFUL there is a BIG difference between RUU and OTA files !!!
Quills88
Newbie
After I locked my bootloader and tried running the OTA update I tried a few things that didn't work.
But what did work for me was when I unlocked bootloader again
And used Hasoon's Toolkit for One S
Dev-Host - The Ultimate Free File Hosting / File Sharing Service
and reflashed the recovery file. I used the recovery_signed.img file (5,957 kb) that I had saved from when I was rooting it the first time and renamed it to a one word name per Hasoon's instructions, then flashed it.
Then I relocked bootloader and did a factory reset and ran the OTA update and it worked.
I was lucky that I had that recovery file saved. Still not sure where I got it from. But one thing for sure is that it was hard to find a RUU file for my CID. Hasoon's toolkit does have links to a website with a list of RUUs on it but mine wasn't on the list.
But what did work for me was when I unlocked bootloader again
And used Hasoon's Toolkit for One S
Dev-Host - The Ultimate Free File Hosting / File Sharing Service
and reflashed the recovery file. I used the recovery_signed.img file (5,957 kb) that I had saved from when I was rooting it the first time and renamed it to a one word name per Hasoon's instructions, then flashed it.
Then I relocked bootloader and did a factory reset and ran the OTA update and it worked.
I was lucky that I had that recovery file saved. Still not sure where I got it from. But one thing for sure is that it was hard to find a RUU file for my CID. Hasoon's toolkit does have links to a website with a list of RUUs on it but mine wasn't on the list.