S-OFF for Desire 500? - HTC Desire 500

S-OFF for Desire 500? - HTC Desire 500

Is there a way of getting S-OFF for this device? I am having major problems without it...
Okay, so I'll start at the beginning. Once upon a time (two days ago), I bought a Desire 500 from ebay that was stuck at the bootloader screen. It arrived today and I have unlocked the bootloader with HTCDEV, but I cannot flash recovery with fastboot. It seems to accept the flash on my computer, but when I try to enter recovery the phone just hangs. I have tried to flash the zip with fastboot, but the error message:
FAILED (remote: not allowed)
keeps coming up. AFAIK this is because I don't have S-OFF, but I should still be able to flash recovery.
Can anyone help?
EDIT - OK, so rumrunner can S-OFF it, but you have to have a ROM installed to use it...

I don't understand....
I literally don't know what I'm doing wrong. I've even found the ROM with the correct CID and tried to flash it through fastboot and RUU mode but it's not working.
Somebody help please... I have tried searching for the answer...
EDIT - I have flashed the correct CWM for my hboot and it has hung on:
Entering Recovery...
with the white HTC screen. It has been like this for ten minutes...

rumrunner didn't s-off my dual desire500.
it's fully rooted
has cwm on it
has not busybox n i wanted to s-off my phone in order to push busybox in it.
any idea?

Dead phone
First of all in order to install the original firmware (so called stock rom) your device needs to be in locked status. Other than that :
I also wanted to s-off my phone which is also stuck both on HTC screen and when trying to enter the recovery. Many articles and threads are saying you need to enable usb debugging in phone options but if you are phone can not load the android os and the corrresponding menu, applying this setting it is not possible. Therefore you can consider your phone is nothing but a flashlight at the moment.
Regarding my searchs our phone's emmc is corrupt or needs to be reprogrammed or something like it. It is not possible to load the official firmware using RUU files or any other custom ROMs.
kiaheyrati038 said:
rumrunner didn't s-off my dual desire500.
it's fully rooted
has cwm on it
has not busybox n i wanted to s-off my phone in order to push busybox in it.
any idea?
Click to expand...
Click to collapse

Related

[Q] Help! - Bricked Incredible S, S-ON, unable to boot past HTC logo

Hi guys,
what I have:
Optus (AU) HTC Incredible S - it was running 2.3.3 fine, no hacks/root or anything has been done to it. [I've done a vol down + power button hboot thingy and it says S-ON]
what happened:
I connected the phone to a WIFI network to update my apps, it started updating many apps. mid-way through the updates, the phone became unresponsive and apparently hung, left it alone for a few hours, it remained hung.
I disconnected the power and pulled the battery.
The phone has since refused to boot past the HTC splash logo.
What I've tried:
I've tried rooting the phone with Revolutionary - however I can't complete the steps as I am unable to boot the phone.
I've tried Hboot with the [PG32IMG.zip] file - nothing seemed to change
I've tried usb fastboot with adb and fastboot - Signature verification failed [well, it is S-ON]
I've tried recovery - failed, gave me 3 arrows, 2 in a circular pattern and one straight, followed by a phone icon and a red triangle and ! mark
I've tried running the RUU.exe file for 2.3.3 optus, but it does not get past 'rebooting to bootloader'
Current situation:
I've spent around 6 hours trying to figure out what went wrong and make it work ... but nothing seems to work ... so guys ... i really could use some help ...
btw, I can't warranty it as I purchased the phone in Australia, but now am in Singapore ... I'll be returning to Australia in January though ...
All help and suggestions will be greatly appreciated ...
Thanks!

hey buddy
well , the easy way to solve your problem is to download the stock rom for your device , and install it using the offical HTC exe ( the rom exe ) .
it will do it all and get your device like brand new .
hope this solve it .

If the above doesn't work send it to any htc repair center. You have to pay but whatever.

hassanhm said:
hey buddy
well , the easy way to solve your problem is to download the stock rom for your device , and install it using the offical HTC exe ( the rom exe ) .
it will do it all and get your device like brand new .
hope this solve it .
Click to expand...
Click to collapse
Hey hassanhm,
thanks for the reply. I've tried searching the HTC official website for the stock rom, however it is not available for download due to the fact that firmware upgrades are now over the air ..
i've downloaded the RUU rom by optus (RUU_Vivo_Gingerbread_S_Optus_AU_2.12.980.2_R_Radio _20.2803.30.085AU_3805.04.03.12_M_release_185028_s igned
http://www.filefactory.com/file/cfdd...028_signed.exe) found here - http://forum.xda-developers.com/showthread.php?t=1033922 - however it just gets stuck on the booting to bootloader step ...
if there a different stock rom exe file i should be using?
Thanks!

I'm a singaporean. Its uncommon to see this kinda stuff :/

looks like dead motherboard i saw thing like that already

I'm from Singapore. I had this issue, spent a day flashing and rebooting to try and fix it. Then I have up and just flashed an official ROM, I think any one will do, then sent it to HTC. It was still s-off but they didn't care. Took just 3 days and they sent it back, fixed and like brand new. I suggest you don't waste time and just sent to HTC. it will come back s-on but you can just root it again.
Hope this helps!
Sent from my HTC Incredible S using XDA App

There's one but when they put latest Hboot (1.16.0000)then it's harder to flash ROM than 1.13.0000. Hope you get your phone back and it's working

expiredyoghurt said:
Hi guys,
what I have:
Optus (AU) HTC Incredible S - it was running 2.3.3 fine, no hacks/root or anything has been done to it. [I've done a vol down + power button hboot thingy and it says S-ON]
what happened:
I connected the phone to a WIFI network to update my apps, it started updating many apps. mid-way through the updates, the phone became unresponsive and apparently hung, left it alone for a few hours, it remained hung.
I disconnected the power and pulled the battery.
The phone has since refused to boot past the HTC splash logo.
Click to expand...
Click to collapse
You must be able to revive, since you did not do anything related to s-off, rooting etc. rooting, s-offing are for modding addict fellow
[/QUOTE]
What I've tried:
I've tried rooting the phone with Revolutionary - however I can't complete the steps as I am unable to boot the phone.
[/QUOTE]
Revolutionary only work on phone with NORMAL BOOTING (Android booting). If you did on fastboot then (I Think) you start create big trouble
I've tried Hboot with the [PG32IMG.zip] file - nothing seemed to change
Click to expand...
Click to collapse
This will only work for UPDATE, mean you must use higher version of ROM than in the phone (if you are s-on) -CMIIW-
I've tried usb fastboot with adb and fastboot - Signature verification failed [well, it is S-ON]
I've tried recovery - failed, gave me 3 arrows, 2 in a circular pattern and one straight, followed by a phone icon and a red triangle and ! mark
I've tried running the RUU.exe file for 2.3.3 optus, but it does not get past 'rebooting to bootloader'
Current situation:
I've spent around 6 hours trying to figure out what went wrong and make it work ... but nothing seems to work ... so guys ... i really could use some help ...
Click to expand...
Click to collapse
can you post your mainver : FYI, I could NOT resolve my vivo since my situation is worse than you, but probably my experience with unsuccesfull result will give different output ... who knows.
on fastboot (I'm sure You know how to do) fastboot getvar all (windows command) and post the output for our analysing together and help each other.
btw, I can't warranty it as I purchased the phone in Australia, but now am in Singapore ... I'll be returning to Australia in January though ...
All help and suggestions will be greatly appreciated ...
Thanks!
Click to expand...
Click to collapse
You will loss a big FUN on your life !!! by choosing easy way.

i have the same problem with a unit of incredible s. will not continue booting up past the htc logo.
Is this a software problem? cause im thinking maybe its the motherboard.

ice_pick88 said:
i have the same problem with a unit of incredible s. will not continue booting up past the htc logo.
Is this a software problem? cause im thinking maybe its the motherboard
Click to expand...
Click to collapse
.
what did you do before stuck. Can you boot into bootloader (?) are you S-ON or S-OFF (?) what is Hboot version do you have. To have bootloader state : press power and volume down button SIMULTANEOUSLY if within TEN MINUTES you do not have bootloader status you should stop and let us know here

Thanks for the reply. Its S-On, Hboot 1.13, I was simply browsing using the phone when it restarted and stuck with the htc logo.

ice_pick88 said:
Thanks for the reply. Its S-On, Hboot 1.13, I was simply browsing using the phone when it restarted and stuck with the htc logo.
Click to expand...
Click to collapse
I'm wondering. You probably did not enable fastboot option > setting > power > UNTHICK fastboot item.
On your today phone state you can not do it. Do you remember ? you enable fastboot option or not. Presumed you enable fastboot option then you can go to bootloader by pressing power and volume down buttons simultaneously > once you come into bootloader there is an option FACTORY RESET. If you see RED TRIANGLE. No other choice (AFAIK) you need to download the RUU of your phone and just run RUU ... all your personal user data will be wiped.

x1123 said:
I'm wondering. You probably did not enable fastboot option > setting > power > UNTHICK fastboot item.
On your today phone state you can not do it. Do you remember ? you enable fastboot option or not. Presumed you enable fastboot option then you can go to bootloader by pressing power and volume down buttons simultaneously > once you come into bootloader there is an option FACTORY RESET. If you see RED TRIANGLE. No other choice (AFAIK) you need to download the RUU of your phone and just run RUU ... all your personal user data will be wiped.
Click to expand...
Click to collapse
Thanks again for the reply. when i choose the factory reset the phone hangs but when i select recovery it goes to the red triangle logo. Where and how can i know whats RUU of my phone? Sorry im literally a noob.

3 days ago, i was having the same problen but i could solve it
Here what you can do:
1. Eject your sd card and insert another android phone. You can create a gold card over another android phone (Making gold card is completely independent from android version or phone model. Trust me.). You can search the forum, there are a lot of guides for making a gold card.
2. Boot into fastboot, plug your usb cable. Open a windows console, and send that command:
Fastboot getvar mainver
It will tell you your mainver.
3. Go here: http://forum.xda-developers.co m/showthread.php?t=1359555 .
In there, you can find original rom list. Choose one which has higher mainver than yours then download it. The thread also explains how to install the original rom.
Hth.
-R

programci_84 said:
3 days ago, i was having the same problen but i could solve it
Here what you can do:
1. Eject your sd card and insert another android phone. You can create a gold card over another android phone (Making gold card is completely independent from android version or phone model. Trust me.). You can search the forum, there are a lot of guides for making a gold card.
2. Boot into fastboot, plug your usb cable. Open a windows console, and send that command:
Fastboot getvar mainver
It will tell you your mainver.
3. Go here: http://forum.xda-developers.co m/showthread.php?t=1359555 .
In there, you can find original rom list. Choose one which has higher mainver than yours then download it. The thread also explains how to install the original rom.
Hth.
-R
Click to expand...
Click to collapse
Just for additional info. If you can not find another android/windows phone to get sdcard CID (you have only one phone and now in trouble). You can use any laptop with Built In card reader at PCI slot and NOT USB STORAGE if you were not have BOTH ... it's time to ask help your neighbour or your friends

Unlock bootloader through htcdev.com (phone doesn't have to boot normally to do this and it remains S-ON)
Flash clockwork recovery
Do arhd wipe
Flash any rom you want
flash the boot.img of that rom
there done

fallenwout said:
Unlock bootloader through htcdev.com (phone doesn't have to boot normally to do this and it remains S-ON)
Flash clockwork recovery
Do arhd wipe
Flash any rom you want
flash the boot.img of that rom
there done
Click to expand...
Click to collapse
Good day,
Thanks for the replies. Im having problem with this step. Im doing the unlocking the bootloader of the phone but when im in the process of inputting the cmd command "fastboot oem get_identifier_token" it gets me the " <waiting for device>
I have installed the latest htc sync version and updated all the drivers but it looks like my pc doesnt detect the incredible s.
Need suggestion guys.
Ill try the Gold card step later maybe it will work.
Thanks again.

[Solved] Stuck on white hboot screen while downgrading

Hi,
I had unlocked boot loader through HTCdev on latest GB stock ROM. So, obviously I was S-ON.
Meanwhile, I tried many ROMs but manually flashing boot image in hastboot.
I had following status of last running mobile when I tried to get S-OFF
Bootloader status: unlocked
S-ON
HBOOT 2.00.0000
Recovery: CWM
ROM: CynovivoX (JB 4.1.2)
Yesterday, I tried to get S-off by downgrading as per following thread
http://forum.xda-developers.com/showthread.php?t=1705913
There were lots of error while script was running, but one I remember was related to goldcard.
While running RUU, It goes well till I find something Error 131, Customer ID related and than exit.
After trying script and RUU many times, my status is
Bootloader status: Relocked
S-ON
HBOOT 2.00.0000
Recovery: ? (can't see or access anymore)
ROM: -
when running fastboot devices, my device is appearing
but in adb devices, nothing there
So, is there still any possibility to recover from this bricked state?
Desperately looking for expert help as I am not developer but somehow....tried this thinking would not be that difficult business....so help.

Try running the latest RUU and restarting everything over. Make sure to pick the right RUU for your region. The latest build number should be 4.14.XXXXX...
Also, in fastboot, your device isn't supposed to be visible with command of adb devices.
Another thing u could try is to unlock the bootloader again and see if u can access recovery again. Adb works in recovery
Sent from the head of the Hammer

If you can get into fastboot but don't have a recovery installed, can't you just flash a new recovery? E.g. grab clockworkmod, connect your phone to your computer via usb and:
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-vivo.img
(obviously replace above code with actual name of .img file)

err this might be stupid, but click on bootloader > recovery.
Looks like you are already in a sub menu when you boot the bootloader.
The error while downgrading is related to you not relocking your phone before downgrading. Always relock before downgrading with an RUU.
Sent from my Nexus 5

Thanks all guys.
But problem fixed. I have unlocked the bootloader again through htcdev and it worked.
Now let me share issue for all other nondevelopers like me who may also face such issue...
runme script is suppose to push some files through adb commands and then reboot to fastboot mode to lock bootloader.
I had adb drivers installed as I got prompt from statusbar.
However still, while running downgrade script (runme), phone was not detected in adb mode and hence no file was pushed to phone. After reboot, phone detected in fastboot and OEM successfully relocked.
I am really surprised why device not found error not appeared and script not stopped. Later I came to know this by running the script without connecting phone and it ran with asking Q&A with found device, and also reading log file.
Then I ran RUU who wiped everything.
So, my device left without any ROM and with OEM locked. I can't access or install recover, ROM etc and RUU was having goldcard error.
Somehow tried to unlock again through token provided by HTCDev earlier (around 2 years back).
And thing become normal and in my control.
My advise: always check "adb devices" before running the script as I found script is misleading of found device and finally locking device. And if such thing happen, easiest one is to get in unlocked from HTCDev and restart whole process.

RmatriX1218 said:
Thanks all guys.
But problem fixed. I have unlocked the bootloader again through htcdev and it worked.
Now let me share issue for all other nondevelopers like me who may also face such issue...
runme script is suppose to push some files through adb commands and then reboot to fastboot mode to lock bootloader.
I had adb drivers installed as I got prompt from statusbar.
However still, while running downgrade script (runme), phone was not detected in adb mode and hence no file was pushed to phone. After reboot, phone detected in fastboot and OEM successfully relocked.
I am really surprised why device not found error not appeared and script not stopped. Later I came to know this by running the script without connecting phone and it ran with asking Q&A with found device, and also reading log file.
Then I ran RUU who wiped everything.
So, my device left without any ROM and with OEM locked. I can't access or install recover, ROM etc and RUU was having goldcard error.
Somehow tried to unlock again through token provided by HTCDev earlier (around 2 years back).
And thing become normal and in my control.
My advise: always check "adb devices" before running the script as I found script is misleading of found device and finally locking device. And if such thing happen, easiest one is to get in unlocked from HTCDev and restart whole process.
Click to expand...
Click to collapse
From what I'm reading, I'm getting a much clearer image of what happened. I believe your problem to be just driver errors...
The script itself is supposed to run regardless of whether phone is properly connected with proper drivers and whatnot. After all, it's just a set of commands in cmd.
But seeing as you ONLY got Error 131, you could have solved this by simply creating a goldcard.

072665995 said:
From what I'm reading, I'm getting a much clearer image of what happened. I believe your problem to be just driver errors...
The script itself is supposed to run regardless of whether phone is properly connected with proper drivers and whatnot. After all, it's just a set of commands in cmd.
But seeing as you ONLY got Error 131, you could have solved this by simply creating a goldcard.
Click to expand...
Click to collapse
Phone was connected in adb mode. This I can say by checking notifications in android and statusbar prompt in windows 7. While running script only, something got wrong getting adb mode not detected.
Anyway, Goldcard was also in my next line of action, but not sure even after creating Goldcard, I may stuck as version-main was not downgraded to 2. However, tried and got resolved with much simpler effort of unlocking through htcdev.
May be, I am also not that competent to understand developing world and only good enough to simply flash ROMs and updates as per instructions.
Anyway, thanks.

One S - Stuck In Loop After Maximus HD Install

I browsed a few other threads, and tried to update the recovery with the latest version per the advice of a member, and prior to this, it was just stuck at the green HTC screen with the red disclaimer under it. And after flashing the newest recovery TWRP it has begun to loop.
I also cannot boot into recovery now. Only fastboot is working,.
Phone info is:
***UNLOCKED****
VLE PVT SHIP S-OFF RL
CID - 11111111
HBOOT- 1.14.0005
RADIO - 1.13.50.05.25
OPENDSP-V29.1.0.45.0622
EMMC-BOOT
NOV 21, 2012, 12:17:41
I believe everything is set for the Maximus ROM to work, but if I am missing something I would appreciate the feedback and help.
Thanks
Tancred

Tancred213 said:
I browsed a few other threads, and tried to update the recovery with the latest version per the advice of a member, and prior to this, it was just stuck at the green HTC screen with the red disclaimer under it. And after flashing the newest recovery TWRP it has begun to loop.
I also cannot boot into recovery now. Only fastboot is working,.
Phone info is:
***UNLOCKED****
VLE PVT SHIP S-OFF RL
CID - 11111111
HBOOT- 1.14.0005
RADIO - 1.13.50.05.25
OPENDSP-V29.1.0.45.0622
EMMC-BOOT
NOV 21, 2012, 12:17:41
I believe everything is set for the Maximus ROM to work, but if I am missing something I would appreciate the feedback and help.
Thanks
Tancred
Click to expand...
Click to collapse
This is HTC ONE forum not ONE S , you can try with RUU.exe while you're in bootloader or " fastboot oem rebootRUU "

Vixa said:
This is HTC ONE forum not ONE S , you can try with RUU.exe while you're in bootloader or " fastboot oem rebootRUU "
Click to expand...
Click to collapse
My bad, I was following posts about this ROM and assumed they were discussing the same phone. But it appears that there isn't a S thread, only an X for this model..
This takes me to a silver HTC logo and hangs there... I have fastboot access, but i cant get ADB to talk to the phone. But with fastboot I can push a new recovery img but still not allowing me into any recovery.

If you cant get into recovery donwload a RUU and get your phone flashed with it from FASTBOOT.

Vixa said:
If you cant get into recovery donwload a RUU and get your phone flashed with it from FASTBOOT.
Click to expand...
Click to collapse
Able to get into Philz recovery and adb sideload zips, but it cant find my sdcard...what a headache this is turning into, and no closer to knowing what the problem was / is.

Tell me can you mount system or get in twrp or something to hold on?
Sent from my HTC One using Tapatalk

Vixa said:
Tell me can you mount system or get in twrp or something to hold on?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Changed TWRP to CWM which is at least allowing me into recovery mode.
Thinking I will have to transfer the files with another android phone onto the memory and try to install the rom again?
Mounting USB fails, it just makes a sound like I have added a drive to my PC non stop every few seconds, and I cant mount anything. formatted it and it seems to have settled it a bit. But I cant do anything with the storage via USB in Windows. Just updated to the latest clockwork for my model and still no success...
With latest version I cant even sideload at the moment.

Tancred213 said:
Changed TWRP to CWM which is at least allowing me into recovery mode.
Thinking I will have to transfer the files with another android phone onto the memory and try to install the rom again?
Mounting USB fails, it just makes a sound like I have added a drive to my PC non stop every few seconds, and I cant mount anything. formatted it and it seems to have settled it a bit. But I cant do anything with the storage via USB in Windows. Just updated to the latest clockwork for my model and still no success...
With latest version I cant even sideload at the moment.
Click to expand...
Click to collapse
Ok, sorted that out, apparently the drivers were having issues, and when I manually picked them I became able to communicate with the phone again like normal. This is like hour 8 of the upgrade so far...
Assuming my firmware is also outdated, and from my searching I havent found an easy way to update my hboot and others without flashing a RUU Rom from T-Mobile, any alternatives to doing that?

Pretty sure I killed it. Downloaded the latest RUU from T-Mobile, after relocking the bootloader and turning S-on, it ran fine, completed, rebooted the phone and now its totally dead. No charge light, doesnt turn on at all. And I was just thinking to myself how hard it is to brick a phone since I have yet to kill one with all of my misadventures....oops. We'll see what happens..

Had you read the HTC One S forum, you would have found out that this particular phone can get hard bricked up S-OFF with SuperCID and then a RUU update is ran.

[Q] Bootloop, ADB Sideload Failed, Wipe Failed

Seeking some help here.
I am from Singapore and using the HTC international version.
It is (was?) rooted but the camera was giving problems and I sent it in for servicing. Even though the hardware fault has nothing to do with the rooting, I was asked to unroot it into stock and they will service it for me.
Ok, fair enough. So this is what I did.
1. I relocked the bootloader using Fastboot
2. Tried to run the RUU which and it didn't run. I used
RUU_M7_UL_JB_50_hTC_Asia_WWE_1.26.707.5_Radio_4A.13.3231.20_10.30.1131.05_release_309365_signed_2_4.exe
3. Realised that I need to turn S-off before the RUU may work, I tried running the Rumrunner but couldn't get it to work.
4. Rumrunner says I need to check USBdebugging but since I couldn't get the phone running, I couldn't have checked that.
5. I decided to just unlock the bootloader and install a custom rom (was using CM11). Tried to push the Zip by ADB but it fails. The computer recognises the device but after pushing the file, the TWRP screen reads ADB Sideload Complete Failed
6. Possibly unrelated, but I tried to do a wipe on TWRP, it reads Factory Reset Complete Failed
So now I can stuck with a bootloop and can't seem to get anything installed or restored.
Would love to know what should I do in such a situation. Thanks guys.

HTC Desire 510 can't do anything with it. Stuck

So here's the story... this is an HTC Desire 510 purchased from Telus here in Canada. I've been messing around with different kernels, ROMs, etc. None of them really worked well for me, so I decided to go back to stock, unlock and try to sell it. Now I'm stuck at the bootloader and I can't figure out what to do. I tried to re-lock the bootloader so I could flash the stock ROM (those were the instructions I read)...
Whenever it boots, it gets to the recovery screen. ("Fastboot USB" / HBOOT) it says *Tampered* and *Relocked* at the top.
Then, when I try to unlock it with Unlock_code.bin (I have tried every method available), and say "Yes", I get the Fastboot USB screen with an overlay that says - at the top: Entering Recovery...
at the bottom it says: This build is for development purposes only, etc.
Then it just stays there until I remove the USB cable and the battery.
I reboot and I get the same thing every time.
Is there any way to fix this? I've tried many an adb command with no avail. I'm ready to throw this thing into the river.

cjmitchell said:
So here's the story... this is an HTC Desire 510 purchased from Telus here in Canada. I've been messing around with different kernels, ROMs, etc. None of them really worked well for me, so I decided to go back to stock, unlock and try to sell it. Now I'm stuck at the bootloader and I can't figure out what to do. I tried to re-lock the bootloader so I could flash the stock ROM (those were the instructions I read)...
Whenever it boots, it gets to the recovery screen. ("Fastboot USB" / HBOOT) it says *Tampered* and *Relocked* at the top.
Then, when I try to unlock it with Unlock_code.bin (I have tried every method available), and say "Yes", I get the Fastboot USB screen with an overlay that says - at the top: Entering Recovery...
at the bottom it says: This build is for development purposes only, etc.
Then it just stays there until I remove the USB cable and the battery.
I reboot and I get the same thing every time.
Is there any way to fix this? I've tried many an adb command with no avail. I'm ready to throw this thing into the river.
Click to expand...
Click to collapse
Is it 64 bit or 32 bit? And what type of recovery did you have on it before?

MrMike2182 said:
Is it 64 bit or 32 bit? And what type of recovery did you have on it before?
Click to expand...
Click to collapse
It's 32 bit and it had TWRP.

cjmitchell said:
It's 32 bit and it had TWRP.
Click to expand...
Click to collapse
What you need to do first of all is find an RUU for your device and then find the original recovery, not the twrp recovery but the actual recovery that was on the phone when you first got it. If you don't flash the original recovery then the RUU will refuse to continue and that's basically HTC's way of trying to prevent us from breaking the phone.. The unlock code you got from HTC you should have kept and whenever you sell the phone pass it along to the new owner.. So to help you understand everything I said first unlock your bootloader again and then flash the original recovery and then lock the bootloader again then run the RUU on the PC.. Some times you have to run the RUU a few times to finally get it to finish completely cause some times it'll hang and just sit there so just end the process and restart it but before ending it be sure you gave it enough time to try before thinking it's stuck because it may not be... After the RUU finishes, the phone will totally be stock again the same way it was the day you bought it..

MrMike2182 said:
What you need to do first of all is find an RUU for your device and then find the original recovery, not the twrp recovery but the actual recovery that was on the phone when you first got it. If you don't flash the original recovery then the RUU will refuse to continue and that's basically HTC's way of trying to prevent us from breaking the phone.. The unlock code you got from HTC you should have kept and whenever you sell the phone pass it along to the new owner.. So to help you understand everything I said first unlock your bootloader again and then flash the original recovery and then lock the bootloader again then run the RUU on the PC.. Some times you have to run the RUU a few times to finally get it to finish completely cause some times it'll hang and just sit there so just end the process and restart it but before ending it be sure you gave it enough time to try before thinking it's stuck because it may not be... After the RUU finishes, the phone will totally be stock again the same way it was the day you bought it..
Click to expand...
Click to collapse
HTC or Telus don't provide a RUU for the Telus version of the phone so I've been trying the Cricket version, doesn't work. It gives me the message: ERROR [131]: CUSTOMER ID ERROR.
There is some russian website that seems to have it for Telus, but you have to pay to access it, and I don't even know if it's what I need. ir-file.com (I can't post links)
So I'm not going down that rabbit hole.
I can't flash any recovery I find...
"fastboot getvar platform" gives me hTCBmsm2886
"fastboot flash recovery (*.img)" gives me a message saying FAILED (remote: signature verify fail) for every single recovery image I can find. Nothing works.

cjmitchell said:
HTC or Telus don't provide a RUU for the Telus version of the phone so I've been trying the Cricket version, doesn't work. It gives me the message: ERROR [131]: CUSTOMER ID ERROR.
There is some russian website that seems to have it for Telus, but you have to pay to access it, and I don't even know if it's what I need. ir-file.com (I can't post links)
So I'm not going down that rabbit hole.
I can't flash any recovery I find...
"fastboot getvar platform" gives me hTCBmsm2886
"fastboot flash recovery (*.img)" gives me a message saying FAILED (remote: signature verify fail) for every single recovery image I can find. Nothing works.
Click to expand...
Click to collapse
Did you try to reflash twrp? If I was in your predicament I'd flash twrp and then there is a rom that I configured to work great on the 32 bit phones it's the Modded CM11 and I'm pretty sure it'll work on yours albeit the cameras aren't working yet at least it's a start and you can find the CM11 I configured here ----> Modded CM11

MrMike2182 said:
Did you try to reflash twrp? If I was in your predicament I'd flash twrp and then there is a rom that I configured to work great on the 32 bit phones it's the Modded CM11 and I'm pretty sure it'll work on yours albeit the cameras aren't working yet at least it's a start and you can find the CM11 I configured here ----> Modded CM11
Click to expand...
Click to collapse
Yeah, I tried to reflash TWRP, I get that message "FAILED: (remote: signature verify fail)"
That is after I type in the C:\adb\ folder "fastboot flash recovery twrp-2.8.7.0-a11.img"
and every other recovery image I can find, including older versions of TWRP.
This is why I'm frustrated, nothing works. If I could flash a ROM that'd be cool, but I can't get out of the bootloader, I can't even get into recovery.

cjmitchell said:
Yeah, I tried to reflash TWRP, I get that message "FAILED: (remote: signature verify fail)"
That is after I type in the C:\adb\ folder "fastboot flash recovery twrp-2.8.7.0-a11.img"
and every other recovery image I can find, including older versions of TWRP.
This is why I'm frustrated, nothing works. If I could flash a ROM that'd be cool, but I can't get out of the bootloader, I can't even get into recovery.
Click to expand...
Click to collapse
I need you to type everything you see on your HBoot screen when you pull the battery and put it back in and then hold the volume down button and then press the power button at the same time and when the screen comes up type everything you see in here so I can see it... I think the reason you're getting the remote signature failure is because the bootloader is still locked and you have to make sure it really is unlocked.. Try that then get back to me.

Yeah, the bootloader is still locked. here's what it says:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
A11_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.101.1372.19.1121
OpenDSP-v28.2.2.00546.0331
OS-
eMMC-boot 1024MB
Aug 19 2015,21:13:29.0
Then the regular menu.
I can't seem to unlock the bootloader.

cjmitchell said:
Yeah, the bootloader is still locked. here's what it says:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
A11_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.101.1372.19.1121
OpenDSP-v28.2.2.00546.0331
OS-
eMMC-boot 1024MB
Aug 19 2015,21:13:29.0
Then the regular menu.
I can't seem to unlock the bootloader.
Click to expand...
Click to collapse
Well if you had the boot unlocked before, why can't you send the unlock_code.bin to it and have it unlock again? Or did you lose the key? Because you're supposed to keep that key.. Did you use some sort of program to try and root the phone? Like them 1 click root apps...
---------- Post added at 06:44 PM ---------- Previous post was at 06:40 PM ----------
Go download this to a computer/laptop whatever and connect the phone to it and try to run this RUU on the PC while the phone is connected to it and turned on in HBoot/fastboot... Do this before trying to unlock the boot again and if it hangs try it again because some times it can take 3 or 4 tries to get it to work... Download Cricket RUU - http://dl3.htc.com/application/RUU_A11_UL_K44_DESIRE_SENSE60_AIO_Aio_Wireless_US_1.11.506.8.exe
Edit: I know you said your carrier is Telus and I know that's a Cricket RUU that I listed, but they are both the same so run it!!
Edit again: Never mind don't bother running the RUU because you're not s-off and you can't change your CID so I suggest you find a way to unlock your bootloader again somehow and then flash the CM11 to test out.

MrMike2182 said:
Well if you had the boot unlocked before, why can't you send the unlock_code.bin to it and have it unlock again? Or did you lose the key? Because you're supposed to keep that key.. Did you use some sort of program to try and root the phone? Like them 1 click root apps...
---------- Post added at 06:44 PM ---------- Previous post was at 06:40 PM ----------
Go download this to a computer/laptop whatever and connect the phone to it and try to run this RUU on the PC while the phone is connected to it and turned on in HBoot/fastboot... Do this before trying to unlock the boot again and if it hangs try it again because some times it can take 3 or 4 tries to get it to work... Download Cricket RUU - http://dl3.htc.com/application/RUU_A11_UL_K44_DESIRE_SENSE60_AIO_Aio_Wireless_US_1.11.506.8.exe
Edit: I know you said your carrier is Telus and I know that's a Cricket RUU that I listed, but they are both the same so run it!!
Edit again: Never mind don't bother running the RUU because you're not s-off and you can't change your CID so I suggest you find a way to unlock your bootloader again somehow and then flash the CM11 to test out.
Click to expand...
Click to collapse
I have the unlock_code.bin, I've been trying to send it to the phone but it doesn't work. I've tried the WinDroid app and the command line "fastboot flash unlocktoken unlock_code.bin" and I get to the screen that asks if I want to unlock the bootloader, but when I select "Yes" it hangs and sticks on that screen, but at the top it says: "Entering Recovery..." and at the bottom it says "This build is for development purposes only", etc.
If I can't flash anything then I'm guessing it's perma-bricked... :/

cjmitchell said:
I have the unlock_code.bin, I've been trying to send it to the phone but it doesn't work. I've tried the WinDroid app and the command line "fastboot flash unlocktoken unlock_code.bin" and I get to the screen that asks if I want to unlock the bootloader, but when I select "Yes" it hangs and sticks on that screen, but at the top it says: "Entering Recovery..." and at the bottom it says "This build is for development purposes only", etc.
If I can't flash anything then I'm guessing it's perma-bricked... :/
Click to expand...
Click to collapse
Right it hung there because there was no recovery flashed so right after you unlock that no matter what just flash twrp to it the second after you tap yes to unlock the bootloader send the recovery to it.

MrMike2182 said:
Right it hung there because there was no recovery flashed so right after you unlock that no matter what just flash twrp to it the second after you tap yes to unlock the bootloader send the recovery to it.
Click to expand...
Click to collapse
as soon as I hit the "Yes" option on the "Unlock bootloader?" screen, it tries to go into recovery. And it's instant. There is no window where I can flash the recovery - I've tried it multiple times.
So I can't unlock it and I can't flash a recovery.
I'm afraid this thing is done for...

cjmitchell said:
as soon as I hit the "Yes" option on the "Unlock bootloader?" screen, it tries to go into recovery. And it's instant. There is no window where I can flash the recovery - I've tried it multiple times.
So I can't unlock it and I can't flash a recovery.
I'm afraid this thing is done for...
Click to expand...
Click to collapse
You are supposed to be unlocking it from a PC and flashing the recovery from the PC also not trying to flash the recovery from the phone you cant do that unless the phones working.. Don't you have minimal ADB and Fastboot installed on a Windows PC?

Database Develop

welcome