[Q] HTC One (T-Mobile) soft bricked

piftoffpenguin · Feb 4, 2014

ok

darksnoopy said:
well sh*t. try to flash/boot this recovery and check adb :-/

http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.3-m7tmo.img

flashed fine, but booting recovery shows twrp splash for 5 seconds then bounces again. . . .

I really think its the battery that is the problem - If I load an img that is not flashed to my device it works fine

darksnoopy · Feb 4, 2014

piftoffpenguin said:
flashed fine, but booting recovery shows twrp splash for 5 seconds then bounces again. . . .

I really think its the battery that is the problem - If I load an img that is not flashed to my device it works fine

twrp? but this is a cwm recovery... something is wrong... maybe corrupted partitions. Try to boot the recovery i posted, dont flash it and then check if "adb devices" lists your device

piftoffpenguin · Feb 5, 2014

understand

[QUAOTE=darksnoopy;50049139]twrp? but this is a cwm recovery... something is wrong... maybe corrupted partitions. Try to boot the recovery i posted, dont flash it and then check if "adb devices" lists your device[/QUOTE]

Thats what I did. I tried flashing it and booting and I still saw the twrp splash.

THEN i just straight booted from the clockwork (Philz) then when I was in, I went to ADB Sideload and it could not see adb devices. After that I moved from my Windows 8n laptop to a XP box and installed the JRE, SDK, HTC Sync, Google USB drivers, etc and went into Phil from there. Sideload, still no ADB devices detected.

Since this happened when the battery died and many others have this issue, I am draining it tonight so that I can use the HTC certified charge in the AM to see if it had something to do with that.

Good suggestions and help. I appreciate it more than you know. This is definitely related to the battery dying, and there are many HTC One Tmobile users who have the same issue without rooting or flashing, so I think this is definitely a bug, Still I want to get around it, but I think the battery stats are hosed or something so I'll let you know in the morning if I make headway. I've never had this phone die before. This was the first in 4 months (I keep a few mobile chargers since I'm a Network Engineer), so it makes sense why I have not had this issue, but it has to do with the battery dying somehow.

chintu_2000 · Feb 5, 2014

Almost Same Problems with me also...

Same problem with me too...
A friend of mine did something with his HTC ONE M7_UL & got into a bootloop

**TAMPERED**
**UNLOCKED**
M7_UL PVT SHIP S-ON RH
HBOOT 1.44.0000
RADIO 4A.14.3250.13
openDSP v26.120.274.0202
eMMC-boot
Apr 12 2013
Serial No. SH34******6
IMEI 3544*********15
Model-id PN0710000
CID HTC_001
SECURITY ON
BUILD MODE SHIP
BOOT MODE FASTBOOT
GETVAR ALL FAILED (STATUS READ FAILED (TOO MANY LINKS)

I tried to solve it with almost all the methods mentioned in this thread.

Deatils are as followed:
------------------------

fastboot erasing cache...okay (0.047s)
fastboot erasing userdata...failed (remote not allowed)
fastboot erasing system....failed (remote not allowed)
fastboot reboot bootloader....nothing happens
fastboot oem rebootRUU....okay (0.031s)...(HTC goes into HTC Grey logo screen)
fastboot flash zip rom.zip......sendin zip...(1176263 KB)...OKAY
(booltloader) zip header checking...
(booltloader) zip info parsing...
FAILED (remote 24 parsing android-info fail)
FINISHED

i tried with 5 roms matching my CID & model-id & all were for S-ON ( as i am also S-ON)

I am able to boot into recovery (TWRP)...did a hard reset also but in vain....
also tried pushing ROM's so that i can install zip from recovery but sideload also...cannot mount
UNABLE TO ADB anything...except for fastboot mode

i also tried with many compatible RUU.exe...again failed

i tried flashing the advanced CWM philz recovery....FAILED (remote: 12 signature verify fail)

I guess I know the problem...(there is no OS installed) & (there is no BUILD NUMBER)

BUT...how do i solve it?

OR is it a hardware problem?

I am using Windows XP as well as Windows 7 on 2 different machines.

piftoffpenguin · Feb 5, 2014

I feel your pain

chintu_2000 said:
Same problem with me too...
A friend of mine did something with his HTC ONE M7_UL & got into a bootloop

**TAMPERED**
**UNLOCKED**
M7_UL PVT SHIP S-ON RH
HBOOT 1.44.0000
RADIO 4A.14.3250.13
openDSP v26.120.274.0202
eMMC-boot
Apr 12 2013
Serial No. SH34******6
IMEI 3544*********15
Model-id PN0710000
CID HTC_001
SECURITY ON
BUILD MODE SHIP
BOOT MODE FASTBOOT
GETVAR ALL FAILED (STATUS READ FAILED (TOO MANY LINKS)

I tried to solve it with almost all the methods mentioned in this thread.
Deatils are as followed:
------------------------

fastboot erasing cache...okay (0.047s)
fastboot erasing userdata...failed (remote not allowed)
fastboot erasing system....failed (remote not allowed)
fastboot reboot bootloader....nothing happens
fastboot oem rebootRUU....okay (0.031s)...(HTC goes into HTC Grey logo screen)
fastboot flash zip rom.zip......sendin zip...(1176263 KB)...OKAY
(booltloader) zip header checking...
(booltloader) zip info parsing...
FAILED (remote 24 parsing android-info fail)
FINISHED

i tried with 5 roms matching my CID & model-id & all were for S-ON ( as i am also S-ON)

I am able to boot into recovery (TWRP)...did a hard reset also but in vain....
also tried pushing ROM's so that i can install zip from recovery but sideload also...cannot mount
UNABLE TO ADB anything...except for fastboot mode

i also tried with many compatible RUU.exe...again failed

i tried flashing the advanced CWM philz recovery....FAILED (remote: 12 signature verify fail)

I guess I know the problem...(there is no OS installed) & (there is no BUILD NUMBER)

BUT...how do i solve it?
OR is it a hardware problem?

I am using Windows XP as well as Windows 7 on 2 different machines.

I checked the TMobile forums and a LOT of people have this issue whether rooted and unlocked or not. Its definitely a hardware bug.

Last night I let it boot loop until it died. Before charging I powered on again just to make sure it drained and it booted 3 more times and died. I then charged it with HTC certified charger and the damn thing is boot looping again. This is a sham by HTC!!

darksnoopy · Feb 5, 2014

piftoffpenguin said:
I checked the TMobile forums and a LOT of people have this issue whether rooted and unlocked or not. Its definitely a hardware bug.

Last night I let it boot loop until it died. Before charging I powered on again just to make sure it drained and it booted 3 more times and died. I then charged it with HTC certified charger and the damn thing is boot looping again. This is a sham by HTC!!

Try to reflash the ruu.exe while u are in fastboot-usb. If you get error dont restart your device but run ruu.exe for second time. Also disconnect pc from internet while u do this

piftoffpenguin · Feb 5, 2014

Did that

darksnoopy said:
Try to reflash the ruu.exe while u are in fastboot-usb. If you get error dont restart your device but run ruu.exe for second time. Also disconnect pc from internet while u do this

I did that. It sees the device and reboots it into a boot loop.

Tried again and when it rebooted, I helf vol down and manually put it back into fastboot and then the RUU fails with Error 171 USB not connected. I assume because its using adb at that point and its not working with adb . . . .

darksnoopy · Feb 5, 2014

piftoffpenguin said:
I did that. It sees the device and reboots it into a boot loop.

Tried again and when it rebooted, I helf vol down and manually put it back into fastboot and then the RUU fails with Error 171 USB not connected. I assume because its using adb at that point and its not working with adb . . . .

I am running out of ideas.
Open the ruu.zip and take boot.img put it in the fastboot folder and flash it. fastboot flash boot boot.img
See if it makes any difference and check for adb after that

piftoffpenguin · Feb 5, 2014

good call

darksnoopy said:
I am running out of ideas.
Open the ruu.zip and take boot.img put it in the fastboot folder and flash it. fastboot flash boot boot.img
See if it makes any difference and check for adb after that

But unfortunately I tried that yesterday

It's beginning to look a lot like JTAG everywhere I go . . . . . XD

piftoffpenguin · Feb 5, 2014

Additional Info

C:\Users\*****\Desktop\FASTBOOT>fastboot oem boot >>C:\htc\htc.txt
... INFOBoot/Recovery signature checking...
INFOTZ_HTC_SVC_HASH ret = 0
INFOsetup_tag addr=0x80600100 cmdline add=0x00346A70
INFOTAG:Ramdisk OK
INFOTAG:skuid 0x34C0D
INFOTAG:hero panel = 0x6940065
INFOTAG:engineerid = 0x0
INFOTAG: PS ID = 0x0
INFOTAG: Gyro ID = 0x2
INFODevice CID is not super CID
INFOCID is T-MOB010
INFOsetting->cid::T-MOB010
INFOserial number: **********
INFOcommandline from head: console=ttyHSL0,115200,n8 androidboot
INFO.hardware=m7 user_debug=31
INFOcommand line length =883
INFOactive commandline: poweron_status=1 reset_status=0 board_m7
INFO_ul.disable_uart3=0 diag.enabled=0 board_m7_ul.debug_uart=0
INFOuserdata_sel=0 androidboot.emmc=true androidboot.e2fsck=true
INFO androidboot.pagesize=2048 skuid=0 ddt=20 ats=0 dap=6 andro
INFOidboot.lb=1 uif=@000 td.sf=1 td.td=1 td.ofs=328 td.prd=1 td.
INFOdly=0 td.tmo=300 hlog.ofs=628 un.ofs=694 imc_online_log=0 a
INFOndroidboot.efuse_info=4NSL androidboot.baseband=4A.14.3250.1
INFO5 androidboot.cid=T-MOB010 androidboot.devicerev=3 androidbo
INFOot.batt_poweron=good
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=local
INFOaARM_Partion[5].name=cache
INFOaARM_Partion[6].name=userdata
INFOaARM_Partion[7].name=devlog
INFOaARM_Partion[8].name=pdata
INFOaARM_Partion[9].name=extra
INFOaARM_Partion[A].name=radio
INFOaARM_Partion.name=adsp
INFOaARM_Partion[C].name=dsps
INFOaARM_Partion[D].name=radio_config
INFOaARM_Partion[E].name=modem_st1
INFOaARM_Partion[F].name=modem_st2
INFOaARM_Partion[10].name=cdma_record
INFOaARM_Partion[11].name=reserve_1
INFOaARM_Partion[12].name=reserve_2
INFOaARM_Partion[13].name=reserve_3
INFOaARM_Partion[14].name=reserve
INFOpartition number=21
INFOValid partition num=21
INFOsetting_get_bootmode() = 2
INFOsmem 8CF04000 (phy 8CF04000): TZ_HTC_SVC_UPDATE_SMEM ret = 0
INFOTZ_HTC_SVC_ENC ret = 0
INFOTZ_HTC_SVC_ENC ret = 0
INFOTZ_HTC_SVC_DISABLE ret = 205643776 (0xC41E000)
INFO[PARTITION_ERR] partition_write_prot_emmc: Cannot find end p
INFOartition [modem]
INFOmsm_mpu_emmc_protect: set write protection fail (from reserv
INFOe_2 to modem)
INFOStart Verify: 3
INFO[RUMBA_S] firmware version: 3-45-43-33-0-0-0-0
INFO[RUMBA_S] ondevice version: 3-45-43-33-4-28-A4-0
INFO[RUMBA_S] firmware version already up-to-date
INFOpm8921_vreg_disable function, vreg_id = 7
INFOpm8921_vreg_disable function, vreg_id = 37
INFOpm8921_vreg_disable function, vreg_id = 34
INFOpm8921_vreg_disable function, vreg_id = 8
INFOjump_to_kernel: machine_id(4308), tags_addr(0x80600100), ker
INFOnel_addr(0x80608000)
INFO-------------------hboot boot time:35198 msec
FAILED (status read failed (Too many links))
finished. total time: 3.035s

darksnoopy · Feb 5, 2014

piftoffpenguin said:
But unfortunately I tried that yesterday

It's beginning to look a lot like JTAG everywhere I go . . . . . XD

:S try to flash this old version of twrp
http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.5.0.0-m7.img
erase cache
flash recovery
erase cache
enter recovery

if you cant enter again then try to boot into it instead of flashing

piftoffpenguin · Feb 5, 2014

Quick question. Why can't I use the command

fastboot oem rebootruu

?? It says command error. Is that because its locked and wont unlock? Also, one thing I saw in the fastboot oem boot messages was

CID is not SuperCID - What does that mean?

darksnoopy · Feb 5, 2014

piftoffpenguin said:
Quick question. Why can't I use the command

fastboot oem rebootruu

?? It says command error. Is that because its locked and wont unlock? Also, one thing I saw in the fastboot oem boot messages was

CID is not SuperCID - What does that mean?

It means you havent change your cid to 11111111. Nothing to worry about.
Now about the error with rebootruu i think its a fastboot error, you can try to fastboot oem rebootRUU by using fastboot in this .zip
http://d-h.st/RvD

Before executing the command your bootloader must be at fastboot-usb

piftoffpenguin · Feb 5, 2014

no dice but!!

darksnoopy said:
It means you havent change your cid to 11111111. Nothing to worry about.
Now about the error with rebootruu i think its a fastboot error, you can try to fastboot oem rebootRUU by using fastboot in this .zip
http://d-h.st/RvD

Before executing the command your bootloader must be at fastboot-usb

Still get the error, but I noticed I ran the command

fastboot update ruu.zip

It tries but wants a boot.sig file and I dont have one

darksnoopy · Feb 5, 2014

piftoffpenguin said:
Still get the error, but I noticed I ran the command

fastboot update ruu.zip

It tries but wants a boot.sig file and I dont have one

post a screenshot of that

piftoffpenguin · Feb 5, 2014

got past that

darksnoopy said:
post a screenshot of that

I got past that and it says does not contain system.img, but clearly it does . . . .

darksnoopy · Feb 5, 2014

piftoffpenguin said:
I got past that and it says does not contain system.img, but clearly it does . . . .

restart ur computer and try it again

nkk71 · Feb 5, 2014

Originally Posted by piftoffpenguin View Post
Quick question. Why can't I use the command

fastboot oem rebootruu

?? It says command error. Is that because its locked and wont unlock? Also, one thing I saw in the fastboot oem boot messages was

CID is not SuperCID - What does that mean?

It means you havent change your cid to 11111111. Nothing to worry about.
Now about the error with rebootruu i think its a fastboot error, you can try to fastboot oem rebootRUU by using fastboot in this .zip
http://d-h.st/RvD

Before executing the command your bootloader must be at fastboot-usb

not that i'm getting involved, but, oh look, i have the same problem when i mistype my commands (and that's with S-Off and SuperCID)

Code:

C:\ADB3>[B][COLOR="Blue"]fastboot oem rebootruu[/COLOR][/B]
...
[COLOR="Blue"][COLOR="Red"](bootloader) [ERR] Command error !!![/COLOR][/COLOR]
OKAY [  0.016s]
finished. total time: 0.016s

C:\ADB3>[B][COLOR="Blue"]fastboot oem rebootRUU[/COLOR][/B]
...
(bootloader) Start Verify: 0
OKAY [  0.047s]
finished. total time: 0.047s

piftoffpenguin · Feb 5, 2014

case sensitive????

nkk71 said:
not that i'm getting involved, but, oh look, i have the same problem when i mistype my commands (and that's with S-Off and SuperCID)

Code:

C:\ADB3>[B][COLOR="Blue"]fastboot oem rebootruu[/COLOR][/B] ... [COLOR="Blue"][COLOR="Red"](bootloader) [ERR] Command error !!![/COLOR][/COLOR] OKAY [ 0.016s] finished. total time: 0.016s C:\ADB3>[B][COLOR="Blue"]fastboot oem rebootRUU[/COLOR][/B] ... (bootloader) Start Verify: 0 OKAY [ 0.047s] finished. total time: 0.047s

WHAAAASSSSSSS?!?!?!?!?!

That rebooted it lol but it went back into boot loop FARK!!

darksnoopy · Feb 5, 2014

piftoffpenguin said:
fastboot oem rebootRUU
INFO[ERR] Command Error !!

fastboot flash zip ruu.zip
sending 'zip' (1037376 KB) . . .
writing 'zip' . . . FAILED (remote: not allowed)
finished. total time: 102.749s

nkk71 said:
not that i'm getting involved, but, oh look, i have the same problem when i mistype my commands (and that's with S-Off and SuperCID)

Code:

C:\ADB3>[B][COLOR="Blue"]fastboot oem rebootruu[/COLOR][/B] ... [COLOR="Blue"][COLOR="Red"](bootloader) [ERR] Command error !!![/COLOR][/COLOR] OKAY [ 0.016s] finished. total time: 0.016s C:\ADB3>[B][COLOR="Blue"]fastboot oem rebootRUU[/COLOR][/B] ... (bootloader) Start Verify: 0 OKAY [ 0.047s] finished. total time: 0.047s

Oh well dont tell me you were typing it wrong! :-/
Edit: Oh you were typing it wrong..

[Q] HTC One (T-Mobile) soft bricked

Senior Member

Senior Member

Senior Member

Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Attachments

Senior Member

Inactive Recognized Developer / Contributor

Senior Member

Senior Member

Similar threads

Top Liked Posts