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

[Q] HTC One SV brick (help)

Hi, Iam newone here. So i need your help. I have HTC One SV where it's bricked the only info where i have is :
*** TAMPERED ***
*** UNLOCKED ***
K2_UL PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.18.40a.00.05
OpenDSP-v13.2.0268.0620
OS-311.401.1
eMMC-boot 1024MB
So i tried to restore,nothing happen. fastory reset nothing happen.
I tried to install latest TWRP but it stuck ot logo of TWRP and after 5min it reboots.
I tried to turn s-on to s-off but adb can not find my device.
i tried to the latest ruu nothing again.
i tries to install rom from fastboot but i says that it can not verify signature.
I tried too remove the trampered but again adb can not see my device
HELP PLEASE.....
p.s.: sorry for my english i'm not good.....

If you using win8 try 7 cuz 8 is kind of creepy in recognizing new devices. And make sure you got the right ruu.
I'm sure @Modding.MyMind can help more.

georgekap said:
Hi, Iam newone here. So i need your help. I have HTC One SV where it's bricked the only info where i have is :
*** TAMPERED ***
*** UNLOCKED ***
K2_UL PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.18.40a.00.05
OpenDSP-v13.2.0268.0620
OS-311.401.1
eMMC-boot 1024MB
So i tried to restore,nothing happen. fastory reset nothing happen.
I tried to install latest TWRP but it stuck ot logo of TWRP and after 5min it reboots.
I tried to turn s-on to s-off but adb can not find my device.
i tried to the latest ruu nothing again.
i tries to install rom from fastboot but i says that it can not verify signature.
I tried too remove the trampered but again adb can not see my device
HELP PLEASE.....
p.s.: sorry for my english i'm not good.....
Click to expand...
Click to collapse
Ok, you had already 4.2.2 on it, thats good, no firmwareupgrade needed!
- Make sure bootloader is unlocked.
- Download and flash (with fastboot) TWRP 2.7.0.1 recovery from here (1. post)
Now you should be able to boot into recovery!
You have two ways you can go now:
- Either download this rom (k2ul version) and flash from TWRP. Don't forget, boot.img must be flashed with fastboot, because you are S-on!
- Or download this stock TWRP backup, place it on your external sd and restore it from recovery.
The location on ext_sdcard for the backup is: \TWRP\BACKUPS\"Put here the serial number of your device"

Sorry, just now reading this. Currently having battery issues with my device. May be finally taking a crap on me and since this is my only one I may be forced to get a new device thus possibly leaving this community.... Still playing with my phone to determine if it will be neceassary or not.
Sent from my C525c using Tapatalk

J.ali.li said:
If you using win8 try 7 cuz 8 is kind of creepy in recognizing new devices. And make sure you got the right ruu.
I'm sure @Modding.MyMind can help more.
Click to expand...
Click to collapse
I'm using win ultimate 7 x64

old.splatterhand said:
Ok, you had already 4.2.2 on it, thats good, no firmwareupgrade needed!
- Make sure bootloader is unlocked.
- Download and flash (with fastboot) TWRP 2.7.0.1 recovery from here (1. post)
Now you should be able to boot into recovery!
You have two ways you can go now:
- Either download this rom (k2ul version) and flash from TWRP. Don't forget, boot.img must be flashed with fastboot, because you are S-on!
- Or download this stock TWRP backup, place it on your external sd and restore it from recovery.
The location on ext_sdcard for the backup is: \TWRP\BACKUPS\"Put here the serial number of your device"
Click to expand...
Click to collapse
I tried to flash twrp but it stuck on htc and at the top it is writes entering recovery...
i tried an other one twrp 2.7.0.1 but it stucks on teamwin and after few min it reboot back to htc logo.

Have you also tried the older version Recovery_TWRP_2.6.3.2_K2_UL.img from same post?
How do you flash it?

old.splatterhand said:
Have you also tried the older version Recovery_TWRP_2.6.3.2_K2_UL.img from same post?
How do you flash it?
Click to expand...
Click to collapse
from fastboot with this command fastboot flash recovery reovery.img
i tried and the older version but it stuck on htc logo with on the top writes entering recovery

georgekap said:
from fastboot with this command fastboot flash recovery reovery.img
i tried and the older version but it stuck on htc logo with on the top writes entering recovery
Click to expand...
Click to collapse
from fastboot with this command fastboot flash recovery recovery.img *
i tried to flash the rom k2ul_4.2.2_3.11.401.1_stock_odexed_v3.zip from the phone.
i rename it pl80img.zip. and now is stuck on htc logo and reboots

Then i think your phone has another issue. Both recoveries are proved working for k2u & k2ul.
This rom is for flashing in recovery, not for the bootloader.

old.splatterhand said:
Then i think your phone has another issue. Both recoveries are proved working for k2u & k2ul.
This rom is for flashing in recovery, not for the bootloader.
Click to expand...
Click to collapse
when i flash recovery from fastboot. whene im try to get in recovery mode after how many min its boot to recovery?

No minutes, just a few seconds.

old.splatterhand said:
No minutes, just a few seconds.
Click to expand...
Click to collapse
How can i downgrade os???

Not possible without a working OS.

@ old.splatterhand
I have same problem k2_ul. phone just restart after 10 sec
i try hard reset, enter recovery with TWRP but nothing happened .
what should i do at now?

More detailed please.
The phone restarts after booting?
After you have entered the pin number?
Also without simcard/sdcard/plugged into charger (while charging)?
Which OS you are running?
Which TWRP?
Connect your phone with fastboot and type into the cmd:
Code:
fastboot getvar all
Put the output here (except your IMEI & Serial number)

This is fastboot info.
phone not getting to booting.just htc logo 10 sec then again restart phone continue.
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.21.0000
(bootloader) version-baseband: 1.18.40a.00.05
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.415.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT313Txxxx
(bootloader) imei: 3528xxxxxxxxx
(bootloader) meid:
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8010000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 3655mV
(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.063s

Please remove also your serial number.
You are able to enter recovery or not?
Post the link, where you've got the recovery from?

no i cant recovery mode.
i try many recovery.img but when i enter recovery its just give me "entering recovery" logo!!

Use this recovery.

[Q] How to erase all data with ADB command?

Hello,
I have an issue with my sensation. The screen stays black. I can boot on my ROM, the bootloader (fastboot), and the recovery, but I can't see nothing.
Someone wants to buy my phone. But I can't sell the phone with my personal data.
I need to know how to erase all data in my phone with ADB command line under fastboot.
Please, help me.

bobatomix said:
Hello,
I have an issue with my sensation. The screen stays black. I can boot on my ROM, the bootloader (fastboot), and the recovery, but I can't see nothing.
Someone wants to buy my phone. But I can't sell the phone with my personal data.
I need to know how to erase all data in my phone with ADB command line under fastboot.
Please, help me.
Click to expand...
Click to collapse
there is an option from bootloader to factory reset the device but i don't know what exactly is doing
did you try to flash an official rom(RUU.exe)?

rzr86 said:
there is an option from bootloader to factory reset the device but i don't know what exactly is doing
did you try to flash an official rom(RUU.exe)?
Click to expand...
Click to collapse
For factory reset : I try but I'm not sure it worked, because I see nothing on the screen.
For official rom(RUU.exe) : I try but it didn't work.
For information my phone is S-OFF.
For me, the solution is to do that with adb's commands. I want to do a full wipe .

bobatomix said:
For factory reset : I try but I'm not sure it worked, because I see nothing on the screen.
For official rom(RUU.exe) : I try but it didn't work.
For information my phone is S-OFF.
For me, the solution is to do that with adb's commands. I want to do a full wipe .
Click to expand...
Click to collapse
since you are on S-OFF change your cid to supercid and flash whatever ruu you want
by the way what problem did you have with ruu?

rzr86 said:
since you are on S-OFF change your cid to supercid and flash whatever ruu you want
by the way what problem did you have with ruu?
Click to expand...
Click to collapse
The phone is S-OFF and supercid.
The message with RUU is ERROR [120] : battery less than 30% - but the battery is full.
I tried this http://forums.androidcentral.com/ge...oyo-get-error-120-battery-less-than-30-a.html , and it didn't work.
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27
(bootloader) version-baseband: 11.24A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.1
(bootloader) serialno: xxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG58*****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4172mV
(bootloader) partition-layout: Generi
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse

bobatomix said:
The phone is S-OFF and supercid.
The message with RUU is ERROR [120] : battery less than 30% - but the battery is full.
I tried this http://forums.androidcentral.com/ge...oyo-get-error-120-battery-less-than-30-a.html , and it didn't work.
Click to expand...
Click to collapse
did you try what it says in post #15 of that link?
try with a different battery if you have
also wipe battery stats from recovery but i don't think it will do anything

rzr86 said:
did you try what it says in post #15 of that link?
try with a different battery if you have
also wipe battery stats from recovery but i don't think it will do anything
Click to expand...
Click to collapse
I tried with my anker. It doesn't work neither.

bobatomix said:
I tried with my anker. It doesn't work neither.
Click to expand...
Click to collapse
if i remember well it has been reported that issue before here in sensation forum
maybe you can find something here
i don't know what else to suggest

rzr86 said:
if i remember well it has been reported that issue before here in sensation forum
maybe you can find something here
i don't know what else to suggest
Click to expand...
Click to collapse
Okk, thanks for your time and your suggestions.

If you format the data partition it will clear or your personal data on your device.Just boot into recovery and wipe data partition.
You could also use the command fastboot erase data.It would be nice to delete cache too (fastboot erase cache).
If you erase data partition it could cause rom instabilities or a not working rom.In my opinion the most safe way to clear all your personal data is to make a full wipe (using 4ext recovery) and to reflash your (custom) rom.
If you have the original rom with original recovery you could use the "factory reset" option from your bootloader to reset the phone.If you have a cwm or other recovery it probably won't work.In any case an RUU would be a very good solution.Have you try to flash your phone using a rom.zip from an original RUU?You have to rename it to PG58IMG.zip and you put it to your sdcard in order to flash it from your bootloader.

Gatosbil said:
If you format the data partition it will clear or your personal data on your device.Just boot into recovery and wipe data partition.
You could also use the command fastboot erase data.It would be nice to delete cache too (fastboot erase cache).
If you erase data partition it could cause rom instabilities or a not working rom.In my opinion the most safe way to clear all your personal data is to make a full wipe (using 4ext recovery) and to reflash your (custom) rom.
If you have the original rom with original recovery you could use the "factory reset" option from your bootloader to reset the phone.If you have a cwm or other recovery it probably won't work.In any case an RUU would be a very good solution.Have you try to flash your phone using a rom.zip from an original RUU?You have to rename it to PG58IMG.zip and you put it to your sdcard in order to flash it from your bootloader.
Click to expand...
Click to collapse
It's very difficult to do something with no screen. I will try the PG58IMG.zip's method. But this method, I think, keeps all data.
I need to do a full wipe without screen, just with adb on the fastboot.

bobatomix said:
It's very difficult to do something with no screen. I will try the PG58IMG.zip's method. But this method, I think, keeps all data.
I need to do a full wipe without screen, just with adb on the fastboot.
Click to expand...
Click to collapse
fastboot oem rebootruu
fastboot erase userdata
and maybe
fastboot erase system
should remove everything

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.

[Solved]Phone does not boot

I was on the latest nightlies of CM14 when i wanted to flash SuperSU via TWRP yesterday evening. After that my phone did not boot up anymore. Now i tried flash the stock image of my xt1032 as usual. But also this does not help. The flashing procedures do not show any errors. The phone remains in the "Warning Bootloader Unlocked" screen.
So if even going back to stock is not working, i have a real problem.
Would be nice if someone could guide me towards a solution.
By the way, i do not remember anymore, but i think 1 year back i did not have the following lines after each fastboot command:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
Edit: I do not know how, but after several times of experimenting my phone back in live without doing anything special.