Hello everyone. In my attempt to experiment with custom ROMS yesterday, I seem to have sort of soft bricked my phone. When I install the stock OS, it installs fine, and I can start the phone. However, after it boots up, there are no apps. Just the clock at the top, the background, and the menu button in the bottom center (but pressing this button doesn't do anything). I can pull down the top menu and go to settings, but I don’t have access to anything else. Furthermore, after a couple minutes, the phone restarts itself. After this first restart, when its gets done booting, there is simply an empty black screen. The only way to get to the state mentioned before is to boot into bootloader, turn the phone off, and then turn it back on.
I’m wholly lost and out of ideas on how to go about troubleshooting this. Here is what I did yesterday to get to this point:
1. Unlocked the bootloader.
2. Flashed the latest Viper rom. It didn’t work; after booting up the phone was forever stuck on the Viper splash screen.
3. Flashed the stock Sprint HTC One rom. Again, after booting up the phone was forever stuck on the HTC splash screen.
4. Used TWRP to format all the data.
5. Flashed the stock Sprint HTC One rom again. This time it worked just fine. At this point, I thought I had discovered a valid method for fixing my soft bricked phone, so I decided to experiment with Viper and Android Revolutions roms to see if I could get them to work. I followed the process of installing a custom rom, getting stuck on the splash screen, formatting the data, then reinstalling the stock rom 3 times. On all three times the stock rom worked when I installed it. However, on the 4th iteration of this cycle, I reached the state I described above.
I tried using the RUU utility, but it doesn’t work (I get a signature verification error). I can enter bootloader and recovery without issue.
I've had this happen to me, Make sure that you re-lock your bootloader before the RUU
fastboot oem lock
I believe this will allow the RUU to start up right and repair. Lemme know how that goes.
jclark11 said:
I've had this happen to me, Make sure that you re-lock your bootloader before the RUU
fastboot oem lock
I believe this will allow the RUU to start up right and repair. Lemme know how that goes.
Click to expand...
Click to collapse
Do you mean you have had the same blank screen problam as well? Or RUU wouldn't work for you?
I'm pretty sure i relocked the bootloader when I tried doing the RUU, but I will definitely try again. Unfortunately, I'm on a trip at the moment, so I'm not sure when I'll be able to look at it again (hopefully Saturday or Tuesday).
Related
I recently upgraded to an HTC One, on Verizon in the US. I promptly used rumrunner s-off to get S-OFF, unlock the bootloader, and obtain root. I also flashed the latest ClockworkMod recovery, with the intent of installing CyanogenMod, but decided I'd try out the stock ROM for a few days first, since my old phone was still on Gingerbread.
Everything was working fine until I decided to remove some Verizon bloatware. While I did back up each app before removing it, I forgot to make a nandroid backup. I only removed things that seemed nonessential -- such as the NFL Mobile app, Slacker radio, and My Verizon, which I'd also removed without issue on my old phone -- but apparently that was not the case, as after rebooting, I got stuck on the Verizon logo during the boot sequence.
I then attempted to perform a factory reset in CWMR, and it appeared to be stuck on "wiping cache", so -- like the impatient idiot I clearly am, as I later found a few threads explaining that this part of the reset process can just take a very long time -- I rebooted the phone to try again. This resulted in CWMR throwing errors about failing to mount several partitions, but it finally seemed to finish the reset on the second try. However, upon reboot, it just sat at the HTC logo forever.
After about an hour, and no success in finding anything on the internet indicating that it should take this long to boot up after a reset, I powered the phone off and back on again. After rebooting, the bootloader screen displayed "OS" in red followed by some random symbols. I could still get into recovery, and could still access the device with fastboot, so I decided to try to reflash the stock ROM, using the RUU zip found here.
Due to some problem (this was all about 6 hours ago while I was at work, and I was quite frustrated at this point, so I don't remember what exactly was the problem here) and based on the advice of another forum thread, I decided to try TWRP instead of CWM. But, TWRP wouldn't go any further than its logo splash screen, so I re-flashed CWM. Afterwards, my phone went into a reboot loop -- the HTC logo comes up, the phone vibrates shortly, and then after a few seconds the screen turns off and it does the same thing over again. If I hold the power button down for long enough, it will power down, but if I try to turn it back on, it will either go into the loop again, or just sit at the HTC logo (left it there for upwards of an hour at one point).
I have found several threads about similar boot loop issues, but as I can't get into hboot/fastboot or recovery, I can't try to apply any of the solutions. I cannot connect from my computer with fastboot or adb -- "devices" lists nothing, and all other commands return either "error: no device found" or "waiting for device". No amount of power+volume down makes any difference, nor does holding the phone under a bright light as several threads suggested. Occasionally it will go to a black screen (not off, just black) that maybe it thinks is the bootloader menu, but it doesn't display anything, and after about 30 seconds it will reboot itself.
Does anyone have any suggestions for getting into recovery and trying to reflash.... something?
Alternatively, if I return it to Verizon at this point, will they be able to tell that it's rooted/unlocked/S-OFF?
Any ideas would be much appreciated!
brasstongue said:
I recently upgraded to an HTC One, on Verizon in the US. I promptly used rumrunner s-off to get S-OFF, unlock the bootloader, and obtain root. I also flashed the latest ClockworkMod recovery, with the intent of installing CyanogenMod, but decided I'd try out the stock ROM for a few days first, since my old phone was still on Gingerbread.
Everything was working fine until I decided to remove some Verizon bloatware. While I did back up each app before removing it, I forgot to make a nandroid backup. I only removed things that seemed nonessential -- such as the NFL Mobile app, Slacker radio, and My Verizon, which I'd also removed without issue on my old phone -- but apparently that was not the case, as after rebooting, I got stuck on the Verizon logo during the boot sequence.
I then attempted to perform a factory reset in CWMR, and it appeared to be stuck on "wiping cache", so -- like the impatient idiot I clearly am, as I later found a few threads explaining that this part of the reset process can just take a very long time -- I rebooted the phone to try again. This resulted in CWMR throwing errors about failing to mount several partitions, but it finally seemed to finish the reset on the second try. However, upon reboot, it just sat at the HTC logo forever.
After about an hour, and no success in finding anything on the internet indicating that it should take this long to boot up after a reset, I powered the phone off and back on again. After rebooting, the bootloader screen displayed "OS" in red followed by some random symbols. I could still get into recovery, and could still access the device with fastboot, so I decided to try to reflash the stock ROM, using the RUU zip found here.
Due to some problem (this was all about 6 hours ago while I was at work, and I was quite frustrated at this point, so I don't remember what exactly was the problem here) and based on the advice of another forum thread, I decided to try TWRP instead of CWM. But, TWRP wouldn't go any further than its logo splash screen, so I re-flashed CWM. Afterwards, my phone went into a reboot loop -- the HTC logo comes up, the phone vibrates shortly, and then after a few seconds the screen turns off and it does the same thing over again. If I hold the power button down for long enough, it will power down, but if I try to turn it back on, it will either go into the loop again, or just sit at the HTC logo (left it there for upwards of an hour at one point).
I have found several threads about similar boot loop issues, but as I can't get into hboot/fastboot or recovery, I can't try to apply any of the solutions. I cannot connect from my computer with fastboot or adb -- "devices" lists nothing, and all other commands return either "error: no device found" or "waiting for device". No amount of power+volume down makes any difference, nor does holding the phone under a bright light as several threads suggested. Occasionally it will go to a black screen (not off, just black) that maybe it thinks is the bootloader menu, but it doesn't display anything, and after about 30 seconds it will reboot itself.
Does anyone have any suggestions for getting into recovery and trying to reflash.... something?
Alternatively, if I return it to Verizon at this point, will they be able to tell that it's rooted/unlocked/S-OFF?
Any ideas would be much appreciated!
Click to expand...
Click to collapse
Can u get into bootloader?? Press power + vol down??
brasstongue said:
After rebooting, the bootloader screen displayed "OS" in red followed by some random symbols.
Click to expand...
Click to collapse
that means your firmware is either in a state of limbo, or you corrupted one of your partitions.
so I decided to try to reflash the stock ROM, using the RUU zip found here. Due to some problem
Click to expand...
Click to collapse
which ruu, and what was the problem
But, TWRP wouldn't go any further than its logo splash screen, so I re-flashed CWM.
Click to expand...
Click to collapse
Did you flash the correct recovery for Verizon (M7_WLS), it's different than international (M7_U/UL)
as @khandelwalsiddharth mentioned you need to get to bootloader if a fix is even possible, so POWER OFF your phone completely, then HOLD VOLDOWN and POWER, when it boots up let go of POWER but keep holding VOLDOWN until you get to bootloader
then you need to have working "fastboot devices" (if you're on Win8.1, you probably need to use another computer with Win7 or use a Linux Live USB)
if you can't get to bootloader, then I don't think this is fixable, cause hboot is corrupt
Thanks for the reply.
nkk71 said:
which ruu, and what was the problem
Click to expand...
Click to collapse
Oh, I guess I forgot to make that a link... I had downloaded the only VZW one on this page but I'm not even sure why I bothered to mention it, as downloading it to my computer was the only thing I ever did with it; I was never able to get as far as flashing it to the phone, so it actually had nothing to do with the problem...
nkk71 said:
Did you flash the correct recovery for Verizon (M7_WLS), it's different than international (M7_U/UL)
Click to expand...
Click to collapse
I was under the impression that Verizon was m7vzw, in which case yes, I was using the correct recovery (6.0.4.7 version listed next to "HTC One (Verizon)" on this page) and it was working just fine the first time I flashed it.
nkk71 said:
as @khandelwalsiddharth mentioned you need to get to bootloader if a fix is even possible, so POWER OFF your phone completely, then HOLD VOLDOWN and POWER, when it boots up let go of POWER but keep holding VOLDOWN until you get to bootloader
Click to expand...
Click to collapse
Yeah, I've tried this about 100 times, and the only thing holding VOLDOWN does is occasionally interrupt the boot loop to send me to the black screen for 30 seconds before going back into the boot loop. I did find one thread where the poster was able to get into the bootloader after letting the phone sit overnight, so I'll try again tomorrow, but I'm not very hopeful.
nkk71 said:
then you need to have working "fastboot devices" (if you're on Win8.1, you probably need to use another computer with Win7 or use a Linux Live USB)
Click to expand...
Click to collapse
I'm on Win7, and "fastboot devices" was working the other day, so I know my drivers are all set up properly and functioning. The phone just isn't booting far enough to connect to the computer.
nkk71 said:
if you can't get to bootloader, then I don't think this is fixable, cause hboot is corrupt
Click to expand...
Click to collapse
So... should be safe to take it back to Verizon and ask for a replacement, since they won't be able to tell it's unlocked? >_>
brasstongue said:
Thanks for the reply.
Oh, I guess I forgot to make that a link... I had downloaded the only VZW one on this page but I'm not even sure why I bothered to mention it, as downloading it to my computer was the only thing I ever did with it; I was never able to get as far as flashing it to the phone, so it actually had nothing to do with the problem...
I was under the impression that Verizon was m7vzw, in which case yes, I was using the correct recovery (6.0.4.7 version listed next to "HTC One (Verizon)" on this page) and it was working just fine the first time I flashed it.
Yeah, I've tried this about 100 times, and the only thing holding VOLDOWN does is occasionally interrupt the boot loop to send me to the black screen for 30 seconds before going back into the boot loop. I did find one thread where the poster was able to get into the bootloader after letting the phone sit overnight, so I'll try again tomorrow, but I'm not very hopeful.
I'm on Win7, and "fastboot devices" was working the other day, so I know my drivers are all set up properly and functioning. The phone just isn't booting far enough to connect to the computer.
So... should be safe to take it back to Verizon and ask for a replacement, since they won't be able to tell it's unlocked? >_>
Click to expand...
Click to collapse
my bad, thought I read Sprint, not sure if Sprint and Verizon use same recovery, but that doesn't really matter now
unless you can get to bootloader, you're stuck, sorry.
If your pc does see "fastboot devices" then it must be in bootloader and flashing a ruu.zip (if available) could (that's a very big could) get the device working again.
Here goes nothing. I have an HTC One m7 unlocked and rooted. Im not sure what happened but I know when it happened. I was trying to install viperone 6.2.1 and it failed and the installer suggested flasing the latest TWRP and try again. I hit ok and my phone rebooted straight to the bootloader. I tried a reboot- straight to bootloader. I tried to go into recovery- straight to bootloader. I tried factory reset- straight to bootloader. I only had access to the bootloader. I eventually found Hasoon2000s All One Tool and flashed a recovery. Made sure I had the latest TWRP and tried viperone again. It installed correctly and I rebooted. Once it loads all I get is a lock screen that I can unlock then a white screen that says htc. It will then force restart and the same thing happens again. Next I tried Paranoid Android. It loads fully but will force restart after a few minutes. I quickly looked at my phone status inbetween restarts and everything network, mobile network type, service state, imei,imei sv are all unknown. Basically no service. Next I flashed the latest CWM recovery. I installed the latest MIUI rom. It installed and during set-up it tried looking for my SIM card and force restarts. It will re-boot and go right back to searching for the SIM card. Rinse and repeat. Next I downloaded CM11 and installed that. Thankfully that does not force restart at all but my phone status is still all unknown. So I go into networks and try mobile plan and it asks for my SIM card which is installed. Then I try mobile network settings/ network operators look for available networks and I get "error while searching for networks". I forgot to mention all the Roms had to be pushed through with adb. Does anyone have a clue as to what I might have done or how I can fix it?
Try flashing a Stock RUU
mjma said:
Here goes nothing. I have an HTC One m7 unlocked and rooted. Im not sure what happened but I know when it happened. I was trying to install viperone 6.2.1 and it failed and the installer suggested flasing the latest TWRP and try again. I hit ok and my phone rebooted straight to the bootloader. I tried a reboot- straight to bootloader. I tried to go into recovery- straight to bootloader. I tried factory reset- straight to bootloader. I only had access to the bootloader. I eventually found Hasoon2000s All One Tool and flashed a recovery. Made sure I had the latest TWRP and tried viperone again. It installed correctly and I rebooted. Once it loads all I get is a lock screen that I can unlock then a white screen that says htc. It will then force restart and the same thing happens again. Next I tried Paranoid Android. It loads fully but will force restart after a few minutes. I quickly looked at my phone status inbetween restarts and everything network, mobile network type, service state, imei,imei sv are all unknown. Basically no service. Next I flashed the latest CWM recovery. I installed the latest MIUI rom. It installed and during set-up it tried looking for my SIM card and force restarts. It will re-boot and go right back to searching for the SIM card. Rinse and repeat. Next I downloaded CM11 and installed that. Thankfully that does not force restart at all but my phone status is still all unknown. So I go into networks and try mobile plan and it asks for my SIM card which is installed. Then I try mobile network settings/ network operators look for available networks and I get "error while searching for networks". I forgot to mention all the Roms had to be pushed through with adb. Does anyone have a clue as to what I might have done or how I can fix it?
Click to expand...
Click to collapse
Try flashing a stock RUU, everything should work fine after wards. You could try to update later on.
Try downloading this (Sprint_HTC_One_m7wls_1.29.651.10_RUU.zip) from http://forum.xda-developers.com/showthread.php?t=2586704
I take it you're S-Off so follow step 3(a)
If not 3(b) then 3(a).
relic626 said:
Try flashing a stock RUU, everything should work fine after wards. You could try to update later on.
Try downloading this (Sprint_HTC_One_m7wls_1.29.651.10_RUU.zip) from http://forum.xda-developers.com/showthread.php?t=2586704
I take it you're S-Off so follow step 3(a)
If not 3(b) then 3(a).
Click to expand...
Click to collapse
Thanks I will try it out and let you know!
relic626 said:
Try flashing a stock RUU, everything should work fine after wards. You could try to update later on.
Try downloading this (Sprint_HTC_One_m7wls_1.29.651.10_RUU.zip) from http://forum.xda-developers.com/showthread.php?t=2586704
I take it you're S-Off so follow step 3(a)
If not 3(b) then 3(a).
Click to expand...
Click to collapse
Ok well I flashed a stock rom and its doing the same thing as ViperOne. It loads and I can see the the lock screen and it will bring up the power menu if I hold down the power button. I still get the white screen with htc on it as my "background" but thats all i see. And as before it goes into a reboot cycle after a minute or so.
Meh
mjma said:
Ok well I flashed a stock rom and its doing the same thing as ViperOne. It loads and I can see the the lock screen and it will bring up the power menu if I hold down the power button. I still get the white screen with htc on it as my "background" but thats all i see. And as before it goes into a reboot cycle after a minute or so.
Click to expand...
Click to collapse
Well i can't give you any more advice as advice because i wouldn't want you to brick your phone on my account. Hopefully a dev see's this and intervenes.
relic626 said:
Well i can't give you any more advice as advice because i wouldn't want you to brick your phone on my account. Hopefully a dev see's this and intervenes.
Click to expand...
Click to collapse
Flashing a "stock rom" is not flashing the RUU -- RUU and then tell us what happened (unless you really meant you actually RUU'd, not merely flashed).
If that' fails, you'll have to back of and get CM 10.1 running, that almost always fixes things.
Actually just re-read that
Flashing a ROM is completely different from flashing a RUU.
Also are you getting a dialer error when you're on that htc splash screen?
Also, yay senior member on thread.
mjma said:
Ok well I flashed a stock rom and its doing the same thing as ViperOne. It loads and I can see the the lock screen and it will bring up the power menu if I hold down the power button. I still get the white screen with htc on it as my "background" but thats all i see. And as before it goes into a reboot cycle after a minute or so.
Click to expand...
Click to collapse
You were installing ViperOne 6.2.1? It could be that that's what screwed you over. IIRC, Viper OTAs are Delta. The latest full ROM is 6.2.0. That is, what you flashed was an update, not a ROM. But whatever.
And as tdhite said, flashing a ROM is not the same as completely bringing your phone back to stock with the RUU tool. Do that please.
I just got and m8 from Cl, it was cheap and I was told the phone had a software issues so I took the plunge.
The phone seems normal, its pack o apps and you can play with it, then I decided to do a factory restore, but it failed (after the reboot it goes to a error screen showing a phone with and exclamation mark)
I tried the same from hboot, same result..
Tried to unlock bootloader, it appears to work but after boot the phone I still the same (loked and with all the user info intact )
Tried to erase the user accounts, it works, I can do a new setup of the Google account, but after restart the phone goes back to the initial state (user accounts are back)
I am not sure what's going on, but it looks like if the memory was protected and after every reboot it goes back to the original state.
Any suggestions of what to do? I am starting to see of there is any way to get warranty thru htc,
Thanks in advance.
The phone is in 4.4.2, can't take updated (it reboots itself on the process)
The phone with the exclamation point indicates the stock Android system recovery is installed. You could try and install TWRP recovery, at which time you could install a custom ROM. My only other thought is to run the RUU for the latest system update. If that doesn't straighten out your issues, something else is going on. Hit the link below and follow the instructions for the manual system update. This is the non-HK RUU. If you need the RUU for the HK version I can post it, also.
http://www.htc.com/us/support/htc-one-m8-sprint/news/
Thanks, I tried to install twrp but it fails, the bootloader is still locked and won't unlock, is there a way to install twrp without unlocking bootloader?
Will give it a try with the RUU, when tried to update thru fastboot it fails, it starts to do all the file checks and it just send you to the "press the power button message" , but no update was perform.
You might give this a try to get your bootloader unlocked and TWRP installed. There is no way around it. You have to unlock the bootloader first before you install TWRP.
http://forum.xda-developers.com/showthread.php?t=2727900
Thanks a lot for the help, nothing has work so far, the phone keeps having random reboots and every time it comes back its like it load an old backup, havent been able to do a firmwware upgrade (from android over wifi, fastboot, or windowsPC).
Is there an utility to test hardware? (possibly memory)
thanks
At the end I contacted HTC support and after some test I was told my phone was still under warranty and I got and RMA (great service)....
Thanks a lot for the help...
I have had my HTC One M7 shortly after it was release. I got it from ATT. I immediately found a guide here and rooted it. I had TWRP and every time ATT tried to push an OTA I would refuse. I haven't bothered with it until a couple weeks ago when I wanted to put in KIT KAT. so I found m7_Stock_Rooted_4.18.502.7_odex.zip. I did a dirty upgrade, as the thread said it was okay. And it was. I am going on a trip so I purchased a sim unlock code in between upgrading to kitkat and today.
I got another OTA. I must not have read the bootloader correctly to refuse the install. I was no longer rooted. I come back to XDA and thought what the heck, I'll try out this ROM, it looks nice: Android_Revolution_HD-One_83.1.zip. I use TWRP to put the ROM in and now I am full of fail. After a little bit of Google I decided to try to do a factory reset. And now I am stuck in a boot loop. I have went back to Google but so far all I have seen is use adb or some other method to put things on the "sd card". But how would I do that when this phone doesn't have a sim card and I can't hook it up to my computer anymore? FWIW at some point in the boot loop my computer will recognize the phone, but it won't stay in that state long before it goes away. What happens is my phone starts too boot. Boot screen comes up. After about 10-15 seconds it restarts. This time saying entering recovery.... at the top. That lasts for about 2 seconds, phone goes black and reboots like normal. Over and over.
Best I can do is get to the android hard reset screen by holding power and reset screen. But that is saying "tampered" and "unlocked" at top. I chose the factory setting option and that doesn't do anything to alter the current state.
Edit:
When I went to flash Android Revolution ROM I chose wipe data. It gave some error that some files were not copied. So I ran it again, straight from TWRP. But that never installed right and I was stuck in a boot loop. I don't have many options with the android hard reset menu. But if choose restore, I will get to see the screen from TWRP flash for just a moment before it goes away and reboots.
Also I do see my phone when I have it plugged in the control panel (windows). Under devices and printers, it is listed as Android 1.0 under unspecified devices.
Budee80 said:
I have had my HTC One M7 shortly after it was release. I got it from ATT. I immediately found a guide here and rooted it. I had TWRP and every time ATT tried to push an OTA I would refuse. I haven't bothered with it until a couple weeks ago when I wanted to put in KIT KAT. so I found m7_Stock_Rooted_4.18.502.7_odex.zip. I did a dirty upgrade, as the thread said it was okay. And it was. I am going on a trip so I purchased a sim unlock code in between upgrading to kitkat and today.
I got another OTA. I must not have read the bootloader correctly to refuse the install. I was no longer rooted. I come back to XDA and thought what the heck, I'll try out this ROM, it looks nice: Android_Revolution_HD-One_83.1.zip. I use TWRP to put the ROM in and now I am full of fail. After a little bit of Google I decided to try to do a factory reset. And now I am stuck in a boot loop. I have went back to Google but so far all I have seen is use adb or some other method to put things on the "sd card". But how would I do that when this phone doesn't have a sim card and I can't hook it up to my computer anymore? FWIW at some point in the boot loop my computer will recognize the phone, but it won't stay in that state long before it goes away. What happens is my phone starts too boot. Boot screen comes up. After about 10-15 seconds it restarts. This time saying entering recovery.... at the top. That lasts for about 2 seconds, phone goes black and reboots like normal. Over and over.
Best I can do is get to the android hard reset screen by holding power and reset screen. But that is saying "tampered" and "unlocked" at top. I chose the factory setting option and that doesn't do anything to alter the current state.
Edit:
When I went to flash Android Revolution ROM I chose wipe data. It gave some error that some files were not copied. So I ran it again, straight from TWRP. But that never installed right and I was stuck in a boot loop. I don't have many options with the android hard reset menu. But if choose restore, I will get to see the screen from TWRP flash for just a moment before it goes away and reboots.
Also I do see my phone when I have it plugged in the control panel (windows). Under devices and printers, it is listed as Android 1.0 under unspecified devices.
Click to expand...
Click to collapse
which twrp version do you have installed?
little123 said:
which twrp version do you have installed?
Click to expand...
Click to collapse
Thanks dude. I had an older version, since I originally rooted this phone around 18 months ago and used a version from back then. I watched a youtube video how to push TWRP onto a soft bricked device using ADB. After that, I was able to install the ROM.
Budee80 said:
Thanks dude. I had an older version, since I originally rooted this phone around 18 months ago and used a version from back then. I watched a youtube video how to push TWRP onto a soft bricked device using ADB. After that, I was able to install the ROM.
Click to expand...
Click to collapse
glad i could help with just a question
Hello,
I fear my daughters european HTC Desire 510 is bricked. First of all, we have already given up on what is on the phone. So no worries if a solution means wiping EVERYTHING from the phone, as long as we can get it to start again.
For some unknown reason, possibly an update the phone went into an almost constant bootloop a month or so before christmas. It could eventually get to the login screen, after going in circles for anything between 20 mins and hours. So I thought I would try to tamper with it. I know how to get into the bootloader from rooting other phones, so I went there to try to reset the phone to the factory settings. The result was that the phone now wouldn't go there again. If I tried to do a second reset it went straight to boot, without any way to interrupt, same thing when trying to go into recovery, instant reboot in the blink of an eye.
What then happens when the phone reboots? It gets to the first screen, green HTC logo and "Powered by Android", it sits there for maybe 30 seconds, then it goes black, buzz and back to the previous HTC logo. And this goes on until the battery dies, I pull the battery or I quickly push the vol down and power buttons to go into HBOOT.
I usually don't give up this easily. I found another thread here on some european guy having trouble with his Desire 510, and one of the answers linked to a RUU for a european 510. So I thought, why not, I hadn't unlocked the bootloader yet. So I downloaded the RUU and tried to install it. It messed with me a little, aparently as expected, and then ran through the whole installation. Before the upgrade, well downgrade to be specific the OS was ver. 1.51.401.4 but now claims to be 1.51.401.1. Problem though is, absolutely no change in behaviour. I have restarted the phone after pulled the battery and waited for anything between seconds and an hour, and the phone does exactly the same thing. It happily goes into HBOOT but won't allow me to do a factory reset, nor will it allow me to access recovery.
It will allow me to access Fastboot though, so I thought, hmmm if I install ClockWorkMod or TWRP, maybe something will change. Since I'm more used to working with CWM I went down that road, went to htcdev.com, got the unlock code and unlocked the phone. It now says <<< UNLOCKED >>> and I ran the fastboot devices command, that happily returned some "CC4********7 fastboot". So I went ahead and installed CWM, the installation went all the way and in the end it happily stated that CWM was installed. But did that mean any difference, noooo. If I try to access either Recovery, that should start CWM or Factory reset and also Check smartsd, instant reboot. And I mean INSTANT. Fastboot works, as already stated. I can also get into Image CRC and Show barcode, but what good is that.
Any ideas. I'm beginning to think that something is physically broken inside the phone.