[Q] Bootloop after phone crash!! - One (M7) Q&A, Help & Troubleshooting

Hi guys!
I have quite common issue with boot looping phone, but the source of it is kind of strange to me. Four days ago I was playing True Skate game, when suddenly phone froze. I have rebooted it (holding power button down) and it had about two boot loops before it started properly. So I ignored it. I used the phone for rest of the day. I had about 10% charged battery last time when I checked. Half an hour later when I arrived at my place the battery was dead (normally 10% lasted for 3h when I was not using it), so I plugged it for charging. When I tried to turn it on after 10-20 minutes it started boot looping. Recovery is not working. I tried flashing stock recovery, CWM and TWRP. None of them worked. It is stuck in boot loop. Adb commands do not work either. “Error: device not found”.I am kind of lost because I do not have any sort of backup. I have very bad habit of not doing any (very lame). I tried relocking and doing RUU, but I could not find right one for my device (cid o2___001). The software on my phone is also out dated. I have Android Revolution HD 12.0 or 13.0(I was kind of busy and I forgot to update it regularly), sorry I can not remember properly rom’s version. Hboot 1.44.0000, htcDev unlocked, s-on. I have tried flashing boot.img. I flashed firmware from OTA.zip(1.29.206.11), because on fastboot getvar all list firmware line was blank. When that was done I realised that now I will need a ROM with this firmware version(if I am right). But I could not find any on the Internet. Fastboot erase cache command is not helping. Actually only bootloader and fastboot commands are working. I tried reinstalling drivers without success. I ran out of ideas. Please help!!

Kemil said:
Hi guys!
I have quite common issue with boot looping phone, but the source of it is kind of strange to me. Four days ago I was playing True Skate game, when suddenly phone froze. I have rebooted it (holding power button down) and it had about two boot loops before it started properly. So I ignored it. I used the phone for rest of the day. I had about 10% charged battery last time when I checked. Half an hour later when I arrived at my place the battery was dead (normally 10% lasted for 3h when I was not using it), so I plugged it for charging. When I tried to turn it on after 10-20 minutes it started boot looping. Recovery is not working. I tried flashing stock recovery, CWM and TWRP. None of them worked. It is stuck in boot loop. Adb commands do not work either. “Error: device not found”.I am kind of lost because I do not have any sort of backup. I have very bad habit of not doing any (very lame). I tried relocking and doing RUU, but I could not find right one for my device (cid o2___001). The software on my phone is also out dated. I have Android Revolution HD 12.0 or 13.0(I was kind of busy and I forgot to update it regularly), sorry I can not remember properly rom’s version. Hboot 1.44.0000, htcDev unlocked, s-on. I have tried flashing boot.img. I flashed firmware from OTA.zip(1.29.206.11), because on fastboot getvar all list firmware line was blank. When that was done I realised that now I will need a ROM with this firmware version(if I am right). But I could not find any on the Internet. Fastboot erase cache command is not helping. Actually only bootloader and fastboot commands are working. I tried reinstalling drivers without success. I ran out of ideas. Please help!!
Click to expand...
Click to collapse
Download hasoons toolkit from here http://forum.xda-developers.com/showthread.php?t=2183942
Try flashing recovery (clockwork mod gsm) from fastboot (you will get a command prompt with error: device not found but just close it down). A cmd window will show that the recovery flashes successfully
Fastboot erase cache
Try boot to bootloader?
Are you looking to get back to 100% stock o2?
Also please post a fastboot getvar all and remove your serial number and imei number

stovie_steve said:
Try flashing recovery....
Click to expand...
Click to collapse
Still in bootloop
stovie_steve said:
Fastboot erase cache
Click to expand...
Click to collapse
Seems not helping
stovie_steve said:
Try boot to bootloader?
Click to expand...
Click to collapse
I can get there, but nowhere further
stovie_steve said:
Are you looking to get back to 100% stock o2?
Click to expand...
Click to collapse
Not really. More like achieve s-off and fully enjoy it I am kind of behind with my device.
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.206.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA364W923776
(bootloader) imei: Damn guys,you know
(bootloader) meid: how to handle noobs
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4315mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.047s
C:\Users\Kamil\HTC\One_All-In-One_Kit_v3.1\data>

Kemil said:
Still in bootloop
Seems not helping
I can get there, but nowhere further
Not really. More like achieve s-off and fully enjoy it I am kind of behind with my device.
fastboot getvar all
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-main: 1.29.206.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
C:\Users\Kamil\HTC\One_All-In-One_Kit_v3.1\data>
Click to expand...
Click to collapse
download CWM from here: http://forum.xda-developers.com/showthread.php?t=2173863
go to bootloader/FASTBOOT USB, and:
fastboot flash recovery recovery-clockwork-touch-6.0.4.5-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
-> enter RECOVERY
then use "adb push <name of rom>.zip /data/media/" to get the ROM on your phone and install through recovery. (if you need a ROM that works with revone, I can send you a link)

nkk71 said:
fastboot flash recovery recovery-clockwork-touch-6.0.4.5-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
-> enter RECOVERY
Click to expand...
Click to collapse
Still can't enter recovery. I also tried flashing version 6.0.4.3, entering by factory reset. Still in bootloop:crying:

Kemil said:
Still can't enter recovery. I also tried flashing version 6.0.4.3, entering by factory reset. Still in bootloop:crying:
Click to expand...
Click to collapse
ok just saw your still on hboot 1.44, can you try this:
fastboot boot <name of recovery>.img
this will not flash it to your phone, but should immediately boot it up.

nkk71 said:
fastboot boot <name of recovery>.img
Click to expand...
Click to collapse
Still looping :crying: Tried all recovery img's which I have got.

Kemil said:
Still looping :crying: Tried all recovery img's which I have got.
Click to expand...
Click to collapse
download this:
recovery-clockwork-touch-6.0.3.2-m7--v2.img 7.2 MB
https://mega.co.nz/#!6E8RiIrQ!GF5LyhmEdg8OQJxuQVVjwSxBljxhW7xsZAHLzjVACsc
confirm MD5: 1c6afb14db3f305b0ad7d85d5af80bef
fastboot reboot-bootloader
fastboot erase cache
fastboot flash recovery recovery-clockwork-touch-6.0.3.2-m7--v2.img
fastboot erase cache
fastboot reboot-bootloader
and copy/paste your command prompt output please.

C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.062s]
finished. total time: 0.062s
C:\adb>fastboot flash recovery recovery-clockwork-touch-6.0.3.2-m7--v2.img
sending 'recovery' (7422 KB)...
OKAY [ 1.186s]
writing 'recovery'...
OKAY [ 0.608s]
finished. total time: 1.794s
C:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\adb>
Still looping:crying: MD5 checksum matched.

Kemil said:
Still looping:crying: MD5 checksum matched.
Click to expand...
Click to collapse
everything looks okay, so sorry out of ideas
and there's no RUU for your version

So am I Is it possible to do something like full wipe? So I could get rid of a problem and start fresh, something like "manual RUU". If you know what I mean?

Kemil said:
So am I Is it possible to do something like full wipe? So I could get rid of a problem and start fresh, something like "manual RUU". If you know what I mean?
Click to expand...
Click to collapse
none of this makes, any sense, but i read you flashed a firmware package, or something (add more spaces between your lines, your paragraph is too hard to read!),
can you share the link of whatever it is you flashed.
and how about a screenshot of your bootloader. thanks

This what I had at the time when I had that crash.
version-bootloader: 1.44.0000
version-baseband: 4A.14.3250.13
version-cpld: None
version-microp: None
version-main: <--- blank??
version-misc: PVT SHIP S-ON
serialno: FA364W923776
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: O2___001
battery-status: good
battery-voltage: 4256mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
So I thought there is something with firmware. Going throught threads and guides I managed to flash firmware package from
OTA_M7_UL_JB_50_O2_UK_1.29.206.11-1.27.206.1_P_release_315484_signed9p2n1xhj0mbk0nvf.
I was hoping that this will get recovery working back again and will let me reflash ROM and so on. Unfortunately, it messed it even more. I considering sending it to some repair experts, but still very curious about the issue.
Bootloader:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
Apr 10 2013,00:11:36:-1

Try something for me..
fastboot flash recovery stockrecovery144.img (download from http://goo.gl/Yzkwtl)
fastboot erase cache
fastboot reboot-bootloader
Go into bootloader and then choose Factory Reset - let that finish running. Did it boot to stock recovery?
Go into fastboot
fastboot flash recovery <custom recovery>.img
fastboot erase cache
fastboot reboot-bootloader
Can you boot into custom recovery now?

SaHiLzZ said:
Try something for me..
fastboot flash recovery stockrecovery144.img (download from http://goo.gl/Yzkwtl)
fastboot erase cache
fastboot reboot-bootloader
Go into bootloader and then choose Factory Reset - let that finish running. Did it boot to stock recovery?
Click to expand...
Click to collapse
Nope.Still looping:crying:
CMD
C:\adb>fastboot devices
FA364W923776 fastboot
C:\adb>fastboot flash recovery recovery-stock-144hboot_htc_one_m7.img
sending 'recovery' (9594 KB)...
OKAY [ 1.275s]
writing 'recovery'...
OKAY [ 0.770s]
finished. total time: 2.045s
C:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.050s]
finished. total time: 0.050s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.040s]
finished. total time: 0.040s
C:\adb>fastboot flash recovery recovery-clockwork-touch-6.0.4.5-m7ul.img
sending 'recovery' (8746 KB)...
OKAY [ 1.160s]
writing 'recovery'...
OKAY [ 0.665s]
finished. total time: 1.830s
C:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.045s]
finished. total time: 0.045s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.040s]
finished. total time: 0.040s
C:\adb>

Just confirming if you did this after flashing stock recovery ? "Go into bootloader and then choose Factory Reset - let that finish running. Did it boot to stock recovery?"

Yes, I did that and it rebooted after 30-35 seconds into bootloop.

Just to confirm again, that you did stock recovery and did a factory reset, it bootlooped, then you install CWM and when you went inside CWM, it bootlooped by itself? Without you doing anything?

Kemil said:
Yes, I did that and it rebooted after 30-35 seconds into bootloop.
Click to expand...
Click to collapse
doesnt sound very good
can you try the following:
fastboot erase cache
fastboot boot <name of recovery>.img <-yes boot, not flash
and see if it holds at least more than a minute. advise back....

nkk71 said:
and see if it holds at least more than a minute. advise back....
Click to expand...
Click to collapse
It reboots after 30-35 seconds:crying:
CMD
C:\adb>fastboot devices
FA364W923776 fastboot
C:\adb>fastboot boot recovery-clockwork-touch-6.0.4.5-m7ul.img
downloading 'boot.img'...
OKAY [ 1.180s]
booting...
OKAY [ 0.000s]
finished. total time: 1.180s
C:\adb>

Related

[Q] Need Help for No Os !! Only get into hboot & fastboot

Hi all ! my HTC one M7 is stuck on HTC logo and bootloop again ! I've unlocked my bootloader and can successfully flash custom recovery (TWRP/CWM/Philz) all the versions of recovery can successfully flash. However when I go into recovery it show only entering recovery and bootloop again & again. I've flash RUU but it say failed seem to be lower version. I can't find my current OS version and can't flash it. My device is S-on therefore I can't flash the other region or other lower hboot version. Let me know How can I fix this problem. I've searched in google and in XDA a whole day but I can't find the right solution. Please help me if you face that error.
My phone detail is -
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.707.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3******728
(bootloader) imei: 35585*******7
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 4297mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.046s
I hope someone can be explained and can help me
Best Regards;
Sorry for my English !
saiarkar said:
Hi all ! my HTC one M7 is stuck on HTC logo and bootloop again ! I've unlocked my bootloader and can successfully flash custom recovery (TWRP/CWM/Philz) all the versions of recovery can successfully flash. However when I go into recovery it show only entering recovery and bootloop again & again. I've flash RUU but it say failed seem to be lower version. I can't find my current OS version and can't flash it. My device is S-on therefore I can't flash the other region or other lower hboot version. Let me know How can I fix this problem. I've searched in google and in XDA a whole day but I can't find the right solution. Please help me if you face that error.
My phone detail is -
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-main: 2.24.707.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
Click to expand...
Click to collapse
Well there is no ruu for your model (except lower version, that wouldn't work with S-On), so you need to figure out why you can't enter recovery.
are you doing a "fastboot erase cache" and using a recovery for your phone model:
get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
2.7.0.4b: http://forum.xda-developers.com/showthread.php?t=2708134
or CWM: http://forum.xda-developers.com/showthread.php?t=2173863
in bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
-> enter recovery
nkk71 said:
Well there is no ruu for your model (except lower version, that wouldn't work with S-On), so you need to figure out why you can't enter recovery.
are you doing a "fastboot erase cache" and using a recovery for your phone model:
get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
2.7.0.4b: http://forum.xda-developers.com/showthread.php?t=2708134
or CWM: http://forum.xda-developers.com/showthread.php?t=2173863
in bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
-> enter recovery
Click to expand...
Click to collapse
Hi ! I've tried all of recovery from xda and google but there is no working recovery. I'm unluck :'( Before I posted a thread to XDA I've searched all HTC One forum and thread but there is no right solutions for me Can you give me the other ways
saiarkar said:
Hi ! I've tried all of recovery from xda and google but there is no working recovery. I'm unluck :'( Before I posted a thread to XDA I've searched all HTC One forum and thread but there is no right solutions for me Can you give me the other ways
Click to expand...
Click to collapse
1- how did you end up in this situation?
2- are checking MD5 on your downloads
3- can you copy/paste the command prompt when you flash custom recovery
4- can you post a screenshot of your bootloader
nkk71 said:
1- how did you end up in this situation?
2- are checking MD5 on your downloads
3- can you copy/paste the command prompt when you flash custom recovery
4- can you post a screenshot of your bootloader
Click to expand...
Click to collapse
C:\Users\User>fastboot flash recovery "D:\HTC One (802e) Recovery to root\recovery-clockwork-6.0.4.6-m7ul.img"
sending 'recovery' (9136 KB)...
OKAY [ 1.158s]
writing 'recovery'...
OKAY [ 0.845s]
finished. total time: 2.013s
C:\Users\User>fastboot erase cache
erasing 'cache'...
OKAY [ 0.468s]
finished. total time: 0.471s
C:\Users\User>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.036s]
finished. total time: 0.037s
Here is my command prompt !! After all I have reboot to recovery and it say "Entering Recovery" then stuck on HTC Log again & again. I can only access on bootloader and fastboot mode
saiarkar said:
C:\Users\User>fastboot flash recovery "D:\HTC One (802e) Recovery to root\recovery-clockwork-6.0.4.6-m7ul.img"
sending 'recovery' (9136 KB)...
OKAY [ 1.158s]
writing 'recovery'...
OKAY [ 0.845s]
finished. total time: 2.013s
C:\Users\User>fastboot erase cache
erasing 'cache'...
OKAY [ 0.468s]
finished. total time: 0.471s
C:\Users\User>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.036s]
finished. total time: 0.037s
Here is my command prompt !! After all I have reboot to recovery and it say "Entering Recovery" then stuck on HTC Log again & again. I can only access on bootloader and fastboot mode
Click to expand...
Click to collapse
and my question 1, 2 and 4?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
here is md5 i have flash and then reboot bootloader then enter the recovery but it is not working
Sent from my iPhone using Tapatalk
saiarkar said:
here is md5 i have flash and then reboot bootloader then enter the recovery but it is not working
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
a simple yes would have been enough, i do believe you , now still to answer is:
1- how did you end up in this situation?
and
4- can you post a screenshot of your bootloader
well this is my bootloader and i'm not understand your question no. (1). Can you ask me clearly! My english not as well.
Sent from my iPhone using Tapatalk
saiarkar said:
i'm not understand your question no. (1). Can you ask me clearly! My english not as well.
Click to expand...
Click to collapse
What I mean is why did this happen?
For example:
did you install something new?
did you flash anything new?
Basically: what changed from the time the phone was working to the time now?
nkk71 said:
What I mean is why did this happen?
For example:
did you install something new?
did you flash anything new?
Basically: what changed from the time the phone was working to the time now?
Click to expand...
Click to collapse
Nothing wrong for my device ! I use my camera to take photo and then this bootloop has been happened. So I've searched in google and test all recovery images but not working as well. Therefore I ask as a thread I've face too many error others devices and I have a little knowledge about soft brick devices. But I can't figure out what is happen this device
saiarkar said:
Nothing wrong for my device ! I use my camera to take photo and then this bootloop has been happened. So I've searched in google and test all recovery images but not working as well. Therefore I ask as a thread I've face too many error others devices and I have a little knowledge about soft brick devices. But I can't figure out what is happen this device
Click to expand...
Click to collapse
Well that doesn't sound good.... this could be a hardware problem
and CWM doesnt work either? sometimes twrp is sensitive when partitions are corrupt, but CWM recovery should work.
May be this is reason. When i have erase recovery partition with 'fastboot erase recovery' it show remote failed. This is may be corrupted recovery partition. Can you find me the right RUU for this device ??
Sent from my iPhone using Tapatalk
saiarkar said:
May be this is reason. When i have erase recovery partition with 'fastboot erase recovery' it show remote failed. This is may be corrupted recovery partition. Can you find me the right RUU for this device ??
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Unfortunately there is no RUU for your model, and since you are S-On no other one will work (and you cannot get S-OFF without a ROM)
try CWM recovery: http://forum.xda-developers.com/showthread.php?t=2173863
fastboot flash <name of cwm>.img
fastboot erase cache
fastboot reboot-bootloader
-> enter RECOVERY
If that doesn't work, try this recovery: http://www.androidfilehost.com/?fid=23329332407590873
same commands as above
Let me know if either one gets to recovery
PS: oh, and even try a stock recovery from here: http://forum.xda-developers.com/showthread.php?t=2463387
if there is no 2.24.707.1 stock recovery, get any 2.24.xxx.x version and try
nkk71 said:
Unfortunately there is no RUU for your model, and since you are S-On no other one will work (and you cannot get S-OFF without a ROM)
try CWM recovery: http://forum.xda-developers.com/showthread.php?t=2173863
fastboot flash <name of cwm>.img
fastboot erase cache
fastboot reboot-bootloader
-> enter RECOVERY
If that doesn't work, try this recovery: http://www.androidfilehost.com/?fid=23329332407590873
same commands as above
Let me know if either one gets to recovery
PS: oh, and even try a stock recovery from here: http://forum.xda-developers.com/showthread.php?t=2463387
if there is no 2.24.707.1 stock recovery, get any 2.24.xxx.x version and try
Click to expand...
Click to collapse
Unfortunately there is no one work for me even stock recovery can't boot up. What can I do in this situation ?
saiarkar said:
Unfortunately there is no one work for me even stock recovery can't boot up. What can I do in this situation ?
Click to expand...
Click to collapse
sounds like a hardware problem, don't have any more ideas at the moment sorry
unless someone has any ideas, it looks like it should go to repair
nkk71 said:
sounds like a hardware problem, don't have any more ideas at the moment sorry
unless someone has any ideas, it looks like it should go to repair
Click to expand...
Click to collapse
Thanks @nkk71 for your time I be waiting here somebody can help me

[Q] HTC One can't enter CWP/TWRP on boot loop please help

Hi Guys
i think i really messed up my HTC one first of all here's the screen details on the boot loader
and I'm a complete noobie on android and this is phone is my frist android device
****UNLOCKED****
M7_UL PVT SHIP S-OFF RH
CID-HTC__044
HBOOT-1.57.0000
RADIO-4T.27.3218.14
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Apr 25 2014
PC: Windows 7 Ultimate
The story is I tried to root my device using this tutorial in youtube from zedomax
and it was a success without trouble,
So I tried to install a custom ROM ViperOne_6.2.0.zip
and its where everything got messed up when the installation returned an error during installation
I tried reinstalling and i think i wiped all the data on the storage including the backup using the TWRP wipe button including OS files
after several attempts i was able to re enter TWRP and/or CWP trying to install via Sideload command but failed
i cant load zip files via my PC too because my pc cant read/write the storage of my phone. (I installed USB drivers and phone is detectable on device manager)
now the bootloader have this error Active cmdline overflow! (1094 Bytes)
Since I'm a real newbie in android may I kindly ask a step-by-step instruction on how can i recover if possible from this trouble.
I would really appreciate everyone's help from this forum.
here's a guide to fix that active cmdline overflow, you messed up one of your partitions and your phone wont work until you fix that issue, you need to follow that guide to the letter, do not skip any parts, read it all first and understand it, if you get any of the commands wrong you could end up with a complete brick so copy and paste them.
http://forum.xda-developers.com/showthread.php?t=2739126
Thank you for the quick reply,
I tried to install "fastboot flash recovery twrp-recovery-2.7-m7-nobcb.img" on fastboot. It installed correctly
when I erased cache then rebooted the fast booth, the "Active cmdline overflow! (**** Bytes)" error was gone
but when i enter recovery, it reboots again to fastboot and the error reappears.
and the cycle repeats again.
I can't get past this
one more thing...I noticed that you used a different adb C:\ADB3> is there a version 3 or is it just a folder name?
when I try to detect device in fastboot:
D:\HTCOne recover\HTCOneRoot>fastboot devices
FA32GW9**** fastboot
but when i try to use the same command on adb:
D:\HTCOne recover\HTCOneRoot>adb devices
List of devices attached
nothing on the list. And ADB commands don't work because it can't recognize the device.
I really need your help. Thanks in Advance
I would like to add that I can't access the phone storage through my PC
one more thing...
how would I know if i got these?
from the guide
"Well you need adb commands, root and busybox... which are only available in a custom recovery or a rooted ROM (with USB debugging enabled)"
1. adb commands
2. root and
3. busybox
4. custom recovery or a rooted ROM (with USB debugging enabled)
which are only available in a custom recovery or a rooted ROM (with USB debugging enabled)"
WilmanB said:
Thank you for the quick reply,
I tried to install "fastboot flash recovery twrp-recovery-2.7-m7-nobcb.img" on fastboot. It installed correctly
when I erased cache then rebooted the fast booth, the "Active cmdline overflow! (**** Bytes)" error was gone
but when i enter recovery, it reboots again to fastboot and the error reappears.
and the cycle repeats again.
I can't get past this
one more thing...I noticed that you used a different adb C:\ADB3> is there a version 3 or is it just a folder name?
Click to expand...
Click to collapse
have you restored mmcblk0p19 like said in the guide?
but when i try to use the same command on adb:
D:\HTCOne recover\HTCOneRoot>adb devices
List of devices attached
nothing on the list.
and ADB commands don't work because it can't recognize the device.
I really need your help. Thanks in Advance
I would like to add that I can't access the phone storage through my PC
Click to expand...
Click to collapse
adb only works from custom recovery or from a booted rom with usb debug on. adb will not works from bootloader and you will not see phone storage from bootloader.
alray said:
have you restored mmcblk0p19 like said in the guide?
Click to expand...
Click to collapse
but adb does not recognize my phone so i cant restore mmcblk0p1 like it says on the instruction
adb wont respond to any adb commands
but fastboot is responsive
"adb only works from custom recovery or from a booted rom with usb debug on."
how do i do this? How will I know if I'm running in a booted ROM with USB debug On?
I install "fastboot flash recovery twrp-recovery-2.7-m7-nobcb.img" on fastboot. It installed correctly but it wont enter recovery mode
First of all you will know if you are running a booted Rom if your phone boots up lol, in your case, yours doesn't, so ignore this and usb debugging.
Fastboot commands only work in bootloader.
Adb commands for you will only work inside recovery.
You must get into recovery to use adb to fix your phone, the reason you apprear to not be able to get in is because of your hboot version, you need to downgrade it, however I leave this completely in your hands and won't be held responsible if you brick your phone, simply, if you flash even the slightest wrong hboot, you'll have a brick, read the rest of that thread after the instructions, your same issue is in that thread.
WilmanB said:
but adb does not recognize my phone so i cant restore mmcblk0p1 like it says on the instruction
adb wont respond to any adb commands
but fastboot is responsive
Click to expand...
Click to collapse
ADB commands = Usable from custom recovery mode or from a normally booted phone (not your case)
FASTBOOT commands = Usable only from bootloader, where you currently are. You can't use adb here
"adb only works from custom recovery or from a booted rom with usb debug on."
how do i do this? How will I know if I'm running in a booted ROM with USB debug On?
Click to expand...
Click to collapse
flash the nobcb verison of twrp, boot in recovery and then you'll be able to use ADB commands.
I install "fastboot flash recovery twrp-recovery-2.7-m7-nobcb.img" on fastboot. It installed correctly but it wont enter recovery mode
Click to expand...
Click to collapse
Code:
fastboot flash recovery twrp-recovery-2.7-m7-nobcb.img
fastboot erase cache
fastboot reboot-bootloader
then try to boot in recovery mode again.
if you are still not able to boot the nobcb recovery, better to ask in the thread Seanie280672 linked you
Wow, thank you all very much. I am now able to enter recovery mode using HBOOT -1.44.0000 through CWT recovery
no more cmdline overflow.
and I'm done restoring mmcblk0p19
now i just need to find the correct RUU to flash I need your help again guys? I'm not really sure what RUU to flash or what to do next from here
WilmanB said:
Wow, thank you all very much. I am now able to enter recovery mode using HBOOT -1.44.0000 through CWT recovery
no more cmdline overflow.
and I'm done restoring mmcblk0p19
now i just need to find the correct RUU to flash I need your help again guys? I'm not really sure what RUU to flash or what to do next from here
Click to expand...
Click to collapse
post the output of "fastboot getvar all" excluding imei and serialno and we'll be able to tell you what ruu you can use.
alray said:
post the output of "fastboot getvar all" excluding imei and serialno and we'll be able to tell you what ruu you can use.
Click to expand...
Click to collapse
@elray
Thanks for replying these are what i got from the getvar command
version: 0.5
version-bootloader: 1.54.0000
version-baseband: 4A.17.3250.14
version-cpld: None
version-microp: None
version-main: 2.24.707.1
version-misc: PVT SHIP S-OFF
serialno: FA32GW9*****
imei: 3558590500*****
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0714000
cidnum: HTC__044
battery-status: good
battery-voltage: 4318mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-d16dc66985
hbootpreupdate: 11
gencheckpt: 0
I wish you can locate a proper RUU for my device.
I would also like to ask if it is possible to install custom ROM on my phone.
I tried to install the ViperOne 6.2.0 and Android Revolution HD 71.1 but it's both unsuccessful
now I'm stuck on Android 4.2.2 in HTC Sense 5 because i can't install new updates to KitKat and Sense 6
WilmanB said:
@elray
Thanks for replying these are what i got from the getvar command
version: 0.5
version-bootloader: 1.54.0000
version-baseband: 4A.17.3250.14
version-cpld: None
version-microp: None
version-main: 2.24.707.1
version-misc: PVT SHIP S-OFF
serialno: FA32GW9*****
imei: 3558590500*****
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0714000
cidnum: HTC__044
battery-status: good
battery-voltage: 4318mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-d16dc66985
hbootpreupdate: 11
gencheckpt: 0
I wish you can locate a proper RUU for my device.
I would also like to ask if it is possible to install custom ROM on my phone.
I tried to install the ViperOne 6.2.0 and Android Revolution HD 71.1 but it's both unsuccessful
now I'm stuck on Android 4.2.2 in HTC Sense 5 because i can't install new updates to KitKat and Sense 6
Click to expand...
Click to collapse
http://www.htc1guru.com/dld/ruu-zip-m7_u_asia_wwe_custom_guruu_3-63-707-4-zip/
or any other ruu if you change your mid/cid
alray said:
http://www.htc1guru.com/dld/ruu-zip-m7_u_asia_wwe_custom_guruu_3-63-707-4-zip/
or any other ruu if you change your mid/cid
Click to expand...
Click to collapse
Sorry @alray but the file in your link returned an error while flashing
3x to flash without rebooting, returned this error:
D:\HTCOne recover\HTCOneRoot>fastboot flash zip RUU.zip
sending 'zip' (1206124 KB)...
OKAY [ 46.103s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 46.549s
D:\HTCOne recover\HTCOneRoot>fastboot flash zip RUU.zip
sending 'zip' (1206124 KB)...
OKAY [ 46.183s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 46.610s
D:\HTCOne recover\HTCOneRoot>fastboot flash zip RUU.zip
sending 'zip' (1206124 KB)...
OKAY [ 46.112s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 46.540s
D:\HTCOne recover\HTCOneRoot>fastboot reboot
rebooting...
finished. total time: 0.038s
I think the RUU file is incompatible with my device that's why it wont proceed.
this is the filename:
RUU Zip M7_U_Asia_WWE_Custom_GuRUU_3.63.707.4.zip
Android.txt
modelid: PN0711000
modelid: PN0714000
cidnum: HTC__044
cidnum: HTC__038
mainver: 3.63.707.4
btype:1
aareport:1
DelCache:1
hbootpreupdate:3
WilmanB said:
Sorry @alray but the file in your link returned an error while flashing
3x to flash without rebooting, returned this error:
D:\HTCOne recover\HTCOneRoot>fastboot flash zip RUU.zip
sending 'zip' (1206124 KB)...
OKAY [ 46.103s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 46.549s
D:\HTCOne recover\HTCOneRoot>fastboot flash zip RUU.zip
sending 'zip' (1206124 KB)...
OKAY [ 46.183s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 46.610s
D:\HTCOne recover\HTCOneRoot>fastboot flash zip RUU.zip
sending 'zip' (1206124 KB)...
OKAY [ 46.112s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 46.540s
D:\HTCOne recover\HTCOneRoot>fastboot reboot
rebooting...
finished. total time: 0.038s
I think the RUU file is incompatible with my device that's why it wont proceed.
this is the filename:
RUU Zip M7_U_Asia_WWE_Custom_GuRUU_3.63.707.4.zip
Android.txt
modelid: PN0711000
modelid: PN0714000
cidnum: HTC__044
cidnum: HTC__038
mainver: 3.63.707.4
btype:1
aareport:1
DelCache:1
hbootpreupdate:3
Click to expand...
Click to collapse
was your phone in ruu mode?
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip
fastboot reboot
alray said:
was your phone in ruu mode?
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip
fastboot reboot
Click to expand...
Click to collapse
yes sir it was in ruu mode. the one with green HTC logo and black background.
WilmanB said:
yes sir it was in ruu mode. the one with green HTC logo and black background.
Click to expand...
Click to collapse
try this one: http://www.htc1guru.com/dld/ruu_m7_...0-13_10-33-1150-01_release_311678_signed-exe/
otherwise, change your mid and cid and try to flash another version ruu.

[Q] M7 bricked! stuck in bootloader/fastboot, cant flash anything or access recovery

Hi there.
My phone is a m7_ul, with s-on, Hboot unlocked.
Code:
***TAMPERED***
***UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4a.26.3263.05
OpenDSP-v32.120.274.0909
OS-4.19.161.11
eMMC-boot 2048MB
Mar 5 2014, 15:58:33.0
My phone has been bricked for a while. Originally water damaged, it at first wouldn't take any custom roms or wouldn't set back to stock, but eventually I managed to get it there and it was working fine, except that at random the phone died or rebooted. Eventually I tried putting a custom ROM on it again, and that didn't quite work, because of the phone randomly rebooting. And I guess here is where I went wrong (I can literally imagine you guys flinch when I say this): I hit 'factory recovery' in bootloader.
So now I can't do anything, besides going from hboot/bootloader onto 'fastboot' (and 'show barcode'). Going from hboot/bootloader onto 'recovery' brings me to fastboot. Even 'power down' or 'reboot bootloader' from fastboot brings me back to fastboot. Sometimes at random times the phone becomes unresponsive even in fastboot so that I have to do a hard reset with power and vol-down keys. The phone charges fine, only switches off when the battery is flat. As soon as it has enough power it goes into fastboot mode.
Plugged into my win8 machine it shows in device manager as 'my htc' (but not on the 'this pc'-view!).
In fastboot, I get the serial number when I enter 'fastboot devices', which is great. With 'fastboot getvar all' I get the following:
Code:
c:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.26.3263.05
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.161.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ************
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3742mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-09ff2ded
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.053s
HOWEVER Trying to flash a custom recovery (like the latest TWRP or CWM), I get following error:
Code:
c:\Android>fastboot flash recovery twrp/recovery.img
target reported max download size of 1514139648 bytes
sending 'recovery' (9948 KB)...
OKAY [ 1.332s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 2.505s
I tried this with numerous recoveries, but no luck. I managed to fastboot erase cache no problem.
but yeah. since i cant flash any recovery, i cant flash any new custom or stock rom. please please help.
herchenm said:
Hi there.
My phone is a m7_ul, with s-on, Hboot unlocked.
Code:
***TAMPERED***
***UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4a.26.3263.05
OpenDSP-v32.120.274.0909
OS-4.19.161.11
eMMC-boot 2048MB
HOWEVER Trying to flash a custom recovery (like the latest TWRP or CWM), I get following error:
[CODE]c:\Android>fastboot flash recovery [COLOR="Blue"]twrp/recovery.img[/COLOR]
target reported max download size of 1514139648 bytes
sending 'recovery' (9948 KB)...
OKAY [ 1.332s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 2.505s
I tried this with numerous recoveries, but no luck. I managed to fastboot erase cache no problem.
but yeah. since i cant flash any recovery, i cant flash any new custom or stock rom. please please help.
Click to expand...
Click to collapse
Remove the imei and serialno from your post.
Since you are on Win 8, you might try Win 7 or Ubuntu (nkk71 has instructions Q5).
I don't know of a way to recover what's there, maybe someone else will have a suggestion. You can always flash in, oemRUU mode, a signed RUU and later flash recovery. But, you will lose all of your data, pic, music, etc.
There are certainly other ways to recover. Anyone?
---------- Post added at 09:15 PM ---------- Previous post was at 09:09 PM ----------
I don't know of a way to recover what's there, maybe someone else will have a suggestion. You can always flash in, oemRUU mode, a signed RUU and later flash recovery. But, you will lose all of your data, pic, music, etc. This rom (http://forum.xda-developers.com/showthread.php?t=2676986) will leave you with a 1.54 hboot, so you won't downgrade to 1.44 and get stuck as the previous poster suggests.
There are certainly other ways to recover. Anyone?
majmoz said:
Remove the imei and serialno from your post.
Click to expand...
Click to collapse
done.
majmoz said:
Since you are on Win 8, you might try Win 7 or Ubuntu (nkk71 has instructions Q5).
Click to expand...
Click to collapse
not sure how that would help me? the phone is being detected and displays as 'my htc' in the windows device manager as well as with the "fastboot devices" command.
this is not the problem.
the problem is that i can't flash anything because of the returned error (image update error), which needs to be fixed but i dont know how
davidrol said:
I don't know of a way to recover what's there, maybe someone else will have a suggestion. You can always flash in, oemRUU mode, a signed RUU and later flash recovery. But, you will lose all of your data, pic, music, etc.
There are certainly other ways to recover. Anyone?
---------- Post added at 09:15 PM ---------- Previous post was at 09:09 PM ----------
I don't know of a way to recover what's there, maybe someone else will have a suggestion. You can always flash in, oemRUU mode, a signed RUU and later flash recovery. But, you will lose all of your data, pic, music, etc. This rom (http://forum.xda-developers.com/showthread.php?t=2676986) will leave you with a 1.54 hboot, so you won't downgrade to 1.44 and get stuck as the previous poster suggests.
There are certainly other ways to recover. Anyone?
Click to expand...
Click to collapse
I don't mind losing all my data. I think the phone is pretty bricked as it is, so if I could get it to work with your help, that'd be a win. Screw keeping the data haha.
I will try flashing the ROM you linked to and get back to you.
davidrol said:
you can always flash in, oemRUU mode, a signed RUU and later flash recovery
Click to expand...
Click to collapse
What do you mean with that? How do I do that? I can't get into recovery (as I cant flash that via the fastboot command) so I cant adb push/sideload
Please help
davidrol said:
This rom (http://forum.xda-developers.com/showthread.php?t=2676986) will leave you with a 1.54 hboot, so you won't downgrade to 1.44 and get stuck as the previous poster suggests.
Click to expand...
Click to collapse
can i still use that though its AT&T and my cidnum is VODAP102?
also, how do I install that ROM if I have no recovery? Im confused.
herchenm said:
can i still use that though its AT&T and my cidnum is VODAP102?
also, how do I install that ROM if I have no recovery? Im confused.
Click to expand...
Click to collapse
No you can't flash that one. You will have to find a signed RUU that matches your VODAP102 cidnum and your model number. Here's the link describing how to flash an RU in fastboot: http://forum.xda-developers.com/showthread.php?t=2251800.
davidrol said:
No you can't flash that one. You will have to find a signed RUU that matches your VODAP102 cidnum and your model number. Here's the link describing how to flash an RU in fastboot: http://forum.xda-developers.com/showthread.php?t=2251800.
Click to expand...
Click to collapse
Am I right in assuming that there isn't any RUU for my cid etc. needs? Haven't been able to found one yet maybe you can help?
Thanks for the link as well! Guess I'm gonna have to find the right RUU first
There is a way to change your cid in fastboot. I haven't the needed to so you'll need to do the research. If changing your cid isn't a problem, heres something: http://www.htc1guru.com/dld/ruu_m7_u_jb_50_htc_europe_1-29-401-2_r_radio_4a-14-3250-13_10-33-. You wont be able to flash an incorrect ruu with s-on (security on).
Sent from my SAMSUNG-SGH-I957 using xda
herchenm said:
can i still use that though its AT&T and my cidnum is VODAP102?
also, how do I install that ROM if I have no recovery? Im confused.
Click to expand...
Click to collapse
your using the wrong command to flash recovery
do it like this
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
you get the file here >> http://techerrata.com/browse/twrp2/m7
Get 2.6.3.3 no other
Your s-on you can't change CID and MID to match an AT&T RUU
your best to flash a Guru reset or a stock .401 Rom
Here's the link to change your cid to supercid: http://forum.xda-developers.com/showthread.php?t=2317536
---------- Post added at 07:33 PM ---------- Previous post was at 07:10 PM ----------
Also, put the twrp file in the same-folder-as-fastboot.
clsA said:
your using the wrong command to flash recovery
do it like this
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
you get the file here >> http://techerrata.com/browse/twrp2/m7
Get 2.6.3.3 no other
Your s-on you can't change CID and MID to match an AT&T RUU
your best to flash a Guru reset or a stock .401 Rom
Click to expand...
Click to collapse
I've been using exactly that command, and like I said, I keep getting the same error (see first post). Nonetheless I tried the recovery you linked to as well, and got the same error:
Code:
c:\Android>fastboot flash recovery or_twrp/openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.336s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 2.615s
I really cannot flash any recoveries.
davidrol said:
Here's the link to change your cid to supercid: http://forum.xda-developers.com/showthread.php?t=2317536
---------- Post added at 07:33 PM ---------- Previous post was at 07:10 PM ----------
Also, put the twrp file in the same-folder-as-fastboot.
Click to expand...
Click to collapse
following the instructions on the guide you linked to I get following error:
Code:
c:\Android>fastboot oem readcid
...
(bootloader) cid: VODAP102
OKAY [ 0.002s]
finished. total time: 0.003s
c:\Android>fastboot oem writecid 11111111
...
(bootloader) [JAVACARD_ERR] SD/USBDISK Init error
OKAY [ 0.001s]
finished. total time: 0.003s
So I cant seem to change the CID :S
I tried changing s-on to s-off so I can change the CID. I used the moonshine s-off (http://forum.xda-developers.com/showthread.php?t=2291087 and downloaded the moonshine_m7_1.29.401.13.zip (which was the only .401 rom)
deinstalled HTC Sync Manager.
command 'fastboot devices' returned the serial number and that the phone is in fastboot-mode.
extracted the zip-file onto my computer into a separate folder, ran the distiller.exe. I confirm everything, it starts running, and then I get following error:
Code:
Ok?
(Yes/No)
Yes
!! Do NOT for any reason touch, unplug, lick or maim your device !!
Checking for updates......
Please wait....
..........
ERROR: run distiller again and READ
Press ENTER to exit
maybe I downloaded the wrong zip-file from Moonshine? Maybe i need to try this one, cause it's vodafone and obvs my CID is Voda? moonshine_m7_1.29.161.11.zip
What do you think?
Try rumrunner
SaHiLzZ said:
Try rumrunner
Click to expand...
Click to collapse
tried that. similar result:
Code:
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
ERROR: run rumrunner again and READ (no adb connection to device. Debugging on?
Drivers?)
Press ENTER to exit
herchenm said:
I've been using exactly that command, and like I said, I keep getting the same error (see first post). Nonetheless I tried the recovery you linked to as well, and got the same error:
Code:
c:\Android>fastboot flash recovery or_twrp/openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.336s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 2.615s
Click to expand...
Click to collapse
i hate to be the bearer of bad news, but pretty sure your phone is a goner
can you try the following command:
fastboot oem rebootRUU
do you get to RUU mode?
you're probably also unable to relock and unlock you device, correct?
nkk71 said:
i hate to be the bearer of bad news, but pretty sure your phone is a goner
can you try the following command:
fastboot oem rebootRUU
do you get to RUU mode?
you're probably also unable to relock and unlock you device, correct?
Click to expand...
Click to collapse
fastboot oem rebootRUU gives me the following (but the bootloader isnt locked, which I think I need to do first, no?)
Code:
c:\Android>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
(bootloader) SD: write failed in CMD25.
OKAY [ 1.065s]
finished. total time: 1.067s
herchenm said:
fastboot oem rebootRUU gives me the following (but the bootloader isnt locked, which I think I need to do first, no?)
Code:
c:\Android>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
(bootloader) SD: write failed in CMD25.
OKAY [ 1.065s]
finished. total time: 1.067s
Click to expand...
Click to collapse
nope sorry mate, it's a goner, your phone is fried
time for a new phone, sorry
nkk71 said:
nope sorry mate, it's a goner, your phone is fried
time for a new phone, sorry
Click to expand...
Click to collapse
i locked the bootloader now and got this
Code:
c:\Android>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 1.157s
and on the screen of the phone it says
Code:
*** tampered ***
*** relocked ***
*** security warning ***
{followed by the rest}
what does that 'security warning' and the error in the relocking of bootloader mean?
herchenm said:
i locked the bootloader now and got this
Code:
c:\Android>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 1.157s
and on the screen of the phone it says
Code:
*** tampered ***
*** relocked ***
*** security warning ***
{followed by the rest}
what does that 'security warning' and the error in the relocking of bootloader mean?
Click to expand...
Click to collapse
security warning is because you are not on [your] stock version
but it doesn't matter, the phone is fried
i'm really sorry
PS: i'm actually surprised the lock command worked

[Q] Tampered, Unlcoked, S-On Hboot 1.57 - No USB Debug Semi Bricked

Over the weekend my phone died and somehow it got stuck in boot loop with tempered flag, I reflashed the recovery from TWRP to Clockwork and factory reset, it returned back to stock..sort of.
Everything had been slow ever since the latest OTA, hence the unlock, root and recovery change but I didn't flash any rom. Until today. I tried flashing "Android Revolution HD 81.0"
Now it won't boot through, at most I get now is bootloader/fastboot/recovery or stuck on green HTC screen.
I tired using RUU via exe (can't find zip because htc1guru.com appears to be down) and it gets stuck at checking header 5%
Issues: S-ON/Hboot 1.57/No USB Debug=no adb=no firewater
I've followed every how-to there is, but all of them require USB debug in some way, I can't get into the phone to get it down, therefore adb doesn't work. at most I have are fastboot commands.
Im at my wits. I just want to get it back to stock, to do that I would need S-off or even just have a RUU that works. This is the RUU:
RUU_M7_UL_K44_SENSE55_MR_BrightstarUS_WWE_4.19.1540.9_Radio_4A.23.3263.28_10.38r.1157.04L_release_353887_signed_3.exe
I've relocked it prior to update RUU but it didn't make a difference except preventing me to enter recovery for other tasks.
ANY help is appreciated
Here are my fastboot getvar all info:
C:\AndroidSDK\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.07.1540.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXX
(bootloader) imei:XXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4266mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.108s
Click to expand...
Click to collapse
PlinXoom said:
Over the weekend my phone died and somehow it got stuck in boot loop with tempered flag, I reflashed the recovery from TWRP to Clockwork and factory reset, it returned back to stock..sort of.
Everything had been slow ever since the latest OTA, hence the unlock, root and recovery change but I didn't flash any rom. Until today. I tried flashing "Android Revolution HD 81.0"
Now it won't boot through, at most I get now is bootloader/fastboot/recovery or stuck on green HTC screen.
I tired using RUU via exe (can't find zip because htc1guru.com appears to be down) and it gets stuck at checking header 5%
Issues: S-ON/Hboot 1.57/No USB Debug=no adb=no firewater
I've followed every how-to there is, but all of them require USB debug in some way, I can't get into the phone to get it down, therefore adb doesn't work. at most I have are fastboot commands.
Im at my wits. I just want to get it back to stock, to do that I would need S-off or even just have a RUU that works. This is the RUU:
RUU_M7_UL_K44_SENSE55_MR_BrightstarUS_WWE_4.19.1540.9_Radio_4A.23.3263.28_10.38r.1157.04L_release_353887_signed_3.exe
I've relocked it prior to update RUU but it didn't make a difference except preventing me to enter recovery for other tasks.
ANY help is appreciated
Here are my fastboot getvar all info:
Click to expand...
Click to collapse
You must flash ARHD using TWRP 2.6.3.3
you can not use older RUU version to restore your phone with S-ON
You can restore your phone back to stock using a nandroid backup of your version and then flash the stock recovery back.
USB debugging is only needed to use ADB when the phone is booted in the OS. Or you can also use ADB from custom recovery even if USB debug is NOT turned on.
So depending what your goal is you should try to either flash TWRP 2.6.3.3 and reflash ARHD or restore your phone using a nandroid backup if the latest dev edition software.
PlinXoom said:
Over the weekend my phone died and somehow it got stuck in boot loop with tempered flag, I reflashed the recovery from TWRP to Clockwork and factory reset, it returned back to stock..sort of.
Everything had been slow ever since the latest OTA, hence the unlock, root and recovery change but I didn't flash any rom. Until today. I tried flashing "Android Revolution HD 81.0"
Now it won't boot through, at most I get now is bootloader/fastboot/recovery or stuck on green HTC screen.
I tired using RUU via exe (can't find zip because htc1guru.com appears to be down) and it gets stuck at checking header 5%
Issues: S-ON/Hboot 1.57/No USB Debug=no adb=no firewater
Click to expand...
Click to collapse
alray is correct, you can not flash that RUU because you are S-ON and it is a lower version than your present phone. There is no RUU for your version at the moment only an OTA. Here is the stock firmware for your version. This would give you stock recovery, stock hboot but it may wipe all of your personal data off of the phone. Place the file in your fastboot/adb folder and rename it firmware.zip. Then you would flash it in bootloader/FASTBOOT USB:
Code:
[B][I]fastboot oem lock[/I][/B]
After that, type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Click to expand...
Click to collapse
After the reboot, you can install TWRP and then flash ARHD 81.0.
C:\AndroidSDK\sdk\platform-tools>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 1.146s
C:\AndroidSDK\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.034s]
finished. total time: 0.034s
C:\AndroidSDK\sdk\platform-tools>fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (47665 KB)...
OKAY [ 2.657s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 8.713s
C:\AndroidSDK\sdk\platform-tools>fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (47665 KB)...
OKAY [ 2.653s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 8.709s
C:\AndroidSDK\sdk\platform-tools>fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (47665 KB)...
OKAY [ 2.653s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 8.710s
C:\AndroidSDK\sdk\platform-tools>
Click to expand...
Click to collapse
I downloaded the file and flashed it, that's what I got.
I went ahead and flashed TWRP 2.6.3.3, that allowed me to have ADB and then I sideloaded the ARHD, now it's working and im setting up.
Question, now that I have the OS back, how should I go about getting S-off and the tampered warning removed. I presume this would save me from loads of trouble down the load. Thanks again in advance.
PlinXoom said:
I went ahead and flashed TWRP 2.6.3.3, that allowed me to have ADB and then I sideloaded the ARHD, now it's working and im setting up.
Question, now that I have the OS back, how should I go about getting S-off and the tampered warning removed. I presume this would save me from loads of trouble down the load. Thanks again in advance.
Click to expand...
Click to collapse
Achieve S-OFF with firewater or sunshine
Download and install this Bootloader Reset Tool
I went ahead and tried with firewater but ran into HTC anti firewater warning. I was told I needed to go back to stock Rom with bulletproof kernel to get it to work then load ARHD after. Being that if I don't intend to change the Rom any time soon, is it worth doing all the swapping around?
PlinXoom said:
I went ahead and tried with firewater but ran into HTC anti firewater warning. I was told I needed to go back to stock Rom with bulletproof kernel to get it to work then load ARHD after. Being that if I don't intend to change the Rom any time soon, is it worth doing all the swapping around?
Click to expand...
Click to collapse
If you develop an issue down the road it is easier to fix with the phone being S-OFF. However, it is a personal choice.
I figured as much, thanks again! :highfive:

Help!! relocked HTC Mini 2, No OS, S-ON, Unlocking Stuck at Entering Recovery

Hi Developers, i relocked my phone so that i could go back to stock rom after rooting had failed and i was stuck at twrp and had deleted my OS by mistake. I tried to install ruu zip but i couldn't find one that had the same CID No: Vodap203. Now my i can't use my phone anymore.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.1102.19.0708
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.18.163.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH4BLWR03678
(bootloader) imei: 351574062555221
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: mem_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P8B20000
(bootloader) cidnum: VODAP203
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 7ad7ebac
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.127s
Hastla said:
Hi Developers, i relocked my phone so that i could go back to stock rom after rooting had failed and i was stuck at twrp and had deleted my OS by mistake. I tried to install ruu zip but i couldn't find one that had the same CID No: Vodap203. Now my i can't use my phone anymore.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.1102.19.0708
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.18.163.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH4BLWR03678
(bootloader) imei: 351574062555221
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: mem_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P8B20000
(bootloader) cidnum: VODAP203
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 7ad7ebac
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.127s
Click to expand...
Click to collapse
The first thing you need to do is download the file here. Change the name to 0P8BIMG.ZIP(that's a zero not "O") and put it in your SD Card directly(No folders). Then get to the bootloader. the file should automatically be read and you will be prompted to flash it.
Make sure your bootloader is "LOCKED" or "RELOCKED" else this won't work
I've tried flashing this ruu before, but it doesn't work simply because the cid numbers are different.
Mine is Vodafone SFR cid No: X.XX.163.X
This Ruu Link is for Vodafone UK Cid No: X.XX.161.X
When flashing, after verification it Says "failed cid, update failed"
Hastla said:
Hi Developers, i relocked my phone so that i could go back to stock rom after rooting had failed and i was stuck at twrp and had deleted my OS by mistake. I tried to install ruu zip but i couldn't find one that had the same CID No: Vodap203. Now my i can't use my phone anymore.
Click to expand...
Click to collapse
Are you sure you deleted your system????
I found that sometimes relocking creates a different partition and the system disappears.
Try unlock bootloader again and check if system is still there.
Also have you tried this TWRP backup?
kativiti said:
Are you sure you deleted your system????
I found that sometimes relocking creates a different partition and the system disappears.
Try unlock bootloader again and check if system is still there.
Also have you tried this TWRP backup?
Click to expand...
Click to collapse
I'm sure i deleted my system. I still can't unlock the bootloader, when unlocking it sticks at entering recovery every now and then...
Hastla said:
I'm sure i deleted my system. I still can't unlock the bootloader, when unlocking it sticks at entering recovery every now and then...
Click to expand...
Click to collapse
if you cant unlock, then you doing something wrong. What error is showing in cmd???
what recovery you have installed?
are you using original HTC cable?
and of course dont start your phone with usb plugged
kativiti said:
if you cant unlock, then you doing something wrong. What error is showing in cmd???
what recovery you have installed?
are you using original HTC cable?
and of course dont start your phone with usb plugged
Click to expand...
Click to collapse
there is no error in cmd
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.110s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.009s]
finished. total time: 0.121s
the problem comes when you select yes on unlocking bootloader option. After pressing power button tounlock, It stuck at "entering recovery" in pink at the top, and down there is a message "This build is for development purposes only..." in red. I tried leaving it that way for like 48hrs, nothing happened
I flashed back the stock recovery to remove the "twrp" before relocking the bootloader after i realized that i had deleted my O.s in order to flash back RUU, only to realize that my cid doesn't march with the available Ruus.
Flashing another recovery right now i.e stock recovery via fastboot...this is the cmd error...
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
sending 'recovery' (9350 KB)...
OKAY [ 1.014s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.682s
Hastla said:
there is no error in cmd
Click to expand...
Click to collapse
OK now we are getting somewhere.
lets go step by step...
get the require goodies here
Flash TWRP and then perform a TWRP backup.
next use my backup to replace the one you just did. (you might have to use adb push if you don't have sdcard)
or if you going for the zip approach flah stock instead.
NOTE: When you flashing stock recovery DO NOT rename the file. it causes errors, like the one you are having.
kativiti said:
OK now we are getting somewhere.
lets go step by step...
get the require goodies here
Flash TWRP and then perform a TWRP backup.
next use my backup to replace the one you just did. (you might have to use adb push if you don't have sdcard)
or if you going for the zip approach flah stock instead.
NOTE: When you flashing stock recovery DO NOT rename the file. it causes errors, like the one you are having.
Click to expand...
Click to collapse
I've downloaded the files. I'm still getting the same error,
C:\Program Files\Minimal ADB and Fastboot>fastboot flash recovery twrp-2.8.1.0-2
0142812-memul.img
sending 'recovery' (10896 KB)...
OKAY [ 1.364s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.140s
I think probably because my bootloader is still Relocked. Unlocking bootloader still stuck at entering recovery. How do i get past unlocking the bootloader coz fastboot command is responding i.e
C:\Program Files\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.119s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.008s]
finished. total time: 0.150s
But when you select yes and press power button, phone doesn't reboot to unlock the bootloader but sticks at "Entering Recovery" in pink at the top. any help here....?
Hastla said:
I've downloaded the files. I'm still getting the same error,
C:\Program Files\Minimal ADB and Fastboot>fastboot flash recovery twrp-2.8.1.0-2
0142812-memul.img
sending 'recovery' (10896 KB)...
OKAY [ 1.364s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.140s
I think probably because my bootloader is still Relocked. Unlocking bootloader still stuck at entering recovery. How do i get past unlocking the bootloader coz fastboot command is responding i.e
C:\Program Files\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.119s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.008s]
finished. total time: 0.150s
But when you select yes and press power button, phone doesn't reboot to unlock the bootloader but sticks at "Entering Recovery" in pink at the top. any help here....?
Click to expand...
Click to collapse
ok. because you don't have system it will go to recovery but your recovery seems to be corrupted.
Can you double check in fastboot if you are in fact bootloader unlocked???
type command fastboot erase cache
try to flash this TWRP instead. (its the one im using)
csoulr666 said:
The first thing you need to do is download the file here. Change the name to 0P8BIMG.ZIP(that's a zero not "O") and put it in your SD Card directly(No folders). Then get to the bootloader. the file should automatically be read and you will be prompted to flash it.
Make sure your bootloader is "LOCKED" or "RELOCKED" else this won't work
Click to expand...
Click to collapse
kativiti said:
ok. because you don't have system it will go to recovery but your recovery seems to be corrupted.
Can you double check in fastboot if you are in fact bootloader unlocked???
type command fastboot erase cache
try to flash this TWRP instead. (its the one im using)
Click to expand...
Click to collapse
In Fastboot, my bootloader is still relocked. I don't know what to do now. And the link you provided for twrp needs a decryption key
cmd output...
C:\Program Files\Minimal ADB and Fastboot>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.020s]
finished. total time: 0.021s
Hastla said:
In Fastboot, my bootloader is still relocked. I don't know what to do now. And the link you provided for twrp needs a decryption key
cmd output...
C:\Program Files\Minimal ADB and Fastboot>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.020s]
finished. total time: 0.021s
Click to expand...
Click to collapse
you need to unlock bootloader
try command fastboot oem unlock
link to TWRP
you wont be able to install recovery until you unlock bootloader.
I strongly suggest you start over and do it again with HTC DEV website. get a new token
Also, are you using original HTC cable?
kativiti said:
you need to unlock bootloader
try command fastboot oem unlock
link to TWRP
you wont be able to install recovery until you unlock bootloader.
I strongly suggest you start over and do it again with HTC DEV website. get a new token
Also, are you using original HTC cable?
Click to expand...
Click to collapse
the cmd command doesn't work
C:\Program Files\Minimal ADB and Fastboot>fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.030s]
finished. total time: 0.031s
I've requested another token from htc dev it responds but pressing the power button afer selecting unlock bootloader, stuck in entering recovery and doesn't reboot, so it doesn't unlock
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hastla said:
the cmd command doesn't work
C:\Program Files\Minimal ADB and Fastboot>fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.030s]
finished. total time: 0.031s
I've requested another token from htc dev it responds but pressing the power button afer selecting unlock bootloader, stuck in entering recovery and doesn't reboot, so it doesn't unlock
Click to expand...
Click to collapse
Its getting hard.
Did you install any custom kernel?
kativiti said:
Its getting hard.
Did you install any custom kernel?
Click to expand...
Click to collapse
No i did not. The only thing that i tried to instal was twrp.
I got a kernel from htc dev that with same cid num as my device. Any idea of how it could help?
Hastla said:
I got a kernel from htc dev that with same cid num as my device. Any idea of how it could help?
Click to expand...
Click to collapse
For some reason you are unable to unlock bootloader. If no one else have any idea why, i suggest you send it off to HTC to repair. there's a 50/50 change they wont charge you.

Categories

Resources