Related
I've been trying to get the 1.29.1540.16 update in my HTC One Dev Edition. So I tried to flash the Stock RUU I downloaded from the HTC site, then download the OTA and then run it from the phone but it just takes me to the TWRP recovery (after I unlocked the bootloader, on "relocked" it just took me to the fastboot screen). What am I doing wrong?
Also when the first time I flashed the RUU (like 2 weeks before) the "Tampered" went away, this time this isn't happening.
Tried relocking/unlocking.
Don't know what to do. Help very much appreciated.
You have to flash the stock recovery first then run the RUU.
shadowboy23 said:
You have to flash the stock recovery first then run the RUU.
Click to expand...
Click to collapse
I feel really dumb asking this but how do I flash the stock recovery? I thought the stock recovery and Stock RUU were the same thing.
vicsalas said:
I feel really dumb asking this but how do I flash the stock recovery? I thought the stock recovery and Stock RUU were the same thing.
Click to expand...
Click to collapse
Recovery is different and it's not included in the RUU (I think). To flash the stock recovery you need to be in fastboot mode and flash via adb. Use this guide by mike1986. http://forum.xda-developers.com/showthread.php?t=2265618. Scroll down to the "Going back to stock" section.
shadowboy23 said:
Recovery is different and it's not included in the RUU (I think). To flash the stock recovery you need to be in fastboot mode and flash via adb. Use this guide by mike1986. http://forum.xda-developers.com/showthread.php?t=2265618. Scroll down to the "Going back to stock" section.
Click to expand...
Click to collapse
Really appreciate the replies. Method 2 of the link you gave me is what I've been doing, but I still see the tampered label and my phone keeps booting back to TWRP (shouldn't this be uninstalled?).
vicsalas said:
Really appreciate the replies. Method 2 of the link you gave me is what I've been doing, but I still see the tampered label and my phone keeps booting back to TWRP (shouldn't this be uninstalled?).
Click to expand...
Click to collapse
Download this: http://d-h.st/b5g
Put it in your adb folder
Reboot to bootloader
Code:
fastboot flash recovery recovery_signed-dev.img
Then you can use the OTA
MacHackz said:
Download this:
Put it in your adb folder
Reboot to bootloader
Code:
fastboot flash recovery recovery_signed-dev.img
Then you can use the OTA
Click to expand...
Click to collapse
Did that, came back an error :FAILED (remote: signature verify fail).
vicsalas said:
Did that, came back an error :FAILED (remote: signature verify fail).
Click to expand...
Click to collapse
Your bootloader is unlocked right?
tedtfra was
MacHackz said:
Your bootloader is unlocked right?
Click to expand...
Click to collapse
Didn't answer before cause I went out to the movies (and of course I didn't enjoy the movie thinking of this).
Right on the money Mac!. Hadn't unlocked the bootloader, did it and worked like a charm. Can't thank you enough, I could install the OTA and that fixed the issues with the capacitive buttons that were my only reason to do so (although phone's so great I think I'd have used it with the buttons issues as well), one last question though: I still have the "tampered" sticker, is that because I did it the other way around? I mean, should I have installed the img file you gave me and then flash the Stock RUU and that would have erased it?
vicsalas said:
Didn't answer before cause I went out to the movies (and of course I didn't enjoy the movie thinking of this).
Right on the money Mac!. Hadn't unlocked the bootloader, did it and worked like a charm. Can't thank you enough, I could install the OTA and that fixed the issues with the capacitive buttons that were my only reason to do so (although phone's so great I think I'd have used it with the buttons issues as well), one last question though: I still have the "tampered" sticker, is that because I did it the other way around? I mean, should I have installed the img file you gave me and then flash the Stock RUU and that would have erased it?
Click to expand...
Click to collapse
You can't remove the Tampered sign It's HTCs way of voiding your warranty
vicsalas said:
Didn't answer before cause I went out to the movies (and of course I didn't enjoy the movie thinking of this).
Right on the money Mac!. Hadn't unlocked the bootloader, did it and worked like a charm. Can't thank you enough, I could install the OTA and that fixed the issues with the capacitive buttons that were my only reason to do so (although phone's so great I think I'd have used it with the buttons issues as well), one last question though: I still have the "tampered" sticker, is that because I did it the other way around? I mean, should I have installed the img file you gave me and then flash the Stock RUU and that would have erased it?
Click to expand...
Click to collapse
Hey i have got the same problem, can you guide me?
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
Hello all,
I'll start with saying how awesome you all are!
Now that the pleasantries are done I have a damned frustrating problem.
I converted my Bell mobility m7 to a gpe m7, it was great until I got the ota 4.4.3 update and like many others got the screen glitch.
So I searched for a way to get it back to stock.
Here us what I've done, flashed twrp and restored the nandroid backup for my device ( all good here) I then changed the cid back to bm___001, also all good. Now it asks me to update the ota, it downloads and verifies, but when I select install now, it boots into twrp recovery and does nothing.
My bootloader is also Black and not the normal white.
My hboot is at 1.54, I have no idea how to get the stock hth recovery on this thing... I have s-off, it's unlocked.
I can get the var dump and post it when I get to my pc.
I've been looking for a week now and I'm stuck. Any help would be awesome..
Just a side, why is there no RUU for bell mobility ?
OTAs only install with stock recoveries. You need to find the correct stock version for the Rom you are on. There is a post on here with all the recoveries
Sent from my HTC One using XDA Premium 4 mobile app
Iz3man said:
Hello all,
I'll start with saying how awesome you all are!
Now that the pleasantries are done I have a damned frustrating problem.
I converted my Bell mobility m7 to a gpe m7, it was great until I got the ota 4.4.3 update and like many others got the screen glitch.
So I searched for a way to get it back to stock.
Here us what I've done, flashed twrp and restored the nandroid backup for my device ( all good here) I then changed the cid back to bm___001, also all good. Now it asks me to update the ota, it downloads and verifies, but when I select install now, it boots into twrp recovery and does nothing.
My bootloader is also Black and not the normal white.
My hboot is at 1.54, I have no idea how to get the stock hth recovery on this thing... I have s-off, it's unlocked.
I can get the var dump and post it when I get to my pc.
I've been looking for a week now and I'm stuck. Any help would be awesome..
Just a side, why is there no RUU for bell mobility ?
Click to expand...
Click to collapse
You need stock recovery installed to install OTA updates..
http://forum.xda-developers.com/showthread.php?t=2545227
Sent from my HTC One using Xparent Skyblue Tapatalk 2
Iz3man said:
Hello all,
I'll start with saying how awesome you all are!
Now that the pleasantries are done I have a damned frustrating problem.
I converted my Bell mobility m7 to a gpe m7, it was great until I got the ota 4.4.3 update and like many others got the screen glitch.
So I searched for a way to get it back to stock.
Here us what I've done, flashed twrp and restored the nandroid backup for my device ( all good here) I then changed the cid back to bm___001, also all good. Now it asks me to update the ota, it downloads and verifies, but when I select install now, it boots into twrp recovery and does nothing.
My bootloader is also Black and not the normal white.
My hboot is at 1.54, I have no idea how to get the stock hth recovery on this thing... I have s-off, it's unlocked.
I can get the var dump and post it when I get to my pc.
I've been looking for a week now and I'm stuck. Any help would be awesome..
Just a side, why is there no RUU for bell mobility ?
Click to expand...
Click to collapse
Why would you try and OTA update a phone with TWRP recovery on it ?
the OTA updates check everything on your phone and can only be used on a totally stock phone with Stock Recovery.
have you tried this >> http://forum.xda-developers.com/showthread.php?t=2529225
The odd thing is the HTC sense Rom checks the update and veryfies it , it starts to install then boots into twrp.
I have hboot 1.54, is that going to be an issue, how do I get to 1.55?
Go Here
Read xda carefully to understand these stuff
from HTC One
Alright I installed the Bell recovery and it works fine. Rebooted phone and it asked again to install ota this time I said install now and watched. Seemed to install fine, but at the very end of the install I got the red triangle. I forced a reboot and I get a blue, then pink screen with boot up sounds, then the HTC logo with blue beats logo and it hangs.
I'll flash twrp back on and restore the nandroid backup I have and restart.
Anyone know why I still have the black bootloader and the Google screen at start up.?
Where Can I get the HTC bootloader?
yatindroid said:
Go Here
Read xda carefully to understand these stuff
from HTC One
Click to expand...
Click to collapse
Thanks for the link.. No idea how I didn't find it earlier...
I have my Sprint HTC One m8 and I'd like to update to ViperOne ROM 3.1.0
I was using ViperOne 1.8.0, but to install the new version I need to get things back to stock so I can get all the OTA's up to the most recent update, and then flash the new ViperOne.
I've gotten this far and now I'm stuck...
Flashed Sprint_HTC_One_M8_1.54.651.8_RUU and now it boots into the stock no problem. Flashed the stock recovery here... http://forum.xda-developers.com/showthread.php?t=2736048 . When I start the phone it recognizes there is an update, but when it tries to install it, the process quits about a quarter of the way through, it gives off the red ! with triangle, then eventually reboots back into android. I feel like I'm missing a step here somewhere, not sure why the stock recovery doesnt work. I can flash back and forth from the stock recovery and twrp, and twrp works. I have access to fastboot if needed.
General specs of the phone as I believe they still are...
S-Off (htc unlock)
Rooted
1.54.651.8 Stock rom
hboot 3.16.00 (i flashed some mod a long time ago to hide the red development message you'd get)
Anything else you need?
Scrufdog said:
I have my Sprint HTC One m8 and I'd like to update to ViperOne ROM 3.1.0
I was using ViperOne 1.8.0, but to install the new version I need to get things back to stock so I can get all the OTA's up to the most recent update, and then flash the new ViperOne.
I've gotten this far and now I'm stuck...
Flashed Sprint_HTC_One_M8_1.54.651.8_RUU and now it boots into the stock no problem. Flashed the stock recovery here... http://forum.xda-developers.com/showthread.php?t=2736048 . When I start the phone it recognizes there is an update, but when it tries to install it, the process quits about a quarter of the way through, it gives off the red ! with triangle, then eventually reboots back into android. I feel like I'm missing a step here somewhere, not sure why the stock recovery doesnt work. I can flash back and forth from the stock recovery and twrp, and twrp works. I have access to fastboot if needed.
General specs of the phone as I believe they still are...
S-Off (htc unlock)
Rooted
1.54.651.8 Stock rom
hboot 3.16.00 (i flashed some mod a long time ago to hide the red development message you'd get)
Anything else you need?
Click to expand...
Click to collapse
delete the cache after flash stock recovery ? fastboot erase cache
dawexxl said:
delete the cache after flash stock recovery ? fastboot erase cache
Click to expand...
Click to collapse
did that, didnt help, but thx
does the phone have to be S-On with a locked bootloader to recieve OTAs?
Scrufdog said:
does the phone have to be S-On with a locked bootloader to recieve OTAs?
Click to expand...
Click to collapse
If you're S-off, no.
You might want to take a look at the thread in the link below. It pretty much covers what you have to do to take the OTA. Since you're S-off, why not install the firmware for the latest update and then flash a ROM based off the latest update? Much simpler than having to go through all the steps you're going through.
http://forum.xda-developers.com/showthread.php?t=2888993
yeah, i was trying to update via methods that were a couple weeks old, which of course are old.... lol
I installed the latest ROM from sprint, then install ViperOne on top of it, going through the install right now. Wifi is working so I guess the firmware updated correctly.
Thanks
I am trying to update to marshmallow ( little behind I know). I have searched for my stock recovery and due to my CID number not being on the stock nandroid&recovery thread, it was a bit harder. I found a few posts elsewhere that Gabe a direct link to it, but I am running into a problem when flashing it. I may be doing something wrong, so hopefully someone can point it out, if I am.
When I flashed it the first time (to update to lollipop) everything went fine. But now when I flash it, I just get a little green progress bar that shows up at the upper right hand side of the bootloader screen. I have been using Windroid by the way, to flash said recovery. When windroid says it's completed, the phone reboots back to bootloader, and I am forced to re-flash TWRP.
Is this because I have the wrong recovery? Or am I missing a step in the process? You DO need a stock recovery to run the RUU, correct? My understanding of the process is:
Flash stock rom & recovery
Relock bootloader
Run RUU.
Please help. Thanks
If you are s-on all you need to do is re-lock bootloader and run the RUU.
Damn. See, I see all these other instructions and get confused. That's what I thought, but I was nervous to try it. The way I described would be for an OTA update, right?
Thank you, by the way
garyg199 said:
Damn. See, I see all these other instructions and get confused. That's what I thought, but I was nervous to try it. The way I described would be for an OTA update, right?
Thank you, by the way
Click to expand...
Click to collapse
I've never taken an OTA lol but as far as I know you need a stock rom (with nothing modified) and stock recovery in order for the OTA to go through without issues.
Easiest way to accomplish that would be to RUU 1 update before the current OTA.