Related
Guys,
My HTC ONE Google Play Edition received the 4.3 update notification, but when I tried, it gave me a status 7 error and refused to install the update. How can I solve this? I'm using stock kernel, CWM recovery, and it's rooted.
Thanks a lot.
felix1212 said:
Guys,
My HTC ONE Google Play Edition received the 4.3 update notification, but when I tried, it gave me a status 7 error and refused to install the update. How can I solve this? I'm using stock kernel, CWM recovery, and it's rooted.
Thanks a lot.
Click to expand...
Click to collapse
you need stock (gpe) recovery and maybe temp unroot (with supersu)
godutch said:
you need stock (gpe) recovery and maybe temp unroot (with supersu)
Click to expand...
Click to collapse
Thanks for reply!! May I know how I can restore both the recovery and ROM to the default one? Should I follow this?
http://forum.xda-developers.com/showthread.php?t=2358781
You have to flash only the stock recovery and relock the bootloader
And yes, use that guide.
After the update will be installed
Guich said:
You have to flash only the stock recovery and relock the bootloader
And yes, use that guide.
After the update will be installed
Click to expand...
Click to collapse
Thanks guy!! I will check the post thoroughly later. However, just one more quick question. Since my device is an original GPE, it looks like all I have to do will be just a fastboot flash recovery & fastboot oem relock? Seems like from that guide, most steps prior to these commands are needed to turn a normal HTC ONE into a GPE one. Am I understanding correctly here?
Thanks again.
Relocking boot loader not necessary. My boot loader is unlocked.
gunnyman said:
Relocking boot loader not necessary. My boot loader is unlocked.
Click to expand...
Click to collapse
Is better if the relock isn't necessary
Guys, thanks for you guys help. I've stocked it back to stock recovery, and have the bootloader locked back. Now when I start the phone, the little lock isn't shown anymore. However, I'm still having 2 issues here.
1) The 4.3 update isn't there anymore!! It doesn't come back even I did a clear cache/force close on the Google Services Framework.
2) It's still showing my phone is still tampered. I booted into the recovery, and it's now the stock one. Is that normal?
Thanks.
Normal because you're rooted
Thanks guy!! I could upgrade successfully.
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
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
Hi,
I was running cyanogenmod 11 nightly and I was trying to flash the stock HTC sense ROM on my phone, but I think I wiped the system and there is no OS installed.
I am on hboot 1.57 and S-On. I have tried several RUUs, but they can't detect my phone.
Please Help!
Your thread has been moved to the Q&A section. Please do not create new threads in the Development section, unless it is development. Please look through the XDA rules, once you have resolution to your issue.
Thank you.
htghd said:
Hi,
I was running cyanogenmod 11 nightly and I was trying to flash the stock HTC sense ROM on my phone, but I think I wiped the system and there is no OS installed.
I am on hboot 1.57 and S-On. I have tried several RUUs, but they can't detect my phone.
Please Help!
Click to expand...
Click to collapse
is your bootloader locked or unlocked? if unlocked, do you have a custom recovery installed? if you can access fastboot and s-on, you're almost certainly not bricked.
also, out of curiosity, what is the error you get when running the RUU exe when it says you can't detect your phone?
Vember31 said:
is your bootloader locked or unlocked? if unlocked, do you have a custom recovery installed? if you can access fastboot and s-on, you're almost certainly not bricked.
also, out of curiosity, what is the error you get when running the RUU exe when it says you can't detect your phone?
Click to expand...
Click to collapse
I have an unlocked bootloader and TWRP installed, but it can't mount the system to flash a ROM.
I think I was getting error 170 USB connection error.
htghd said:
I have an unlocked bootloader and TWRP installed, but it can't mount the system to flash a ROM.
I think I was getting error 170 USB connection error.
Click to expand...
Click to collapse
I was also getting error 170 just yesterday that the RUU couldn't detect the phone. it was happening for me with the bootloader locked (and unlocked too for that matter). i don't have an answer for that yet.
As for the system mounting, I was having the same problem . I went into TWRP, went to Mount and mounted data. I'm not sure if that step mattered. I then went into Wipe/Advanced Wipe and wiped everything (except usb-otg), which I believe formatted system and data properly, but cache was still a problem. I then used "adb push" to push a ROM to internal storage and flashed it. At this point, everything was working except cache was still not able to mount. When I hit the wipe cache/dalvik button after flashing the ROM though it formatted cache properly (I had previously done fastboot format cache which made it unreadable). Basically, just wiping and flashing until I had it working again.
Let me know if this works for you too.
Thanks Vember31!
I'll try it tomorrow and i'll let you know if it works.
Hey Guys!
I was able to un-brick my phone with the correct version of the RUU. I don't know how I was able to fix the USB error, but my computer was able to recognize my phone. I am back on stock HTC Sense 6 with android 4.4.2 kit kat. I am going to put some sort of stock android ROM on it.
Are there any other ROMS other than cyanogenmod that you would recommend?
htghd said:
Hey Guys!
I was able to un-brick my phone with the correct version of the RUU. I don't know how I was able to fix the USB error, but my computer was able to recognize my phone. I am back on stock HTC Sense 6 with android 4.4.2 kit kat. I am going to put some sort of stock android ROM on it.
Are there any other ROMS other than cyanogenmod that you would recommend?
Click to expand...
Click to collapse
Which RUU did you use??
There are a handful of great AOSP roms out right now for m7spr. I'd check the Sprint HTC One Android Development threads. In terms of lollipop, we have CM12 (unofficial), liquid smooth, pac beta builds, unofficial aicp (new) and a couple of 5.0+ GE/Sense builds. There are no active roms in the Original Android Development threads at this time. I've tried all of the aosp builds and would say they're all comparable, though with some i've had "no sim card" issues
I used the Sprint HTC One M7 5.05.651.2 RUU
http://forums.androidcentral.com/ht...449708-ruu-sprint-htc-onem7-5-05-651-2-a.html
Hey Guys,
Here is a link to the latest 6.16.651.2 lollipop RUU for the Sprint HTC One M7
Hello everyone,
I run Note 5, but not that it is in the repair I wanted to try and get 6.0 onto my HTC One M7. Problem is I don't know how to root it. What I did before, I had International version of M7 so I rooted it and installed Google Play Edition rom. Obviously since then my root is gone (not sure about recovery), OTA updated it to 5.1 and that's it.
I have tried 1 click root, Kingo Root but none of them would root. How can I go about rooting this device now? Do I need to revert to stock or what?
Now here are my rom details:
Kernel Version 3.4.10-ge0627be
Build number LMY470.H11
Thank you.
sup3r1or said:
Hello everyone,
I run Note 5, but not that it is in the repair I wanted to try and get 6.0 onto my HTC One M7. Problem is I don't know how to root it. What I did before, I had International version of M7 so I rooted it and installed Google Play Edition rom. Obviously since then my root is gone (not sure about recovery), OTA updated it to 5.1 and that's it.
I have tried 1 click root, Kingo Root but none of them would root. How can I go about rooting this device now? Do I need to revert to stock or what?
Now here are my rom details:
Kernel Version 3.4.10-ge0627be
Build number LMY470.H11
Thank you.
Click to expand...
Click to collapse
There is no android 6.0 for the M7 and the only 6.0 custom roms you'll find for it now are nightly (unstable) builds of Cyagnogenmod 13
For your rooting question, simply flash twrp recovery and then flash update-supersu2.46.zip using twrp and the phone is rooted.
I remember when I got this phone I installed clockwork mod then rooted then installed unrooted GPE rom. Does that mean that my customer recovery is still there untouched or has it been wiped and replaced with stock one?
Also would you be kind enough to point me to where can I find how to replaced Clockwork recovery with TWRP ?
I guess I will wait for some custom 6.0 rom in the future.
sup3r1or said:
Also would you be kind enough to point me to where can I find how to replaced Clockwork recovery with TWRP ?
I guess I will wait for some custom 6.0 rom in the future.
Click to expand...
Click to collapse
Code:
fastboot flash recovery <file_name>.img
fastboot erase cache
fastboot reboot-bootloader
(...)Does that mean that my customer recovery is still there untouched or has it been wiped and replaced with stock one?
Click to expand...
Click to collapse
If you want to know what recovery is currently installed on the phone, why not simply booting in recovery mode?
alray said:
Code:
fastboot flash recovery <file_name>.img
fastboot erase cache
fastboot reboot-bootloader
If you want to know what recovery is currently installed on the phone, why not simply booting in recovery mode?
Click to expand...
Click to collapse
Dang... You beat me to it [emoji23]
Overall I want to know your opinion in Clockwork vs TWRP? Which one is better right now? More useful?
sup3r1or said:
Overall I want to know your opinion in Clockwork vs TWRP? Which one is better right now? More useful?
Click to expand...
Click to collapse
TWRP all the way! [emoji4]