Develop Bugs

How to unroot HOX and put original software on it?

How to unroot HOX and put the original update on it?
I am now using CM10.

Desaf said:
How to unroot HOX and put the original update on it?
I am now using CM10.
Click to expand...
Click to collapse
You'd need to find the original RUU for whatever CID your phone is and flash that onto the handset and then relock it.
There's a thread around here somewhere, try the search bar

The-Last-Hylian said:
You'd need to find the original RUU for whatever CID your phone is and flash that onto the handset and then relock it.
There's a thread around here somewhere, try the search bar
Click to expand...
Click to collapse
I'm actually curious on this too, mainly for the sake of getting the OTA update and making sure it updates everything that fastboot flashing cannot, such as the HBOOT.
So it's not possible to simply install a stock ROM and just reflash the original recovery to have the OTA install?

You mean this thread http://forum.xda-developers.com/showthread.php?t=1660807 ?
Could someone tell me a easy way to unroot and flash ruu on it?

On the tread i post above, I can´t download the ruu. It says its more than 500 mb and I need a premium account.
So is there a other way to unlock and unroot en put the original software on the one x?

Try this http://www.youtube.com/watch?v=SZuAjz4PIjU
It did work for me, i guess i downloaded the ruu a couple of monthes ago.

Desaf said:
On the tread i post above, I can´t download the ruu. It says its more than 500 mb and I need a premium account.
So is there a other way to unlock and unroot en put the original software on the one x?
Click to expand...
Click to collapse
here you go
http://dl3.htc.com/application/htc_one_x_RUU_2.20.502.7_att_us_08022012.exe
direct from the source. 2.2 RUU for ATT USA
just download, connect your phone to your computer with a USB cord, set it to "debugging mode" and "charge only" and run the .exe file
now the whole CID re-locking bootloader stuff i have no clue on bc i didn't ever unlock the loader.

Also Runnung CM10 Endeavoru 4.2.1
Hi! i am also having problems with my HOX im running the Cyanogenmod10 Endeavoru with Android 4.2.1 on my one X and it has caused me nothing but trouble. i tried to do the RUU thing and flash everything back to stock but i keep getting the ERROR 171 USB Connection Error. and i tried to do some research here more on the forums and i got confused if i can flash back to stock rom with 4.2.1 or not? because i saw some threads saying that it was very impossible and i don't want to go to the Service Centers to void my warranty and such. Can someone please help me on this please? i really want to get everything working back on my HOX and get the OTA Jellybean.

Problems with Wifi [Not scanning]

Hi guys,
This is my first thread here in XDA, so, forgive me by a possible mistake.
I recently bought a HOX, the seller said that is the international version.
I'm in 4.0.3, with software version 1.29.707.11 (already checked for updates, but phone says its up to date)
So, sometimes when i turn my wifi on, he doesn't connect in my network (already saved), i go to wifi settings, put to scan, and, aparently, the phone don't scan the networks and doesn't found my network too.
Obviously, im on the range of the network, and don't have that factory problem with bad wifi signal.
And, sometimes too, phone takes a lot of time to get carrier signal, so i turn on plane mode, then turn off, and finally get carrier signal.
My question is: is this normal? What can i try to fix it? (Thinked on a factory reset)
I don't tried anything yet.
If anyone could help, i'll appreciate and if the thread is on the wrong place, please move it

Just try flashing the RUU, which will delete everything and return it to stock.

BenPope said:
Just try flashing the RUU, which will delete everything and return it to stock.
Click to expand...
Click to collapse
Thanks for the help Pope!
I am VERY noob in HTC tools, can you say me what exactly is this "RUU", and where i can get it?
Its basically, a factory reset right? What is the difference from normal FR to this RUU tool?

lock! said:
Thanks for the help Pope!
I am VERY noob in HTC tools, can you say me what exactly is this "RUU", and where i can get it?
Its basically, a factory reset right? What is the difference from normal FR to this RUU tool?
Click to expand...
Click to collapse
The difference is that it will reflash the ROM from scratch, it's the first thing HTC do when you take your phone for repair. It's very safe (when flashed with decent remaining battery) and very thorough.
Check the Shipped ROM sticky in the development section.

I am searching about the Rom Update Utility, but i'm not finding a good tutorial to follow, explaining the whole process.
If anyone could help me in the process :laugh:
Edit:
Thanks again Pope! I'll look in dev section

You just have to charge the phone, put the phone in fastboot mode (hold down the volume down key when switching on the phone, then navigate from there), plug phone into Windows PC and double click RUU.
You may want to do an "adb backup" (you'll have search for this) beforehand, flash RUU, test and then restore.

BenPope said:
You just have to charge the phone, put the phone in fastboot mode (hold down the volume down key when switching on the phone, then navigate from there), plug phone into Windows PC and double click RUU.
You may want to do an "adb backup" (you'll have search for this) beforehand, flash RUU, test and then restore.
Click to expand...
Click to collapse
I'm not finding the correct RUU file for the One X, can you help me? Or just show me a place to search... (Some links here at job are blocked --') Basically finding the correct RUU file i'll do the rest without problem...
This "restore" you mean in the end, its the factory reset in the phone? Or another restore?
Don't need a backup, i got the phone 2 days ago hehehe

My HOX is totally clean.
No unlocked bootloader, no root.
This will not be a problem doing the flash with the stock RUU right?

lock! said:
My HOX is totally clean.
No unlocked bootloader, no root.
This will not be a problem doing the flash with the stock RUU right?
Click to expand...
Click to collapse
No, that's perfect, you don't need anything other than stock, and it will remain stock.
http://www.filefactory.com/file/5c0...Radio_1.1204.105.14_release_260743_signed.exe

BenPope said:
No, that's perfect, you don't need anything other than stock, and it will remain stock.
http://www.filefactory.com/file/5c0...Radio_1.1204.105.14_release_260743_signed.exe
Click to expand...
Click to collapse
Ben sorry for tons of questions hehe
I'm reading a tutorial, and on it said that i need my CID number, in order to download the correct RUU file for the correct region of my HOX. How can i know if this RUU you posted is the correct for my HOX?
I've tried to get my CID number (downloaded the fastboot flasher tool) but when i put the cid command he returns: CID > None lol
I Know that my HOX is from Shangai (has a SH in serial number) and got my MID number.
So, i just need to know which file i need to download, the right one of course hehehe
If i will need the CID to know, i'll ask for the files for fastboot commands (i don't found them)
If not, just confirm the link you posted ealier if its the correct RUU for my case.
PS.: This link posted is only for premium users, and i don't have a premium acc, can you provide in another mirror?

You can't flash the wrong RUU, the phone won't let you.
You don't need your CID as you are not unlocked, knowing that you are 1.29.707.x is enough. It's the right RUU.
I'm sure you don't need me to hold your hand whilst you use google to find that file somewhere else. The sticky dev thread I previously mentioned will likely have a ton of mirrors for the file.

So.. i'll look fot the file in other places.
Today, i've connected in my wifi network, and the phone says there's an update...
It's the same update announced days ago, but in my case with a different update number...
Phone has been upgraded to ICS 4.0.4 and Sense 4.1.
If the problems persist, i will flash the RUU anyway, but, because of this update, nothing changes right? The RUU file you posted still valid for my HOX?

Not any more, you've updated your hboot, so you'll need an updated RUU (you can't install on older hboot, packaged with an older RUU).
You're lucky:
http://www.filefactory.com/file/3rc...Radio_2.1204.135.20_release_278245_signed.exe
and
http://forum.xda-developers.com/showpost.php?p=30273253&postcount=1724

BenPope said:
Not any more, you've updated your hboot, so you'll need an updated RUU (you can't install on older hboot, packaged with an older RUU).
You're lucky:
http://www.filefactory.com/file/3rc...Radio_2.1204.135.20_release_278245_signed.exe
and
http://forum.xda-developers.com/showpost.php?p=30273253&postcount=1724
Click to expand...
Click to collapse
HELL YEAH!
I'll test for 2 ~ 3 days, if i note the same problem i'll flash it!
Thanks for all the help Pope!

With this 707 update I got better WiFi ..smooth, fast...amazing
Sent from my HTC One X using XDA Premium HD app

dragonesdenano said:
With this 707 update I got better WiFi ..smooth, fast...amazing
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
Same here man...
In a network that once stood in 40% signal, now i'm getting almost 100%!
Apparently, carrier signal is working fine too.. i'll test for more 3 days...

[Q] Why is my HTC One x (PROTOTYPE) stuck on ICS?

Why is my HTC One x (PROTOTYPE) stuck on ICS?
Hey guys, This is my first post ever on XDA so please forgive me if I sound like an idiot
I got hold of a HTC One x which was already had an unlocked bootloader, rooted and had CWM recovery installed. I was told that I have a prototype version of the one x. Anyway that is not issue. when I got the phone it was running android version 4.0.4 HTC Sense version 4.1 and I checked software update. The 3.14.401.27 OTA update was available so I proceeded with the update and after the reboot I found my phone stuck in a bootloop and the only way for me to sort it out was by restoring my nand back up from CWM. I really wanted the new Sense 5 UI and android jelly bean so I downloaded:
RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_TW_3.14.709.20_Rad io_5.1204.162.29_release_292865_signed.exe
My CID was HTC__621 thats why I downloaded that ruu but after flashing it not was I only stuck in a bootloop but also when I entered recovery mode it was just a blank black screen with the back lights on. I even flashed different versions of CWM recovery and TWRP which gave me the same black screen so I flashed the stock recovery.img which also gave me the same black screen. I thought me maybe a different Ruu would resolve this issue so I used 'JBFWTOOL21' to change my CID to '11111111' this allowed me to flash:
RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radi o_5.1204.162.29_release_298897_signed.exe
&
RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Ra dio_5.1204.162.29_release_302015_signed.exe
After trying both these ruu's I still found my device stuck in a bootloop. Next I downloaded 'Endeavoru_CustomRUU' this contained a 'rom.zip' which I belive was a jelly bean rom and said it would update my image version to '3.14.401.31' after flashing this ruu, my phone booted up past the 'HTC Quietly Brilliant' screen but into a black screen but I could hear the boot sound and knew it booted up but it still gave me a black screen. barre in mind this was the only rom that booted up and didn't get stuck in a bootloop but the downside was I had no picture on the screen it was literally pitch black with the backlight on when it went past the 'HTC Quietly Brilliant' boot screen. I didn't even see the one x boot animation. I could only hear the boot up sound and once it was booted up the notification LED would flash I was receiving network settings from my operator. That was about it. I booted into recovery to see wether that worked but unfortunatelly it was also still giving me a black screen. The only thing I could boot into without a problem was 'power button + volume down' which booted into bootloader in which I chose 'fastboot' to flash all these roms.
At this point I thought my device was soft bricked so I gave it to my friends father who happened to really good with his IT skills. He managed to change my device's CID from 'HTC__621' to 'HTC__001' after doing so he downloaded this ruu and flashed it:
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radi o_2.1204.135.20_release_274900_signed.exe
This ruu turned out to work perfectly fine with my device. Everything functioned once again, the device was able to boot into recovery and boot normally without a hassle. I also discovered that this was the rom that I received my phone with which put me back to the start on android 4.0.4
I was really annoyed with the fact that I was stuck on ICS so I flashed the MaximusHD 21.1.0 rom and its boot.img which put me into a bootloop again. I also tried other custom roms such as Revolution and SD secxces which all put my phone in a bootloop even though I flashed their boot.img kernels. I knew that I required a hboot 1.33.0000 or above in order to flash jb roms so I used 'JBFWTOOL21' once again before flashing these custom roms to update my hboot from 1.12.0000 to 1.33.0000. so all these bootloops still occourd after doing all this and I just had to return back to ICS. barre in mind I only tried flashing JB roms as I want sense 5 so I don't know if a custom ics rom would work on my device as I havent tried it yet but I know for a full fact that none of the jb roms work on my device.
For those who are wondering here, I uploaded some pictures of my device just check the attachments. It has all the information you may want to know about my device (HTC One X PROTOTYPE).
I really hope someone can help me update to jelly bean and get sense 5 as I am frustrated from failing and being stuck in bootloops
If you read all of this I honestly appreciate it and I Thank you for it, I hope you can help me!

all you need to do is flash the stock recovery from this post>>>>>http://forum.xda-developers.com/showthread.php?t=1975140

I did that
nogotaclue said:
all you need to do is flash the stock recovery from this post>>>>>http://forum.xda-developers.com/showthread.php?t=1975140
Click to expand...
Click to collapse
Thank you for your input, but I already done that which resulted no success for me. The only way for me to overcome these black screens was by flashing:
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
This makes my device fully functional again but it just leaves me locked on ICS because when do the OTA updates, Flash JB ruu's or even flash custom JB roms I just get stuck on bootloops. I don't seem to get one JB version of android working on my device. Thats why I'm here seeking for help from geniuses like yourself. At the moment my device is back on android 4.0.4 but thats about it. It works perfectly fine on this version but I just can't update no matter what way I try I end up in a bootloop

so you have a stock recovery now? and receive ota notifications?

Yes
nogotaclue said:
so you have a stock recovery now? and receive ota notifications?
Click to expand...
Click to collapse
Yes I do and if I proceed with the update it will install without any problems but once it reboots it will be stuck in a bootloop. I ended up returning back to ICS and ignoring the update prompts when get told to update my software.
here you can see the update notification I recieve:

sN_iPower said:
Yes I do and if I proceed with the update it will install without any problems but once it reboots it will be stuck in a bootloop. I ended up returning back to ICS and ignoring the update prompts when get told to update my software.
here you can see the update notification I recieve:
Click to expand...
Click to collapse
you could try installing the update and if it bootloops go into the bootloader, vol down and power, and do a factory reset from there

alright
nogotaclue said:
you could try installing the update and if it bootloops go into the bootloader, vol down and power, and do a factory reset from there
Click to expand...
Click to collapse
alright im going to try that now, I will get back to you once I done it

nogotaclue said:
you could try installing the update and if it bootloops go into the bootloader, vol down and power, and do a factory reset from there
Click to expand...
Click to collapse
I just tried everything you told me, and I still ended up in a boot loop now I have to flash
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
to return back to ICS

sN_iPower said:
I just tried everything you told me, and I still ended up in a boot loop now I have to flash
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
to return back to ICS
Click to expand...
Click to collapse
I'm curious why you first chose an asian ruu for your first attempt and then got the european ruu. there is another ruu available but I need you to answer the above first.
I have to go to work now so I won't be able to answer you, there is another ruu available for version number, it's the 18th one down the list, release 974956 http://www.androidruu.com/?developer=Endeavor

sN_iPower said:
Thank you for your input, but I already done that which resulted no success for me. The only way for me to overcome these black screens was by flashing:
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
This makes my device fully functional again but it just leaves me locked on ICS because when do the OTA updates, Flash JB ruu's or even flash custom JB roms I just get stuck on bootloops. I don't seem to get one JB version of android working on my device. Thats why I'm here seeking for help from geniuses like yourself. At the moment my device is back on android 4.0.4 but thats about it. It works perfectly fine on this version but I just can't update no matter what way I try I end up in a bootloop
Click to expand...
Click to collapse
Lock you are S-OFF try fastboot writecid HTC__032 i think is something like this and see what will happend after applay update. Or try manualy update with this RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radio_5.1204.162.29_release_298897_signed.exe after changeing the CID
The other way is manualy update your hboot to high version! Download from here firmware .zip for region 401 hboot1.31 and see what will happend

nogotaclue said:
I'm curious why you first chose an asian ruu for your first attempt and then got the european ruu. there is another ruu available but I need you to answer the above first.
I have to go to work now so I won't be able to answer you, there is another ruu available for version number, it's the 18th one down the list, release 974956 http://www.androidruu.com/?developer=Endeavor
Click to expand...
Click to collapse
I flashed the asian ruu first because my CID used to be HTC__621 which requires TW ruu's (I tried the JB one) also on the back of my device it says made in Taiwan. But after flashing the rom it didn't work and put me in a bootloop so I changed my CID to 11111111 and flashed the European ruu ( I tried the JB one) which also didn't work and ended up putting me in a bootloop. It was my friends father who then changed my CID to HTC__001 and flashed the European ICS ruu which worked flawlessly. Do think I should flash the ruu you recommended? because its a ICS ruu and I'm trying to get to JB. Anyway I really thank you for trying to help me, you are the only one who replied to me
Look at this image it shows you that my device was made in Taiwan

Thant said:
Lock you are S-OFF try fastboot writecid HTC__032 i think is something like this and see what will happend after applay update. Or try manualy update with this RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radio_5.1204.162.29_release_298897_signed.exe after changeing the CID
The other way is manualy update your hboot to high version! Download from here firmware .zip for region 401 hboot1.31 and see what will happend
Click to expand...
Click to collapse
sN_iPower said:
I flashed the asian ruu first because my CID used to be HTC__621 which requires TW ruu's (I tried the JB one) also on the back of my device it says made in Taiwan. But after flashing the rom it didn't work and put me in a bootloop so I changed my CID to 11111111 and flashed the European ruu ( I tried the JB one) which also didn't work and ended up putting me in a bootloop. It was my friends father who then changed my CID to HTC__001 and flashed the European ICS ruu which worked flawlessly. Do think I should flash the ruu you recommended? because its a ICS ruu and I'm trying to get to JB. Anyway I really thank you for trying to help me, you are the only one who replied to me
Look at this image it shows you that my device was made in Taiwan
Click to expand...
Click to collapse
Actually @Thant replied also, try what he suggests at the bottom of his post to update your hboot, it's a different one to the one you tried, then try a higher ruu

I am wondering why everyone, OP and those attempting to assist, are assuming that what is apparently a prototype model of the One X would even be compatible with the updates.
If it is a prototype, regardless of how it identifies itself, it may have differences that simply prevent ANY of these software versions from operating.
I think that is one possibility the OP may have to be prepared for.

Tigerlight said:
I am wondering why everyone, OP and those attempting to assist, are assuming that what is apparently a prototype model of the One X would even be compatible with the updates.
If it is a prototype, regardless of how it identifies itself, it may have differences that simply prevent ANY of these software versions from operating.
I think that is one possibility the OP may have to be prepared for.
Click to expand...
Click to collapse
Maybe you are right he must to prepear and know the chance to broke his OneX is big because is prototype.

Tigerlight said:
I am wondering why everyone, OP and those attempting to assist, are assuming that what is apparently a prototype model of the One X would even be compatible with the updates.
If it is a prototype, regardless of how it identifies itself, it may have differences that simply prevent ANY of these software versions from operating.
I think that is one possibility the OP may have to be prepared for.
Click to expand...
Click to collapse
That had crossed my mind actually, but he is receiving ota notifications and the results he posted from "getvar all" indicate everything is as it should be, same model number even.
I have come across an early prototype before and the only 2 differences were the casing and slightly larger headphone jack socket. AFAIK the hardware was the same. Unfortunately, the one I saw wasn't working so I don't know what version of android it had

nogotaclue said:
I'm curious why you first chose an asian ruu for your first attempt and then got the european ruu. there is another ruu available but I need you to answer the above first.
I have to go to work now so I won't be able to answer you, there is another ruu available for version number, it's the 18th one down the list, release 974956 androidruu/?developer=Endeavor
Click to expand...
Click to collapse
Just to ask further: i dont see ruu for 4.19.707.3 (cid htc_044) on the site androidruu? I'm looking for it but yet to find, except for odexed/deodexed stock rom.
Sent from my HTC One X using xda app-developers app

xb2 said:
Just to ask further: i dont see ruu for 4.19.707.3 (cid htc_044) on the site androidruu? I'm looking for it but yet to find, except for odexed/deodexed stock rom.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
No more RUU only stock rom or nandroid. You never find that RUU because HTC never release this RUU.

Thant said:
No more RUU only stock rom or nandroid. You never find that RUU because HTC never release this RUU.
Click to expand...
Click to collapse
Ah, I see. Manual flashing stock rom is still ok anyway.
Thanks for the info, Thant
Sent from my HTC One X using xda app-developers app

Welcome... this had been discussed...
http://forum.xda-developers.com/showthread.php?t=2232063

I have Htc one x Prototype only ics no custom recovery no jb
hi, i have a htc one x protoype(engineer model) i have tried many times to install custom recovery and jb ruu but result is always same. bootloop and black screen. is someone can help. i know only xda members can help. so plz

[Q] rumrunner / s-off without a working OS

It's been awhile since I've messed around with Android bootloaders, but my buddy just came to me with a seemingly fried HTC One that has been stock since it was purchased. I'm trying to help him out.
We can get to the bootloader, but that is it. No OS will load, and the factory reset option does nothing. I read up on unlocking the bootloader via HTCDev, but as I'm sure you're all aware, that no longer works (MID Error 160) due to Verizon patching the exploit.
I discovered the following XDA development thread: http://forum.xda-developers.com/showthread.php?t=2473644 , but I am not allowed to post on that thread because I don't have enough posts!
It's a little bit over my head, as I'm not familiar with the rumrunner / s-off process. However, it seems that I will need to follow those steps if I want to unlock the bootloader with the hope of flashing a ROM and resurrecting the phone.
My question is this: with the current state of this phone not being able to load any OS / ROM, and having a locked bootloader, is there any possibility I can unlock the bootloader and get a ROM flashed? Is it possible I'm overthinking this? Is there a way to simply flash the stock ROM again since that is seemingly nowhere to be found? Or is this phone simply bricked? Since I can get to the bootloader, I would imagine there is some light at the end of the tunnel.
Thanks for any help you guys can give. If someone wants to offer their assistance to me directly and take the issue off the message boards, I'll gladly PayPal you 20 USD if you have a solution!
Hope everyone is having a Happy New Year.

Just to clarify, the bootloader is locked and I have S-ON.
It seems I am in a bind, because I cannot flash any stock ROM or recovery with a locked bootloader. And I cannot unlock my bootloader because Verizon has blocked the standard exploit using HTCDev.

Hey buddy, what you need is a signed ruu which is the factory version of the os that comes with the phone. The signed part means that you can flash it with locked bootloader. Here Ya go
http://forum.xda-developers.com/showthread.php?p=46506621
Just ask me if you have any questions. You will need to have the htc drivers and fastboot and adb installed of course.

Would that work if I wanted to return to 4.2 from 4.3, locked and s-on? I was too nieve and took the 4.3 update
Sent from my HTC6500LVW using xda app-developers app

tdwpkidd said:
Would that work if I wanted to return to 4.2 from 4.3, locked and s-on? I was too nieve and took the 4.3 update
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
Haha I wish.

Chilidog said:
Hey buddy, what you need is a signed ruu which is the factory version of the os that comes with the phone. The signed part means that you can flash it with locked bootloader. Here Ya go
http://forum.xda-developers.com/showthread.php?p=46506621
Just ask me if you have any questions. You will need to have the htc drivers and fastboot and adb installed of course.
Click to expand...
Click to collapse
Thanks so much for your reply. I've got the HTC drivers and the Android SDK loaded, and I used the fastboot tool when trying to unlock the boot loader using HTCDev.
Just to clarify, am I simply looking to download the signed RUU at the bottom of the second paper in that thread? Then flash it? Is that all? A lot of the other instructions in that thread seem irrelevant to my situation. If you could just point me in the right direction as to what I need to do with that RUU file, I'd appreciate it.

jmattia said:
Thanks so much for your reply. I've got the HTC drivers and the Android SDK loaded, and I used the fastboot tool when trying to unlock the boot loader using HTCDev.
Just to clarify, am I simply looking to download the signed RUU at the bottom of the second paper in that thread? Then flash it? Is that all? A lot of the other instructions in that thread seem irrelevant to my situation. If you could just point me in the right direction as to what I need to do with that RUU file, I'd appreciate it.
Click to expand...
Click to collapse
If you took the 4.3 update you will need the 4.3 ruu which I haven't seen yet....so if locked and s-on you are screwed. Now depending on how far they took the flashing and since you say its a sprint phone you might be able to HTC Dev unlock and at least get something booted until s-off is achieved on 4.3.
Sent from my Nexus 7 using Tapatalk

@jmattia Check your PM.

Need to return my Tmobile HTC 10 to stock

I am completely new at this and figured out how to unlock, root, and s-off using Sunshine. I received a new HTC 10 because my original phone's speakers cracked. I know I need to S-on, then run the ruu, and then s-on agian. I just cant figure out where to get the ruu for my phone.
I backed up my phone before on TWRP before changing the ROM and cant seem to find the file. I have three days to return my phone or Ill get charged for the phone. I need help please.

lou8414 said:
I am completely new at this and figured out how to unlock, root, and s-off using Sunshine. I received a new HTC 10 because my original phone's speakers cracked. I know I need to S-on, then run the ruu, and then s-on agian. I just cant figure out where to get the ruu for my phone.
I backed up my phone before on TWRP before changing the ROM and cant seem to find the file. I have three days to return my phone or Ill get charged for the phone. I need help please.
Click to expand...
Click to collapse
I believe you'll need to grab the system image from someone that backed it up and restore that way? I'm not sure as I'm new to this device.
Sent from my HTC 10 using XDA-Developers mobile app

both stock tmobile recovery and rom are in the stickied guide to root/recovery. I just recently sent my device back for warranty replacement.
stock recovery is here : http://forum.xda-developers.com/showpost.php?p=67248508&postcount=505 and stock rom is in OP.