Database Develop

[Q] Stock image / rom

Well, I've been trying to use some custom roms and after all I restored the backup I made before, everything fine.
Today I wanted to try to use a custom rom again but it wouldn't work so I decided to wait for the official ICS release for the IncS. And here we get to my problem: When I restore the backup, and manually flash the boot.img (have to do this manually, got S-ON) and I boot my phone it gets to the HTC bootscreen, reboots and automatically gets to the CWM recovery.
Can anyone provide me an original boot.img (I haven't found it yet) or the whole standard android rom? If you have another solution, I would like to hear it!

Vaxx93 said:
Well, I've been trying to use some custom roms and after all I restored the backup I made before, everything fine.
Today I wanted to try to use a custom rom again but it wouldn't work so I decided to wait for the official ICS release for the IncS. And here we get to my problem: When I restore the backup, and manually flash the boot.img (have to do this manually, got S-ON) and I boot my phone it gets to the HTC bootscreen, reboots and automatically gets to the CWM recovery.
Can anyone provide me an original boot.img (I haven't found it yet) or the whole standard android rom? If you have another solution, I would like to hear it!
Click to expand...
Click to collapse
You can find the latest OTA in the Android Dev section. If you would use the search function ( yeah we really have a "search" function.. ) you would easily find it. If you want your boot.img we do need what for a Rom from which carrier you got.

Silversniper said:
You can find the latest OTA in the Android Dev section. If you would use the search function ( yeah we really have a "search" function.. ) you would easily find it. If you want your boot.img we do need what for a Rom from which carrier you got.
Click to expand...
Click to collapse
Actually I DID use the search, but I haven't found any stock roms for the IncS.. I would like a boot.img for T-Mobile carrier (that's what a 'carrier' is right?).

Vaxx93 said:
Actually I DID use the search, but I haven't found any stock roms for the IncS.. I would like a boot.img for T-Mobile carrier (that's what a 'carrier' is right?).
Click to expand...
Click to collapse
Here is the sticky thread in the Development section that contains official HTC Shipped RUU/ROMs for the IncS.
http://forum.xda-developers.com/showthread.php?t=1033922

tpbklake said:
Here is the sticky thread in the Development section that contains official HTC Shipped RUU/ROMs for the IncS.
http://forum.xda-developers.com/showthread.php?t=1033922
Click to expand...
Click to collapse
Thàt is helpfull! Thanks! Now my, probably last, question: how do I know which version I need? I know I have a WWE version, but which one?

Vaxx93 said:
Thàt is helpfull! Thanks! Now my, probably last, question: how do I know which version I need? I know I have a WWE version, but which one?
Click to expand...
Click to collapse
I have just been reviewing your posts and you posted that you applied the OTA and received HBOOT 2.01.0001, correct?
Then the RUU/ROM you need is the 3.11.405.2 version.
You also stated that you were able to unlock HBOOT 2.01.0001 using the HTCDEV.com site, correct? Which custom recovery did you install after that?

tpbklake said:
I have just been reviewing your posts and you posted that you applied the OTA and received HBOOT 2.01.0001, correct?
Then the RUU/ROM you need is the 3.11.405.2 version.
You also stated that you were able to unlock HBOOT 2.01.0001 using the HTCDEV.com site, correct? Which custom recovery did you install after that?
Click to expand...
Click to collapse
That's all correct, I installed the CWM recovery after that, not sure which version, the most recent one if I'm sure. I notice that the RUU/ROMS are .exe, do I flash these the same way as a .zip rom?

Vaxx93 said:
That's all correct, I installed the CWM recovery after that, not sure which version, the most recent one if I'm sure. I notice that the RUU/ROMS are .exe, do I flash these the same way as a .zip rom?
Click to expand...
Click to collapse
No, you run the exe on a PC and follow the directions on the screens. The program will tell you when to connect your phone to the PC using the USB cable.
This will completely wipe your phone and reload the ROM. Your HBOOT screen will probably show RELOCKED and you will need to unlock it again. Please confirm.

tpbklake said:
No, you run the exe on a PC and follow the directions on the screens. The program will tell you when to connect your phone to the PC using the USB cable.
This will completely wipe your phone and reload the ROM. Your HBOOT screen will probably show RELOCKED and you will need to unlock it again. Please confirm.
Click to expand...
Click to collapse
If that's true, I LOVE YOU, that's what I've been looking for. Is there a way to save my data like contacts, whatsapp messages and settings and stuff or do I have to live with the fact that I get a completely "new" phone?

Vaxx93 said:
If that's true, I LOVE YOU, that's what I've been looking for. Is there a way to save my data like contacts, whatsapp messages and settings and stuff or do I have to live with the fact that I get a completely "new" phone?
Click to expand...
Click to collapse
You can sync your contacts to your Google/Gmail account or save them to your SD cards. You can use Titanium Backup to backup apps and some settings.

Well this sucks: The ROM Updatestff can't update the Android hpone. Get the right ROM Update program and try again.
Were you sure that this is the right one? ;p

Vaxx93 said:
Well this sucks: The ROM Updatestff can't update the Android hpone. Get the right ROM Update program and try again.
Were you sure that this is the right one? ;p
Click to expand...
Click to collapse
This is the only one that has HBOOT 2.01.0001. You will also need to relock your HBOOT before you run the RUU using the command:
fastboot oem lock

tpbklake said:
This is the only one that has HBOOT 2.01.0001. You will also need to relock your HBOOT before you run the RUU using the command:
fastboot oem lock
Click to expand...
Click to collapse
Okay I did that now, it said that it was succeeded and a line under that one it said that it failed. Trying to update now, curious what happens.
It seems that he's updating now!

He updated it to the original Android, dude, you're amazing! Thanks mennnn! Just forbid myself to ever try a custom rom again and just stick to waiting for official releases

Vaxx93 said:
He updated it to the original Android, dude, you're amazing! Thanks mennnn! Just forbid myself to ever try a custom rom again and just stick to waiting for official releases
Click to expand...
Click to collapse
Glad to help! Next time just use the "Thanks" button....

Ah ofcourse, I'm pretty new to the forum and didn't notice the thanksbutton before. Used it to thank you right away!

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] [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

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.