Help HTC One SV K2_CL soft-bricked

[kc2jav]

I've checked other similar threads and tried procedures that worked for others, but I am still unable to recover into TWRP and normal boot hangs on the initial HTC screen.

I have the following in the bootloader display:

*** TAMPERED ***
*** UNLOCKED ***
K2_CL PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.12.50.0516
OpenDSP-v10.2.0268.0401
OS-
eMMC-boot 1024MB
Apr 14 2014,18:55:20.0

Fastboot detects my phone on either a Windows or Ubuntu laptop, but I cannot see any device when invoking "adb devices" on either laptop.

This is the 2nd time I managed to soft-brick this phone. Last week I was able to flash TWRP and recover in that manner, but while using an app to "clean" junk from memory the phone soft-bricked again o) and now I cannot even recover into TWRP. I've tried multiple times to flash different recent versions of TWRP to no avail. I cannot seem to change the phone to S-OFF either, and I am in need of help!

Assistance is very much appreciated!!

 

[ModdingMyMind]

fastboot flash recovery customrecovery.img

That would be the proper command for installing your TWRP recovery on your device with respect to the recovery partition.

Make sure the Official TWRP version is not 2.7.1.0 or below as it will not work properly since you are on 4.2.2 with HBoot 2.21.

If the above command fails then you need to share in detail the steps you took prior to using that command.

Worst case, you jacked up your recovery partition.

 

[kc2jav]

Thank you for your help. I think I may have jacked up the recovery partition. Per your suggestion I did the following:

C:\Android>fastboot devices
HT38CS700287    fastboot

C:\Android>fastboot flash recovery recovery.img
sending 'recovery' (9932 KB)...
OKAY [  1.126s]
writing 'recovery'...
OKAY [  2.570s]
finished. total time: 3.698s

Upon selecting the Recovery option from the HBoot main menu the phone went into "Entering Recovery..." for about 30 seconds, then rebooted itself and hung on the initial splash screen.

Here's a summary of what commands I used during my trials last week:

fastboot flash recovery recovery.img (renamed from K2_CL_TWRP_2.7.1.0d_Extended.img or openrecovery-twrp-2.7.1.0-k2_cl.img, neither worked)

fastboot oem rebootRUU (dark screen with htc logo appears)
then> fastboot flash zip PL80IMG.zip
result: OKAY (finished), but phone just goes into reboot cycle

fastboot oem rebootRUU (dark screen with htc logo appears)
then> fastboot flash recovery twrp.img (renamed from K2_CL_TWRP_2.7.1.0d_Extended.img or openrecovery-twrp-2.7.1.0-k2_cl.img, OKAY (finished) but phone goes into reboot cycle)

fastboot erase cache
fastboot oem rebootRUU (dark screen with htc logo appears)
then> fastboot flash zip decrypted_k2_cl_2.06.653.6_rom.zip
result:
sending zip
OKAY
writing zip
(bootloader) signature checking
FAILED (remote: 12 signature verify fail)

Last thing I tried that seemed to work initially is in the attached (lengthy output) but the phone still hangs in rebooting.

If you are willing to go through a "resurrection" with me I will be very much appreciative.

<rant>I started down the path of rooting this device because of the crazy memory limitations from the stock device. It is astonishing to me that a company would release a product with sd card expansion and not provide a means for the user to safely move (or sense and then set the external sd card memory as a default for applications installation). </rant>

Thank you, ModdingMyMind!

 

[ModdingMyMind]

Well, I appreciate the info. I'm currently at a lost though. You were using a proper TWRP recovery for your device and the proper fastboot commands, "fastboot devices" & "fastboot flash recovery recovery.img". I personally do not see what would be causing your recovery to bootloop. The mere fact that the recovery partition is partially working tells me it isn't corrupted.

I'm gonna have to put some thought in to your dilemma, but the above should have worked.

 

[ModdingMyMind]

Your device must be unlocked when flashing a recovery. In your first post you mentioned it was, however, verify on your part that it still is while you install the custom recovery. If the bootloader is locked it will fail. I can already say it is safe to assume your bootloader is in fact unlocked simply because fastboot is telling you it was successful.

This is gonna be a strange question as well: are you positively sure your device is a K2_CL??

 

[kc2jav]

Here's what my HBoot screen looks like:

https://drive.google.com/file/d/0B9HlpLwxYmSAclcxOUoxSjA4bms/edit?usp=sharing

 

[ModdingMyMind]

Here's what my HBoot screen looks like:

https://drive.google.com/file/d/0B9HlpLwxYmSAclcxOUoxSjA4bms/edit?usp=sharing

Do me a favor, download this TWRP and try it.

http://techerrata.com/file/twrp2/k2_cl/openrecovery-twrp-2.7.1.1-k2_cl.img

 

[kc2jav]

C:\Android>fastboot flash recovery recovery.img
sending 'recovery' (10002 KB)...
OKAY [  1.150s]
writing 'recovery'...
OKAY [  2.556s]
finished. total time: 3.708s

C:\Android>

ModdingMyMind,

After executing this above (renaming the downloaded file from you as recovery.img), I returned to the HBoot menu and selected RECOVERY, pushed the power button and I get:

... and after about 30 seconds or so the phone reboots and hangs at the initial "htc quietly brilliant" splash screen.

 

[ModdingMyMind]

C:\Android>fastboot flash recovery recovery.img
sending 'recovery' (10002 KB)...
OKAY [  1.150s]
writing 'recovery'...
OKAY [  2.556s]
finished. total time: 3.708s

C:\Android>

ModdingMyMind,

After executing this above (renaming the downloaded file from you as recovery.img), I returned to the HBoot menu and selected RECOVERY, pushed the power button and I get:

... and after about 30 seconds or so the phone reboots and hangs at the initial "htc quietly brilliant" splash screen.

Well then, your situation has me at a complete lost....... ( Rarely happens :-/ )

You can boot up your system correct?

 

[ModdingMyMind]

Hold up..... Your recovery while entering doesn't show the red text at the bottom which it would if a custom recovery were installed. In your case there isn't one installed. Fastboot is saying it is successful but it's not or the red text would appear when entering the recovery.

Type out:

fastboot flash recovery

Then hit the space bar. Now click on the custom recovery image and drag then drop on to the terminal (if linux) / msdos prompt (if windows). Now hit enter. Fingers crossed lol.

 

[kc2jav]

No, I have not been able to boot the system for two weeks now - it always goes into a boot-loop or it hangs on the initial splash screen.

 

[kc2jav]

Hold up..... Your recovery while entering doesn't show the red text at the bottom which it would if a custom recovery were installed. In your case there isn't one installed. Fastboot is saying it is successful but it's not or the red text would appear when entering the recovery.

Type out:

fastboot flash recovery

Then hit the space bar. Now click on the custom recovery image and drag then drop on to the terminal (if linux) / msdos prompt (if windows). Now hit enter. Fingers crossed lol.

Just tried this (dragging the original custom recovery image file I downloaded from you earlier today) with the same result. Did not see any red text at the bottom, phone reboots and hangs.



p.s. I will repeat this on my Ubuntu laptop at home later this evening, using Windows 7 Professional here at work

 

[kc2jav]

Interesting ... different behavior on Ubuntu Linux 14.04.

~/Desktop/htc 
16:33 $ fastboot devices
HT38CS700287	fastboot
~/Desktop/htc 
16:43 $ fastboot flash recovery '/home/solimeno/Desktop/htc/openrecovery-twrp-2.7.1.1-k2_cl.img' 
sending 'recovery' (10002 KB)...

... at this point my terminal window on the Ubuntu laptop is hanging. Apparently the image is not writing to the recovery partition on the phone. This action also makes the phone hang on the fastboot usb screen and I have to remove the battery to get back to the HBoot menu.

(tried this twice with identical results, also tried as root using sudo same result)

 

[ModdingMyMind]

Interesting ... different behavior on Ubuntu Linux 14.04.

~/Desktop/htc 
16:33 $ fastboot devices
HT38CS700287fastboot
~/Desktop/htc 
16:43 $ fastboot flash recovery '/home/solimeno/Desktop/htc/openrecovery-twrp-2.7.1.1-k2_cl.img' 
sending 'recovery' (10002 KB)...

... at this point my terminal window on the Ubuntu laptop is hanging. Apparently the image is not writing to the recovery partition on the phone. This action also makes the phone hang on the fastboot usb screen and I have to remove the battery to get back to the HBoot menu.

(tried this twice with identical results, also tried as root using sudo same result)

I don't know where you got fastboot from.

Install it on your linux distro with the following terminal command:

sudo apt-get install fastboot && sudo apt-get install adb

 

[kc2jav]

Hmmm ... this is weird.

21:47 $ sudo apt-get install fastboot
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package fastboot
~ 
21:47 $ sudo apt-get install adb
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package adb
~ 
21:47 $

I think I had previously installed these tools from the "Stand Alone Android SDK Tools" at https://developer.android.com/sdk/installing/index.html

 

[ModdingMyMind]

Hmmm ... this is weird.

21:47 $ sudo apt-get install fastboot
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package fastboot
~ 
21:47 $ sudo apt-get install adb
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package adb
~ 
21:47 $

I think I had previously installed these tools from the "Stand Alone Android SDK Tools" at https://developer.android.com/sdk/installing/index.html

My apologies lol:

sudo apt-get install android-tools-adb && sudo apt-get install android-tools-fastboot

I previously gave you the wrong command.

 

[kc2jav]

OK - it looks like I have the right tools installed.

04:51 $ sudo apt-get install android-tools-adb && sudo apt-get install android-tools-fastboot
[sudo] password for solimeno: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
android-tools-adb is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree       
Reading state information... Done
android-tools-fastboot is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
~ 
04:51 $

 

[ModdingMyMind]

OK - it looks like I have the right tools installed.

04:51 $ sudo apt-get install android-tools-adb && sudo apt-get install android-tools-fastboot
[sudo] password for solimeno: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
android-tools-adb is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree       
Reading state information... Done
android-tools-fastboot is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
~ 
04:51 $

Hmm, well then, I must say that I am at a lost. For whatever the reason may be, the custom recovery is not being installed. If it were installed there would be a bunch of red text at the bottom of the screen as you enter the recovery. In your case, the red text is not there, and you have used the proper ways for going about installed TWRP. At this point I am not sure what the cause is for your device as I have personally never seen this kind of issue before nor can I duplicate it on my end.

 

[kc2jav]

Thank you for all the time you have spent assisting me, ModdingMyMind.
Though this problem persists, I do appreciate your efforts!

 

[kc2jav]

I've read online here (scroll down to post by Scotty85): http://androidforums.com/one-sv-all-things-root/723528-stock-ruu.html

that it may be possible to restore a stock image back to the phone if I can identify the appropriate RUU. The following is output from my phone:

~/Desktop/htc 
20:50 $ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.21.0000
(bootloader) version-baseband: 1.12.50.0516
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.11.653.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT38CS700287
(bootloader) imei: 990001457072056
(bootloader) meid: 99000145707205
(bootloader) product: k2_cl
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8011000
(bootloader) cidnum: SPCS_003
(bootloader) battery-status: good
(bootloader) battery-voltage: 4296mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dc34ae5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.072s

I have attempted to run this RUU without success: AndroidRUU | The #1 source for Android RUU files

Can anyone help me identify another RUU that would work with my phone based on the output of fastboot getvar all?

 

[ModdingMyMind]

I've read online here (scroll down to post by Scotty85): http://androidforums.com/one-sv-all-things-root/723528-stock-ruu.html

that it may be possible to restore a stock image back to the phone if I can identify the appropriate RUU. The following is output from my phone:

~/Desktop/htc 
20:50 $ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.21.0000
(bootloader) version-baseband: 1.12.50.0516
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.11.653.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT38CS700287
(bootloader) imei: 990001457072056
(bootloader) meid: 99000145707205
(bootloader) product: k2_cl
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8011000
(bootloader) cidnum: SPCS_003
(bootloader) battery-status: good
(bootloader) battery-voltage: 4296mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dc34ae5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.072s

I have attempted to run this RUU without success: AndroidRUU | The #1 source for Android RUU files

Can anyone help me identify another RUU that would work with my phone based on the output of fastboot getvar all?

Won't work because you are S-On. When S-On the RUU is expected to be equivalent to your devices current OS or greater. Our RUU is only for 4.1.2 which is below your current OS. Both boot loader versions are different and therefore it will not succeed.

 

[ModdingMyMind]

You would have to be S-Off otherwise.

 

[kc2jav]

Thanks for the explanation. I guess I can wait for a new 4.2.2 RUU to become available and then try this method.

 

[ModdingMyMind]

Thanks for the explanation. I guess I can wait for a new 4.2.2 RUU to become available and then try this method.

I contacted HTC requesting that an RUU be released for the K2_CL based on 4.2.2. Never got a response so who knows what will happen. Would be nice to have.

 

[kLethal]

aaaaaa they released one