Database Develop

[Q] Stock recoveries - The right one, their behavior and the risks of flashing them

Hi, I have an Unlocked 32GB HTC One (BS_US001) and I'm having a hard time trying to find info about stock recoveries.
My phone currently is on stock 4.1.2, bootloader unlocked, S-Off and rooted. I was using the TWRP recovery, used to root my phone. Since the 4.3 update came out, I was searching for the stock recovery to proceed with the update, but too many different files seems to exist. I just want to install the right recovery and apply the 4.3 update, no full ROM flash.
Yesterday I flashed this recovery file (9MB) and got icons similar of those on the right of this image.
Today, I flashed this one (7.9MB) and got something like this, the little android icon.
Later, I've found another one (9.8MB).
Edit: and another one, a few bytes shorter than the third.
But now I'm little afraid of flashing again, just for the sake of it.
So, first of all, which one is the right file for my phone (yet another one)?
Second, I flash recoveries through fastboot command line (fastboot flash recovery recovery.img). Can this method and command brick my phone?
Third, how the stock recovery behaves on your phone? Both times, when I flashed the files and entered in recovery mode, my phone would boot 2 or 3 times straight into recovery mode again, until it boot itself properly, into the system. Also, recovery mode goes from the green to the red icon and awaits until I reboot the phone again.
Thanks in advance.
Final edit: For the sake of others lost in the lack of good info, I'm editing this old post.
I found some crap advices here and there. One of them was the need to relock the bootloader to accept OTAs. It doesn't make any sense, but if you are seeking help, you will take **** as good advice. Don't do it.
Another bad advice was about the stock recovery. Just open the last update you got (Downloads folder on your phone or get the OTA from HTC website) and extract the recovery.img file. Flash it and you have the proper stock recovery for your phone.
All of this is about the stock HTC One - no custom roms, no xposed changes, nothing. The only thing I did prior to this was to flash TWRP and root. That's how I want my phone for now - stock with root.

I kind of went through this today. Ended up just wiping it, running a RUU and reapplying OTAs.
I'll tell you this… after I went through this I attempted to salvage the stock recovery before rerooting etc. I was stuck trying to get fastboot to boot a recovery instead of flash one. I did find an alternate way to harvest the recovery. I got it out of the ota. I'm not done testing it yet, but my phone was still showing tampered. Flashed cwr and called it a day at that point
Sent from my HTC One

Thank you for your answer. I'm trying to avoid the whole RUU thing, but I'll keep it as a last resource, for sure. Also, I'm trying to understand more about this piece of software called recovery.

The one I sent you is pulled directly from stock 1.29.1540.16 for Dev. edition, which comes with an unlocked bootloader as well. Also, it's signed, which will allow it to be flashed whether you're s-on or off. Assuming your MID is PN0712000, with CID BS_US001, this recovery is your stock and will work. Hope it helps.

kibmikey1 said:
The one I sent you is pulled directly from stock 1.29.1540.16 for Dev. edition, which comes with an unlocked bootloader as well. Also, it's signed, which will allow it to be flashed whether you're s-on or off. Assuming your MID is PN0712000, with CID BS_US001, this recovery is your stock and will work. Hope it helps.
Click to expand...
Click to collapse
I've been running into similar issues. For the previous 2 OTA's (1540.3 --> 1540.16 & 1540.16 --> 1540.17), simply reflashed stock recovery, ran the OTA, it updated, then I flashed TWRP again. For the most recent OTA (3.22.1540.1, I think), that seems to not be working, but I can't seem to find the right recovery. I've found 1540.3's recovery, but not 1540.16 (or .17 if there was a new recovery in that OTA). Where did you end up finding it?
Thanks!

bjg222 said:
I've been running into similar issues. For the previous 2 OTA's (1540.3 --> 1540.16 & 1540.16 --> 1540.17), simply reflashed stock recovery, ran the OTA, it updated, then I flashed TWRP again. For the most recent OTA (3.22.1540.1, I think), that seems to not be working, but I can't seem to find the right recovery. I've found 1540.3's recovery, but not 1540.16 (or .17 if there was a new recovery in that OTA). Where did you end up finding it?
Thanks!
Click to expand...
Click to collapse
I pulled it directly from my decrypted RUU zip of 1540.16.

Here, there are some of stock recovery.
Check if there is the right version for you.
You have to check the versionmain on your phone

kibmikey1 said:
I pulled it directly from my decrypted RUU zip of 1540.16.
Click to expand...
Click to collapse
Would you be willing to share it? I haven't found a decrypted version of the 1540.16 RUU since Bugsy's hosting server stopped hosting downloads (The new thread only has 1540.3 last I checked).
Guich said:
Here, there are some of stock recovery.
Check if there is the right version for you.
You have to check the versionmain on your phone
Click to expand...
Click to collapse
Thanks, looks like for the dev edition, those sites only have the new recovery from the Android 4.3 updated (3.22.1540.1), though

bjg222 said:
Thanks, looks like for the dev edition, those sites only have the new recovery from the Android 4.3 updated (3.22.1540.1), though
Click to expand...
Click to collapse
Is the 3.22 in the folder

Guich said:
Is the 3.22 in the folder
Click to expand...
Click to collapse
In the Dev Edition folder, 3.22 is all that's there. Have you had any luck finding the 1.29.1540.16 recovery? That's the one I need.

bjg222 said:
In the Dev Edition folder, 3.22 is all that's there. Have you had any luck finding the 1.29.1540.16 recovery? That's the one I need.
Click to expand...
Click to collapse
1.29.1540.16 Developer Edition signed stock recovery.

Has anyone else flashed stock recovery while on custom ROM? I was pleasantly surprised to discover my SD card was wiped Is this normal, and was there some way I could have figured out this was what was going to happen? I don't really understand what stock recovery does/is for. The only other time I'd flashed stock recovery was after restoring to stock ROM from nandroid.

kibmikey1 said:
1.29.1540.16 Developer Edition signed stock recovery.
Click to expand...
Click to collapse
Awesome, thanks!

bjg222 said:
Awesome, thanks!
Click to expand...
Click to collapse
Have you had any luck with this? I have a DE 64gb and I'm in the same situation you were/are, I'm on stock recovery but I can't accept the OTA unlike the other 4.1.2 ones. Always gets stuck on the red triangle !.

arikah said:
Have you had any luck with this? I have a DE 64gb and I'm in the same situation you were/are, I'm on stock recovery but I can't accept the OTA unlike the other 4.1.2 ones. Always gets stuck on the red triangle !.
Click to expand...
Click to collapse
If you're rooted, unroot through SU, then do a factory reset and try it again.

kibmikey1 said:
If you're rooted, unroot through SU, then do a factory reset and try it again.
Click to expand...
Click to collapse
I haven't been rooted since one of the last 4.1.2 updates, because that's when I went back to stock recovery. I was able to accept those OTA packs, why is this one different? I'm really trying to save factory resets or RUU's for the absolute last ditch effort, in fact I'm more likely to stick with 4.1.2 until I can find a way to do this.

help
I have att htc one dev edition, its in soft brick state and i cny get it to do anything, i have tried running the recovery kit, and that get to the end then error 131...
could somebody please suggest some help for me please, thanks in advance

[Q] Phone misbehaving after stock RUU flash

I think this is going to need an experienced dev to answer. Its a small question and probably a small answer but I'm going to put all the information I can.
Ok, so my background is that I recently returned my phone stock, the steps I took were:
S-off, flash RUU, root, remove tampered and unlocked flags, unroot, flash stock recovery, lock the bootloader, s-on.
I then OTAed myself up to 4.3 sense 5.5.
My issue is that having returned to stock, my phone has some instabilities like:
1. it randomly restarted once,
2. I can't lock the device (but can power it off so its not the button broken),
3. and once I opened the camera and the camera bit only took a square of the screen, as in it didn't fill up the whole screen, and the camera menus were messed up (when I rotated, half of the menus were cropped out of the screen, but it went back to normal around 15 seconds later).
Anyway, reason I'm posting this is that I have a niggling feeling that, being originally a CID J15 and x.xx.415.x (middle east firmware which has no RUU available) firmware device, I flashed a 401.x (Europe I think) firmware RUU, this is giving my device some issues. Would that be possible? I got the RUU from htc1guru and it listed J15 as one of the suitable CIDs for the RUU. I also, after unrooting, relocking bootloader and s-on, flashed the RUU again, because as far as I know the RUU (something made by HTC officially) will not flash on a CID that it was not made for, and it worked just fine. So, thats not the issue then is it? I can't think of anything else, I didn't even install any apps yet, only whatsapp.

3alaawi said:
I think this is going to need an experienced dev to answer. Its a small question and probably a small answer but I'm going to put all the information I can.
Ok, so my background is that I recently returned my phone stock, the steps I took were:
S-off, flash RUU, root, remove tampered and unlocked flags, unroot, flash stock recovery, lock the bootloader, s-on.
I then OTAed myself up to 4.3 sense 5.5.
My issue is that having returned to stock, my phone has some instabilities like:
1. it randomly restarted once,
2. I can't lock the device (but can power it off so its not the button broken),
3. and once I opened the camera and the camera bit only took a square of the screen, as in it didn't fill up the whole screen, and the camera menus were messed up (when I rotated, half of the menus were cropped out of the screen, but it went back to normal around 15 seconds later).
Anyway, reason I'm posting this is that I have a niggling feeling that, being originally a CID J15 and x.xx.415.x (middle east firmware which has no RUU available) firmware device, I flashed a 401.x (Europe I think) firmware RUU, this is giving my device some issues. Would that be possible? I got the RUU from htc1guru and it listed J15 as one of the suitable CIDs for the RUU. I also, after unrooting, relocking bootloader and s-on, flashed the RUU again, because as far as I know the RUU (something made by HTC officially) will not flash on a CID that it was not made for, and it worked just fine. So, thats not the issue then is it? I can't think of anything else, I didn't even install any apps yet, only whatsapp.
Click to expand...
Click to collapse
Could you provide the following informations? Because then it's easier to determine the reason for the misbehaviour...
-Did you also have these issues with the firmware you got from the RUU, I mean did you also experience these issues without any OTAs?
-Could you post the link to the RUU you used? Because I also RUUed my phone a few days ago with the same procedure.. but actually, I am from Europe
-Did you flash the stock hboot 1.44 before flashing the RUU?
And as far my knowledge goes, the middle east HTC One doesn't have other hardware, it only has a bit different software, so this shouldn't be the cause for the issues..
Other than that:
Unlock your phone, use a custom recovery and flash a different ROM, and if it works in this case, you can exclude other firmware parts than the system...
And maybe you wanna try out one of these RUUs:
http://www.androidruu.com/index.php?developer=M7
Maybe there is one for you

LibertyMarine said:
Could you provide the following informations? Because then it's easier to determine the reason for the misbehaviour...
-Did you also have these issues with the firmware you got from the RUU, I mean did you also experience these issues without any OTAs?
-Could you post the link to the RUU you used? Because I also RUUed my phone a few days ago with the same procedure.. but actually, I am from Europe
-Did you flash the stock hboot 1.44 before flashing the RUU?
And as far my knowledge goes, the middle east HTC One doesn't have other hardware, it only has a bit different software, so this shouldn't be the cause for the issues..
Other than that:
Unlock your phone, use a custom recovery and flash a different ROM, and if it works in this case, you can exclude other firmware parts than the system...
And maybe you wanna try out one of these RUUs:
http://www.androidruu.com/index.php?developer=M7
Maybe there is one for you
Click to expand...
Click to collapse
Hello,
Here's the RUU I flashed:
http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
It didn't flash first and it said on the link I just posted that I may need hboot 1.44 and so I downloaded and flashed that one and then it worked.
I couldn't tell you if I experienced this before the OTA or not because I OTAed one update after the other immediately. What I can say however is that the home and back button seemed less sensitive to touch in the initial builds, but one of the OTAs made it how it always is.
A for unlocking again and flashing a different rom, I guess I could flash a stock 401 4.3 rom and redo the unrooting process. I just found it really odd that I'm having these issues whilst being on full stock, I've only ever had these issues when flashing unreliable roms and kernels. You lost me at "excluding other firmware parts" though. My main concern is that I want zero chance for anyone to know that my devices was rooted once upon a time, so I wouldn't want to compromise that.

3alaawi said:
Hello,
Here's the RUU I flashed:
http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
It didn't flash first and it said on the link I just posted that I may need hboot 1.44 and so I downloaded and flashed that one and then it worked.
I couldn't tell you if I experienced this before the OTA or not because I OTAed one update after the other immediately. What I can say however is that the home and back button seemed less sensitive to touch in the initial builds, but one of the OTAs made it how it always is.
A for unlocking again and flashing a different rom, I guess I could flash a stock 401 4.3 rom and redo the unrooting process. I just found it really odd that I'm having these issues whilst being on full stock, I've only ever had these issues when flashing unreliable roms and kernels. You lost me at "excluding other firmware parts" though. My main concern is that I want zero chance for anyone to know that my devices was rooted once upon a time, so I wouldn't want to compromise that.
Click to expand...
Click to collapse
Ok.. I flashed the zip.. but this really shouldn't be an issue
But with "excluding other firmware parts" I meant.. if you try another ROM and there it works, you should definitely know that the issue is caused by the system and not by hardware or bootloader etc...
Try another ROM and if it works fine, you can try another RUU.. maybe the zip.. and then you can re-unroot your HTC One and then they won't have any chance finding out what you'd done

3alaawi said:
Hello,
Here's the RUU I flashed:
http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
It didn't flash first and it said on the link I just posted that I may need hboot 1.44 and so I downloaded and flashed that one and then it worked.
I couldn't tell you if I experienced this before the OTA or not because I OTAed one update after the other immediately. What I can say however is that the home and back button seemed less sensitive to touch in the initial builds, but one of the OTAs made it how it always is.
A for unlocking again and flashing a different rom, I guess I could flash a stock 401 4.3 rom and redo the unrooting process. I just found it really odd that I'm having these issues whilst being on full stock, I've only ever had these issues when flashing unreliable roms and kernels. You lost me at "excluding other firmware parts" though. My main concern is that I want zero chance for anyone to know that my devices was rooted once upon a time, so I wouldn't want to compromise that.
Click to expand...
Click to collapse
Did it work? Or can I provide more help?

LibertyMarine said:
Did it work? Or can I provide more help?
Click to expand...
Click to collapse
I actually just booted into the bootloader and turned the phone on again. Then I could lock my device again and it seemed stable though I didn't have much time to test it. I just sent it in for repairs earlier today (for another issue, I have the camera tint problem with my device).
I'm guessing the previous times I reset it, it had that option in the power menu on (fast boot or something like that) maybe thats why the problems didn't go away?
Anyway, thanks for your help

Dont't buy HTC. They Thef's .
This is Problem.... Producer send fake updates to destroy all firmware stock too. I Have Desire 626 from ORANGE PL and my phone get update with this same problems. One idea. Dont't buy HTC. They Thef's .

[Q] HTC One w ARHD12 - how to get Three's 4G update?

OK, so about 9 months ago I rooted my Three branded HTC one, installed CWM recovery and put ARHD12 on there and it's been brilliant. Three are now rolling out the 4G radio updates which as far as I understand is entirely separate to any ROM such as ARHD. So how do I get the radio update? Do I have to go back to stock? If so, now's the time to confess I didn't take a backup before I installed ARHD. So I guess I need the most recent Three RUU - do I have to remove CWM before I install it? I'm not a n00b - I managed to do this on my own last time and I'm fairly technically competent. The only problem I have now is one of time - I can't spend an entire day figuring stuff out due to the 9-month old bundle of joy that requires a fair bit of attention! If you can help me with a fairly simple outline of what to do in what order, that would be very much appreciated. Cheers!

ShadowTD said:
OK, so about 9 months ago I rooted my Three branded HTC one, installed CWM recovery and put ARHD12 on there and it's been brilliant. Three are now rolling out the 4G radio updates which as far as I understand is entirely separate to any ROM such as ARHD. So how do I get the radio update? Do I have to go back to stock? If so, now's the time to confess I didn't take a backup before I installed ARHD. So I guess I need the most recent Three RUU - do I have to remove CWM before I install it? I'm not a n00b - I managed to do this on my own last time and I'm fairly technically competent. The only problem I have now is one of time - I can't spend an entire day figuring stuff out due to the 9-month old bundle of joy that requires a fair bit of attention! If you can help me with a fairly simple outline of what to do in what order, that would be very much appreciated. Cheers!
Click to expand...
Click to collapse
You will have to return completely to stock. That means everything must be as it was out of the box. As for the ruu for your carrier, if they released it then it should be in one of the stickies.
Bat cave One

I'm on Three in the UK and before I flashed a custom ROM I made sure I got S-Off then flashed the latest unbranded firmware(FUU_4.19.401.9-TWRP2633_combined_nowipe.exe which I got from XDA) and then changed my CID to SuperCID. After that I flashed custom ROM without flashing a stock ROM. LTE/4G works perfectly ok.

heat57 said:
I'm on Three in the UK and before I flashed a custom ROM I made sure I got S-Off then flashed the latest unbranded firmware(FUU_4.19.401.9-TWRP2633_combined_nowipe.exe which I got from XDA) and then changed my CID to SuperCID. After that I flashed custom ROM without flashing a stock ROM. LTE/4G works perfectly ok.
Click to expand...
Click to collapse
Thanks Heat57. I'm currently S-On, Unlocked, Tampered. I've also found this thread:
http://forum.xda-developers.com/showthread.php?t=2419699
which seems to contain all of the radio files in the world, and also all of the firmware. This radio:
(1.29.401.12 WWE OTA) Radio_4A.14.3250.13_10.33.1150.01L
Looks interested, but you say you never flashed your radio? When did you get your one?
I'm thinking from your post I'm going to get S-OFF (using Revone, yes?) and flash a firmware to see if the 4G radio options show up. I can't see the one you mentioned - could you recommend one from the above thread? Also, it says TWRP - I'm using CWM - is that a problem?
Final question - if I do a backup I'm backing up the radio and firmware as well? So if I make a total plums of this I can get back to CWM and restore?
TIA for any further help you can give me

ShadowTD said:
Thanks Heat57. I'm currently S-On, Unlocked, Tampered. I've also found this thread:
http://forum.xda-developers.com/showthread.php?t=2419699
which seems to contain all of the radio files in the world, and also all of the firmware. This radio:
(1.29.401.12 WWE OTA) Radio_4A.14.3250.13_10.33.1150.01L
Looks interested, but you say you never flashed your radio? When did you get your one?
I'm thinking from your post I'm going to get S-OFF (using Revone, yes?) and flash a firmware to see if the 4G radio options show up. I can't see the one you mentioned - could you recommend one from the above thread? Also, it says TWRP - I'm using CWM - is that a problem?
Final question - if I do a backup I'm backing up the radio and firmware as well? So if I make a total plums of this I can get back to CWM and restore?
TIA for any further help you can give me
Click to expand...
Click to collapse
Well, I flashed the firmware, which amongst other hardware bits includes the radio. My first goal was to unlock the bootloader and then S-Off, as the latter removes any potential issues with firmware flashes and the like. I also went and changed CID to 11111111, which I understand is SuperCID and enables flashing of firmware and ROMs of different CID designations. Please beware, YOU MUST BE S-OFF FOR FIRMWARE FLASHING!!!
Regarding your question of revone, if you're on hboot 1.44 then yes, revone, hboot version 1.54 and 1.55 only work with rumrunner and latest versions require the 'firewater' exploit.
I am relatively new to HTC, although I owned an original Desire many years ago, so I still remember the peculiarities of HTC ROM. I had a Galaxy Note 2 and rooting and flashing ROMs there is a piece of cake by comparison. I digress.
Unlike most other manufacturers, where you get everything included in the custom ROM, it seems with HTC that is not the case, hence if you want to update your radio for example, you need to flash a firmware package. Therefore, I am not certain if a Nandroid would restore the firmware, if you encounter any problems, maybe someone more knowledgeable can confirm. In any event, if you're S-Off then flashing any firmware for the M7ul should work, so worst case, if you mess up you could always flash the one I pointed out via adb. Here is a link to the latest firmware http://forum.xda-developers.com/showthread.php?t=2485651
Regarding the recovery, I just prefer TWRP and use the one but last version 2.6.3.4, which works perfectly. #However, there is no reason why your CWM should not be adequate. Before I took the jump, after just receiving my One, I read through the threads for about a day to make sure I got it right.
Finally, if you end up rooted and S-Off then there is a supper little flashable zip called 'Guru_Bootloade_Reset_1.0.zip' that allows you to remove the tampered flag, relock the bootloader and unlock it again by simply flashing it and selecting what you want in it's aroma installer. You'll find it on XDA as well, justuse the search function.

Stuck on 4.1.2 can't update to Sense 6/4.4, Three UK Unlocked Stock ROM

Hi everyone,
I've just bought an used HTC One M7 that was locked to Three UK but I managed to get it unlocked via a code from ebay. The phone is on 4.1.2 and the recovery mode shows S-ON, LOCKED so I'm guessing its all stock. The CID is H3G_001 and the OTA updater keeps saying that I'm already on the latest update. The phone isn't rooted either. I've already tried resetting to factory settings but that didn't help. I've had a look at RUU's but couldn't find anything for Three UK/H3G_001.
Could anyone tell me how I could get the Sense 6 update? I've tried clearing the data/cache in the updater and google services framework but still nothing. I don't want to tamper with the bootloader etc if possible.
Thanks,
Anthony

Anzzle said:
Hi everyone,
I've just bought an used HTC One M7 that was locked to Three UK but I managed to get it unlocked via a code from ebay. The phone is on 4.1.2 and the recovery mode shows S-ON, LOCKED so I'm guessing its all stock. The CID is H3G_001 and the OTA updater keeps saying that I'm already on the latest update. The phone isn't rooted either. I've already tried resetting to factory settings but that didn't help. I've had a look at RUU's but couldn't find anything for Three UK/H3G_001.
Could anyone tell me how I could get the Sense 6 update? I've tried clearing the data/cache in the updater and google services framework but still nothing. I don't want to tamper with the bootloader etc if possible.
Thanks,
Anthony
Click to expand...
Click to collapse
Updates are dependent on the carrier for carrier locked phones. It is possible that H3G has not updated their phone. A lot of people will S-OFF their phone to change their CID & MID to get the updates quicker by going to either the Int'l (.401) version or the DevEd (.1540) version which are updated directly from HTC. Your version is .771. For carrier updates, you must remain on the carrier's network to receive them. Check with H3G to see if an update is available and when or if you can expect to receive it.

majmoz said:
Updates are dependent on the carrier for carrier locked phones. It is possible that H3G has not updated their phone. A lot of people will S-OFF their phone to change their CID & MID to get the updates quicker by going to either the Int'l (.401) version or the DevEd (.1540) version which are updated directly from HTC. Your version is .771. For carrier updates, you must remain on the carrier's network to receive them. Check with H3G to see if an update is available and when or if you can expect to receive it.
Click to expand...
Click to collapse
Hey there, thanks for your reply.
I've had a look around the internet and I've found the OTA update zip for my phone from 4.1.2 to 4.2 (1.28.771 to 2.24.771), then another one OTA zip for 4.2 to 4.3 (2.24.771 to 3.62.771). However the issue now is, I can't flash it using the stock recovery as I have S-ON I believe and it throws back an "invalid operation" error when I try to apply an update via internal storage. I'm trying to get S-OFF but I'm not having any luck at the moment, as ideally I don't want to mess with the bootloader. I'll give it another go tomorrow, given up for tonight.
The phone is for my brother and he's fine with 4.1.2/Sense 5 tbh but would like Sense 6 features if possible.

Anzzle said:
Hey there, thanks for your reply.
I've had a look around the internet and I've found the OTA update zip for my phone from 4.1.2 to 4.2 (1.28.771 to 2.24.771), then another one OTA zip for 4.2 to 4.3 (2.24.771 to 3.62.771). However the issue now is, I can't flash it using the stock recovery as I have S-ON I believe and it throws back an "invalid operation" error when I try to apply an update via internal storage. I'm trying to get S-OFF but I'm not having any luck at the moment, as ideally I don't want to mess with the bootloader. I'll give it another go tomorrow, given up for tonight.
The phone is for my brother and he's fine with 4.1.2/Sense 5 tbh but would like Sense 6 features if possible.
Click to expand...
Click to collapse
if you don't want to mess with the bootloader then try Sunshine to s-off: http://forum.xda-developers.com/showthread.php?p=53624322

Anzzle said:
Hey there, thanks for your reply.
I've had a look around the internet and I've found the OTA update zip for my phone from 4.1.2 to 4.2 (1.28.771 to 2.24.771), then another one OTA zip for 4.2 to 4.3 (2.24.771 to 3.62.771). However the issue now is, I can't flash it using the stock recovery as I have S-ON I believe and it throws back an "invalid operation" error when I try to apply an update via internal storage. I'm trying to get S-OFF but I'm not having any luck at the moment, as ideally I don't want to mess with the bootloader. I'll give it another go tomorrow, given up for tonight.
The phone is for my brother and he's fine with 4.1.2/Sense 5 tbh but would like Sense 6 features if possible.
Click to expand...
Click to collapse
OTA update is flashed in stock recovery. Here is a post explaining the OTA process. This post might explain what you are missing for the OTA to work. I think you must select from "internal storage" instead of "sdcard" when you install the OTA.

majmoz said:
OTA update is flashed in stock recovery. Here is a post explaining the OTA process. This post might explain what you are missing for the OTA to work. I think you must select from "internal storage" instead of "sdcard" when you install the OTA.
Click to expand...
Click to collapse
I've tried following the process but it just gives a "Invalid Operation" message when ever I select from Internal Storage. I'm losing patience with this, why can't OTA just work.
Thanks for your help anyways.

Anzzle said:
I've tried following the process but it just gives a "Invalid Operation" message when ever I select from Internal Storage. I'm losing patience with this, why can't OTA just work.
Thanks for your help anyways.
Click to expand...
Click to collapse
you can't manually flash ota with a s-on phone, only s-off.

Anzzle said:
I've tried following the process but it just gives a "Invalid Operation" message when ever I select from Internal Storage. I'm losing patience with this, why can't OTA just work.
Thanks for your help anyways.
Click to expand...
Click to collapse
Try following this post. Make sure that your version number matches exactly the second version in the file name. Change the name to "update.zip" and place in the SDCARD.

[Q] Stuck at Boot after OTA update

I have an unlocked and rooted HTC One M7, which I just updated to the latest version of android via an OTA update.
I used the process I always use for this, by reverting back to the stock recovery, then doing the update.
Even though the update completed, the initial boot after the update won't complete anymore. I am stuck at the HTC One Boot-logo.
I know that it usually takes longer to boot after an update, for the first time. However I have waited 60+ minutes now and it still did not move on.
Some more detailed information:
- Unlocked bootloader
- S-OFF
- H-Boot: 1.61.0000
- Radio: 4T.35.3218.16
- Version-Main before update: 7.18.161.2 (This is also the stock recovery I pulled and flashed before doing the OTA)
- Version-Main after update: 7.18.161.21
- CID: VODAP110
- Variant m7_ul unlocked / international
What I have tried:
1st As mentioned above, re-flashing stock recovery, update -> No boot
2nd Recovery from an older nandroid backup, made on the previous version, so 7.18.161.2. After recovering, my device worked fine again, like before the update. HOWEVER: The system version (inside the OS, aswell as adb and bootloader) still showed 7.18.161.21, which should be the version AFTER the update. It still tells me that I need to update my phone though.
3rd Since then I have tried to re-flash the stock recovery, this time the one for 7.18.161.21, since it showed me I was on this version. Again, the update completed without any hickup, but it is now stuck at boot again.

PhilDrummer said:
I have an unlocked and rooted HTC One M7, which I just updated to the latest version of android via an OTA update.
I used the process I always use for this, by reverting back to the stock recovery, then doing the update.
Even though the update completed, the initial boot after the update won't complete anymore. I am stuck at the HTC One Boot-logo.
I know that it usually takes longer to boot after an update, for the first time. However I have waited 60+ minutes now and it still did not move on.
Some more detailed information:
- Unlocked bootloader
- S-OFF
- H-Boot: 1.61.0000
- Radio: 4T.35.3218.16
- Version-Main before update: 7.18.161.2 (This is also the stock recovery I pulled and flashed before doing the OTA)
- Version-Main after update: 7.18.161.21
- CID: VODAP110
- Variant m7_ul unlocked / international
What I have tried:
1st As mentioned above, re-flashing stock recovery, update -> No boot
2nd Recovery from an older nandroid backup, made on the previous version, so 7.18.161.2. After recovering, my device worked fine again, like before the update. HOWEVER: The system version (inside the OS, aswell as adb and bootloader) still showed 7.18.161.21, which should be the version AFTER the update. It still tells me that I need to update my phone though.
3rd Since then I have tried to re-flash the stock recovery, this time the one for 7.18.161.21, since it showed me I was on this version. Again, the update completed without any hickup, but it is now stuck at boot again.
Click to expand...
Click to collapse
You are confusing software and firmware version. When installing an ota update, both the software and firmware are updated. Nandroid backups doenst include the firmware, flashing one will only restore the software. So you are restoring a .2 software on a . 21 firmware.
Anyway you have soff just flash the latest ruu available for your phone and then update it

alray said:
You are confusing software and firmware version. When installing an ota update, both the software and firmware are updated. Nandroid backups doenst include the firmware, flashing one will only restore the software. So you are restoring a .2 software on a . 21 firmware.
Anyway you have soff just flash the latest ruu available for your phone and then update it
Click to expand...
Click to collapse
I have tried finding the correct RUU, but I am getting a little confused with the available ones. When selecting the RUU, is only the variant of the phone important (so unlocked in my case) or do I have to match everything, as in CID, Carrier etc.? Because I cannot seem to find one that has matching information, except for the variant.

PhilDrummer said:
I have tried finding the correct RUU, but I am getting a little confused with the available ones. When selecting the RUU, is only the variant of the phone important (so unlocked in my case) or do I have to match everything, as in CID, Carrier etc.? Because I cannot seem to find one that has matching information, except for the variant.
Click to expand...
Click to collapse
7.18.161.2 is the first ruu posted in this thread

alray said:
7.18.161.2 is the first ruu posted in this thread
Click to expand...
Click to collapse
Wow, sorry I somehow didn't manage to find that :angel:
Thaks a lot!
Btw, since you said the firmware is not included in a Nandroid backup, if I create one now, do the whole procedure and if something fails, re-flash the nandroid, should everything still be working fine just as it is now? I'm guessing yes, right?
Also: If I now flash the ruu, deleting all data etc in the process, and then update, I won't have any option of re-aquiring all my data/settings either, right?
So in the end effect, this update will basically "flush" my phone

Same problem
Hi
I experienced the same problem while updating from 7.18.161.2 to 7.18.161.21. My bootloader was unlocked l, S-on and flashed stock recovery before I did the OTA. This procedure was working fine since a long time. Unfortunately this time I got stuck at the HTC boot logo, same as OP.
After flashing the RUU, locking the bootloader (this I guess was the important step) and do the OTA again, it finally worked. Too bad I lost all my precious data. Yeye backup I know
Im really aware of unlocking my bootloader again and have the same problem the next time they might release an update.
Now my question is, did HTC or my Carrier (Swisscom) changed anything in the update procedure?
Regards
red1337

red1337 said:
Hi
I experienced the same problem while updating from 7.18.161.2 to 7.18.161.21. My bootloader was unlocked l, S-on and flashed stock recovery before I did the OTA. This procedure was working fine since a long time. Unfortunately this time I got stuck at the HTC boot logo, same as OP.
After flashing the RUU, locking the bootloader (this I guess was the important step) and do the OTA again, it finally worked. Too bad I lost all my precious data. Yeye backup I know
Im really aware of unlocking my bootloader again and have the same problem the next time they might release an update.
Now my question is, did HTC or my Carrier (Swisscom) changed anything in the update procedure?
Regards
red1337
Click to expand...
Click to collapse
They will probably not have anymore updates but to install one you need:
stock recovery of the same firmware version or from the ota update version
stock /system partition (any missing/modified/corrupted files on this partition will makes the ota install fail)
stock /data/preload (any missing/modified/corrupted files on this partition will makes the ota install fail, unlocking the bootloader wipes everything in this folder)
More details here:http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9