Database Develop

[Q] Phone possible bricked?

I recently purchased an HTC One from CSpire (CDMA but has a simcard?) and I tried to flash a ROM but it didnt go as planed.
Now when I get into the bootloader and try to do anything the phone either gets stuck in a bootloop or just shuts off then goes straight back to bootloader.
I have tried using multiple RUU's, flashed multiple recovery .img's, and even tried to flash an entirely new version of twrp but nothing worked.
Is it possible to use bootloader to extract a ROM from my pc, via USB, to my HTC One? From there I could go into twrp and run the file but I am not sure exactly how that would work.
Hope I gave enough info and did this post right as this is my first on here.
Thanks!

ShiftStride said:
I recently purchased an HTC One from CSpire (CDMA but has a simcard?)
Click to expand...
Click to collapse
SIM card is needed on cdma phone for LTE.
ShiftStride said:
I tried to flash a ROM but it didnt go as planed.
Click to expand...
Click to collapse
Why? What rom did you flashed, please provide a link!
ShiftStride said:
Now when I get into the bootloader and try to do anything the phone either gets stuck in a bootloop or just shuts off then goes straight back to bootloader.
Click to expand...
Click to collapse
fastboot erase cache? What recovery did you flashed? link please!
ShiftStride said:
I have tried using multiple RUU's, flashed multiple recovery .img's, and even tried to flash an entirely new version of twrp but nothing worked.
Click to expand...
Click to collapse
wohh.... Which RUU/recovery version?
ShiftStride said:
Is it possible to use bootloader to extract a ROM from my pc, via USB, to my HTC One? From there I could go into twrp and run the file but I am not sure exactly how that would work.
Click to expand...
Click to collapse
No not from bootloader. A ruu is flashed from fastboot ruu mode and a rom from a custom recovery.
ShiftStride said:
Hope I gave enough info and did this post right as this is my first on here.
Click to expand...
Click to collapse
Please post the output of ''fastboot getvar all'' minus IMEI and SERIALNO. Also post those links of what you tried to flash.

@alray
alray said:
SIM card is needed on cdma phone for LTE.
Click to expand...
Click to collapse
That makes sense thanks!
Why? What rom did you flashed, please provide a link!
Click to expand...
Click to collapse
I used these two ROMS:
http://forum.xda-developers.com/showthread.php?t=2334294
&
http://forum.xda-developers.com/showthread.php?t=2183023
fastboot erase cache? What recovery did you flashed? link please!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2550778
I just went to the bootloader and the into recovery mode and instead of TWRP I get ClockworkMod Recovery v6.0.4.3 ...? i dont ever remember putting this on my device
wohh.... Which RUU/recovery version?
Click to expand...
Click to collapse
I used this version:
http://forum.xda-developers.com/showthread.php?t=2508907
I tried others but this was the closet one to the version that was on my phone. (The phone now has no image version when I did it?)
No not from bootloader. A ruu is flashed from fastboot ruu mode and a rom from a custom recovery.
Click to expand...
Click to collapse
Ohhhh okay thank you for explaining!
Please post the output of ''fastboot getvar all'' minus IMEI and SERIALNO. Also post those links of what you tried to flash.
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 1.00.20.0913_3
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 99000146225408
product: m7_wls
platform: HBOOT-8064
modelid: PN0720000
cidnum: UTSI_005
battery-status: good
battery-voltage: 3801mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-005bf6a40e
hbootpreupdate: 11
gencheckpt: 0
Are you talking about TWRP or CWm? If so I tried using TWRP 2.6.3.3
Thank you soooo much for the quick reply! I would have responded sooner but I am just now getting off work :laugh:

ShiftStride said:
http://forum.xda-developers.com/showthread.php?t=2334294
&
http://forum.xda-developers.com/showthread.php?t=2183023
Click to expand...
Click to collapse
Make sure to use a rom that is Sprint compatible, I know your phone is C spire but this is the same model variant as Sprint (M7WLS)
Also newer 4.4+ rom require at least TWRP 2.6.3.3.
List of compatible roms for your phone can be found here
Again note that all stuff related to the ''international'' version of the phone (M7_UL) won't work on your phone but ''Sprint'' stuff should work (M7WLS) This apply to roms, recoveries, everything!
ShiftStride said:
http://forum.xda-developers.com/showthread.php?t=2550778
Click to expand...
Click to collapse
This is probably the cause of your problem. The recovery you linked above is for M7_UL and M7_U variant of the HTC ONE not the M7WLS!
The TWRP recovery version for your phone is HERE
Code:
fastboot flash recovery openrecovery-twrp-2.7.0.1-m7wls.img
fastboot erase cache
fastboot reboot-bootloader
I hope you did not messed your partitions by flashing wrong recoveries/roms...
ShiftStride said:
I used this version:
http://forum.xda-developers.com/showthread.php?t=2508907
I tried others but this was the closet one to the version that was on my phone. (The phone now has no image version when I did it?)
Click to expand...
Click to collapse
RUU must be same or higher firmware version + CID and MID must match. Unfortunately this RUU is for Sprint which mean it is for Sprint CID not for C Spire CID , Btw there is no RUU I can found for your phone over the internet. So better to forgive that.
ShiftStride said:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 1.00.20.0913_3
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
meid:
product: m7_wls Your phone variant
platform: HBOOT-8064
modelid: PN0720000 Your MID
cidnum: UTSI_005 Your CID (C-Spire)
battery-status: good
battery-voltage: 3801mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-005bf6a40e
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
So flash the proper recovery to your phone, clear cache and reboot to recovery.
After push a M7WLS roms to your phone and install it.

alray said:
Make sure to use a rom that is Sprint compatible, I know your phone is C spire but this is the same model variant as Sprint (M7WLS)
Also newer 4.4+ rom require at least TWRP 2.6.3.3.
List of compatible roms for your phone can be found here
Again note that all stuff related to the ''international'' version of the phone (M7_UL) won't work on your phone but ''Sprint'' stuff should work (M7WLS) This apply to roms, recoveries, everything!
This is probably the cause of your problem. The recovery you linked above is for M7_UL and M7_U variant of the HTC ONE not the M7WLS!
The TWRP recovery version for your phone is HERE
Code:
fastboot flash recovery openrecovery-twrp-2.7.0.1-m7wls.img
fastboot erase cache
fastboot reboot-bootloader
I hope you did not messed your partitions by flashing wrong recoveries/roms...
RUU must be same or higher firmware version + CID and MID must match. Unfortunately this RUU is for Sprint which mean it is for Sprint CID not for C Spire CID , Btw there is no RUU I can found for your phone over the internet. So better to forgive that.
So flash the proper recovery to your phone, clear cache and reboot to recovery.
After push a M7WLS roms to your phone and install it.
Click to expand...
Click to collapse
@alray
Okay so I flashed the new recovery, cleared the cache, and am now in the bootloader.
What do you mean by push the rom to it? I am going with the Viper ROM but the download site doesnt seem to be up
Thanks again for the help man!
UPDATE: I tried to use ADB to 'push' the ROM onto the device so I could then install it with twrp in recovery mode. The problem is that ADM doesn't find my device but FastBoot does. I've looked this problem up and have found nothing that helps. Sorry for such the last response and thanks again!

ShiftStride said:
@alray
Okay so I flashed the new recovery, cleared the cache, and am now in the bootloader.
What do you mean by push the rom to it? I am going with the Viper ROM but the download site doesnt seem to be up
Thanks again for the help man!
UPDATE: I tried to use ADB to 'push' the ROM onto the device so I could then install it with twrp in recovery mode. The problem is that ADM doesn't find my device but FastBoot does. I've looked this problem up and have found nothing that helps. Sorry for such the last response and thanks again!
Click to expand...
Click to collapse
were you booted in twrp to use adb push?
Boot your phone to TWRP main menu and adb push <name_of_rom>.zip /sdcard/ then in twrp select ''install'' and choose the rom and swipe to flash.

alray said:
were you booted in twrp to use adb push?
Boot your phone to TWRP main menu and adb push <name_of_rom>.zip /sdcard/ then in twrp select ''install'' and choose the rom and swipe to flash.
Click to expand...
Click to collapse
@alray
Yes and it STILL doesnt recognize my device,,,I'm about to loose it as this is the THIRD day without a phone. I reeeeaaaaalllyy am not looking foward to spending 500 on a new phone
I've looked around to try and fix this problem but no luck
I have also tried two different computers one with Windows 8 and one with 7. I dont know if that matters but I tried.
Thanks for sticking with me to help me out!

ShiftStride said:
@alray
Yes and it STILL doesnt recognize my device,,,I'm about to loose it as this is the THIRD day without a phone. I reeeeaaaaalllyy am not looking foward to spending 500 on a new phone
I've looked around to try and fix this problem but no luck
I have also tried two different computers one with Windows 8 and one with 7. I dont know if that matters but I tried.
Thanks for sticking with me to help me out!
Click to expand...
Click to collapse
When in twrp, in windows device manger, how the phone is listed? Android usb devices ----> My HTC ? if not follow this guide:
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
2) Q: I'm using Windows 7 what should I worry about
A: when you issue the command "fastboot boot CWM.img" (now only in CWM/TWRP restore method) there's a high chance drivers won't correctly install
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways​
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
-------------------------------------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse

alray said:
When in twrp, in windows device manger, how the phone is listed? Android usb devices ----> My HTC ? if not follow this guide:
Click to expand...
Click to collapse
@alray
OH MY GOD THANK YOU SO MUCH! I can't explain the joy you have given me today! Not only did you help me fix the problem, you educated me to a point that I feel comfortable to do it again on my own. Thank you sooooooooooooooooooooooooooooooo much! Have a great day!

ShiftStride said:
@alray
OH MY GOD THANK YOU SO MUCH! I can't explain the joy you have given me today! Not only did you help me fix the problem, you educated me to a point that I feel comfortable to do it again on my own. Thank you sooooooooooooooooooooooooooooooo much! Have a great day!
Click to expand...
Click to collapse
Np, thanks nkk71 for his guide :good:
and please edit your thread title to ''Solved''
thanks

[q] q my htc one not entering recovery mode

HI ALL
MY HTC ONE AT&T UNLOCKED
MY HTC ONE hade a problem with battery
three days back i replace the battery but my device keep rebooting :crying:
i can enter bootloader menu but not revcovery
i try to flash boot.img from cmd its don completely but device same
i try to run ruu rom its don completely but device same
there on different in one case the htc screen come with wirning "This build is for development purposes only do not distribute outside of HTC without HTC's permission ..."
- Device details -
M7_UL PVT SHIP S-OFF RH
CID-CWS__001
HBOOT-1.55.0000
RADIO-4A.19.3263.13
openDSP-v31.120.274.0617
OS-3.17.502.3
eMMc-boot 2048MB
sep 10 2013,01:32:23.0
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3562mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
hope you can help guys
best regards

fastboot flash recovery recovery_name.img
fastboot erase cache

First off, remove your IMEI and Serial Number from the post above. That's sensitive information.
Second, normally the "Development Purpose" message should disappear once you flash back to stock with RUU. are you positive that flashing finished successfully?
Anyhow your problem should be solved - as BenPope has said - by reflashing your recovery. Just pick a suitable revocery image, enter Bootloader in FastbootUSB mode and give it a try:
Code:
fastboot flash recovery recovery_name.img
fastboot erase cache

i did this guys and my device still same

supermagic49 said:
i did this guys and my device still same
Click to expand...
Click to collapse
Which recovery exactly did you flash? Are you absolutely positive it was a suitable version for your device?
How by the way did you change the battery yourself? Did you disassemble the phone? If so you might perhaps have broken something?
Gesendet von meinem SM-T705 mit Tapatalk

- I had tried all recovery files CWS__001 in this link http://forum.xda-developers.com/showthread.php?t=2545227
- i changed battery in maintenance center but u think it can start bootloader accept flashing an there is something broken
do u advice to disassemble n see
regards

supermagic49 said:
- I had tried all recovery files CWS__001 in this link http://forum.xda-developers.com/showthread.php?t=2545227
Click to expand...
Click to collapse
Those are Stock Recoverys if I'm not mistaken. So even if you flashed those you wouldn't recognize any difference as they don't change anything compared to stock.
But first there's something else I oversaw. In your OP you stated your details. It seems you haven't yet unlocked your bootloader? Or did you just leave out that information? That would be the reason why flashing anything does not work - AT ALL.
Unlock your Bootloader (use seach, there are lots of tutorials on how to do that). Second, please don't temper with the boot.img right now. There is no reason for you to change or overwrite a working bootloader. In fact the chances are you would mess up things even more. So leave the boot.img alone for now.
My suggestion is:
- Unlock your Bootloader (with HTCDev)
- Flash a Custom Recovery (e.g. TWRP - http://forum.xda-developers.com/showthread.php?t=2173870)
- Take it from there. See if recovery works and if so, go ahead an flash a Custom ROM, a Nandroid Backup or get yourself S-OFF (Firewater or Rumrunner) and flash back a stock RUU.
RUUs can be a bit tricky with S-ON. So although you theoretically should be able to flash a (newer) RUU even with S-ON, you can make sure it works by being S-OFF first. SInce only then can you also downgrade your Device via RUU plus it then does not matter if you're locked / unlocked / relocked / tempered. Thing is you need a working Android to get S-OFF. That's why I suggested flashing a Custom ROM. Just about any suitable M7 ROM will do, for example: http://forum.xda-developers.com/showthread.php?t=2334294. Give it a try and tell me how it went, will you? Best of luck. But if you're unsure about anything, ask first. Don't mess things up even more

Ok nosmint
thnx for ur kind following
- my device is unlocked
-i flash one of the recovery u refer to with the order " fastboot flash boot" because "flash revocery" return to me with "remot no allowed"
-flash zip and flash recovery is not allowed i think if i clear this problem every thing will be fine
one more thing i open my device i found to cable not fixed i fix bu no changes
that,s the cable was not fixed
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://i.ytimg.com/vi/S5KNmDeJ4Ww/maxresdefault.jpg

nosmint said:
... get yourself S-OFF (Firewater or Rumrunner) and flash back a stock RUU.
RUUs can be a bit tricky with S-ON.
Click to expand...
Click to collapse
the OP says:
(bootloader) version-misc: PVT SHIP S-OFF

nkk71 said:
the OP says:
(bootloader) version-misc: PVT SHIP S-OFF
Click to expand...
Click to collapse
Any advice dear

supermagic49 said:
Any advice dear
Click to expand...
Click to collapse
Well first of all please explain what your goal is.... do you want custom ROM, stock ROM, etc.
Second, we are talking about bootloader unlocked not SIM-unlocked, this
- my device is unlocked
-i flash one of the recovery u refer to with the order " fastboot flash boot" because "flash revocery" return to me with "remot no allowed"
Click to expand...
Click to collapse
indicates your bootloader is either LOCKED or RELOCKED
look at the first line of the attached screenshot.
So please explain what your goal is, and i'll try and help from there.

How can i clear the message of " remote not allowed so i can flash recovery
Regards

supermagic49 said:
How can i clear the message of " remote not allowed so i can flash recovery
Regards
Click to expand...
Click to collapse
you would need to unlock bootloader (it's pretty easy with S-Off), but please first tell us what you want to achieve

nkk71 said:
Well first of all please explain what your goal is.... do you want custom ROM, stock ROM, etc.
Second, we are talking about bootloader unlocked not SIM-unlocked, this
indicates your bootloader is either LOCKED or RELOCKED
look at the first line of the attached screenshot.
So please explain what your goal is, and i'll try and help from there.
Click to expand...
Click to collapse
Fine
my goal to see my device working with custom ROM or stock ROM
my bootloader unlocked i just forget to mention that

supermagic49 said:
Fine
my goal to see my device working with custom ROM or stock ROM
my bootloader unlocked i just forget to mention that
Click to expand...
Click to collapse
use this RUU: http://androidruu.com/getdownload.p...13_10.38j.1157.04_release_334235_signed_2.exe
that will wipe your phone completely and install stock ROM and firmware.

i had tried this too but no change

ruu info
When looking for ruu.exe I went through 6 or 7 different ones. 1 way to know if u have the right ruu is by searching your android and sense version also provider currently on your phone otherwise the ruu won't work s-off dosnt matter I never turned it off on my phone and still got the ruu to work

HTC one M7 continuously reboots till battery drains

I am having problem with my htc one. It continuously reboots. Displays HTC Logo then O2 then Beats audio and then restart.
The things which I have tried doing are
after volume down and pressing power button factory reset, in fast boot rebooted the boot loader. When I go into the recovery it gives red triangle with an exclamation mark in the middle.
I tried connecting it with adb but it says
List of devices attached and then empty no device
adb shell gives
error: device not found
I tried fastboot devices -> this displays
W910109 fastboot
D:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.206.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA386W910109
(bootloader) imei: 357864053760359
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4298mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.117s
Can anyone help me in the matter. My device warranty is void. All I want it to go back to factory reset.
thanks

hammaad110 said:
I am having problem with my htc one. It continuously reboots. Displays HTC Logo then O2 then Beats audio and then restart.
The things which I have tried doing are
after volume down and pressing power button factory reset, in fast boot rebooted the boot loader. When I go into the recovery it gives red triangle with an exclamation mark in the middle.
I tried connecting it with adb but it says
List of devices attached and then empty no device
adb shell gives
error: device not found
I tried fastboot devices -> this displays
W910109 fastboot
D:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.206.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA386W910109
(bootloader) imei: 357864053760359
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4298mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.117s
Can anyone help me in the matter. My device warranty is void. All I want it to go back to factory reset.
thanks
Click to expand...
Click to collapse
Did you do a factory reset? If so you will need to reflash the rom.

zelendel said:
Did you do a factory reset? If so you will need to reflash the rom.
Click to expand...
Click to collapse
i have tried doing factory reset but it stops giving a red triangle with an exclamation mark.
i would be glad if you can guide me to the steps regarding reflashing the rom.

hammaad110 said:
I am having problem with my htc one. It continuously reboots. Displays HTC Logo then O2 then Beats audio and then restart.
The things which I have tried doing are
after volume down and pressing power button factory reset, in fast boot rebooted the boot loader. When I go into the recovery it gives red triangle with an exclamation mark in the middle.
I tried connecting it with adb but it says
List of devices attached and then empty no device
adb shell gives
error: device not found
I tried fastboot devices -> this displays
W910109 fastboot
D:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.206.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA386W910109
(bootloader) imei: 357864053760359
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4298mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.117s
Can anyone help me in the matter. My device warranty is void. All I want it to go back to factory reset.
thanks
Click to expand...
Click to collapse
waiting for assistance

hammaad110 said:
waiting for assistance
Click to expand...
Click to collapse
Search the site. Everything you need has already been posted.

zelendel said:
Search the site. Everything you need has already been posted.
Click to expand...
Click to collapse
I have downloaded the RUU file
htc1guru.com/dld/ruu_m7_ul_k44_sense55_mr_o2_uk_4-20-206-16_radio_4a-23-3263-28_10-38r-1157-04l_release_353143_signed_2-exe
for modelid: PN0710000
cidnum: O2___001
I executed the file while in Fastboot usb mode. The file gave different messages and told me that going to urgrade the ROM to 4.xx. Then it asked me to press next. When I pressed next it restarted the phone and it again went into the infinite loop on restating. while the PC screen was saying waiting for the bootloader and then after 2 or 3 min it said that error in the USB connection.
the phone says MY HTC in Android USB devices when its in Fastboot mode while in normal boot loader mode its not detected. Also adb does not gives anything when i give command adb devices. However Fastboot devices gives serial number if the device.

hammaad110 said:
I have downloaded the RUU file
htc1guru.com/dld/ruu_m7_ul_k44_sense55_mr_o2_uk_4-20-206-16_radio_4a-23-3263-28_10-38r-1157-04l_release_353143_signed_2-exe
for modelid: PN0710000
cidnum: O2___001
I executed the file while in Fastboot usb mode. The file gave different messages and told me that going to urgrade the ROM to 4.xx. Then it asked me to press next. When I pressed next it restarted the phone and it again went into the infinite loop on restating. while the PC screen was saying waiting for the bootloader and then after 2 or 3 min it said that error in the USB connection.
the phone says MY HTC in Android USB devices when its in Fastboot mode while in normal boot loader mode its not detected. Also adb does not gives anything when i give command adb devices. However Fastboot devices gives serial number if the device.
Click to expand...
Click to collapse
I would remove all the drivers and start from scratch. FIrst thing you will need to get working is your adb drivers on your PC. Make sure to be running windows 7, uninstall all android drivers, reboot PC, then plug in the android in bootloader mode and let the OS install the needed drivers.

zelendel said:
I would remove all the drivers and start from scratch. FIrst thing you will need to get working is your adb drivers on your PC. Make sure to be running windows 7, uninstall all android drivers, reboot PC, then plug in the android in bootloader mode and let the OS install the needed drivers.
Click to expand...
Click to collapse
Done that. it only detects a hardware in fastboot mode and no device is detected in bootloader mode.

hammaad110 said:
Done that. it only detects a hardware in fastboot mode and no device is detected in bootloader mode.
Click to expand...
Click to collapse
Then something is wrong with your driver set up. Check the threads in this section of other ways to get it working. I know that if you had HTC sync installed that it would cause these issues. I have never had this issue where what I discribed above didnt fix

hammaad110 said:
Done that. it only detects a hardware in fastboot mode and no device is detected in bootloader mode.
Click to expand...
Click to collapse
could you define the difference between "fastboot mode" and "bootloader mode"?
if you are in bootloader and it says FASTBOOT USB (in red), it will detect your device

nkk71 said:
could you define the difference between "fastboot mode" and "bootloader mode"?
if you are in bootloader and it says FASTBOOT USB (in red), it will detect your device
Click to expand...
Click to collapse
Yes my device is detected in FASTBOOT USB but is not detected in ADB devices even in BOOTLOADER
since my bootloader is LOCKED. I had tried unlocking it through htcdev procedure but after the procedure and pressing ok on device it again says LOCKED
so I cannot UNLOCK the bootloader and thus cannot install custom recovery.
What should I do now

hammaad110 said:
Yes my device is detected in FASTBOOT USB but is not detected in ADB devices even in BOOTLOADER
since my bootloader is LOCKED. I had tried unlocking it through htcdev procedure but after the procedure and pressing ok on device it again says LOCKED
so I cannot UNLOCK the bootloader and thus cannot install custom recovery.
What should I do now
Click to expand...
Click to collapse
you should redo all the unlocking procedure try that

hammaad110 said:
Yes my device is detected in FASTBOOT USB but is not detected in ADB devices even in BOOTLOADER
since my bootloader is LOCKED. I had tried unlocking it through htcdev procedure but after the procedure and pressing ok on device it again says LOCKED
so I cannot UNLOCK the bootloader and thus cannot install custom recovery.
What should I do now
Click to expand...
Click to collapse
not sure what you mean, but:
fastboot commands work in bootloader (FASTBOOT USB on the phone screen), adb does not
adb commands work in custom recovery
adb commands work in booted up phone with USB debuggin enabled

hammaad110 said:
Yes my device is detected in FASTBOOT USB but is not detected in ADB devices even in BOOTLOADER
since my bootloader is LOCKED. I had tried unlocking it through htcdev procedure but after the procedure and pressing ok on device it again says LOCKED
so I cannot UNLOCK the bootloader and thus cannot install custom recovery.
What should I do now
Click to expand...
Click to collapse
As I explained in our pm's you need to be on hboot 1.55 to use that ruu.
To get your phone unlocked I think you need to flash firmware to refresh your hboot. But unfortunately there isn't any available any where unless @nkk71 knows where you might find it.
With your phone in its current state there is no way for you to use adb, since it won't work in stock recovery. I'm considering going out of my way to help you out here but let's see if nkk71 has anything first.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk

Danny201281 said:
As I explained in our pm's you need to be on hboot 1.55 to use that ruu.
To get your phone unlocked I think you need to flash firmware to refresh your hboot. But unfortunately there isn't any available any where unless @nkk71 knows where you might find it.
With your phone in its current state there is no way for you to use adb, since it won't work in stock recovery. I'm considering going out of my way to help you out here but let's see if nkk71 has anything first.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Click to expand...
Click to collapse
I haven't looked much, but didn't see any 2.24.206.7 or higher firmware.zip in the usual places... it may be out there but i didn't see it.
hammaad110 said:
since my bootloader is LOCKED. I had tried unlocking it through htcdev procedure but after the procedure and pressing ok on device it again says LOCKED
so I cannot UNLOCK the bootloader and thus cannot install custom recovery.
What should I do now
Click to expand...
Click to collapse
wait, i guess i misunderstood, are you saying HTCdev bootloader unlock is no longer working?? (can you copy/paste command prompt output of that, don't forget to get a new token)
can you also copy/paste the command prompt output of "fastboot oem rebootRUU", do you actually get to ruu mode:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
if you can get to RUU mode, you should try to get the RUU to work.
the 4.xx RUUs are OK, but are very picky about PC configuration, USB ports, etc.

nkk71 said:
I haven't looked much, but didn't see any 2.24.206.7 or higher firmware.zip in the usual places... it may be out there but i didn't see it.
wait, i guess i misunderstood, are you saying HTCdev bootloader unlock is no longer working?? (can you copy/paste command prompt output of that, don't forget to get a new token)
can you also copy/paste the command prompt output of "fastboot oem rebootRUU", do you actually get to ruu mode:
if you can get to RUU mode, you should try to get the RUU to work.
the 4.xx RUUs are OK, but are very picky about PC configuration, USB ports, etc.
Click to expand...
Click to collapse
Hi nkk71, I had the same problem with my friends O2uk m7, When it comes helpful files there doesn't seem to be anything for O2.
The bootloader unlocking goes fine up untill the the point he selects "yes" to unlock on the phone. The phone reboots but is still locked.
The RUU in question is an exe I used it myself after many hours of of failing with error 12 signature verification failed, with hboot 1.57. it's the same with this situation. Eventually my friend decided to pay for the sunshine app so I could s-off the device and I finally got the ruu to work by, changing the cid to HTC__001 I then manipulated the firmware using 401 WWE firmware to bring the phone to hboot 1.55. I then changed the cid back to O2__001 and the RUU worked.
So I think he needs the 3.xx.206.x firmware to run the ruu.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk

Danny201281 said:
Hi nkk71, I had the same problem with my friends O2uk m7, When it comes helpful files there doesn't seem to be anything for O2.
The bootloader unlocking goes fine up untill the the point he selects "yes" to unlock on the phone. The phone reboots but is still locked.
The RUU in question is an exe I used it myself after many hours of of failing with error 12 signature verification failed, with hboot 1.57. it's the same with this situation. Eventually my friend decided to pay for the sunshine app so I could s-off the device and I finally got the ruu to work by, changing the cid to HTC__001 I then manipulated the firmware using 401 WWE firmware to bring the phone to hboot 1.55. I then changed the cid back to O2__001 and the RUU worked.
So I think he needs the 3.xx.206.x firmware to run the ruu.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Click to expand...
Click to collapse
ah, yes, i think you're right, HTC did change some "stuff" between earlier releases and later ones, so that would explain the signature fail.
but how did the OP end up in this situation? could very well be a hardware problem... do you have any info on that? considering he's S-On / LOCKED (ie never messed with his phone), and a "semi-successful" HTCdev unlock (ie token is fine, but unlock doesn't unlock) does sound awfully familiar to a hardware problem
* what's the command output of "fastboot oem rebootRUU"? does it go to ruu mode?
* how did this happen?? (is it one of those "it happened suddenly" things?)

nkk71 said:
ah, yes, i think you're right, HTC did change some "stuff" between earlier releases and later ones, so that would explain the signature fail.
but how did the OP end up in this situation? could very well be a hardware problem... do you have any info on that? considering he's S-On / LOCKED (ie never messed with his phone), and a "semi-successful" HTCdev unlock (ie token is fine, but unlock doesn't unlock) does sound awfully familiar to a hardware problem
* what's the command output of "fastboot oem rebootRUU"? does it go to ruu mode?
* how did this happen?? (is it one of those "it happened suddenly" things?)
Click to expand...
Click to collapse
From our pm's
Then it may be because you need to update hboot first.
Are you running the ruu to fix a bootloop problem?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Click to expand...
Click to collapse
Yes exactly. I want to clear the boot loop problem. The cellphone is of my client and I dont know exactly what he has done wrong with it. As far as he says that he only cleared some junk files and phone is in this condition.
Click to expand...
Click to collapse
I'll be honest I was considering converting my phone to O2 stock and capturing the ota's and making a few stock nandroids. A lot of trouble to help one person especially as you think it could be hardware. But it would help the O2 community as a whole so maybe worth the effort.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk

Danny201281 said:
From our pm's
Yes exactly. I want to clear the boot loop problem. The cellphone is of my client and I dont know exactly what he has done wrong with it. As far as he says that he only cleared some junk files and phone is in this condition.
Click to expand...
Click to collapse
I'll be honest I was considering converting my phone to O2 stock and capturing the ota's and making a few stock nandroids. A lot of trouble to help one person especially as you think it could be hardware. But it would help the O2 community as a whole so maybe worth the effort.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Click to expand...
Click to collapse
Well not knowing the background is a real problem.
Do you happen to know the colour of the bootloader? is it a GPE bootloader... this could be another badly done Sense to GPE back to Sense conversion... therefore missing the necessary files/partitions for htcdev unlock to work (even if it's a HTC bootloader)
There is a 4.xx firmware that he could flash (has hboot 1.56 dd Nov 29 2013), though I will not recommend it, as chances of unlocking bootloader will be slim if the O2 RUU fails.
and yeah, capturing all those OTAs for O2, is going to be a bit of work... don't wanna sound selfish, but i'm in no mood for that atm... maybe if i have time on weekend i might consider it, though that is a big maybe

nkk71 said:
Well not knowing the background is a real problem.
Do you happen to know the colour of the bootloader? is it a GPE bootloader... this could be another badly done Sense to GPE back to Sense conversion... therefore missing the necessary files/partitions for htcdev unlock to work (even if it's a HTC bootloader)
There is a 4.xx firmware that he could flash (has hboot 1.56 dd Nov 29 2013), though I will not recommend it, as chances of unlocking bootloader will be slim if the O2 RUU fails.
and yeah, capturing all those OTAs for O2, is going to be a bit of work... don't wanna sound selfish, but i'm in no mood for that atm... maybe if i have time on weekend i might consider it, though that is a big maybe
Click to expand...
Click to collapse
I don't know the bootloader color sorry maybe @hammaad110 can post a picture for us?
I may have a go at capturing the otas if I can make time for it. I won't be capturing them all though may be just the 2.xx and 3.xx with Stock nandroids that would be enough for using the RUU at least and possibility of a reset zip.
Besides I already have the necessary files to make the change to O2. So I wouldn't trouble yourself with that. It was my idea so I wouldn't expect you to go to the trouble of making it happen
As for the bootloader unlocking problem I remember a similar case, although weather we came to a solution is sketchy in my memory. I seem to remember flashing the current firmware fixed the problem. I'll look through my posts and pm's to try to find it so I can clarify it. If that was the case I'll probably capture the ota's to help this guy out and maybe a few others.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk

[Q] [REWARD] Sprint m7 stuck in RUU mode (aka 'Fancy Paperweight Mode')

Have a very strange problem with my Sprint HTC One m7. Hoping it is software related only. I appear to be stuck in RUU mode. Whenever the phone boots, I am met by the black screen with silver HTC logo in the center and triangles with exclamation points inside in all four corners. Here is my 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:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3773mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
After replacing the battery inside the phone, as well as the front housing with digitizer and screen and back housing, I booted up and was met by a boot loop. Prior to installing new hardware mentioned, I had been using CM12 Android L. I booted into bootloader menu and tried to boot up recovery. Got stuck at the screen which tells you the phone is booting into the recovery. No dice. Recovery never loaded. Rebooted into bootloader and fastboot relocked in anticipation of running either of the two most recent RUUs that matched my HBOOT version (1.57).
Both RUUs have failed me. Both of the two most recent RUUs fail with the incorrect image error (though these are the correct images).
I've also tried flashing firmware. I always get the '12 signature verify failed' message. When I go through the recovery process after the RUU fails, the phone always reboots back into RUU mode. I unplugged it to find the following info displayed on my phone itself:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Makes me wonder what [12] CIR stands for.... Google has turned up zip on this.
So, as you can see, I've tried it all basically. Nothing will get the damn thing out of RUU mode. Now I'm wishing to all ends that I would have just s-offed this stupid thing so I could try to roll back to some old firmware or something.
Of course, I have no access to ADB. I can send fastboot commands and can successfully unlock/relock the phone. I have installed the HTC One driver for my device, as well as the HTC Sync application, but the device is still showing up as Android 1.0 in my 'Devices and Printers' folder on Windows 7 (32-bit).
This is pretty much where I am at for the moment. I would love any ideas my fellow XDAers may have. Maybe the Android L release will result in an RUU that will help, though I have little confidence in that considering the 5.05.651.2 firmware and RUU was of no help.
This luckily is no longer my daily driver. I moved on to a Samsung Galaxy Note 4 on a different network. I thought about using my old One as a fancy coaster that lights up when plugged into the wall or a computer, but when I sat my beer on it, it didn't really seem stable because of the curved back housing.
The scariest thing of all about this is that my problem has even stumped @clsA. It's pretty bad when someone who has literally helped fix 1000s of HTC One m7 Brick Editions can't figure out WTH is going on.
To make this interesting, I promise a respectable donation to whomever offers the piece of advice that gets the device working for me (if it is indeed a software issue). If it's my motherboard, I'm gonna be broke from slapping down 130 bucks or so for a new one (though I really believe it is software related because I was beyond careful when transferring everything to the new housing).
Let the 45th HTC Hunger Games Begin!

Because you are S-on, don't you have to relock your bootloader before running an RUU!
Edit: I see the relocked on the screenshot now. I was just reading the text

There's no easy answer like that, for sure. Haha. I am able to unlock bootloader and push boot image and recovery image via fastboot, but have been unable to push a Nandroid system image and my data image for some reason. The backups were made in TWRP when it was working for me before the hardware changes. Anyone know where I can find a good stock system image and data image to push?

System image should be of the 5.03.651.3 variety. Since TWRP splits my backup into two images, I used copy /b command to combine, but I am still getting sparse header mismatch error.

I am not convinced that if system is accepted via fastboot flash that it would work.

Couple of things if you can access fastboot. Try sudo fastboot erase cache and have you tried super CID? not sure if soff is required for the latter.
Sent from my HTC One using Tapatalk

Tried the fastboot erase cache before to no avail. Not sure what super CID is. Will look into it.

It's a fastboot command to change the Cid... It allows us3rs to flash ruus made by other carriers. Generally means nothing for sprint since we are tied down to cdma however may help the signature verification problem you are having
Sent from my HTC One using Tapatalk

Gotta be s off to use it. Blah.

I'm positive it has something to do with the CIR.img that is in the latest RUU when decrypted. I can flash basically any img to the phone manually except that CIR.img file. The same CIR that is mentioned as reason for failure in the RUU readout above no less. WTF is the CIR?

MarkBell said:
I'm positive it has something to do with the CIR.img that is in the latest RUU when decrypted. I can flash basically any img to the phone manually except that CIR.img file. The same CIR that is mentioned as reason for failure in the RUU readout above no less. WTF is the CIR?
Click to expand...
Click to collapse
Why are you using the decrypted RUU?

Because I am trying everything, including pulling the system image files, boot image files, etc. out of firmware packages that may be relevant and flashing them via flashboot.

MarkBell said:
Because I am trying everything, including pulling the system image files, boot image files, etc. out of firmware packages that may be relevant and flashing them via flashboot.
Click to expand...
Click to collapse
Decrypted won't work since you are s-on.

I understand. I am just trying everything. Even if it doesn't make sense. Desperate.

I'm just stumped. I believe I've tried every possible remedy. Maybe time to send it off to HTC.

Contacted HTC looking for info on CIR Failed-PU. They have been good to me in the past so hopefully they will have some advice. If not, then I'll just send it back for repair.

I am now in contact with HTC about this issue. A tier 3 escalation professional will be coming here to XDA to research the problem with my phone. I recently tried flashing the new Lollipop RUU provided by HTC for Sprint devices. The image failed, again with the same error (CIR - PU). Hopefully something fruitful will come of this that will benefit anyone in the future with this type of issue.

Your s- on , have tried to unlock the boot loader with htcdev.com method and s-off and try flashing a custom recovery, I've been stuck like this before , try using fastboot oem unlock ,see if it will reunlock it with out htcdev.com if u gain s-off u can also use ruu ,make sure your using the right one for your hardware,or if u gain unlock change to supercid

As stated before, I can freely unlock and relock bootloader no problem. But the device won't even boot to the bootloader menu. I can flash fastboot commands from the black screen with silver HTC logo (RUU mode), but in order to flash the fastboot command for supercid I need to get s off. In order to be s off on my hboot version, I need to be able to flash commands thru adb, which I cannot in its current state. I can successfully flash a custom recovery but since I can't boot into bootloader menu, I have no way of getting the device to boot into recovery mode. It is literally stuck in RUU mode.

What firmware are you on it doesn't say ?

HTC One M7 bootloop, locked bootloader, s-off, nothing works, recovery, flashing

Hi. Everyone I just bought a second hand HTC One M7 and the phone has software issues. I already researched hours into it and tried to fix it by my self but it seems that HTC phones are the hardest phones to fix... So when I start the phone it goes into a infinite bootloop, if I start the bootloader by holding volume down + power, the phone goes into hboot and shows this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So it looks like the phone's bootloader is Locked and S-ON.
Now going deeper into the rabbits hole, the phone appears to be SuperCID 11111111, but who knows? Maybe the previous owner changed its CID...?
(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.19.401.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA416W901137
(bootloader) imei: 3594050*******
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3795mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Anyway I tried, Factory Reset, NOTHING, I tried Recovery, nothing, still infinite bootloops. I tried making the phone S-OFF with rumrunner_HTC_0.5.0 and damn I can't even do that. It says "Failed"....
I tried flashing this zip RUU with fastboot: PN07IMG_M7_U_L50_SENSE60_MR_hTC_Asia_TW_7.18.709.1 51_Radio_4T.35.3218.16_10.33Q.1718.01D_release_458 881_signed_2_4.zip
And it says FAIL file too large or something... the file is about 1.56GB
I even tried copying the RUU archive on a memory flashdrive and connect it via OTG cable. I saw on many threads on this forum suggestions that if the phone can't be flashed through a computer + fastboot, then it must be flashed via "SD card method". What in the world does this even mean? I don't understand?? M7 does NOT have a SD card slot.
Maybe the previous owner accidentally flashed a wrong rom? I don't know, all I know is that this phone consumed at least 12 hours of my time and all for nothing, I still haven't fixed it.
Can someone help me fix this phone? I would be very grateful!

Ok, forget all of that. I finally managed to flash the ROM PN07IMG_M7_U_L50_SENSE60_MR_hTC_Asia_TW_7.18.709.1 51_Radio_4T.35.3218.16_10.33Q.1718.01D_release_458 881_signed_2_4.zip, I was stunned when I was greeted with a "Success!" message in fastboot, I rebooted the phone but the phone is still not repaired. I still get bootloops, same behavior, any ideas? Should I try a different ROM? What do you recommend? The phone behaves as if I didn't flash anything....
Thanks!

myrunes said:
Ok, forget all of that. I finally managed to flash the ROM PN07IMG_M7_U_L50_SENSE60_MR_hTC_Asia_TW_7.18.709.1 51_Radio_4T.35.3218.16_10.33Q.1718.01D_release_458 881_signed_2_4.zip, I was stunned when I was greeted with a "Success!" message in fastboot, I rebooted the phone but the phone is still not repaired. I still get bootloops, same behavior, any ideas? Should I try a different ROM? What do you recommend? The phone behaves as if I didn't flash anything....
Thanks!
Click to expand...
Click to collapse
7.18.709.151 is a M7_U ruu (for the non-LTE variant).
Try with the 7.19.401.51 version and post results (a screenshot or cpoy/paste of your cmd window)
Don't forget that you must use htc_fastboot.exe to flash the ruu (not fastboot.exe form google)

alray said:
7.18.709.151 is a M7_U ruu (for the non-LTE variant).
Try with the 7.19.401.51 version and post results (a screenshot or cpoy/paste of your cmd window)
Don't forget that you must use htc_fastboot.exe to flash the ruu (not fastboot.exe form google)
Click to expand...
Click to collapse
I also tried this:
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.5 1_Radio_4T.35.3218.16_10.33Q.1718.01L_release_4588 03_signed.zip
and this
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed_2_4.zip
and it didn't work! I even unlocked the Bootloader, its all good it says "unlocked tampered" now, then installed both TWRP and CWM the phone said "OKAY" after installing but then when I go to recovery, NOTHING! It says "Entering Recovery..." then the phone goes into endless restarts. Perhaps my phone has hardware damage such as a failed NAND chip? At this stage I'm really leaning towards believing that the hardware part, (motherboard) is defective, not just software issues...
There's also a possibility that the phone was flashed with a wrong RUU and this is why its behaving like this however, no matter how wrong the RUU might have been, its still strange that with a unlocked bootloader I cannot properly install a custom recovery such as TWRP.
If Im doing something wrong then please let me know. Thanks

myrunes said:
I also tried this:
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.5 1_Radio_4T.35.3218.16_10.33Q.1718.01L_release_4588 03_signed.zip
and this
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed_2_4.zip
and it didn't work! I even unlocked the Bootloader, its all good it says "unlocked tampered" now, then installed both TWRP and CWM the phone said "OKAY" after installing but then when I go to recovery, NOTHING! It says "Entering Recovery..." then the phone goes into endless restarts. Perhaps my phone has hardware damage such as a failed NAND chip? At this stage I'm really leaning towards believing that the hardware part, (motherboard) is defective, not just software issues...
There's also a possibility that the phone was flashed with a wrong RUU and this is why its behaving like this however, no matter how wrong the RUU might have been, its still strange that with a unlocked bootloader I cannot properly install a custom recovery such as TWRP.
If Im doing something wrong then please let me know. Thanks
Click to expand...
Click to collapse
When you phone is S-ON it must have a locked or re-locked bootloader to flash RUU. Only with S-OFF you can flash a ruu with an unlocked bootloader. TWRP should flash fine if your bootloader is unlocked. Try MDMower's universal version of twrp: https://android.cmphys.com/twrp-m7/

Try flashing this 7.19.401.51 RUU.zip file.
https://androidfilehost.com/?fid=24369303960689843
Don't forget to relock the bootloader and use htc_fastboot.exe to flash the zip