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

Help Need help here ( HTC ONE M7 bootloop )

Hello everyone.. i have an htc one m7 which is stuck in a bootloop.On the htc logo. image ( http://postimg.org/image/dq6t5w9lz/ )
I've tried to flash the phone using this guide ( http://www.droid-now.com/2015/06/tutorial-unlock-root-flash-custom-rom-on-htc-one-m7/ )but can't unlock the bootloader using fastboot cause the usb debugging is off
Tried to flash recovery also but nothing


C:\adb>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.231s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.354s


Tried fastboot,htcdev,adb push,htc one toolkit,windroid universal toolkit but nothing works..

Here some informations , hope that helps..

http://postimg.org/image/4broumenb/

C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.21.707.105
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Remouved
(bootloader) imei: Removed
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 4053mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.112s

What to do???

Thanks
DSC_0029.JPG

DSC_0030.JPG
DSC_0030.JPG
DSC_0030.JPG
 
You can't flash TWRP until you unlock the bootloader.

Unlocking the bootloader via fastboot and HTCdev.com has *nothing* to do with USB debugging being on or off.

Follow the instructions at HTCdev.com to unlock your bootloader.

Forget adb, forget toolkits, just focus on HTCdev.com - it's not difficult.

Unlock the bootloader.

Install TWRP.

Make a backup in TWRP before you change or flash anything else. (All of the know it all blogs and toolkits skip this step and it screws you if you don't do it.)

Then set about rooting or whatever else you're trying to do.
 
You can't flash TWRP until you unlock the bootloader.

Unlocking the bootloader via fastboot and HTCdev.com has *nothing* to do with USB debugging being on or off.

Follow the instructions at HTCdev.com to unlock your bootloader.

Forget adb, forget toolkits, just focus on HTCdev.com - it's not difficult.

Unlock the bootloader.

Install TWRP.

Make a backup in TWRP before you change or flash anything else. (All of the know it all blogs and toolkits skip this step and it screws you if you don't do it.)

Then set about rooting or whatever else you're trying to do.



I tried but when the phone reboot it stuck on the logo again...
 
Thanks for replying.

I've followed all the instructions on the htcdev website till i got the black screen with yes or no to unlock the bootloader on the phone . This
IMG_20150820_054714.jpg


Then when i highlight yes and select it by pressing the power button the phone vibrate and it bring me back to the htc logo .seem it doesn't reboot at all.


What to do now??

Thanks
 
I'm concerned about the bootloader commit number.

Was this phone bought used recently?

Was it working correctly before you started all this?
 
Follow the instructions *exactly* from here -

http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944

Find your download for version 7.21.707.5 and CID HTC__044 - it's there.

You can see that I matched those from your getvar all results.

Make 100% sure that you have the right version, that you have the htc_fastboot indicated by the instructions, and just follow the instructions.

Make sure that your phone has a 50% charge or better before trying it.

If anything can fix your phone, it's that.
 
Follow the instructions *exactly* from here -

http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944

Find your download for version 7.21.707.5 and CID HTC__044 - it's there.

You can see that I matched those from your getvar all results.

Make 100% sure that you have the right version, that you have the htc_fastboot indicated by the instructions, and just follow the instructions.

Make sure that your phone has a 50% charge or better before trying it.

If anything can fix your phone, it's that.

Alright will try it.

Thanks
 
Sorry but the cid for version7.21.707.105 does not match. On the website the cid is htc_ _ 38 and mine is htc _ _ 44. Is it fine?
No, it's not fine at all.

Match the CID - you can see I recommended the later version number (point 5 is greater than point 105) based on your getvar results.

1440049241198.jpg

It should be OK.
 
Last edited:
Me again...




htc_fastboot oem rebootRUU
ok

but when i tried to flash the zip file using the command line below its says failed.

htc_fastboot flash zip RUU.zip

Capture.PNG


any idea ?
 
Hmmm...

If someone gained s-off to the bootloader and followed the very bad advice to return it to s-on, or much worse, the bad advice to cover it up by editing the bootloader, then the phone may be in an undetermined state and beyond hope.

Try this and hope for the best - go to normal FASTBOOT USB mode and say

fastboot oem lock

If it says it's successful, try the RUU flash procedure again.

After that, I'm completely out of ideas.
 
Hmmm...

If someone gained s-off to the bootloader and followed the very bad advice to return it to s-on, or much worse, the bad advice to cover it up by editing the bootloader, then the phone may be in an undetermined state and beyond hope.

Try this and hope for the best - go to normal FASTBOOT USB mode and say

fastboot oem lock

If it says it's successful, try the RUU flash procedure again.

After that, I'm completely out of ideas.

already tried .. it says its already locked..
do you think its a hardware problem??
 
The bootloader and/or recovery is scrambled.

You'll see in your getvar output that it says security is on, otherwise known as s-on.

If that's true the phone would have protected itself from a bad RUU flash attempt.

So that takes me back to wondering if s-on/s-off/s-on was tampered with before.

Or - it's just on its way to a more complete hardware failure.

I've seen Motorolas do what yours is doing - never thought I'd see an HTC do that, and as you can guess, I've done a lot with HTCs.
 
The bootloader and/or recovery is scrambled.

You'll see in your getvar output that it says security is on, otherwise known as s-on.

If that's true the phone would have protected itself from a bad RUU flash attempt.

So that takes me back to wondering if s-on/s-off/s-on was tampered with before.

Or - it's just on its way to a more complete hardware failure.

I've seen Motorolas do what yours is doing - never thought I'd see an HTC do that, and as you can guess, I've done a lot with HTCs.

OMG, their is nothing i can do then... :(
 
Back
Top Bottom