Develop Bugs

[Q][SOLVED] Need help with bricked Desire Z - S-ON | Stuck on white HTC logo

Hi, can some one respond to this? perhaps I bricked my Z doing:
I had rooted and S-OFF and I flashed PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip"
as I wanted to return to original stock rom. I did it from Goldcard SD card, what I prepared before. By doing this I lost root but remained S-OFF
Than I followed: http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Unrooting_and_Returning_to_Stock go to S-ON and I managed this. Everything was going smooth so later when I was non root and S-ON, an OTA update came and I confirmed. Also next OTA update 2.3.3 T-mobile came with 73MB update and I confirmed too later. But the phone stucked after second update to 2.3.3 on HTC Logo and does not boot system.
- Hboot works
- recovery does not work (red attention mark)
- I have working fastboot and adb from PC
- phone is now S-ON and not rooted
... but not sure how to continue
tried flash new recovery but all fastboot end up like this:
Code:
$ fastboot flash recovery recovery-clockwork-3.0.2.4-vision.img
sending 'recovery' (4466 KB)...
OKAY [ 0.770s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.261s
I can not flash another PC10IMG.zip as it says, no valid ID.
Really sucked here.
Anyone some good ideas or phone is postmortem?

You flashed a g2 rom on your dz?
I'd say grab the lastest rom from http://www.shipped-roms.com/index.php?category=android&model=Vision
and flash it via ruu mode (fastboot oem rebootRUU, fastboot flash zip nameOfZip.zip)
-Nipqer

Yes I did
I tried now as per your advise, but I have signature errors, tried two zips, same result.
Code:
$ fastboot flash zip Vision_TMOUS_1.12.531.0_Radio_12.18.60.05P_26.01.00.17_M2_144460.zip
sending 'zip' (118430 KB)...
OKAY [ 20.029s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 33.034s
Any Ideas?

bump, anyone please?
Flashing any stock rom end up with signature error, the phone is branded to (INFOCID is T-MOB010)
no access to adb
INFOversion: 0.5
INFOversion-bootloader: 0.82.0000
INFOversion-baseband: 26.02.01.15_M2
INFOversion-cpld: None
INFOversion-microp: 0425
INFOversion-main: 1.19.531.1
INFOserialno: SH133RT00363
INFOimei: 352212047598680
INFOproduct: vision
INFOplatform: HBOOT-7230
INFOmodelid: PC1011000
INFOcidnum: T-MOB010
INFObattery-status: good
INFObattery-voltage: 3939mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-fafe9aa3
INFOhbootpreupdate: 11
INFOgencheckpt: 0

Try a different rom from shipped-roms.
the 1.19.531.1 rom or higher
-Nipqer

Nipqer said:
Try a different rom from shipped-roms.
the 1.19.531.1 rom or higher
-Nipqer
Click to expand...
Click to collapse
thanks. all images and I tried about 6 different including RRU I got from exe and gained from temp dir gives:
Code:
Image verification failed
HBOOT drops back to main menu, recovery says this error message.
any more hints?

Could you join the #G2ROOT irc channel on freenode It'll be easier to try help you there.
-Nipqer

Solved by creating GC by different method. Looks we did not have working GC before.

Can you be a bit more specific?
Sent from my HTC Vision using Tapatalk 2

Wildfire jammed in FASTBOOT

Welcome.
I have the following problem with my HTC. When you turn on the phone immediately turns on fastboot and can not control buttons Vol + / - on the menu. Can I come in hboot, but there did not respond to my commands.
It is a chance to solve the problem?
*** UNLOCKED ***
BUZZ PVT SHIP S-ON
HBOOT-1002.0000
MICROP-0622
TOUCH PANEL-ATMELC03_16ac
RADIO-3.35.20.10
Click to expand...
Click to collapse

BukeR00 said:
Welcome.
I have the following problem with my HTC. When you turn on the phone immediately turns on fastboot and can not control buttons Vol + / - on the menu. Can I come in hboot, but there did not respond to my commands.
It is a chance to solve the problem?
Click to expand...
Click to collapse
Does it boot Into hboot or fastboot specifically? Also do you have an sdcard in the phone? And lastly when you plug in the usb cable to issue commands does the phone change to hbootUSB or fastbootUSB at all and does Windows detect and Install drivers?
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2

When I push the power button, phone starts in FASTBOOT. I can run it in hboot by pressing Vol-+ PWR.
In both modes, the buttons are not working. When I connect the USB cable changes as FASTBOOT USB / HBOOT USB or something like that. I have a card in your phone, I try without the card.

BukeR00 said:
When I push the power button, phone starts in FASTBOOT. I can run it in hboot by pressing Vol-+ PWR.
In both modes, the buttons are not working. When I connect the USB cable changes as FASTBOOT USB / HBOOT USB or something like that. I have a card in your phone, I try without the card.
Click to expand...
Click to collapse
OK please try without the card in also when you are in fastboot USB can you issue the command fastboot getvar all please and see if it works.
Sent from my Nexus 7 using Tapatalk 4

Code:
C:\adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.02.0000
INFOversion-baseband: 3.35.20.10
INFOversion-cpld: None
INFOversion-microp: 0622
INFOversion-main: 2.46.0.0
INFOserialno: ###########
INFOimei: ###########
INFOproduct: buzz
INFOplatform: HBOOT-7225
INFOmodelid: PC4910000
INFOcidnum: HTC__032
INFObattery-status: good
INFObattery-voltage: 3955mV
INFOpartition-layout: HTC
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 42e5cc47
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.053s
Without the card the same problems. Keys are not working. When I'm try to upload RUU crashes. 155 ERROR. I tried to many versions, as last RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.24H_3.35.20.10_release_160191_signed
Thanks for your reply

BukeR00 said:
Code:
C:\adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.02.0000
INFOversion-baseband: 3.35.20.10
INFOversion-cpld: None
INFOversion-microp: 0622
INFOversion-main: 2.46.0.0
INFOserialno: ##########
INFOimei: ###############
INFOproduct: buzz
INFOplatform: HBOOT-7225
INFOmodelid: PC4910000
INFOcidnum: HTC__032
INFObattery-status: good
INFObattery-voltage: 3955mV
INFOpartition-layout: HTC
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 42e5cc47
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.053s
Without the card the same problems. Keys are not working. When I'm try to upload RUU crashes. 155 ERROR. I tried to many versions, as last RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.24H_3.35.20.10_release_160191_signed
Thanks for your reply
Click to expand...
Click to collapse
I should have said, block out your imei and HTC serial number like I have. You never know whos watching...
Anyway, your bootloader is still unlocked so ruus wont flash. You can use the command fastboot oem lock to relock the bootloader. But, it's unlikely that it will work as you have an upgraded hboot. If I was you I would I would extract the Rom.zip from the ruu. Then extract that Rom.zip and you should end up with several images and some .nbh files. place the boot.img, system.img, data.img Into your fastboot folder. Then you going to want to format the phone with fastboot and then flash the phone with fastboot. http://androidforums.com/one-s-all-things-root/714676-list-fastboot-command.html here is a command list but I will tell you what I think it should be, and if you hit a snag refer to the link. So the commands should be in this order assuming you are CD'd to your fastboot folder
fastboot format boot
fastboot format system
fastboot format data
fastboot format cache
Then assuming it all goes well then issue these commands
fastboot flash system.img
fastboot flash data.img
fastboot flash boot.img
fastboot flash boot.img
fastboot reboot
Yes that flash the boot.img twice is not a typo all going well after this you should able to boot up. if you hit any big problems just hit the thread pal
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2

Code:
C:\adb>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (No such file or directory))
finished. total time: 0.015s
In FASTBOOT shows now - *** RELOCKED ***
Code:
fastboot format boot
fastboot format system
fastboot format data
fastboot format cache
It does not work. There is no these commands
Code:
C:\adb>fastboot erase boot
erasing 'boot'... FAILED (remote: not allowed)
finished. total time: 0.002s
C:\adb> fastboot erase data
erasing 'data'... FAILED (remote: not allowed)
finished. total time: 0.002s
C:\adb>fastboot erase system
erasing 'system'... FAILED (remote: not allowed)
finished. total time: 0.002s
Code:
C:\adb>fastboot flash system.img
unknown partition 'system.img'
error: cannot determine image filename for 'system.img'
C:\adb>\fastboot flash data.img
'\fastboot' is not recognized as an internal or external command,
operable program or batch file.
C:\adb>fastboot flash boot.img
unknown partition 'boot.img'
error: cannot determine image filename for 'boot.img'
C:\adb>fastboot flash system system.img
sending 'system' (212163 KB)... OKAY [ 44.854s]
writing 'system'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 98.833s
C:\adb>fastboot flash boot boot.img
sending 'boot' (2476 KB)... OKAY [ 1.050s]
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.689s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.012s
In my rom.zip there is no data.img
After the command fastboot reboot the phone hangs on the white HTC boot screen.

BukeR00 said:
Code:
C:\adb>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (No such file or directory))
finished. total time: 0.015s
In FASTBOOT shows now - *** RELOCKED ***
Code:
fastboot format boot
fastboot format system
fastboot format data
fastboot format cache
It does not work. There is no these commands
Code:
C:\adb>fastboot erase boot
erasing 'boot'... FAILED (remote: not allowed)
finished. total time: 0.002s
C:\adb> fastboot erase data
erasing 'data'... FAILED (remote: not allowed)
finished. total time: 0.002s
C:\adb>fastboot erase system
erasing 'system'... FAILED (remote: not allowed)
finished. total time: 0.002s
Code:
C:\adb>fastboot flash system.img
unknown partition 'system.img'
error: cannot determine image filename for 'system.img'
C:\adb>\fastboot flash data.img
'\fastboot' is not recognized as an internal or external command,
operable program or batch file.
C:\adb>fastboot flash boot.img
unknown partition 'boot.img'
error: cannot determine image filename for 'boot.img'
C:\adb>fastboot flash system system.img
sending 'system' (212163 KB)... OKAY [ 44.854s]
writing 'system'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 98.833s
C:\adb>fastboot flash boot boot.img
sending 'boot' (2476 KB)... OKAY [ 1.050s]
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.689s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.012s
In my rom.zip there is no data.img
After the command fastboot reboot the phone hangs on the white HTC boot screen.
Click to expand...
Click to collapse
Ah. This could be problematic. I should have been clearer, I didn't mean for you to lock your bootloader again, I was simply informing you it would need to be locked for an ruu to run. None of those commands will work while the bootloader is locked. If you were the one to unlock the device the you can unlock it again assuming you have the unlock_token.bin, using the same fastboot command again. If you didn't you will have to go to www.htcdev.com and make an account, then go to bootloader unlock, select wildfire buzz and ignore the bootloader update, as you already have it. (Skip should be near the bottom.) Then follow the instructions and get the bootloader unlocked again. Then issue the commands excluding the lock bootloader one and the flash data data.img as you don't have it. Its not a problem though, I was just covering all bases, incase it did have a data.img in there make sure you still do the data format though!
Sorry for the confusion
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2

What version of RUU I must use? I tested 3 versions and none of them has data.img
I have uploaded the files system.img, recovery.img, userdata.img and the phone still does not work. How can I delete the data. Fastboot format command does not work, there is no such command.
And after the command fastboot erase still:
Code:
C:\adb>fastboot erase boot
erasing 'boot'... FAILED (remote: not allowed)
finished. total time: 0.002s
C:\adb> fastboot erase data
erasing 'data'... FAILED (remote: not allowed)
finished. total time: 0.002s
C:\adb>fastboot erase system
erasing 'system'... FAILED (remote: not allowed)
finished. total time: 0.002s

BukeR00 said:
What version of RUU I must use? I tested 3 versions and none of them has data.img
I have uploaded the files system.img, recovery.img, userdata.img and the phone still does not work. How can I delete the data. Fastboot format command does not work, there is no such command.
And after the command fastboot erase still:
Code:
C:\adb>fastboot erase boot
erasing 'boot'... FAILED (remote: not allowed)
finished. total time: 0.002s
C:\adb> fastboot erase data
erasing 'data'... FAILED (remote: not allowed)
finished. total time: 0.002s
C:\adb>fastboot erase system
erasing 'system'... FAILED (remote: not allowed)
finished. total time: 0.002s
Click to expand...
Click to collapse
did you get the bootloader unlocked again? fastboot commands will only work on unlocked bootloaders.
Dont worry about the data.img, you do not need it. i simply added it incase the ruu had it and you got confused. again, it is not required.

Yes, I have unlocked bootloader, but comands still don't work.
//edit:
C:\sdk\sdk\platform-tools>fastboot format boot
formatting 'boot' partition...
FAILED (remote: unknown command)
FAILED (remote: unknown command)
finished. total time: 0.006s
C:\sdk\sdk\platform-tools>fastboot format system\
formatting 'system\' partition...
FAILED (remote: unknown command)
FAILED (remote: unknown command)
finished. total time: 0.006s
C:\sdk\sdk\platform-tools>fastboot format userdata
formatting 'userdata' partition...
FAILED (remote: unknown command)
FAILED (remote: unknown command)
finished. total time: 0.006s
Click to expand...
Click to collapse

BukeR00 said:
Yes, I have unlocked bootloader, but comands still don't work.
//edit:
Click to expand...
Click to collapse
hmmm. well if we cannot format the partitions then we are not going to have much luck :/
ok lets try a different tactic. download this and rename it to just recovery.img . then place it into your adb folder and then issue the following command via fastboot.
Code:
fastboot boot recovery.img
hopefully this will allow you to boot into clockworkmod recovery. when you enter clockworkmod recovery use the volume buttons to move and the trackball to select, power is back. format everything. then try to mount your sdcard using advanced/mount storage or sdcard, something to that effect. then place this file onto it. all going well you should be able to then flash this rom. dismount the usb storage, then go back to the main menu (power button) then go to flash/install, select choose zip and then the zip file we placed there. hopefully the recovery will install without issue. then, open the copy of the rom you downloaded on your pc and extract the boot.img. reboot the phone into fastboot and then use the command fastboot flash boot boot.img
all going well this rom will boot and you will have a working phone again.

Unfortunately, it does not change anything. I can not enter into Clockworkmod recovery. The keys are not working

BukeR00 said:
Unfortunately, it does not change anything. I can not enter into Clockworkmod recovery. The keys are not working
Click to expand...
Click to collapse
it should boot into cwm automatically, no button intervention required.

Unfortunately does not turn ClockworkMod. Phone lay two days without batteries, has launched today as normal. Everything worked. I wanted to do S-OFF by unrevoked, entered into hboot, the phone resets and hung on the HTC screen. After removing the battery turns on hboot again. In Unrevoked I saw that wrote "ClockworMode Recovery"

BukeR00 said:
Unfortunately does not turn ClockworkMod. Phone lay two days without batteries, has launched today as normal. Everything worked. I wanted to do S-OFF by unrevoked, entered into hboot, the phone resets and hung on the HTC screen. After removing the battery turns on hboot again. In Unrevoked I saw that wrote "ClockworMode Recovery"
Click to expand...
Click to collapse
Unrevoked doesnt s-off it only roots and flashes a recovery.
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2

[Q]Error rom update: FAILED (remote: not allowed)

I've been trying to update my phone to taktik for a few days now, but I can't flash the rom.
bootloader:
Code:
ACE PVT SHIP S-OFF RL
HBOOT-2.00.0027
MICROP-0438
RADIO 26.14.52.27
eMMC boot
Code:
C:\Users\Johan>fastboot devices
HT0BSRX00016 fastboot
C:\Users\Johan>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 2.00.0027
INFOversion-baseband: 26.14.52.27
INFOversion-cpld: None
INFOversion-microp: 0438
INFOversion-main: 3.12.405.2
INFOserialno: HT0BSRX00016
INFOimei: 352668043966306
INFOproduct: ace
INFOplatform: HBOOT-7230
INFOmodelid: PD9810000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 4138mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 743ca94a
INFOhbootpreupdate: 11
INFOgencheckpt: 0
INFOregion-id: 0
all: Done!
finished. total time: 0.020s
What I tried:
Easy ace root tool:
Code:
your build version is 3.12.405.2
Your will reboot in fastboot again to continue the process
* server not running *
Obtaining Unlock Token
< waiting for device >
[B] ... INFO[ERR] Command error !!![/B]
OKAY [ 0.008s]
finished. total time: 0.009s
adb fastboot flash
Code:
sending 'recovery' (4876 KB)...
OKAY [ 1.131s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.458s
When I try to go into recovery I get a red triangle.
I spend many hours trying to fix this en searched dozens of threads, but I can't find a solution.

johanliefers said:
I've been trying to update my phone to taktik for a few days now, but I can't flash the rom.
bootloader:
I spend many hours trying to fix this en searched dozens of threads, but I can't find a solution.
Click to expand...
Click to collapse
Update your hboot to .0029 then unlock your bootloader via HTCDev site.Google for the hboot update.
EDIT: Just saw you're S-OFF.Just rename this zip to PD98IMG.zip, put it on your sdcard and boot to bootloader(not fastboot, the main menu of the bootloader)hit any button and it will ask for an update.Confirm, then reboot when it asks.In bootloader go to recovery, and select it.You should have CWM.

Steam. said:
Update your hboot to .0029 then unlock your bootloader via HTCDev site.Google for the hboot update.
EDIT: Just saw you're S-OFF.Just rename this zip to PD98IMG.zip, put it on your sdcard and boot to bootloader(not fastboot, the main menu of the bootloader)hit any button and it will ask for an update.Confirm, then reboot when it asks.In bootloader go to recovery, and select it.You should have CWM.
Click to expand...
Click to collapse
Thanks a lot! It worked. I just put PD98IMG.zip on my sd, now I can get into recovery again.

HTC DESIRE HD s-on
johanliefers said:
Thanks a lot! It worked. I just put PD98IMG.zip on my sd, now I can get into recovery again.
Click to expand...
Click to collapse
what should i do?.....................................................................................

[Q] Back to Stock HTC One X

Ok so, I decided the custom rom thing I was doing was getting boring so I wanted to get back to my stock rom. Y'know, htc one x, 4.2.2 Sense 5 that all cool stuff.
I got instructions and I tried my best in the following order.
Getting fastboot
putting boot and recovery in fastboot
flashing them and erasing cashe
relocking bootloader and erasing cashe
booting to fastboot mode again
starting RUU exe
now the RUU exe had a problem. I did a fastboot getvar cid to find i needed the following: CID HTC__J15
from here: http://forum.xda-developers.com/showthread.php?t=1975140
now that thread linked me to a .rar file that didn't have an exe file in it so i was super confused.
So i googled and i found this file:
RUU_ENDEAVOR_U_ICS_40_HTC_ARA_1.29.415.11_Radio_1.1204.105.14_release_260742_signed.exe
(^I lost the link lol, but thats the file name)
which matched what i needed. I think.
When i ran that, it said I had the wrong RUU for that device. Do i? I'm not really sure. Can someone link me to the right one?
Problem is also that I can't get past the bootloader screen now. Turning it off and on just brings me back to the bootloader.

Shiverfire said:
Ok so, I decided the custom rom thing I was doing was getting boring so I wanted to get back to my stock rom. Y'know, htc one x, 4.2.2 Sense 5 that all cool stuff.
I got instructions and I tried my best in the following order.
Getting fastboot
putting boot and recovery in fastboot
flashing them and erasing cashe
relocking bootloader and erasing cashe
booting to fastboot mode again
starting RUU exe
now the RUU exe had a problem. I did a fastboot getvar cid to find i needed the following: CID HTC__J15
from here: http://forum.xda-developers.com/showthread.php?t=1975140
now that thread linked me to a .rar file that didn't have an exe file in it so i was super confused.
So i googled and i found this file:
RUU_ENDEAVOR_U_ICS_40_HTC_ARA_1.29.415.11_Radio_1.1204.105.14_release_260742_signed.exe
(^I lost the link lol, but thats the file name)
which matched what i needed. I think.
When i ran that, it said I had the wrong RUU for that device. Do i? I'm not really sure. Can someone link me to the right one?
Problem is also that I can't get past the bootloader screen now. Turning it off and on just brings me back to the bootloader.
Click to expand...
Click to collapse
post the result from command fastboot getvar all and delete your S/N and IMEI from the info

plzzzzz help i have same problem
plzzzzz help i have same problem

nima619 said:
plzzzzz help i have same problem
Click to expand...
Click to collapse
Read along and do the same
Sent from my HTC One X using XDA Premium 4 mobile app

(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.73.0000
(bootloader) version-baseband: 5.1204.167.31
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.415.3
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 3730mV
(bootloader) devpower: 56
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.954s

Only way to go back to stock rom is a nandroid backup. Ruu does not exist with that number.
I am hosting one here
Nandroid backup HTC__J15 - 4.20.415.rar - 614.05 MB
Flash the recovery.img AND the boot.img from the nandroid backup. Then mount the sdcard in the recovery and unpack the .rar file to the designated path.
Probably clockworkmod\backup\time and date folder\nand backup files in img and tar files etc etc
Then make a full wipe in the recovery (wipe ALL you can EXCEPT the sdcard)
Then restore the nand.
Sent from my HTC One X using XDA Premium 4 mobile app

ok i did that and:
\Fastboot>fastboot flash boot boot.img
sending 'boot' (8192 KB)...
OKAY [ 1.030s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 1.240s
\Fastboot>fastboot flash recovery recovery.img
sending 'recovery' (8192 KB)...
OKAY [ 1.118s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.325s
It won't let me go into recovery. Just comes back to bootloader. I can't mount the nandroid backup into the device

Shiverfire said:
ok i did that and:
\Fastboot>fastboot flash boot boot.img
sending 'boot' (8192 KB)...
OKAY [ 1.030s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 1.240s
\Fastboot>fastboot flash recovery recovery.img
sending 'recovery' (8192 KB)...
OKAY [ 1.118s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.325s
It won't let me go into recovery. Just comes back to bootloader. I can't mount the nandroid backup into the device
Click to expand...
Click to collapse
Are you UNLOCK your bootloader via htcdev.com?

Yeah it's locked or relocked
Sent from my HTC One X using XDA Premium 4 mobile app

In the first step I said I relocked my bootloader cause it was a step I read in a tutorial to go back to stock. It says ***RELOCKED*** on top.

Unlock it.......
Sent from my HTC One X using XDA Premium 4 mobile app

ok this is really annoying. my phone cant complete unlocking the bootloader cause its battery is too low. i put it on charge for 2 hours and its still low cause i cant turn the screen off or turn the phone off. When i turn the phone off without the charger, it stays off, but as soon as i put it in, it turns on. Ughhh

Use the batt script in fastboot mode to charge the battery
https://www.dropbox.com/s/aaah8gqz8j024xz/Batt script.bat
Phone in fastboot mode, script in fastboot folder and execute it with admin rights !
Sent from my HTC One X using XDA Premium 4 mobile app

Got it charged and fixed! Restoring now!

.-. nvm it got stuck when when i chose recovery in bootloader

Got stuck how ?
Sent from my HTC One X using XDA Premium 4 mobile app

when i go into recovery (i tried with rom manager too) it stops at the HTC screen

Fastboot flash the recovery.img from the nand backup. Also do :
Fastboot erase cache
After the recovery.img flash !
P.s. ditch rommanager ....it's useless on the hox !
Sent from my HTC One X using XDA Premium 4 mobile app

Ok tried restoring and it said MD5 was a mismatch.

Go here for that
http://forum.xda-developers.com/showthread.php?t=2579568
Sent from my HTC One X using XDA Premium 4 mobile app

Can't Flash TWRP "Signature Verify Fail"

This is an ATT version phone I rooted this phone a couple of days ago with TWRP. However, I had to use adb to enter fastboot as it would not go to fastboot using power/volume keys. Actually, it never shows a fastboot screen, even in adb, so it may have been going into fastboot all along and I just could not see it.
So, instead of leaving well enough alone, I RUU'ed (newest ATT version from HTC site) it to try to get fastboot to work normally (it still works, I just can't see it on screen). Now, I can't get rooted again. FWIW, I did make a backup with TWRP before RUU'ed. Regardless, there is nothing on this phone I need to keep, I just want to root it before I start using it.
Any help is greatly appreciated...
Here is my unlock sequence. Note what happens if I try to flash TWRP immediately after unlock. I have to CTRL C and Reboot phone.
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash unlockt
oken unlock_code.bin
target reported max download size of 1826414592 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.110s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.012s]
finished. total time: 0.125s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recover
twrp30m8.img
^C
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb reboot bootloader
Now when I try to flash TWRP, I get :
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recover
twrp30m8.img
target reported max download size of 1826414592 bytes
sending 'recover' (20022 KB)...
OKAY [ 1.884s]
writing 'recover'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.611s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.28.502.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(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: 7f8e91a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.089s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot devices
HT445####### fastboot
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.013s

Fastboot flash recover is wrong, it should be :
Fastboot flash recovery < see the Y there.

Mr Hofs said:
Fastboot flash recover is wrong, it should be :
Fastboot flash recovery < see the Y there.
Click to expand...
Click to collapse
Same Results:
C:\s>fastboot flash recovery twrpm8.img
target reported max download size of 1826414592 bytes
sending 'recovery' (14818 KB)...
OKAY [ 1.438s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.976s
C:\s>
C:\s>fastboot flash recovery twrp30m8
error: cannot load 'twrp30m8'
C:\s>fastboot flash recovery twrp30m8.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20022 KB)...
OKAY [ 1.889s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.616s
C:\s>

Bad download then, see how the sizes of the file are different when you flash it again. At least the command is correct now. Re-download the recovery file and try again.

Mr Hofs said:
Bad download then, see how the sizes of the file are different when you flash it again. At least the command is correct now. Re-download the recovery file and try again.
Click to expand...
Click to collapse
Already tried that, but tried again. First below is my result before I downloaded new twrp and the second one is my result after I re-downloaded image
C:\s>fastboot flash recovery twrp.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20022 KB)...
OKAY [ 1.896s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.625s
C:\s>fastboot flash recovery twrp.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20022 KB)...
OKAY [ 1.899s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.625s
C:\s>

Try the HTC_fastboot adb package. It's posted several times here on xda.

Mr Hofs said:
Try the HTC_fastboot adb package. It's posted several times here on xda.
Click to expand...
Click to collapse
Still no luck, same error (see below). This worked flawless before I flashed the latest ATT RUU.
Is it possible phone is still not unlocked or would I be getting that far if it was still locked?
Question. This phone is AT&T (more details in getvar above) but at the end of the contract, AT&T sent me code to unlock the SIM. Now, the SIM I am using is on a T-Mobile MVNO (TING). Since they SIM unlocked the phone, would I be able to and would there be any advantage/risk to trying to flash the Stock RUU for HTC unlocked/developer. It is a higher software version than the ATT version I flashed (twice).
C:\FB>htc_fastboot flash recovery twrp.img
sending 'recovery' (20022 KB)... OKAY
writing 'recovery'... (bootloader) signature checking...
FAILsignature verify fail
FAILED (remote: signature verify fail)
Execution time is 3(s)

Any other ideas? I can't see bootloader screen, but it appears I can access and do all bootloader functions in adb.
I would really like to be able to eliminate locked bootloader as the issue, is there anything else I can flash or try that might let me know if bootloader is still locked. I can get results from getvar and fastboot devices.
I also have an image of the phone saved from TWRP before I flashed the RUU, but seems no way to get that image back. I am not opposed to purchasing S-off if that will for sure help me.

Try to flash a lower version of TWRP and see if that helps: https://dl.twrp.me/m8/twrp-2.8.7.0-m8.img.html

joikep said:
Try to flash a lower version of TWRP and see if that helps: https://dl.twrp.me/m8/twrp-2.8.7.0-m8.img.html
Click to expand...
Click to collapse
Already tried two previous versions

rockfordpi said:
Already tried two previous versions
Click to expand...
Click to collapse
OK, lets try this a different way. IF one were to try to flash TWRP to M8 AND the bootloader was NOT UNLOCKED, what error message would one get?
Would there still be a response from adb getvar and fastboot devices IF the bootloader were locked?
Trying to eliminate potential issues one at a time
Is there a more appropriate forum for me to post the question?

rockfordpi said:
OK, lets try this a different way. IF one were to try to flash TWRP to M8 AND the bootloader was NOT UNLOCKED, what error message would one get?
Would there still be a response from adb getvar and fastboot devices IF the bootloader were locked?
Trying to eliminate potential issues one at a time
Is there a more appropriate forum for me to post the question?
Click to expand...
Click to collapse
OK, we can close this one out. I did want to post my solution, just in case anyone else had a similar error.
Long Story a little bit shorter, on my HTC one M8, the error:
sending 'recovery' (11976 KB)... OKAY
writing 'recovery'... (bootloader) signature checking...
FAILsignature verify fail
FAILED (remote: signature verify fail)
Was due to a locked bootloader. Because, for some reason I can't see the bootloader on my phone, I could not see the lock status, so I was having to do EVERYTHING via ADB. The problem was, when unlocking the bootloader there is screen on the phone that asks you to confirm yes or no if you want to unlock it. I could not see that screen and the instructions I was reading left that out (It was a good assumption that if one was trying to unlock one would know to say YES. LOL). So, I was missing that step. When I found that step, even though I could not see it on screen, I just blindly pushed volume down and then power to select. At that point it unlocked and allowed me to flash twrp 3.0.
Still do not know WHY I can't see the bootloader screen. I wonder if for some reason the colors are off in my bootloader screen and all the words are the same color as the background or it is trying to redirect that output somewhere else.
but at this point I am going to live with it as trying to fix it is what got me in here in the first place.

Hi,
I have the same problem phne always reboot in fastboot menu.
The status is also RELOCKED after fashing stock ROM RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
But I'm not able to user adb : device not found.
Fastboot seems working but not adb
Someone have an idea to help me ?
Many thanks

foosee said:
Hi,
I have the same problem phne always reboot in fastboot menu.
Click to expand...
Click to collapse
The top post is in regards to getting signature verify fail message when flashing custom recovery. So I don't see how it's the "same problem".
Be careful about saying "same problem" without giving any specific information about your actual problem, or device details. From my experience, I've seen many dozens of times where folks say they have the "same problem" and when prompted for more info, we find there are many many differences.
foosee said:
Hi,
I have the same problem phne always reboot in fastboot menu.
The status is also RELOCKED after fashing stock ROM
RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
Click to expand...
Click to collapse
Did the RUU flash successfully, or were there any error messages?
Also, please do fastboot getvar all, and post the results (delete IMEI and serial number before posting) so we can see more info about the phone.
foosee said:
But I'm not able to user adb : device not found.
Fastboot seems working but not adb
Click to expand...
Click to collapse
This is normal and expected. You can't use adb when in bootloader. And you can't use fastboot and adb simultaneously. Meaning, when one works, the other will not work, by definition.
Fastboot = only works in bootloader fastboot mode
adb = only works within OS, or alternately will work in custom recovery TWRP
If you issue the command fastboot devices, you should find that it works.
It is also not clear what you are trying to use adb to do (what commands?).