Database Develop

[Q] Help! No radios installed at all

I mistakenly wiped the htc one m7 trying to install a rom based off kit kat I believe. Well, now I have no radios listed at all on the boot screen. I followed the tutorial on the forum for using fast boot to reflash the boot I believe. Process involved an older boot, which didn't flash with an error. I successfully flashed the latest 4.06 version of boot which was successful.
The thread went on to say I should start with the stock rom. Couldn't get it to load with adb side loader or fast boot flash zip name.zip. I have been able to successfully side load viper one, the latest version, and I have the latest version of terp as the recovery.
My problem is the phone will stay on no more than 15 sec. Before it reboots. I cannot see it in my computer although it shows up in device manager. I installed the latest driver from a thread on here.
Seems my options are fast boot and side loader, but I get a signed verification fail when I try to fast boot the radio , also taken from a radio thread here. I'm pretty sure I need s off which is the only thing left. Would this cause the phone to reboot continuously?
I'm tired of messing with it is it time to trash it or is this fixable? Thanks in advance and I'll give any info you guys need to help.

Latest Sprint Radio

from fastboot getvar
C:\Users\Tai\Desktop\HTC One Backup\Restore Data\Others>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA3C4S903734
(bootloader) imei: 990004288501756
(bootloader) meid: 99000428850175
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3796mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
C:\Users\Tai\Desktop\HTC One Backup\Restore Data\Others>
I dont know if this helps or not.

This is what I get from fastboot when I try to load the radio...
C:\Users\Tai\Desktop\HTC One Backup\Restore Data\Others>fastboot flash radio Rad
io_HTC.zip
sending 'radio' (18554 KB)...
OKAY [ 2.250s]
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 5.500s
C:\Users\Tai\Desktop\HTC One Backup\Restore Data\Others>
This is where I was last night. After searching on the threads, it seems that flashing hboot is ok, but the radios cannot be flashed without S-OFF. At this point what are my options as far as getting this radio in.
It did this auto reboot every 10-15 sec. the minute i flashed the improper rom. Again I've tried fixing with thread guidance on here for softbricking a Sprint device by flashing an ATT, etc. device.
Please help. Are there people you can call to undo damage like this or are you stuck fixing yourself?
Thanks

tpan1983 said:
This is what I get from fastboot when I try to load the radio...
C:\Users\Tai\Desktop\HTC One Backup\Restore Data\Others>fastboot flash radio Rad
io_HTC.zip
sending 'radio' (18554 KB)...
OKAY [ 2.250s]
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 5.500s
C:\Users\Tai\Desktop\HTC One Backup\Restore Data\Others>
This is where I was last night. After searching on the threads, it seems that flashing hboot is ok, but the radios cannot be flashed without S-OFF. At this point what are my options as far as getting this radio in.
It did this auto reboot every 10-15 sec. the minute i flashed the improper rom. Again I've tried fixing with thread guidance on here for softbricking a Sprint device by flashing an ATT, etc. device.
Please help. Are there people you can call to undo damage like this or are you stuck fixing yourself?
Thanks
Click to expand...
Click to collapse
if you are using fastboot the radio has to be an image file, not a zip, or a boot.img, or get a radio zip file and flash from recovery.

54594563 3255
Aldo101t said:
if you are using fastboot the radio has to be an image file, not a zip, or a boot.img, or get a radio zip file and flash from recovery.
Click to expand...
Click to collapse
Woops typo. So, what I was doing was opening the .zip, and there are two files. A .inf I believe, and the image file (which Windows recognizes as such). I'm copying and pasting this file in the folder with the tools and fastbooting the .img with the command
fastboot devices
I see the phone serial and fastboot
fastboot flash radio radio.img
I get the error I posted before...
I would like to explore flashing from recovery. Given my situation is this possible? Also, do the stock ROMs, the RUU I believe, does it have the radio installed?

The link BD Posted here are flashable zips for recovery install
Sent from my HTCONE using Tapatalk

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

Hi Guys
i think i really messed up my HTC one first of all here's the screen details on the boot loader
and I'm a complete noobie on android and this is phone is my frist android device
****UNLOCKED****
M7_UL PVT SHIP S-OFF RH
CID-HTC__044
HBOOT-1.57.0000
RADIO-4T.27.3218.14
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Apr 25 2014
PC: Windows 7 Ultimate
The story is I tried to root my device using this tutorial in youtube from zedomax
and it was a success without trouble,
So I tried to install a custom ROM ViperOne_6.2.0.zip
and its where everything got messed up when the installation returned an error during installation
I tried reinstalling and i think i wiped all the data on the storage including the backup using the TWRP wipe button including OS files
after several attempts i was able to re enter TWRP and/or CWP trying to install via Sideload command but failed
i cant load zip files via my PC too because my pc cant read/write the storage of my phone. (I installed USB drivers and phone is detectable on device manager)
now the bootloader have this error Active cmdline overflow! (1094 Bytes)
Since I'm a real newbie in android may I kindly ask a step-by-step instruction on how can i recover if possible from this trouble.
I would really appreciate everyone's help from this forum.

here's a guide to fix that active cmdline overflow, you messed up one of your partitions and your phone wont work until you fix that issue, you need to follow that guide to the letter, do not skip any parts, read it all first and understand it, if you get any of the commands wrong you could end up with a complete brick so copy and paste them.
http://forum.xda-developers.com/showthread.php?t=2739126

Thank you for the quick reply,
I tried to install "fastboot flash recovery twrp-recovery-2.7-m7-nobcb.img" on fastboot. It installed correctly
when I erased cache then rebooted the fast booth, the "Active cmdline overflow! (**** Bytes)" error was gone
but when i enter recovery, it reboots again to fastboot and the error reappears.
and the cycle repeats again.
I can't get past this
one more thing...I noticed that you used a different adb C:\ADB3> is there a version 3 or is it just a folder name?
when I try to detect device in fastboot:
D:\HTCOne recover\HTCOneRoot>fastboot devices
FA32GW9**** fastboot
but when i try to use the same command on adb:
D:\HTCOne recover\HTCOneRoot>adb devices
List of devices attached
nothing on the list. And ADB commands don't work because it can't recognize the device.
I really need your help. Thanks in Advance
I would like to add that I can't access the phone storage through my PC
one more thing...
how would I know if i got these?
from the guide
"Well you need adb commands, root and busybox... which are only available in a custom recovery or a rooted ROM (with USB debugging enabled)"
1. adb commands
2. root and
3. busybox
4. custom recovery or a rooted ROM (with USB debugging enabled)
which are only available in a custom recovery or a rooted ROM (with USB debugging enabled)"

WilmanB said:
Thank you for the quick reply,
I tried to install "fastboot flash recovery twrp-recovery-2.7-m7-nobcb.img" on fastboot. It installed correctly
when I erased cache then rebooted the fast booth, the "Active cmdline overflow! (**** Bytes)" error was gone
but when i enter recovery, it reboots again to fastboot and the error reappears.
and the cycle repeats again.
I can't get past this
one more thing...I noticed that you used a different adb C:\ADB3> is there a version 3 or is it just a folder name?
Click to expand...
Click to collapse
have you restored mmcblk0p19 like said in the guide?
but when i try to use the same command on adb:
D:\HTCOne recover\HTCOneRoot>adb devices
List of devices attached
nothing on the list.
and ADB commands don't work because it can't recognize the device.
I really need your help. Thanks in Advance
I would like to add that I can't access the phone storage through my PC
Click to expand...
Click to collapse
adb only works from custom recovery or from a booted rom with usb debug on. adb will not works from bootloader and you will not see phone storage from bootloader.

alray said:
have you restored mmcblk0p19 like said in the guide?
Click to expand...
Click to collapse
but adb does not recognize my phone so i cant restore mmcblk0p1 like it says on the instruction
adb wont respond to any adb commands
but fastboot is responsive
"adb only works from custom recovery or from a booted rom with usb debug on."
how do i do this? How will I know if I'm running in a booted ROM with USB debug On?
I install "fastboot flash recovery twrp-recovery-2.7-m7-nobcb.img" on fastboot. It installed correctly but it wont enter recovery mode

First of all you will know if you are running a booted Rom if your phone boots up lol, in your case, yours doesn't, so ignore this and usb debugging.
Fastboot commands only work in bootloader.
Adb commands for you will only work inside recovery.
You must get into recovery to use adb to fix your phone, the reason you apprear to not be able to get in is because of your hboot version, you need to downgrade it, however I leave this completely in your hands and won't be held responsible if you brick your phone, simply, if you flash even the slightest wrong hboot, you'll have a brick, read the rest of that thread after the instructions, your same issue is in that thread.

WilmanB said:
but adb does not recognize my phone so i cant restore mmcblk0p1 like it says on the instruction
adb wont respond to any adb commands
but fastboot is responsive
Click to expand...
Click to collapse
ADB commands = Usable from custom recovery mode or from a normally booted phone (not your case)
FASTBOOT commands = Usable only from bootloader, where you currently are. You can't use adb here
"adb only works from custom recovery or from a booted rom with usb debug on."
how do i do this? How will I know if I'm running in a booted ROM with USB debug On?
Click to expand...
Click to collapse
flash the nobcb verison of twrp, boot in recovery and then you'll be able to use ADB commands.
I install "fastboot flash recovery twrp-recovery-2.7-m7-nobcb.img" on fastboot. It installed correctly but it wont enter recovery mode
Click to expand...
Click to collapse
Code:
fastboot flash recovery twrp-recovery-2.7-m7-nobcb.img
fastboot erase cache
fastboot reboot-bootloader
then try to boot in recovery mode again.
if you are still not able to boot the nobcb recovery, better to ask in the thread Seanie280672 linked you

Wow, thank you all very much. I am now able to enter recovery mode using HBOOT -1.44.0000 through CWT recovery
no more cmdline overflow.
and I'm done restoring mmcblk0p19
now i just need to find the correct RUU to flash I need your help again guys? I'm not really sure what RUU to flash or what to do next from here

WilmanB said:
Wow, thank you all very much. I am now able to enter recovery mode using HBOOT -1.44.0000 through CWT recovery
no more cmdline overflow.
and I'm done restoring mmcblk0p19
now i just need to find the correct RUU to flash I need your help again guys? I'm not really sure what RUU to flash or what to do next from here
Click to expand...
Click to collapse
post the output of "fastboot getvar all" excluding imei and serialno and we'll be able to tell you what ruu you can use.

alray said:
post the output of "fastboot getvar all" excluding imei and serialno and we'll be able to tell you what ruu you can use.
Click to expand...
Click to collapse
@elray
Thanks for replying these are what i got from the getvar command
version: 0.5
version-bootloader: 1.54.0000
version-baseband: 4A.17.3250.14
version-cpld: None
version-microp: None
version-main: 2.24.707.1
version-misc: PVT SHIP S-OFF
serialno: FA32GW9*****
imei: 3558590500*****
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0714000
cidnum: HTC__044
battery-status: good
battery-voltage: 4318mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-d16dc66985
hbootpreupdate: 11
gencheckpt: 0
I wish you can locate a proper RUU for my device.
I would also like to ask if it is possible to install custom ROM on my phone.
I tried to install the ViperOne 6.2.0 and Android Revolution HD 71.1 but it's both unsuccessful
now I'm stuck on Android 4.2.2 in HTC Sense 5 because i can't install new updates to KitKat and Sense 6

WilmanB said:
@elray
Thanks for replying these are what i got from the getvar command
version: 0.5
version-bootloader: 1.54.0000
version-baseband: 4A.17.3250.14
version-cpld: None
version-microp: None
version-main: 2.24.707.1
version-misc: PVT SHIP S-OFF
serialno: FA32GW9*****
imei: 3558590500*****
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0714000
cidnum: HTC__044
battery-status: good
battery-voltage: 4318mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-d16dc66985
hbootpreupdate: 11
gencheckpt: 0
I wish you can locate a proper RUU for my device.
I would also like to ask if it is possible to install custom ROM on my phone.
I tried to install the ViperOne 6.2.0 and Android Revolution HD 71.1 but it's both unsuccessful
now I'm stuck on Android 4.2.2 in HTC Sense 5 because i can't install new updates to KitKat and Sense 6
Click to expand...
Click to collapse
http://www.htc1guru.com/dld/ruu-zip-m7_u_asia_wwe_custom_guruu_3-63-707-4-zip/
or any other ruu if you change your mid/cid

alray said:
http://www.htc1guru.com/dld/ruu-zip-m7_u_asia_wwe_custom_guruu_3-63-707-4-zip/
or any other ruu if you change your mid/cid
Click to expand...
Click to collapse
Sorry @alray but the file in your link returned an error while flashing
3x to flash without rebooting, returned this error:
D:\HTCOne recover\HTCOneRoot>fastboot flash zip RUU.zip
sending 'zip' (1206124 KB)...
OKAY [ 46.103s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 46.549s
D:\HTCOne recover\HTCOneRoot>fastboot flash zip RUU.zip
sending 'zip' (1206124 KB)...
OKAY [ 46.183s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 46.610s
D:\HTCOne recover\HTCOneRoot>fastboot flash zip RUU.zip
sending 'zip' (1206124 KB)...
OKAY [ 46.112s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 46.540s
D:\HTCOne recover\HTCOneRoot>fastboot reboot
rebooting...
finished. total time: 0.038s
I think the RUU file is incompatible with my device that's why it wont proceed.
this is the filename:
RUU Zip M7_U_Asia_WWE_Custom_GuRUU_3.63.707.4.zip
Android.txt
modelid: PN0711000
modelid: PN0714000
cidnum: HTC__044
cidnum: HTC__038
mainver: 3.63.707.4
btype:1
aareport:1
DelCache:1
hbootpreupdate:3

WilmanB said:
Sorry @alray but the file in your link returned an error while flashing
3x to flash without rebooting, returned this error:
D:\HTCOne recover\HTCOneRoot>fastboot flash zip RUU.zip
sending 'zip' (1206124 KB)...
OKAY [ 46.103s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 46.549s
D:\HTCOne recover\HTCOneRoot>fastboot flash zip RUU.zip
sending 'zip' (1206124 KB)...
OKAY [ 46.183s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 46.610s
D:\HTCOne recover\HTCOneRoot>fastboot flash zip RUU.zip
sending 'zip' (1206124 KB)...
OKAY [ 46.112s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 46.540s
D:\HTCOne recover\HTCOneRoot>fastboot reboot
rebooting...
finished. total time: 0.038s
I think the RUU file is incompatible with my device that's why it wont proceed.
this is the filename:
RUU Zip M7_U_Asia_WWE_Custom_GuRUU_3.63.707.4.zip
Android.txt
modelid: PN0711000
modelid: PN0714000
cidnum: HTC__044
cidnum: HTC__038
mainver: 3.63.707.4
btype:1
aareport:1
DelCache:1
hbootpreupdate:3
Click to expand...
Click to collapse
was your phone in ruu mode?
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip
fastboot reboot

alray said:
was your phone in ruu mode?
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip
fastboot reboot
Click to expand...
Click to collapse
yes sir it was in ruu mode. the one with green HTC logo and black background.

WilmanB said:
yes sir it was in ruu mode. the one with green HTC logo and black background.
Click to expand...
Click to collapse
try this one: http://www.htc1guru.com/dld/ruu_m7_...0-13_10-33-1150-01_release_311678_signed-exe/
otherwise, change your mid and cid and try to flash another version ruu.

[Q] Soft-bricked Phone Issue

Hello all,
I am having trouble trying to restore my AT&T HTC One M7 back to being functional again. The phone was soft-bricked "somehow" by my ex-wife and have been trying to restore it for the past few months. I have done alot of searching and tried many options but nothing is working so far.
The phone had never been rooted and has no custom roms on it. After it was soft-bricked, I was able to get it unlocked at one point, but stupidly enough I followed some wrong advice on how to proceed from there and relocked the phone. Now I cannot unlock it again in order to try to put TWRP or recovery on the phone to get it working again.
So far I have tried the following approaches to this issue:
1)I tried going through the HTC dev site steps to get a unlock code, but nothing happens on the phone screen even after getting a successful notice in CMD screen. (I tried both the original code and getting a new code)
2)Every time I try to flash it on there also I get signature failures in CMD and nothing happens on the phone.
3)I also tried running a stock RUU app, but after the process beings the final update, I get a usb cable error saying it is unplugged when it is not.
Thanks in advance for any suggestions.

To me that sounds like it might be a corrupt boot loader. You could also try to gain s-off and flash a recovery that way. Rumrunner works well: http://rumrunner.us
If you can s-off it then you can flash an hboot image which should fix the issue. Just go to the hboot section on the rumrunner website. Then install TWRP etc....

Your bootloader needs to be locked in order to run the RUU. Boot to bootloader screen and make sure you are in Fastboot. If on Windows, ensure you have adb installed correctly. Open command prompt on Windows with phone connected and type 'Fastboot relock oem'. This should relock the bootloader. From there, you need to make sure you have the correct RUU for your firmware, boot the phone to the main bootloader screen and run the RUU. Let me know if you need more details.

MarkBell said:
Your bootloader needs to be locked in order to run the RUU. Boot to bootloader screen and make sure you are in Fastboot. If on Windows, ensure you have adb installed correctly. Open command prompt on Windows with phone connected and type 'Fastboot relock oem'. This should relock the bootloader. From there, you need to make sure you have the correct RUU for your firmware, boot the phone to the main bootloader screen and run the RUU. Let me know if you need more details.
Click to expand...
Click to collapse
Thanks for sticking around and helping others
The correct command to lock the bootloader is fastboot oem lock. but he says he can't unlock his bootloader so I doubt that's the problem.
@Squirrelsquisher what is the software version on the phone
3.xx.502.x / 4.xx.502.x / 5.xx.502.x ?
you can use a fastboot command to get the info
fastboot getvar all
you can post the result here or just give me your version number as you have AT&T I already know you MID and CID

I love Xda, and plan to become more involved. My thinking is he is likely flashing the wrong RUU. If there is a mistake to be made, I've made it.
---------- Post added at 07:47 PM ---------- Previous post was at 07:37 PM ----------
And sorry about screwing up that Fastboot command. Lol. Posting too early in the day I guess. Lol. It is indeed Fastboot oem lock. I skimmed over the fact he can't unlock the bootloader. Sorry.

clsA said:
Thanks for sticking around and helping others
The correct command to lock the bootloader is fastboot oem lock. but he says he can't unlock his bootloader so I doubt that's the problem.
@Squirrelsquisher what is the software version on the phone
3.xx.502.x / 4.xx.502.x / 5.xx.502.x ?
you can use a fastboot command to get the info
fastboot getvar all
you can post the result here or just give me your version number as you have AT&T I already know you MID and CID
Click to expand...
Click to collapse
The software version on the phone is 4.18.502.7 and I made sure to get the same version RUU because I read I cannot use a lesser version than the phone. Also, my phone is also not unlocked, it is relocked currently. When I ran the RUU, it was processing just fine and didnt get a wrong version error. The only error I got was the crazy usb cable error because it was connected just fine.

Squirrelsquisher said:
The software version on the phone is 4.18.502.7 and I made sure to get the same version RUU because I read I cannot use a lesser version than the phone. Also, my phone is also not unlocked, it is relocked currently. When I ran the RUU, it was processing just fine and didnt get a wrong version error. The only error I got was the crazy usb cable error because it was connected just fine.
Click to expand...
Click to collapse
Try using a different USB cable. Make sure it's not one of those cheap ones from ebay. I've had issues with those before. Use your stock usb cord if you can. Let me know if you try that and it still doesn't work. Also try a different USB port on your computer. For some reason, port 2 tends to work best for most people is what I've read.

Squirrelsquisher said:
The software version on the phone is 4.18.502.7 and I made sure to get the same version RUU because I read I cannot use a lesser version than the phone. Also, my phone is also not unlocked, it is relocked currently. When I ran the RUU, it was processing just fine and didnt get a wrong version error. The only error I got was the crazy usb cable error because it was connected just fine.
Click to expand...
Click to collapse
You can flash just the firmware zip
It's on my android file host
I'll post the link when I get to my PC

MarkBell said:
Try using a different USB cable. Make sure it's not one of those cheap ones from ebay. I've had issues with those before. Use your stock usb cord if you can. Let me know if you try that and it still doesn't work. Also try a different USB port on your computer. For some reason, port 2 tends to work best for most people is what I've read.
Click to expand...
Click to collapse
I tried again using different USB ports and different cables with the same error result. Both cables that I used are stock HTC One cables that came with this problem phone and my newer M8 version.
The RUU I have been trying is:
RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2

Did you have sense 5.5 or had you upgraded to Sense 6 before? If you upgraded look for the RUU made for your software version with Sense 6. You may also try a newer RUU version. Just don't try an older one.

MarkBell said:
Did you have sense 5.5 or had you upgraded to Sense 6 before? If you upgraded look for the RUU made for your software version with Sense 6. You may also try a newer RUU version. Just don't try an older one.
Click to expand...
Click to collapse
I didn't get any version errors during the update and I have not seen any RUU out there with sense 6 that doesn't require S-off.

Have you tried the first one on this list? http://forum.xda-developers.com/showthread.php?t=2428276
---------- Post added at 03:19 AM ---------- Previous post was at 03:15 AM ----------
Also. Make sure you check the MD5 of everything you download. I've heard of people downloading corrupted RUUs using Google Chrome. Try another browser. Any other one besides the one you have been using and check the MD5.

Squirrelsquisher said:
I didn't get any version errors during the update and I have not seen any RUU out there with sense 6 that doesn't require S-off.
Click to expand...
Click to collapse
MarkBell said:
Have you tried the first one on this list? http://forum.xda-developers.com/showthread.php?t=2428276
---------- Post added at 03:19 AM ---------- Previous post was at 03:15 AM ----------
Also. Make sure you check the MD5 of everything you download. I've heard of people downloading corrupted RUUs using Google Chrome. Try another browser. Any other one besides the one you have been using and check the MD5.
Click to expand...
Click to collapse
He said in both post #6 and #9 that that is the RUU he's trying
Here's the firmware from the OTA try flashing it then the RUU
http://www.androidfilehost.com/?fid=23329332407580581

I meant that download specifically thinking along the lines of a bad file/download. clsA is very good and I recommend following any advice he gives.

clsA said:
He said in both post #6 and #9 that that is the RUU he's trying
Here's the firmware from the OTA try flashing it then the RUU
Could you be a little more specific on the steps involved in that? Because I tried straight flashing that file and it said it could not load.
Click to expand...
Click to collapse

Squirrelsquisher said:
Could you be a little more specific on the steps involved in that? Because I tried straight flashing that file and it said it could not load.
Click to expand...
Click to collapse
In these situations, it's usually best to always post a "fastboot getvar all" excluding IMEI, possibly a screenshot of bootloader, and a copy/paste of your command prompt output.
the way to flash firmware is:
fastboot oem rebootRUU
fastboot flash zip ATT_OTA.4.18.502.7.firmware.zip
fastboot flash zip ATT_OTA.4.18.502.7.firmware.zip <- yes twice!!, first will say failed flush again, second one should report success
fastboot reboot-bootloader

nkk71 said:
In these situations, it's usually best to always post a "fastboot getvar all" excluding IMEI, possibly a screenshot of bootloader, and a copy/paste of your command prompt output.
the way to flash firmware is:
fastboot oem rebootRUU
fastboot flash zip ATT_OTA.4.18.502.7.firmware.zip
fastboot flash zip ATT_OTA.4.18.502.7.firmware.zip <- yes twice!!, first will say failed flush again, second one should report success
fastboot reboot-bootloader
Click to expand...
Click to collapse
I attached a screenshot of the getvar results before attempting those steps you posted.

I attached the results of the steps you posted that I should use. Since the results says it failed, I did not run the RUU afterwards.

Squirrelsquisher said:
I attached the results of the steps you posted that I should use. Since the results says it failed, I did not run the RUU afterwards.
Click to expand...
Click to collapse
getvar looks ok (well, more or less), what says "it failed"?
example of a copy/paste of a command prompt output:
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot oem rebootRUU[/COLOR][/B]
...
(bootloader) Start Verify: 0
OKAY [ 0.047s]
finished. total time: 0.047s
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot flash zip <myfirmwarezip>.zip[/COLOR][/B]
sending 'zip' (1033216 KB)...
OKAY [ 41.559s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
[B][COLOR="Red"]FAILED (remote: 90 hboot pre-update! please flush image again immediately)[/COLOR][/B]
finished. total time: 43.118s
^^ as expected "flush again"
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot flash zip <myfirmwarezip>.zip[/COLOR][/B]
< waiting for device >
sending 'zip' (1033216 KB)...
OKAY [ 41.912s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[sbl3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl3,0
(bootloader) [RUU]UZ,sbl3,100
(bootloader) [RUU]WP,sbl3,0
(bootloader) [RUU]WP,sbl3,100
(bootloader) ...... Successful
(bootloader) start image[rpm] unzipping & flushing...
(bootloader) [RUU]UZ,rpm,0
(bootloader) [RUU]UZ,rpm,100
(bootloader) [RUU]WP,rpm,0
(bootloader) [RUU]WP,rpm,100
(bootloader) ...... Successful
(bootloader) start image[pg2fs_spcustom] unzipping & flushing...
(bootloader) [RUU]UZ,pg2fs_spcustom,0
(bootloader) [RUU]UZ,pg2fs_spcustom,38
(bootloader) [RUU]UZ,pg2fs_spcustom,99
(bootloader) [RUU]UZ,pg2fs_spcustom,100
(bootloader) ...... Successful
(bootloader) start image[tz] unzipping & flushing...
(bootloader) [RUU]UZ,tz,0
(bootloader) [RUU]UZ,tz,100
(bootloader) [RUU]WP,tz,0
(bootloader) [RUU]WP,tz,100
(bootloader) ...... Successful
(bootloader) start image[sbl1-2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-2,0
(bootloader) [RUU]UZ,sbl1-2,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
......
......
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]WP,rcdata,0
[B](bootloader) ...... Successful
OKAY [200.187s]
finished. total time: 242.101s[/B]
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.037s]
finished. total time: 0.037s
---------- Post added at 06:28 PM ---------- Previous post was at 06:24 PM ----------
Squirrelsquisher said:
I attached the results of the steps you posted that I should use. Since the results says it failed, I did not run the RUU afterwards.
Click to expand...
Click to collapse
oh crap, just saw your screenshot
are you using a USB3 port?

nkk71 said:
getvar looks ok (well, more or less), what says "it failed"?
example of a copy/paste of a command prompt output:
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot oem rebootRUU[/COLOR][/B]
...
(bootloader) Start Verify: 0
OKAY [ 0.047s]
finished. total time: 0.047s
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot flash zip <myfirmwarezip>.zip[/COLOR][/B]
sending 'zip' (1033216 KB)...
OKAY [ 41.559s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
[B][COLOR="Red"]FAILED (remote: 90 hboot pre-update! please flush image again immediately)[/COLOR][/B]
finished. total time: 43.118s
^^ as expected "flush again"
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot flash zip <myfirmwarezip>.zip[/COLOR][/B]
< waiting for device >
sending 'zip' (1033216 KB)...
OKAY [ 41.912s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[sbl3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl3,0
(bootloader) [RUU]UZ,sbl3,100
(bootloader) [RUU]WP,sbl3,0
(bootloader) [RUU]WP,sbl3,100
(bootloader) ...... Successful
(bootloader) start image[rpm] unzipping & flushing...
(bootloader) [RUU]UZ,rpm,0
(bootloader) [RUU]UZ,rpm,100
(bootloader) [RUU]WP,rpm,0
(bootloader) [RUU]WP,rpm,100
(bootloader) ...... Successful
(bootloader) start image[pg2fs_spcustom] unzipping & flushing...
(bootloader) [RUU]UZ,pg2fs_spcustom,0
(bootloader) [RUU]UZ,pg2fs_spcustom,38
(bootloader) [RUU]UZ,pg2fs_spcustom,99
(bootloader) [RUU]UZ,pg2fs_spcustom,100
(bootloader) ...... Successful
(bootloader) start image[tz] unzipping & flushing...
(bootloader) [RUU]UZ,tz,0
(bootloader) [RUU]UZ,tz,100
(bootloader) [RUU]WP,tz,0
(bootloader) [RUU]WP,tz,100
(bootloader) ...... Successful
(bootloader) start image[sbl1-2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-2,0
(bootloader) [RUU]UZ,sbl1-2,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
......
......
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]WP,rcdata,0
[B](bootloader) ...... Successful
OKAY [200.187s]
finished. total time: 242.101s[/B]
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.037s]
finished. total time: 0.037s
---------- Post added at 06:28 PM ---------- Previous post was at 06:24 PM ----------
oh crap, just saw your screenshot
are you using a USB3 port?
Click to expand...
Click to collapse
My PC does not have USB3 ports, only USB2. I don't see how the speed of the transfer would affect the process though?

[Q] There is no RUU for 4T.29.3218.08 :S

Hello, guys.
I bought recently M7 (used) and its awesome.
But i got many problems because of me, and my warranty.
I unlocked bootloader after i get my phone from warranty. But I used my phone about 1 week, and i saw the problem, my screen in left side were getting off. So i tryed to get him back to stock (runned viper before). And now im stucked in the middle of phones death. Its kind a awful. Its 3PM and im trying to find RUU to flash it , and get it to warranty, but there is no ruu for this upgrade. In the google. In the web. In the ethernet. Im so sad right now for myself.
_____________________
Guys, im stucked in the bootloader, and i cant get anywhere.
PC founds my lovely M7 in fastboot mode only. no recovery no nothing. Is there any alternative to get back my stock rom, so i can get him in to warranty again ?
my getvar down here
Code:
INFOversion: 0.5
INFOversion-bootloader: 1.57.0000
INFOversion-baseband: 4T.29.3218.08
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 6.09.401.5
INFOversion-misc: PVT SHIP S-ON
INFOserialno: FA35M-----------------
INFOimei: ------------------
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0710000
INFOcidnum: HTC__032
INFObattery-status: good
INFObattery-voltage: 3884mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-6d8a0b9b
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
Ill try my best to find this dasiuudhasiudsiadhgfdshiogndfs RUU again, and again.
I really hope that some1 can say me what should i do. Or the baddest thing- i should ruin my phone without evidence, but its last thing i want to do.
I hope, someone will give me the light in this tunnel.
Best regards, Berils.
Post scriptum
tryed to use these RUU's:
RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1
RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4
no luck.
Click to expand...
Click to collapse
sorry for my bad english writing skills.

berilslv said:
Hello, guys.
I bought recently M7 (used) and its awesome.
But i got many problems because of me, and my warranty.
I unlocked bootloader after i get my phone from warranty. But I used my phone about 1 week, and i saw the problem, my screen in left side were getting off. So i tryed to get him back to stock (runned viper before). And now im stucked in the middle of phones death. Its kind a awful. Its 3PM and im trying to find RUU to flash it , and get it to warranty, but there is no ruu for this upgrade. In the google. In the web. In the ethernet. Im so sad right now for myself.
_____________________
Guys, im stucked in the bootloader, and i cant get anywhere.
PC founds my lovely M7 in fastboot mode only. no recovery no nothing. Is there any alternative to get back my stock rom, so i can get him in to warranty again ?
my getvar down here
Code:
INFOversion: 0.5
INFOversion-bootloader: 1.57.0000
INFOversion-baseband: 4T.29.3218.08
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 6.09.401.5
INFOversion-misc: PVT SHIP S-ON
INFOserialno: [COLOR="Red"]removed[/COLOR]
INFOimei: [COLOR="Red"]removed[/COLOR]
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0710000
INFOcidnum: HTC__032
INFObattery-status: good
INFObattery-voltage: 3884mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-6d8a0b9b
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
Ill try my best to find this dasiuudhasiudsiadhgfdshiogndfs RUU again, and again.
I really hope that some1 can say me what should i do. Or the baddest thing- i should ruin my phone without evidence, but its last thing i want to do.
I hope, someone will give me the light in this tunnel.
Best regards, Berils.
Post scriptum
tryed to use these RUU's:
sorry for my bad english writing skills.
Click to expand...
Click to collapse
There is no RUU that I can find but I did find a nandroid backup. Since you are having issues with recovery, you might want to run the firmware first. Then you can flash TWRP to install the nandroid. Here is how you flash the firmware, rename it firmware.zip and place in your fastboot/adb folder:
To open a cmd promt in the fastboot/adb folder, hold down the Shift key, right-click on the folder name/icon and choose Open command window here.
Code:
[B][I]adb reboot bootloader[/I][/B]
After that, type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Click to expand...
Click to collapse

There is no RUU that I can find but I did find a nandroid backup. Since you are having issues with recovery, you might want to run the firmware first. Then you can flash TWRP to install the nandroid. Here is how you flash the firmware, rename it firmware.zip and place in your fastboot/adb folder:
Quote:
To open a cmd promt in the fastboot/adb folder, hold down the Shift key, right-click on the folder name/icon and choose Open command window here.
Code:
adb reboot bootloader
After that, type:
Code:
fastboot oem rebootRUU
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
fastboot flash zip firmware.zip
Repeat the same command: IMPORTANT
Code:
fastboot flash zip firmware.zip
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
fastboot reboot
Click to expand...
Click to collapse
@majmoz
i got error after bootloader signature checking....
FAILED (remote: 12 signature verify fail)
what should i do? :S
[SOLUTION]
Guys, if someone get the same, it means that you should unlock bootloader again. i where locked it.
=============================================================
(bootloader) read zipped android_info fail
Again FAILED (remote: 99 unknown fail)
[till now i dont have solution]
------------------------------------
Thanks mate for great instructions!
I guess ill get stock rom, with TWRP.
But witch guide u recomend for getting it fully stock [s-on] ***Tampered*** *** RElocked*** *** Security warning***
tryed rumruneer and squabbi/firewater versions, they didnt worked for me.
Can u recommend me something too from this opera?
Faithfully, Berils.

sry for double post, but i hope it will refresh title, and some will help me in this situation.
I got TWRP, but i dont understand how to flash nandroid.RAR file. tryed to change to zip, ofcourse w/o success
Tryed to put these files witch where inside the .rar , but twrp dont shows up these in backup section.[ and there is different types of files, not like orginal backup folder]
maybe there is tut. for creating working nandroid backup in TWRP , from rar file? cant find that in google/xda too.
Someone?

berilslv said:
sry for double post, but i hope it will refresh title, and some will help me in this situation.
I got TWRP, but i dont understand how to flash nandroid.RAR file. tryed to change to zip, ofcourse w/o success
Tryed to put these files witch where inside the .rar , but twrp dont shows up these in backup section.[ and there is different types of files, not like orginal backup folder]
maybe there is tut. for creating working nandroid backup in TWRP , from rar file? cant find that in google/xda too.
Someone?
Click to expand...
Click to collapse
The nandroid.rar file needs to be extracted and you will get a folder with several items in it. The extracted folder is then placed on your phone //sdcard/TWRP/BACKUP/<Your-Serial-Number>/<Extracted Folder Name>. Once on your phone then boot into TWRP select RESTORE and you should see the Extracted Folder Name select it. An option to ensure you get the correct folder names, you can go into TWRP and select Backup when it is complete exit TWRP to System. When connected to your PC you can see the file names, just copy your extracted folder to the serial number folder.
For programs to extract a rar file check here.
---------- Post added at 08:46 AM ---------- Previous post was at 08:39 AM ----------
berilslv said:
@majmoz
i got error after bootloader signature checking....
FAILED (remote: 12 signature verify fail)
what should i do? :S
[SOLUTION]
Guys, if someone get the same, it means that you should unlock bootloader again. i where locked it.
=============================================================
(bootloader) read zipped android_info fail
Again FAILED (remote: 99 unknown fail)
[till now i dont have solution]
------------------------------------
Thanks mate for great instructions!
I guess ill get stock rom, with TWRP.
But witch guide u recomend for getting it fully stock [s-on] ***Tampered*** *** RElocked*** *** Security warning***
tryed rumruneer and squabbi/firewater versions, they didnt worked for me.
Can u recommend me something too from this opera?
Faithfully, Berils.
Click to expand...
Click to collapse
I would use nkk71's SuperGuide in my signature for returning to stock just make sure you follow the steps in order. If you have tried firewater and get the "whelp this sucks..." then your best option is sunshine but there is a $25 cost.

majmoz said:
The nandroid.rar file needs to be extracted and you will get a folder with several items in it. The extracted folder is then placed on your phone //sdcard/TWRP/BACKUP/<Your-Serial-Number>/<Extracted Folder Name>. Once on your phone then boot into TWRP select RESTORE and you should see the Extracted Folder Name select it. An option to ensure you get the correct folder names, you can go into TWRP and select Backup when it is complete exit TWRP to System. When connected to your PC you can see the file names, just copy your extracted folder to the serial number folder.
For programs to extract a rar file check here.
---------- Post added at 08:46 AM ---------- Previous post was at 08:39 AM ----------
I would use nkk71's SuperGuide in my signature for returning to stock just make sure you follow the steps in order. If you have tried firewater and get the "whelp this sucks..." then your best option is sunshine but there is a $25 cost.
Click to expand...
Click to collapse
Thanks mate, i very appreciate your tips and answers, they where very useful. Ok, thny ill leave phone *** TAMPARED and ***Relocked, and i hope that cant be reason for the refuse from carrier warranty. Because how can i unstick display with unlocked bootloader.
I guess HTC M7 forum is helpful as htc sensation, this was my first experience. Awesome!
Hoping for getting s-off to 1.57.0000 for free soon.
Cheers, Berils.
This topic can be closed Moders.!

Trying to do the same, but during the firmware installation I got error
C:\fastboot>fastboot flash zip firmware.zip
sending 'zip' (550869 KB)...
OKAY [ 26.547s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
finished. total time: 26.797s
Click to expand...
Click to collapse
what Im doing wrong?
here is my getvar information"
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35**********
(bootloader) imei: ********************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 3705mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a
(bootloader) hbootpreupdate: 11
Click to expand...
Click to collapse
But when I just install the nandroid backup, my phone boots up, is working for few seconds and then restart.

jurgins said:
Trying to do the same, but during the firmware installation I got error
what Im doing wrong?
here is my getvar information"
But when I just install the nandroid backup, my phone boots up, is working for few seconds and then restart.
Click to expand...
Click to collapse
Remove your imei and serialno from your post
Are you S-ON? If so, then your bootloader must be locked/relocked before running the firmware.

Guys - help!!
I'm in the same place - bought a brick online
No recovery - if tried to access - I'm getting to botaloader again.
reboot loop.
Bootloader
******Tampered*******
******Relocked********
******Security warning*******
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.29.3218.08
version-cpld: None
version-microp: None
version-main: 6.09.401.5
version-misc: PVT SHIP S-ON
serialno: 00000000000000
imei: 00000000000000
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__Y13
battery-status: good
battery-voltage: 4271mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-6d8a0b9b
hbootpreupdate: 11
gencheckpt: 0
Tried to flash firmware:
t>fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (550869 KB)...
OKAY [ 20.687s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 82.480s
>fastboot flash recovery openrecovery-twrp-2.8.5.0-m7.img
target reported max download size of 1493475328 bytes
sending 'recovery' (11992 KB)...
OKAY [ 1.451s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.047s
I've got only boatloader access - fastboot.
Is there any way to unlock bootloader in fastboot? (mine looks like was unlocked earlier)
Also boatloader acting weirdly - when accessed it's constantly switching between fastboot -hboot options like power button would be pressed every second. If I hold it - it stops - then I can to choose other options - if released option is selected. Could be button issue.

Managed to soft-brick my HTC One m7, need help to recover

Hi everyone, I inherited a used HTC One m7 from my son after my iPhone 4 died. This is my first android device. The phone worked perfect with the stock OS, except the green tint issue after a factory pink tint camera fix. My son never had the time to address the issue, but I decided to try to fix the problem by replacing the awb_cal file. I'm not a Linux guy, so I started from scratch.
Unlocked, installed TWRP, rooted. Because of my inexperience with not only TWRP, but Linux, during the process I managed to wipe clean my HTC. I read lots of instructions to get back in business, but some of them caused more trouble than help. Now, I ended up with a nonfunctioning beautiful piece of technology.
This is where I'm now:
(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.17.661.52
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34RW911052
(bootloader) imei: 354439053805232
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4330mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-eff4f609
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.137s
Using Windows 7 Pro, have installed the fastboot/ADB drivers, installed HTC Sync Manager.
TWRP 3.0.2-0 installed, but not working, can't get into twrp recovery from fastboot-usb mode, it returns to fastboot-usb. In this mode fastboot recognizes the device in cmd. The only way to get ADB recognize my device is to go through the Unlock_code routine. The phone boots right into TWRP, but stops responding at the Running OpenRecoveryScript screen, "Updating partition details... done - Full SELinux support is present. - Running Recovery Commands - Formatting Cache using make_ext4fs... - Wiping data without wiping /data/media ... - Done. - Done processing script file". It hangs here, but now ADB recognizes my device. After rebooting manually into fastboot, it shows Tampered - Relocked, so the unlocking not finishing.
I tried to flash the PN07IMG_M7_UL_L50_SENSE60_MR_TELUS_WWE_7.17.661.7_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420202_signed.zip file in Relocked, with htc_fastboot in rebootRUU mode, but after the first writing I cannot start the second flashing, because it doen't stop but starts sending 'zip' ... (43286 KB) by itself and gets unresponsive at that line:
sending 'zip'... (43286 KB) OKAY
sending time = 3.097 secs
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
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
For "hboot-preupdate" response, restart the same procedure for device HT34RW9110
52...
sending 'zip'... (43286 KB)
Since that in the Bootloader it says in red: OS-7.17.661.52 (7.17.661.7)
I tried to give as much detail as I can, and now I need help please, what should I do. Thanks

vik919 said:
After rebooting manually into fastboot, it shows Tampered - Relocked, so the unlocking not finishing.
Click to expand...
Click to collapse
Unlocking the bootloader requires the stock recovery, not a custom recovery because when unlocking the bootloader, the phone must first make a factory reset using the stock recovery before the bootloader can be unlocked (this is to prevent unauthorized access to your data). If you don't have the stock recovery, your phone will try to boot it, custom recovery will boot instead of the stock one, unlock process will fail because the script is made for the stock recovery, phone will reboot to bootloader mode with the phone still in the locked/relocked state. Unfortunately, you can not boot custom software (recovery/rom/kernel) if the bootloader is locked/relocked. Flashing the recovery partition also requires an unlocked bootloader. You're kinda stock in an endless loop... You need to unlock the bootloader, bootloader unlock requires stock recovery, flashing back the stock recovery requires an unlocked bootloader... Long story short, never relock if custom software is installed.
When the phone is S-ON and (re)Locked, you can only flash signed files (official HTC files) that are same or newer version than what is already on your phone. You'll need to find either the 7.17.661.52 RUU or a 7.17.661.52 firmware.zip. (firmware.zip can be extracted from an ota update.zip so the 7.17.661.52 update file would be ok).

alray said:
Unlocking the bootloader requires the stock recovery, not a custom recovery because when unlocking the bootloader, the phone must first make a factory reset using the stock recovery before the bootloader can be unlocked (this is to prevent unauthorized access to your data). If you don't have the stock recovery, your phone will try to boot it, custom recovery will boot instead of the stock one, unlock process will fail because the script is made for the stock recovery, phone will reboot to bootloader mode with the phone still in the locked/relocked state. Unfortunately, you can not boot custom software (recovery/rom/kernel) if the bootloader is locked/relocked. Flashing the recovery partition also requires an unlocked bootloader. You're kinda stock in an endless loop... You need to unlock the bootloader, bootloader unlock requires stock recovery, flashing back the stock recovery requires an unlocked bootloader... Long story short, never relock if custom software is installed.
When the phone is S-ON and (re)Locked, you can only flash signed files (official HTC files) that are same or newer version than what is already on your phone. You'll need to find either the 7.17.661.52 RUU or a 7.17.661.52 firmware.zip. (firmware.zip can be extracted from an ota update.zip so the 7.17.661.52 update file would be ok).
Click to expand...
Click to collapse
Thanks alray for your response.
So, that PN07IMG_M7_UL_L50_SENSE60_MR_TELUS_WWE_7.17.661.7_ Radio_4T.35.3218.16_10.33Q.1718.01L_release_420202 _signed.zip file can't flash somehow my 7.17.661.52 firmware? I was not able to find any other file for my phone then this one. I don't use the phone on the Telus network anymore. is there any workaround?

vik919 said:
Thanks alray for your response.
So, that PN07IMG_M7_UL_L50_SENSE60_MR_TELUS_WWE_7.17.661.7_ Radio_4T.35.3218.16_10.33Q.1718.01L_release_420202 _signed.zip file can't flash somehow my 7.17.661.52 firmware? I was not able to find any other file for my phone then this one. I don't use the phone on the Telus network anymore. is there any workaround?
Click to expand...
Click to collapse
There is a 7.17.661.52 ruu on ir-file.com but downloading from this website requires a paid subscription
Sent from my HTC One using XDA Labs

alray said:
There is a 7.17.661.52 ruu on ir-file.com but downloading from this website requires a paid subscription
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
Is this the one you mean?
pn07img_m7_ul_l50_sense60_mr_telus_wwe_7.17.661.52_radio_4t.35.3218.16_10.33q.1718.01l_release_460209_signed.zip

vik919 said:
Is this the one you mean?
pn07img_m7_ul_l50_sense60_mr_telus_wwe_7.17.661.52_radio_4t.35.3218.16_10.33q.1718.01l_release_460209_signed.zip
Click to expand...
Click to collapse
Yes
Sent from my HTC One using XDA Labs

alray said:
Yes
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
I wouldn't mind to pay that 20 bucks if I knew that it would get me through the first steps to fix my phone. My only concern is that I already tried the
PN07IMG_M7_UL_L50_SENSE60_MR_TELUS_WWE_7.17.661.7_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420202_signed.zip
file and it did not work. This is the one which went in once, but I didn't get the opportunity to flash second time. It is now hanging in brackets in my bootloader beside the 7.1.7.661.52 firmware number.
Also, I checked this file and I can't see any zip file in it I could extract. Wouldn't it be with that paid one which looks pretty much the same except the firmware version number?
PN07IMG_M7_UL_L50_SENSE60_MR_TELUS_WWE_7.17.661.52_Radio_4T.35.3218.16_10.33Q.1718.01l_release_46020 9_signed.zip
Wait a minute!
I just double checked and found at IR-File.com under Firmware an other file for my phone.
pn07img_m7_ul_l50_sense60_mr_telus_wwe_7.17.661.7_radio_4t.35.3218.16_10.33q.1718.01l_release_420202_signed_hboot.zip
This file ending with _hboot.zip only 493.0 MB in size compare to the other two files which are both about 1.5 GB. Is it possible that this latter one has the firmware.zip in it I could extract?
Please, advise, which one do I need?