Database Info

[Q] I *almost* bricked my daughter's ChaCha - help

Hi,
I almost bricked my daughter's ChaCha. Half a year ago I unlocked the bootloader to be able to install and run Link2sd to increase performance of the phone and have my daughter have all the apps on it she wants. But a week or so ago the phone started to act up and I decided to take a look.
End of the story is that the phone, when turned on, boots into fastboot automatically but the volume and power keys do not work at all. So I can't select reboot or recovery or anything. I have to remove the battery to switch it off...
Apparently system and recovery are gone cause when I issue 'fastboot oem boot' the response is '(bootloader) [ERR] Boot/Recovery image does not exist!!!'. That can't be good...
The bootloader got relocked in the process of trying to fix it which complicates the problem. Now I can't re-unlock it because the volume and power keys don't work. I can get fastboot in unlock mode but can't select 'yes' and continue because the keys do not work...
I tried re-installing stock rom via RUU with various results. Version 1.33 complains about a customer id (error 131), version 1.13 thinks it's a signature error (error 132) and version 1.18 (I must be desperate) doesn't like the bootloader version (error 140).
I tried creating an old school goldcard to get the phone to accept RUU 1.33 but obviously that failed too. Since I can't get into the phone over adb (only fastboot) I can't get the phone's CID. Also, system is reported to be nonexistent so trying to extract the CID is a dead end anyway.
I think I've tried everything and I'm about to give up. But I thought, before I do that, I better check with the experts here to see if anybody else has a brilliant idea to solve my problem. I'm considering buying the XTC clip but I'm not sure if that will work since the phone is so far gone already. Maybe someone here knows the answer to that?
Below is what 'fastboot getvar all' gives me. Hopefully that helps in answering my question: Is this phone bricked or is there still hope?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.10.0000
(bootloader) version-baseband: 7.51.35.19
(bootloader) version-cpld: None
(bootloader) version-microp: 0557
(bootloader) version-main: 1.57.0.0
(bootloader) serialno: HT16GV409974
(bootloader) imei: 355746042148642
(bootloader) product: chacha
(bootloader) platform: HBOOT-7227
(bootloader) modelid: PH0611000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4193mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d86ac222
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0

It doesn't look like it's anything you've done. If the bootloader is now locked, I would take advantage of that and send it back to the shop to get it repaired. (obviously, don't mention that you tampered with it). That shouldn't happen, I've got link2SD, and so has my partner and we've never had any problems like that, so I think it must be something wrong with your phone :/

Progress
Thanks for your reply. I thought about returning it the phone to have it repaired but it's apparent the phone has been unlocked and re-locked again. That will probably void warranty.
I don't think Link2sd caused this problem. Something else must have happened but I doubt it's a hardware problem.
I've made a bit of progress in the meantime. Somehow (I don't know how) the phone got in to recovery. The screen was black though but I could get into it with adb shell! So I got my CID and created a goldkey. I hoped that was all I needed but I still can't flash a stock rom over RUU because now they all complain about my hboot version which is 1.10
I think I need a RUU rom (exe) that supports hboot 1.10. Or, a way to downgrade to 1.07 or 1.05. Or a way to flash or push something onto the phone while in recovery.
Any help will be appreciated...

NoLimit64 said:
Hi,
...when turned on, boots into fastboot
Click to expand...
Click to collapse
Well if you are able to boot into fastboot maybe you can try this method. I used this to revive my friend's chacha.
Download this tool (it is, I believe, adlx's small fastboot tool). Extract it and navigate to it with cmd (I did this on windows). But before that download a RUU for your chacha (I used 1.3.3 version since it was the only one I could find), run RUU but don't flash it and don't exit the application as well. Then locate your temp folder (%temp%) and find somewhere in one of the folders a zip named Rom.zip (use the search function if you prefer). Copy the Rom.zip anywhere you like and extract system.img, boot.img and recovery.img and place them in the same folder where you extracted fastboot tools. And now enter these commands in cmd (don't forget to navigate to the folder you placed all the files):
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash boot boot.img
When it is finished, reboot your phone (you will probably need to do this by pulling the battery out) and hopefully you will have the stock rom installed.
Hope that this will help you.
Regards

didije said:
Well if you are able to boot into fastboot maybe you can try this method. I used this to revive my friend's chacha.
Download this tool (it is, I believe, adlx's small fastboot tool). Extract it and navigate to it with cmd (I did this on windows). But before that download a RUU for your chacha (I used 1.3.3 version since it was the only one I could find), run RUU but don't flash it and don't exit the application as well. Then locate your temp folder (%temp%) and find somewhere in one of the folders a zip named Rom.zip (use the search function if you prefer). Copy the Rom.zip anywhere you like and extract system.img, boot.img and recovery.img and place them in the same folder where you extracted fastboot tools. And now enter this commands in cmd (don't forget to navigate to the folder you placed all the files):
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash boot boot.img
When it is finished, reboot your phone (you will probably need to do this by pulling the battery out) and hopefully you will have the stock rom installed.
Hope that this will help you.
Regards
Click to expand...
Click to collapse
I had an issue with flashing an RUU because of HBOOT version, but as didje said, the 1.33 RUU version works with that HBOOT version

ethancottier said:
I had an issue with flashing an RUU because of HBOOT version, but as didje said, the 1.33 RUU version works with that HBOOT version
Click to expand...
Click to collapse
I always have issues flashing RUUs. Error this, error that, really annoying, so I don't flash them anymore. Now, I just flash manually those three files and I have no worries.

didije said:
I always have issues flashing RUUs. Error this, error that, really annoying, so I don't flash them anymore. Now, I just flash manually those three files and I have no worries.
Click to expand...
Click to collapse
Sorry, no luck....
C:\Fastboot\Fastboot>fastboot flash recovery recovery.img
sending 'recovery' (3172 KB)... OKAY [ 2.480s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
C:\Fastboot\Fastboot>fastboot flash system system.img
sending 'system' (259524 KB)... OKAY [ 62.605s]
writing 'system'... INFOsignature checking...
FAILED (remote: signature verify fail)
C:\Fastboot\Fastboot>fastboot flash boot boot.img
sending 'boot' (2572 KB)... OKAY [ 2.282s]
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
As I mentioned. bootloader is relocked (my bad) so flashing the individual files will not work. Unlocking the bootloader won't work either because for some reason the volume and power keys do not work while in bootloader
Running the 1.33 RUU (RUU_Chacha_HTC_Europe_1.33.401.1_Radio_47.17.35.3033H_7.48.35.14_2_release_204385_signed.exe) returns error 140 Bootloader version error when run with goldkey inserted. Without the goldkey it returns error 131 customer id error... At least the goldkey seems to work but my phone does not accept this version but I can't figure out why.
Strang thing though, the RUU says I currently have version 1.57 which means I'm downgrading to 1.33.
I'm going to try this method: http://forum.xda-developers.com/showthread.php?t=1320392
Thanks so far!!

Ah, bootloader is re-locked.. I missed that part. Bummer... Hope you will find a way. It is really strange that vol. keys do not work.

didije said:
Ah, bootloader is re-locked.. I missed that part. Bummer... Hope you will find a way. It is really strange that vol. keys do not work.
Click to expand...
Click to collapse
Did you disable fastboot in the settings? (Not sure in which part it is... Thought apps)...
If you uncheck the marker, you should be able to enter recovery, etc, again... Worked for me when I had this problem... It wasn't the bootloader that was locked, just me using the fastboot.
When you press vol down+pwr when Fastboot is enabled, you won't see your bootloader screen, it just boots fast...
Maybe worth a try...

Bunnybugs_007 said:
Did you disable fastboot in the settings? (Not sure in which part it is... Thought apps)...
If you uncheck the marker, you should be able to enter recovery, etc, again... Worked for me when I had this problem... It wasn't the bootloader that was locked, just me using the fastboot.
When you press vol down+pwr when Fastboot is enabled, you won't see your bootloader screen, it just boots fast...
Maybe worth a try...
Click to expand...
Click to collapse
Oh my, you must have misunderstood us. He CAN enter the bootloader menu, but he cannot do anything because the bootloader got re-locked (opposite to HTC Dev unlocking - when you enter hboot, bootloader menu or what is called you can see on the top "locked", "unlocked" or in my case "re-locked" - I relocked mine to take it to the service but I didn't thought that it will say RE-locked ) so he cannot flash anything unless he finds a way to unlock it again or s-off the device. That is the problem.

didije said:
... in my case "re-locked" - I relocked mine...
Click to expand...
Click to collapse
I got the same HTC chacha CID: HTC_E11, its something like "Nederlanden" version.
Re-locked don't undo Lock - just simply lock "bootloader".
You will never go back
You should Unlock by "htcdev . com/bootloader/unlock-instructions/page-3"
Then You'll be able to flash via fastboot ,sysem.img, boot.img, recovery.img

i have same problem
NoLimit64 said:
Hi,
I almost bricked my daughter's ChaCha. Half a year ago I unlocked the bootloader to be able to install and run Link2sd to increase performance of the phone and have my daughter have all the apps on it she wants. But a week or so ago the phone started to act up and I decided to take a look.
End of the story is that the phone, when turned on, boots into fastboot automatically but the volume and power keys do not work at all. So I can't select reboot or recovery or anything. I have to remove the battery to switch it off...
Apparently system and recovery are gone cause when I issue 'fastboot oem boot' the response is '(bootloader) [ERR] Boot/Recovery image does not exist!!!'. That can't be good...
The bootloader got relocked in the process of trying to fix it which complicates the problem. Now I can't re-unlock it because the volume and power keys don't work. I can get fastboot in unlock mode but can't select 'yes' and continue because the keys do not work...
I tried re-installing stock rom via RUU with various results. Version 1.33 complains about a customer id (error 131), version 1.13 thinks it's a signature error (error 132) and version 1.18 (I must be desperate) doesn't like the bootloader version (error 140).
I tried creating an old school goldcard to get the phone to accept RUU 1.33 but obviously that failed too. Since I can't get into the phone over adb (only fastboot) I can't get the phone's CID. Also, system is reported to be nonexistent so trying to extract the CID is a dead end anyway.
I think I've tried everything and I'm about to give up. But I thought, before I do that, I better check with the experts here to see if anybody else has a brilliant idea to solve my problem. I'm considering buying the XTC clip but I'm not sure if that will work since the phone is so far gone already. Maybe someone here knows the answer to that?
Below is what 'fastboot getvar all' gives me. Hopefully that helps in answering my question: Is this phone bricked or is there still hope?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.10.0000
(bootloader) version-baseband: 7.51.35.19
(bootloader) version-cpld: None
(bootloader) version-microp: 0557
(bootloader) version-main: 1.57.0.0
(bootloader) serialno: HT16GV409974
(bootloader) imei: 355746042148642
(bootloader) product: chacha
(bootloader) platform: HBOOT-7227
(bootloader) modelid: PH0611000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4193mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d86ac222
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
i tried to relock my htc chacha and baaamm. now hboot is locked and dead because no work any volume or power keys in hboot menu. i cant select any option. doesnt work vol+ or vol- or power here. also android os doesnt start normally if i restart to this phone directly opening hboot menu (also doesnt see any device on pc). but only way to access my phone via command. my way is:
1. shutdown phone (only way is remove your battery this status )
2. plug in usb cable your pc and phone
3. dont push to start button only wait until led is on
4. push to red(end call) button
5. now your phone is detected by the pc
6. you can use (phone is power off status still) fasboot commads
7.i use fastboot reboot command and start the phone.
anyway phone is accessible still . i have relocked phone using a nonsafe software i think hboot data damaged. QUESTION IS THAT: HOW CAN WE REPAIR HBOOT ON LOCKED STATUS WITHOUT USING ANY HARDWARE (JTAG OR XTCLIP).

stuck on a black HTC screen with 4 warning triangles in each corner

I flashed HPSGill's rom on Friday which is Sense 5 themed, It didn't boot up. So I went back to recovery, wiped everything down, and proceeded to flash the stock ROM. The RUU installation failed, giving me a 150 Error. I have used the same RUU for a year now. I then tried running some fastboot commands but most of them give me "REMOTE: NOT ALLOWED".
The phone goes into fastboot mode as when I execute "fastboot devices" i see my phone serial number on the command line. I can't however access adb. On removing the cable it takes me to the bootloader white screen, only now, the options for reboot, reset factory settings, recovery, etc, are not visible.
It just shows me my phone information, bootloader as relocked, and RUU highlighted. I have tried flashing the RUU multiple times, after each flash attempt, all partitions, except the userdata partition shows userdata FAIL-PU, which as I understand is the partition update failing, bootloader shows - BYPASSED. I have also tried downloading the same RUU just in case somehow the one I had was corrupted. But same result.
HTC service center says since I have rooted my phone, I will have to pay 6000 rs. for a 7000rs. phone to get it repaired. Is there any way back from this ? I have sent it to the service center and will get it back tomorrow, So I can only post screenshots if needed tomorrow. I have scoured the internet for the solution and I have read some odd success stories, but none of them for the explorer, mostly for desires. Any help appreciated.
I will be trying bortak's guide in the meanwhile which is again for htc desire.

Well from what I get so far you're stuck in the middle of a bad RUU flash, idea is you need to complete an RUU flash before you can do anything else, from this I get only try flashing several times this RUU or try with some another RUU else, if there is no fastboot this is hard to be fixed, try sending pm to @legen_dary , he experimented for a while to find some s-off way, so he should know a little bit more about this stuff. I'll continue the search, if find something will share, you also, do share what have you discovered, and if something works what is it.

shortyoko said:
Well from what I get so far you're stuck in the middle of a bad RUU flash, idea is you need to complete an RUU flash before you can do anything else, from this I get only try flashing several times this RUU or try with some another RUU else, if there is no fastboot this is hard to be fixed, try sending pm to @legen_dary , he experimented for a while to find some s-off way, so he should know a little bit more about this stuff. I'll continue the search, if find something will share, you also, do share what have you discovered, and if something works what is it.
Click to expand...
Click to collapse
Thanks for the reply. As I mentioned, the moment i connect the phone via the USB cable, it automatically goes into fastboot mode as when i run "fastboot devices", my device shows up. So I'm considering, not all hope is lost. I have to get to work, will be getting my phone back today, will experiment some and get back here at night.
forgot to mention a couple of things.
1. the bootloader shows relocked. On running the fastboot flash unlocktoken Unlock_code.bin, the command completes successfully but the bootloader still shows relocked. And because it constantly shows relocked, I'm not able to install a custom recovery as well.
2. tried putting the rom in the RUU on sdcard and renaming it as PBsomething.zip. but it wont read the sd card. So flashed it manually via fastboot flash zip zipname.zip runs upto a certain point then gives me something like this
RUU: "FAILED (remote: 90 hboot pre-update! please flush image again immediately)" So I tried reflashing it, but keeps giving the same error.
So since the sd card is not being read at all, I guess bortak's method of creating a goldcard goes out the window.

Hmmm.. This is the second such case i've seen..
Have you tried getting the unlock token again from htcdev??
Also, try updating your hboot version...
Or, get any hboot from an ruu, and do a
Code:
fastboot boot hboot.img
If it wrks, you'll atleast be able to unlock the bootloader, and put a recovery on it..
If, however, your original bootloader remains locked, then you wont be able to access the recovery as well..
In fact, it wouldnt go past the hboot...
ғг๏๓ ҭђє ғเรђ™
---------- Post added at 08:19 AM ---------- Previous post was at 08:15 AM ----------
legen_dary said:
hmmm.. This is the second such case i've seen..
Have you tried getting the unlock token again from htcdev??
Also, try updating your hboot version...
Or, get any hboot from an ruu, and do a
Code:
fastboot boot hboot.img
if it wrks, you'll atleast be able to unlock the bootloader, and put a recovery on it..
If, however, your original bootloader remains locked, then you wont be able to access the recovery as well..
In fact, it wouldnt go past the hboot...
Edit : The correct filename is pj03img.zip(or something)..
When the phone first starts in the hboot, you should see a series of filenames, along with "not found" errors.. If you do, then it does scan the sdcard...
ғг๏๓ ҭђє ғเรђ™
Click to expand...
Click to collapse
ғг๏๓ ҭђє ғเรђ™

legen_dary said:
Hmmm.. This is the second such case i've seen..
Have you tried getting the unlock token again from htcdev??
Also, try updating your hboot version...
Or, get any hboot from an ruu, and do a
Code:
fastboot boot hboot.img
If it wrks, you'll atleast be able to unlock the bootloader, and put a recovery on it..
If, however, your original bootloader remains locked, then you wont be able to access the recovery as well..
In fact, it wouldnt go past the hboot...
ғг๏๓ ҭђє ғเรђ™
---------- Post added at 08:19 AM ---------- Previous post was at 08:15 AM ----------
ғг๏๓ ҭђє ғเรђ™
Click to expand...
Click to collapse
Thanks. will try it out and get back to you but after about 12 hours, I am yet to get back my phone and gotta get to work.

burnt nand
your nand is burnt.you should use cute_prince's method.
Steps of solution
1.flash twrp via fastboot -------fastboot flash recovery twrp.img
2.boot recovery via fastboot------fastboot boot twrp.img
3.apply cute prince method -------http://forum.xda-developers.com/showpost.php?p=36868966&postcount=2367
4.re lock bootloader via fastboot ------fastboot oem lock
5.run compatible ruu
6[optional ] unlock bootloader and Flash favourite rom

juristokrat said:
your nand is burnt.you should use cute_prince's method.
Steps of solution
1.flash twrp via fastboot -------fastboot flash recovery twrp.img
2.boot recovery via fastboot------fastboot boot twrp.img
3.apply cute prince method -------http://forum.xda-developers.com/showpost.php?p=36868966&postcount=2367
4.re lock bootloader via fastboot ------fastboot oem lock
5.run compatible ruu
6[optional ] unlock bootloader and Flash favourite rom
Click to expand...
Click to collapse
He's unable to unlock the bootloader so it's impossible to flash a custom recovery
You can't use fastboot boot or fastboot flash with a locked bootloader. Can you get into HBOOT mode by holding volume down and power while switching on the device? Or does it go straight into FASTBOOT mode?

i tried
1) unlocking bootloader, and now its unlocked.
2) fastboot getvar all gives me
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.03.0000
(bootloader) version-baseband: 1.11.82.17
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.720.3
(bootloader) serialno: ********
(bootloader) imei: *******
(bootloader) product: pico
(bootloader) platform: HBOOT-7225A
(bootloader) modelid: PJ0310000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 3673mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 30d3dcb5
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.032s
3) fastboot oem boot boots up the phone and is now stuck in a bootloop. gives me the htc jingle and restarts. tried pulling the battery and volume down + power combination to get to the hboot menu, but brings me back to the black htc screen with 4 triangles. At least there is some progress. Now I somehow just need to get that menu back that comes up after the volume down + power combination.
4) tried fastboot oem resetRUUflag and it gave me this -
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.009s
5) tried fastboot boot hboot.img with the boot.img from the RUU
it gave me -
creating boot image...
creating boot image - 788480 bytes
downloading 'boot.img'...
OKAY [ 0.263s]
booting...
FAILED (remote: reproduce boot image with on-flash ramdisk error)
finished. total time: 0.300s

Can you get into recovery?

The boot.img file is the kernel bro.. Not the hboot..
The file you're looking for is hboot -something-something.img
ғг๏๓ ҭђє ғเรђ™

@sachin thomas - No I can't get into recovery
@legen_dary - hboot_1.03.0000_30d3dcb5_1129_signed this one right ? i just renamed it to hboot.img to avoid typing or copying the whole name
EDIT : i find this flag out of place . (bootloader) boot-mode: RUU. should it be RUU ? i think this is the one causing all the problem, though of course i may be wrong.

salil_1337 said:
@sachin thomas - No I can't get into recovery
@legen_dary - hboot_1.03.0000_30d3dcb5_1129_signed this one right ? i just renamed it to hboot.img to avoid typing or copying the whole name
EDIT : i find this flag out of place . (bootloader) boot-mode: RUU. should it be RUU ? i think this is the one causing all the problem, though of course i may be wrong.
Click to expand...
Click to collapse
You can't boot from a signed HBOOT image because it's a plain binary file and not an android boot image. As you have unlocked the bootloader try fastboot boot with any recovery.img file (CWM or TWRP)

Sachin Thomas said:
You can't boot from a signed HBOOT image because it's a plain binary file and not an android boot image. As you have unlocked the bootloader try fastboot boot with any recovery.img file (CWM or TWRP)
Click to expand...
Click to collapse
EXCELLENT !
did this -
I:\Android Rooting\Flash>fastboot boot recovery-clockwork-5.0.2.8-pico.img
downloading 'boot.img'...
OKAY [ 0.810s]
booting...
OKAY [ 0.014s]
finished. total time: 0.834s
and now I am in CWM recovery screen.
EDIT 1: wiped all partitions.
EDIT 2 : rebooted the phone to check if it let me into the hboot menu, but it comes back to the black htc screen with 4 exclamation marks

salil_1337 said:
EXCELLENT !
did this -
I:\Android Rooting\Flash>fastboot boot recovery-clockwork-5.0.2.8-pico.img
downloading 'boot.img'...
OKAY [ 0.810s]
booting...
OKAY [ 0.014s]
finished. total time: 0.834s
and now I am in CWM recovery screen.
EDIT : wiped all partitions.
Click to expand...
Click to collapse
To be on the safer side do cute_prince's nand recovery procedure as juristokrat suggested

Sachin Thomas said:
To be on the safer side do cute_prince's nand recovery procedure as juristokrat suggested
Click to expand...
Click to collapse
i did that when i got my nand burned after installing cm10 beta 6. But AFAIK and as far as I understand, i need to place the flash_erase file into system/xbin. I am right now stuck in recovery. How am I supposed to do it from there ? is there a flashable zip for it which will run the commands via recovery ?
EDIT : this is FAR better than i expected. since I'm in recovery, adb devices spits this out -
adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
SH1BJVN07184 recovery

salil_1337 said:
i did that when i got my nand burned after installing cm10 beta 6. But AFAIK and as far as I understand, i need to place the flash_erase file into system/xbin. I am right now stuck in recovery. How am I supposed to do it from there ? is there a flashable zip for it which will run the commands via recovery ?
Click to expand...
Click to collapse
Mount your SD card in recovery and place the file in the root of the SD card. Now, if you have TWRP you can use its file manager to move it into system/xbin and set permissions to 755
If you have CWM you can type the following in adb shell:
cd /
mv /sdcard/flash_erase /system/xbin
cd system/xbin
chmod 755 flash_erase
Click to expand...
Click to collapse
Then find a newer RUU and run it

Sachin Thomas said:
Mount your SD card in recovery and place the file in the root of the SD card. Now, if you have TWRP you can use its file manager to move it into system/xbin and set permissions to 755
If you have CWM you can type the following in adb shell:
Click to expand...
Click to collapse
OK. booted via twrp, copied file from sd card, but there seems to be no xbin folder in system
EDIT : ran it directly from the sd card via the terminal in twrp, it ran without errors. rebooted the phone, still comes up to the black htc screen

salil_1337 said:
OK. booted via twrp, copied file from sd card, but there seems to be no xbin folder in system
Click to expand...
Click to collapse
Mount system

Sachin Thomas said:
Mount system
Click to expand...
Click to collapse
after mounting system, its still showing only one folder in system . lost+found. nothing else.
ran it directly from the sd card via the terminal in twrp, it ran without errors. rebooted the phone, still comes up to the black htc screen

salil_1337 said:
after mounting system, its still showing only one folder in system . lost+found. nothing else.
ran it directly from the sd card via the terminal in twrp, it ran without errors. rebooted the phone, still comes up to the black htc screen
Click to expand...
Click to collapse
Oh, the xbin folder should have got deleted when you formatted system. I don't think you can't get rid of the HTC screen without successfully flashing an RUU. Our aim is to get rid of bad blocks which prevents the RUU from getting flashed
Are you sure that it ran without errors? Move it into /system and change permission to 755 and re-run it before attempting to flash another RUU

RUU M8_VZW 4.4.3 (s-off only)

S-off ONLY!!
As many of you are aware, flashing roms to our phone comes with risk. That risk is dimished by the availability of an RUU for our phone.
I have created as much of an RUU as we can put together at this point. This is for s-off users only. I repeat...s-off only.
This zip is an RUUmode/hboot flashable stock RUUish compilation of the current boot/hboot/system/recovery/radio/firmware images. Just like an RUU... this WILL wipe your phone (internal memory). IF you are able...backup data prior to using this. This works EXACTLY like an RUU for s-off users. Two options exist for using this zip. This will land you on STOCK kitkat 4.4.3 pre-rooted with stock recovery. I have tested this on my kid's wife's M8 (she has no choice... ).
NOTE...HTC started preloading some files to /data on the latest Rom. There's not a clean way to add them to an ruu so please flash the following file in recovery after getting your phone back to stock. If you don't, the only problem would be that gallery is missing the sticker files under edit.
If coming from 4.4.4 firmware you will need to flash 4.4.3. in RUU mode prior to flashing this..
- https://www.androidfilehost.com/?fid=23622183712470028
Option 1
Copy 0P6BIMG.zip to root of a physical SD formatted to fat32. No exfat! No internal storage! Must be external SD formated to fat32!
Reboot phone to bootloader and follow prompts once RUU is detected by phone.
Option 2 (Might not be working!)
Fastboot RUU mode . This method assumes you have a working ADB/Fastboot directory on your PC. Download RUUish file and place in your working fastboot/adb directory. Boot your phone to fastboot mode and connect to PC. Issue the following commands.
fastboot oem rebootRUU
###while in this mode your phone will display an HTC logo on the screen
fastboot flash zip 0P6BIMG.zip
##while in this mode you will see an HTC logo on the screen and a green status bar across the bottom of the screen. When command output ##completes it may say reboot required to flush etc... if that's the case issue a "fastboot reboot-bootloader" command and restart option 1 again.
example
## assuming flash completes and no further flushing/reboots are requested from the cmd output you can now either do one of two things 1)##reboot or 2)flash a custom recovery. IF you simply wish to reboot the system you can issue "fastboot reboot" which will reboot system.
## expect a good 5 minute plus first boot!
Optional If you wish to flash a custom recovery before leaving RUU mode you can. This is helpful if you have relocked for any reason as you CAN flash a recovery using this method while locked (since s-off). Download the ruuM8TWRP_2_7_1.zip below and place it in your working fastboot/adb directory. Once in place, issue the following command.
fastboot flash zip ruuM8_TWRP_2_7_1.zip
##example output
C:\Users\dottat\Downloads\mini-sdk-1.0.31-windows>fastboot flash zip ruuM8_TWRP_2_7_1.zip
target reported max download size of 1830711296 bytes
sending 'zip' (11756 KB)...
OKAY [ 1.404s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) total_image_number=1
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,7
(bootloader) [RUU]UZ,recovery,13
(bootloader) [RUU]UZ,recovery,20
(bootloader) [RUU]UZ,recovery,27
(bootloader) [RUU]UZ,recovery,36
(bootloader) [RUU]UZ,recovery,41
(bootloader) [RUU]UZ,recovery,57
(bootloader) [RUU]UZ,recovery,62
(bootloader) [RUU]UZ,recovery,69
(bootloader) [RUU]UZ,recovery,76
(bootloader) [RUU]UZ,recovery,84
(bootloader) [RUU]UZ,recovery,90
(bootloader) [RUU]UZ,recovery,97
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
OKAY [ 3.713s]
finished. total time: 5.117s
Once completed you can issue the command "fastboot reboot-bootloader" to return to hboot so you can enter recovery.
Downloads Do NOT mirror these elsewhere.
RUU link
- https://www.androidfilehost.com/?fid=23622183712470087
md5 f223e75d24266c379849e9e4a606f3d1
RUU Mode TWRP 2.8
- https://www.androidfilehost.com/?fid=23622183712470114
md5 2c654e1eadc0c3f3d1477591fb4e84b7
Stickers Fix
- http://www.androidfilehost.com/?fid=23329332407590188
md5 dda3713d8d0c4b50a1c80814c8bd07c5
HTC backup app (highly recommend this gem)
- http://www.androidfilehost.com/?fid=23329332407589902
md5 b7ec08c021b5fb8b1b86a0ab3535c1dd

mine................

You had me all excited for a minute!!! Great to see your getting ready tho. Thanks for all of your hard work.

Sweet!

Nice!.... Your last ruu saved my a$$!

ughhhh, i almost wet my pants

Sweet

Oh yes, the new 4.4.3 firmware we've all been waiting for....
nope! Just dottat (in my Chuck Testa voice)

JWhetstone02 said:
Oh yes, the new 4.4.3 firmware we've all been waiting for....
nope! Just dottat (in my Chuck Testa voice)
Click to expand...
Click to collapse
You guys crack me up. Enjoying the wait eh?

dottat said:
You guys crack me up. Enjoying the wait eh?
Click to expand...
Click to collapse
Patience is a virtue... Unfortunately, not one of mine.

Well played, almost had me ready to leave work early and head home hahaha

JediMindTrixx said:
Patience is a virtue... Unfortunately, not one of mine.
Click to expand...
Click to collapse
Hah... you don't have to explain... I DID get my moto 360 this weekend.. so i understand completely

dottat said:
Hah... you don't have to explain... I DID get my moto 360 this weekend.. so i understand completely
Click to expand...
Click to collapse
I know its off topic but since we are waiting, what are your thoughts on the moto 360 so far?

JediMindTrixx said:
Patience is a virtue... Unfortunately, not one of mine.
Click to expand...
Click to collapse
Bwuahahaha I hear that @JediMindTrixx I've been patient for far to long. Hope soon it's released. No more 4min wait boot up*yaay*.
Sent from my Insanely powered M8 using Tapatalk

Code:
[QUOTE="dottat, post: 55361775, member: 3472611"][B][SIZE="5"]S-off ONLY!![/SIZE][/B]
As many of you are aware, flashing roms to our phone comes with risk. That risk is dimished by the availability of an RUU for our phone.
I have created as much of an RUU as we can put together at this point. This is for s-off users only. I repeat...s-off only.
This zip is an RUUmode/hboot flashable stock RUUish compilation of the current boot/hboot/system/recovery/radio/firmware images. Just like an RUU... this WILL wipe your phone (internal memory). IF you are able...backup data prior to using this. This works EXACTLY like an RUU for s-off users. Two options exist for using this zip. This will land you on STOCK kitkat 4.4.3 pre-rooted with stock recovery. I have tested this on my [STRIKE]kid's[/STRIKE] wife's M8 (she has no choice... :)).
NOTE...HTC started preloading some files to /data on the latest Rom. There's not a clean way to add them to an ruu so please flash the following file in recovery after getting your phone back to stock. If you don't, the only problem would be that gallery is missing the sticker files under edit.
[B][SIZE="5"]Option 1[/SIZE][/B]
Fastboot RUU mode (preferred). This method assumes you have a working ADB/Fastboot directory on your PC. Download RUUish file and place in your working fastboot/adb directory. Boot your phone to fastboot mode and connect to PC. Issue the following commands.
fastboot oem rebootRUU
###while in this mode your phone will display an HTC logo on the screen
fastboot flash zip 0P6BIMG.zip
##while in this mode you will see an HTC logo on the screen and a green status bar across the bottom of the screen. When command output ##completes it may say reboot required to flush etc... if that's the case issue a "fastboot reboot-bootloader" command and restart option 1 again.
example
[HIDE][/HIDE]
## assuming flash completes and no further flushing/reboots are requested from the cmd output you can now either do one of two things 1)##reboot or 2)flash a custom recovery. IF you simply wish to reboot the system you can issue "fastboot reboot" which will reboot system.
## expect a good 5 minute plus first boot!
[B]Optional[/B] If you wish to flash a custom recovery before leaving RUU mode you can. This is helpful if you have relocked for any reason as you CAN flash a recovery using this method while locked (since s-off). Download the ruuM8TWRP_2_7_1.zip below and place it in your working fastboot/adb directory. Once in place, issue the following command.
fastboot flash zip ruuM8_TWRP_2_7_1.zip
##example output
[HIDE]C:\Users\dottat\Downloads\mini-sdk-1.0.31-windows>fastboot flash zip ruuM8_TWRP_2_7_1.zip
target reported max download size of 1830711296 bytes
sending 'zip' (11756 KB)...
OKAY [ 1.404s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) total_image_number=1
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,7
(bootloader) [RUU]UZ,recovery,13
(bootloader) [RUU]UZ,recovery,20
(bootloader) [RUU]UZ,recovery,27
(bootloader) [RUU]UZ,recovery,36
(bootloader) [RUU]UZ,recovery,41
(bootloader) [RUU]UZ,recovery,57
(bootloader) [RUU]UZ,recovery,62
(bootloader) [RUU]UZ,recovery,69
(bootloader) [RUU]UZ,recovery,76
(bootloader) [RUU]UZ,recovery,84
(bootloader) [RUU]UZ,recovery,90
(bootloader) [RUU]UZ,recovery,97
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
OKAY [ 3.713s]
finished. total time: 5.117s[/HIDE]
Once completed you can issue the command "fastboot reboot-bootloader" to return to hboot so you can enter recovery.
[B][SIZE="5"]Option 2[/SIZE][/B]
Copy 0P6BIMG.zip to root of a physical SD formatted to fat32. No exfat! No internal storage! Must be external SD formated to fat32!
Reboot phone to bootloader and follow prompts once RUU is detected by phone.
[B]Downloads[/B]
[B]RUU link [/B]
[url]pending[/url]
md5
[B]RUU Mode TWRP 2.7.1[/B]
[url]https://www.androidfilehost.com/?fid=23622183712469358[/url]
md5 db77a00008eed750b4900f4c1ebb59a8
[B]Stickers Fix[/B]
[url]http://www.androidfilehost.com/?fid=23329332407590188[/url]
md5 dda3713d8d0c4b50a1c80814c8bd07c5
[B]HTC backup app (highly recommend this gem)[/B]
[url]http://www.androidfilehost.com/?fid=23329332407589902[/url]
md5 b7ec08c021b5fb8b1b86a0ab3535c1dd[/QUOTE]
So, what improvements are made with this, what will it change, how dangerous is it, and will it affect me on AOSP roms?

bracketslash said:
Code:
So, what improvements are made with this, what will it change, how dangerous is it, and will it affect me on AOSP roms?
Click to expand...
Click to collapse
They added more bacon, the version number will change, dwarves may eat your cat but other than that you're safe, and finally no it shouldn't affect aosp unless your cat maintains the device in which case being eaten by a dwarf will hamper releases.

bracketslash said:
Code:
So, what improvements are made with this, what will it change, how dangerous is it, and will it affect me on AOSP roms?
Click to expand...
Click to collapse
This is the latest article I could find that explains most of the changes. Hope this helps.
http://www.android.gs/verizon-htc-one-m8-android-4-4-3-update-available-now-for-download/

mademan420 said:
I know its off topic but since we are waiting, what are your thoughts on the moto 360 so far?
Click to expand...
Click to collapse
My daily driver phone is a one max.. so far.. my moto 360 and my one max seem to be linked on battery life. At the end of the day, I have almost half of the battery on each device left. I have my moto 360 screen not set to that mode that keeps the screen on all the time. I like it. It does exactly what i was hoping it would and it's not killing the battery.

Nandroid Backup Beforehand
This may be stupid but would I be able to flash the RUU and then restore a nandroid i made right before to get all my data and apps etc back on the phone with the new firmware??

Seanzle said:
This may be stupid but would I be able to flash the RUU and then restore a nandroid i made right before to get all my data and apps etc back on the phone with the new firmware??
Click to expand...
Click to collapse
I do it that way when i'm on a stock rom that i've made changes to that i'm too lazy to undo... If it's very close to stock, usually restoring just /data works fine. Alternatively, you can use the HTC backup app in the OP to have your texts/email accounts/desktop/apps(no app data)/etc backed up.

(Q) ONE SV firmware totally wrecked

so here's the thing. My GF One SV crashed today on reboot. yeaaah right the well known "stuck on quietly brilliant screen thing" but for me no problem cause for sure it ain't the first htc and it ain't the first time this sh*t happens :cyclops:
So unlocked the bootloader via htc-dev, flashed TWRP recovery and flashed several different kernels (4.1.2 and 4.2.2) cause we both don't know which stock firmware her phone has. I do know what's in her bootloader but I don't know what's on her system partition. Well back to the story. After flashing and failing several times i took a look on the partitions (twrp -> backup) and saw that some partitions were missing so I wiped cache through TWRP and I saw several failures e.g. "..can't mount /data" and also the system partition only had 19MB quite few for a approx. 700MB firmware file!
I read along the xda-developer forums and was told that I'm supposed to try another recovery. So did I (TWRP 2.6.X.X till 2.8.X.X tried every single one) and I had a change in the phones behavior! Now nothing works except the bootloader with fastboot. No matter which one of the recoveries I flash...
This phone just can't be serious! I had this situation more than once with my One X and it always could be solved by flashing another kernel but the One SV is one b*tch of a phone
please help me!

Only a kernel doesn't help you, if the system partition is screw up.
Don't flash different recoverys, 2.8 was never out for EU SV's. You can break even more in this way. I guess the newest recovery you can use is this one.
But first, post your info from your bootloader and output of fastboot getvar all

HEY EVERYONE!
So about 3 days ago I got myself this HTC ONE SV and today I decided to update the HTC software to the SENSE 5..
OH MAN, do I so regret it! I don't like the icons, the layout or nothing!:thumbdown:
I just wanna go back to 2 days ago..when I was excited about my new phone!!!!
I chatted with an HTC rep and I was told there was nothing I could do about the update...but if I choose, a soft reset could be done..
LONG STORY SHORT..
PLEASE PLEASE PLEASE SOMEONE TELL ME THERE IS HOPE OF RETURNING MY PHONE TO IT'S ORIGINAL STATE!
And if there is...how I could fix this issue...
Boost is my carrier btw..
Thanks so much to all!
Love, Elysia:thumbup::thumbup::thumbup:
Sent from my C525c

@old.splatterhand
old.splatterhand said:
Only a kernel doesn't help you, if the system partition is screw up.
Don't flash different recoverys, 2.8 was never out for EU SV's. You can break even more in this way. I guess the newest recovery you can use is this one.
But first, post your info from your bootloader and output of fastboot getvar all
Click to expand...
Click to collapse
Bootloader information:
***TAMPERED***
***UNLOCKED***
K2_UL PVT SHIP S-ON RL
HBOOT-2.21.0000
Radio 1.23.40h.00.20
Open DSP-v13.2.0268.0620
OS-
eMMC boot 1024MB
fastboot:
GearX-2latform-tools GearX$ ./fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.21.0000
(bootloader) version-baseband: 1.23.40h.00.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT321TP03551
(bootloader) imei: ********************
(bootloader) meid:
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8010000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 4316mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2bb255c2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.072s
Click to expand...
Click to collapse
thank you in advance!

GearX said:
@old.splatterhand
Bootloader information:
***TAMPERED***
***UNLOCKED***
K2_UL PVT SHIP S-ON RL
HBOOT-2.21.0000
Radio 1.23.40h.00.20
Open DSP-v13.2.0268.0620
OS-
eMMC boot 1024MB
fastboot:
thank you in advance!
Click to expand...
Click to collapse
Ok, the recovery you should use is link in my post above. Flash it and try to flash this rom (k2_ul version) from twrp. If that don't work, you don't have much chances.

updated recovery to 2.8.4.0 compatible with 2.21 hboot: http://forum.xda-developers.com/htc...recovery-twrp-2-8-4-0-touch-recovery-t3011704
please report if any bugs

elysiawashere said:
HEY EVERYONE!
So about 3 days ago I got myself this HTC ONE SV and today I decided to update the HTC software to the SENSE 5..
OH MAN, do I so regret it! I don't like the icons, the layout or nothing!:thumbdown:
I just wanna go back to 2 days ago..when I was excited about my new phone!!!!
I chatted with an HTC rep and I was told there was nothing I could do about the update...but if I choose, a soft reset could be done..
LONG STORY SHORT..
PLEASE PLEASE PLEASE SOMEONE TELL ME THERE IS HOPE OF RETURNING MY PHONE TO IT'S ORIGINAL STATE!
And if there is...how I could fix this issue...
Boost is my carrier btw..
Thanks so much to all!
Love, Elysia:thumbup::thumbup::thumbup:
Sent from my C525c
Click to expand...
Click to collapse
Hello Elysia.
Basically they are right, they don't provide an option to downgrade.
But, when you are S-off, there is an way to downgrade your software. But this is not an easy way for a beginner! You should also know, if you are doing something wrong on this way, you can brick your device!
To show you the way you have to go:
- Unlock your device/bootloader at www.htcdev.com
- Flash TWRP recovery and SuperSu to get root
- S-off your device using www.rumrunner.us
- downgrade your hboot using PL80IMG.zip method
- flash the 2.06 RUU for Boost
- Profit
Basic knowledge in adb/fastboot commands are important!

old.splatterhand said:
Ok, the recovery you should use is link in my post above. Flash it and try to flash this rom (k2_ul version) from twrp. If that don't work, you don't have much chances.
Click to expand...
Click to collapse
Okay thank you. So did I:
GearX: platform-tools GearX$ ./fastboot flash recovery openrecovery-twrp-2.7.0.1-k2_ul.img
sending 'recovery' (8382 KB)...
OKAY [ 1.209s]
writing 'recovery'...
OKAY [ 2.299s]
finished. total time: 3.508s
GearX: platform-tools GearX$ ./fastboot erase cache
erasing 'cache'...
OKAY [ 0.135s]
finished. total time: 0.135s
GearX: platform-tools GearX$ ./fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.195s]
finished. total time: 0.195s
Click to expand...
Click to collapse
unfortunately I'm stuck in the Bootscreen which says in pink: "Entering Recovery..."

What recovery did you use? The one linked by me has a different name!

old.splatterhand said:
What recovery did you use? The one linked by me has a different name!
Click to expand...
Click to collapse
I used the TWRP 2.7.0.1 from their official homepage. I tried it again with the recovery from your link:
GearX: platform-tools GearX$ ./fastboot flash recovery TWRP-2.7.0.1-k2_ul-k2u.img
sending 'recovery' (8452 KB)...
OKAY [ 1.209s]
writing 'recovery'...
OKAY [ 2.313s]
finished. total time: 3.522s
GearX: platform-tools GearX$ ./fastboot erase cache
erasing 'cache'...
OKAY [ 0.135s]
finished. total time: 0.135s
GearX: platform-tools GearX$ ./fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.182s]
finished. total time: 0.182s
Click to expand...
Click to collapse
...and lol it works?!?!?!?! Where the heck is the difference between yours and the one from official TWRP?

The official is build on old sources and not updated to 4.2.2 for this device.
Next time use the files we are telling you!

old.splatterhand said:
The official is build on old sources and not updated to 4.2.2 for this device.
Next time use the files we are telling you!
Click to expand...
Click to collapse
Right. Now I flashed the recommended firmware file:
GearX: platform-tools GearX$ ./adb push k2ul_4.2.2_3.11.401.1_stock_odexed_v3.zip /sdcard/
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
3244 KB/s (681159041 bytes in 205.034s)
GearX: platform-tools GearX$ ./fastboot flash boot boot.img
sending 'boot' (6160 KB)...
OKAY [ 0.982s]
writing 'boot'...
OKAY [ 1.817s]
finished. total time: 2.800s
GearX: platform-tools GearX$ ./fastboot erase cache
erasing 'cache'...
OKAY [ 0.153s]
finished. total time: 0.153s
GearX: platform-tools GearX$ ./fastboot reboot
rebooting...
finished. total time: 0.181s
Click to expand...
Click to collapse
When I flashed the firmware throught TWRP the blue part of the progress bar reached nearly 50% and after 5 seconds of flashing it rebooted itself...
But it still hangs itself in the quietly brilliant screen

First, you are trying to flash a rom, not the firmware.
Then, how did you flash the rom, in recovery -> install?
Have you done a wipe before?

old.splatterhand said:
First, you are trying to flash a rom, not the firmware.
Then, how did you flash the rom, in recovery -> install?
Have you done a wipe before?
Click to expand...
Click to collapse
I pushed the rom via adb to the sdcard root folder, then installed it through TWRP recovery -> install -> selected the zip
no wipe before. Which partitions should be wiped? I want to lose as less personal data as possible.

Right now i think there isn't any data to loose and you should be happy if you can bring up the phone back to life.
But just in case, make a backup of system, data, cache & dalvik (and if available android.secure), then wipe - advanced and wipe those partitions.
---------- Post added at 14:05 ---------- Previous post was at 14:03 ----------
I think you can also start to download this TWRP backup.

old.splatterhand said:
Right now i think there isn't any data to loose and you should be happy if you can bring up the phone back to life.
But just in case, make a backup of system, data, cache & dalvik (and if available android.secure), then wipe - advanced and wipe those partitions.
---------- Post added at 14:05 ---------- Previous post was at 14:03 ----------
I think you can also start to download this TWRP backup.
Click to expand...
Click to collapse
Thank you sir
without the wiping it would've never worked! after the wiping the rom installed correctly, then I flashed the kernel through fastboot and now it works correct again :good:

Glad to hear

old.splatterhand said:
Glad to hear
Click to expand...
Click to collapse
bought you a beer via PayPal for your fast and excellent help :good:

GearX said:
bought you a beer via PayPal for your fast and excellent help :good:
Click to expand...
Click to collapse
Thanks a lot. I really appreciate it :good:

old.splatterhand said:
Thanks a lot. I really appreciate it :good:
Click to expand...
Click to collapse
unfortunately I need to pick up this thread again...
As everything was fine some days passed. Early in february the device began to mess around again. First time it hung itself while charging over night (nothing else was done because I was sleeping) and the phone didn't wake me up on time. That one really sucked. I pulled the battery for about 10 minutes, pushed it back into the phone, started it up and everything was fine.
Approximately one week later a very similar situation. The device was in the locker while I was working and in the afternoon when I came back it was in TWRP. It was not possible to tap anything because the touchscreen did not respond as it should So once again I pulled the battery for some minutes... afterwards I tried to start it normal but I wouldn't want to do so. I plugged it to the charger and suddenly it started normally. Again it worked for a few days but then...
...some days later I wanted to pick it up from my locker after work and it was off. Since then it was not possible to start it anymore. It does not respond to anything. Power + volume- or power + Volume+ or only the volume button. The only reaction is when its plugged to the charger: the charging LED flashes once shortly. Then no more signal.
What has happened to the SV?

Ville c2 bricked? unable to mount SD card, no recovery

Hi guys, so a while ago I flashed Venom Rom to my one s c2.
In the recent weeks I noticed, that the memory was getting more and more full. But I couldn't find the files responsible for that.
So I did a factory reset, which didn't help. So I tried to wipe the storage in TWRP 2.6.3.0. . Furthermore I did a "total wipe" so I checked every option in the wipe section.
After that, I couldn't boot the phone, because there seemed to be no OS installed. So i tried to flash the ROM which I loaded onto the phones storage but it was gone.
When I tried to transfer a ROM to the phone's storage it said "unable to mount sdcard". So I couldn't transfer any files to my phone.
After hours of reading through various threads, I tried to get it back to stock by running a RUU.
Unfortunately I couldnt find the exact one for my device. This is what fastboot displays when i type in "fastboot getvar all":
version: 0.5
version-bootloader: 3.01.0000
version-baseband: 16.15.20.29_M
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: SH25YW404475
imei: 352762055439276
meid:
product: villec2
platform: HBOOT-8260
modelid: PJ4020000
cidnum: HTC__102
battery-status: good
battery-voltage: 4014mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 9006d003
hbootpreupdate: 11
gencheckpt: 0
So I tried these ones (tried running as administrator as well):
RUU_VILLEC2_U_ICS_40_HTC_Europe_1.09.401.101_Radio_16.11.20.02U_16.05.20.11_M2_release_261381_signed
and
RUU_VILLEC2_U_ICS_40_HTC_Europe_1.11.401.101_Radio_16.12.20.02U_16.05.20.16_M2_release_261661_signed
But they didnt work out. It always displays "error 155" and on the phone's display it says "older hboot version" .
And now I can't even access the recovery anymore... And because I tried to run a RUU I relocked my bootloader....
I really can't find a RUU with the correct Radio and don't know how to identify the hboot version of the RUU.
I already tried to flash a recovery again via fastboot, but it didn't work as well :
C:\*****\platform-tools>fastboot flash recovery twrpvillec2.img
sending 'recovery' (6420 KB)...
OKAY [ 1.291s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.079s
I'm really lost guys, I hope I didn't hardbrick my phone.
If anyone has any suggestions, please help.
Thanks!

maybe you can try this rom http://androidruu.com/download.php?...326a10c55adc0bf34ecb3f5611d8b1015471164225450 "RUU_VILLEC2_U_ICS_40_HTC_Europe_1.11.401.110_Radio_16.12.20.02U_16.05.20.16_M2_release_263510_signed.exe"
you must have your bootloader relock to use a run. and unlock to flash a custom recovery

JavierG123 said:
maybe you can try this rom http://androidruu.com/download.php?...326a10c55adc0bf34ecb3f5611d8b1015471164225450 "RUU_VILLEC2_U_ICS_40_HTC_Europe_1.11.401.110_Radio_16.12.20.02U_16.05.20.16_M2_release_263510_signed.exe"
you must have your bootloader relock to use a run. and unlock to flash a custom recovery
Click to expand...
Click to collapse
Thanks for your suggestion!
I tried the RUU, but it didnt work out. Still Error 155 and the phone says "Hboot Version is older" ...
How can I read the HBOOT Version in the filename, anyway?
But running a RUU is the correct and only way to go in my situation, isnt it?

So, as I already knew, the problem was the hboot Version of my device...
So I'm now trying to downgrade my hboot version and try one of the RUUs again...

So...downgrading Bootloader doesnt work... tried every hboot version listed in this post
Maybe trying a JB RUU, which doesnt really fit all the other requirements...trying that now

Still no success, since I can't find a unbranded JB RUU fitted for my phone....
running out of ideas here...
anyone else got any suggestions?
btw: I reflashed twrp 2.6.3.0. but still cant access the internal sd...cant even mount it.

DonKaio said:
Hi guys, so a while ago I flashed Venom Rom to my one s c2.
In the recent weeks I noticed, that the memory was getting more and more full. But I couldn't find the files responsible for that.
So I did a factory reset, which didn't help. So I tried to wipe the storage in TWRP 2.6.3.0. . Furthermore I did a "total wipe" so I checked every option in the wipe section.
After that, I couldn't boot the phone, because there seemed to be no OS installed. So i tried to flash the ROM which I loaded onto the phones storage but it was gone.
When I tried to transfer a ROM to the phone's storage it said "unable to mount sdcard". So I couldn't transfer any files to my phone.
After hours of reading through various threads, I tried to get it back to stock by running a RUU.
Unfortunately I couldnt find the exact one for my device. This is what fastboot displays when i type in "fastboot getvar all":
version: 0.5
version-bootloader: 3.01.0000
version-baseband: 16.15.20.29_M
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: SH25YW404475
imei: 352762055439276
meid:
product: villec2
platform: HBOOT-8260
modelid: PJ4020000
cidnum: HTC__102
battery-status: good
battery-voltage: 4014mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 9006d003
hbootpreupdate: 11
gencheckpt: 0
So I tried these ones (tried running as administrator as well):
RUU_VILLEC2_U_ICS_40_HTC_Europe_1.09.401.101_Radio_16.11.20.02U_16.05.20.11_M2_release_261381_signed
and
RUU_VILLEC2_U_ICS_40_HTC_Europe_1.11.401.101_Radio_16.12.20.02U_16.05.20.16_M2_release_261661_signed
But they didnt work out. It always displays "error 155" and on the phone's display it says "older hboot version" .
And now I can't even access the recovery anymore... And because I tried to run a RUU I relocked my bootloader....
I really can't find a RUU with the correct Radio and don't know how to identify the hboot version of the RUU.
I already tried to flash a recovery again via fastboot, but it didn't work as well :
C:\*****\platform-tools>fastboot flash recovery twrpvillec2.img
sending 'recovery' (6420 KB)...
OKAY [ 1.291s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.079s
I'm really lost guys, I hope I didn't hardbrick my phone.
If anyone has any suggestions, please help.
Thanks!
Click to expand...
Click to collapse
You need to unlock your bootloader again than flash the stock recovery there you can make a factory reset and than your storage is back if you need the stock recovery
Or stock backup than say it...

pauldey said:
You need to unlock your bootloader again than flash the stock recovery there you can make a factory reset and than your storage is back if you need the stock recovery
Or stock backup than say it...
Click to expand...
Click to collapse
Yes please, I actually do have some older backups, but I don't know how to flash them since I can't move files to the phone anymore.
Thanks for your help!

i can suggest you install SaM ROM. this is the threat http://forum.xda-developers.com/htc-one-s/c2-development/rom-sam-rom-sense-7-blinkfeed-t3117135 using this recovery http://file.mikhei777.org.ua/HTC_VilleC2/openrecovery-twrp-2.7.1.0-villec2.img

DonKaio said:
Yes please, I actually do have some older backups, but I don't know how to flash them since I can't move files to the phone anymore.
Thanks for your help!
Click to expand...
Click to collapse
hey, here is the stock recovery:https://www.dropbox.com/s/qavj4ythvc0v4gg/recovery.img?dl=0
you need to unlock your booloader again, than go to fastboot and flash the recovery like every other: fastboot flash recovery recovery.img than: fastboot erase cache and fastboot reboot-bootloader
than you go in the stock recovery there you can make a factory reset
here you find all how you can use the stock recovery: http://llabtoofer.com/2014/02/24/how-to-manually-install-ota-updates/
and than you can flash the recovery from my backup folder after this you can mount your sd card and push the stock backup on your phone and restore the backup
and here the stock backup: https://www.dropbox.com/s/hhggqd1gith8pkf/4.1.1%20stock%20rom%20C2%20TWRP%202.6.3.0.rar?dl=0
pauldey.

Thanks guys, worked great!
Awesome!

I have the same problem. In adb devices I see some serial and 'recovery', maybe its the phone, but I got an error when tried to move another file into phone.
I've tried to unlock it again but I that code to use it in bootloader is not showing up.