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

Cannot run "fastboot boot img" successfully.

I've tried everything, Windows and Mac, standalone adb and fastboot as well as full SDK version, different USB ports, and I'm at a loss on what to do.
I got a Hong Kong version U11+ (CID: HTC_622, Asia-HK-CHT)
Whatever I do every time I try to boot via the fastboot boot command in bootloader mode it seems to work at first and then nothing, just a black screen.
The terminal output seems to indicate all went well and yet that's not the case:
fastboot boot twrp-3.1.1-2_unofficial-ocm_2.img
downloading 'boot.img'...
OKAY [ 0.894s]
booting...
OKAY [ 10.112s]
finished. total time: 11.006s
Click to expand...
Click to collapse
Here is the output of fastboot getvar all:
boot-mode:FASTBOOT
unlocked:yes
off-mode-charge:0
charger-screen-enabled:0
battery-soc-ok:yes
battery-voltage:3911
version-baseband:
version-bootloader:
variant:MSM UFS
partition-type:cache:ext4
partition-size:cache: 0xE000000
partition-type:userdata:ext4
partition-size:userdata: 0x1C3C800000
partition-type:system:ext4
partition-size:system: 0x101000000
secure:yes
serialno: *removed*
product:HTC_Phone
max-download-size:536870912
kernel:uefi
Click to expand...
Click to collapse
Any clue on what is happening?

Exactly the same is happening for me when I just try and boot it rather than flash it. I'm on the Chinese variant of the phone with Chinese firmware. I get exactly the same message on adb (successfully booted) but just a black screen on the phone.

Prot02018 said:
Exactly the same is happening for me when I just try and boot it rather than flash it. I'm on the Chinese variant of the phone with Chinese firmware. I get exactly the same message on adb (successfully booted) but just a black screen on the phone.
Click to expand...
Click to collapse
How did you do ? rebooting is not as simple as we think ,

afaik, fastboot boot does not work anymore on recent HTC devices , so you have to flash it in order to boot into twrp

DeeZZ_NuuZZ said:
afaik, fastboot boot does not work anymore on recent HTC devices , so you have to flash it in order to boot into twrp
Click to expand...
Click to collapse
Oh, well that makes sense! Thanks.
Does anybody know if RUU.zips contain the stock recovery too? As well as everything else needed to get the phone back to stock?

Prot02018 said:
Oh, well that makes sense! Thanks.
Does anybody know if RUU.zips contain the stock recovery too? As well as everything else needed to get the phone back to stock?
Click to expand...
Click to collapse
A ruu contains everything
Sent from my HTC 10 using XDA Labs

aurelienlux said:
I've tried everything, Windows and Mac, standalone adb and fastboot as well as full SDK version, different USB ports, and I'm at a loss on what to do.
I got a Hong Kong version U11+ (CID: HTC_622, Asia-HK-CHT)
Whatever I do every time I try to boot via the fastboot boot command in bootloader mode it seems to work at first and then nothing, just a black screen.
The terminal output seems to indicate all went well and yet that's not the case:
Here is the output of fastboot getvar all:
Any clue on what is happening?
Click to expand...
Click to collapse
Hi. I have the same phone but my max download size is 2399200000. Is there any reason why yours is lots higher than mine? I tried flashing a RUU and I keep getting messages saying file size larger than device limit. Is there a way we can change this max download limit? Thanks.

bricked htcu11 i think, please help !!!

Hello All,
Please can someone help, I successfully rooted my htc u11 and put a custom rom on to phone . I decided to go back to stock and restore my phone as new. I had unlocked and locked my bootloader all ok.
Now I have the problems, my phone cant seem to unlock bootloader, everytime I try and fastboot recovery or roms. I get this message 9 ru security fail recovery and bootloader isn't bl-unlocke.
Im stuck ,plus when I boot the phone I get the message, your phone is not to be trusted . Please can anyone help.

mackenzie121 said:
Hello All,
Please can someone help, I successfully rooted my htc u11 and put a custom rom on to phone . I decided to go back to stock and restore my phone as new. I had unlocked and locked my bootloader all ok.
Now I have the problems, my phone cant seem to unlock bootloader, everytime I try and fastboot recovery or roms. I get this message 9 ru security fail recovery and bootloader isn't bl-unlocke.
Im stuck ,plus when I boot the phone I get the message, your phone is not to be trusted . Please can anyone help.
Click to expand...
Click to collapse
Hi, let's see if there's any chance...
Enter the download mode and connect it to the PC then type fastboot devices to make it recognize.
If you recognize it, try typing fastboot oem get_identifier_token and see what happens...

paulpier007 said:
Hi, let's see if there's any chance...
Enter the download mode and connect it to the PC then type fastboot devices to make it recognize.
If you recognize it, try typing fastboot oem get_identifier_token and see what happens...
Click to expand...
Click to collapse
yeah fastboot devices sees it and recongnizes it biut when I do oem get identifier I get
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.012s]
finished. total time: 0.012s

mackenzie121 said:
yeah fastboot devices sees it and recongnizes it biut when I do oem get identifier I get
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.012s]
finished. total time: 0.012s
Click to expand...
Click to collapse
Did you try running a RUU

thicklizard said:
Did you try running a RUU
Click to expand...
Click to collapse
as in putting the rom on memory card and booting into download mode? and pressing up on the volume. yes I have tried many , but they all say mismatch. Unless im doing something wrong?
cant seem to find the right RUU.
this is what I have on my phone
****relocked***
***production***
htc_ocnuhl pvt s-on
LK-1.0.0.0000
radio-8998-002772tov-1802241313
openDSP-v11.6.00.347.cb8998_0711
os - 2.33.206.9

You can find RUU files here(in thread search):
https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048

mackenzie121 said:
as in putting the rom on memory card and booting into download mode? and pressing up on the volume. yes I have tried many , but they all say mismatch. Unless im doing something wrong?
cant seem to find the right RUU.
this is what I have on my phone
****relocked***
***production***
htc_ocnuhl pvt s-on
LK-1.0.0.0000
radio-8998-002772tov-1802241313
openDSP-v11.6.00.347.cb8998_0711
os - 2.33.206.9
Click to expand...
Click to collapse
i had same problem,
start unlocking your bootloader on htcdev website and take new token: (fastboot oem get_identifier_token) until you save NEW "Unlock_code.bin” in fastboot directory then : (fastboot flash unlocktoken Unlock_code.bin)
just start all from the beginning and everything should go right
Or
copy RUU to your external sd card and rename to 2PZCIMG (leave the .zip extension untouched); reboot to download mode and it will ask you (in yellow) to choose UP to start the RUU flash (previously copied to the External SD card) or DOWN to cancel flash and make a normal boot.

[HELP] Unlock Android bootloader without OEM Unlock (Phone doesn't start)

¡ I need help please !
I have a HTC Desire 10 pro (From Aliexpress, yes warranty avoid), it was working fine (more than a year) until a few days ago. One morning I took it and it was off but the notification led was not on despite charging. I tried to turn it on and enter to recovery but it was not responding. I decided to open the phone to remove the battery and verify that it was not damaged. Mysteriously the battery was in good condition, and once I removed it and plugged it back in, the phone responded again when connecting the USB and the charger.
But there is a problem, when the system is going to boot, after showing the HTC logo, the phone turns off together with the notification led and returns to the state in which I found it at first.
I removed and placed the battery again so that it would respond again, but now I entered to recovery to make a reset, but the problem is that the recovery is very outdated, so it does not have the "wipe data" options.
It should be said that i can enter into a "recovery mode" that shows:
"
hTC download mode
*** LOCKED ***
htc_a56dj_pro_dtwl PVT S-ON
LK-1.01.0000(8804eff8)
RADIO-UNKNOWN
OpenDSP-UNKNOWN
OS-1.18.400.22
Aug 1 2017,13:15:24(929341)
system info
show barcode
reboot to bootloader
reboot to download mode
reboot
power down
Security Warranty
If you flash this phone with any ROM
that was not officially released by HTC
you take the risk of
releasing your personal and financial
information to unknown sources.
SD NOT MOUNTED
OTG NOT MOUNTED
FILE NOT FOUND
"
Where the blue txt is the actual menu.
In this "recovery mode" I can't use ADB commands, i only can execute some fastboot commands (PC recognizes my device because of fastboot drivers) as "reboot", but for example:
* I can't use the "erase" command because my current recovery is not supported:
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
FAILED (remote: Partition userdata erase not supported)
finished. total time: 0.022s
"
* Nor I can directly install the TWRP recovery because it tells me:
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 1596000000 bytes
sending 'recovery' (14320 KB)...
OKAY [ 1.507s]
writing 'recovery'...
(bootloader) HOSD CL#929341
FAILED (remote: 9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKE)
finished. total time: 2.550s
"
* And I can't use the "oem unlock" command either because it just says:
"
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.062s]
finished. total time: 0.062s
"
Finally "getvar all" command shows this (i think could be useful):
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_a56dj_pro_dtwl
(bootloader) version: 1.0
(bootloader) max-download-size: 1596000000
(bootloader) serialno: LC68B1000101
(bootloader) current-slot:
(bootloader) imei: ( here shows IMEI correctly )
(bootloader) version-main: 1.18.400.22
(bootloader) boot-mode: download
(bootloader) version-baseband: READ version-baseband ERROR
(bootloader) version-bootloader: 1.01.0000(8804eff8)
(bootloader) mid: 2PYA1****
(bootloader) cid: 11111111
all:
finished. total time: 0.061s
"
Well, this is the situation, and i think the solution is:
Install the TWRP recovery to do a factory reset and if necessary install a ROM (official or not).
Buuut, to install the recovery I need to activate USB debugging (MANUALLY in the android options) and activate the OEM unlock option to unlock the bootloader, which is impossible for me since the phone "turns off" before starting.
My question is:
How to activate OEM unlock option without having to access to android settings? I mean, with commands in fastboot or in some software.
I have searched a LOT on the internet and I can't find anything about it, all the tutorials have the device fully functional, not like me that my device does not start.

Hmmm ill help you with your answer if u can get help for me with mine

Zaq1xsw222 said:
Hmmm ill help you with your answer if u can get help for me with mine
Click to expand...
Click to collapse
So help me and give me your answer, let me see if i can help you

CheckS86 said:
So help me and give me your answer, let me see if i can help you
Click to expand...
Click to collapse
Ok so you was saying you need a command right to type into linux shell. But hold on did you put a custom rom onto the phone yourself
Also, if your phone randomly stopped working by its self, our issues may be related........

Zaq1xsw222 said:
Ok so you was saying you need a command right to type into linux shell. But hold on did you put a custom rom onto the phone yourself
Also, if your phone randomly stopped working by its self, our issues may be related........
Click to expand...
Click to collapse
No, i dont flash nothing in this phone, it just stopped working by itself.
I have a Windows 10 pc and i only can use some fastboot commands, so, i already tried various commands but my outdated recovery only letme run some of them!

CheckS86 said:
No, i dont flash nothing in this phone, it just stopped working by itself.
I have a Windows 10 pc and i only can use some fastboot commands, so, i already tried various commands but my outdated recovery only letme run some of them!
Click to expand...
Click to collapse
What was the last thing you done on your phone?
The last setting you changed?
Have you tried turning the phone on with the battery out?

Zaq1xsw222 said:
What was the last thing you done on your phone?
The last setting you changed?
Have you tried turning the phone on with the battery out?
Click to expand...
Click to collapse
I was playing or using whatsapp maybe, and yes, i tried that, but never start (because of the volt needed), only the LED is on

CheckS86 said:
I was playing or using whatsapp maybe, and yes, i tried that, but never start (because of the volt needed), only the LED is on
Click to expand...
Click to collapse
Here u go.
Hard Reset HTC Desire 10 Pro, how to - HardReset.info
www.hardreset.info

Ok now its your turn

Zaq1xsw222 said:
Here u go.
Hard Reset HTC Desire 10 Pro, how to - HardReset.info
www.hardreset.info
Click to expand...
Click to collapse
The phone make exatly the same, after set the HTC logo the screen and LED turn down (like an animation when lock your screen), i dont know why, but making this led mi to the begining :/
(tell me your question btw)

CheckS86 said:
The phone make exatly the same, after set the HTC logo the screen and LED turn down (like an animation when lock your screen), i dont know why, but making this led mi to the begining :/
(tell me your question btw)
Click to expand...
Click to collapse
Have you tried to restart your phone in safety mode?

Zaq1xsw222 said:
Have you tried to restart your phone in safety mode?
Click to expand...
Click to collapse
It doesn't work, this just led me to de begining too.
The phone can't start, so maybe re-install his firmware is the best option. I already search the firmware for this phone (to try flash it with SP Flashtool), even here in XDA there is an RUU Collection for this phone, but none of them is compatible with mine. This is the firmware compatible:
2PYAIMG_A56DJ_PRO_DTWL_M60_SENSE80GP_HTC_India_SEA_1.18.400.22_Radio_0.A56DJPV1P32.7900.0216.A56T_release_508642_combined_signed_2_4.zip
but is only available to buy... here for example:
2PYAIMG_A56DJ_PRO_DTWL_M60_SENSE80GP_HTC_India_SEA_1.18.400.22_Radio_0.A56DJPV1P32.7900.0216.A56T_release_508642_combined_signed_2_4.zip | Easy Firmware
easy-firmware.com
IDK why this firmware is not in other pages .

Reinstall stock firmware so you can boot into system. Then follow instructions to unlock with unlock code