Database Develop

Need help here urgently

I've helped my friend to flash his Incredible S and i've experienced problems in the process. He Has a HBOOT version of 1.16.0000 and has a radio version of 3805.09.03.27_M. I've attempted to unlock the bootloader using the htcdev website's method. All the steps went well but after all the procedures, the phone still appears as S-ON. I've managed to flash the recovery into the phone and used it to flash a custom rom (Android Revolution) and rebooted the phone after the flashing is complete. The phone just gets stuck at the HTC logo with white background. I've then decided to revert everything back to normal by flashing back to stock with the official RUU but i had error 150 while flashing. I've also tried renaming the rom.zip into PG32IMG.zip to flash it through HBOOT but nothing happens. I'm really lost now, can someone give me a solution to it?

verx123 said:
I've helped my friend to flash his Incredible S and i've experienced problems in the process. He Has a HBOOT version of 1.16.0000 and has a radio version of 3805.09.03.27_M. I've attempted to unlock the bootloader using the htcdev website's method. All the steps went well but after all the procedures, the phone still appears as S-ON. I've managed to flash the recovery into the phone and used it to flash a custom rom (Android Revolution) and rebooted the phone after the flashing is complete. The phone just gets stuck at the HTC logo with white background. I've then decided to revert everything back to normal by flashing back to stock with the official RUU but i had error 150 while flashing. I've also tried renaming the rom.zip into PG32IMG.zip to flash it through HBOOT but nothing happens. I'm really lost now, can someone give me a solution to it?
Click to expand...
Click to collapse
s-on will be there...u will just be able to use custom recovery. try flashing a custom rom different from Android Revolution . by the way ..in android revolution you can also try to flash the "revert to stock 1.0 Ghz" patch because sometimes it causes that problem due to OC settings not suiting a phone.
want s-off too? See this

ajeya said:
s-on will be there...u will just be able to use custom recovery. try flashing a custom rom different from Android Revolution . by the way ..in android revolution you can also try to flash the "revert to stock 1.0 Ghz" patch because sometimes it causes that problem due to OC settings not suiting a phone.
want s-off too? See this
Click to expand...
Click to collapse
just wanna ask! how to revert to stock 1.0ghz!

I thank you for your reply.another question, can I still flash to
a sense based ROM?
Sent from my GT-N7000 using XDA App

verx123 said:
I thank you for your reply.another question, can I still flash to
a sense based ROM?
Sent from my GT-N7000 using XDA App
Click to expand...
Click to collapse
One other tip since you are dealing with an unlocked HBOOT version. When you flash a custom ROM in recovery mode you must then manually flash the boot.img file from the zip file in Fastboot mode using the command:
Fastboot flash boot [path to boot.img]

tpbklake said:
One other tip since you are dealing with an unlocked HBOOT version. When you flash a custom ROM in recovery mode you must then manually flash the boot.img file from the zip file in Fastboot mode using the command:
Fastboot flash boot [path to boot.img]
Click to expand...
Click to collapse
Umm, the path to boot.img is the root of the sdcard am i right?

Thanks guys i managed to get it S-offed and flashed to a sense 3.5 rom. But i have another problem now, my signals are super low, most of the time it write limited services. I've flashed to another radio version but the signal's still the same weak.

santhoshpirate said:
just wanna ask! how to revert to stock 1.0ghz!
Click to expand...
Click to collapse
by flashing this patch in ARHD rom !
---------- Post added at 09:52 PM ---------- Previous post was at 09:50 PM ----------
verx123 said:
Thanks guys i managed to get it S-offed and flashed to a sense 3.5 rom. But i have another problem now, my signals are super low, most of the time it write limited services. I've flashed to another radio version but the signal's still the same weak.
Click to expand...
Click to collapse
what radios have u tried? were the signals good enough before ?

It was normal until I flashed to the sense 3.5 ROM, but I've found a solution to it by flashing to an older radio version.thanks for helping me out
Sent from my GT-N7000 using XDA App

Returning back to stock while keeping root

Hi everyone!
This is my first post, since I never had any trouble toying around with my device. I have a rooted Incredible S, that ran MIUI perfectly. I want to return back to stock (this is imperative) and use the official ICS by HTC. I tried putting back my nandroid backup, which didn't work (perhaps an incompatible radio? I have no idea...). That's when I downloaded a stock, cracked ROM from a thread I found here. This is a Gingerbread ROM with Sence 3.0 I think. Obviously, I can't get the OTA to work. I think the issue here is that my recovery is still CWM, and that OTA only works with the stock recovery (this is what I concluded from research).
This is where I'm having trouble. A RUU doesn't seem to recognise my device, so that's not an option right now. Windows recognises my SD card when I hook up my phone through USB, so I can install ROMs just fine. Is there any way to get the stock recovery and the stock ROM without using a RUU, while keeping my device rooted? I really want all of this to be stock, so no mods, hacks or tweaks. I want my phone to be in the same state as when I bought it and rooted it, before installing custom ROMS. Is this possible?
Many, many thanks in advance!

gladii said:
Hi everyone!
This is my first post, since I never had any trouble toying around with my device. I have a rooted Incredible S, that ran MIUI perfectly. I want to return back to stock (this is imperative) and use the official ICS by HTC. I tried putting back my nandroid backup, which didn't work (perhaps an incompatible radio? I have no idea...). That's when I downloaded a stock, cracked ROM from a thread I found here. This is a Gingerbread ROM with Sence 3.0 I think. Obviously, I can't get the OTA to work. I think the issue here is that my recovery is still CWM, and that OTA only works with the stock recovery (this is what I concluded from research).
This is where I'm having trouble. A RUU doesn't seem to recognise my device, so that's not an option right now. Windows recognises my SD card when I hook up my phone through USB, so I can install ROMs just fine. Is there any way to get the stock recovery and the stock ROM without using a RUU, while keeping my device rooted? I really want all of this to be stock, so no mods, hacks or tweaks. I want my phone to be in the same state as when I bought it and rooted it, before installing custom ROMS. Is this possible?
Many, many thanks in advance!
Click to expand...
Click to collapse
Hey mate, official welcome from me Second welcome from me today lol
I would advise against going s-on and fully stock.
You cannot run a ruu or ota with a custom recovery/root.
So the easiest way to get the stock experience you want is by flashing one of tpbklake's rooted stock roms. They are basically stock roms with root and can run on a custom recovery. No tweaks or anything
http://forum.xda-developers.com/showthread.php?t=1773520
http://forum.xda-developers.com/showthread.php?t=1756500
The link above (top one) is based off a newer ruu from asia, although there is not much difference
I would also suggest to try ARHD 3.0.x for the stock optimised rom
Also which bootloader version do you have?

gladii said:
Hi everyone!
This is my first post, since I never had any trouble toying around with my device. I have a rooted Incredible S, that ran MIUI perfectly. I want to return back to stock (this is imperative) and use the official ICS by HTC. I tried putting back my nandroid backup, which didn't work (perhaps an incompatible radio? I have no idea...). That's when I downloaded a stock, cracked ROM from a thread I found here. This is a Gingerbread ROM with Sence 3.0 I think. Obviously, I can't get the OTA to work. I think the issue here is that my recovery is still CWM, and that OTA only works with the stock recovery (this is what I concluded from research).
This is where I'm having trouble. A RUU doesn't seem to recognise my device, so that's not an option right now. Windows recognises my SD card when I hook up my phone through USB, so I can install ROMs just fine. Is there any way to get the stock recovery and the stock ROM without using a RUU, while keeping my device rooted? I really want all of this to be stock, so no mods, hacks or tweaks. I want my phone to be in the same state as when I bought it and rooted it, before installing custom ROMS. Is this possible?
Many, many thanks in advance!
Click to expand...
Click to collapse
Yes there a some ROMs in the Development section that are completely stock that you can flash through recovery.
The original GB 2.3.3/Sense 2.1, the GB 2.3.5/Sense 3.0 and the latest ICS 4.0.4/Sense 3.6

markj338 said:
Hey mate, official welcome from me Second welcome from me today lol
I would advise against going s-on and fully stock.
You cannot run a ruu or ota with a custom recovery/root.
So the easiest way to get the stock experience you want is by flashing one of tpbklake's rooted stock roms. They are basically stock roms with root and can run on a custom recovery. No tweaks or anything
http://forum.xda-developers.com/showthread.php?t=1773520
http://forum.xda-developers.com/showthread.php?t=1756500
The link above (top one) is based off a newer ruu from asia, although there is not much difference
I would also suggest to try ARHD 3.0.x for the stock optimised rom
Also which bootloader version do you have?
Click to expand...
Click to collapse
I'm going to sell my device so I need it back the way it was. I want to keep it rooted though, so that the next owner can decide for himself what he wants to do with it. If he he's no techie, he can enjoy the device in stock (including OTAs, or can this be done like you mentioned?). If whe wants to toy with it, he can do that too. If it's easier to just go back to stock entirely, that's fine too.
It seems that I can no longer get into hboot now? After installing that hacked gingerbread, my device just boots into Android when pressing volume down and power??
tpbklake, I'll try to flash one of those when I can get back into recovery

Weird.. Taking out the battery fixed my recovery issue. I'll flash that ROM
Btw I seem to have hboot 6.13.1002 and radio 3805.06.03.03_M. Is this the info you need?

gladii said:
Weird.. Taking out the battery fixed my recovery issue. I'll flash that ROM
Btw I seem to have hboot 6.13.1002 and radio 3805.06.03.03_M. Is this the info you need?
Click to expand...
Click to collapse
Yes
But since you want stock it won't matter
You CANNOT have both root and ota updates
Either one or the other unfortunately
You have to make a choice a rooted stock ROM will be identical to the official ota from htc but you will be able to keep root, but can't get ota updates
but unfortunately I think sense 3.6 4.0.4 is the last update
But, I have been proven wrong before
Sent from my Nexus 7

K then in my case a full stock device would be best. How do I get started with this? First install a stock ROM, then the stock recovery and then put It back in S-OFF? Which ROM should I install (would prefer the stock 2.3.3)? And where can I find the recovery? Sorry for the basic questions but those lists of ROMs can get a bit complicated..

Still getting nowhere If I flash a stock ROM in CWM, my recovery won't go back to stock, will it? Shouldn't I try to get the stock recovery first and then use a RUU? Problem is that I can't seem to find a stock recovery anywhere. And when I extract the ROM from a RUU, it's only about 180 MB, so that can't be right, can it?

gladii said:
Still getting nowhere If I flash a stock ROM in CWM, my recovery won't go back to stock, will it? Shouldn't I try to get the stock recovery first and then use a RUU? Problem is that I can't seem to find a stock recovery anywhere. And when I extract the ROM from a RUU, it's only about 180 MB, so that can't be right, can it?
Click to expand...
Click to collapse
Which ruu? Here's a good guide http://forum.xda-developers.com/showthread.php?t=1359555 but I find it faster to flash the alparev then run the ruu, 2 steps and done.

Nonverbose said:
Which ruu? Here's a good guide http://forum.xda-developers.com/showthread.php?t=1359555 but I find it faster to flash the alparev then run the ruu, 2 steps and done.
Click to expand...
Click to collapse
Sorry for the late reply. I've been busy with exams. I've tried the RUU RUU_IncredibleC_Verizon_WWE_1.22.605.0_Radio_1.00.03.04.06_release_161493_NoDriver (but I don't actually have a Verizon, could that be the problem?).
I really have no idea what all the info in the filename means, so it's difficult to find one that fits my needs. I'll take a look at your link right now and report back!

gladii said:
Sorry for the late reply. I've been busy with exams. I've tried the RUU RUU_IncredibleC_Verizon_WWE_1.22.605.0_Radio_1.00.03.04.06_release_161493_NoDriver (but I don't actually have a Verizon, could that be the problem?).
I really have no idea what all the info in the filename means, so it's difficult to find one that fits my needs. I'll take a look at your link right now and report back!
Click to expand...
Click to collapse
DO NOT attemtp to flash that one!!!! The Verizon DINC2 is a CDMA device and the radio is not compatible.
Please read the post that nonverbose referenced for you. That tells you all you need to do.

tpbklake said:
DO NOT attemtp to flash that one!!!! The Verizon DINC2 is a CDMA device and the radio is not compatible.
Click to expand...
Click to collapse
Wow, good thing it didn't succeed! How about this one:
RUU_Vivo_Gingerbread_S_HTC_ARA_2.30.415.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199399_signed.exe
(download link: http://www.filefactory.com/file/c0af340/n/RUU_Vivo_Gingerbread_S_HTC_ARA_2.30.415.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199399_signed.exe)

gladii said:
Wow, good thing it didn't succeed! How about this one:
RUU_Vivo_Gingerbread_S_HTC_ARA_2.30.415.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199399_signed.exe
(download link: http://www.filefactory.com/file/c0a...5AU_3805.06.03.03_M_release_199399_signed.exe)
Click to expand...
Click to collapse
What region of the world are you in? I would recommend the HTC WWE 2.30.405.1.

tpbklake said:
What region of the world are you in? I would recommend the HTC WWE 2.30.405.1.
Click to expand...
Click to collapse
Belgium (Brussels), western Europe. I bought the device here so it should be pretty local... I'll try that one. What does the WWE mean? (Just for the info)

gladii said:
Belgium (Brussels), western Europe. I bought the device here so it should be pretty local... I'll try that one. What does the WWE mean? (Just for the info)
Click to expand...
Click to collapse
World Wide English with support for most European languages

gladii said:
Belgium (Brussels), western Europe. I bought the device here so it should be pretty local... I'll try that one. What does the WWE mean? (Just for the info)
Click to expand...
Click to collapse
Ah, perfect! Canceled my download, but there's a 20 minute interval before starting a new one, so it'll take me at least an hour to download it.

I've encountered this issue before, but randomness seemed to solve it back then: a fastboot command just displays "<waiting for device>" and then keeps hanging there. "fastboot devices" returns an empty line, so that's consistent. Phone is in fastboot USB mode, so I'm not sure what could be the issue?
And then I have a question. In that guide, it says that I should extract HBOOT.img from the rom I installed. In my case, my rom only contains a file named "hboot_1.13.0000_CRC_8a731c6e_0401.img" (along with others of course, but I assume they are redundant in this step); will that one do?

gladii said:
I've encountered this issue before, but randomness seemed to solve it back then: a fastboot command just displays "<waiting for device>" and then keeps hanging there. "fastboot devices" returns an empty line, so that's consistent. Phone is in fastboot USB mode, so I'm not sure what could be the issue?
And then I have a question. In that guide, it says that I should extract HBOOT.img from the rom I installed. In my case, my rom only contains a file named "hboot_1.13.0000_CRC_8a731c6e_0401.img" (along with others of course, but I assume they are redundant in this step); will that one do?
Click to expand...
Click to collapse
Sounds like it may be a port issue, cable issue or driver issue on the PC.
Have you tried different ports or a different cable? Do you have HTC Sync running in the System Tray on the PC?
As for the hboot file, yes that is the one.

gladii said:
And then I have a question. In that guide, it says that I should extract HBOOT.img from the rom I installed. In my case, my rom only contains a file named "hboot_1.13.0000_CRC_8a731c6e_0401.img" (along with others of course, but I assume they are redundant in this step); will that one do?
Click to expand...
Click to collapse
I thought you wanted to go to stock ICS? Hboot 1.13 it a gingerbread hboot. If you just flash the vivo_downgrade.img then run the ruu, there will be no need to extract and flash the hboot from the ruu.

Nonverbose said:
I thought you wanted to go to stock ICS? Hboot 1.13 it a gingerbread hboot. If you just flash the vivo_downgrade.img then run the ruu, there will be no need to extract and flash the hboot from the ruu.
Click to expand...
Click to collapse
No I wanted it back the way I wanted it. Rom, recovery,... all stock. But surely I'll give ICS a testdrive via OTA

[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] [SOLVED] Unlocked/Rooted with S-On want OTA

I would like to install the AT&T OTA of 4.4.2 but have a custom recovery and am unable to upgrade. I am rooted with the stock 4.3 ROM and have the twrp recovery installed. I have S-ON. I've searched around trying to find a way to get this to work but can't seem to figure it out. I've tried looking around for an AT&T 4.3 stock recovery to try and flash it but can't seem to find one. The one from the Dev sticky page is not available for download. Can someone detail the steps I have to perform to get the 4.4.2 OTA from AT&T. Thanks in advance.
[SOLVED]
OK, problem fixed and 4.4.2 installed from OTA. I had relocked the bootloader on my phone so... start from scratch. Steps to resolve
1 - Unlock Bootloader
2 - Get S-Off on device (Makes everything easier). I used Firewater (http://firewater-soff.com)
3 - Flash the AT&T 3.17.502.3 (4.3) RUU from here (http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/). You may need a different one if not on AT&T
4 - Start phone, check for update. Let it download. Cake.
Now off to redo all the settings on my phone. Hope this helps someone else.

You can extract recovery.IMG from the ATT 4.4.2 OTA update if you can't find anything else.
sent from my mobile device

SaHiLzZ said:
You can extract recovery.IMG from the ATT 4.4.2 OTA update if you can't find anything else.
sent from my mobile device
Click to expand...
Click to collapse
Awesome, that's what I wanted to hear. I'm going to give that a shot. Thank you

Stock recoveries here: http://d-h.st/users/guich/?fld_id=29380#files
sent from my mobile device

SaHiLzZ said:
Stock recoveries here: http://d-h.st/users/guich/?fld_id=29380#files
sent from my mobile device
Click to expand...
Click to collapse
I flashed my recovery but recovery now just gets a read triangle with the exclamation

Let the phone download OTA and apply it
sent from my mobile device

SaHiLzZ said:
Let the phone download OTA and apply it
sent from my mobile device
Click to expand...
Click to collapse
Doing now.

It downloaded and attempted to install, then failed half way. Anything else I have to do before I update? Do I have to lock my bootloader again or unroot?
Sent from my HTC One using xda app-developers app

Yea lock bootloader
sent from my mobile device

No dice. Same deal.
Sent from my HTC One using xda app-developers app

Text/Photo of the error?

SaHiLzZ said:
Text/Photo of the error?
Click to expand...
Click to collapse
It doesn't give me an error. The OTA downloads, reboots and gets to a triangle with the green arrows inside and starts installing, then about 25% of the way it stops and goes to a red triangle. I'm thinking the MD5 to one of my files may be failing. I installed an edit to the framework sometime ago to get the hotspot working (that's the only change to the stock rom I've made). It doesn't really give me an error message though.

It could be the issue. You will need to choose one of the few options:
1. Restore a stock ATT OS for the same version you have (4.3) and update again
2. S-OFF (Preferred to avoid future messy bricks) and reinstall old ATT RUU and then upgrade all the way without custom rom/rooting/firmware changes
3. Wait for someone to post a custom rom install of the new ATT 4.4 update and install that.

SaHiLzZ said:
It could be the issue. You will need to choose one of the few options:
1. Restore a stock ATT OS for the same version you have (4.3) and update again
2. S-OFF (Preferred to avoid future messy bricks) and reinstall old ATT RUU and then upgrade all the way without custom rom/rooting/firmware changes
3. Wait for someone to post a custom rom install of the new ATT 4.4 update and install that.
Click to expand...
Click to collapse
Thanks, I appreciate your help. I think I'm gonna go with option 2, depending on how much time I have to do this, or 3 if time is an issue. Just one more question for you. Is firewater the best method to get S-Off or do you recommend a different one?

SMaximus7 said:
Thanks, I appreciate your help. I think I'm gonna go with option 2, depending on how much time I have to do this, or 3 if time is an issue. Just one more question for you. Is firewater the best method to get S-Off or do you recommend a different one?
Click to expand...
Click to collapse
If the ota stops on the second half as you discribe I think you have the wrong stock recovery. Different version than your "version-main"

mb_guy said:
If the ota stops on the second half as you discribe I think you have the wrong stock recovery. Different version than your "version-main"
Click to expand...
Click to collapse
I guess it can't hurt to try and reflash the recovery and retry. I'll give it a try.

SMaximus7 said:
I guess it can't hurt to try and reflash the recovery and retry. I'll give it a try.
Click to expand...
Click to collapse
I had the exact same thing occur, had a newer recovery than "fastboot getvar all"

mb_guy said:
I had the exact same thing occur, had a newer recovery than "fastboot getvar all"
Click to expand...
Click to collapse
It could be because I flashed the recovery that came with the OTA with fastboot and then after SaHiLzZ pointed me in the right direction was able to download the 4.3 recovery but flashed that one with flashify. I bet you the one I did with flashify didn't take. Funny thing is I also relocked my bootloader and now must unlock it again and that will probably wipe my device. What a mess, oh well, I hope that's all it is and at least I'm learning as I go.

SMaximus7 said:
It could be because I flashed the recovery that came with the OTA with fastboot and then after SaHiLzZ pointed me in the right direction was able to download the 4.3 recovery but flashed that one with flashify. I bet you the one I did with flashify didn't take. Funny thing is I also relocked my bootloader and now must unlock it again and that will probably wipe my device. What a mess, oh well, I hope that's all it is and at least I'm learning as I go.
Click to expand...
Click to collapse
Ya, I was lucky, had a nandroid . But you are right the recovery in the ota is too new.

Solved
OK, problem fixed and 4.4.2 installed from OTA. I had relocked the bootloader on my phone so... start from scratch. Steps to resolve
1 - Unlock Bootloader
2 - Get S-Off on device (Makes everything easier). I used Firewater (http://firewater-soff.com)
3 - Flash the AT&T 3.17.502.3 (4.3) RUU from here (http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/). You may need a different one if not on AT&T
4 - Start phone, check for update. Let it download. Cake.
Now off to redo all the settings on my phone. Hope this helps someone else. Thanks everybody for chiming in.

[Q] Need help getting back to stock

Hello, I have rooted (s-on) my Htc one m8 Harmon/Kardon edition. I have seen a lot of threads and guides showing how to do this but none of them seem to apply to my specific cid, which is SPCS_004. I haven't been able to find any compatible nandroid backups. I think maybe im just in over my head and I don't want to mess anything up....can anyone point me in the right direction?

darth_skater said:
Hello, I have rooted (s-on) my Htc one m8 Harmon/Kardon edition. I have seen a lot of threads and guides showing how to do this but none of them seem to apply to my specific cid, which is SPCS_004. I haven't been able to find any compatible nandroid backups. I think maybe im just in over my head and I don't want to mess anything up....can anyone point me in the right direction?
Click to expand...
Click to collapse
Just to be clear, I have installed a custom rom and I am now wanting to go back to the original stock rom.....and also the stock recovery if possible so I can install OTA updates.

darth_skater said:
Just to be clear, I have installed a custom rom and I am now wanting to go back to the original stock rom.....and also the stock recovery if possible so I can install OTA updates.
Click to expand...
Click to collapse
RUU is the easiest way to return to stock

BD619 said:
RUU is the easiest way to return to stock
Click to expand...
Click to collapse
So if i just run that, i will be completely back to stock? and if I have the hk model, it is definitely compatible?

darth_skater said:
So if i just run that, i will be completely back to stock? and if I have the hk model, it is definitely compatible?
Click to expand...
Click to collapse
Yes it will wipe your phone just like it came from the factory, so backup anything important to your PC.
Yes there a HK RUU's and non HK RUU's in the thread I linked.

You can download the RUU directly from HTC:
http://www.htc.com/us/support/htc-one-m8-harman-kardon-edition-sprint/news/
It is located at the bottom of the page. But you might want to wait a few days and download the Lollipop RUU when it releases. It will replace the current KK version once approved and FOTA is pushed out.

BD619 said:
Yes it will wipe your phone just like it came from the factory, so backup anything important to your PC.
Yes there a HK RUU's and non HK RUU's in the thread I linked.
Click to expand...
Click to collapse
It threw me an error. ERROR [155]: UNKNOWN ERROR the ROM update utility cannot update your android phone. Please get the correct ROM update utility and try again. This is what I was trying to avoid. Now my phone won't boot at all.

darth_skater said:
It threw me an error. ERROR [155]: UNKNOWN ERROR the ROM update utility cannot update your android phone. Please get the correct ROM update utility and try again. This is what I was trying to avoid. Now my phone won't boot at all.
Click to expand...
Click to collapse
Here are some things to try.
Did you re-lock your bootloader?
Try a different USB port (USB2 work best)
Try a different PC.
To get back to bootloader press power vol up until the screen turns black then hold vol down.
If you know how to use adb/fastboot commands you can open a cmd and type
fastboot reboot-bootloader

BD619 said:
Here are some things to try.
Did you re-lock your bootloader?
Try a different USB port (USB2 work best)
Try a different PC.
To get back to bootloader press power vol up until the screen turns black then hold vol down.
If you know how to use adb/fastboot commands you can open a cmd and type
fastboot reboot-bootloader
Click to expand...
Click to collapse
I did not re lock my bootloader. I tried a different usb port, with no luck. I don't have another PC to try it with. What should I do to at least get my phone working in the meantime? even if it isn't stock? Can I just flash a rom through recovery?

darth_skater said:
I did not re lock my bootloader. I tried a different usb port, with no luck. I don't have another PC to try it with. What should I do to at least get my phone working in the meantime? even if it isn't stock? Can I just flash a rom through recovery?
Click to expand...
Click to collapse
If you are s-on you have to re-lock the bootloader for it to work.
You should be able to flash a rom thru recovery.

BD619 said:
If you are s-on you have to re-lock the bootloader for it to work.
You should be able to flash a rom thru recovery.
Click to expand...
Click to collapse
I AM BACK IN BUSINESS! Thank you so much for your help.

darth_skater said:
I AM BACK IN BUSINESS! Thank you so much for your help.
Click to expand...
Click to collapse
Glad I could help