Database Develop

[Q] ¿How do I uninstall TWRP?

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?

[Q] I hope I have't bricked my Sprint HTC One

It all started when I rebooted my phone one day. My phone loaded up the lock screen with google voice. I could say the pin but could never get my phone unlocked. The keyboard button didn't work. So rather than just bootloader/factory resetting my phone, i decided i might as well unlock it and give myself root and flash a rom and try it out. I am an experienced EVO 4G user and have flashed many a rom. I did not have any problems unlocking the phone, flashing the TWRP recovery, applying su, or flashing the rom. I flashed the rootbox rom. It worked just fine. I then decided I was going to try a different rom out. I was not aware that there were roms that would cause problems... the non-sprint roms. I then tried to flash several non-sprint roms. None of the worked and eventually my phone would only boot up into the bootloader. I was able to successfully fastboot flash the TWRP recovery back onto my phone. I tried then to load in a sprint rom. Apparently I had messed up my radios, file structure and possibly other stuff, as no rom would work at that point. After much research, I found I needed to apply the RUU to get my phone back into "sprint" mode with the correct radios and file structure. I have been trying for hours now to do just that. I have tried all the methods listed on xda. The current condition of my phone: Will boot only into bootloader, will not boot into recovery although i think the TWRP recovery is still on my phone. I have the tampered, relocked, and security warning messages at the top of my phone. I am still s-on. I cannot get s-off as I have no accessible os on the phone to use the adb commands. I do have fastboot access. I have tried to fastboot flash the ruu and I get failed messages either <remote: 12 signature verify fail> or <remote: 43 main version check fail>
Any/All advice recommendations are welcome. If there is a thread about fixing bricked phones or tools to load RUU, I have tried them to no avail.
Thanks

Have you tried running the RUU from your PC? It would also help to know if you are on 1.29 or 1.31.

MrFixit007 said:
It all started when I rebooted my phone one day. My phone loaded up the lock screen with google voice. I could say the pin but could never get my phone unlocked. The keyboard button didn't work. So rather than just bootloader/factory resetting my phone, i decided i might as well unlock it and give myself root and flash a rom and try it out. I am an experienced EVO 4G user and have flashed many a rom. I did not have any problems unlocking the phone, flashing the TWRP recovery, applying su, or flashing the rom. I flashed the rootbox rom. It worked just fine. I then decided I was going to try a different rom out. I was not aware that there were roms that would cause problems... the non-sprint roms. I then tried to flash several non-sprint roms. None of the worked and eventually my phone would only boot up into the bootloader. I was able to successfully fastboot flash the TWRP recovery back onto my phone. I tried then to load in a sprint rom. Apparently I had messed up my radios, file structure and possibly other stuff, as no rom would work at that point. After much research, I found I needed to apply the RUU to get my phone back into "sprint" mode with the correct radios and file structure. I have been trying for hours now to do just that. I have tried all the methods listed on xda. The current condition of my phone: Will boot only into bootloader, will not boot into recovery although i think the TWRP recovery is still on my phone. I have the tampered, relocked, and security warning messages at the top of my phone. I am still s-on. I cannot get s-off as I have no accessible os on the phone to use the adb commands. I do have fastboot access. I have tried to fastboot flash the ruu and I get failed messages either <remote: 12 signature verify fail> or <remote: 43 main version check fail>
Any/All advice recommendations are welcome. If there is a thread about fixing bricked phones or tools to load RUU, I have tried them to no avail.
Thanks
Click to expand...
Click to collapse
Pm me your teamviewer information and I'll help you out.

bigdaddy619 said:
Have you tried running the RUU from your PC? It would also help to know if you are on 1.29 or 1.31.
Click to expand...
Click to collapse
I am on 1.31. I have tried running the RUU from my PC and I got error 140. I tried looking that up and could not find any solutions to that. I figured it was because I am on 1.31 and not 1.29 and I still had s-on. That is when I tried to get s-off so that I could apply the 1.29. Is it possible to open a fastboot shell? I was going to try to push the revone files to the phone via fastboot and then run the commands via fastboot, but didn't get around to trying that out last night.

Indirect said:
Pm me your teamviewer information and I'll help you out.
Click to expand...
Click to collapse
Thanks a bunch! I have sent you a PM. I'll send you another one when I get home from work.

MrFixit007 said:
Thanks a bunch! I have sent you a PM. I'll send you another one when I get home from work.
Click to expand...
Click to collapse
OK!! Awesome! Indirect showed me the error of my ways!! So now I have TWRP recovery back on my phone and I was able to get RUU to be successful.
What are the recommended next steps?

MrFixit007 said:
OK!! Awesome! Indirect showed me the error of my ways!! So now I have TWRP recovery back on my phone and I was able to get RUU to be successful.
What are the recommended next steps?
Click to expand...
Click to collapse
What do you want to know?
Sent from?

MrFixit007 said:
OK!! Awesome! Indirect showed me the error of my ways!! So now I have TWRP recovery back on my phone and I was able to get RUU to be successful.
What are the recommended next steps?
Click to expand...
Click to collapse
Congrats on getting phone back up. I recommend you stay away from flashing Roms that are not for Sprint but I think you learned that part first hand already.

im0rtalz said:
Congrats on getting phone back up. I recommend you stay away from flashing Roms that are not for Sprint but I think you learned that part first hand already.
Click to expand...
Click to collapse
bigdaddy619 said:
What do you want to know?
Sent from?
Click to expand...
Click to collapse
Yeah, I sure did. Coming from an OG EVO 4G that was a little bit of a nasty surprise. Wel my phone is sitting on the fastboot screen after the successful ruu. The only message at the top is **relocked***
Can i boot like normal now? Should i flash a rom at this point? i'm kinda still wearing the kid gloves...

MrFixit007 said:
Yeah, I sure did. Coming from an OG EVO 4G that was a little bit of a nasty surprise. Wel my phone is sitting on the fastboot screen after the successful ruu. The only message at the top is **relocked***
Can i boot like normal now? Should i flash a rom at this point? i'm kinda still wearing the kid gloves...
Click to expand...
Click to collapse
Did Indirect get you S-OFF? If not you need to unlock your bootloader again then re-flash TWRP or CWM then you can flash a rom. Any questions shoot me a PM

bigdaddy619 said:
Did Indirect get you S-OFF? If not you need to unlock your bootloader again then re-flash TWRP or CWM then you can flash a rom. Any questions shoot me a PM
Click to expand...
Click to collapse
We did not get to s-off. I am still s-on. the way I understand it is that basically I am back at square one... only I can use the fastboot command to unlock the bootloader, I don't need to go to the HTC website. and once i put a recovery on i can load any SPRINT ROM i want.
i'll do my best to be good this time

MrFixit007 said:
We did not get to s-off. I am still s-on. the way I understand it is that basically I am back at square one... only I can use the fastboot command to unlock the bootloader, I don't need to go to the HTC website. and once i put a recovery on i can load any SPRINT ROM i want.
i'll do my best to be good this time
Click to expand...
Click to collapse
Check PM

MrFixit007 said:
OK!! Awesome! Indirect showed me the error of my ways!! So now I have TWRP recovery back on my phone and I was able to get RUU to be successful.
What are the recommended next steps?
Click to expand...
Click to collapse
Indirect helps so many people on herr. We are lucky to have the folks in this forum.
Sent from my (M7WLS) HTC ONE.

theotrman said:
Indirect helps so many people on herr. We are lucky to have the folks in this forum.
Sent from my (M7WLS) HTC ONE.
Click to expand...
Click to collapse
Indirect is a beast

bigdaddy619 said:
Indirect is a beast
Click to expand...
Click to collapse
yep! Indirect and bigdaddy are both beasts!

theotrman said:
Indirect helps so many people on herr. We are lucky to have the folks in this forum.
Sent from my (M7WLS) HTC ONE.
Click to expand...
Click to collapse
Indirect and bigdaddy have both helped me out bunches tonight!!! I am completely back in action!!

What in the world did Indirect do that worked to well?
I'm in a similar situation right now and I'm still stuck.

NotSneakyNinja said:
What in the world did Indirect do that worked to well?
I'm in a similar situation right now and I'm still stuck.
Click to expand...
Click to collapse
Probably downgraded him from 1.31 to 1.29 so he could RUU
Sent from?

NotSneakyNinja said:
What in the world did Indirect do that worked to well?
I'm in a similar situation right now and I'm still stuck.
Click to expand...
Click to collapse
The key is knowing what fastboot commands to use and in which order. I had gotten stuck and gotten some of them out of order. I'd be willing to help you out like indirect did for me. If you PM me your teamviewer information i can help you out.

MrFixit007 said:
The key is knowing what fastboot commands to use and in which order. I had gotten stuck and gotten some of them out of order. I'd be willing to help you out like indirect did for me. If you PM me your teamviewer information i can help you out.
Click to expand...
Click to collapse
I got him fixed up

Need Help Restoring Google Play Edition to Stock (HBOOT 1.54 - 4.3 AOSP)

Hello,
I seem to have gotten myself into a bind, and looking ahead to the 4.4 KitKat release, I am not sure how to get myself out of it. I've already done a lot of research and troubleshooting on my own, but can't seem to resolve the problem.
I purchased an HTC One Google Play edition, and decided to root to apply a quick fix with utilizing the Nexus 5 launcher. To that end, I unlocked my bootloader and rooted. I had a Windows 7 partition on my Mac at the time, but it was giving me trouble. Since the root, I became dissatisfied with the performance of the phone, and attempted to restore to factory.
I flashed stock recovery again, and relocked the bootloader. Now the bootloader shows as "relocked" and "tampered." However, in between root and unroot attempts, I upgraded my partition to Windows 8.1. Suddenly, when in fastboot, my HTC One shows up as "USB Device not Recognized," meaning I cannot issue any commands using ADB. If I don't get "waiting for device" I get "device offline," and my device is still rooted.
Whenever I uninstall Super SU, it's right back upon reboot.
I currently have S-ON. I am unable to get S-OFF because my computer doesn't recognize the phone when in fastboot. I tried updating and downloading different HTC Drivers to no avail.
I want to attempt to get my device back to its exact status when I bought the phone. Meaning, I want to have my bootloader as locked, keep S-ON (although I don't mind having S-OFF temporarily), and flash the stock RUU/Recovery. Upon Google Search, this seems easy, but there is not much out there for the GPE. A lot of the guides I have found are for Sense versions. My phone is not a GPE conversion. It is an actual GPE phone purchased on the Play Store.
Phone is functional, but I am concerned when 4.4 comes out, the update will fail or brick.
Sorry if this thread is long. I wanted to be as detailed as possible when asking for help. Thanks again to anyone on XDA who can assist.

mikhailov1 said:
Hello,
I seem to have gotten myself into a bind, and looking ahead to the 4.4 KitKat release, I am not sure how to get myself out of it. I've already done a lot of research and troubleshooting on my own, but can't seem to resolve the problem.
I purchased an HTC One Google Play edition, and decided to root to apply a quick fix with utilizing the Nexus 5 launcher. To that end, I unlocked my bootloader and rooted. I had a Windows 7 partition on my Mac at the time, but it was giving me trouble. Since the root, I became dissatisfied with the performance of the phone, and attempted to restore to factory.
I flashed stock recovery again, and relocked the bootloader. Now the bootloader shows as "relocked" and "tampered." However, in between root and unroot attempts, I upgraded my partition to Windows 8.1. Suddenly, when in fastboot, my HTC One shows up as "USB Device not Recognized," meaning I cannot issue any commands using ADB. If I don't get "waiting for device" I get "device offline," and my device is still rooted.
Whenever I uninstall Super SU, it's right back upon reboot.
I currently have S-ON. I am unable to get S-OFF because my computer doesn't recognize the phone when in fastboot. I tried updating and downloading different HTC Drivers to no avail.
I want to attempt to get my device back to its exact status when I bought the phone. Meaning, I want to have my bootloader as locked, keep S-ON (although I don't mind having S-OFF temporarily), and flash the stock RUU/Recovery. Upon Google Search, this seems easy, but there is not much out there for the GPE. A lot of the guides I have found are for Sense versions. My phone is not a GPE conversion. It is an actual GPE phone purchased on the Play Store.
Phone is functional, but I am concerned when 4.4 comes out, the update will fail or brick.
Sorry if this thread is long. I wanted to be as detailed as possible when asking for help. Thanks again to anyone on XDA who can assist.
Click to expand...
Click to collapse
try this http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers
it worked for some users

Thanks. Will try when I get home. I was able to use my Win 7 computer at work to unlock the boot loader again, but I cannot get S Off. I ran rumrunner and it looked like it was working, but then said FATAL: download update. Is there no rumrunner for GPE?
Sent from my HTC One using Tapatalk

Update: Your suggestion worked perfectly! I was able to unlock my bootloader again from my windows 8.1. I'm now trying to get S-OFF and flash the stock gpe RUU. To date, the RUU fails to install, and rumrunner gives me errors that ask me to run the program again. I feel I am still stuck as I want to eliminate root and make sure I can receive OTA. Is there anything else I can do? I'm still running stock 4.3 and stock recovery for the GPE.
Sent from my HTC One using Tapatalk

mikhailov1 said:
Update: Your suggestion worked perfectly! I was able to unlock my bootloader again from my windows 8.1. I'm now trying to get S-OFF and flash the stock gpe RUU. To date, the RUU fails to install, and rumrunner gives me errors that ask me to run the program again. I feel I am still stuck as I want to eliminate root and make sure I can receive OTA. Is there anything else I can do? I'm still running stock 4.3 and stock recovery for the GPE.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
You got stock rom and stock recovery ryt... lock the bootloader and check for update

Prash8429 said:
You got stock rom and stock recovery ryt... lock the bootloader and check for update
Click to expand...
Click to collapse
Yeah I have stock rom and I removed TWRP and flashed stock recovery. Because I did two factory restores from bootloader, I'm assuming the stock recovery is working properly, but I'm a noob at this stuff so I could be wrong.
Going to relock the bootloader, remove SuperSU, and attempt the update when it hits. Hopefully it will work.
Thanks for your help! Since I'm a new member, how do I add to your thanks meter? Want to make sure you're properly....thanked.

mikhailov1 said:
Yeah I have stock rom and I removed TWRP and flashed stock recovery. Because I did two factory restores from bootloader, I'm assuming the stock recovery is working properly, but I'm a noob at this stuff so I could be wrong.
Going to relock the bootloader, remove SuperSU, and attempt the update when it hits. Hopefully it will work.
Thanks for your help! Since I'm a new member, how do I add to your thanks meter? Want to make sure you're properly....thanked.
Click to expand...
Click to collapse
you can still get OTA with a rooted phone, as long as you have stock recovery and flashed stock ruu.... tip if your having trouble with flashing ruu change the zip file name to something simple like ruu.zip worked for me.:good:

mikhailov1 said:
Update: Your suggestion worked perfectly! I was able to unlock my bootloader again from my windows 8.1. I'm now trying to get S-OFF and flash the stock gpe RUU. To date, the RUU fails to install, and rumrunner gives me errors that ask me to run the program again. I feel I am still stuck as I want to eliminate root and make sure I can receive OTA. Is there anything else I can do? I'm still running stock 4.3 and stock recovery for the GPE.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Can you tell me if your bootloader was 1.54 or 1.55? I have been unable to get Windows 8.1 to recognize the 1.54 bootloader. It always says "device not recognized" If yours was 1.54.0000 I will try this fix. Thanks.

I am 1.54.
Sent from my Nexus 5 using Tapatalk

Thanks for this, helped me out alot
Sent from my HTC One using XDA Premium 4 mobile app

Verizon Htc one, rom reboots every few minutes.

Hello guys Im having a problem with my vzw htc one and I know its my fault, I basically soft bricked the phone however it loads into currently installed rom (I had 3 and only one that would load) I have but reboots every few minutes with no access to the internal memory. I was trying to install Google play edition 4.4 kitkat however I forgot the radios are different for our phones and I installed the incorrect radio so now I am stuck only with the bootloader and CWM recovery but I cannot flash any files through fastboot because its apparently still locked (im getting the remote not allowed error) My phones is S off and rooted (I used rumrunner) . I have tried to mount usb storage in recovery with no luck and I have tried to flash a new rom and radio through boot loader but its locked and htc dev wont let you unlock our phones so im kinda stuck
If anyone has a solution to my problem I would really appreciate it I use my phone for a lot of stuff while deployed here in Afghanistan I use Roshan prepaid sim card works well.Thanks for any help and have a great day !

armyguy1989 said:
Hello guys Im having a problem with my vzw htc one and I know its my fault, I basically soft bricked the phone however it loads into currently installed rom (I had 3 and only one that would load) I have but reboots every few minutes with no access to the internal memory. I was trying to install Google play edition 4.4 kitkat however I forgot the radios are different for our phones and I installed the incorrect radio so now I am stuck only with the bootloader and CWM recovery but I cannot flash any files through fastboot because its apparently still locked (im getting the remote not allowed error) My phones is S off and rooted (I used rumrunner) . I have tried to mount usb storage in recovery with no luck and I have tried to flash a new rom and radio through boot loader but its locked and htc dev wont let you unlock our phones so im kinda stuck
If anyone has a solution to my problem I would really appreciate it I use my phone for a lot of stuff while deployed here in Afghanistan I use Roshan prepaid sim card works well.Thanks for any help and have a great day !
Click to expand...
Click to collapse
instructions to unlock are here ...you use revone (on hboot 1.44)
http://forum.xda-developers.com/showthread.php?t=2314582&nocache=1
Correction Below for hboot 1.54 use this >> http://forum.xda-developers.com/showthread.php?t=2470340
I also suggest update to TWRP if you want to flash the modern kit kat roms
http://techerrata.com/browse/twrp2/m7vzw
fastboot flash recovery openrecovery-twrp.img
fastboot erase cache
fastboot reboot-bootloader

clsA said:
instructions to unlock are here ...you use revone
http://forum.xda-developers.com/showthread.php?t=2314582&nocache=1
I also suggest update to TWRP if you want to flash the modern kit kat roms
http://techerrata.com/browse/twrp2/m7vzw
fastboot flash recovery openrecovery-twrp.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Thank you so much clsA I will do this when I get off work im on a government computer, thanks again !

clsA said:
instructions to unlock are here ...you use revone
http://forum.xda-developers.com/showthread.php?t=2314582&nocache=1
I also suggest update to TWRP if you want to flash the modern kit kat roms
http://techerrata.com/browse/twrp2/m7vzw
fastboot flash recovery openrecovery-twrp.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
So revone will unlock my hboot ? Im already s-off but my problem is its saying it doesnt support hboot 1.54 and thats what I have

armyguy1989 said:
So revone will unlock my hboot ? Im already s-off but my problem is its saying it doesnt support hboot 1.54 and thats what I have
Click to expand...
Click to collapse
I think some functions like unlock still work. if not you'll have to flash a firmware to get back to 1.44 hboot
sorry try here >> http://forum.xda-developers.com/showthread.php?t=2470340

147
clsA said:
I think some functions like unlock still work. if not you'll have to flash a firmware to get back to 1.44 hboot
sorry try here >> http://forum.xda-developers.com/showthread.php?t=2470340
Click to expand...
Click to collapse
Im using my buddies laptop and 3g hotspot at work I just installed twrp it works fine I have the correct radio to load on my phone is there i way i can flash this new correct radio without unlocking the hboot ? Everything is erased but i still have carbon rom running so if i get the correct radio again i can just use the phone normally and install the rom using the computer. if that doesnt work can i use adb sideload or something in twrp recovery ? i tried to mount usb in twrp but still no go.

armyguy1989 said:
Im using my buddies laptop and 3g hotspot at work I just installed twrp it works fine I have the correct radio to load on my phone it has a boot img is there i way i can flash this new correct radio and a new rom without unlocking the hboot ? like using adb sideload or in twrp recovery ? i tried to mouunt usb in twrp but still no go.
Click to expand...
Click to collapse
you can download any flashable radio and replace the radio.img in the zip with yours and flash it in twrp.
here's one of mine >> http://www.androidfilehost.com/?fid=23501681358550122
Edit: and did you look at scotty's lock / unlock page ?
Also the Carbon rom could be part of your problem
try a normal Sense Rom - like http://forum.xda-developers.com/showthread.php?t=2693502
or
here>> http://forum.xda-developers.com/showthread.php?t=2485319

clsA said:
you can download any flashable radio and replace the radio.img in the zip with yours and flash it in twrp.
here's one of mine >> http://www.androidfilehost.com/?fid=23501681358550122
Edit: and did you look at scotty's lock / unlock page ?
Also the Carbon rom could be part of your problem
try a normal Sense Rom - like http://forum.xda-developers.com/showthread.php?t=2693502
or
here>> http://forum.xda-developers.com/showthread.php?t=2485319
Click to expand...
Click to collapse
I did see that and cool I will use yours. I guess I will try to unlock it in case this happens again but ill probably never mess with the radio again lol.
i wasnt using the carbon rom anymore i had 2 more roms on my sd card and when i flashed the incorrect radio the other two wouldnt even work. thescreen was black when it loaded. carbon rom is the only one that would load but it just reboots every few minutes i tried to copy the files on the sd card before it rebooted but wouldnt work
just out of curiousity how would i flash that with the bootloader locked. i really want to know incase something ever happens again. im still learning alot of this stuff lol
Im going to unlock the hboot real quick and see if that works. you should private message me your paypal im going to buy you dinner for all your help

btw this my current radio 4T.21.3218.21 im guessing it doesnt work with verizon htc one lol.

Never mind I found the donate button !

armyguy1989 said:
Never mind I found the donate button !
Click to expand...
Click to collapse
This is the newest Verizon radio
http://forum.xda-developers.com/devdb/project/dl/?id=6511
and in my dropbox as well >> https://www.dropbox.com/s/0yq7d3xnrni9hm3/Flashable-m7vzw_4.10.605.3_1.13.41.0421_Radio.zip
Thanks for the Dinner and Drink

clsA said:
This is the newest Verizon radio
http://forum.xda-developers.com/devdb/project/dl/?id=6511
and in my dropbox as well >> https://www.dropbox.com/s/0yq7d3xnrni9hm3/Flashable-m7vzw_4.10.605.3_1.13.41.0421_Radio.zip
Thanks for the Dinner and Drink
Click to expand...
Click to collapse
Well i feel like a dumbass right now unless its just a crazy stroke of luck. i had my usb plugged in to the ss 3.0 and when reading the instructions to setup up the adb it said to make sure you not using a 3.0 usb. so i switched and when i rebooted carbon rom becase it says i need usb debugging on but when i rebboted my internal sd popped up and i tried to move the files and it worked and then reboot lol. i went into recovery and flashed google play rom and its working however my Afghanistan roshan simcard isnt working now i set it back to global but no go. what radio should i flash now if yours works fine with verizon ill just use yours. which one should I use ?

armyguy1989 said:
Well i feel like a dumbass right now unless its just a crazy stroke of luck. i had my usb plugged in to the ss 3.0 and when reading the instructions to setup up the adb it said to make sure you not using a 3.0 usb. so i switched and when i rebooted carbon rom becase it says i need usb debugging on but when i rebboted my internal sd popped up and i tried to move the files and it worked and then reboot lol. i went into recovery and flashed google play rom and its working however my Afghanistan roshan simcard isnt working now i set it back to global but no go. what radio should i flash now if yours works fine with verizon ill just use yours. which one should I use ?
Click to expand...
Click to collapse
Did you set the APN setting on the new Rom ?
Setting/mobile data/access point name
Stick with the newest Verizon radio I posted above

No I havent done that yet i just installed your radio ill try that now.

HTC One M8 With TWRP: Trouble With ROMs

Huge amount of frustration with trying to deal with my phone
I soft bricked my HTC One M8 HK not too long ago, and had left it sitting in the dust for a while as I had no options of fixing it because I wiped the memory on accident (how I did, I don't know. Guess I'm dumb. That's not the point though). It's been sitting on my dresser for about 2 months being unused as I had no microSD cards in hand. All it had was an unlocked bootloader and working TWRP.
As of right now, I've tried to install 4 ROMs. All 4 did not work. I followed the instructions and unlocked my bootloader and did all other essential things. I installed ViperOneM8 before being ignorant that my WiFi wouldn't work. It was the only ROM I installed that actually booted properly. The only issue was that I had no WiFi. Had it worked, I wouldn't be making this thread. Then I got Android Revolution HD, installed it and it installed properly. I booted it into system, and it brought me to bootloader. This was the same issue I had while trying to install my first ROM, and still happens. Then I got CyanogenMod, and it didn't even install. TWRP told me it failed right off the bat. Same thing with whenever I tried to install a stock firmware recovery of the variant I have, HK Sprint.
Right now, I'm getting the 4.2.5 HK RUU in hopes that it works. I tried it previously, and it was a literal waste of time. I've been here for 5 hours trying different ROMs and to no success. I was very faithful I would get to use my phone again, although unless this RUU actually works, I don't have a lot of positive faith for my phone.
Are there any fixes for getting something like CyanogenMod to work? I actually really wanted this ROM after I remembered it, and was quite let down after it failed to work. Also, is there anything I should do with the phone before I go farther with anything?
Thanks for any help you all can give, I would greatly appreciate it. Sucks not having a phone, so I'll take any help I can get. Thanks once again!
EDIT: The RUU did not work. It failed to update. Waiting for answers I guess..

F0rZ3r0 said:
I soft bricked my HTC One M8 HK not too long ago, and had left it sitting in the dust for a while as I had no options of fixing it because I wiped the memory on accident (how I did, I don't know. Guess I'm dumb. That's not the point though). It's been sitting on my dresser for about 2 months being unused as I had no microSD cards in hand. All it had was an unlocked bootloader and working TWRP.
As of right now, I've tried to install 4 ROMs. All 4 did not work. I followed the instructions and unlocked my bootloader and did all other essential things. I installed ViperOneM8 before being ignorant that my WiFi wouldn't work. It was the only ROM I installed that actually booted properly. The only issue was that I had no WiFi. Had it worked, I wouldn't be making this thread. Then I got Android Revolution HD, installed it and it installed properly. I booted it into system, and it brought me to bootloader. This was the same issue I had while trying to install my first ROM, and still happens. Then I got CyanogenMod, and it didn't even install. TWRP told me it failed right off the bat. Same thing with whenever I tried to install a stock firmware recovery of the variant I have, HK Sprint.
Right now, I'm getting the 4.2.5 HK RUU in hopes that it works. I tried it previously, and it was a literal waste of time. I've been here for 5 hours trying different ROMs and to no success. I was very faithful I would get to use my phone again, although unless this RUU actually works, I don't have a lot of positive faith for my phone.
Are there any fixes for getting something like CyanogenMod to work? I actually really wanted this ROM after I remembered it, and was quite let down after it failed to work. Also, is there anything I should do with the phone before I go farther with anything?
Thanks for any help you all can give, I would greatly appreciate it. Sucks not having a phone, so I'll take any help I can get. Thanks once again!
EDIT: The RUU did not work. It failed to update. Waiting for answers I guess..
Click to expand...
Click to collapse
Flashing RUU requires locked bootloader.

Alright, I'm seriously about to just throw this thing in the dumpster. I've been here another 2 hours trying to get Cyanogen to work, and I figured out the issue with it. The updater script file wasn't accepting m8_whl. I'm still unaware how in the Mod Edit I'm supposed to put m8_whl into the script for it to be accepted.
To be more specific, the actual updater script has m8whl, while my phone recognizes as m8_whl. It denies it.
I thought I put it into the script correctly, although it is not accepting it. I found a quote not saying the location, and I assumed in the latest release of Cyanogen 12 for M8s, it was in /META-INF/google/android/updater-script
Please, someone help me before I have an anger episode. This thing has literally wasted my whole Mod Edit day.

F0rZ3r0 said:
Alright, I'm seriously about to just throw this thing in the dumpster. I've been here another 2 hours trying to get Cyanogen to work, and I figured out the issue with it. The updater script file wasn't accepting m8_whl. I'm still unaware how in the Mod Edit I'm supposed to put m8_whl into the script for it to be accepted.
To be more specific, the actual updater script has m8whl, while my phone recognizes as m8_whl. It denies it.
I thought I put it into the script correctly, although it is not accepting it. I found a quote not saying the location, and I assumed in the latest release of Cyanogen 12 for M8s, it was in /META-INF/google/android/updater-script
Please, someone help me before I have an anger episode. This thing has literally wasted my whole Mod Edit day.
Click to expand...
Click to collapse
Don't toss it, it's still worth something, even if not to you. But as @popthosegaskets said, you need to relock the bootloader to flash the RUU. If it's been sitting for awhile, what version of firmware and hboot was it on prior to not working? Perhaps the issue is that it's older, also try flashing the newest version of TWRP if you still want to install a custom OS.
If you want to RUU, just use the fastboot command "fastboot oem lock" while in fastboot and then run the RUU. I think it reboots after locking.

dopy25 said:
Don't toss it, it's still worth something, even if not to you. But as @popthosegaskets said, you need to relock the bootloader to flash the RUU. If it's been sitting for awhile, what version of firmware and hboot was it on prior to not working? Perhaps the issue is that it's older, also try flashing the newest version of TWRP if you still want to install a custom OS.
If you want to RUU, just use the fastboot command "fastboot oem lock" while in fastboot and then run the RUU. I think it reboots after locking.
Click to expand...
Click to collapse
Alright, doing this now. I'm a lot calmer today, so I can do this.

dopy25 said:
Don't toss it, it's still worth something, even if not to you. But as @popthosegaskets said, you need to relock the bootloader to flash the RUU. If it's been sitting for awhile, what version of firmware and hboot was it on prior to not working? Perhaps the issue is that it's older, also try flashing the newest version of TWRP if you still want to install a custom OS.
If you want to RUU, just use the fastboot command "fastboot oem lock" while in fastboot and then run the RUU. I think it reboots after locking.
Click to expand...
Click to collapse
Didn't work, the RUU gave me the same error as last time, it tells me its the wrong RUU. Got both the stock RUUs just to see if I got it wrong about HK, both failed. Please help...

F0rZ3r0 said:
Didn't work, the RUU gave me the same error as last time, it tells me its the wrong RUU. Got both the stock RUUs just to see if I got it wrong about HK, both failed. Please help...
Click to expand...
Click to collapse
[Mod hat on] I know it can be frustrating at times but please take it easy with the swearing. [/Mod hat off]
You might try flashing the Full firmware that matches the RUU that you are trying to flash, the past couple updates require hboots to match on both your device and the RUU or you will get an error.

Sloth said:
[Mod hat on] I know it can be frustrating at times but please take it easy with the swearing. [/Mod hat off]
You might try flashing the Full firmware that matches the RUU that you are trying to flash, the past couple updates require hboots to match on both your device and the RUU or you will get an error.
Click to expand...
Click to collapse
My apologies for the swearing, was angry at the time.
Also, my hboot version seems to be 3.18. Not sure what to do in order to be able to flash firmware. My OS version seems to be 2.16.651.4 as well if that helps.
What would I have to do in order to install a ROM and how?

If you are not flashing the full firmware to begin with, that's the issue. From your OP it looks like you only have an unlocked BL and had TWRP.
You must relock the BL and then run the full RUU, you can get it in the thread here, or get it from HTC. Either way you need the full one, it flashes the FW and Software as well as bootloader and radios.
HTC: http://dl3.htc.com.s3.amazonaws.com..._NV_SPCS_1.52_003_release_446220_signed_2.exe
Thread with all and modified FW
http://forum.xda-developers.com/showthread.php?t=2729173
Are you S-Off or On? If you are running the *.651* then that's the non HK version. It's ok if you flashed a modified stock, but if you got that from an RUU, that would be what the issue is. I think

dopy25 said:
If you are not flashing the full firmware to begin with, that's the issue. From your OP it looks like you only have an unlocked BL and had TWRP.
You must relock the BL and then run the full RUU, you can get it in the thread here, or get it from HTC. Either way you need the full one, it flashes the FW and Software as well as bootloader and radios.
HTC: http://dl3.htc.com.s3.amazonaws.com..._NV_SPCS_1.52_003_release_446220_signed_2.exe
Thread with all and modified FW
http://forum.xda-developers.com/showthread.php?t=2729173
Are you S-Off or On? If you are running the *.651* then that's the non HK version. It's ok if you flashed a modified stock, but if you got that from an RUU, that would be what the issue is. I think
Click to expand...
Click to collapse
I believe I'm S-OFF.

F0rZ3r0 said:
I believe I'm S-OFF.
Click to expand...
Click to collapse
look in bootloader it will tell you if you are s-off or s-on.

Sloth said:
look in bootloader it will tell you if you are s-off or s-on.
Click to expand...
Click to collapse
Never mind, S-ON.

F0rZ3r0 said:
Never mind, S-ON.
Click to expand...
Click to collapse
Ok re-lock your bootloader if you have not already.
Flash this for Non HK 4.25.651.18 Full Firmware
Flash this for HK 4.25.654.18 Full Firmware
Instructions:
-rename firmware to firmware.zip
-copy firmware.zip to your sdk folder
-boot into bootloader
-plug in usb
-select fastboot option (screen should say fastboot usb)
-type fastboot oem rebootRUU
-when u see the black screen w/ HTC, type fastboot flash zip firmware.zip
-when it's done, type fastboot reboot
Once done flash the latest Non HK or HK RUU found here... http://forum.xda-developers.com/showthread.php?t=2729173
Then unlock your bootloader again using the unlock code you got from HTC.
Re-flash the latest TWRP found here... https://dl.twrp.me/m8/
This will give you a fresh start then you can try to flash the rom you want.

Sloth said:
Ok re-lock your bootloader if you have not already.
Flash this for Non HK 4.25.651.18 Full Firmware
Flash this for HK 4.25.654.18 Full Firmware
Instructions:
-rename firmware to firmware.zip
-copy firmware.zip to your sdk folder
-boot into bootloader
-plug in usb
-select fastboot option (screen should say fastboot usb)
-type fastboot oem rebootRUU
-when u see the black screen w/ HTC, type fastboot flash zip firmware.zip
-when it's done, type fastboot reboot
Once done flash the latest Non HK or HK RUU found here... http://forum.xda-developers.com/showthread.php?t=2729173
Then unlock your bootloader again using the unlock code you got from HTC.
Re-flash the latest TWRP found here... https://dl.twrp.me/m8/
This will give you a fresh start then you can try to flash the rom you want.
Click to expand...
Click to collapse
Umm...I don't have anything called SDK :/
What do I do then?

F0rZ3r0 said:
Umm...I don't have anything called SDK :/
What do I do then?
Click to expand...
Click to collapse
If you have a platform-tools you can use that or use the folder attached.
Unzip it and copy the files to a folder.

Sloth said:
If you have a platform-tools you can use that or use the folder attached.
Unzip it and copy the files to a folder.
Click to expand...
Click to collapse
Alright, I did it all, but it doesn't seem to be changing once I send over the zip. Is it meant to take a while or is there something wrong?
EDIT: 20 minutes later and still at the sending. Something probably went wrong.
EDIT 2: 30 minutes later, still sending.

F0rZ3r0 said:
Alright, I did it all, but it doesn't seem to be changing once I send over the zip. Is it meant to take a while or is there something wrong?
EDIT: 20 minutes later and still at the sending. Something probably went wrong.
EDIT 2: 30 minutes later, still sending.
Click to expand...
Click to collapse
Should only be a few seconds.

Sloth said:
Should only be a few seconds.
Click to expand...
Click to collapse
Not sure what the issue here is then. As I write this, it is still sending. I'm not sure what the issue is...

Check PM.