Database Develop

[Q] AlphaRevX S-OFF, Clockwork recovery and want to upgrade to WWE_2.30.405.1

All,
I want to install the WWE_2.30.405.1 OTA upgrade that arrived yesterday but when I tried, it failed, so I need some help.
I have an IncS that came with Froyo and which I then upgraded OTA to gingerbread when it arrived.
I later unlocked with AplhaRevX and installed Clockwork Recovery, then rooted by following the great guide in the dev section.
I don't really care about S-OFF, clockwork or root anymore, been there done that, didn't really make much difference to what I want to do with my phone, so if I have to reset to a stock S-On phone with standard recovery etc then thats fine.
Can anyone help?
This is what I tried, but it didn't work...
Last night I got an OTA notification that there was an update, so went ahead and tried the install.
When it rebooted I got a a boot screen with an exclamation mark in a triangle and the Android guy. Then nothing..
After about 20 minutes I decided to take out the battery and reboot, that got me back in and my phone is working now, but without the upgrade, so now I'm here looking for help.

You can upgrade with the RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20 .2808.30.085AU_3805.06.03.03_M_release_199308_signed.
Donwload link on the forums.

Thanks, just found the link, but the hosting server is currently down so I can't test. Will post results when I can get the file and know what to do with it.
Some more questions...
The link is in the form of a windows EXE which makes me somewhat nervous.
I've only ever installed andoid rom's via the OTA update process, and so I'm not sure what I should do with this file.
I'll download later and see if I can figure it out, but have you explicitly tried this with the combination I have listed above?
I have a working phone right now so I'm not interested in anything that is untested.
Looking at other threads with the combination I have listed above, but applied in a different order, people have needed to resort to XTC-Clips to recover, I won't be able to do that so I need to fix this in software only.

abcprice said:
Thanks, just found the link, but the hosting server is currently down so I can't test. Will post results when I can get the file and know what to do with it.
Some more questions...
The link is in the form of a windows EXE which makes me somewhat nervous.
I've only ever installed andoid rom's via the OTA update process, and so I'm not sure what I should do with this file.
I'll download later and see if I can figure it out, but have you explicitly tried this with the combination I have listed above?
I have a working phone right now so I'm not interested in anything that is untested.
Looking at other threads with the combination I have listed above, but applied in a different order, people have needed to resort to XTC-Clips to recover, I won't be able to do that so I need to fix this in software only.
Click to expand...
Click to collapse
what you need to do is just to download the latest Ruu v2.30.405.1, connect ur phone to computer, double click the EXE file that you downloaded to run the Ruu program on a winxp/win7, click the confirm or ok button ,then you'll get what you want in about 15mins...remember not to do anything on ur phone or computer during this period.

OK Great. Will do as soon as I can download from filefactory again.
Again though I want to know has anyone tested this process and what will state will my phone be in when it is complete?
Just want a bit of reasurance that someone has actually done this with an AlpharevX S-Off phone and clockwork recovery installed.

abcprice said:
OK Great. Will do as soon as I can download from filefactory again.
Again though I want to know has anyone tested this process and what will state will my phone be in when it is complete?
Just want a bit of reasurance that someone has actually done this with an AlpharevX S-Off phone and clockwork recovery installed.
Click to expand...
Click to collapse
Those that were able to download the 2.30 RUU before the file server went down have reported that after upgrading to 2.30 AlphaRevX is no longer able to successfully run and S-OFF this version even though the HBOOT loader appears to be identical to the 2.12 RUU. If you currently have S-OFF and wish to retain it, then you shouldn't install the 2.30 RUU. You should wait for someone to build a rooted version of this ROM.

Or S-OFF with old rom, install ARHD 1.1.0 (2.30.405.1 based) and after the radio .06.03.03_M.
This is the right way.

tpbklake said:
Those that were able to download the 2.30 RUU before the file server went down have reported that after upgrading to 2.30 AlphaRevX is no longer able to successfully run and S-OFF this version even though the HBOOT loader appears to be identical to the 2.12 RUU. If you currently have S-OFF and wish to retain it, then you shouldn't install the 2.30 RUU. You should wait for someone to build a rooted version of this ROM.
Click to expand...
Click to collapse
OK Thanks.
Do you have a link to someone 'reporting' that they tried the RUU on a phone with AlphaRevX S-Off and Clockwork?
Not worried about losing my S-Off status or root, I want my phone to be able to take OTA updates again, in fact if I could restore to the state it was in before I unlocked, then that would be best of all.
Also anyone willing to post a copy of the RUU somewhere else for download, cos the filefactory link still seems to be down.

abcprice said:
OK Thanks.
Do you have a link to someone 'reporting' that they tried the RUU on a phone with AlphaRevX S-Off and Clockwork?
Not worried about losing my S-Off status or root, I want my phone to be able to take OTA updates again, in fact if I could restore to the state it was in before I unlocked, then that would be best of all.
Also anyone willing to post a copy of the RUU somewhere else for download, cos the filefactory link still seems to be down.
Click to expand...
Click to collapse
Here is a thread that discusses flashing the RUU and the attempts of AlphaRevX:
http://forum.xda-developers.com/showthread.php?t=1153871

OK That thread is all about how it didn't work, and the download site is still broken, so I'm not going to try anything for now.
I'll be away with work next week and need my phone to work, so I'll look in again when I get back and see if anything has changed.
Thanks for all your help anyway, I don't think this thread actually got even close to answering my question, but at least you tried.
If I try flashingthe RUU file then I'll be sure to let you know how it turned out.
Bye for now.

abcprice said:
OK That thread is all about how it didn't work, and the download site is still broken, so I'm not going to try anything for now.
I'll be away with work next week and need my phone to work, so I'll look in again when I get back and see if anything has changed.
Thanks for all your help anyway, I don't think this thread actually got even close to answering my question, but at least you tried.
If I try flashingthe RUU file then I'll be sure to let you know how it turned out.
Bye for now.
Click to expand...
Click to collapse
The point of mentioning that thread was that these users had previously used AlphaRevX to gain S-OFF and when they installed the 2.30 RUU and they lost root and S-OFF and they are now attempting to get S-OFF back which is the part that is failing.

OK So I'm back from my trip and today I had a chance to play with this a bit.
I downloaded this RUU http://api.viglink.com/api/click?format=go&drKey=1359&loc=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1033922&v=1&libid=1310921120143&out=http%3A%2F%2Fwww.filefactory.com%2Ffile%2Fcc2d60f%2Fn%2FRUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed.exe&title=%5BROMs%5DIncredible%20S%20Shipped%20ROMs%20Collection%20-%20xda-developers&txt=http%3A%2F%2Fwww.filefactory.com%2Ffile%2Fcc2d...308_signed.exe and tested an install.
I got what I wanted more or less, I have the update and all looks good..
However for those of you following from home, these are the trade-offs.
All data on my phone was erased. I had an 'out of box' experience when I booted the phone.
I lost S-Off status
I Lost root
I seem to have a corrupt recovery partition. (When I select recovery from the boot menu it hangs at a screen with a red triangle and an exclamation mark. Only way to boot the phone after that is to remove the battery and re-insert).
4 in particular bothers me a bit, as I'm not sure how to recover that and I'm not sure if I may need it in future. If you remember, what I originally wanted was to be able to get OTA updates in future, from reading around, I don't think that will be possible with a corrupt recovery image, so any tips on fixing that would be great.

Just download the latest or if you wanna keep s off a previous RUU from your carrier. And run the program it will return the phone to stalk
Sent from my HTC Incredible S using XDA Premium App

Hmm, thats what I think I've done.
My device is not tied to a carrier, so the WWE RUU Should have been the right one.
I have now also tried using fastboot to flash the recovery, but I get the following error
C:\Phone\>fastboot.exe flash recovery recovery.img
sending 'recovery' (3658 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
I tried with an older recovery from WWE 212 as well, but got the same error. Don't really know where to go next, but any help gladly recieved.

abcprice said:
OK So I'm back from my trip and today I had a chance to play with this a bit.
I downloaded this RUU http://api.viglink.com/api/click?format=go&drKey=1359&loc=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1033922&v=1&libid=1310921120143&out=http%3A%2F%2Fwww.filefactory.com%2Ffile%2Fcc2d60f%2Fn%2FRUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed.exe&title=%5BROMs%5DIncredible%20S%20Shipped%20ROMs%20Collection%20-%20xda-developers&txt=http%3A%2F%2Fwww.filefactory.com%2Ffile%2Fcc2d...308_signed.exe and tested an install.
I got what I wanted more or less, I have the update and all looks good..
However for those of you following from home, these are the trade-offs.
All data on my phone was erased. I had an 'out of box' experience when I booted the phone.
I lost S-Off status
I Lost root
I seem to have a corrupt recovery partition. (When I select recovery from the boot menu it hangs at a screen with a red triangle and an exclamation mark. Only way to boot the phone after that is to remove the battery and re-insert).
4 in particular bothers me a bit, as I'm not sure how to recover that and I'm not sure if I may need it in future. If you remember, what I originally wanted was to be able to get OTA updates in future, from reading around, I don't think that will be possible with a corrupt recovery image, so any tips on fixing that would be great.
Click to expand...
Click to collapse
That's not corrupt, that's what happens on stock

Ahh OK, if that is normal then how do I test that my recovery partition is good? I don't want to get buggered when the next OTA comes along.

Stock RUU's Download Here >

​
This is an update on a previous post, this time however you don't have to sieve through Chinese websites to get them....i have spent time to get them for you!
This Will revert your HTC Salsa to Stock​​
By using these you will wipe everything you have done. Recovery will be wiped, unknown about lock/unlocked boot-loader as i haven't attempted this with unlocked boot-loader before as.i had s-off at the time.
You do this at your own risk, i take no responsibility at all for anything that may or may not happen lol​​
Instructions for use.
HTC SYNC installed but not running, you want the cable driver mainly.
Instead of following on screen instruction via the RUU, set your phone into fastboot mode yourself then activate/run the RUU.exe you require, i would suggest run as administrator (right click on application)
This will take some time to install, i did it on 3rd attempt, first 2 were relying on the RUU to boot the phone for me...3rd i booted into fastboot/bootloader myself and away it went.
if for any reason it doesn't respond to you or it doesn't install stock or freezes, whip out the battery and do it all again!
Below are the RUU's please find the correct region your in and download accordingly. EU RUU is a common one if the others don't work. all roms are based of this version.
RUU_Icon_G_HTCCN_CHS_1.24.1400.4_Radio_47.14.35.3030H_7.47.35.17_release_204455_signed.exe
RUU_Icon_G_HTC_Europe_1.12.401.1_R_Radio_47.14.35.3030H_7.47.35.17_release_193257_signed.exe
RUU_Icon_G_O2_UK_1.18.206.2_Radio_47.14.35.3030H_7.47.35.17_release_198160_signed.exe
RUU_Icon_G_hTC_Asia_HK_1.16.708.3_Radio_47.14.35.3030H_7.47.35.17_release_197702_signed.exe
RUU_Icon_G_hTC_Asia_India_1.12.720.2_Radio_47.14.35.3030H_7.47.35.17_release_193467_signed.exe
RUU_Icon_G_HTC_TUR_1.18.468.2_Radio_47.14.35.3030H_7.47.35.17_release_199341_signed.exe
RUU_Icon_G_Hutch_AUS_1.18.861.1_Radio_47.14.35.3030H_7.47.35.17_release_197619_signed.exe
RUU_Icon_G_Voda-Hutch_AU_1.17.862.2_Radio_47.14.35.3030H_7.47.35.17_release_198433_signed.exe
RUU_Icon_G_Chunghwa_1.13.751.1_Radio_47.14.35.3030H_7.47.35.17_release_193940_signed.exe
RUU_Icon_G_hTC_Asia_WWE_1.12.707.2_Radio_47.14.35.3030H_7.47.35.17_release_193464_signed.exe
as the link in the lower post suggested you can also try this
*this wasn't provided by me please don't blame me if anything goes wrong*
1. Download your RUU
2. Extract and copy the system.img AND boot.img to the same directory as your fastboot tools "C:/fastboottools" ( make sure to copy both files )
3. Enter the fastboot mode on your phone by pressing volume down + power button after the device has been turned off.
4. Choose fastboot on the phone by pressing power button, and then connect your phone to your PC
5. Using fastboot tools, open the Command prompt and navigate to "C:\fastboottools" then run this command on cmd: "fastboot flash system system.img"
6. Dont reboot, Using fastboot tools, run this command on cmd: "fastboot flash boot boot.img"
( The two commands in step 5 and 6 are different, make sure to type each one correctly and to do them straight after each other )
7. Reboot phone. let it boot up, you will still get bootloop or error message.
8. Take out the battery.
9. Boot back into bootloader ( Volume down + power ).
10. Now choose recovery.
11. Phone should now reboot itself and bam, all should now work fine.​

Well it seems a lot of you shadows hiding away wanted these lol, as the downloads in 1 day surprised me lol.
BigBear is using Xparent Tapatalk Purple

I managed to revert back to stock using this method http://forum.xda-developers.com/showthread.php?t=1631121
Now I am running 2.3.3
Now i just want to update to 2.3.5 if possible, haven't been able to get OTA updates. Do you know how i can go about it?
CWM recovery is still intact.
Thanks

The salsa will never have 2.3.5 ota. HTC stopped at 2.3.3 and discontinued updates for us. well the stopped producing the salsa and totally dropped it.
that's why we have 2.3.5 roms that are not meant for us...ie no FB button that works correctly, no mirror or front facing camera.
and this is probably why noone is still running stock roms anymore
BigBear is using Xparent Tapatalk Purple

getting error 155 again and again. Used RUU_Europe, RUU_UK, RUU_Asia_WWE, RU_Asia_India. Rebooted to the fastboot screen myself but the RUU takes over from the white screen and fastboot menu and goes into the black screen with HTC written. Tried letting RUU boot itself but still same error.
EDIT:
I have previously unlocked bootloader to gain Root Access since I had S-ON on my device. Need help urgently. Can I revert back to a locked Bootloader or anything ?

Now I have relocked the bootloader and tried the Europe Salsa RUU.... It is giving me Error 140 now claiming the bootloader version is invalid.
HBOOT is updated and I notice that the Radio version mentioned on Fastboot Bootloader screen is different than mentioned in the RUU.
Mine says:
*** Relocked ***
ICON_G PVT SHIP S-ON RL
HBOOT-1.08.0000
MICROP-0558
RADIO-7.51.35.19
Dec 16 2011,16:12:07

razasohail said:
getting error 155 again and again. Used RUU_Europe, RUU_UK, RUU_Asia_WWE, RU_Asia_India. Rebooted to the fastboot screen myself but the RUU takes over from the white screen and fastboot menu and goes into the black screen with HTC written. Tried letting RUU boot itself but still same error.
EDIT:
I have previously unlocked bootloader to gain Root Access since I had S-ON on my device. Need help urgently. Can I revert back to a locked Bootloader or anything ?
Click to expand...
Click to collapse
Did you take a nandroid backup in recovery at all?, if so restore it.if recovery isn't there reinstall recovery and restore your backup.
BigBear is using Xparent Tapatalk Purple

Get the phone to Stock
Hi..
Where can I get these files
system.img and boot.img
2. Extract and copy the system.img AND boot.img to the same directory as your fastboot tools "C:/fastboottools" ( make sure to copy both files )

arekapudi said:
Hi..
Where can I get these files
system.img and boot.img
2. Extract and copy the system.img AND boot.img to the same directory as your fastboot tools "C:/fastboottools" ( make sure to copy both files )
Click to expand...
Click to collapse
this guide wasn't provided by me, i do know what this means but its hard to explain to a newbie...
for the more technical side of go here >http://forum.xda-developers.com/showthread.php?t=1631121, it may help you...

ok after of hours of fiddling around with this, I have come to the point where I really need the system.img and boot.img files
my phone is stuck at the htc boot screen with white background.
I have installed htc cable driver and got fastboottools files created and did some googling and found out that the only other way to install this is by running the exe while in fastboot and have to bootloader "relocked"
I tried to extract them from the executable using 7-zip but can't see them there.
Any help is greatly appreciated. thanks.

Saturn007 said:
ok after of hours of fiddling around with this, I have come to the point where I really need the system.img and boot.img files
my phone is stuck at the htc boot screen with white background.
I have installed htc cable driver and got fastboottools files created and did some googling and found out that the only other way to install this is by running the exe while in fastboot and have to bootloader "relocked"
I tried to extract them from the executable using 7-zip but can't see them there.
Any help is greatly appreciated. thanks.
Click to expand...
Click to collapse
in all fairness mate, i can't help on this. these guides were provided by others and has been known to work for us. i have not tried this and will not be trying this either as i have no desire to revert. what i do mention in all rom threads is this. take a backup of your stock rom in recovery before you tamper or change anything, this way you can revert straight back to your stock rom, no questions asked.
i would think though you may not have either installed correctly or its the wrong ruu, but i can't tell

BigBearEvo said:
in all fairness mate, i can't help on this. these guides were provided by others and has been known to work for us. i have not tried this and will not be trying this either as i have no desire to revert. what i do mention in all rom threads is this. take a backup of your stock rom in recovery before you tamper or change anything, this way you can revert straight back to your stock rom, no questions asked.
i would think though you may not have either installed correctly or its the wrong ruu, but i can't tell
Click to expand...
Click to collapse
I am not holding you responsible for any of my actions mate. I do appreciate all the info you provided here.
I attempted to do a backup but the SD card got full in the middle of the process. My luck.
I was just asking if anyone (not necessarily you) would have a copy of these files as I attempted to download the files from the other thread, http://forum.xda-developers.com/showthread.php?t=1631121, but the links are dead. I was hoping someone might have them and would like to share with us. That's all.

Saturn007 said:
I am not holding you responsible for any of my actions mate. I do appreciate all the info you provided here.
I attempted to do a backup but the SD card got full in the middle of the process. My luck.
I was just asking if anyone (not necessarily you) would have a copy of these files as I attempted to download the files from the other thread, http://forum.xda-developers.com/showthread.php?t=1631121, but the links are dead. I was hoping someone might have them and would like to share with us. That's all.
Click to expand...
Click to collapse
tel me what you want and ill get it, but you have to tell me which file to get it from and ill host it up for you. ie you want the system.img and boot.img but from which ruu?

BigBearEvo said:
tel me what you want and ill get it, but you have to tell me which file to get it from and ill host it up for you. ie you want the system.img and boot.img but from which ruu?
Click to expand...
Click to collapse
Hi i am getting error 140 aswell after relocking my bootloader..???can someone help me as im trying to restore and im struggeling...
any help will be appreciated but i tried some other tutorials but they require a zip version of the RUU.. ;(

gagan313 said:
Hi i am getting error 140 aswell after relocking my bootloader..???can someone help me as im trying to restore and im struggeling...
any help will be appreciated but i tried some other tutorials but they require a zip version of the RUU.. ;(
Click to expand...
Click to collapse
you won't get a zip version ruu only stock as i listed rom wise. now did you lock the bootloader before trying to add stock back on?
if you did there's part of your problem.
unlock it again, go find stock.zip in stock rom thread in android development section and flash it....then lock the bootloader. if you lock the loader again please note root etc won't work/function correctly again. to have any root privilege's you require either s-off or unlocked bootloader.

BigBearEvo said:
you won't get a zip version ruu only stock as i listed rom wise. now did you lock the bootloader before trying to add stock back on?
if you did there's part of your problem.
unlock it again, go find stock.zip in stock rom thread in android development section and flash it....then lock the bootloader. if you lock the loader again please note root etc won't work/function correctly again. to have any root privilege's you require either s-off or unlocked bootloader.
Click to expand...
Click to collapse
ok i will try that now
---------- Post added at 09:53 PM ---------- Previous post was at 09:41 PM ----------
nope... it dosnt work... it says bootloader version error
(which came up before..)
just so you know.. i am S-ON and hboot 1.8.00000 or somthing...
---------- Post added at 10:34 PM ---------- Previous post was at 09:53 PM ----------
could it be posssible that i have the wrong RUU??
i am definatly on EURO but when i go through the ruu install wizard it says:
Verify that you want to update the ROM version:
From:
Image version:
1.28.0.0
To:
Image version:
1.12.401.1_r
could i have the wrong one?? or is this normal??

gagan313 said:
ok i will try that now
---------- Post added at 09:53 PM ---------- Previous post was at 09:41 PM ----------
nope... it dosnt work... it says bootloader version error
(which came up before..)
just so you know.. i am S-ON and hboot 1.8.00000 or somthing...
---------- Post added at 10:34 PM ---------- Previous post was at 09:53 PM ----------
could it be posssible that i have the wrong RUU??
i am definatly on EURO but when i go through the ruu install wizard it says:
Verify that you want to update the ROM version:
From:
Image version:
1.28.0.0
To:
Image version:
1.12.401.1_r
could i have the wrong one?? or is this normal??
Click to expand...
Click to collapse
tends to be normal that, but just to let you know...i have only ever reset using the ruu once before and it took along time to do it! since then ive never gone back. ive flashed stock.zip which gave me back stock...but its not for me.
so flash my stock.zip nothing else.
if it is just Facebook your having issues with then don't just swap roms or go back to stock, it won't help, it will probably make it worse to be honest. im using a new black Facebook as i hosted in the thread in android apps section and have no problems with it.
just make sure you have Facebook installed and moved to sd only.

BigBearEvo said:
tends to be normal that, but just to let you know...i have only ever reset using the ruu once before and it took along time to do it! since then ive never gone back. ive flashed stock.zip which gave me back stock...but its not for me.
so flash my stock.zip nothing else.
if it is just Facebook your having issues with then don't just swap roms or go back to stock, it won't help, it will probably make it worse to be honest. im using a new black Facebook as i hosted in the thread in android apps section and have no problems with it.
just make sure you have Facebook installed and moved to sd only.
Click to expand...
Click to collapse
thats just the thing you see....
for some reason, if i try the stock.zip i always have wifi issues as well as facebook issues and well... i have tried all the facebooks from 1.9.9 to the black one and it dosnt seem to sign in... evern after i have unin installed and moved to sd card using links2sd....:crying:
as for stock....
what i think is that there is a problem with my hboot... and error massage came up saying my hboot is newer than the one im trying to install... any way i can downgrade? (sorry for asking for so much of you)

gagan313 said:
that's just the thing you see....
for some reason, if i try the stock.zip i always have WiFi issues as well as Facebook issues and well... i have tried all the Facebook from 1.9.9 to the black one and it doesn't seem to sign in... even after i have uninstalled and moved to sdcard using link2sd....:crying:
as for stock....
what i think is that there is a problem with my hboot... and error massage came up saying my hboot is newer than the one im trying to install... any way i can downgrade? (sorry for asking for so much of you)
Click to expand...
Click to collapse
no way to downgrade sorry.
it has been noted elsewhere that this Facebook issue tends to fail when its installed on normal internal memory or as an update on-top of the system Facebook already installed.
you can tell if this is the case by going into link2sd and looking at Facebook.apk, it may have a green updated next to it. you can remove this update by uninstalling it.
i don't have this problem as it works fine on CM7.
you can try and uninstall the Facebook you have, go into recovery wipe cache/dalvik and reboot, apparently this removes all traces it was there.
reboot and install Facebook 2.0 or black which ever.
using link2sd move it to the sdcard and then try it.
i am gonna try this on other roms when i can to see if this works or not.

BigBearEvo said:
no way to downgrade sorry.
it has been noted elsewhere that this Facebook issue tends to fail when its installed on normal internal memory or as an update on-top of the system Facebook already installed.
you can tell if this is the case by going into link2sd and looking at Facebook.apk, it may have a green updated next to it. you can remove this update by uninstalling it.
i don't have this problem as it works fine on CM7.
you can try and uninstall the Facebook you have, go into recovery wipe cache/dalvik and reboot, apparently this removes all traces it was there.
reboot and install Facebook 2.0 or black which ever.
using link2sd move it to the sdcard and then try it.
i am gonna try this on other roms when i can to see if this works or not.
Click to expand...
Click to collapse
ok ill give it a shot

[Q] Tried to get my One back to Stock, gone wrong somehwere

Hi, recently the screen broke on my 2 week old HTC One.
Amazon were kind enough to send me a new one, but I had modded the hell out of the first one (using various online tutorials to root and then ROM it), and now have the need to return it.
So I followed various tutorials to try and restore it back to 100% stock. (Didn't bother making it "Locked" rather than "Unlocked").
What I did was I used the HTC One All-In-One Toolkit, and "relocked bootloader". I then tried to flash the RUU, all went well, but when I try to start it up after, it gives a blank black screen. However, after giving it a while, holding the power button, or pressing the back button sometimes results in a vibration, so I'm presuming that it is starting, but not displaying anything. I was hoping that my phone would come up in windows so I could re-flash twrp and flash Sense that way, but it does not appear.
I tried factory resetting in this state, but when I try boot it up after that, a logo comes up which is a phone, with 2 green arrows forming a circle inside it, then a green arrow pointing down inside that.
Also, flashing twrp.img seems to go well, but when select "recovery", nothing happens, it just seems to boot up normally.
I am now at a loss of ideas, as this process was suggested by all the sources I could find, and it works perfectly for them, see no reason for it not to for me.
If anyone has any idea how to fix this, please, please respond as quickly as possible, it has to be with Amazon by the 4th, and I have no clue what to do!
Thanks,
-Accudio

yeah i got the point here, just one question, are you S-OFF or not? if yes, which is you bootloader?

matt95 said:
yeah i got the point here, just one question, are you S-OFF or not? if yes, which is you bootloader?
Click to expand...
Click to collapse
No, I'm S-ON, when I first did it I was a bit of a noob, and none of the tutorials I followed said anything about S-ON/S-OFF. Only just found out about it when researching how to put it back. :/

You can't access recovery because your phone is locked, so first off you need to unlock again your phone

matt95 said:
You can't access recovery because your phone is locked, so first off you need to unlock again your phone
Click to expand...
Click to collapse
Gotta go now, but well do when I next can. Using the "Unlock Bootloader" tool on the HTC Dev website yeah?

Accudio said:
Gotta go now, but well do when I next can. Using the "Unlock Bootloader" tool on the HTC Dev website yeah?
Click to expand...
Click to collapse
Yeah, however you can use the previous Unlockcode.bin that you used to unlock it the first time...

matt95 said:
Yeah, however you can use the previous Unlockcode.bin that you used to unlock it the first time...
Click to expand...
Click to collapse
OK, I have now unlocked it, I'd flash TWRP now yes?
EDIT: Now flashed TWRP, it's working fine, but how can I transfer the ROM zip across without having a version of android that works?

Accudio said:
OK, I have now unlocked it, I'd flash TWRP now yes?
EDIT: Now flashed TWRP, it's working fine, but how can I transfer the ROM zip across without having a version of android that works?
Click to expand...
Click to collapse
adb commands work in recovery too.
either use "adp push rom.zip /sdcard/" or use the sideload method

Thanks a lot guys, you've been a great help! 2 more questions for you if you don't mind:
1. The ROM I found doesn't seem to work properly, so have you got any ideas of ROMs of Sense 5, no root, so it will appear to amazon that it is stock, even if it isn't exactly, or do you know where I can get an RUU and how to flash it to get my phone back to exactly stock?
2. This won't be a big deal, but how could I achieve S-OFF to revert my HTC recovery to say "Locked" rather than "Tampered" and "Relocked"
If they aren't possible, no big deal, just would be nice if I can. Again, thanks a ton, you've saved my neck! xD
EDIT: I am downloading a different ROM to try, so hopefully that will work better.

Accudio said:
Thanks a lot guys, you've been a great help! 2 more questions for you if you don't mind:
1. The ROM I found doesn't seem to work properly, so have you got any ideas of ROMs of Sense 5, no root, so it will appear to amazon that it is stock, even if it isn't exactly, or do you know where I can get an RUU and how to flash it to get my phone back to exactly stock?
2. This won't be a big deal, but how could I achieve S-OFF to revert my HTC recovery to say "Locked" rather than "Tampered" and "Relocked"
If they aren't possible, no big deal, just would be nice if I can. Again, thanks a ton, you've saved my neck! xD
Click to expand...
Click to collapse
1. Just download a stock odexed rom from the development section. There are many to choose from.
OR
Pick a RUU from here. http://forum.xda-developers.com/showthread.php?p=39588860
2. Use this link to do that. Then read the instructions on how to reset the flags.
Did amazon really replace your broken phone for free? Thats what I call customer service. Too bad I bought mine from ATT.
THIRD OPTION:
Download http://forum.xda-developers.com/showthread.php?t=2353083
And remove supersu.apk from the zip file before you flash it.

aooga said:
1. Just download a stock odexed rom from the development section. There are many to choose from.
2. Use this link to do that. Then read the instructions on how to reset the flags.
Did amazon really replace your broken phone for free? Thats what I call customer service. Too bad I bought mine from ATT.
Click to expand...
Click to collapse
Yeah, I dropped it onto my carpet and the screen cracked pretty majorly, so I contacted HTC pretty annoyed (as you can expect), and they said that I must have had a dodgy model for it to have broken so easily. Amazon was reluctant but because I had HTC's word they sent me a free replacement.

Accudio said:
Yeah, I dropped it onto my carpet and the screen cracked pretty majorly, so I contacted HTC pretty annoyed (as you can expect), and they said that I must have had a dodgy model for it to have broken so easily. Amazon was reluctant but because I had HTC's word they sent me a free replacement.
Click to expand...
Click to collapse
Wow. thats nice of them. Read my previous post to answer your questions. I added another option.

aooga said:
1. Just download a stock odexed rom from the development section. There are many to choose from.
OR
Pick a RUU from here. http://forum.xda-developers.com/showthread.php?p=39588860
2. Use this link to do that. Then read the instructions on how to reset the flags.
Did amazon really replace your broken phone for free? Thats what I call customer service. Too bad I bought mine from ATT.
THIRD OPTION:
Download http://forum.xda-developers.com/showthread.php?t=2353083
And remove supersu.apk from the zip file before you flash it.
Click to expand...
Click to collapse
I have HBOOT version 1.54, so as the Revone thread says I cannot use that. Is there any other way or will I just not be able to do it? Had a quick look and couldn't find anything.

Accudio said:
I have HBOOT version 1.54, so as the Revone thread says I cannot use that. Is there any other way or will I just not be able to do it? Had a quick look and couldn't find anything.
Click to expand...
Click to collapse
ohhh..that might be a problem. How did you manage to get on hboot 1.54? I don't think there is a S-off method for that yet. Do you still have the unlockcode.bin from when you unlocked it the first time?

aooga said:
ohhh..that might be a problem. How did you manage to get on hboot 1.54? I don't think there is a S-off method for that yet. Do you still have the unlockcode.bin from when you unlocked it the first time?
Click to expand...
Click to collapse
I don't know, if I remember correctly it was actually on that when I got it, not certain though. I do have my first unlockcode.bin saved.

Accudio said:
I don't know, if I remember correctly it was actually on that when I got it, not certain though. I do have my first unlockcode.bin saved.
Click to expand...
Click to collapse
You should be able to unlock your bootloader again with the unlockcode.
If I'm not mistaken, in order to flash a RUU you need to:
- Flash stock recovery.img through bootloader+fastboot
- Flash stock boot.img through bootloader+fastboot
RUU should flash now whether bootloader is locked, unlocked or relocked.

Accudio said:
I don't know, if I remember correctly it was actually on that when I got it, not certain though. I do have my first unlockcode.bin saved.
Click to expand...
Click to collapse
as long as you used that file to unlock this phone, then it will work.

Ok, I'm getting an error saying:
"Unfortunately, HTC Sense has stopped."
and also
"Unfortunately Contacts Storage has stopped."
I had the Contacts srtorage one with my old S2, which I fixed by clearing data of contacts storage, but the one about HTC sense stops anything from working.

aooga said:
1. Just download a stock odexed rom from the development section. There are many to choose from.
OR
Pick a RUU from here. http://forum.xda-developers.com/showthread.php?p=39588860
2. Use this link to do that. Then read the instructions on how to reset the flags.
Did amazon really replace your broken phone for free? Thats what I call customer service. Too bad I bought mine from ATT.
THIRD OPTION:
Download http://forum.xda-developers.com/showthread.php?t=2353083
And remove supersu.apk from the zip file before you flash it.
Click to expand...
Click to collapse
Sorry if I'm being a bit of a noob, how would I remove superuser.apk?

Accudio said:
Sorry if I'm being a bit of a noob, how would I remove superuser.apk?
Click to expand...
Click to collapse
if you have a pc, before you push the rom to your phone, open the zip file and delete the apk in /system/app/supersu.apk

[Q] Need Help please with strange bootloop problem

A friend has asked me to try and fix there M7 ul. It was. Completely stock on O2 UK. They got a notification for system update (4.4.2 Sense6.0). While installing they left the phone and when they came back it was off. After some fiddling they managed to get it to come on but it would only boot to the bootloader which had Tampered and Locked flags.
This is where I came in so I tried booting to stock recovery to see if the OTA would complete but it was a no go. The screen just stayed black for ages then eventually would show the phone picture with red exclamation. Using volume up+power to get the recovery menu to reset cache returned it to the normal picture with green arrows. But reboot and repeat So I tried fastboot erase cache and attempted ota again with same results.
At this point I told them that anything more I tried may void the warranty so better to send it in but there is no warranty so asked me to do whatever I can. Naturally for me the next step was to unlock the bootloader to regain some control. First I just let the phone boot this time no bootloader screen but it just looped on the HTC splash screen.(i kind of expected that). So next I reboot bootloader and flash twrp2.6.3.3 erase cache and boot recovery. ARHD rom was already in my android folder so pushed it strait over. Ran into some pitfalls trying to flash the rom like instant reboots when flashing started and disappearing zip files fixed with e2fsck, zip failed message fixed with Format data and eventually got the rom installed. I know first boot normally takes a while but this seemed longer than expected but eventually booted the rom and everything seemed to be working fine.
After setting up the basics and testing a few things (installing and running apps. Playing music and so on) I rebooted the phone but again it bootloops on HTC splash screen. Tried everything to get it to boot like wipeing cache/dalvik, dirty flash, clean install even fix permissions nothing worked except Format Data in Twrp Full wipe, re-push rom re-flash rom. Phone took a while but booted and again worked perfectly while setting up and using the phone. So tried restart and again bootloop on HTC splash
So I'm now at a point where I think I've narrowed it down to the Kernel or Ramdisk or atleast the partition there installed on. Since if I use the Superwipe script to wipe only the boot partition cache/dalvik then refresh the boot.img or flash a kernel from recovery (i've been using bulletproof kernel) the phone will boot with the rom and settings intact.
If there is a problem with this partition I do not know how to fix it. I know mmcblk0p33 is the boot partition but is it where the boot.img actually lives or is that the bootloader partition?
If it is the boot.img partition can I repair it with mke2fs or e2fsck or some other tool?
There is an ruu available for the device so if I can just stop the bootloop I could s-off and then ruu and return it to stock. But firewater won't work and I think it's because of the procedure involved in getting the phone to boot is interfering with the push somehow. Firewater will push ok and chmod works but when I try to run firewater nothing happens and then the firewater file disappears and I have to push it again which means re-wipeing and flashing the kernel. I'm really not sure where to go from here any help or suggestions would be most appreciated thanks in advance :fingers-crossed:

Ok so s-off is out of the question since this phone has emmc cid 9001 best I can hope for now is a firmware.zip. I did keep trying firewater and eventually got it to run but sure enough I got Whelp this sucks!!
Would using cwm to format boot be any different to what superwipe dose? It says Format Boot but dose it actually format it or just wipe the data from it? I haven't used cwm since my galaxy ace days.

Danny201281 said:
Ok so s-off is out of the question since this phone has emmc cid 9001 best I can hope for now is a firmware.zip. I did keep trying firewater and eventually got it to run but sure enough I got Whelp this sucks!!
Would using cwm to format boot be any different to what superwipe dose? It says Format Boot but dose it actually format it or just wipe the data from it? I haven't used cwm since my galaxy ace days.
Click to expand...
Click to collapse
you could try a full wipe firmware.zip and HBOOT, you will have to use the one you currently have on the device or the next newer one due to s-on, it will / should re-write your partitions, try looking here:
(searching for link)

Seanie280672 said:
you could try a full wipe firmware.zip and HBOOT, you will have to use the one you currently have on the device or the next newer one due to s-on, it will / should re-write your partitions, try looking here:
(searching for link)
Click to expand...
Click to collapse
Thanks for reply.
Yep I've been looking for a firmware.zip it on 5.12.206.3 all I can find is an ruu.exe but it's the version before. I searched the updates thread and no one seems to have captured the OTA file so can't even extract from there.

Danny201281 said:
Thanks for reply.
Yep I've been looking for a firmware.zip it on 5.12.206.3 all I can find is an ruu.exe but it's the version before. I searched the updates thread and no one seems to have captured the OTA file so can't even extract from there.
Click to expand...
Click to collapse
trouble is, you will need the full firmware, not just an OTA, and the wipe version, usually I see the page with the HBOOTs and firmwares everywhere, do you think I can find it now I need it...........
found it finally, check see if yours is in there, full wipe section: https://docs.google.com/spreadsheets/d/1LQDLpVZYyUpXPgC2sh1BvAS9Oo8B-fTiZU_JhpIH-fU/pubhtml#
---------- Post added at 01:50 PM ---------- Previous post was at 01:40 PM ----------
trouble is too, you cant s-off without a working rom on it, unless you can find someone who can do it by java card for you which is all done from the bootloader.

Seanie280672 said:
trouble is, you will need the full firmware, not just an OTA, and the wipe version, usually I see the page with the HBOOTs and firmwares everywhere, do you think I can find it now I need it...........
found it finally, check see if yours is in there, full wipe section: https://docs.google.com/spreadsheets/d/1LQDLpVZYyUpXPgC2sh1BvAS9Oo8B-fTiZU_JhpIH-fU/pubhtml#
Click to expand...
Click to collapse
Thanks for looking I'll start searching for it now. I hope there's something out there. :fingers-crossed:

Danny201281 said:
Thanks for looking I'll start searching for it now. I hope there's something out there. :fingers-crossed:
Click to expand...
Click to collapse
is it the HTC one ? or the HTC one Mini ?

Danny201281 said:
Thanks for looking I'll start searching for it now. I hope there's something out there. :fingers-crossed:
Click to expand...
Click to collapse
I can get a working rom no problem but it will only boot if I superwipe the boot partition and reflash kernel. Other wise it just bootloops.
But I've already had the whelp this sucks message so no s-off that's why's I need a matching firmware.

Seanie280672 said:
is it the HTC one ? or the HTC one Mini ?
Click to expand...
Click to collapse
HTC one M7_UL

Danny201281 said:
HTC one M7_UL
Click to expand...
Click to collapse
The only RUU I could find is 4.xx.206.xx, you really need s-off to sort it, as you cant use that RUU, there is no RUU for your current version as its all ota's to get to that point, you may have some luck if you can find the next one up which will be 6.06.206.xx.
however, if you are in the UK and can live without your phone for a few days, then give these guys a call, book your phone in with them, and send it to them, they will s-off it by java card and send it back the same day, overall it takes about 3 or 4 days, its who I used, they were very helpful and friendly bunch of guys, best £15 quid ive ever spent.
http://www.fonefunshop.co.uk/Unlocking/htc_s-off_service.htm
---------- Post added at 02:09 PM ---------- Previous post was at 02:01 PM ----------
actually, im over thinking things, have you tried this, it should also re-write your partitions: http://forum.xda-developers.com/showthread.php?t=2770684

Seanie280672 said:
actually, im over thinking things, have you tried this, it should also re-write your partitions: http://forum.xda-developers.com/showthread.php?t=2770684
Click to expand...
Click to collapse
Yes I remember this thread starting up I had considered this but not sure it would work as phone isn't in qhusb dload plus no evidence so far (i've still got some posts to read) it works with s-on. But I'll definitely give it a try if all else fails. Thanks again

Well I don't know if it's from the repeated wiping and flashing of the kernel or what but the phone seems to boot every time without the need to reflash the kernel now. Only it takes about 20mins looping once or twice on the splash screen. Once it gets past that from the boot animation onwards it works flawlessly. I can't get my head around it.

Just to put some closure to this. It's determined to be a hardware problem. Possibly a damaged memory chip. I did manage to return it to stock before handing it back to the owner with the bad news. But it will not boot the stock Rom at all just loops endlessly on the HTC LOGO splash screen.
Case closed
Sent from my HTC One M7 ARHD 71.1 (Minus Purple tint) using TapaTalk

Black Screen, Phone On, But No Backlight

Ok so before I begin, I've read everything online and cannot figure this out. I've searched the forums for hours and still no luck.
I have the HTC One M7 with T-Mobile
I've had it since December with no issues at all, and still in mint condition. Never dropped.
I have it rooted, with boot unlocked
ViperOne ROM Installed, stock kernel.
Ok so Tuesday night I was going to bed (phone still on and working) and plugged my phone in to the charger to charge for the night as I usually do every night. Wake up in the morning and hit the power button to unlock the phone and to my surprise the display doesn't come on. As I said I've never dropped this phone in the entire 9 months I've had it, nor has it ever gotten wet.
This is NOT the first time this has happened either. I've had the phone display flicker on/off and after a couple times it will just stay on. It's also went off and I've fixed it by holding a light to the sensor in the top left and it came on. This time I'm not having any luck.
Please help! It's rooted, with custom ROM, and boot unlocked, therefore I cannot send it in for repair as warranty is voided. I've tried restoring it back to stock the best I can via mirror Android to PC program, but it's very difficult. I've restored it once before, I just don't get why it's not working again with me holding the light to the sensor. Any help and/or suggestions would be greatly aprreciated!! Thank you!

Kev_McCall said:
Ok so before I begin, I've read everything online and cannot figure this out. I've searched the forums for hours and still no luck.
I have the HTC One M7 with T-Mobile
I've had it since December with no issues at all, and still in mint condition. Never dropped.
I have it rooted, with boot unlocked
ViperOne ROM Installed, stock kernel.
Ok so Tuesday night I was going to bed (phone still on and working) and plugged my phone in to the charger to charge for the night as I usually do every night. Wake up in the morning and hit the power button to unlock the phone and to my surprise the display doesn't come on. As I said I've never dropped this phone in the entire 9 months I've had it, nor has it ever gotten wet.
This is NOT the first time this has happened either. I've had the phone display flicker on/off and after a couple times it will just stay on. It's also went off and I've fixed it by holding a light to the sensor in the top left and it came on. This time I'm not having any luck.
Please help! It's rooted, with custom ROM, and boot unlocked, therefore I cannot send it in for repair as warranty is voided. I've tried restoring it back to stock the best I can via mirror Android to PC program, but it's very difficult. I've restored it once before, I just don't get why it's not working again with me holding the light to the sensor. Any help and/or suggestions would be greatly aprreciated!! Thank you!
Click to expand...
Click to collapse
Well issues like this are common with custom roms. You would need to pull a log cat or DSM message and send it to the developers.

Kev_McCall said:
Ok so before I begin, I've read everything online and cannot figure this out. I've searched the forums for hours and still no luck.
I have the HTC One M7 with T-Mobile
I've had it since December with no issues at all, and still in mint condition. Never dropped.
I have it rooted, with boot unlocked
ViperOne ROM Installed, stock kernel.
Click to expand...
Click to collapse
If you are not S-OFF, then you will have to relock your bootloader with this command: fastboot oem lock
Then run this RUU 5.14.531.11 That will put you back at stock and if you want to put a custom rom or root you can try it again.

zelendel said:
Well issues like this are common with custom roms. You would need to pull a log cat or DSM message and send it to the developers.
Click to expand...
Click to collapse
Thanks for the reply, so how would I go about pulling log cat and DSM?

majmoz said:
If you are not S-OFF, then you will have to relock your bootloader with this command: fastboot oem lock
Then run this RUU 5.14.531.11 That will put you back at stock and if you want to put a custom rom or root you can try it again.
Click to expand...
Click to collapse
Thanks man! I've tried other RUU's with no luck. So just to be certain, in order to flash an RUU, you need S-Off wit Bootloader locked? Is it not possible to flash RUU with S-On? Going to do this now. I'll let you know. I'll keep you guys updated. Feeling good about this.

Kev_McCall said:
Thanks man! I've tried other RUU's with no luck. So just to be certain, in order to flash an RUU, you need S-Off wit Bootloader locked? No, if you S-OFF you can leave it unlocked.
Is it not possible to flash RUU with S-On? No, if S-ON you can only flash it if your bootloader is locked and the same OS version or higher.
Going to do this now. I'll let you know. I'll keep you guys updated. Feeling good about this.
Click to expand...
Click to collapse
See comments above.

majmoz said:
See comments above.
Click to expand...
Click to collapse
Ok so I succesfully Installed the RUU and back to stock rom, but upon rebooting, my screen did not turn back on. I've read of dozens of other users who have experienced this same thing. I guess the next step would be to fully return it to stock, turning S-On, removing tampered, unrooting, etc, and just returning it for another phone. @majmoz

Kev_McCall said:
Ok so I succesfully Installed the RUU and back to stock rom, but upon rebooting, my screen did not turn back on. I've read of dozens of other users who have experienced this same thing. I guess the next step would be to fully return it to stock, turning S-On, removing tampered, unrooting, etc, and just returning it for another phone. @majmoz
Click to expand...
Click to collapse
If you successfully ran the RUU, then you are stock with a relocked bootloader. The downside is you have to be S-OFF to remove the tampered and to change the "relocked" to "locked".
If you are S-OFF, then you would have to put TWRP 2.6.3.3 or 2.7.1.2 and install this Bootloader Reset Tool. Then flash a stock recovery. You are now completely back to stock.

majmoz said:
If you successfully ran the RUU, then you are stock with a relocked bootloader. The downside is you have to be S-OFF to remove the tampered and to change the "relocked" to "locked".
If you are S-OFF, then you would have to put TWRP 2.6.3.3 or 2.7.1.2 and install this Bootloader Reset Tool. Then flash a stock recovery. You are now completely back to stock.
Click to expand...
Click to collapse
Yea. I turned S-Off before I even ran the RUU. So there's one thing I'm confused about. If I'm trying to return to complete stock state, why would I install Twrp or CWM if those don't come with it? Is there any other way to do this? As I have no back-light and it's been very hard to do all that I've done so far. Screen hasn't come on, so I'm working blind here. Lucky for me I remember where most of the buttons are at and with the help of ADB, I've gotten this far. @majmoz

Kev_McCall said:
Yea. I turned S-Off before I even ran the RUU. So there's one thing I'm confused about. If I'm trying to return to complete stock state, why would I install Twrp or CWM if those don't come with it? Is there any other way to do this? As I have no back-light and it's been very hard to do all that I've done so far. Screen hasn't come on, so I'm working blind here. Lucky for me I remember where most of the buttons are at and with the help of ADB, I've gotten this far. @majmoz
Click to expand...
Click to collapse
Yes, look at nkk71 guide in my signature he has the steps in post 3 or 4. I'm away from the house so I can't post the link.

majmoz said:
Yes, look at nkk71 guide in my signature he has the steps in post 3 or 4. I'm away from the house so I can't post the link.
Click to expand...
Click to collapse
@majmoz
Hey bro thank you so much for the help so far, I really appreciate it. I just have one last problem. I've already talked with HTC and they're going to be sending me a replacement and I have to send my phone back in within 10 days but they said they would be checking for root.
So question 1. When you restore phone to stock ROM via RUU it unroots the phone correct?
Second problem. Now that I've restored the stock rom, usb debugging isn't enabled and I can re-enable it due to not being able to see the screen. So because USB Debugging is not enabled ADB is no longer recognizing it when I run "adb devices"
Because of this I can't turn bootloader, tampered, and lock stats back on. I'm really nervous sending my phone back in like this. I hate to keep bothering you, but you seem to know your stuff a lot more than I, and I'd hate to start a new thread. Thanks again bro.

Kev_McCall said:
@majmoz
So question 1. When you restore phone to stock ROM via RUU it unroots the phone correct?
Second problem. Now that I've restored the stock rom, usb debugging isn't enabled and I can re-enable it due to not being able to see the screen. So because USB Debugging is not enabled ADB is no longer recognizing it when I run "adb devices"
Because of this I can't turn bootloader, tampered, and lock stats back on. I'm really nervous sending my phone back in like this. I hate to keep bothering you, but you seem to know your stuff a lot more than I, and I'd hate to start a new thread. Thanks again bro.
Click to expand...
Click to collapse
1. RUU unroots the phone.
2. Yes, you need USB Debugging enabled and a custom recovery (nkk71 uses CWM).
I have been racking my brain all night. This is a long shot, but if HTC is sending you a replacement before you have to ship yours back then here is an idea. With the replacement phone side by side; memic the commands to open Settings on both phones doing the replacement phone first, then the old phone. The location of the items should be in the same place on both screens. It may take a couple of tries but you seem adapt at reading blank screens. I'm still researching a way to turn it on remotely, but this is the only solution I could come up with presently.
When you get USB Debugging enabled, use nkk71's guide to install CWM on your phone. Then complete the manual steps to remove "Tampered" and to "Locked" the phone. Reboot the phone into bootloader per the instructions. Now we need to put the stock recovery back on the phone. You can get the stock recovery out of the last OTA. Download it to your PC, then open the zip file. Within the zip is the firmware.zip, open it and you will see recovery.img file this is the stock recovery. Just extract it and flash it like you did the custom recovery earlier. Going back to nkk71's guide, complete the fastboot command to return to S-ON. Now you are completely stock with no hint of root.

@majmoz
I'm beast! lol Ok so quick update to my problem. So I got the bright idea to use the Power+Volume Down to take screenshots of my display as I blindly tapped and used that as a guide and moved forward to unlocking developer options, then enabling USB debugging. I can now see my device in ADB once again. Should be pretty cake from here. Thank you so much bro! And also, HTC has agreed to send me a new phone, but I must first send mine in. They would have sent me one first and then I send mine in later, but they wanted to place a $600 credit hold on my card. **** THAT. The rep told me they would be checking for other damages as well as if it rooted.

Kev_McCall said:
@majmoz
I'm beast! lol Ok so quick update to my problem. So I got the bright idea to use the Power+Volume Down to take screenshots of my display as I blindly tapped and used that as a guide and moved forward to unlocking developer options, then enabling USB debugging. I can now see my device in ADB once again. Should be pretty cake from here. Thank you so much bro! And also, HTC has agreed to send me a new phone, but I must first send mine in. They would have sent me one first and then I send mine in later, but they wanted to place a $600 credit hold on my card. **** THAT. The rep told me they would be checking for other damages as well as if it rooted.
Click to expand...
Click to collapse
You are a genius!!! I will have to remember that if this type of situation arises again.

@majmoz
Ok so I've been reading those sites and I know I'm so close to being back to 100% stock, but now I'm stuck. I'm confused as to what order to things.
I restore stock recovery, then lock bootloader, turn S-ON,and remove tampered and return to Locked status?
Here are my fastboot getvar details. Just trying to get this done as soon as possible as I'm also in the process of moving and wont have net here much longer. So as soon as I get this done I can send my phone back in and get the replacement. Really hate being without a phone.

Kev_McCall said:
@majmoz
Ok so I've been reading those sites and I know I'm so close to being back to 100% stock, but now I'm stuck. I'm confused as to what order to things.
I restore stock recovery, then lock bootloader, turn S-ON,and remove tampered and return to Locked status?
Here are my fastboot getvar details. Just trying to get this done as soon as possible as I'm also in the process of moving and wont have net here much longer. So as soon as I get this done I can send my phone back in and get the replacement. Really hate being without a phone.
Click to expand...
Click to collapse
Here I put them in your new post.

Alright cool thanks! I really shouldn't have created a new thread, but I wasn't sure if you would be on for much longer. Reading it now.

Kev_McCall said:
Alright cool thanks! I really shouldn't have created a new thread, but I wasn't sure if you would be on for much longer. Reading it now.
Click to expand...
Click to collapse
it doesn't take 5 threads to fix one problem does it ?

clsA said:
it doesn't take 5 threads to fix one problem does it ?
Click to expand...
Click to collapse
Probably not, you're right. But when other people don't respond to my initial thread it's kind of hard. I'm still stuck And just trying to get this finished up. Would you care to help? It's not much.

Kev_McCall said:
Probably not, you're right. But when other people don't respond to my initial thread it's kind of hard. I'm still stuck And just trying to get this finished up. Would you care to help? It's not much.
Click to expand...
Click to collapse
we all have other lives besides XDA .. you have to be patient
I have a few min where are you now in the recovery process ?