Database Develop

HTC ONE stuck on Bootloader screen HELP PLEASE!!!!!

Im really frinking out my phone is stuck on Bootloader screen i root everything was good and for some stupid reason i decided to updated it to 4.3 and after i run it and it restart i just keep going back to bootloader screen try recovery but it will just got back to same screen when you plug into the computer it does detect ti just fine but i don't know what to do this is what is on my screen. i try RUU but is say i have the wrong version (31.1)
and the phone is like completely wipe out. some HELP ME PLEASE , I don't have insurance nor warranty and the phone is like 1 month old
Sprint HTC one
***tampered***
***Relocked***
M7_WIL PVT SHI P S-ON RH
HBOOT-1.44.0000
OpenDSP-v31.120.274.0617
eMMC-boot

Please help. Im in the same situtation
Same thing happened to me. PLS HELP
My phone is bricked and is stuck in a bootloop. When trying to unroot my device to get the new 4.3 update on my Sprint HTC One something went bad. I went to the twrp recovery and I accidentally swiped the system data. I’ve tried running the Sprint_HTC_One_m7wls_1.29.651.7_RUU but I get
Error: 140-------- S-ON is the problem is my guess
I also tried adb sideload, but whenever I try that the sideload gets stuck on 1%
Then tried flashing a stock ROM using USB-OTG in TWRP Sprint_HTC_One_1.31.651.2_Stock, it’ll come up with an unable to mount error. But I reformatted my flashdrive and it was able to actually flash the ROM, but the ROM just goes into a bootloop again.
Anything would be much obliged!!!!

I got mine fixed!!!
Followed Indirect's forum http://forum.xda-developers.com/showthread.php?t=2390821. Much love and thanks Indirect

blacky305 said:
Same thing happened to me. PLS HELP
My phone is bricked and is stuck in a bootloop. When trying to unroot my device to get the new 4.3 update on my Sprint HTC One something went bad. I went to the twrp recovery and I accidentally swiped the system data. I’ve tried running the Sprint_HTC_One_m7wls_1.29.651.7_RUU but I get
Error: 140-------- S-ON is the problem is my guess
I also tried adb sideload, but whenever I try that the sideload gets stuck on 1%
Then tried flashing a stock ROM using USB-OTG in TWRP Sprint_HTC_One_1.31.651.2_Stock, it’ll come up with an unable to mount error. But I reformatted my flashdrive and it was able to actually flash the ROM, but the ROM just goes into a bootloop again.
Anything would be much obliged!!!!
Click to expand...
Click to collapse
How did you resolve this, I am in the same boat.
when trying to ADB any image I get a signature verify fail error.
So far I haven't been able to send any image without getting that error.
I would be greatful for any help!

blacky305 said:
Followed Indirect's forum http://forum.xda-developers.com/showthread.php?t=2390821. Much love and thanks Indirect
Click to expand...
Click to collapse
i went there but tells me that i need to use ADB to do this
adb shell
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
adb reboot bootloader
fastboot oem lock
but i cant use ADB because it wont find my device and is probably bc debugging is not enable bu o cant enable it bc i can get out of bootloader is there a way e enable debugging from the bootloader??

Cubanflow2992 said:
i went there but tells me that i need to use ADB to do this
adb shell
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
adb reboot bootloader
fastboot oem lock
but i cant use ADB because it wont find my device and is probably bc debugging is not enable bu o cant enable it bc i can get out of bootloader is there a way e enable debugging from the bootloader??
Click to expand...
Click to collapse
in the same boat...

For me, it wouldn't find my device either for step 3"adb reboot bootloader", so I just rebooted through Twrp on phone. I'll explain my process a bit more below.
Cubanflow2992 said:
but i cant use ADB because it wont find my device and is probably bc debugging is not enable bu o cant enable it bc i can get out of bootloader is there a way e enable debugging from the bootloader??
Click to expand...
Click to collapse
When you restart your phone, like you would regularly, when it goes to a black screen you can use the top notification pull down thing to get into settings where you might me able to change the debugging.
---------- Post added at 03:46 AM ---------- Previous post was at 03:18 AM ----------
khigdon1 said:
How did you resolve this, I am in the same boat.
when trying to ADB any image I get a signature verify fail error.
So far I haven't been able to send any image without getting that error.
I would be greatful for any help!
Click to expand...
Click to collapse
I did a **** load of stuff to try to fix it, even let my roommate go at it for a day. Numerous things were done beforehand but I would often get the same error. The thing that did the trick was following Indirect's forum.
I had my phone unlocked, went in to recovery, the first two adb commands did some stuff. The third command I received an error however recognizing the command, I just rebooted the phone through the TWRP menu. I then went into fastboot where I relocked the phone. After locking the phone I ran Sprint_HTC_One_m7wls_1.29.651.7_RUU and my phone was fixed. Hopes this helps

Did you guy type exit after the echo command?

bigdaddy619 said:
Did you guy type exit after the echo command?
Click to expand...
Click to collapse
I closed out the window after the echo command. I later reopened a new command window to lock the phone in fastboot

blacky305 said:
For me, it wouldn't find my device either for step 3"adb reboot bootloader", so I just rebooted through Twrp on phone. I'll explain my process a bit more below.
When you restart your phone, like you would regularly, when it goes to a black screen you can use the top notification pull down thing to get into settings where you might me able to change the debugging.
is never goes to back screen when i turn my phone on like i would regularly it goes to the bootloader screen i select recovery and i goes to the TWRP ... i just bot a OTG USB cable and i place the custome rom the usb and plug ti into my phone but i will not load it
Click to expand...
Click to collapse

Otg cable must be a powered one.
Sent from my HTCONE using XDA Premium 4 mobile app

mrlakadaddy said:
Otg cable must be a powered one.
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i got this one
eForCity Micro USB OTG to USB 2.0 Adapter compatible with Samsung© Galaxy S III / S3

HTC ONE stuck in bootloader

Ok I tried everything I possibly could before posting for help. I installed SD v11.2 Ultimate and after installing I rebooted and my HTC One went into bootloader and its stuck there. I cant even get into recovery when I try it just goes back into bootloader. The only thing I have acces to is fastboot. ADB does not even work. I have tried factory reset and it does not work. I have tried reinstalling my recovery but I cant get past (remote access not allwed). Any time I use fast boot I get the remote access not allowed error, and every time I use the fastboot oem flash I get a (remote 32 header error).
I tired to flash a Sprint RUU and I get a Failed (remote:32 Header error). I have tried everything possible and nothing. Please help.
One thing I did notice on getvar all,is (version baseband is N/A)
My HTC One is
S-OFF
Super Cid
Rooted

Hmmm. So I saw that the ROM has Sprint support so my assumption is that while flashing it you chose the wrong phone model, not Sprint. This causes the partitions to go corrupt. You must use a RUU, follow this guide follow this guide http://forum.xda-developers.com/showthread.php?t=2460013 BUT instead of flashing the ruu posted there you need the latest ruu (cause you are on 4.3) http://forum.xda-developers.com/showthread.php?t=2508907
And BTW you should definitely get your CID back, it would have saved your ass from flashing the wrong model. SuperCID is used only in GSM variants to get faster updated, in our case it's useless
Sent from my HTCONE using Tapatalk

No luch...
elvisypi said:
Hmmm. So I saw that the ROM has Sprint support so my assumption is that while flashing it you chose the wrong phone model, not Sprint. This causes the partitions to go corrupt. You must use a RUU, follow this guide follow this guide http://forum.xda-developers.com/showthread.php?t=2460013 BUT instead of flashing the ruu posted there you need the latest ruu (cause you are on 4.3) http://forum.xda-developers.com/showthread.php?t=2508907
And BTW you should definitely get your CID back, it would have saved your ass from flashing the wrong model. SuperCID is used only in GSM variants to get faster updated, in our case it's useless
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Thanks for all your help elvisypi, I tried the above and nothing works. I cant seem to get my phone bootloader unlocked again, when I try I cant get passed remote access not allowed. I tried to flash OEM the RUU you tole me and I still get the remote 32 header error.
Is there a way to completly wipe out the phone and reinstall fresh?

arc209 said:
Thanks for all your help elvisypi, I tried the above and nothing works. I cant seem to get my phone bootloader unlocked again, when I try I cant get passed remote access not allowed. I tried to flash OEM the RUU you tole me and I still get the remote 32 header error.
Is there a way to completly wipe out the phone and reinstall fresh?
Click to expand...
Click to collapse
You clearly didn't read the thread. It doesn't state anywhere "unlock bootloader".
I'll quote it for you
Go to fastboot
adb shell
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
adb reboot bootloader
fastboot oem lock
You'll get an error. It's normal
Finally type exit
Than you can flash the ruu http://forum.xda-developers.com/showthread.php?t=2508907
Do exactly as I tell you.
Sent from my HTCONE using Tapatalk

Still stuck
elvisypi said:
You clearly didn't read the thread. It doesn't state anywhere "unlock bootloader".
I'll quote it for you
Go to fastboot
adb shell
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
adb reboot bootloader
fastboot oem lock
You'll get an error. It's normal
Finally type exit
Than you can flash the ruu http://forum.xda-developers.com/showthread.php?t=2508907
Do exactly as I tell you.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply agian elvisypi, but for some reason I may be doing this wrong when I type in adb shell it cant find the device. As of now my bootloader is locked.

elvisypi said:
You clearly didn't read the thread. It doesn't state anywhere "unlock bootloader".
I'll quote it for you
Go to fastboot
adb shell
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
adb reboot bootloader
fastboot oem lock
You'll get an error. It's normal
Finally type exit
Than you can flash the ruu http://forum.xda-developers.com/showthread.php?t=2508907
Do exactly as I tell you.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
well u tried, ha!!

arc209 said:
Thanks for the reply agian elvisypi, but for some reason I may be doing this wrong when I type in adb shell it cant find the device. As of now my bootloader is locked.
Click to expand...
Click to collapse
Than you have problems with your drivers or ADB folders.
First uninstall all the HTC drivers you have installed on your PC. Than install the "Naked driver" from here http://forum.xda-developers.com/showthread.php?t=2263822
Install tge android ADB from here http://forum.xda-developers.com/showthread.php?t=2263822
Than do the procedure I previously topd you
Sent from my HTCONE using Tapatalk

[Q] Trouble with s-off HBoot 1.55

Whats up guys
I am having one hell of a time trying to get s-off on my sprint htc one m7_wls running 4.3. Hboot 1.55. I've tried revone and no matter what I do the command ./revone -P always fails. Then I tried rumrunner and that got to the point Where it passed the two tests then after fixing some skunky rum when it boots me back into fastboot for the 2nd time i get the error FATAL Download updated version from ww . rumrunner. us The only thing i havent tried yet is charging my phone to 100% and trying rumrunner. it was at about 75% the two times i tried it. SO anyway, if anyone here can help me to get one of these programs to work for me or just point me in the right direction I would very much appreciate that.
Thanks Fellas

Check PM

roffo4One said:
Whats up guys
I am having one hell of a time trying to get s-off on my sprint htc one m7_wls running 4.3. Hboot 1.55. I've tried revone and no matter what I do the command ./revone -P always fails. Then I tried rumrunner and that got to the point Where it passed the two tests then after fixing some skunky rum when it boots me back into fastboot for the 2nd time i get the error FATAL Download updated version from ww . rumrunner. us The only thing i havent tried yet is charging my phone to 100% and trying rumrunner. it was at about 75% the two times i tried it. SO anyway, if anyone here can help me to get one of these programs to work for me or just point me in the right direction I would very much appreciate that.
Thanks Fellas
Click to expand...
Click to collapse
Here's what I did:
1) Loaded the @benny3 stock, odex 4.3 ROM ;
2) Booted that ROM up, (and after my first run of rumrunner failed) updated the superSU binary (open superSU and it'll tell you to update, let your recovery do it);
3) When rebooted, I tested adb to assure it works (you need that for sure);
4) I then ran "adb shell" so I could "su" once -- that let me 'grant' access to su so rumrunner won't need to wait for superSU;
5) Rebooted into bootloader ( fastboot (usb) ) so I could test fastboot working "fastboot devices better return good info";
6) ran fastboot reboot to reboot normally;
7) ran rumrunner -- no issues, just anxious waits through the many minute process and reboots.
Hope that helps -- I run linux, so much easier from a driver perspective, but make sure your HTC drivers work and you DO NOT HAVE HTC SYNC installed. Use just the naked USB drivers.

tdhite said:
Here's what I did:
1) Loaded the @benny3 stock, odex 4.3 ROM ;
2) Booted that ROM up, (and after my first run of rumrunner failed) updated the superSU binary (open superSU and it'll tell you to update, let your recovery do it);
3) When rebooted, I tested adb to assure it works (you need that for sure);
4) I then ran "adb shell" so I could "su" once -- that let me 'grant' access to su so rumrunner won't need to wait for superSU;
5) Rebooted into bootloader ( fastboot (usb) ) so I could test fastboot working "fastboot devices better return good info";
6) ran fastboot reboot to reboot normally;
7) ran rumrunner -- no issues, just anxious waits through the many minute process and reboots.
Hope that helps -- I run linux, so much easier from a driver perspective, but make sure your HTC drivers work and you DO NOT HAVE HTC SYNC installed. Use just the naked USB drivers.
Click to expand...
Click to collapse
I had the drivers installed but since I am s on when I uninstall HTC sync when the phone reboots after the rumrunner tests it's reinstalled. Does thst affect the process at all?

roffo4One said:
I had the drivers installed but since I am s on when I uninstall HTC sync when the phone reboots after the rumrunner tests it's reinstalled. Does thst affect the process at all?
Click to expand...
Click to collapse
I guess I'm not helping you anymore?

roffo4One said:
I had the drivers installed but since I am s on when I uninstall HTC sync when the phone reboots after the rumrunner tests it's reinstalled. Does thst affect the process at all?
Click to expand...
Click to collapse
Well -- I'm not sure all that makes sense. But if @bigdaddy619 is helping you, you don't need to look further for help. You're in the exact right hands. I'll follow his lead from here.

Thank you
tdhite said:
Here's what I did:
1) Loaded the @benny3 stock, odex 4.3 ROM ;
2) Booted that ROM up, (and after my first run of rumrunner failed) updated the superSU binary (open superSU and it'll tell you to update, let your recovery do it);
3) When rebooted, I tested adb to assure it works (you need that for sure);
4) I then ran "adb shell" so I could "su" once -- that let me 'grant' access to su so rumrunner won't need to wait for superSU;
5) Rebooted into bootloader ( fastboot (usb) ) so I could test fastboot working "fastboot devices better return good info";
6) ran fastboot reboot to reboot normally;
7) ran rumrunner -- no issues, just anxious waits through the many minute process and reboots.
Hope that helps -- I run linux, so much easier from a driver perspective, but make sure your HTC drivers work and you DO NOT HAVE HTC SYNC installed. Use just the naked USB drivers.
Click to expand...
Click to collapse
thank you so much for your help

xbdarkfox said:
thank you so much for your help
Click to expand...
Click to collapse
What version of software were you on when this was successful? I am on 3.05.651.6 and understand it is necessary to downgrade to be able to use rumrunner successfully.
Thanks!

Docarut said:
What version of software were you on when this was successful? I am on 3.05.651.6 and understand it is necessary to downgrade to be able to use rumrunner successfully.
Thanks!
Click to expand...
Click to collapse
Sprint_HTC_One_m7wls 3.04.651.2 I had flashed an unsupported ROM and used Sprint_HTC_One_m7wls_3_04_651_2_RUU to flash back to stock. Rumrunner takes a few times just be patient

[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.

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?