Database Develop

Can I unroot from fastboot?

I Can Only Access Fast Boot And RECOVERY. Is there any way to unroot and and put my phone back in stock mode from here? Stock recovery. I don't care if I can't install the stock ROM. I just need this area to be stock so i can send the phone to warranty
Sent from my myTouch 4G using xda app-developers app

dpshptl said:
I Can Only Access Fast Boot And RECOVERY. Is there any way to unroot and and put my phone back in stock mode from here? Stock recovery. I don't care if I can't install the stock ROM. I just need this area to be stock so i can send the phone to warranty
Sent from my myTouch 4G using xda app-developers app
Click to expand...
Click to collapse
Why do you only need a stock recovery to send it to warranty?
For warranty, as far as I can tell, you need a LOCKED bootloader (not RELOCKED), and no TAMPERED, and stock firmware and ROM.
You could check out my guide, on how to return 100% back to stock.

nkk71 said:
Why do you only need a stock recovery to send it to warranty?
For warranty, as far as I can tell, you need a LOCKED bootloader (not RELOCKED), and no TAMPERED, and stock firmware and ROM.
You could check out my guide, on how to return 100% back to stock.
Click to expand...
Click to collapse
The problem is my phone was stock and running kitkat just a few days ago. Then one day i used it and the screen flashed a few times the buttons on the bottom flashed a few times. Then it reboot itself and got stuck. I could never go back from there. I tried a few diff things nothing worked. So I ended up rooting and installing a custom ROM. All was fine but when I reboot it would get stuck again. Sometimes it would auto reboot and get stuck. The only thing I could do is wipe and reinstall a ROM and it would be fine as long as it did not reboot.
So i would like to undo my root and return my phone. The only problem is I can only access the bootloader.
Here is the fastboot getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.24.3263.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.531.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3821mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s

dpshptl said:
The problem is my phone was stock and running kitkat just a few days ago. Then one day i used it and the screen flashed a few times the buttons on the bottom flashed a few times. Then it reboot itself and got stuck. I could never go back from there. I tried a few diff things nothing worked. So I ended up rooting and installing a custom ROM. All was fine but when I reboot it would get stuck again. Sometimes it would auto reboot and get stuck. The only thing I could do is wipe and reinstall a ROM and it would be fine as long as it did not reboot.
So i would like to undo my root and return my phone. The only problem is I can only access the bootloader.
Here is the fastboot getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.24.3263.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.531.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3821mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Click to expand...
Click to collapse
I have already explained to you their is no T-mobile RUU for your version
all you can do is flash the GURU Reset and install stock recovery and take the OTA and send your phone back

If you can get s off you can go back to stock t mobile. I did it with my o2-UK phone. But you def need s off first
Sent from my HTC One using xda app-developers app

The problem with this is it requires s-off. From my understanding I can't gain s-off from where my phone is stuck. Correct me if I'm wrong.
Sent from my myTouch 4G using xda app-developers app

Have you tried using firewater to get s off? If it doesn't work, as mentioned above, guru reset only option
Sent from my HTC One using xda app-developers app

dpshptl said:
The problem with this is it requires s-off. From my understanding I can't gain s-off from where my phone is stuck. Correct me if I'm wrong.
Sent from my myTouch 4G using xda app-developers app
Click to expand...
Click to collapse
no the Guru reset does not require s-off
you flash it like a rom and choose to install stock recovery during install
---------- Post added at 06:32 PM ---------- Previous post was at 06:27 PM ----------
dpshptl said:
The problem with this is it requires s-off. From my understanding I can't gain s-off from where my phone is stuck. Correct me if I'm wrong.
Sent from my myTouch 4G using xda app-developers app
Click to expand...
Click to collapse
Read this page very carefully you will need a usb otg cable to use a mouse to control you phone if you use the old t-mobile reset
http://www.htc1guru.com/downloads/stock-rom-downloads/

No the guru reset does not require s off. It will not be stock t mobile though as well
Sent from my HTC One using xda app-developers app

Now I have a new problem. The phone boot up somehow and went to the lock screen. I cant do anything there though. The screen is not responsive. Vol up and down turns the vol up and down. Holding down the power button does not reboot or turn off the phone. A message says hold for 3, 2, 1 sec and the phone will reboot. But nothing happens. I have been holding the power button down for mins at a time while pushing and not pushing the vol buttons and the home buttons.

clsA said:
I have already explained to you their is no T-mobile RUU for your version
all you can do is flash the GURU Reset and install stock recovery and take the OTA and send your phone back
Click to expand...
Click to collapse
But how is he going to get LOCKED not relocked?
dpshptl said:
Now I have a new problem. The phone boot up somehow and went to the lock screen. I cant do anything there though. The screen is not responsive. Vol up and down turns the vol up and down. Holding down the power button does not reboot or turn off the phone. A message says hold for 3, 2, 1 sec and the phone will reboot. But nothing happens. I have been holding the power button down for mins at a time while pushing and not pushing the vol buttons and the home buttons.
Click to expand...
Click to collapse
you flashed a 1.xx rom on a 2.xx+ firmware, and @clsA mentioned in his post: "you will need a usb otg cable to use a mouse to control you phone if you use the old t-mobile reset"

I tried the guru reset but no luck. The process finished with no errors but when bootloader rebooted the phone was still in tampered and unlocked mode.
What is the old t-mobile reset method? I have an OTG cable and a mouse just need instructions or a link.

dpshptl said:
I tried the guru reset but no luck. The process finished with no errors but when bootloader rebooted the phone was still in tampered and unlocked mode.
What is the old t-mobile reset method? I have an OTG cable and a mouse just need instructions or a link.
Click to expand...
Click to collapse
The guru reset was to get your phone working again .. you now need to work on getting s-off so you can remove the tampered and lock the phone to return it

clsA said:
The guru reset was to get your phone working again .. you now need to work on getting s-off so you can remove the tampered and lock the phone to return it
Click to expand...
Click to collapse
All methods to get s_off requires the phone to boot up all the way. How do I get s_off from bootloader

dpshptl said:
All methods to get s_off requires the phone to boot up all the way. How do I get s_off from bootloader
Click to expand...
Click to collapse
install the guru reset .. your phone should boot up

The problem I'm having is even if I hey the phone back up. When it needs to reboot again it will get stuck at the splash screen and I'm back to where I started. Whenever I need to reboot to finish a process the phone hangs and I'm screwed. I have do so many things and wiped the pogo few so many times nothing helps. All install and updates and fast boot commands and everything works fine until the reboot.

dpshptl said:
The problem I'm having is even if I hey the phone back up. When it needs to reboot again it will get stuck at the splash screen and I'm back to where I started. Whenever I need to reboot to finish a process the phone hangs and I'm screwed. I have do so many things and wiped the pogo few so many times nothing helps. All install and updates and fast boot commands and everything works fine until the reboot.
Click to expand...
Click to collapse
I'm out of ideas maybe @nkk71 can think of something else
Did you flash the Guru reset and install stock recovery and then do a factory reset / wipe caches?

nkk71 said:
But how is he going to get LOCKED not relocked?
you flashed a 1.xx rom on a 2.xx+ firmware, and @clsA mentioned in his post: "you will need a usb otg cable to use a mouse to control you phone if you use the old t-mobile reset"
Click to expand...
Click to collapse
clsA said:
I'm out of ideas maybe @nkk71 can think of something else
Did you flash the Guru reset and install stock recovery and then do a factory reset / wipe caches?
Click to expand...
Click to collapse
Yeah guru flashed without any problems. Then auto rebooted into bootloader, where it was still tampered and unlocked. I went into recovery but it just kept looping to boatloader. So i flashed TWRP again and wiped everything and here I am. I think its some major hardware problem because whenever the phone reboots from anywhere on the phone, it starts looping and hanging. The phone has been wiped clean so many times and had everything installed from a jump drive. So I cant imagine something being left on there that is causing the problem.

Can someone give me a link to the stock RUU. I'm confused between all of them. The phone seems to be stable now. I reboot it several times and it works. But I do need to use a mouse cuz the touch screen does not work.

Their is no RUU
You need to start working on getting s_off
Sent from my HTC One_M8 using Tapatalk

[Q] HTC One M7 (AT&T-US) Stuck in Boot Loop

My AT&T HTC One is stuck in a continuous boot loop. It flashes to the HTC splash screen for roughly 7 seconds, turns off for roughly 5 seconds, then on again. It will do this until the battery is fully depleted. Plugging the phone into my PC yields no results as the boot loop triggers a "device is not plugged in" error message over and over on my windows 7 PC. I am able to access the recovery mode holding down the power button and volume down rocker but once in recovery mode the phone promptly reboots itself back into the continuous boot loop, I have a window of a couple of seconds to navigate options in recovery mode. Stranger still is that my up and down volume buttons seem to be less responsive, sometimes I am only able to move up, other times only down. I can select recovery if I am fast enough, which takes me to the HTC splash screen with the text "Entering recovery..." however the phone then reboots back into the boot loop.
My recovery menu:
M7-UL PVT SHIP S-ON RH
HBOOT-1.55.0000
OPEN DSP-v31.120.274.0617
OS 3.17.502.3
eMMC Boot 2048 MB
I am running stock odexed 4.3 with the Sense skin
Drivers cannot be installed on my PC due to the continuous resetting and navigating the recovery menu is borderline impossible.
After being severely annoyed by the bloatware that comes with the OTA firmware updates from AT&T I rooted my phone and installed the ARHD custom rom. It has worked flawlessly for about 3 months until yesterday 5/3/2014 the phone began the boot loop while it was sitting on my desk idle for about an hour. Plugging the phone into the charger yields no visible changes either (the charging indicator light does not turn on). Last night the phone boot-looped itself into a depleted battery. I plugged it in and after 5 minutes of charging I was able to get it to boot so I chose to boot it into safe mode. I had to get to bed and was unable to troubleshoot the phone further so I left the phone in safe mode, only to find it in the boot loop around 5-6:00 this morning. I am going to let the battery drain again and try to do a cache wipe once I can get the thing into safe mode. Any help on this issue would be much appreciated.

svenell said:
My recovery menu:
M7-UL PVT SHIP S-ON RH
HBOOT-1.55.0000
OPEN DSP-v31.120.274.0617
OS 3.17.502.3
eMMC Boot 2048 MB
I am running the HTC Sense skin of Android Revolution HD 4.3
Drivers cannot be installed on my PC due to the continuous resetting and navigating the recovery menu is borderline impossible.
Click to expand...
Click to collapse
First question ARHD 4.3 ?? (Sense Edition)? link please
second, let's start with the basics:
Force reboot: press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)
how stable is bootloader? all good?
If yes, copy/paste a "fastboot getvar all" (excluding IMEI and s/n)

@nkk71 Thanks for the prompt response!
Out of left field my phone left the boot loop after 4 hours and I was able to get it to boot normal. I entered the recovery menu and was able to get into CWMR 6.0.4.3 where I wiped the cache partition. So far the phone seems stable. Any measures I need to take to prevent this problem from occurring in the future?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ~~~~~~~~~~
(bootloader) imei: ~~~~~~~~~~
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4088mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.057s
I also misspoke, I am running a stock odexed 4.3 with Sense.

svenell said:
@nkk71 Thanks for the prompt response!
Out of left field my phone left the boot loop after 4 hours and I was able to get it to boot normal. I entered the recovery menu and was able to get into CWMR 6.0.4.3 where I wiped the cache partition. So far the phone seems stable. Any measures I need to take to prevent this problem from occurring in the future?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
I also misspoke, I am running a stock odexed 4.3 with Sense.
Click to expand...
Click to collapse
well that looks all good... could it be some debris in the phone's USB port? or the charger and/or cable is going bad? or even a bad power button?
(just a couple of guesses, nothing concrete... but worth checking anyway)

nkk71 said:
well that looks all good... could it be some debris in the phone's USB port? or the charger and/or cable is going bad? or even a bad power button?
(just a couple of guesses, nothing concrete... but worth checking anyway)
Click to expand...
Click to collapse
Thanks again for the help nkk71. So far so good, the USB port seems to be clear and functioning, and I did a key test in the recovery menu and the power button seems responsive to my clicks.
I am thinking about updating to the ARHD 53.0 (4.4.2+ HTC Sense 5.5) In hopes that it might fix any issues that could be going on causing my phone to be prone to boot loops. I just need to do some research before I update to make sure its safe.

svenell said:
Thanks again for the help nkk71. So far so good, the USB port seems to be clear and functioning, and I did a key test in the recovery menu and the power button seems responsive to my clicks.
I am thinking about updating to the ARHD 53.0 (4.4.2+ HTC Sense 5.5) In hopes that it might fix any issues that could be going on causing my phone to be prone to boot loops. I just need to do some research before I update to make sure its safe.
Click to expand...
Click to collapse
Sure no problem.
But, if you're going for a 4.4 ROM, then you need to get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
2.7.0.4b: http://forum.xda-developers.com/showthread.php?t=2708134
in bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
CWM is not fully compatible with 4.4 ROMs yet..... just a heads up

Thanks for the heads up! I guess this is considered SOLVED, however it was sheer luck that the boot loop stopped and I was able to get into the phone. Thanks again for the help

[Q] HTC ONE (M7UL) imei problems + rebooting + s-on

Hi you all,
So to start things off i might say i tried alot of things to revive my htc one.
What happenend?
I wanted to give my htc one some new life so I thought lets factory reset it. All worked well but then the horror just began. My One began rebooting and rebooting itself over and over. So what i did next was enabled flight mode throught the power button and restarted the phone. So from then on it was running for about 30 seconds untill it starts rebooting again.
So what I did is unlock the phone and tried several Custom Roms. The only ones working are old cm11 roms, but I can not get S-Off to reflash the firmware because I am stuck with an eMMC 9001xxxxx... chip, so I guess bad luck for me.
So now my phone will not detect ANY SIM Card and will not show any imei number or baseband in the os. In the bootloader however they are still there, both of them.
RUU's will not work for me as I am S-ON and stuck on hboot 1.57
SunShine is not working either as my phone shuts down after aprox. 30 seconds on sense rom.
Firewater is not working either as it has an 9001.... eMMC chip.
my getvar stats:
PHP:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3972mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
So my question is are there still any suggestions for me, that I didn't do or just overlooked?
So I would appreciate anything, before tearing it apart..
Cheers

shieldeverything said:
Hi you all,
So to start things off i might say i tried alot of things to revive my htc one.
What happenend?
I wanted to give my htc one some new life so I thought lets factory reset it. All worked well but then the horror just began. My One began rebooting and rebooting itself over and over. So what i did next was enabled flight mode throught the power button and restarted the phone. So from then on it was running for about 30 seconds untill it starts rebooting again.
So what I did is unlock the phone and tried several Custom Roms. The only ones working are old cm11 roms, but I can not get S-Off to reflash the firmware because I am stuck with an eMMC 9001xxxxx... chip, so I guess bad luck for me.
So now my phone will not detect ANY SIM Card and will not show any imei number or baseband in the os. In the bootloader however they are still there, both of them.
RUU's will not work for me as I am S-ON and stuck on hboot 1.57
SunShine is not working either as my phone shuts down after aprox. 30 seconds on sense rom.
Firewater is not working either as it has an 9001.... eMMC chip.
my getvar stats:
PHP:
(bootloader) version: 0.5(bootloader) version-bootloader: 1.57.0000(bootloader) version-baseband: 4A.21.3263.04(bootloader) version-cpld: None(bootloader) version-microp: None(bootloader) version-main: 6.09.401.10(bootloader) version-misc: PVT SHIP S-ON(bootloader) serialno: (bootloader) imei: (bootloader) meid: 00000000000000(bootloader) product: m7_ul(bootloader) platform: HBOOT-8064(bootloader) modelid: PN0710000(bootloader) cidnum: HTC__102(bootloader) battery-status: good(bootloader) battery-voltage: 3972mV(bootloader) partition-layout: Generic(bootloader) security: on(bootloader) build-mode: SHIP(bootloader) boot-mode: FASTBOOT(bootloader) commitno-bootloader: dirty-6d8a0b9b(bootloader) hbootpreupdate: 11(bootloader) gencheckpt: 0
So my question is are there still any suggestions for me, that I didn't do or just overlooked?
So I would appreciate anything, before tearing it apart..
Cheers
Click to expand...
Click to collapse
You don't need s-off to flash firmware. You only need s-off to downgrade or to use custom firmware. You will however need to relock your bootloader. Although I should tell you Unknown imei & Baseband often turns out to be a hardware problem.
You can flash this firmware with a relocked bootloader. You will need to 're flash custom recovery and Rom to boot the phone afterwards. Unless you flash a stock Rom first, Stock Rom can be downloaded here http://forum.xda-developers.com/htc-one/development/rom-4-4-3-sense-6-6-09-401-5-100-stock-t2854300
Firmware download
http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/6.09.401.10.zip
Download it and put it in your fastboot folder and rename it firmware.zip.
Reboot the phone to the bootloader and Connect fastbootusb. Now open your Fastboot command line and type
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Code:
fastboot oem rebootRUU
--- case sensitive. ---^^^
The phone will reboot to a black screen with a Silver HTC LOGO. This is RUU mode. Now we're going to flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash will be short. It's just a preupdate preparing the hboot for the new firmware. So we need to do the same command again.
Code:
fastboot flash zip firmware.zip
The second flash will take a little longer and this time it will flash the full firmware. The progress bar on the phone screen will not reach 100% this is normal as long as the command window has completed its output the flash is done.
Code:
fastboot reboot-bootloader
If you found my posts helpful, no need to say thanks. There's a button for that

Danny201281 said:
You don't need s-off to flash firmware. You only need s-off to downgrade or to use custom firmware. You will however need to relock your bootloader. Although I should tell you Unknown imei & Baseband often turns out to be a hardware problem.
You can flash this firmware with a relocked bootloader. You will need to 're flash custom recovery and Rom to boot the phone afterwards. Unless you flash a stock Rom first, Stock Rom can be downloaded here http://forum.xda-developers.com/htc-one/development/rom-4-4-3-sense-6-6-09-401-5-100-stock-t2854300
Firmware download
http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/6.09.401.10.zip
Download it and put it in your fastboot folder and rename it firmware.zip.
Reboot the phone to the bootloader and Connect fastbootusb. Now open your Fastboot command line and type
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Code:
fastboot oem rebootRUU
--- case sensitive. ---^^^
The phone will reboot to a black screen with a Silver HTC LOGO. This is RUU mode. Now we're going to flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash will be short. It's just a preupdate preparing the hboot for the new firmware. So we need to do the same command again.
Code:
fastboot flash zip firmware.zip
The second flash will take a little longer and this time it will flash the full firmware. The progress bar on the phone screen will not reach 100% this is normal as long as the command window has completed its output the flash is done.
Code:
fastboot reboot-bootloader
If you found my posts helpful, no need to say thanks. There's a button for that
Click to expand...
Click to collapse
Ok cheers m8!
I am gonna try it right now. Yeah I heard about the hardware problem, but I was thinking mine might be not because it happened after a factory reset (done in the os itself). I once was able to bring back baseband and imei but I just can't remember what exactely I did.
So I am going to report back as soon as I tried. I am wondering.
Btw you know what hardware defect actually would cause it (just wondering)
Thx!

shieldeverything said:
Ok cheers m8!
I am gonna try it right now. Yeah I heard about the hardware problem, but I was thinking mine might be not because it happened after a factory reset (done in the os itself). I once was able to bring back baseband and imei but I just can't remember what exactely I did.
So I am going to report back as soon as I tried. I am wondering.
Btw you know what hardware defect actually would cause it (just wondering)
Thx!
Click to expand...
Click to collapse
With your phone s-on and on the latest firmware there's not much else you can do but flash the firmware package I linked. If you can get s-off you can try an ruu.
From a hardware perspective It's the antenna connector pin that causes the issue as far as I'm aware. I only know of one that was repaired without returning to HTC and the antenna connector pin was the cause. Replacing it solved the problem.
If you found my posts helpful, no need to say thanks. There's a button for that

Danny201281 said:
With your phone s-on and on the latest firmware there's not much else you can do but flash the firmware package I linked. If you can get s-off you can try an ruu.
From a hardware perspective It's the antenna connector pin that causes the issue as far as I'm aware. I only know of one that was repaired without returning to HTC and the antenna connector pin was the cause. Replacing it solved the problem.
If you found my posts helpful, no need to say thanks. There's a button for that
Click to expand...
Click to collapse
So I did everything and it worked. But only for 5-10 minutes and then it startet rebooting again and again. So I guess this is a hardware problem too and as I don't have any warranty or something there my m7ul goes...
Thx for your help anyways!

[Q] Desire 500 not booting and 7 vibrate

Hi.
My Desire 500 after Press Power Button no booting and 7 times vibrate and Stay in HTC Logo.
Please help me to solve this problem would.
thanks.

ehsanvaniusha said:
Hi.
My Desire 500 after Press Power Button no booting and 7 times vibrate and Stay in HTC Logo.
Please help me to solve this problem would.
thanks.
Click to expand...
Click to collapse
What happened before that?

Htc desire 500 not Power on but LED blinking
I am also got same problem, I unlocked my phone 2 weeks back but am not installing SuperSu but my mobile works well after that. Two days back my phones battery drained fully after i charge my phone it automatically goes to CWM Recovery but i am not doing anything in CWM just came back. After my phone not charging but led light blinking.
I tried to Cover Middle two Ports in battery with plastic, but it not works. So I tried to Charge my battery using Battery charger, this also not works, finally i removed sd card, sim card, battery and leave it for 5hours then i try to switch on, but not works.
So please help me to recover my phone

My HTC doesnt turn on
i unlocked my desire 500 bootloader few days ago. and installed cwm recovery. and the last night my mobile attery drained out totally.
since then, mobile is not starting. if trying to boot into bootloader...it vibrates for 7 times and thats it!
ive tried all possible ways to turn it on. charged it for 3+ hours. still its helpless. please help me!

vkrishna126 said:
i unlocked my desire 500 bootloader few days ago. and installed cwm recovery. and the last night my mobile attery drained out totally.
since then, mobile is not starting. if trying to boot into bootloader...it vibrates for 7 times and thats it!
ive tried all possible ways to turn it on. charged it for 3+ hours. still its helpless. please help me!
Click to expand...
Click to collapse
Hold power button and connect charger. Hold the button until phone power on.

vkrishna126 said:
i unlocked my desire 500 bootloader few days ago. and installed cwm recovery. and the last night my mobile attery drained out totally.
since then, mobile is not starting. if trying to boot into bootloader...it vibrates for 7 times and thats it!
ive tried all possible ways to turn it on. charged it for 3+ hours. still its helpless. please help me!
Click to expand...
Click to collapse
Hi there
Take out the battery for half an hour and then try again.
You can get into hboot
The problem is cwm
ufonek said:
Hold power button and connect charger. Hold the button until phone power on.
Click to expand...
Click to collapse
I did not try this way
I had the same problem but the problem was solved after another flash cwm
Sorry for my bad english

ufonek said:
Hold power button and connect charger. Hold the button until phone power on.
Click to expand...
Click to collapse
its not working. its only vibrating 7 times.
---------- Post added at 11:06 AM ---------- Previous post was at 10:41 AM ----------
monem2222 said:
Hi there
Take out the battery for half an hour and then try again.
You can get into hboot
The problem is cwm
its not working either.
Click to expand...
Click to collapse

vkrishna126 said:
its not working. its only vibrating 7 times.
---------- Post added at 11:06 AM ---------- Previous post was at 10:41 AM ----------
monem2222 said:
Hi there
Take out the battery for half an hour and then try again.
You can get into hboot
The problem is cwm
its not working either.
Click to expand...
Click to collapse
It takes a very long time. Maybe 20 seconds. Do not release the button.
Click to expand...
Click to collapse

Had the same problem and tried everything you have suggested here and none worked. Had to send it for repair, it turned out it was a fabric defect in the mother board.

Hi
i have almost same problem , phone is Desire 500 , ONE SIM
phone was updating via wifi and its hang and restart and now the situation is phone is hang on HTC logo in case its power up
most of the times its didnt power up only 7 times vibration i try all recommendation to keep battery out for few hours and put back and try again
and all is the same
i power phone , keep vibrate , i hold the VOL down for few time , its booted into bootloader , here it the details
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.02.0001
(bootloader) version-baseband: 14.11.36Q4.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.20.401.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT3A7WE02854
(bootloader) imei: XXXXXXXXXXXXXXXXX
(bootloader) meid:
(bootloader) product: z4u
(bootloader) platform: HBOOT-8x25Q
(bootloader) modelid: 0P3Z11200
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4120mV
(bootloader) partition-layout: HTC
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-455c2e73
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
i read some posts about unlock bootloader and flash recovery and flash custom rom , i download all files , but when i try to unlockboot loader
i got very strange thing , i flash the unlock bin file , it gaves me YES or no to unlock boot loader , i press Yes and power , it dosent make anything
i press many times on the power button , but nothing , i go to NO and press power button , it works and phone restart again to 7 Vibrate mode
my method to unlock bootloader via HTCdev and i select 1 time Desire* and another time i select other supported models , and same
i search for RUU to flash it anywhere but i cant find any
really its most stange problem i have met in my life
please if anybody have suggestion ,let me know
Thanks

vibrate 7 times
i have almost same problem , phone is Desire 500 , DUAL SIM
phone was updating via wifi and its hang and restart and now the situation is phone is hang on HTC logo in case its power up
most of the times its didnt power up only 7 times vibration i try all recommendation to keep battery out for few hours and put back and try again
and all is the same
i power phone , keep vibrate , i hold the VOL down for few time , its booted into bootloader , here it the details
INFOversion: 0.5
INFOversion-bootloader: 1.03
INFOversion-baseband: 14.15.
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.26.401.2
INFOversion-misc: PVT SHIP S
INFOserialno: HT3ASWE00850
INFOimei: 357654052335273
INFOmeid:
INFOproduct: z4dug
INFOplatform: HBOOT-8x25Q
INFOmodelid: 0P3Z10000
INFOcidnum: HTC__032
INFObattery-status: low
INFObattery-voltage: 3380mV
INFOpartition-layout: HTC
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dir
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
finished. total time: 0.025s
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.03.0001
(bootloader) version-baseband: 14.15.50QD.26
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT3ASWE00850
(bootloader) imei: 357654052335273
(bootloader) meid:
(bootloader) product: z4dug
(bootloader) platform: HBOOT-8x25Q
(bootloader) modelid: 0P3Z10000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: low
(bootloader) battery-voltage: 3380mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e9f20193
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s
i read some posts about unlock bootloader and flash recovery and flash custom rom , i download all files , but when i try to unlockboot loader
i got very strange thing , i flash the unlock bin file , it gaves me YES or no to unlock boot loader , i press Yes and power , it dosent make anything
i press many times on the power button , but nothing , i go to NO and press power button , it works and phone restart again to 7 Vibrate mode

zecktu2004 said:
but when i try to unlockboot loader
i got very strange thing , i flash the unlock bin file , it gaves me YES or no to unlock boot loader , i press Yes and power , it dosent make anything
i press many times on the power button , but nothing , i go to NO and press power button , it works and phone restart again to 7 Vibrate mode
Click to expand...
Click to collapse
I have the same problem

zecktu2004 said:
... when i try to unlockboot loader
i got very strange thing , i flash the unlock bin file , it gaves me YES or no to unlock boot loader , i press Yes and power , it dosent make anything
i press many times on the power button , but nothing , i go to NO and press power button , it works and phone restart again to 7 Vibrate mode
Click to expand...
Click to collapse
System_F said:
I have the same problem
Click to expand...
Click to collapse
+1
Same here. I lost all my hope on the device. I will never buy an HTC phone anymore. The google nexus phones do not have this stuped boot lock or restrictions, right? If that's right, my next phone will be a nexus.

7 or 5 times vibrating on boot mean security zone is damaged. Only JTAG or DireceEMMC method can solve Your problem. Or You can send phone to warranty service.

kwaku85, thanks for the info. They connected it to a jtag box. Nothing worked. They said something about a chip or memory problem which they are waiting the part to arrive. They said there is only a little chance for it to work.

Yea I have same problem and after read all these posts in this topic... I lost my hope...
I have unlock bootloader but s-on.... I can't flash,recovery T_T nothing...

You can repair your phones, I had the same problem (vibrating 7 times). In the general thread see my guide, you will find the links for the RUU files

http://forum.xda-developers.com/desire-500/general/how-to-to-htc-stock-rom-solve-boot-t3239984

HTC desire 500 stuck on fastboot
Hello,
I have the same problem (vibrate 7 times at boot and stuck at HTC logo). This happend about a mounth after i installed the ROM from this post: http://forum.xda-developers.com/desire-500/development/rom-htc-desire-500-dualsim-cleanrom-t2812995
Custom Rom for the Desire 500 dualsim CleaN Rom v0.99beta.
now everytime i'm tring to write with fastboot any boot.img, recovery.img i'm getting the error: FAILED: remote: image update error
Please help what can i do?
Thnak you.
Z4DUG PVT SHIP S-ON RL
HBOOT-1.03.0001
RADIO-14.15.50QD.26
OS-1.26.401.2
eMMC-boot
Apr 2 2014,22:06:44.0

asiq.89 said:
I am also got same problem, I unlocked my phone 2 weeks back but am not installing SuperSu but my mobile works well after that. Two days back my phones battery drained fully after i charge my phone it automatically goes to CWM Recovery but i am not doing anything in CWM just came back. After my phone not charging but led light blinking.
As I faced this problem many times
I had find ( not proper)solution that is to remove battery if fully drained and charge battery from other phone to 5-10min and put battery to desire 500 i keep charged It will boot up to Cmw recovery and just power on it
2. To Charge Phone to Pc or Laptop it will bootup be patience .Sorry To my English
Click to expand...
Click to collapse

[Q] Possible Hard Brick. How can I fix it?

Dear XDA-Developers Forum,
I require your help fixing my HTC One M7.
When I tried to use an RUU to set it back to stock firmware the RUU.exe returned error 155. Maybe I did something wrong. I have some experience flashing different phones but I'm not a pro like most people here..
Anyway, the phone hung at the black screen with the HTC logo. At some point I managed to reconnect to the bootloader and Fastboot commands were still available. I tried using Fastboot to verify I had the correct RUU which to all appearance was the case. After trying to reboot to system the phone is stuck in a loop. It displays the CM logo from the ROM it had previously installed.
From here, I'm stuck. Power button does not work, combinations to go into bootloader don't work. The only thing that does work is holding power and vol+ and vol- at the same time. This makes the phone reboot (showing white HTC screen with green logo). After a few seconds I am however stuck with the CM logo.
Is there a way to fix this?
Some additional info on my device:
HBoot 1.55
Bootloader unlocked
S-ON (although that's strange cause I had it turned off before)
CM 10.2 installed
TWRP 2.8.5.0
I hope someone has a solution. Of course all drivers and software are up to date and I have backup of my relevent data. I fear that I will need to get a replacement since extensive Google-Search would not yield a solution so far. It could be I'm just not educated enough to understand.
Best regards
Nick

Little Update
Without any chance of turning the device off and re-entering bootloader or recovery I waited until the battery finally died.
I plugged it into the wall charger. I was then finally able to start to the bootloader. It looked very usual. The security alert had disappeared and it was in HBoot mode.
I went on and selected factory reset guessing this to be the easiest and quite likely solution to the bootloop. TWRP started but showed a number of mounting errors and did not finish the operation. After auto-restart I'm back at the bootloop from the start.
Waiting for the battery to die again...
Any suggestions what I should do next?

DNK83 said:
Without any chance of turning the device off and re-entering bootloader or recovery I waited until the battery finally died.
I plugged it into the wall charger. I was then finally able to start to the bootloader. It looked very usual. The security alert had disappeared and it was in HBoot mode.
I went on and selected factory reset guessing this to be the easiest and quite likely solution to the bootloop. TWRP started but showed a number of mounting errors and did not finish the operation. After auto-restart I'm back at the bootloop from the start.
Waiting for the battery to die again...
Any suggestions what I should do next?
Click to expand...
Click to collapse
Error 155 means your using the wrong RUU
You don't need to keep waiting for the battery to die, hold down the volume down button and the power button together, keep them held down, the captive lights on the bottom will flash about 15 times, when the phone goes off, let go of the power button only, the phone should now boot to the bootloader.
post your fastboot getvar all without imei and serial number please, anyone here needs more info about your phone before we can help and this will tell us all everything we need to know.

Hello,
thanks for your reply.
I have tried holding the power button and vol- together. Even after more than 30 seconds the phone does not react and keeps on showing the CM logo.
Sorry, for not providing more information. I would've posted the getvar info before but was not able to connect through fastboot.
Will do once the battery is charged enough for the next try.

After the battery dying and charging a little bit I was able to go into fastboot mode. The loader screen was showing "fastboot usb". Trying to obtain the variables yields:
C:\fastboot>fastboot getvar (all)
getvarall) FAILED (remote: unknown command)
finished. total time: 0.016s

DNK83 said:
After the battery dying and charging a little bit I was able to go into fastboot mode. The loader screen was showing "fastboot usb". Trying to obtain the variables yields:
C:\fastboot>fastboot getvar (all)
getvarall) FAILED (remote: unknown command)
finished. total time: 0.016s
Click to expand...
Click to collapse
take the brackets off the all () the command is fastboot getvar all

DNK83 said:
After the battery dying and charging a little bit I was able to go into fastboot mode. The loader screen was showing "fastboot usb". Trying to obtain the variables yields:
C:\fastboot>fastboot getvar (all)
getvarall) FAILED (remote: unknown command)
finished. total time: 0.016s
Click to expand...
Click to collapse
Why the brackets () in "fastboot getvar (all)" ? The command is "fastboot getvar all" without the quotes.

C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.206.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3684mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s

alray said:
Why the brackets () in "fastboot getvar (all)" ? The command is "fastboot getvar all" without the quotes.
Click to expand...
Click to collapse
The brackets are added because I'm tired and kinda angry.

DNK83 said:
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.206.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3684mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Click to expand...
Click to collapse
first of all I recommend you flash twrp 2.8.6.0 from here, it will make life easier for you: https://dl.twrp.me/m7/twrp-2.8.6.0-m7.img.html
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
then enter twrp, and create a very simple backup, just something like boot or cache.
now plug your phone into the computer, it should open on your computer as this version of twrp supports MTP, navigate to the TWRP backup folder on your phone and delete the backup file from the folder (just the backup file itself, none of the folders) it will be in TWRP/BACKUP/PHONE SERIAL NUMBER/DATE AND OTHER DIGITS/ delete the file in here and replace with the files in this zip (make sure you extract the zip first): https://www.androidfilehost.com/?fid=95897840722646676
now unplug your phone and restore the backup.

The installation of TWRP worked fine. Trying to make the simple backup yields a bunch of failed attempts to mount.

DNK83 said:
The installation of TWRP worked fine. Trying to make the simple backup yields a bunch of failed attempts to mount.
Click to expand...
Click to collapse
in that case, select wipe, and then format data button, type yes to confirm, when done, select reboot to recovery for change to take effect, it will say no OS installed, just ignore it, it will also ask you if you would like to install super SU, select do not install, when the phone boots back to recovery, try backup again.

Okay.
I formatted the card and was able to do the backup. I was neither notified of a missing OS nor asked if I wanted to Install Super SU. Reboot to Recovery worked normal.
Plugging the phone into my computer does not yield a connection that I could use to copy files.

DNK83 said:
Okay.
I formatted the card and was able to do the backup. I was neither notified of a missing OS nor asked if I wanted to Install Super SU. Reboot to Recovery worked normal.
Plugging the phone into my computer does not yield a connection that I could use to copy files.
Click to expand...
Click to collapse
make sure you are on the recovery main screen when you plug the phone into your computer, no sub menu's.
If it still doesn't appear on your computer, double check your device manager to make sure its showing in there correctly.

A "Google Nexus ADB Interface" is listed. Is that what we're looking for?
Btw: many thanks for the help so far. It's becoming quite exciting right now.

DNK83 said:
A "Google Nexus ADB Interface" is listed. Is that what we're looking for?
Btw: many thanks for the help so far. It's becoming quite exciting right now.
Click to expand...
Click to collapse
Strange, it should look like this pict below, I'm using a HTC One M8, with the latest TWRP, but its the same thing as yours, as I previously had the M7.
try uninstall, that driver and then manually install the correct driver.
check Question 2 here on how to manually force the driver: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2

I have tried re-installing the HTC driver. So far no results. Did you want me to remove this ADB thing from the device manager? I am rebooting quickly to see if Win7 is the problem.

DNK83 said:
I have tried re-installing the HTC driver. So far no results. Did you want me to remove this ADB thing from the device manager? I am rebooting quickly to see if Win7 is the problem.
Click to expand...
Click to collapse
yes, just right click that other driver and uninstall it, then reboot.
I just download HTC sync manager and install that for my drivers, then just uninstall HTC sync, you will see the driver package which comes with sync manager just above it, leave that one alone, never had a problem with it.

The hardware detection ran when I plugged the phone in. The device is again listed as "Google Nexus ADB Device"
I have a package installed named "Minimal ADB and Fastboot Version 1.2". This is probably the reason why my phone is listed this way right now...uninstall?

DNK83 said:
The hardware detection ran when I plugged the phone in. The device is again listed as "Google Nexus ADB Device"
I have a package installed named "Minimal ADB and Fastboot Version 1.2". This is probably the reason why my phone is listed this way right now...uninstall?
Click to expand...
Click to collapse
strange, ive never seen it appear like that.
ive attached my adb and fastboot files below if you want to use those, maybe yours came with the google nexus driver.