Related
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!
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.
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!
Click to expand...
Click to collapse
You better wait till january and claim the warranty!
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.
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!
Click to expand...
Click to collapse
If you claim warranty : YOU LOSS A CHANCE TO HAVE BIG FUN I'm exactly on your situation (may be worse), but probably we feel different. I can only boot into fastboot and hboot ... LOL
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.
Some basic info about my phone-
HBOOT 1.47.0000
Radio 2.42.01.04.23
Carrier- iWireless (Kroger, Sprint subsidary)
S-ON
Alright, so I was just using my phone as normal. Running CM7.2 and ClockWorkMod Recovery. I turned off my phone, everything was fine. When I went to turn it on again, it showed the green HTC logo, as per normal, then it suddenly rebooted. There, it showed the green HTC logo again, and it'll just stay there. So I tried to boot into recovery (pulled the battery, put it back in, held the red end call button + volume down, got into hboot, then pressed home to go to recovery).
The thing is- it did the same thing. Reboot before it gets to recovery, and then stuck at the HTC Logo. I tried using the Sprint RUU, didn't work- it told me to download the right RUU for this phone, and gives me an error 131. I used the flashable RUU found in this thread (found here), in conjunction with this tutorial (found here). It gave me an error that looked like this when I ran "fastboot flash zip *flashable RUU zip path*"
Code:
FAILED (remote: 42 custom id check fail)
I believe it has something to do with the fact that it is NOT a Sprint branded phone. It doesn't even have a Google logo on the back.
Since it's not S-OFF, I can't flash a recovery via fastboot. I'm stuck. Help?
*TO CLARIFY*
I can't get into Recovery, or the actual system. I also can't access adb. The only part I can access is the bootloader and fastboot.
How much battery did you have left before you turned your phone off ?? Also what was the reason you turned your phone off ??? Also you linked to the use fastboot thread did you already type the "fastboot reboot reboot RUU" command ??
#Root-Hack_Mod*Always\
laie1472 said:
How much battery did you have left before you turned your phone off ?? Also what was the reason you turned your phone off ??? Also you linked to the use fastboot thread did you already type the "fastboot reboot reboot RUU" command ??
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
About 75% if I remember correctly. Only light usage. And I just turned it off in school, we were taking a test. Nothing abnormal about turning it off. And yes, several times. Tried flashing recovery/system/boot in every way possible, using that command and not using that command. I noticed something else- it seems like the NAND memory is completely wiped. There is NOTHING on the phone, other than the bootloader.
After you ran that command you tried to flash a zip or no ??? And more info on when you say the bootloader is the only thing on the phone would be appreciated. Also when you plug your phone into your pc does it recognize in its current state ??? Also when you boot into the bootloader what info is now displayed ???
#Root-Hack_Mod*Always\
laie1472 said:
After you ran that command you tried to flash a zip or no ??? And more info on when you say the bootloader is the only thing on the phone would be appreciated. Also when you plug your phone into your pc does it recognize in its current state ??? Also when you boot into the bootloader what info is now displayed ???
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
Yes, I tried flashing multiple times. As I said, it fails with a CID check failure. And it doesn't seem that there's anything on the NAND anymore, as it doesn't even get to the boot logo, and recovery will just restart the phone.
My PC recognizes my phone, only in fastboot. And just normal bootloader info- model number, baseband, etc.
Lately my phone has been rebooting itself quite a bit. It seems to be getting progressively worse to the point where if I open any app for more than a minute or two then my phone will reboot. I've tried uninstalling quite a few third party apps but that didn't do the trick. Whenever I try to do a hard reset (whether it's through settings or the HBOOT menu) the phone will shut down and then instead of getting the picture of a phone with the green thing in the middle and a status bar below that indicating the phone is resetting, I get a picture of a phone with a red symbol similar to a hazard sign that will last for about 30 seconds then the phone just boots back up to my home screen. I had put an incorrect custom ROM on this phone about 5-6 months ago but I was able to get the stock Sprint ROM back on the phone and relock the boot loader and the phone functioned fine ever since up until about a week ago when it started rebooting randomly. I have a feeling this may be part of the reason why the factory reset is not working. Does anyone have any ideas on how to proceed? Can I do a factory reset by pushing a ROM to the phone through my computer?
If u are s-off then I suggest u download the ruu and run it. If s-off all u have to do is go to hboot and select fast boot and run the program it will reset the phone back to whatever software version it is for the ruu. If your not s-off you will need to get the ruu that matches your firmware. That should fix your troubles if not then you have something faulty with the hardware itself
Sent from my iPad using Tapatalk
Ok I am S-ON and here is what I am trying to do. I downloaded the RUU that matches my phone current software from the link below and placed the file in the platform-tools folder after renaming it. When I run the fastboot oem rebootRUU command in the cmd prompt, my phone just reboots rather than booting to the black screen with the silver HTC logo. Any suggestions on how to proceed?
http://forum.xda-developers.com/showthread.php?t=2687690
Also, my bootloader shows that it is relocked
coppertop4646 said:
Ok I am S-ON and here is what I am trying to do. I downloaded the RUU that matches my phone current software from the link below and placed the file in the platform-tools folder after renaming it. When I run the fastboot oem rebootRUU command in the cmd prompt, my phone just reboots rather than booting to the black screen with the silver HTC logo. Any suggestions on how to proceed?
http://forum.xda-developers.com/showthread.php?t=2687690
Also, my bootloader shows that it is relocked
Click to expand...
Click to collapse
That is a firmware flashing that will do nothing for u. Here is a link to the newest RUU I can find http://forum.xda-developers.com/showthread.php?t=2658910
Sent from my One using Tapatalk
luigi311 said:
That is a firmware flashing that will do nothing for u. Here is a link to the newest RUU I can find http://forum.xda-developers.com/showthread.php?t=2658910
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Ok I tried that RUU yesterday and couldn't seem to get anywhere because I kept getting error 170 (tried updating drivers, installing HTC sync, etc). Tried again today and got error 170 again, so then I went in my bootloader, then fastboot, connected USB cable, fastboot usb. I then ran the RUU and it said it was going to update my phone. The status bar then said "Waiting for bootloader" and my phone just rebooted itself to the home screen and then I got like error 171 or something (another USB error). I'm kind of running out of ideas at this point. I believe something is wrong with my recovery or I have some sort of bug because I attempted to flash a custom recovery today (TWRP) but when I unlocked my bootloader, I restarted the phone and entered my bootloader again but it still said relocked (even though the prompt on my phone came up giving me the warnings asking if I was sure I wanted to unlock the bootloader) so when I run the command fastboot flash recovery twrp.img I get something along the lines of can't read twrp.img or can't open twrp.img (yes I made sure the file is in the same folder that I am running the adb out of). Willing to try any recommendations at this point because my phone is pretty useless as of right now because it restarts every couple minutes. HTC wants $150 to fix it which I told them I'm not willing to pay, rather buy a new phone.
So, I took a look around the forums thinking that maybe another newbie such myself did this thing but apparently I am one of a kind. So here is my story:
I have my HTC One M7 since the summer of 2014, I rooted it without any problems and unrooted it when the Lollipop update came out. After two or three days of the update, I had a problem where my phone would lose all sounds and would be unable to play any media that involved music. I thought it might be a software problem so I rooted it again and I installed the ViperOne ROM from the forums. Despite the fact that I really loved the ROM, the problem insisted and once/twice a day I needed to clear cache, restart the phone and if I was lucky it would go away on the first trial.
P.S. The problem only occurred when a call started.
This past Friday however, the problem wouldn't go away no matter what I did. My phone had lost all sounds and I couldn't do anything about it. Ringtones, alarms, videos, youtube, calls, even the bootup sound, nothing.
So I decided to redo everything from the beginning, in case I did something wrong and with the hope that it will just get fixed. Thinking that my software was the problem, I decided not to do a backup (please don't kill me I know it was a stupid decision) and to just wipe everything off, and do it from scratch. I re-installed viper as a first step but it didn't fix. I wiped the whole system and data partitions and installed the ROM again, nothing. Then I tried to install a clean HTC RUU and I found that the latest was this one
Code:
RUU_M7_UL_K44_SENSE55_MR_BrightstarUS_WWE_4.19.1540.9_Radio_4A.23.3263.28_10.38r.1157.04L_release_353887_signed_3
but it needed to be installed through HTC Sync and it just wouldn't work. I was getting a message that the phone was not connected.
Uninstalled HTC Sync, Re-installed HTCDriver_4.1.0.001 and downloaded a KitKat ROM from HTC1Guru site but when I tried to install it, I was getting an error message from the TWRP recovery.
Next, I downloaded Guru_Reset_M7_2.24.401.8, installed it, opened it, sound still wouldn't work no matter what. Also, while I installed the Guru Reset, I was asked if I wanted to also install stock recovery and I said yes. Since this ROM was able to be installed, I started doing the OTA updates with the hope that one of them might fix the sound problem. On the third update, the phone got bricked and stuck in a bootloop.
At this point, I can only enter bootloader without the phone crashing.
Recovery gives me a Red triangle with an exclamation mark in it.
Factory Reset goes bootloop.
And the worst of all is that now my PC doesn't recognize the device and fastboot commands give me the "waiting for device" middle finger and I can't do anything.
TL;DR
phone got bricked and stuck in a bootloop.
At this point, I can only enter bootloader without the phone crashing.
Recovery gives me a Red triangle with an exclamation mark in it.
Factory Reset goes bootloop.
And the worst of all is that now my PC doesn't recognize the device and fastboot commands give me the "waiting for device" middle finger and I can't do anything.
Please help me I don't know what to do and I cannot send it to service to fix it because the Bootloader has the "Tampered" message on top.
This is what my bootloader has:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4A.17.3250.14
OpenDSP-v35.120.274.0718
OS-7.19.401.2
eMMC-boot 2048MB
skypse said:
So, I took a look around the forums thinking that maybe another newbie such myself did this thing but apparently I am one of a kind. So here is my story:
I have my HTC One M7 since the summer of 2014, I rooted it without any problems and unrooted it when the Lollipop update came out. After two or three days of the update, I had a problem where my phone would lose all sounds and would be unable to play any media that involved music. I thought it might be a software problem so I rooted it again and I installed the ViperOne ROM from the forums. Despite the fact that I really loved the ROM, the problem insisted and once/twice a day I needed to clear cache, restart the phone and if I was lucky it would go away on the first trial.
P.S. The problem only occurred when a call started.
This past Friday however, the problem wouldn't go away no matter what I did. My phone had lost all sounds and I couldn't do anything about it. Ringtones, alarms, videos, youtube, calls, even the bootup sound, nothing.
So I decided to redo everything from the beginning, in case I did something wrong and with the hope that it will just get fixed. Thinking that my software was the problem, I decided not to do a backup (please don't kill me I know it was a stupid decision) and to just wipe everything off, and do it from scratch. I re-installed viper as a first step but it didn't fix. I wiped the whole system and data partitions and installed the ROM again, nothing. Then I tried to install a clean HTC RUU and I found that the latest was this one
Code:
RUU_M7_UL_K44_SENSE55_MR_BrightstarUS_WWE_4.19.1540.9_Radio_4A.23.3263.28_10.38r.1157.04L_release_353887_signed_3
but it needed to be installed through HTC Sync and it just wouldn't work. I was getting a message that the phone was not connected.
Uninstalled HTC Sync, Re-installed HTCDriver_4.1.0.001 and downloaded a KitKat ROM from HTC1Guru site but when I tried to install it, I was getting an error message from the TWRP recovery.
Next, I downloaded Guru_Reset_M7_2.24.401.8, installed it, opened it, sound still wouldn't work no matter what. Also, while I installed the Guru Reset, I was asked if I wanted to also install stock recovery and I said yes. Since this ROM was able to be installed, I started doing the OTA updates with the hope that one of them might fix the sound problem. On the third update, the phone got bricked and stuck in a bootloop.
At this point, I can only enter bootloader without the phone crashing.
Recovery gives me a Red triangle with an exclamation mark in it.
Factory Reset goes bootloop.
And the worst of all is that now my PC doesn't recognize the device and fastboot commands give me the "waiting for device" middle finger and I can't do anything.
TL;DR
phone got bricked and stuck in a bootloop.
At this point, I can only enter bootloader without the phone crashing.
Recovery gives me a Red triangle with an exclamation mark in it.
Factory Reset goes bootloop.
And the worst of all is that now my PC doesn't recognize the device and fastboot commands give me the "waiting for device" middle finger and I can't do anything.
Please help me I don't know what to do and I cannot send it to service to fix it because the Bootloader has the "Tampered" message on top.
This is what my bootloader has:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4A.17.3250.14
OpenDSP-v35.120.274.0718
OS-7.19.401.2
eMMC-boot 2048MB
Click to expand...
Click to collapse
oops, that's the wrong RUU for you phone, I would also hazard a guess that the guru reset is just too old, the key for you is in the numbers, your current os is 7.19.401.2 its the 401 part which matters the most, the 7 part is also android revision, as your on 7, I would say 2 is very too old for your phone., the RUU you tried to use if you look at the numbers is android revision 4 developer edition 1540 (4.19.1540.9) hope that explains that a little for you.
The red exclamation mark is stock recovery, when you see that symbol, press volume up and power a few times and you'll get the menu.
well the first thing you need to do is get your drivers sorted, so uninstall HTC sync manager and the drivers now restart your computer, then re-download it, install it, and then go into add/remove programs and remove HTC sync, just above it you will see HTC driver package, leave that alone.
now boot your phone into the bootloader, fastboot USB mode and plug it into the computer, leave it alone to detect your phone ands install the fastboot drivers.
your going to need to download 2 files: your RUU zip and HTC's fastboot to flash it: https://www.androidfilehost.com/?fid=95916177934554130 rename this file to RUU for ease, and also download this: https://www.androidfilehost.com/?fid=96042739161891970, put both files on your computer in the same folder as your current adb and fastboot files, then just issue these commands, this will wipe your entire phone by the way, but I think you've probably already done that anyway.
fastboot oem lock
fastboot erase cache
fastboot reboot-bootloader
your phone should now say tampered and relocked at the top
fastboot oem rebootRUU black screen silver HTC logo
htc_fastboot flash zip RUU.zip notice your now using the HTC fastboot, the normal one wont work for this flash
it take about 10 mins to flash, at the end make sure it says successful and OKAY, final commands are:
fastboot reboot-bootloader
fastboot reboot
phone should now boot, it will be a first time boot so may take a while
Seanie280672 said:
oops, that's the wrong RUU for you phone, I would also hazard a guess that the guru reset is just too old, the key for you is in the numbers, your current os is 7.19.401.2 its the 401 part which matters the most, the 7 part is also android revision, as your on 7, I would say 2 is very too old for your phone., the RUU you tried to use if you look at the numbers is android revision 4 developer edition 1540 (4.19.1540.9) hope that explains that a little for you.
The red exclamation mark is stock recovery, when you see that symbol, press volume up and power a few times and you'll get the menu.
well the first thing you need to do is get your drivers sorted, so uninstall HTC sync manager and the drivers now restart your computer, then re-download it, install it, and then go into add/remove programs and remove HTC sync, just above it you will see HTC driver package, leave that alone.
now boot your phone into the bootloader, fastboot USB mode and plug it into the computer, leave it alone to detect your phone ands install the fastboot drivers.
your going to need to download 2 files: your RUU zip and HTC's fastboot to flash it: https://www.androidfilehost.com/?fid=95916177934554130 rename this file to RUU for ease, and also download this: https://www.androidfilehost.com/?fid=96042739161891970, put both files on your computer in the same folder as your current adb and fastboot files, then just issue these commands, this will wipe your entire phone by the way, but I think you've probably already done that anyway.
fastboot oem lock
fastboot erase cache
fastboot reboot-bootloader
your phone should now say tampered and relocked at the top
fastboot oem rebootRUU black screen silver HTC logo
htc_fastboot flash zip RUU.zip notice your now using the HTC fastboot, the normal one wont work for this flash
it take about 10 mins to flash, at the end make sure it says successful and OKAY, final commands are:
fastboot reboot-bootloader
fastboot reboot
phone should now boot, it will be a first time boot so may take a while
Click to expand...
Click to collapse
Thank you very much for your help Seanie. I followed all the steps as you described but I still get "waiting for device" message in the command prompt. How can I overcome this? Is it supposed to be a problem with the drivers?
skypse said:
Thank you very much for your help Seanie. I followed all the steps as you described but I still get "waiting for device" message in the command prompt. How can I overcome this? Is it supposed to be a problem with the drivers?
Click to expand...
Click to collapse
yes it's a driver issue
see nkk71 guide post 2 faq 2 / to get fastboot working with your phone
http://forum.xda-developers.com/showthread.php?t=2541082
Thank you for your reply! I downloaded the drivers from the guide and it works. I'm on step 5 now and waiting for flash to end.
EDIT: So everything worked perfectly and I finally was able to turn my phone on again. Thank you very much for your assistance!
Bad news is that the sound problem is still here. I really have no idea on what would be the problem. Maybe it has something to do with the hardware and the whole Lollipop upgrade was an unfortunate moment. I guess I'll start another thread in the following days to see if anyone can help with that.
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?