Database Develop

M7 stuck on recovery after relock

Hi guys,
I've been trying to reset my One back to stock and I've accidentally got it stuck in recovery after I reclocked it with the All-in-one toolkit. Every time I restart it won't load Android and instead just goes to recovery.
I'm on Orange UK, HBOOT 1.44 and fastboot gives me:
(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.401.13
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4135mV
(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.039s
Please help I'm really stuck here!

Ok I've unlocked the phone again and now I can boot it up normally.... Can anyone help me with how to go back to stock? I don't want to mess it up again.
I'm running Android Revolution HD 20.2 Android 4.3, Sense 5.0

You can't boot locked with a custom recovery. That was your problem. Just relock and run a RUU right then and there.

iElvis said:
You can't boot locked with a custom recovery. That was your problem. Just relock and run a RUU right then and there.
Click to expand...
Click to collapse
I've found a few RUU's with the right baseband 4A.14.3250.13, but can only find 1.29.401.2 and 1.29.401.15. I tried to use these originally but it wouldn't do it... Any idea which one to go for? Thanks

gemuzz said:
I've found a few RUU's with the right baseband 4A.14.3250.13, but can only find 1.29.401.2 and 1.29.401.15. I tried to use these originally but it wouldn't do it... Any idea which one to go for? Thanks
Click to expand...
Click to collapse
You're on HTC__001, which is the generic European version. Those RUUs ought to work. What error message are you getting?

iElvis said:
You're on HTC__001, which is the generic European version. Those RUUs ought to work. What error message are you getting?
Click to expand...
Click to collapse
Right now I'm having trouble locking the bootloader before running the RUU. Everytime I try to lock I get
C:\Users\George\Desktop\fastboot>fastboot oem lock
...
FAILED (status read failed (Too many links))
finished. total time: -0.000s
Click to expand...
Click to collapse
And fastboot freezes so I have to do a hard reset.
I also tried to run the ruu in All-In-One Toolkit and got this
sending 'zip' (1010379 KB)...
OKAY [ 34.607s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 162.643s
Click to expand...
Click to collapse

Are you in bootloader or recovery when running fastboot oem lock?

iElvis said:
Are you in bootloader or recovery when running fastboot oem lock?
Click to expand...
Click to collapse
Bootloader in fastboot usb

gemuzz said:
Bootloader in fastboot usb
Click to expand...
Click to collapse
try issuing the command
fastboot oem relock
instead to lock your bootloader
but before relocking your bootloader
download your guru reset from here
install using the custom recovery (twrp/cwm)
during installation, install the stock recovery and do not root
after that, you should be back to to stock and all you need to do is relock your device
why dont you s-off your device so you can be 100% stock and would seem like your phone is out of the box?

Since you're still on hboot 1.44, I recommend you get S-Off using revone, also remove TAMPERED and put it LOCKED (using revone), then you can use the European RUU to downgrade and restore fully to 100% stock.

[Q] Htc One M7 Signature verify fail

Hello guys. I have a htc one m7 with me and I flashed a custom rom using clockwork mod. After flashing the custom rom, the phone got stuck at htc logo and it doesn't go into recovery anymore. I wiped cache using "fastboot wipe cache" but it didn't help. When I try to flash a different recovery, I always get this signature error:
Code:
target reported max download size of 1476849664 bytes
sending 'recovery' (9948 KB)...
OKAY [ 1.259s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.169s
I also have a picture of the bootloader screen attached. Thanks in advance
Sincerely, Djems

djems3 said:
Hello guys. I have a htc one m7 with me and I flashed a custom rom using clockwork mod. After flashing the custom rom, the phone got stuck at htc logo and it doesn't go into recovery anymore. I wiped cache using "fastboot wipe cache" but it didn't help. When I try to flash a different recovery, I always get this signature error:
Code:
target reported max download size of 1476849664 bytes
sending 'recovery' (9948 KB)...
OKAY [ 1.259s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.169s
I also have a picture of the bootloader screen attached. Thanks in advance
Sincerely, Djems
Click to expand...
Click to collapse
1- the command is: fastboot erase cache
2- you need to have bootloader UNLOCKED to be able to flash a custom recovery

nkk71 said:
1- the command is: fastboot erase cache
2- you need to have bootloader UNLOCKED to be able to flash a custom recovery
Click to expand...
Click to collapse
Yeah, sorry; I wrote the wrong command here. About the bootloader, is there a way to unlock it in fastboot because I have no way to go in recovery and the phone won't turn on.
Regards, Djems

djems3 said:
Yeah, sorry; I wrote the wrong command here. About the bootloader, is there a way to unlock it in fastboot because I have no way to go in recovery and the phone won't turn on.
Regards, Djems
Click to expand...
Click to collapse
You'll have to use HTCdev to unlock (especially since you're S-On, and no recovery)

nkk71 said:
You'll have to use HTCdev to unlock (especially since you're S-On, and no recovery)
Click to expand...
Click to collapse
same porblem here

djems3 said:
Hello guys. I have a htc one m7 with me and I flashed a custom rom using clockwork mod. After flashing the custom rom, the phone got stuck at htc logo and it doesn't go into recovery anymore. I wiped cache using "fastboot wipe cache" but it didn't help. When I try to flash a different recovery, I always get this signature error:
Code:
target reported max download size of 1476849664 bytes
sending 'recovery' (9948 KB)...
OKAY [ 1.259s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.169s
I also have a picture of the bootloader screen attached. Thanks in advance
Sincerely, Djems
Click to expand...
Click to collapse
I had this problem before
so you need to unlock your bootloder by "cmd" order and then your device will be restart and enter to recovery direct in this moment flash any custom rom and this step will be unlock your bootloder and allow you to do any thing

nkk71 said:
1- the command is: fastboot erase cache
2- you need to have bootloader UNLOCKED to be able to flash a custom recovery
Click to expand...
Click to collapse
my phone htc one m7 version
C:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT346W907135
(bootloader) imei: 354439057592281
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4277mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.063s
its got soft bricked....its doesn't starts.
I can't do s-off because unable to enable usb debugging ,,,please...
give me detailed steps to get my phone back to working.
Thanks in advance

ranjth1834 said:
my phone htc one m7 version
C:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT346W907135
(bootloader) imei: 354439057592281
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4277mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.063s
its got soft bricked....its doesn't starts.
I can't do s-off because unable to enable usb debugging ,,,please...
give me detailed steps to get my phone back to working.
Thanks in advance
Click to expand...
Click to collapse
So your bootloader unlocked? Device is Stock or with custom recovery? How did it soft brick. Failed OTA? or bad flash with no is installled?
Sent from my M7 Running ARHD 92.x

Danny201281 said:
So your bootloader unlocked? Device is Stock or with custom recovery? How did it soft brick. Failed OTA? or bad flash with no is installled?
Sent from my M7 Running ARHD 92.x
Click to expand...
Click to collapse
Its strucked in bootloop.....I did a mistake ,i didn't backup any data....
It stays in htc logo after loop.
---------- Post added at 11:04 AM ---------- Previous post was at 10:57 AM ----------
ranjth1834 said:
Its strucked in bootloop.....I did a mistake ,i didn't backup any data....
It stays in htc logo after loop.
Click to expand...
Click to collapse
btw thanks for the reply.....

ranjth1834 said:
Its strucked in bootloop.....I did a mistake ,i didn't backup any data....
It stays in htc logo after loop.
---------- Post added at 11:04 AM ---------- Previous post was at 10:57 AM ----------
btw thanks for the reply.....
Click to expand...
Click to collapse
Okay so you just need to get a Rom installed on the device. Here is the stock rom for your m7 https://www.androidfilehost.com/?fid=23501681358545274 you don't have to use this rom you can use any rom you choose. But if your still on the At&t network this will enable you to update via OTA. Otherwise use any rom you prefer.
There are a number of ways to get the rom to your internal storage. Probably re easiest is to flash TWRP 2.8.5.0. This will allow you to view your internal storage when connected to your pc in recovery. Then you can simply drag and drop the rom onto your device. Then install it with TWRP.
TWRP 2.8.5.0 does tend to hang while installing some roms though. So if you run into problems installing the rom try an older version of TWRP.
Or you can use adb to push the rom. This should work with any recovery. Put the rom in your fastboot folder and rename it something simple e.g - rom.zip
Boot the device to recovery and connect your usb cable. In a fastboot command prompt type
Code:
adb push rom.zip /sdcard
The command prompt will appear unresponsive until the push is complete (several minutes). When it's done install the rom with your recovery :good:
Sent from my SM-T230 using Tapatalk

I have done all the steps you have mentioned,,......
And flashing rom also succesfull...
but the problems remains same.
it stays in htc logo after loop/.....
please help to resolve this issue...
thanks for the reply.

ranjth1834 said:
I have done all the steps you have mentioned,,......
And flashing rom also succesfull...
but the problems remains same.
it stays in htc logo after loop/.....
please help to resolve this issue...
thanks for the reply.
Click to expand...
Click to collapse
Thanks for the suggestion...
I flashed gpe edition...it worked
Thank you very much...
I inserted sim ...but didnt detect the carrier...
:good::good:

my m7 failed while ota update...after many tries now it always says signature verification failed. its still s-on and official indian set...pls help

[Q] [HELP]HTC Boots straight into Fastboot

I have read countless threads, tried over a dozen roms, Unlocked and re-locked the bootloader countless times. Flashed recoveries to it more than enough number of times but I can get my phone to work.
My phone boots straight into hboot and there is no OS installed on it, thanks to my meddling with it a while back.
here are all the information I can get off the phone.
Tampered
Relocked
M7_WLS PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-1.01.20.0515
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
May 15 2014, 16:31:22.0
C:\Android\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0515
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:xxxxxxxxxx
(bootloader) imei: xxxxxxxxxx
(bootloader) meid: xxxxxxxxx
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4308mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.048s
This is what i get when I try to look bootloader
C:\Android\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 (Too many links))
finished. total time: 1.139s
This is what I get when writing twrp to it
C:\Android\sdk\platform-tools>fastboot flash recovery openrecovery-twrp-2.7.1.0-
m7wls.img
sending 'recovery' (9450 KB)...
OKAY [ 1.213s]
writing 'recovery'...
OKAY [ 0.805s]
finished. total time: 2.019s
But am unable to mount either data, system nor USB OTG, tried adb sideload too unsucessfull
I relock boot loader and try to RUU this rom Guru Reset M7 Sprint 1.29.651.10 get this response
C:\Android\sdk\platform-tools>fastboot flash zip firmware.zip
sending 'zip' (989298 KB)...
OKAY [ 42.241s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 140.397s
I have tried a lot of other roms too
Now am left thinking my device is useless now... If there is any hope for it, I will try it out..
Your help will be appreciated.
Thanks

pledgyno said:
I have read countless threads, tried over a dozen roms, Unlocked and re-locked the bootloader countless times. Flashed recoveries to it more than enough number of times but I can get my phone to work.
My phone boots straight into hboot and there is no OS installed on it, thanks to my meddling with it a while back.
here are all the information I can get off the phone.
Tampered
Relocked This has to be unlocked to flash recovery
C:\Android\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0515
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxremove
(bootloader) imei: xxxremovexxx
(bootloader) meid: remove
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
I relock boot loader and try to RUU this rom Guru Reset M7 Sprint 1.29.651.10 get this response
C:\Android\sdk\platform-tools>fastboot flash zip firmware.zip
sending 'zip' (989298 KB)...
OKAY [ 42.241s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 140.397s This is wrong !
I have tried a lot of other roms too
Now am left thinking my device is useless now... If there is any hope for it, I will try it out..
Your help will be appreciated.
Thanks
Click to expand...
Click to collapse
couple of things
your bootloader has to be unlocked to flash the recovery and rom
then in recovery install the Guru reset, it's a rom not a fastboot firmware
also edit your post to remove the serial and IMEI

clsA said:
couple of things
your bootloader has to be unlocked to flash the recovery and rom
then in recovery install the Guru reset, it's a rom not a fastboot firmware
also edit your post to remove the serial and IMEI
Click to expand...
Click to collapse
Thanks for your response and I have done the necessary edits to my post.
I unlocked bootloader before flashing both recovery and rom
and can you direct me to the rom that am supposed to flash to my device? if there are any info you require to find the rom i will provide

pledgyno said:
Thanks for your response and I have done the necessary edits to my post.
I unlocked bootloader before flashing both recovery and rom
and can you direct me to the rom that am supposed to flash to my device? if there are any info you require to find the rom i will provide
Click to expand...
Click to collapse
I would use this one
Sprint_One_Stock_Rooted_Deodexed_4.06.651.4.zip
http://qc1.androidfilehost.com/dl/J...rint_One_Stock_Rooted_Deodexed_4.06.651.4.zip
or this one
http://forum.xda-developers.com/showthread.php?t=2694171

138
clsA said:
I would use this one
Sprint_One_Stock_Rooted_Deodexed_4.06.651.4.zip
Click to expand...
Click to collapse
The link you sent me is dead, but am going to search for the file and try it out.
Thanks.
Will will update this thread after that
Update: Found the second listed file, am downloading now

pledgyno said:
The link you sent me is dead, but am going to search for the file and try it out.
Thanks.
Will will update this thread after that
Click to expand...
Click to collapse
new link ^^^up^^^

clsA said:
new link ^^^up^^^
Click to expand...
Click to collapse
I tried this rom and this is what i got
Sprint_One_Stock_Rooted_Deodexed_4.06.651.4
C:\Android\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.041s]
finished. total time: 0.041s
C:\Android\sdk\platform-tools>fastboot flash zip firmware.zip
sending 'zip' (1031149 KB)...
OKAY [ 44.015s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 146.275s

I tried this rom too
Bad Boyz Sprint ONE ROM 4.4.2 Sense 6 v1.0
No luck
C:\Android\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Android\sdk\platform-tools>fastboot flash zip firmware.zip
sending 'zip' (1151472 KB)...
OKAY [ 49.062s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 163.173s
Any other ideas?
Thanks

pledgyno said:
I tried this rom too
Bad Boyz Sprint ONE ROM 4.4.2 Sense 6 v1.0
No luck
C:\Android\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Android\sdk\platform-tools>fastboot flash zip firmware.zip
sending 'zip' (1151472 KB)...
OKAY [ 49.062s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 163.173s
Any other ideas?
Thanks
Click to expand...
Click to collapse
YOU FLASH THAT FILE FROM RECOVERY not fastboot. it's a rom zip

Aldo101t said:
YOU FLASH THAT FILE FROM RECOVERY not fastboot. it's a rom zip
Click to expand...
Click to collapse
am unable to get the file onto the phone so how do I do this?

pledgyno said:
am unable to get the file onto the phone so how do I do this?
Click to expand...
Click to collapse
read this: http://forum.xda-developers.com/showpost.php?p=54141500&postcount=2
you just need the part about pushing, don't download any of the files, they are not for your phone

Seanie280672 said:
read this: http://forum.xda-developers.com/showpost.php?p=54141500&postcount=2
you just need the part about pushing, don't download any of the files, they are not for your phone
Click to expand...
Click to collapse
When I type adb usb I get error device not found

pledgyno said:
When I type adb usb I get error device not found
Click to expand...
Click to collapse
where in that link does it say to type adb usb ? the command with the rom in the same folder as adb and fastboot on your computer, and your phone plugged in and on the main screen of recovery you type adb push (rom_name).zip /sdcard/

Seanie280672 said:
where in that link does it say to type adb usb ? the command with the rom in the same folder as adb and fastboot on your computer, and your phone plugged in and on the main screen of recovery you type adb push (rom_name).zip /sdcard/
Click to expand...
Click to collapse
I did exactly what you said and this is what i got
C:\Android\sdk\platform-tools>adb push firmware.zip /sdcard/
error: device not found

pledgyno said:
I did exactly what you said and this is what i got
C:\Android\sdk\platform-tools>adb push firmware.zip /sdcard/
error: device not found
Click to expand...
Click to collapse
you need to update your drivers and/r update your adb and fastboot, you can find a link to adb and fastboot on the page I linked before, and you can get your drivers by downloading HTC sync manager and then install, once installed, remove htc sync just leaving the drivers.

Seanie280672 said:
you need to update your drivers and/r update your adb and fastboot, you can find a link to adb and fastboot on the page I linked before, and you can get your drivers by downloading HTC sync manager and then install, once installed, remove htc sync just leaving the drivers.
Click to expand...
Click to collapse
Am downloading the HTC sync manager, when done i will try once more

I got it to work..
I started all over again
Unlocked the bootloader
installed twrp
installed this adb driver http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi
I proceeded with adb sideload of Bad Boyz Sprint ONE ROM 4.4.2 Sense 6 v1.0
And everything was perfect
I owe a lot of thanks clsA, Aldo101t and Seanie280672

I have the same issue
I cant seem to install my rom zip, done adb push, and adb sideload. Everytime I try and install the rom the phone reboots and file is missing from sdcard.
pledgyno said:
I got it to work..
I started all over again
Unlocked the bootloader
installed twrp
installed this adb driver
I proceeded with adb sideload of Bad Boyz Sprint ONE ROM 4.4.2 Sense 6 v1.0
And everything was perfect
I owe a lot of thanks clsA, Aldo101t and Seanie280672
Click to expand...
Click to collapse

HELP! One mini 2 can't unlock bootloader doesn't show splash screen

Okay lots of issues hopefully one easy fix,
I have had a HOM2 given to me to fix for my friend so just want it back to stock , it has no radios it mentions invalid_ver_* , same for another option, the bootloader is LOCKED here is my getvar info
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.19.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH466WR01102
(bootloader) imei: 35***********
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: mem_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P8B20000
(bootloader) cidnum: HTC__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: be7179e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
, its bootlooping into bootloader, so my first thought was unlock bootloader flash recovery and side load a rom, play with radios and such after, but trying to unlock the bootloader doesn't work I've tried HTC dev twice to check the unlock code but it pushes it to the device and claims it was successful I get this;
**UNLOCK CODE***
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.109s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.016s]
finished. total time: 0.125ss
tried different USB cables and ports but every time I try I don't get the unlock splash screen asking me to unlock, so I went through the forums and tried a few things found that clearing cache or and data gives me
**CLEAR CACHE***
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 5.038ss
I tried flashing recovery (just for kicks) I get
***SEND RECOVERY***
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery-twrp-2.8.5.0.img
sending 'recovery' (11796 KB)...
OKAY [ 10.472s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 11.316sss
Which I guess is to be expected,
I then found an RUU for the device and was thankful the unlocking didn't work so I was still locked, but every one I try to download is corrupt? Anybody have a working link for a UK ee (orange) radios and firmware? And do I have the right idea with this, download, rename, chuck it on an sdcard and bootloader should find it automatically?
Thanks for any advice

martipello86 said:
Okay lots of issues hopefully one easy fix,
I have had a HOM2 given to me to fix for my friend so just want it back to stock , it has no radios it mentions invalid_ver_* , same for another option, the bootloader is LOCKED
Click to expand...
Click to collapse
Since the phone was given to you, Are you using an original HTC cable???? you need that for any flashing to work.

Yes I have an original HTC cable,

martipello86 said:
Yes I have an original HTC cable,
Click to expand...
Click to collapse
kativiti said:
Since the phone was given to you, Are you using an original HTC cable???? you need that for any flashing to work.
Click to expand...
Click to collapse
I have the original cable, just does not want to work, and the RUU says its corrupt when I try to put it on the SD card

kativiti said:
Since the phone was given to you, Are you using an original HTC cable???? you need that for any flashing to work.
Click to expand...
Click to collapse
i found a way to get the ruu onto the sdcard by uploading the file to dropbox and redownloading it straight to the memory card then stuck it in the phone tried an orange ruu it gets half way through updating then stops and spits out a message to say its not the right cid so i got the wwe version that looks like itll work but then fails and tells me 'MAIN VERSION IS OLDER' update failed.
ANY IDEAS WELCOME!!!!!!!

HTC One M7 - Bricked?

Hey guys.
I was wondering if anyone could take some time and help figure out what's wrong with my Htc one!
So my new phone broke and so i went back to my One that i haven't used in ages.
Anyways it was alredy rooted with S-Off and first thing i was trying todo was to install TWRP and a new rom.
After i installed twrp and rebooted the phone and upon start i sent me directly in to the "power off + Volume down" menu and i tried to enter Recovery.
All i get is "Active cmdline overflow! (2169 Bytes)" then nothing more.
So i tried some fastboot commands and this is what i get from
Fastboot devices ҟÀü«/륑-1ý}ËÙ fastboot
I reckoning something is wrong here because the name has never shown like this before.
If i try adb devices i get nothing.
So i started to belive that maybe the cable was ****ed and now i almost tried 7 diffrent cables and all of them is giving me the same message.
I tried a diffrent computer, i tried in windows 10 and now im in Ubuntu 16.04 and still cant get adb to show the device.
This is what i get from "fastboot getvar all"
HTML:
sudo 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:
(bootloader) version-misc: UNKNOWN SHIP S-OFF
(bootloader) serialno: ҟ���/륑-1�}��
(bootloader) imei: ****************** <---------- CHANGED THIS ONE TO STARS!
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: �
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3776mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-01dc707e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
Anyway the (bootloader) serialno: ҟ���/륑-1�}�� and (bootloader) modelid: � dosent look good right ?
Well i did follow this guide "https://forum.xda-developers.com/showthread.php?t=2739126" and i can install twrp and everything but i cant enter it and the adb commands further in the guide dosent work because adb wont list the phone.
I also tried:
HTML:
sudo fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.039s]
finished. total time: 0.039s
sudo fastboot flash zip 1.29.401.12_hboot_1.44.zip
target reported max download size of 1514139648 bytes
sending 'zip' (501 KB)...
OKAY [ 0.243s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 0.644s
And there's something wrong with the mode id
What is my option, is the phone ****ed or is it possible to fix it ?
Thanks in advanced!

Have you tried to flash stock recovery or RUU?

JB_ said:
Hey guys.
I was wondering if anyone could take some time and help figure out what's wrong with my Htc one!
So my new phone broke and so i went back to my One that i haven't used in ages.
Anyways it was alredy rooted with S-Off and first thing i was trying todo was to install TWRP and a new rom.
After i installed twrp and rebooted the phone and upon start i sent me directly in to the "power off + Volume down" menu and i tried to enter Recovery.
All i get is "Active cmdline overflow! (2169 Bytes)" then nothing more.
So i tried some fastboot commands and this is what i get from
Fastboot devices ҟÀü«/륑-1ý}ËÙ fastboot
I reckoning something is wrong here because the name has never shown like this before.
If i try adb devices i get nothing.
So i started to belive that maybe the cable was ****ed and now i almost tried 7 diffrent cables and all of them is giving me the same message.
I tried a diffrent computer, i tried in windows 10 and now im in Ubuntu 16.04 and still cant get adb to show the device.
This is what i get from "fastboot getvar all"
HTML:
sudo 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:
(bootloader) version-misc: UNKNOWN SHIP S-OFF
(bootloader) serialno: ҟ���/륑-1�}��
(bootloader) imei: ****************** <---------- CHANGED THIS ONE TO STARS!
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: �
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3776mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-01dc707e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
Anyway the (bootloader) serialno: ҟ���/륑-1�}�� and (bootloader) modelid: � dosent look good right ?
Well i did follow this guide "https://forum.xda-developers.com/showthread.php?t=2739126" and i can install twrp and everything but i cant enter it and the adb commands further in the guide dosent work because adb wont list the phone.
I also tried:
HTML:
sudo fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.039s]
finished. total time: 0.039s
sudo fastboot flash zip 1.29.401.12_hboot_1.44.zip
target reported max download size of 1514139648 bytes
sending 'zip' (501 KB)...
OKAY [ 0.243s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 0.644s
And there's something wrong with the mode id
What is my option, is the phone ****ed or is it possible to fix it ?
Thanks in advanced!
Click to expand...
Click to collapse
What roms did you flashed (post a link) ? Active cmdline overflow is caused by a corrupted misc partition, most of the time because the user flashed a rom for another device than the m7. During the installation, the updater script of that rom flash images to wrong partitions (since all phone models have a different partition layout). Some partitions are unique to each m7 and if they get corrupted, a simple ruu flash will not solve your problem.
Your adb problem is most likely a driver issue. Make sure you have the latest drivers from HTC (those that are bundled with HTCSync) and try again. The only way out of this is to make p19 healthy again by following that guide you linked (if it was caused by an incompatible rom flash...waiting for your link).
Btw do not attempt to downgrade to hboot 1.44 if you're using windows 8/10 or you'll also loose fastboot connectivity.

alray said:
What roms did you flashed (post a link) ? Active cmdline overflow is caused by a corrupted misc partition, most of the time because the user flashed a rom for another device than the m7. During the installation, the updater script of that rom flash images to wrong partitions (since all phone models have a different partition layout). Some partitions are unique to each m7 and if they get corrupted, a simple ruu flash will not solve your problem.
Your adb problem is most likely a driver issue. Make sure you have the latest drivers from HTC (those that are bundled with HTCSync) and try again. The only way out of this is to make p19 healthy again by following that guide you linked (if it was caused by an incompatible rom flash...waiting for your link).
Btw do not attempt to downgrade to hboot 1.44 if you're using windows 8/10 or you'll also loose fastboot connectivity.
Click to expand...
Click to collapse
Well as I want to remember it I don't think I have flashed a rom yet, I never got that far I just tried to flash twrp 2.8.4.0.
Do i even need drivers in Ubuntu ? I was under the influence that I didn't need any.

JIMSHERIKO said:
Have you tried to flash stock recovery or RUU?
Click to expand...
Click to collapse
Well if I understand it right when I try to flash a RUU it just says unknown modelid and I think because it's corrupted or something. :/

JB_ said:
Do i even need drivers in Ubuntu ? I was under the influence that I didn't need any.
Click to expand...
Click to collapse
No you don't, only on windows, sorry. ADB should work fine from twrp and no drivers required on ubuntu, adb will not work from the bootloader.

alray said:
No you don't, only on windows, sorry. ADB should work fine from twrp and no drivers required on ubuntu, adb will not work from the bootloader.
Click to expand...
Click to collapse
Ah so i need to get TWRP up and running for adb to work then.
Well looks like i got my awnser then. Thank you for your time!