Develop Bugs

When are we getting a Dev Edition RUU!?

Phone has been out a while now but still no developer edition RUU. I'm interested in converting by M8 (which is an AT&T variant previously converted to a GPE) to a developer edition version but don't want to do so until the RUU is released. Does anyone know HTC's typical time frame for releasing it? Is there any other fairly simple way to make this conversion from GPE to Developer Edition? Thanks.

Lol I need help with this too. I have SIM Unlocked BS_US002 and converted to GPE. The Dev RUU would be the closest to my phone and there is no 1540 firmwares posted so I can't get back to Sense.
Sent from my HTC One_M8 using Tapatalk

metaphz said:
Lol I need help with this too. I have SIM Unlocked BS_US002 and converted to GPE. The Dev RUU would be the closest to my phone and there is no 1540 firmwares posted so I can't get back to Sense.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
NextNexus said:
Phone has been out a while now but still no developer edition RUU. I'm interested in converting by M8 (which is an AT&T variant previously converted to a GPE) to a developer edition version but don't want to do so until the RUU is released. Does anyone know HTC's typical time frame for releasing it? Is there any other fairly simple way to make this conversion from GPE to Developer Edition? Thanks.
Click to expand...
Click to collapse
There are a bunch of guides on this. All you have to do is flash the ota firmware, change mid/cid, and put developer nandroid and recovery on your phone. Obviously check/change mid/cid before flashing the firmware.zip.

an0ther said:
There are a bunch of guides on this. All you have to do is flash the ota firmware, change mid/cid, and put developer nandroid and recovery on your phone. Obviously check/change mid/cid before flashing the firmware.zip.
Click to expand...
Click to collapse
Can you direct me to a specific guide? Thanks.

NextNexus said:
Can you direct me to a specific guide? Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2739571&page=3
scroll down a little, look for the big post

an0ther said:
http://forum.xda-developers.com/showthread.php?t=2739571&page=3
scroll down a little, look for the big post
Click to expand...
Click to collapse
That's just the OTA update. How is a 110MB update going to wipe GPE and repartition the Device, and install Sense.
Sent from my HTC One_M8 using Tapatalk

Ive also gone back and forth with the GPE and SenseUI based setups. I would much rather have an RUU to re partition my device but the guide worked fairly well. I have never waitied this long for an RUU for an HTC device tho.

serialtoon said:
Ive also gone back and forth with the GPE and SenseUI based setups. I would much rather have an RUU to re partition my device but the guide worked fairly well. I have never waitied this long for an RUU for an HTC device tho.
Click to expand...
Click to collapse
Right. Just seems a little strange that HTC hasn't released the official RUU yet.

s-off hboot 3.16

Is it possible to s-off hboot 3.16 wihout using SunShine? Just want to get red of that red text. Doing my head in.

Kahun said:
Is it possible to s-off hboot 3.16 wihout using SunShine? Just want to get red of that red text. Doing my head in.
Click to expand...
Click to collapse
if u get a whelp message using firewater, sunshine is ur only way to go

S-off with firewater worked fine for me on the AT&T version with 3.16 hboot (before sunshine even existed). As mentioned, you can always try it, as there is no harm in doing so. Worst that will happen is firewater tells you it won't work.
But if you are on AT&T (don't know if other carriers have hboot 3.16) firewater should work fine.

redpoint73 said:
S-off with firewater worked fine for me on the AT&T version with 3.16 hboot (before sunshine even existed). As mentioned, you can always try it, as there is no harm in doing so. Worst that will happen is firewater tells you it won't work.
But if you are on AT&T (don't know if other carriers have hboot 3.16) firewater should work fine.
Click to expand...
Click to collapse
Think OP is from uk, no ATT here mate lol

exocetdj said:
Think OP is from uk, no ATT here mate lol
Click to expand...
Click to collapse
No idea, as there is also an Ipswich in Massachusetts, USA. Folks need to be specific (as you have kindly done in your "location") as a great many town names happen in multiple different places (especially UK and New England, USA).
In any case, my feeling is firewater is only patched in later hboots, and any phone with hboot 3.16 will probably work. I can only comment on the AT&T version, since that is what I own.

redpoint73 said:
No idea, as there is also an Ipswich in Massachusetts, USA. Folks need to be specific (as you have kindly done in your "location") as a great many town names happen in multiple different places (especially UK and New England, USA).
In any case, my feeling is firewater is only patched in later hboots, and any phone with hboot 3.16 will probably work. I can only comment on the AT&T version, since that is what I own.
Click to expand...
Click to collapse
It was wierd with firewater, i got my m8 5 days after UK release and firewater would not work on mine, but i have heard it worked with alot of the ATT and verizon models in the US

exocetdj said:
It was wierd with firewater, i got my m8 5 days after UK release and firewater would not work on mine, but i have heard it worked with alot of the ATT and verizon models in the US
Click to expand...
Click to collapse
That is strange. Have you seen similar reports from others on your variant?

redpoint73 said:
That is strange. Have you seen similar reports from others on your variant?
Click to expand...
Click to collapse
Yup, alot of unbranded european users got the dreaded "whelp" message whilst peeps in the US were celebrating s off lol

exocetdj said:
Yup, alot of unbranded european users got the dreaded "whelp" message whilst peeps in the US were celebrating s off lol
Click to expand...
Click to collapse
Good to know, thanks. I know firewater doesn't work for newer hboots; but wasn't aware that other versions with hboot 3.16 are not compatible as well.
As you already mentioned, the worst that can happen is OP runs firewater, and he gets the "whelp" message. So its worth a shot.

redpoint73 said:
As you already mentioned, the worst that can happen is OP runs firewater, and he gets the "whelp" message. So its worth a shot.
Click to expand...
Click to collapse
true, defo worth a shot
it won't blow up everything like typing google into google does hahahaha

I tried firewater before I posted here and it didn't work. Its Ipswich in UK I'm from.

exocetdj said:
true, defo worth a shot
it won't blow up everything like typing google into google does hahahaha
Click to expand...
Click to collapse
I have AT&T variant with 3.16 and it doesn't work. Tried multiple times. That sucks lol
Sent from my HTC One_M8 using XDA Free mobile app

I'm looking for an old version of firewater to S-OFF my AT&T htc one m8 with Hboot 3.16 and 4.4.2 android some one keeped and archive of this file please ?

youssefz said:
I'm looking for an old version of firewater to S-OFF my AT&T htc one m8 with Hboot 3.16 and 4.4.2 android some one keeped and archive of this file please ?
Click to expand...
Click to collapse
That won't work. Firewater was an online service. It stopped working once the dev stopped supporting it in December.
Sunshine s-off is the only current working method.

Other person's nandroid?

I have found a nandroid backup that is compatible with my device. Do I flash the .zip like a custom ROM? I tried extracting the folder to TWRP/BACKUPS/*number*/ but when I go to recovery and restore, it will not see the folder. What do I do?
Sent from my HTC One_M8 using XDA Free mobile app

TWRP expects the nandroid to be in a specific folder and the one you got probably has the incorrect device ID.
Go into TWRP > backup and make a nandroid only of your recovery.
Then go to /sdcard/TWRP/Backup and inside you should see another folder named with your phones device ID.
Open it and delete the contents.
Then copy the contents of the nandroid you want to restore into that folder.
When you go back to TWRP > Restore, it now should find the nandroid - IF that nandroid was made in a compatible TWRP version. If it was made in CWM you would have to use that recovery.
Kinda risky what you are trying to do unless you know exactly how that nandroid was created.
Better to flash a RUU, IMHO.

You say it's risky? Would this possibly brick my phone? I don't care if it won't boot up or soft bricked after this but do you recommend doing this or not?
Sent from my HTC One_M8 using XDA Free mobile app

I don't know....
Do you trust the source of the nandroid?
Do you know what exactly the person was running at the time?
Do you know with which recovery and version thereof it was created and if that is compatible with your recovery?
I wouldn't do it. Flash a RUU if you want to go back to stock.

a nandroid won't brick your device ! And there are no sense ruu files ... at least no carrier branded ones. And when you download the nand and check the recovery.log you can read all info.
You think i keep a thread up that will brick devices ?
Restoring a nandroid to get back to stock is very safe !

Mr Hofs said:
Dude a nandroid won't brick your device ! And there are no sense ruu files ...
Click to expand...
Click to collapse
Errr, I have the RUU for the AT&T M8... I used it to restore one of my M8's to stock. When I upgraded it to the VIper 2.0 rom, the dual camera kept giving me a blocked warning. So I found the RUU for the phone and restored it to 4.4.2 Stock rom. But since I own 2 M8's I had one set up the way I like, so I just transfered the file to the second M8 and restore it to the phone. Worked like a charm. Funny how I have 2 M8's, had them both on Viper 2.1.0. One gives the dual camera warning, one doesn't. So I restore the one with the warning to stock, and the warning disappeared..

Yeah but what about people with a s-on device and a specific carrier..
Where are those ruu files ? There aren't any.....there is a very small selection of ruu files that can help a small group of people ! That's my point here. And who said he has a AT&T ..... Check my thread and check all the cid and main numbers then give me the links to the ruu files that are compatible with the nands i am hosting there.....get my point ?

Mr Hofs said:
a nandroid won't brick your device ! And there are no sense ruu files ... at least no carrier branded ones. And when you download the nand and check the recovery.log you can read all info.
You think i keep a thread up that will brick devices ?
Restoring a nandroid to get back to stock is very safe !
Click to expand...
Click to collapse
Hey mate! No reason to get offended! I did not mean to question your integrity or something and much less to insult you. I did not and still do not have any idea where the OP got the nandroid from! He never referenced it! Could have been from a friend's phone created with who knows what! Could have been from God knows what shady website...
That's why I asked him: Do you trust the source?
How am I to know it's you?

Ah well i am not offended. But i don't think a nand will likely brick the phone as it doesn't flash a firmware or such....it's actually only software so it's pretty harmless and easy to recover from

Mr Hofs said:
Ah well i am not offended. But i don't think a nand will likely brick the phone as it doesn't flash a firmware or such....it's actually only software so it's pretty harmless and easy to recover from
Click to expand...
Click to collapse
I never said that, OP asked that!
But I'm glad we're square :good:

Mr Hofs said:
Yeah but what about people with a s-on device and a specific carrier..
Where are those ruu files ? There aren't any.....there is a very small selection of ruu files that can help a small group of people ! That's my point here. And who said he has a AT&T ..... Check my thread and check all the cid and main numbers then give me the links to the ruu files that are compatible with the nands i am hosting there.....get my point ?
Click to expand...
Click to collapse
I am sorry for getting you mad, but I don't lie. The RUU file is here on XDA, like all the wise guys say
"Do a search"
I did, I downloaded it and installed in on my M8. ONly carrier I found was for AT&T, the OP didn't say
berndblb said:
I wouldn't do it. Flash a RUU if you want to go back to stock.
Click to expand...
Click to collapse
You did. So I was letting him know there was a RUU for AT&T on XDA. He didn't mention what carrier he was with. Since that was the only RUU I found for the M8, I suggested it.
Most of the rest of you stuff makes no sense.
Mr Hofs said:
Where are those ruu files ? There aren't any....
Click to expand...
Click to collapse
Wait, didn't you just tell him to:
berndblb said:
Flash a RUU if you want to go back to stock.
Click to expand...
Click to collapse
HUH You tell him to flash one in one breath, then state there is none in another. But IF he is on AT&T, I know there is one. I am not going to search for you, but if I run across it, I will drop a link maybe later.
---------- Post added at 05:57 AM ---------- Previous post was at 05:10 AM ----------
http://forum.xda-developers.com/showthread.php?t=2757462
Sent from my AT&T HTC One M8, running the ViperOne M8 ROM via Tapatalk.

Ugh....this is exactly why i want to stop posting on xda and withdraw from it completely. The main problem is that people flash things without knowing what it is....afterwards its "it didn't work" what now ? You can link a ruu and many people just execute it.
I'm not mad, i am misinterpreted.....i am making a point that's all.
Thanks and cheers. I will stop responding as it's the second time i believe you make me go off topic.

But flashing a nandroid backup that it's origins are unknown is like you said, unwise and could cause more problems than what it is worth. But not fatal, that I agree with. I also agree that sometimes posting here can lead to a whole lot of confusion, specially for beginners in flashing roms. Good thing about this is that this is one more area they can visit to get a link to return to stock before they return the phone for repair. So it wasn't all in vain. Sit, drink a beer (or coffee) relax and try to have a nice day.
Sent from my AT&T HTC One M8, running the ViperOne M8 ROM via Tapatalk.

Mr Hofs said:
Where are those ruu files ? There aren't any.....there is a very small selection of ruu files that can help a small group of people ! That's my point here. And who said he has a AT&T ..... Check my thread and check all the cid and main numbers then give me the links to the ruu files that are compatible with the nands i am hosting there.....get my point ?
Click to expand...
Click to collapse
If that was your point, its not what you wrote:
Mr Hofs said:
And there are no sense ruu files ... at least no carrier branded ones.
Click to expand...
Click to collapse
HTC posted the RUU for AT&T quite some time ago: http://www.htc.com/us/support/htc-one-m8-att/news/
Folks here keep saying "there are no RUUs", "HTC doesn't release RUUs anymore" and its simply not correct to make these statements as being generalized for all versions and all instances; although it seems to be true for a great many versions. If anything, this device is missing a good index of OTAs, RUUs, etc. by CID.
Not trying to pick a fight or anything, just want to prevent any misinformation.

redpoint73 said:
If that was your point, its not what you wrote:
HTC posted the RUU for AT&T quite some time ago: http://www.htc.com/us/support/htc-one-m8-att/news/
Folks here keep saying "there are no RUUs", "HTC doesn't release RUUs anymore" and its simply not correct to make these statements as being generalized for all versions and all instances; although it seems to be true for a great many versions. If anything, this device is missing a good index of OTAs, RUUs, etc. by CID.
Not trying to pick a fight or anything, just want to prevent any misinformation.
Click to expand...
Click to collapse
I haven't visited this thread in a while because my problem was resolved but i had a question. I want to accept an OTA. I'm fairly sure I know how to do this (I have a stock NAND, recovery, and i know i have to relock my bootloader) this will update my firmware to 2.22.xx.x After this is done i can re unlock my bootloader right? Also would i be able to restore one of my TWRP backups or will restoring replace my firmware with the old one that i had when the backup was made?

Restoring a full backup after an ota will replace your OS so that's not an option because you don't want to go back to your old (before ota) situation it will not replace the firmware. Only restore data ! And no need to relock the bootloader for an ota.....totally unnecessary !

redpoint73 said:
If that was your point, its not what you wrote:
HTC posted the RUU for AT&T quite some time ago: http://www.htc.com/us/support/htc-one-m8-att/news/
Folks here keep saying "there are no RUUs", "HTC doesn't release RUUs anymore" and its simply not correct to make these statements as being generalized for all versions and all instances; although it seems to be true for a great many versions. If anything, this device is missing a good index of OTAs, RUUs, etc. by CID.
Not trying to pick a fight or anything, just want to prevent any misinformation.
Click to expand...
Click to collapse
Mr Hofs said:
Restoring a full backup after an ota will replace your OS so that's not an option because you don't want to go back to your old (before ota) situation it will not replace the firmware. Only restore data ! And no need to relock the bootloader for an ota.....totally unnecessary !
Click to expand...
Click to collapse
Thanks for the reply! So bootloader can stay unlocked? In all the threads I checked you have to be relocked by doing "fastboot oem lock" but ok I'll take your word for it! Also you say that restoring isn't good so I'll have to stick with reflashing ROMs from scratch?

I think we are mixing things up. If you are already running the latest based roms why would you update ?
Why would you update to the 2.22 or higher base and then go back to a 1.54 based rom ?

Mr Hofs said:
I think we are mixing things up. If you are already running the latest based roms why would you update ?
Why would you update to the 2.22 or higher base and then go back to a 1.54 based rom ?
Click to expand...
Click to collapse
lol I'm just glad to see that your name is also Bernd :good:
Seems like you're a "troll" with 2 different IDs on here :angel: some of these guys didn't just misquote you, but completely misidentified you! :silly:

BerndM14 said:
lol I'm just glad to see that your name is also Bernd :good:
Seems like you're a "troll" with 2 different IDs on here :angel: some of these guys didn't just misquote you, but completely misidentified you! :silly:
Click to expand...
Click to collapse
Haha yeah i didnt even respond to that quote error. Not worth the hassle mate

I have a T-mobile HTC One M9. Can I update to nougat using the unlocked RUU?

Hi, I was wondering if it is possible for me to use the stock RUU to update to nougat on my htc one m9 rather than waiting for t-mobile to release a verified rom later in the year?

Yes u can. Just make sure that u are s-off and bootloader unlocked and then flash the dev edition ruu and u will get nougat.

Faisal0000 said:
Yes u can. Just make sure that u are s-off and bootloader unlocked and then flash the dev edition ruu and u will get nougat.
Click to expand...
Click to collapse
Not quite. To flash the developer RUU on a T-Mobile branded M9, you'll need to change your MID & CID to match the SKU of the developer edition RUU. If you don't know about these acronyms, stop what you are doing and read up. The FAQ section of the M9 readme thread, question 9, walks you through converting GSM phones (like the T-Mobile version) to the developer edition.

Faisal0000 said:
Yes u can. Just make sure that u are s-off and bootloader unlocked and then flash the dev edition ruu and u will get nougat.
Click to expand...
Click to collapse
Hi, And me I have htc one m9 sprint i can flash ruu nougat???

EKB8789 said:
Hi, And me I have htc one m9 sprint i can flash ruu nougat???
Click to expand...
Click to collapse
Not until Sprint releases the Android Nougat update.
The only update the is currently available is for the developer edition of the M9, a GSM model. Sprint is a CDMA carrier and incompatible with GSM.

Thanks for clarifying.
And you cannot flash on sprint or cdma phones. The ruu is only for gsm phones.

computerslayer said:
Not quite. To flash the developer RUU on a T-Mobile branded M9, you'll need to change your MID & CID to match the SKU of the developer edition RUU. If you don't know about these acronyms, stop what you are doing and read up. The FAQ section of the M9 readme thread, question 9, walks you through converting GSM phones (like the T-Mobile version) to the developer edition.
Click to expand...
Click to collapse
Thanks for linking me that. It also solved my question about why I was experiencing a bootloop, and gave me the method I had been searching for to crossflash

boredherobrine13 said:
Thanks for linking me that. It also solved my question about why I was experiencing a bootloop, and gave me the method I had been searching for to crossflash
Click to expand...
Click to collapse
Wonderful! Always nice when we find a solution. Kudos go to Flippy498, who created that thread and updates it as things come out, and to the many XDA members who have contributed to it.

computerslayer said:
Wonderful! Always nice when we find a solution. Kudos go to Flippy498, who created that thread and updates it as things come out, and to the many XDA members who have contributed to it.
Click to expand...
Click to collapse
Yup, now my next question is...how do i flash firmware v4...as I did CID/MID conversion to the Dev/Unlocked version, but now need the firmware, not just the RUU to flash

boredherobrine13 said:
Yup, now my next question is...how do i flash firmware v4...as I did CID/MID conversion to the Dev/Unlocked version, but now need the firmware, not just the RUU to flash
Click to expand...
Click to collapse
RUUs have the firmware along with everything else. While I'm pretty sure there's a way to flash individual components (radio, firmware, et cetera), that is beyond me. I stick to using the RUUs, and recommend them heartily. The easiest method is the SD card method - outlined in that same post. You'll end up wiping your internal phone storage (so back up what you care about), but it'll get you to the latest and greatest for the M9.

computerslayer said:
RUUs have the firmware along with everything else. While I'm pretty sure there's a way to flash individual components (radio, firmware, et cetera), that is beyond me. I stick to using the RUUs, and recommend them heartily. The easiest method is the SD card method - outlined in that same post. You'll end up wiping your internal phone storage (so back up what you care about), but it'll get you to the latest and greatest for the M9.
Click to expand...
Click to collapse
Really? I read that you couldn't use an RUU because verify key on firmware v1-3 is different from the one on v4, so you need v4 firmware to use a v4 RUU, which requires using a method. So I converted to dev/ATT/unlocked, flashed a v3 RUU I found online, and now I'm going to try to update to v4 which is apparently safer. If this fails, I'll try the RUU. After all, this is all vanilla to HTC so it should tell me if it won't work.

boredherobrine13 said:
Really? I read that you couldn't use an RUU because verify key on firmware v1-3 is different from the one on v4, so you need v4 firmware to use a v4 RUU, which requires using a method. So I converted to dev/ATT/unlocked, flashed a v3 RUU I found online, and now I'm going to try to update to v4 which is apparently safer. If this fails, I'll try the RUU. After all, this is all vanilla to HTC so it should tell me if it won't work.
Click to expand...
Click to collapse
I'm pretty sure the issues about keys has to do with trying to downgrade. But that's above my knowledge level.
I know for sure that you can apply the Nougat RUU after the Marshmallow RUU without issue because I have done this myself.

computerslayer said:
I'm pretty sure the issues about keys has to do with trying to downgrade. But that's above my knowledge level.
I know for sure that you can apply the Nougat RUU after the Marshmallow RUU without issue because I have done this myself.
Click to expand...
Click to collapse
Really? Well..I've already applied v3.0 and am going through all the updates. But Its certainly worth a try I suppose.

computerslayer said:
I'm pretty sure the issues about keys has to do with trying to downgrade. But that's above my knowledge level.
I know for sure that you can apply the Nougat RUU after the Marshmallow RUU without issue because I have done this myself.
Click to expand...
Click to collapse
Just tried. Got an err.

boredherobrine13 said:
Just tried. Got an err.
Click to expand...
Click to collapse
Are you trying to take OTA updates or using an RUU?
Also, what's the error message?

computerslayer said:
Are you trying to take OTA updates or using an RUU?
Also, what's the error message?
Click to expand...
Click to collapse
Tried to use an RUU. Got a signature error of some sort. Can't remember the number. RN it is taking OTA updates smoothly. Now, it will either get to v4 eventually through the OTA updates, or it will cut off at the top of v3 (in which case I have done something horribly wrong). I will try to flash RUU after I get v4 through OTA, just for fun and for the sake of the community
Edit 1: v4 finally showed up through OTA. 2GB Downloading currently. Will still RUU to double check compatibility. Will post back with success or not.
Edit 2: v4 was successful, device convered to HIMAULATT. Now flashing the Dev RUU, which works. It didn't work on v3. Therefor I was correct, and RUU v3 -> v4 isn't compatible.

boredherobrine13 said:
Tried to use an RUU. Got a signature error of some sort. Can't remember the number. RN it is taking OTA updates smoothly. Now, it will either get to v4 eventually through the OTA updates, or it will cut off at the top of v3 (in which case I have done something horribly wrong). I will try to flash RUU after I get v4 through OTA, just for fun and for the sake of the community
Edit 1: v4 finally showed up through OTA. 2GB Downloading currently. Will still RUU to double check compatibility. Will post back with success or not.
Edit 2: v4 was successful, device convered to HIMAULATT. Now flashing the Dev RUU, which works. It didn't work on v3. Therefor I was correct, and RUU v3 -> v4 isn't compatible.
Click to expand...
Click to collapse
Going from Marshmallow to Nougat is definitely possible (I've done it myself) - I'm not sure why your phone gave you such troubles. But in any case, I'm glad your phone is fully updated! Congratulations.

computerslayer said:
Going from Marshmallow to Nougat is definitely possible (I've done it myself) - I'm not sure why your phone gave you such troubles. But in any case, I'm glad your phone is fully updated! Congratulations.
Click to expand...
Click to collapse
As I wrote before, was not successful with mine. I was not able to flash Su 2.79. How did that work for you.
Pls can you make a discription how to
Mine is S-on, is it neccessary first to s-off

Can't flash anything and phone goes into random reboots

I'm currently at loss for what to do now, heres what happened which I think started all these problems
-Was running ICE 5.5.1 stable
-Phone randomly reboots into HTC's white startup screen
-went into TWRP and wiped everything including internal storage
-flashed a new rom hoping it'll stop the reboots, and halfway during the flash the phone reboots itself even before completing
-now stuck with no OS and cant get into recovery
kernel: lk
product: htc_himauhl
version: 1.0
version-main: 3.42.708.3
boot-mode: download
version-baseband: 01.01_U11440801_97.04.60111G_F
version-bootloader: 1.0.0.0000
mid: 0PJA10000
cid: HTC__044
download mode shows "FILE /mnt/media_rw/ext_sd/0PJAIMG.zip; FILE NOT FOUND"
Anybody got any suggestions? Hopefully someone here knows something about this

digged around and found that I might need to flash 0PJAIMG.ZIP. Any kind helpful souls out there able to post the image for 3.42.708.3? Tried finding everywhere but couldn't find the relevant file in this forum

You can flash any 3.xx.708.xx firmware. Only the first and third set of numbers really matter. The second set is incremental version, forth set is times to push to devices.
Bear in mind that your device is rooted and unlocked bootloader so flashing stock isn't an option.
Beamed in by telepathy.

shivadow said:
You can flash any 3.xx.708.xx firmware. Only the first and third set of numbers really matter. The second set is incremental version, forth set is times to push to devices.
Bear in mind that your device is rooted and unlocked bootloader so flashing stock isn't an option.
Beamed in by telepathy.
Click to expand...
Click to collapse
aw shucks, is there any other way to get out of this problem?

12021656627z said:
aw shucks, is there any other way to get out of this problem?
Click to expand...
Click to collapse
Flashing an RUU is definitely the way to go, and will work just fine as long as your SKU and OS version match with the RUU you're attempting to flash.
Being rooted and/or having an unlocked bootloader will not affect the success/failure of flashing an RUU. Follow the instructions on the readme page and you should be golden.

computerslayer said:
Flashing an RUU is definitely the way to go, and will work just fine as long as your SKU and OS version match with the RUU you're attempting to flash.
Being rooted and/or having an unlocked bootloader will not affect the success/failure of flashing an RUU. Follow the instructions on the readme page and you should be golden.
Click to expand...
Click to collapse
I've tried and the only RUU that matches the SKU 708 is 1.32.708.15, is it possible to flash that on my current firmware? I've read that it's not compatible... or is it?

computerslayer said:
Flashing an RUU is definitely the way to go, and will work just fine as long as your SKU and OS version match with the RUU you're attempting to flash.
Being rooted and/or having an unlocked bootloader will not affect the success/failure of flashing an RUU. Follow the instructions on the readme page and you should be golden.
Click to expand...
Click to collapse
ruu.exe only?. These htc rules are confusing. There needs to be a sticky with the requirements for each state of the phone.
12021656627z said:
I've tried and the only RUU that matches the SKU 708 is 1.32.708.15, is it possible to flash that on my current firmware? I've read that it's not compatible... or is it?
Click to expand...
Click to collapse
too old. You can't downgrade.
12021656627z said:
aw shucks, is there any other way to get out of this problem?
Click to expand...
Click to collapse
Probably not. Only HTC can fix it afaik. I reckon your attempts to flash will fail.
Beamed in by telepathy.

12021656627z said:
I've tried and the only RUU that matches the SKU 708 is 1.32.708.15, is it possible to flash that on my current firmware? I've read that it's not compatible... or is it?
Click to expand...
Click to collapse
You've read correctly. You need a 3.xx.708.xx RUU (EDITED: See Flippy498's correction below). It may be possible to get on from a paid repository of firmwares, but I don't have any recommendations there.
While HTC can almost assuredly help you (for a fee), it may be worthwhile to look into the paid service mentioned in the readme thread to see if that is more cost-effective.

shivadow said:
You can flash any 3.xx.708.xx firmware. Only the first and third set of numbers really matter. The second set is incremental version, forth set is times to push to devices.
Click to expand...
Click to collapse
computerslayer said:
You've read correctly. You need a 3.xx.708.xx RUU.
Click to expand...
Click to collapse
No, not only the first and the third number of the firmware version matter for S-ON phones. The X and the SKU in X.XX.SKU.YY need to match between the RUU and the phones current firmware. Only Y is allowed to differ if the phone is S-ON.
And a RUU actually flashes everything back to stock. So this
shivadow said:
Bear in mind that your device is rooted and unlocked bootloader so flashing stock isn't an option.
Click to expand...
Click to collapse
isn't true at all.
shivadow said:
ruu.exe only?. These htc rules are confusing. There needs to be a sticky with the requirements for each state of the phone.
Click to expand...
Click to collapse
There is a sticky with all needed information for RUUs: The ReadMe thread. (But as always, if you call something "ReadMe" you can rest assured that no one really reads it...) Flashing RUU.exe files can be a pain (just like using htc_fastboot)*. It's easier to use the SD card method. The ReadMe thread even explains how to get the *.zip out of the *.exe.
* I actually never had issues with them but I faced enough users here on XDA and on Handy-FAQ who just couldn't get them to work.
12021656627z said:
I've tried and the only RUU that matches the SKU 708 is 1.32.708.15, is it possible to flash that on my current firmware? I've read that it's not compatible... or is it?
Click to expand...
Click to collapse
As mentioned before by the others, that RUU is too old.
shivadow said:
Only HTC can fix it afaik. I reckon your attempts to flash will fail.
Click to expand...
Click to collapse
computerslayer said:
It may be possible to get on from a paid repository of firmwares, but I don't have any recommendations there.
Click to expand...
Click to collapse
How about Llabtoofer's RUU service as suggested in the ReadMe thread? Or Easy-Firmware if you prefer to own the RUU? (If you choose the latter make sure not to download a RUU with "combined_signed" in its naming. Those are custom made and only flashable with S-OFF. And don't forget to make it available for others, afterwards. )

Flippy498 said:
How about Llabtoofer's RUU service as suggested in the ReadMe thread? Or Easy-Firmware if you prefer to own the RUU? (If you choose the latter make sure not to download a RUU with "combined_signed" in its naming. Those are custom made and only flashable with S-OFF. And don't forget to make it available for others, afterwards. )
Click to expand...
Click to collapse
Thanks for the suggestions! Sad to know that Easy-Firmware is only available for S-OFF users, it could've been great if its flashable on S-ON. Looks like the only way out of is Llabtoofer's RUU service

12021656627z said:
Thanks for the suggestions! Sad to know that Easy-Firmware is only available for S-OFF users, it could've been great if its flashable on S-ON. Looks like the only way out of is Llabtoofer's RUU service
Click to expand...
Click to collapse
Easy-Firmware is usable for S-ON users. You just need to make sure that you don't download a "combined_signed" RUU. The ones with only "signed" should be just fine (e.g. "0PJAIMG_HIMA_UHL_M60_SENSE70_MR_hTC_Asia_HK_3.42.708.3_Radio_01.01_U11440801_97.04.60111G_F_release_471142_signed_2_4_2.zip" or "0PJAIMG_HIMA_UHL_M60_SENSE70_MR_hTC_Asia_HK_3.42.708.3_Radio_01.01_U11440801_97.04.60111G_F_release_471142_signed_2_4.zip").

computerslayer said:
You've read correctly. You need a 3.xx.708.xx RUU. It may be possible to get on from a paid repository of firmwares, but I don't have any recommendations there.
While HTC can almost assuredly help you (for a fee), it may be worthwhile to look into the paid service mentioned in the readme thread to see if that is more cost-effective.
Click to expand...
Click to collapse
shivadow said:
ruu.exe only?. These htc rules are confusing. There needs to be a sticky with the requirements for each state of the phone.
too old. You can't downgrade.
Probably not. Only HTC can fix it afaik. I reckon your attempts to flash will fail.
Beamed in by telepathy.
Click to expand...
Click to collapse
Any rough estimates on how much will the repair by HTC cost?

Flippy498 said:
Easy-Firmware is usable for S-ON users. You just need to make sure that you don't download a "combined_signed" RUU. The ones with only "signed" are just fine.
Click to expand...
Click to collapse
Oh! Sorry I must've misread your post then. I'll consider giving it a shot!

Flippy498 said:
No, not only the first and the third number of the firmware version matter for S-ON phones. The X and the SKU in X.XX.SKU.YY need to match between the RUU and the phones current firmware. Only Y is allowed to differ if the phone is S-ON.
Click to expand...
Click to collapse
I'm sorry for spreading bad information. Thanks for the correction.