• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

HTC ONE M7 BRICKED?

P

paintman64

Lurker
My HTC One M7 is stuck in black screen with HTC In middle and four triangles with ! in them at four corners. It does not go into the recovery mode or anything. When I connect to laptop, it stays in the same screen, but if I disconnect the laptop cable, it goes into a screen showing:
****Tampered***
****Relocked****
M7_UL PVT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4T.35.3218.16
OpenDSP-v35.120.274.0718
OS-6.10.531.10 (7.18.531.35)
e-MMC-boot 2048MB
Aug 19 2015, 03:47:53.0

RUU

RUU is highlighted in orange, but I cant get to move to it or click it or select it.

I downloaded twrp.img and when I give "fastboot flash recover twrp.img", i get the following:
Target reported max download size of 1514139648 bytes
sending "recovery" (9932KB)
okay [1.213 S]
writing 'recovery'
<bootloader> signature checking....
FAILED <remote : 12 signature verify fail>
Finished. total time : 2.254 s

Please help. I am at my wits end.

Thanks in advance
Paintman64
 
You cannot flash TWRP because the bootloader is locked. Either unlock it again or try reflashing with an RUU.

What happened to get it into this state? And how come you have a phone that has been unlocked and modified and know about TWRP but don't recognise the bootloader (the screen with the information) even in an unusual state?
 
Hi, Hadron. Thank you for the revert. Long story short. It started with a boot-loop. I unlocked the bootloader using HTCdev. As I could not find a correct RUU, I flashed twrp and flashed a third party rom. It flashed well, but did not recognize the sim card and was unstable. I found a T-Mobile RUU and started flashing. Flashing failed in the middle, and I ended up with a phone with the four triangles. I am trying to unlock the bootloader again, through HTC Dev, but am unable to. I tried to flash a T-mobile RUU now, with a matching CID, but still, there is a signature verify fail was returned. Any help is appreciated.
Thanks in advance. Hope my rambling makes sense.

Best,

Paintsman
 
Hi

Unlocked bootloader again using unlockcode.bin received from HTC. When i flashed the RUU using flashboot flash zip xxxx.zip, error returned: 12 signature very fail. Any help is appreciated.

Thanks in advance.
 
You are sure this RUU is a good download (you checked the md5sum) and is at least as new as your phone's firmware (since it won't let you downgrade the firmware using an RUU)? And that it's an official RUU, not some other zip (anything other than a full official RUU will produce a signature verification error).

If you have the RUU as a zip then have you made sure it's in RUU mode before you tried to flash it? Use

fastboot oem rebootRUU

before you try "fastboot flash zip". From memory that should give you a black screen with HTC in silvery letters, which is "RUU mode". "fastboot flash zip" won't work in ordinary fastboot mode.

Note that flashing an RUU this way is a two-stage process. The first time you do it it should just flash the hboot, then end with a message like:

"FAILED (remote: 90 hboot pre-update! please flush image again immediately)"

(Why they've never corrected that spelling mistake I don't know ;)). So if you see what looks like a successful hboot flash followed by that message, do what it says and repeat the "fastboot flash zip xxxx.zip" command. The second time it should take a lot longer, flash all the other partitions, and end with a lot of messages telling you it's succeeded. The progress bar on the phone screen should stop at ~90% - that's normal. The last bit is rebooting, but it stops rather than doing that automatically in case there are any errors during the flashing (to give you a chance to fix them). As long as there are no errors and the computer tells you it was successful you can then

fastboot reboot-bootloader

and it should complete.
 
Hadron said:
You are sure this RUU is a good download (you checked the md5sum) and is at least as new as your phone's firmware (since it won't let you downgrade the firmware using an RUU)? And that it's an official RUU, not some other zip (anything other than a full official RUU will produce a signature verification error).

If you have the RUU as a zip then have you made sure it's in RUU mode before you tried to flash it? Use

fastboot oem rebootRUU

before you try "fastboot flash zip". From memory that should give you a black screen with HTC in silvery letters, which is "RUU mode". "fastboot flash zip" won't work in ordinary fastboot mode.

Note that flashing an RUU this way is a two-stage process. The first time you do it it should just flash the hboot, then end with a message like:

"FAILED (remote: 90 hboot pre-update! please flush image again immediately)"

(Why they've never corrected that spelling mistake I don't know ;)). So if you see what looks like a successful hboot flash followed by that message, do what it says and repeat the "fastboot flash zip xxxx.zip" command. The second time it should take a lot longer, flash all the other partitions, and end with a lot of messages telling you it's succeeded. The progress bar on the phone screen should stop at ~90% - that's normal. The last bit is rebooting, but it stops rather than doing that automatically in case there are any errors during the flashing (to give you a chance to fix them). As long as there are no errors and the computer tells you it was successful you can then

fastboot reboot-bootloader

and it should complete.
Click to expand...
HI Hadron,

Thank you. My apologies for delay in responding. I was traveling and connectivity was poor.

1. When i issue command fastboot oem rebootRUU, I get response OKAY, finished. So I think the RUU mode is on. But the phone screen stays on black screen, four triangles in four corners and htc in silver letters in middle.

2. The RUU I am using is RUU Zip M7_UL_JB43_SENSE50_MR_TMOUS_3.24.531.3_Radio_4A.21.3263.03_10.38m.1157.04_release_336982_signed_2_decrypted.zip. My version in phone is 7.18.531.35. I don't know how to check the version in the zip file. But the flash fails, so this RUU is useless anyway.

3. I downloaded an exe: RUU_M7_UL_L50_SENSE60_MR_TMOUS_7.18.531.35_Radio_4T.35.3218.16_10.33Q.1718.01L_release_448809_signed_2.exe from HTC website. But I dont know how to push this to phone. When I double click the exe file, it launches an installer, but the installation is not finished.

From the discussion, I understand, I need RUU.zip for 7.18.531.35. But dont know where to get. I googled but could not find the same.

Is there no way we can load some other ROM in present condition?

Any help is appreciated.
Thanks in advance.

Paintsman.
 
Hadron said:
You are sure this RUU is a good download (you checked the md5sum) and is at least as new as your phone's firmware (since it won't let you downgrade the firmware using an RUU)? And that it's an official RUU, not some other zip (anything other than a full official RUU will produce a signature verification error).

If you have the RUU as a zip then have you made sure it's in RUU mode before you tried to flash it? Use

fastboot oem rebootRUU

before you try "fastboot flash zip". From memory that should give you a black screen with HTC in silvery letters, which is "RUU mode". "fastboot flash zip" won't work in ordinary fastboot mode.

Note that flashing an RUU this way is a two-stage process. The first time you do it it should just flash the hboot, then end with a message like:

"FAILED (remote: 90 hboot pre-update! please flush image again immediately)"

(Why they've never corrected that spelling mistake I don't know ;)). So if you see what looks like a successful hboot flash followed by that message, do what it says and repeat the "fastboot flash zip xxxx.zip" command. The second time it should take a lot longer, flash all the other partitions, and end with a lot of messages telling you it's succeeded. The progress bar on the phone screen should stop at ~90% - that's normal. The last bit is rebooting, but it stops rather than doing that automatically in case there are any errors during the flashing (to give you a chance to fix them). As long as there are no errors and the computer tells you it was successful you can then

fastboot reboot-bootloader

and it should complete.
Click to expand...
Hi Hadron,

Continuing my previous post, I now understand the unlock token command is not unlocking the the bootloader. At fastboot, I get a response, unlock token check successfully; OKAY; but the phone still showns "RELOCKED" status.

Any thoughts?

Best,
Paintsman
 
If you are trying to run an RUU then actually you need the bootloader to be locked. Unlocking will only help if you are installing a custom recovery.

The .exe RUU you have has a better chance of working. It looks like the zip one is too old. You don't push the .exe to the phone, you connect the phone to a PC and run the .exe on the PC (it then does the flashing).

There is also a way to extract the RUU zip from the .exe, but it requires running the .exe at least through the first couple of steps. This XDA thread has some information on it (see first post and post 7) - it's a bit old but I don't think that the way RUUs work has really changed.
 
Hadron said:
If you are trying to run an RUU then actually you need the bootloader to be locked. Unlocking will only help if you are installing a custom recovery.

The .exe RUU you have has a better chance of working. It looks like the zip one is too old. You don't push the .exe to the phone, you connect the phone to a PC and run the .exe on the PC (it then does the flashing).

There is also a way to extract the RUU zip from the .exe, but it requires running the .exe at least through the first couple of steps. This XDA thread has some information on it (see first post and post 7) - it's a bit old but I don't think that the way RUUs work has really changed.
Click to expand...

Hi Hadrian,

Thanks for the revert. The XDA Thread looks promising. I will try that over next weekend, and keep you posted. In the meanwhile, is there someway we can unlock the bootloader in the present status?
 
You must log in or register to reply here.
Back
Top Bottom