Database Develop

Trouble with ONE

I'm having trouble with my phone. I am not a n00b, but i wouldn't call myself a professional either.
I've tried both revone and moonshine to root and flash a custom recovery and S-OFF, and none of them are having any success
I'm guessing i need recovery to work in order to flash the root files.
Every time i try flash the TWRP recovery (2.6), the CMD window reports success, but when the phone tries to boot into the recovery, all i get is a quick flash of a screen that looks like the one with the red warnings at the bottom, and then it reboots again going straight to my home screen
Take a look at my phone stats below, and let me know if it's compatible or not with current root/recovery/S-Off methods
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.980.17
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT364W906325
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__039
(bootloader) battery-status: good
(bootloader) battery-voltage: 4292mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.044s

OneCheekyDevil said:
I'm having trouble with my phone. I am not a n00b, but i wouldn't call myself a professional either.
I've tried both revone and moonshine to root and flash a custom recovery and S-OFF, and none of them are having any success
I'm guessing i need recovery to work in order to flash the root files.
Every time i try flash the TWRP recovery (2.6), the CMD window reports success, but when the phone tries to boot into the recovery, all i get is a quick flash of a screen that looks like the one with the red warnings at the bottom, and then it reboots again going straight to my home screen
Take a look at my phone stats below, and let me know if it's compatible or not with current root/recovery/S-Off methods
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.980.17
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__039
(bootloader) battery-status: good
(bootloader) battery-voltage: 4292mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.044s
Click to expand...
Click to collapse
In fastboot have you tried running
Code:
fastboot erase cache
then try rebooting into recovery?
Also you might want to clear out your serial number that you posted

Flash the recovery until you can see the tampered string
However, go s-off before flash the custom recovery, revone method don't need this

I have the same problem, going to try some of the above see if anything helps. Whats the recomended method.. what ive done so far
1) unlocked bootloader (shows unlocked)
2) flashed recovery
3) erased cache
Booting recovery essentially shows a screen flash (text that i cant read) and then boots the phone as normal. Do i need to worry about S-OFF ? as i didn't when i had a HTC one before (this is my second device)

Erasing cache didn't help.
I've tried using revone to S-Off, but i either get error -2 or error -6.
Really frustrating not knowing what those error codes mean to know what i need to change to have some success :/
With moonshine, i get about 2-3 reboots in, and then it fails telling me to unlock the bootloader with HTC - WHICH I ALREADY HAVE!!!
When i left my OneX because i couldn't S-OFF it, and went to the ONE, i thought S-OFF would've been as easy as it was with my Desire... obviously not

Thing is, i dont consider myself a Pro, but ive unlocked and flashed roms/recoveries on a fair number of android phones. I've had 2 HTC one's (this one, and a white one before it) the same process worked fine for the first HTC one - this one (recently bought) isnt having any of it.
Wondering if there is a problem with recent versions - same issue with OpenRecovery and Clockwork TOuch. The HTC one i have is a black 32GB asian model (ordered through mobility.com.au this week)

Everyone have the Tampered string?

Tampered string ? when ? usually i see that string when i'm booting a custom recovery. In this case the screen isnt on long enough to boot it, it's literally a flash of red text (fraction of a second) then it boots back into normal boot.
When should i see the tampered that you mention ?

When you will flash the recovery, you will see in bootloader screen the ****TAMPERED**** String.
IF you don't have this, you don't have the recovery installed.

Hmmm....
Something flashes very quickly before rebooting normally when i try to boot into recovery after a successful flash (aparently)
Dont think it's the TAMPERED string.
There's about 4-5 lines of red text at the bottom that comes up too quickly to read any of it.
I have the 64Gb version.
Android: 4.1.2
Software: 1.29.980.17
Kernel: 3.4.10-gcf4caea
[email protected] #1
In the HBOOT screen, it says the build date is May 3 2013

Strange, if you will flash the 2.5 version of the TWRP, it will work fine?

Guich said:
When you will flash the recovery, you will see in bootloader screen the ****TAMPERED**** String.
IF you don't have this, you don't have the recovery installed.
Click to expand...
Click to collapse
My bootloader says ' *** UNLOCKED ***' and obviously 'FASTBOOT USB' in bed.
Dont see tampered anywhere...on it.
When i try to go to boot recovery screen goes back, flash of 'some text' too fast to read' then back to normal HTC boot and back to normal boot.

acantril said:
My bootloader says ' *** UNLOCKED ***' and obviously 'FASTBOOT USB' in bed.
Dont see tampered anywhere...on it.
When i try to go to boot recovery screen goes back, flash of 'some text' too fast to read' then back to normal HTC boot and back to normal boot.
Click to expand...
Click to collapse
So, try to reflash the recovery until you will see tampered in the top of the screen

How many times ? i think i've spam flashed it maybe 30 times ? no tampered.

I was trying the 2.5 version initially, with no luck.
The process i'm doing from home screen is:
ADB REBOOT BOOTLOADER
(it reboots into bootloader. wait for fastboot-usb)
FASTBOOT FLASH RECOVERY OPENRECOVERY-TWRP-2.5.0.0-M7.IMG
sending 'recovery' (8006 KB)
OKAY [ 1.232s ]
writing 'recovery'
OKAY [ 0.064s ]
finished. total time: 1.872s
FASTBOOT ERASE CACHE (just in case measure)
erasing 'cache'
OKAY [ 0.062s ]
finished. total time: 0.062s
FASTBOOT REBOOT-BOOTLOADER
wait for phone to reboot to bootloader
select bootloader
select recovery
white HTC screen shows
something flashes quickly
phone switches off and switches back on to boot normally
no recovery

Waiit people, do you have fastboot on into the Settings -> Battery?

Ooops
feel like a n00b now.
When i first got the phone, i had switched it off.
Then i unlocked the bootloader via HTC.
Didn't realise when it factory wiped the phone, it'd be resetting the fastboot. (well DUH!)
NOW i have the tampered on the top! (dont mind the excitement here - it means i'm one step closer)
and we have success!!!!!!
GUICH, if you were here, i'd shmooch you!
Thanks for all your help and patience.
Maybe now i might be able to root and S-OFF the phone.
Have to feed my 4 month old who's been crying for my attention the last 30 mins, and then pick up the wife from work.
Will report back tonight if i have any troubles or successes.
Thanks again

Fastboot is OFF in settings -> Battery for me...
---------- Post added at 01:18 AM ---------- Previous post was at 01:17 AM ----------
OneCheekyDevil said:
I was trying the 2.5 version initially, with no luck.
The process i'm doing from home screen is:
ADB REBOOT BOOTLOADER
(it reboots into bootloader. wait for fastboot-usb)
FASTBOOT FLASH RECOVERY OPENRECOVERY-TWRP-2.5.0.0-M7.IMG
sending 'recovery' (8006 KB)
OKAY [ 1.232s ]
writing 'recovery'
OKAY [ 0.064s ]
finished. total time: 1.872s
FASTBOOT ERASE CACHE (just in case measure)
erasing 'cache'
OKAY [ 0.062s ]
finished. total time: 0.062s
FASTBOOT REBOOT-BOOTLOADER
wait for phone to reboot to bootloader
select bootloader
select recovery
white HTC screen shows
something flashes quickly
phone switches off and switches back on to boot normally
no recovery
Click to expand...
Click to collapse
Exactly the same for me, and i have fastboot OFF in settings battery.
Edit : Ok this is v.odd, turned fastboot off and on again, no change. Then did a hard reset on phone (as in press and hold power), then it booted back up, then dod ./adb reboot recovery and it went into recovery fine. Seems like the Fastboot was stuck on ON somehow ?

htc one bootlop brick

My htc One is bricked and i dont know what to do.
One day it just randomly prompted that it was going to power down and after that its been stuck in the bootloop cycle.
it only powers on to bootloop cycle when connected to a charger or pc after a period of time. The charging LED has been does not show.
I tried to launch recovery but it reboots before completing the process; infact it only stays in the bootloader screen for 5 secs before it reboots.
I've tried to fastboot erase cache and i get the error too many links, as the phone reboots back into the loop. also to note that when i plug in the htc one into the pc it tries to install it (when its in fast boot right before it reboots) but it cant because it says its unplug. (Ive tried many different cord, i even got a brand new oem cable from another htc one at the AT&T store)
the phone is rooted/unlock with a trickdroid and has been over 2 months without a issue.
I fear that the phone is gone....please help
i would even be willing to open the phone since its not under warranty....

I had my phone boot looping a couple days ago although the issue was because it did not have a rom nor recovery installed. I managed to get out of the boot loop and into the bootloader by holding both the up and down volume keys with the power button until the phone shut down, you should see the home and back keys flash 7 or 8 times before the screen shuts down. IMMEDIATELY after your screen powers down, release the keys you are currently holding and press the down volume and the power key, with any luck this should get you to the bootloader screen.

Wozzie said:
I had my phone boot looping a couple days ago although the issue was because it did not have a rom nor recovery installed. I managed to get out of the boot loop and into the bootloader by holding both the up and down volume keys with the power button until the phone shut down, you should see the home and back keys flash 7 or 8 times before the screen shuts down. IMMEDIATELY after your screen powers down, release the keys you are currently holding and press the down volume and the power key, with any luck this should get you to the bootloader screen.
Click to expand...
Click to collapse
I've been in the bootloader menu plenty of times, the problem is the phone reboots in 5 sec regardless... so when I select fastboot might open up that menu or may not either way it reboots. Thanks for your responding... Im going to let it drain overnight and tinker with it in the morning

Dreadedfox said:
I've been in the bootloader menu plenty of times, the problem is the phone reboots in 5 sec regardless... so when I select fastboot might open up that menu or may not either way it reboots. Thanks for your responding... Im going to let it drain overnight and tinker with it in the morning
Click to expand...
Click to collapse
I do not know if this is the wisest idea or if it has been tried before but you could try interrutpting the reboot cycle by booting into ruu mode. Try
Code:
fastboot oem rebootRUU
The code should take less then a second to enter if you have it typed out and waiting.
Once you are in the RUU section just type this
Code:
fastboot reboot-bootloader
With any luck you might be able to break the bootloop

Dreadedfox said:
My htc One is bricked and i dont know what to do.
One day it just randomly prompted that it was going to power down and after that its been stuck in the bootloop cycle.
it only powers on to bootloop cycle when connected to a charger or pc after a period of time. The charging LED has been does not show.
I tried to launch recovery but it reboots before completing the process; infact it only stays in the bootloader screen for 5 secs before it reboots.
I've tried to fastboot erase cache and i get the error too many links, as the phone reboots back into the loop. also to note that when i plug in the htc one into the pc it tries to install it (when its in fast boot right before it reboots) but it cant because it says its unplug. (Ive tried many different cord, i even got a brand new oem cable from another htc one at the AT&T store)
the phone is rooted/unlock with a trickdroid and has been over 2 months without a issue.
I fear that the phone is gone....please help
i would even be willing to open the phone since its not under warranty....
Click to expand...
Click to collapse
so you cant get to bootloader?

zaphodbeeb said:
so you cant get to bootloader?
Click to expand...
Click to collapse
Sorry for being unclear. I can get in the bootloader but the boot loop cycle is interrupting any process I begin
I can enter ruu with a custom rom. I'm currently running trickdriod

Wozzie said:
I do not know if this is the wisest idea or if it has been tried before but you could try interrutpting the reboot cycle by booting into ruu mode. Try
Code:
fastboot oem rebootRUU
The code should take less then a second to enter if you have it typed out and waiting.
Once you are in the RUU section just type this
Code:
fastboot reboot-bootloader
With any luck you might be able to break the bootloop
Click to expand...
Click to collapse
I did this and it didnt break the bootloop cycle but it did go into ruu mode before rebooting and once it rebooted it showed the trickdriod splash screen which it hasnt before and the bottom keys flashed a few times.... I tried getvar... and heres the info
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.12
(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: low
(bootloader) battery-voltage: 3448mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.273s

Just a few questions, can you get into fastboot at all? can you lock your bootloader using fastboot and then run a stock RUU.exe while your phones in fastboot?

TaintedCross said:
Just a few questions, can you get into fastboot at all? can you lock your bootloader using fastboot and then run a stock RUU.exe while your phones in fastboot?
Click to expand...
Click to collapse
Yes i can get into fastboot for a few seconds.... I cant lock my boot bootloader it always fail, im guessing due to the phone rebooting before it is done

< waiting for device >
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 1.198s
ok I relocked bootloader but its still reboot cycle now going straight into bootloader....

[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 does not charge while in OS. Kernal or Firmware??

So the full story is my HTC ONE m7 has had this happen about 3 times now. The first time it happened the battery ran to 0% and I fixed it using a flashlight, Power + Vol down while plugged in. The second time I was playing a game and the phone seemed to overheat and shut itself down, that was fixed with Power + Vol down while plugged in. This time my son was watching videos and the phone went to 0% again and shutdown. I charged it while off to 100% and turned the phone on but now it doesn't charge again while powered on or in 'OS'. I've had this phone for a year and a half, love the phone but this issue drives me crazy and a lot of people seem to have the same problem but there is no apparent fix.
I've tried:
Power + Vol up and down for 2+ minutes
Power + Vol down with/or without flashlight
Power + Vol up
Safemode/ reboot
factory reset (lost everything)
HTC support (useless)
All this was done while completely stock. So I did this next:
Rooted/Bootloader Team Win 2.8.3.0 twrp then totally wiped everything even original 'OS' without a backup first 'Dumb' on my part... so I eventually loaded the twrp recovery 2.8.3.0 and flashed ROM HD revolution 84.
What I really don't get is that there is no way it is hardware related because while I'm in Bootloader or Recovery the phone charges fine and communicates through usb (PC see's it with access to the internal storage) totally fine. But as soon as I'm in the 'OS' I can't use the usb port at all. PC doesn't see the phone (no sound when plugged in) and doesn't charge even while plugged into AC adapter. My question is could it be a corrupt kernal or firmware?? Whatever it is between the bootloader and OS load the phone completely disables the usb port. Possible Fix???

Roddyrex said:
So the full story is my HTC ONE m7 has had this happen about 3 times now. The first time it happened the battery ran to 0% and I fixed it using a flashlight, Power + Vol down while plugged in. The second time I was playing a game and the phone seemed to overheat and shut itself down, that was fixed with Power + Vol down while plugged in. This time my son was watching videos and the phone went to 0% again and shutdown. I charged it while off to 100% and turned the phone on but now it doesn't charge again while powered on or in 'OS'. I've had this phone for a year and a half, love the phone but this issue drives me crazy and a lot of people seem to have the same problem but there is no apparent fix.
I've tried:
Power + Vol up and down for 2+ minutes
Power + Vol down with/or without flashlight
Power + Vol up
Safemode/ reboot
factory reset (lost everything)
HTC support (useless)
All this was done while completely stock. So I did this next:
Rooted/Bootloader Team Win 2.8.3.0 twrp then totally wiped everything even original 'OS' without a backup first 'Dumb' on my part... so I eventually loaded the twrp recovery 2.8.3.0 and flashed ROM HD revolution 84.
What I really don't get is that there is no way it is hardware related because while I'm in Bootloader or Recovery the phone charges fine and communicates through usb (PC see's it with access to the internal storage) totally fine. But as soon as I'm in the 'OS' I can't use the usb port at all. PC doesn't see the phone (no sound when plugged in) and doesn't charge even while plugged into AC adapter. My question is could it be a corrupt kernal or firmware?? Whatever it is between the bootloader and OS load the phone completely disables the usb port. Possible Fix???
Click to expand...
Click to collapse
You are correct the next logical thing to try is either the firmware or kernel (which is included with the stock firmware). See if you can find the stock firmware for your version and give it a try. If stock kernel doesn't help then try a custom kernel, you can find them in the Development Section.

So to update my firmware I would need to be S-OFF and I'm not sure how to do that when I have no USB/ADB available in windows with my device at the home screen ie. rumrunner. Is there a way to get S-off from bootloader or Fastboot?

Here is my phone info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.661.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4104mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s

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