Database Info

Replacing T-mobile ROM with Generic HTC ROM

Ive just installed a generic HTC rom over the top of the T-mobile rom pre-installed on the device.
I will check whether the things that everyone is reporting to be missing from the t-mobile rom are now working
UPDATE:
This rom does not seem to add any major features, it pretty much the same but without all the t-mobile branding
**NEW URL**
http://androidfiledepot.com/Storage...io_32.30.00.28U_4.05.00.11_release_121865.exe

so you have root acces?! or can you load an htc rom but no other roms?

where is this generic rom

OK, i take no responsibility if you brick your new phone if you do this
This update will remove all t-mobile branding from your handset. Should you have problems with your handset you will need to find a t-mobile rom to reinstall onto the device before returning to t-mobile for repair.
You will need a Goldcard and the following rom http://androidfiledepot.com/Storage...io_32.30.00.28U_4.05.00.11_release_121865.exe
Once you have created a goldcard insert it into your phone and start it up, then run the exe file listed above.
This will install the HTC rom onto your device and will remove all the t-mobile branding (apart from the sim lock)
Ive only spent about 10 mins testing the device since the update but everything seems fine.
If anyone is:
1. Concerned about the current lack of a t-mobile rom to undo changes this rom would make
2. is unsure of how to install the rom
3. Doesnt see the point of installing this rom
I would recomend that you simply DONT install this rom
PS...For those of you who want the 3d Gallery from the Nexus1 on your Desire you can simply install the 3dGallery.apk in the normal way

Just interested but is this rom newer than the one we are using at the moment, also, I created a Goldcard for my hero a few months back is it the same thing for this, or do you have access to a guide, also doesn't a goldcard technically allow us to install custom roms onto the desire.

What crap have T-mobile installed? =/

I can't see much T-Mobile on mine just when it boots up it says T-Mobile but apart from that the rest of the stuff is sense ui things.

nintendolinky said:
Just interested but is this rom newer than the one we are using at the moment, also, I created a Goldcard for my hero a few months back is it the same thing for this, or do you have access to a guide, also doesn't a goldcard technically allow us to install custom roms onto the desire.
Click to expand...
Click to collapse
The one linked to in my post does indeed appear to be newer, ive noticed a virgin media icon which was easily removed. It seems that although it is listed as a stock ROM its not a fully stock htc ROM after all.
All T-mobile branding is gone obviously.
I just used an old Goldcard that was created for either my Hero or Dream

Jabbypants said:
I can't see much T-Mobile on mine just when it boots up it says T-Mobile but apart from that the rest of the stuff is sense ui things.
Click to expand...
Click to collapse
Sorry My bad, I was meaning all the logos and changed icons and all the changes within senseUI.

Hardly anything T-Mobile on it... Not sure what the benefit of flashing is tbh...
I won't be flashing the ROM, not until there is a clear benefit to actually doing it..

I still don't think there is any T-mobile stuff on it, if it was branded with there crap it would come in a T-Mobile box, as far as i can see its the Desire that i have seen on the net.
The changes in sense is down to htc same with everything else, all these phones are is sim locked imo.

These are the 2 differences I've noticed so far:
T-Mobile Bootup Animation
Browser icon has WNW over it (web n walk)

brummiesteven said:
These are the 2 differences I've noticed so far:
T-Mobile Bootup Animation
Browser icon has WNW over it (web n walk)
Click to expand...
Click to collapse
Yerp - and a new ROM won't remove the T-Mobile boot up screen..
So i think anyone flashing a new ROM is slightly insane - just to remove a w'n'w icon... As it really is very very small.
Nowt else on there T-Mobile wise

thedalmeny said:
Yerp - and a new ROM won't remove the T-Mobile boot up screen..
So i think anyone flashing a new ROM is slightly insane - just to remove a w'n'w icon... As it really is very very small.
Nowt else on there T-Mobile wise
Click to expand...
Click to collapse
Errr. Yes it will remove everything t-mobile as its a full ROM.
Everything changes to HTC's logos

SGTDavePwnage said:
Errr. Yes it will remove everything t-mobile as its a full ROM.
Everything changes to HTC's logos
Click to expand...
Click to collapse
It shouldn't do mate...
I flashed god knows how many ROMs on my HTC Magic - never once did it remove the Vodafone boot logo...

Just seems a lot of hassle just to get htc logos on to me, all that risk for something minor.

SGTDavePwnage said:
Errr. Yes it will remove everything t-mobile as its a full ROM.
Everything changes to HTC's logos
Click to expand...
Click to collapse
Will it? I've flashed dozens of ROMs onto my G1, and I still have the original T-Mobile splash screen every time it boots.

setspeed said:
Will it? I've flashed dozens of ROMs onto my G1, and I still have the original T-Mobile splash screen every time it boots.
Click to expand...
Click to collapse
I think he may be right. Look at the way the desire boot...
[HTC]
[T-Mobile Logo]
Looks like "HTC" is the unremovable splash screen and T-Mobile is the bootload image (like the ANDROID on cyanogen G1).

setspeed said:
Will it? I've flashed dozens of ROMs onto my G1, and I still have the original T-Mobile splash screen every time it boots.
Click to expand...
Click to collapse
Yes, if you flash a FULL rom it flashes everything. The radio, boot logos the lot.
Im not going to be flashing it every day, just the once to get rid of all the logos.
If you dont want to flash it then DONT. At least if people know that they have the option they can decide for themselves.
As for the people moaning about the risk, that's your choice...but I bet your going to flash a similar update in the near future
PS..I find it interesting that ppl are happy to moan at someone who was willing to try installing a new rom that could have included new things, yet most likely wouldn't have attempted the experement themselves

Apart from mentioned did the update change any other icons, or just the web browser and boot logo.

[Q] stuck please help!

I have searched and searched and have not been able to find exactly what I am looking for.
I have an HTC One S on the Rogers network in Canada. It was originally a Fido phone but worked fine on Rogers without unlocking or rooting...?
I rooted it and installed CWM and it was working great.
I decided to try to flash the jellybean rom and thats when things went screwy.
I pushed some things in recovery and as embarrassing as it is I cant tell you exactly what I pushed but I can no longer get to the CWM recovery. I am stuck in the white bootloader screen.
It now says tampered relocked security warning.
Heres the thing. I have tried everything I have found online and nothing.
I think I should be trying to flash the stock ROM but I cant find one that is for a One S on the rogers network.
I have downloaded everything from the drivers, SDK, ROM's, hasoons all in one...adb, and so on and so on.
If anyone can help get this thing working I will paypal you some cash!
Thanks in advance!
Tom

are you sure you have the s4 version and not the s3? that could be your issue. what does the model number on the box say?

how do i know what model it is?
on the box it says Z520m, Android with HTC Sense

that's the s4. you could try to flash the tmous stock ruu, but idk if your going to find the exact rom you're looking for. i used this rom http://forum.xda-developers.com/showthread.php?t=1648526&highlight=stock+duo when i first started flashing because it is completely stock, just optimized for better battery life and faster processes

[Q] hboot 2.14.0000

So I updated my rogers HTC One X with the OTA jellybean update. Then I decided I wanted to root. I did, TWRP (the older revision than the current one) didn't work because the touchscreen wouldn't work. Updated TWRP to the highest version (the one with the on screen keyboard?) and it worked. Flashed Jellybam, stuck on boot screen, flashing white and animation. Then I flashed the boot.img with adb, then flashed jellybam again. Worked, but no touch screen.
Is my solution just to wait for roms that support new hboot?

So what was the benefit to doing the ota again? You seem like you knew the risks I'm just wondering what the reward was?
Sent from my HTC One XL

Are you sure you are on the latest version (2.3.3.1)? Its supposed to fix the the touch screen issue.
http://forum.xda-developers.com/showthread.php?t=1677447

My reward was the chance to have a digital interaction with someone who offers no answer to a simple question, and instead thinks snark is worth their posting time. Obviously.

Twrp works fine as I said. It's the roms, once flashed, that don't respond to touchscreen swipes.

veemodz823 said:
Twrp works fine as I said. It's the roms, once flashed, that don't respond to touchscreen swipes.
Click to expand...
Click to collapse
The hboot screwed up both touchscreen response within TWRP and within the OS. I would have assumed that the new version of TWRP fixed both. I'm not personally on hboot 2.14, so hopefully some folks that are can chime in with some insight.

redpoint73 said:
The hboot screwed up both touchscreen response within TWRP and within the OS. I would have assumed that the new version of TWRP fixed both. I'm not personally on hboot 2.14, so hopefully some folks that are can chime in with some insight.
Click to expand...
Click to collapse
I didn't think that a recovery would actually fix something within an os when the two are two completely different things in my mind. I think that TWRP working on 2.14 means that something in TWRP has been changed from previous versions to accomodate 2.14. I guess the same just has to be done for the roms, but that's just my uneducated guessing and logic.

I too am having the same issues. Installed 5 different rom's, all of them had no touch screen capabilities. Still working on it, if I come across anything I will let you know. Were you able to backup your old rom with TWRP? If you did I would love if you could send me your recovery file since CWM happened to delete mine. I have Rogers evita if that's the same as yours.

Hey, no I didn't back up.
did you try this rom?
http://forum.xda-developers.com/showthread.php?t=2076361

veemodz823 said:
I didn't think that a recovery would actually fix something within an os when the two are two completely different things in my mind.
Click to expand...
Click to collapse
Yes, they are separate. But it's recovery that is installing the OS. So it seems logical to me it can cause a problem with the OS.
Sent from my HTC One X using xda app-developers app

veemodz823 said:
My reward was the chance to have a digital interaction with someone who offers no answer to a simple question, and instead thinks snark is worth their posting time. Obviously.
Click to expand...
Click to collapse
Sorry I didn't know you didn't have a backup. Now I feel terrible for joking with you before.
Sent from my HTC One XL

veemodz823 said:
Hey, no I didn't back up.
did you try this rom?
http://forum.xda-developers.com/showthread.php?t=2076361
Click to expand...
Click to collapse
I haven't tried that rom, it's an Australia one....don't know if that would work for us rogers guys. Might perm brick it

http://forum.xda-developers.com/showthread.php?t=2083314
It seems to have worked for this dude and I *believe* the Telstra is the same phone as ours and not an international version. But make sure. I would've flashed it but I'm at my volunteer.

Telstra is the same phone as Rogers (dual core S4 version of the One X/XL).
If it works, you'll need to manually enter the Rogers APN.
Sent from my HTC_Flyer_P512_NA using xda app-developers app

Does anybody think its possible that the new OTA firmware (flashing the entire OTA and not just the ROM) has some sort of difference compared to older ones.. surely a broken touch screen after the OTA can't be a coincidence. 2nd case.
Or its possible that the ROMs/recovery aren't compatible with some sort of change in firmware.. I wonder..

absolutelygrim said:
Does anybody think its possible that the new OTA firmware (flashing the entire OTA and not just the ROM) has some sort of difference compared to older ones.. surely a broken touch screen after the OTA can't be a coincidence. 2nd case.
Or its possible that the ROMs/recovery aren't compatible with some sort of change in firmware.. I wonder..
Click to expand...
Click to collapse
The weird thing is this: with older TWRP you can't get the touch screen to respond, but with newer TWRP it will respond to touch.
In the thread I posted above someone says this:
"Well known and posted about all over this forum.
HTC changed some firmware relating to the touchscreen in the 3.17 update. Roms require a kernel update to work. Twrp can cheat and just use htc's new kernel, cm10 build their kernel from source so could be hard to figure what changed until HTC release source."

veemodz823 said:
The weird thing is this: with older TWRP you can't get the touch screen to respond, but with newer TWRP it will respond to touch.
In the thread I posted above someone says this:
"Well known and posted about all over this forum.
HTC changed some firmware relating to the touchscreen in the 3.17 update. Roms require a kernel update to work. Twrp can cheat and just use htc's new kernel, cm10 build their kernel from source so could be hard to figure what changed until HTC release source."
Click to expand...
Click to collapse
typical HTC.. If you are still having issues, I may be able to help you RUU downgrade

Some already quoted me but to be clear.
Htc ship firmware updates with their official updates that customs rarely ever ship. Firmware relating to the touchscreen were updated and kernel changes are required to use it.
Twrp uses official sense kernel so just updated to latest. All kernels based on the kernel that shipped with 3.17 willbe fine.
Eg custom 3.17 jb roms and kernels will be fine.
But all things not based on 3.17 do not have the required kernel updates for the touchscreen.
It is unknown what changed so likely this won't get resolved until Htc release source for 3.17 kernel.
Downgrading from 3.17 has been reported to perma brick phones. Do so at your own risk, you have been warned..
---------- Post added at 05:07 AM ---------- Previous post was at 04:27 AM ----------
Also twrp does not install os/roms. Roms install themself. Roms include an update binary that has all the file operation apps like del, copy, move, read operation etc. And they include an update script that makes use of all the apps it ships with.
Twrp is a skeleton, it just starts the Rom and lets the rom do its own thing.
Twrp does not alter how a Rom installs, eg it can neither break nor fix things like this touchscreen problem.

All right, so to he clear, its just a matter of waiting for 3.17 compatible roms. Would that be far off considering Twrp is already updated to support 3.17 kernal roms? Or does HTC need to release source for custom 3.17 roms to be made? And what about that Telstra Rom that was mentioned? Why would that work, how was that made?

Twrp 2.3.3.1 works because it uses Htc sense 3.17 kernel (based on linux kernel 3.4.10). Twrp does not "support 3.17 kernel roms", twrp does not care what kernel a Rom has. Twrp simply has updated so it can function. If a Rom can function or not has nothing to do with twrp.
Telstra 3.17 Rom works because it is based on 3.17 Telstra Rom and uses the 3.17 kernel.
There is several 3.17 based roms. Based on the singtel 3.17.707.1 and Telstra 3.17.841.1 and I'm sure now there is loads of evita regions with 3.17 available more variations will show up.
Cm is not a sense rom. Same goes for aokp and such. Anything in "original development" is not based on sense. All those can not use sense kernels as they would need to add all the extra Htc stuff for it to work and you just end up with sense and not cm etc.
I can say again; only roms that can use the 3.17 kernel work and basically that just means only sense 3.17 roms. Anything else will not work. That is unlikely to change until 3.17 kernel source is released. There is several 3.17 based roms.
Kernel source could take up to 3 months. It has been 1 already. So could be another 2 months before this can be fixed in non sense roms.

Custom ROMs Boot to White Screen With HTC Logo

Hello all! This is my first post on XDA, so hopefully I don't screw anything up
Anywho, I have a rooted Verizon HTC One (M8) that I was running CyanogenMod on up until recently when I wanted to switch back to a ROM based on HTC Sense. I ended up finding the Android Revolution HD mod for the M8 and decided to give it a try. I flashed my firmware to 3.28.401.7 as that was the one listed on the post, and installed it using TWRP. The device booted, I left it alone, but for some reason it would show a lock screen (that would only let me swipe up) and after I would unlock it all that would be shown was the HTC logo over a white background, with the home and back buttons lit up. Thinking that maybe I goofed, I kept trying again. Eventually I gave up on Android Revolution and decided to try the ViperOne mod, and it ended up doing the same exact thing. Does anyone have any ideas? Thanks for your time, and any help is greatly appreciated!
Regards,
Nate

NathanialTheGreat said:
Hello all! This is my first post on XDA, so hopefully I don't screw anything up
Anywho, I have a rooted Verizon HTC One (M8) that I was running CyanogenMod on up until recently when I wanted to switch back to a ROM based on HTC Sense. I ended up finding the Android Revolution HD mod for the M8 and decided to give it a try. I flashed my firmware to 3.28.401.7 as that was the one listed on the post, and installed it using TWRP. The device booted, I left it alone, but for some reason it would show a lock screen (that would only let me swipe up) and after I would unlock it all that would be shown was the HTC logo over a white background, with the home and back buttons lit up. Thinking that maybe I goofed, I kept trying again. Eventually I gave up on Android Revolution and decided to try the ViperOne mod, and it ended up doing the same exact thing. Does anyone have any ideas? Thanks for your time, and any help is greatly appreciated!
Regards,
Nate
Click to expand...
Click to collapse
X.X.401.X firmware is for Europe. UK variants. You should not be flashing firmware to your vzw one like that. Flash back to stock vzw firmware.

dottat said:
X.X.401.X firmware is for Europe. UK variants. You should not be flashing firmware to your vzw one like that. Flash back to stock vzw firmware.
Click to expand...
Click to collapse
Ahhh okay, thanks! So, how limited do the options for flashing ROMs become for the One? Also, once I revert back to stock firmware, will I be able to retry one of the ROMs that I tried previously, or will the stock vzw firmware not be compliant? I apologize for any super nooby questions, this is my first system dealing with root stuff (as I had an iPhone previously so I used jailbreak items)

NathanialTheGreat said:
Ahhh okay, thanks! So, how limited do the options for flashing ROMs become for the One? Also, once I revert back to stock firmware, will I be able to retry one of the ROMs that I tried previously, or will the stock vzw firmware not be compliant? I apologize for any super nooby questions, this is my first system dealing with root stuff (as I had an iPhone previously so I used jailbreak items)
Click to expand...
Click to collapse
Just stick to the roms from the M8 VZW Development forum and you'll be fine. Viper is there, NuSense, CleanROM and many more...

Windows Phone 10 on HTC One M8

I did something really dumb even though I was advised not to. I managed to get the Windows Phone 10 Technical Preview on my HTC One M8 for Windows. The OS version that got pushed to it simply is not compatible with this hardware and so many things don't work. I want to go back but the Microsoft-provided recovery tool doesn't detect the phone because it was never intended to work with this model. In short, my question is does anyone have a way to just flash an HTC One M8 for Windows back to the factory T-Mobile ROM that it came with out of the box? If so, where do I get it and how can I flash to it? HTC has no recovery tool to speak of for this phone, Microsoft was just as much help, and TMo wants me to pay an insurance deductible before they will replace the thing. I will be ever so grateful if someone can help out.
Thanks!

reptarsaurusflex said:
I did something really dumb even though I was advised not to. I managed to get the Windows Phone 10 Technical Preview on my HTC One M8 for Windows. The OS version that got pushed to it simply is not compatible with this hardware and so many things don't work. I want to go back but the Microsoft-provided recovery tool doesn't detect the phone because it was never intended to work with this model. In short, my question is does anyone have a way to just flash an HTC One M8 for Windows back to the factory T-Mobile ROM that it came with out of the box? If so, where do I get it and how can I flash to it? HTC has no recovery tool to speak of for this phone, Microsoft was just as much help, and TMo wants me to pay an insurance deductible before they will replace the thing. I will be ever so grateful if someone can help out.
Thanks!
Click to expand...
Click to collapse
Generally I think you are out of luck until they launch the Windows 10TP for HTC M8's. When that happens, you should be able to use the Windows Phone Recovery Tool to re-flash your phone. It looks like it's basically a re-skinned version of the Lumia Software Recovery tool, and it only makes sense for them to release this as well if they are going to be providing a way to recover and flash non-Lumia branded phones in the future.
There is a way to re-flash the HTC One M8 for Windows if you have the ROM, but so far only the Verizon version has leaked. I hope this is not your only phone, because if you wait a month or so you should be able to re-flash using the Microsoft tool
You have absolutely no right to be mad at Microsoft, HTC and/or T-Mobile for the problems. They are completely justified making you pay the deductible to get this fixed, why should they eat the cost of fixing it?

Don't get me wrong, I don't blame anyone but myself for this. I'm simply surprised that there isn't a recovery option out there in general. Someone could have a problem that isn't their fault at all that could benefit from having this. That being said, I have an open ticket with the HTC dev team. All I really want is access to a ROM that must clearly already exist. The software got on the phone in the first place, right? Of course I am not a dev and probably have no idea what I'm talking about. I apologize if I'm coming off as an ass looking for a hand out. It just seems to me that this is a simple issue with a simple fix. I know from when I had a Lumia device that I could open up the navifirm+ software and download any ROM for any windows phone from any region of the world.

reptarsaurusflex said:
Don't get me wrong, I don't blame anyone but myself for this. I'm simply surprised that there isn't a recovery option out there in general. Someone could have a problem that isn't their fault at all that could benefit from having this. That being said, I have an open ticket with the HTC dev team. All I really want is access to a ROM that must clearly already exist. The software got on the phone in the first place, right? Of course I am not a dev and probably have no idea what I'm talking about. I apologize if I'm coming off as an ass looking for a hand out. It just seems to me that this is a simple issue with a simple fix. I know from when I had a Lumia device that I could open up the navifirm+ software and download any ROM for any windows phone from any region of the world.
Click to expand...
Click to collapse
Fair enough. Its a bit weird that only Nokia put out any kind of program to re-flash phones, but I have a feeling that the app Microsoft has put out will, going forward, be used to reflash any Windows Phone that is having problems. They kind of need to provide that functionality if they are going to take control of the update process from the carriers (which i know they want to do, whether they actually pull it off remains to be seen).
I'd say just hang in there, you will likely be able to re-flash in a month or so. I hope you can somehow get access to the rom, but there isn't program released to flash it on the phone (though there are ways, look at the Verizon RUU thread. There is also a Youtube video out there showing how to do it)

i was the first with htc w8 (tmous) to hack the w10 beta on it if you check my twitter.
the only reason why i even considered to do this is because i have a way out.
that can't be said for public. so why the hell you didn't check if you have
a way to go back to stock before even considering such a highly
experimental thing to your precious device?
sure you can't expect any support from ms or tmous for that scenario.
i flashed back to w81 the next day already because of htc related bugs.
i will restore it for you if you send it to me and pay 2-way shipping.
this is a one time personal offer from me that i will do for you.
contact me via pm if you didn't send it in yet.
let this be a lesson to you guys...

reptarsaurusflex said:
I did something really dumb even though I was advised not to. I managed to get the Windows Phone 10 Technical Preview on my HTC One M8 for Windows. The OS version that got pushed to it simply is not compatible with this hardware and so many things don't work. I want to go back but the Microsoft-provided recovery tool doesn't detect the phone because it was never intended to work with this model. In short, my question is does anyone have a way to just flash an HTC One M8 for Windows back to the factory T-Mobile ROM that it came with out of the box? If so, where do I get it and how can I flash to it? HTC has no recovery tool to speak of for this phone, Microsoft was just as much help, and TMo wants me to pay an insurance deductible before they will replace the thing. I will be ever so grateful if someone can help out.
Thanks!
Click to expand...
Click to collapse
You might be out of luck for now at the moment. I'm sure the TMo ROMS aren't available, otherwise you would be able to. Remember that the trick to update to Windows 10 Preview was AT YOUR OWN RISK due the fact that the phone isn't OFFICIALLY SUPPORTED

HD2Owner said:
i was the first with htc w8 (tmous) to hack the w10 beta on it if you check my .
the only reason why i even considered to do this is because i have a way out.
that can't be said for public. so why the hell you didn't check if you have
a way to go back to stock before even considering such a highly
experimental thing to your precious device?
sure you can't expect any support from ms or tmous for that scenario.
i flashed back to w81 the next day already because of htc related bugs.
i will restore it for you if you send it to me and pay 2-way shipping.
this is a one time personal offer from me that i will do for you.
contact me via pm if you didn't send it in yet.
let this be a lesson to you guys...
Click to expand...
Click to collapse
I'd like to know how you did this instead of sending you my phone.

flashed the stock rom.

HD2Owner said:
flashed the stock rom.
Click to expand...
Click to collapse
Is it possible to flash the stock rom on a verizon phone?

sure. by stock rom i mean the original rom meant for the device/carrier.
on verizon w8 -> verizon rom
on at&t w8 -> at&t rom
on tmous w8 -> tmous rom
don't try to flash different carrier rom. it won't work.
all 3 carrier variants have different modelID which is checked before allowing flash.

HTC One M8 for Windows
HD2Owner said:
sure. by stock rom i mean the original rom meant for the device/carrier.
on verizon w8 -> verizon rom
on at&t w8 -> at&t rom
on tmous w8 -> tmous rom
don't try to flash different carrier rom. it won't work.
all 3 carrier variants have different modelID which is checked before allowing flash.
Click to expand...
Click to collapse
I have been looking everywhere for the Verizon rom and software so I can reflash my phone. Do you happened to know where I can get these?

dans95tbird said:
I have been looking everywhere for the Verizon rom and software so I can reflash my phone. Do you happened to know where I can get these?
Click to expand...
Click to collapse
there: http://forum.xda-developers.com/showpost.php?p=55201370&postcount=2
download the htc RUU that i attached to this post and extract with winrar.
place the htc w8 verizon nbh in the extracted RUU folder with filename "RUU_Signed.nbh".
then go into bootloader (power off, then hold vol-&vol+ while pressing power until it vibrates).
it will show white bootloader screen with hardware info.
when the pc installed the drivers for bootloader mode it switches from "serial" to "usb" on the bottom.
then doubleclick the ROMUpdateUtility.exe and it will flash the phone.
everything will be wiped of course.

HD2Owner said:
there: http://forum.xda-developers.com/showpost.php?p=55201370&postcount=2
download the htc RUU that i attached to this post and extract with winrar.
place the htc w8 verizon nbh in the extracted RUU folder with filename "RUU_Signed.nbh".
then go into bootloader (power off, then hold vol-&vol+ while pressing power until it vibrates).
it will show white bootloader screen with hardware info.
when the pc installed the drivers for bootloader mode it switches from "serial" to "usb" on the bottom.
then doubleclick the ROMUpdateUtility.exe and it will flash the phone.
everything will be wiped of course.
Click to expand...
Click to collapse
since ppl dnt seem to give u a thanks ill spam the thread any say thank and the "thanks" button....ppl appreciate his help!!!

The latest build of Win10 works way better on a One M8 btw. I have installed it using the registry method and running it without many problems. So if you have a t-mobile/at&t version of this phone (where there is no RUU availible) with windows 10 installed i advice upgrading to the latest build.

really? i noticed bugs with background picture not showing and many htc apps/settings not working..
they work now on latest build?

in the new version of windows phone recovery tool, ms added support for htc devices.
http://go.microsoft.com/fwlink/?LinkID=525569

Any luck with Verizon HTC One?
HD2Owner said:
in the new version of windows phone recovery tool, ms added support for htc devices.
Click to expand...
Click to collapse
I downloaded the newest version, 2.0.3, of the recovery tool. Even though it says it supports HTC devices it still fails to rollback my Verizon HTC M8. I receive the error: "Software Package is not found on server"
This is after the tool recognizes my device and asks me to restart in boot-loader mode.
Anyone else have success with using ver. 2.0.3 with a HTC M8?

Shockakohn said:
I downloaded the newest version, 2.0.3, of the recovery tool. Even though it says it supports HTC devices it still fails to rollback my Verizon HTC M8. I receive the error: "Software Package is not found on server"
This is after the tool recognizes my device and asks me to restart in boot-loader mode.
Anyone else have success with using ver. 2.0.3 with a HTC M8?
Click to expand...
Click to collapse
Recognized my T-Mobile M8 and flashed WP8.1 successfully.

Not able to update to latest Windows 10 mobile TP build
My HTC One is currently on 10.0.12562.84 (Build 10080). For some reason I am not able to see the latest build 10.0.12648.133 (Build 10149). Any one able to update to the latest build. Any idea why I'm not seeing it still?
Tried using the phone recovery tool to flash back to 8.1 but it says no builds available.

germanh said:
Tried using the phone recovery tool to flash back to 8.1 but it says no builds available.
Click to expand...
Click to collapse
which variant? verizon, at&t or tmous?