Database Develop

Silver HTC logo; only fastboot; no adb; no volume - and pwr to get to bootloader

Hey guys. Up until about two weeks ago I was enjoying Android L on my Sprint HTC One m7 with HBOOT 1.57. My battery needed replacing so I ordered the rear and front housing with digitizer and screen, along with a new battery, as I saw how beat up the phone can get when opening it to replace the battery. The battery replacement was a success, but when I turned the phone on, it would not go past the HTC boot logo. More accurately, it would go past the boot logo, show a little series of dots at the top of the phone and then go back to logo and loop over again. I figured having the motherboard off the phone for a couple weeks may have done something to internal SD, so I decided to boot into recovery only to be met with the same problem... it wouldn't get past the boot into recovery mode. So then I decided to try to run the latest RUU, and everytime I do it, it seems to fail at the point where the RUU process shows radio. Now I'm stuck on the silver HTC logo screen with four exclamation marks (one at each corner) on the screen. I can't even get to the bootloader menu on the phone to switch to fastboot. However, the phone still seems to take fastboot commands. No adb access and no direct access to the bootloader via the phone itself.
Any ideas on how to get this working again would be very appreciated.
Here is my getvar:
C:\Users\Bell\Desktop\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0515
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(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: 4272mV
(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
all: Done!
finished. total time: 0.064s
C:\Users\Bell\Desktop\fastboot>
Here is what I get when I try to run the 5.03.651.3 RUU: (in case you can't see, it says it [12] CIR Failed-PU. The rest pass just fine.) Same thing when I run the 5.05.xxxxxx RUU.
Just to be clear: I am S-On. I have tried the two most recent RUUs with no luck. My bootloader is relocked. I am actually very seasoned with issues on the m7 but this has me stumped. I believe it has something to do with the signature failing, as seen in the screenshot below. It stops the RUUs from progressing past the signature verification.

MarkBell said:
Hey guys. Up until about two weeks ago I was enjoying Android L on my Sprint HTC One m7 with HBOOT 1.57. My battery needed replacing so I ordered the rear and front housing with digitizer and screen, along with a new battery, as I saw how beat up the phone can get when opening it to replace the battery. The battery replacement was a success, but when I turned the phone on, it would not go past the HTC boot logo. More accurately, it would go past the boot logo, show a little series of dots at the top of the phone and then go back to logo and loop over again. I figured having the motherboard off the phone for a couple weeks may have done something to internal SD, so I decided to boot into recovery only to be met with the same problem... it wouldn't get past the boot into recovery mode. So then I decided to try to run the latest RUU, and everytime I do it, it seems to fail at the point where the RUU process shows radio. Now I'm stuck on the silver HTC logo screen with four exclamation marks (one at each corner) on the screen. I can't even get to the bootloader menu on the phone to switch to fastboot. However, the phone still seems to take fastboot commands.
Any ideas on how to get this working again would be very appreciated.
Here is my getvar:
C:\Users\Bell\Desktop\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0515
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(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: 4272mV
(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
all: Done!
finished. total time: 0.064s
C:\Users\Bell\Desktop\fastboot>
Here is what I get when I try to run the 5.03.651.3 RUU:
Click to expand...
Click to collapse
Pretty please follow the rules and post in Sprint HTC One Q&A.
I guarantee people will help you there; if you post in Android Dev, I feel like you'll be turned away immediately.

I have no answer... But I do find it strange that battery maintenance (even with additional plastic maintenance) would have any effect on software. To be clearer:
are there any other events that may be relevant (like a drop, static shock, magnetized screwdriver, gouge to circuit board or wire, water, etc.), or any other event that may have damaged or corrupted what should be nonvolatile memory
Is it possible the battery is a physical fit, but in fact not meant for the phone (bad/corrupt/incompatible in someway that doesn't "break" but also doesn't work)
I assume you didn't need a soldering iron in any way... And there was no high heat source (to remove stickers, or loosen plastic, etc.) that may have allowed soldering to shift/merge
Since I personally have never changed a battery in this phone model, I am not sure if the phone cares about a battery SN, or other indicators that someone did 'factory maintenance' and perhaps there is a special step left to do to tell the phone the battery is legit... But only Apple would be that paranoid and anal.... Right?
I'm not fishing for 'I told you so', I'm just trying to help everyone help you... And can't fathom how a battery matters to the hboot or radio...
Aaron

I am certain there was no damage caused to the hardware itself. It's strictly something software related. Anyone know what that CIR Failed-PU stands for when the RUU fails to install? I've also noticed the OS is in red for some reason (see screenshot). Not sure if that is normal. Also, sorry for posting question in wrong thread. I had surgery on my Middle Ear a couple days ago (stapedectomy) so my head is still a bit swimmy, and I wasn't thinking clearly when I posted. The battery is an OEM battery with a fresher date on it versus the old battery. Exactly alike in every way, including that it came with its own pop connector and ribbon to hook up to the motherboard.
I am certain it is something software related. Just not sure. I believe it has something to do with the CIR Failed-PU error message.

I applied no heat, either, just to clarify. Was super careful about static electricity, etc. I hooked the battery up to the old housing and tried it before transferring all the internals to the newly ordered housing and it was working great. The only reason I switched to the new housing was for cosmetic reasons. But all the new parts I got are genuine. I had the motherboard off the m7 for about two weeks before transferring to the new housing (was waiting on the rear housing to be shipped). I just use this One to play around with and develop. The Note 4 is my daily driver these days. I was hoping to get this one looking new and in working order so my wife could finally join the world of Android, as she is still using an old Samsung R375c.

@BD619: Could you help me out over here? Need some detailed instructions. My current state is that the phone boots directly to the silver htc logo with four exclamation marks in each corner. None of the RUUS I have tried have worked. I double checked to ensure my bootloader was relocked before trying to run the RUU that matches my H boot version.

I can still send fastboot commands, apparently, as that is how I grabbed the getvar.

First make sure you are using the correct RUU... looks like the 5.03.651.2 or 5.05.651.2 should work.
Second if the RUU fails there should be an option to recover...follow the instructions once you click the recover button.

Tried this one: http://forum.xda-developers.com/showthread.php?t=2795856 Same problem.

MarkBell said:
Tried this one: http://forum.xda-developers.com/showthread.php?t=2795856 Same problem.
Click to expand...
Click to collapse
You might try flashing the Full Firmware first.
Try the 5.03 RUU the 5.05 seems to be hit or miss whether it works or not

Do you mean Sprint_HTC_One_m7wls_5.03.651.3_RUU.zip? If so, I have no success with that one either

And I did extract before running the wizard as directed.

MarkBell said:
And I did extract before running the wizard as directed.
Click to expand...
Click to collapse
Try flashing the full firmware then try the RUU

OK. That I haven't tried yet, but I will do it first thing in the morning. Gotta get the kiddo in bed before Santa gets here. Thanks for the help so far.

MarkBell said:
OK. That I haven't tried yet, but I will do it first thing in the morning. Gotta get the kiddo in bed before Santa gets here. Thanks for the help so far.
Click to expand...
Click to collapse
No worries Merry Xmas.

Still haven't had a chance to test your recommendation. Will probably have time tomorrow. Xmas season is crazy, and even more so when you just had a prosthetic bone implanted in your middle ear two days ago. Lol.

Didn't work, unfortunately. I'm beginning to wonder if despite all precautions I've borked the internal SD during my repair. I was so so careful, though. Even wore a bracelet that kept me grounded. Stored everything in bubble tape...

Strange things continuing. Can't even get to the bootloader menu but all fastboot commands are responding. Ie. I just unlocked the bootloader and I am gonna try to flash TWRP.

I still only get the silver HTC screen with the exclamation marks in the four corners.

Can't flash TWRP. Got the old 12 signature verify failed. Is there a command that will allow me to test the state of my phone's internal storage?

[Q] Cannot install any ROM's at all, but can access bootloader.

Hi guys, my first post on here, sorry it has to be a request for help.. I've read through a mountain of threads about M7 issues, but none seem to match my issue, so I figure I can only ask.
Oh, by the way, I am very much a novice at this, so I may need things to be explained in a little more detail than some. I'm not a total noob as I have modded a few other phones in the past.
I have an HTC One M7 and decided I wanted to flash a different ROM. I went to HTCDEV and went through the process to unlock the bootloader. This went flawlessly.
I then installed TWRP 2.6.3.3 in fastboot. Again no problems.
I have an OTG cable (with external power).
I made a backup with TWRP which went ahead without error.
I then did a test flash of ViperOne 6.2.0 which went without issue, but ultimately I wanted to flash ARHD 91.1 (Lollipop 5.0.2).
My problem is that after ViperOne 6.2.0 I can no longer install ANY ROM at all. It says installing but then TWRP returns to the main menu with no error mentioned. I'm sure it's something I've done, just don't know what. After a few failed flashes I did format various partitions, and I suspect I flumped something at this point!?!
It's like the all the partitions on the phone are locked. And everytime I exit TWRP it says you have no OS installed and also says I'm not rooted and do I want to install SuperSU. I say yes everytime, but it will ask the next time still.
It's got to the point that I've ran out of ideas, so I hope there is someone that may have an idea.
So to summarise,
I have an unlocked bootloader.
I am still S-ON as I have HBOOT 1.57 and Rumrunner wont work.
I have no ROM installed, so cannot boot the phone into anything but fastboot and recovery (I can still flash different recovery environments from fastboot)
Hopefully someone may have an idea. Thanks very much in advance.

Loafmanuk said:
Hi guys, my first post on here, sorry it has to be a request for help.. I've read through a mountain of threads about M7 issues, but none seem to match my issue, so I figure I can only ask.
Oh, by the way, I am very much a novice at this, so I may need things to be explained in a little more detail than some. I'm not a total noob as I have modded a few other phones in the past.
I have an HTC One M7 and decided I wanted to flash a different ROM. I went to HTCDEV and went through the process to unlock the bootloader. This went flawlessly.
I then installed TWRP 2.6.3.3 in fastboot. Again no problems.
I have an OTG cable (with external power).
I made a backup with TWRP which went ahead without error.
I then did a test flash of ViperOne 6.2.0 which went without issue, but ultimately I wanted to flash ARHD 91.1 (Lollipop 5.0.2).
My problem is that after ViperOne 6.2.0 I can no longer install ANY ROM at all. It says installing but then TWRP returns to the main menu with no error mentioned. I'm sure it's something I've done, just don't know what. After a few failed flashes I did format various partitions, and I suspect I flumped something at this point!?!
It's like the all the partitions on the phone are locked. And everytime I exit TWRP it says you have no OS installed and also says I'm not rooted and do I want to install SuperSU. I say yes everytime, but it will ask the next time still.
It's got to the point that I've ran out of ideas, so I hope there is someone that may have an idea.
So to summarise,
I have an unlocked bootloader.
I am still S-ON as I have HBOOT 1.57 and Rumrunner wont work.
I have no ROM installed, so cannot boot the phone into anything but fastboot and recovery (I can still flash different recovery environments from fastboot)
Hopefully someone may have an idea. Thanks very much in advance.
Click to expand...
Click to collapse
ok first of all, you need to use TWRP latest for Lollipop custom roms, 2.6.3.3 is too old, use 2.8.6.0, also, expect problems with Lollipop roms whilst your still on KitKat firmware (hboot 1.57), you really need to be on Lollipop firmware to use Lollipop custom roms.
People using the latest Lollipop custom roms on KK firmware are reporting no wifi, Bluetooth issues etc.
can you post your fastboot getvar all please without imei and serial number please.

Hi, thanks for the quick response.
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.16.61.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ************
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4275mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I hope this shows something up.
I really appreciate your help.

BTW, I tried TWRP 2.8.6.0, but it wont read from the external USB stick like 2.6.3.3 does!?! Plus I can't install CM11 or 12 either, so it,s not just newer ROM's.

Loafmanuk said:
Hi, thanks for the quick response.
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.16.61.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ************
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4275mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I hope this shows something up.
I really appreciate your help.
Click to expand...
Click to collapse
yup shows me a lot of info: 6.16.61.8 this shows me your on Orange UK network, although its now T-Mo & Orange together as EE, sorry but they've not released the Lollipop update yet for the 61's which is the 3rd set of numbers pulled from that long number above, this also confirms your on orange UK ORANG001 and so does this: PN0710000 kind of......... long story
m7_ul this tells me you have the LTE version of the M7
4275mV battery info = good
4T.28.3218.04 radio version
1.57.0000 hboot version
(bootloader) security: on (bootloader) build-mode: SHIP PVT SHIP S-ON basically your s-on
it would show your imei number and serial number too, but you want to keep those 2 numbers to yourself.
---------- Post added at 06:40 PM ---------- Previous post was at 06:36 PM ----------
Loafmanuk said:
BTW, I tried TWRP 2.8.6.0, but it wont read from the external USB stick like 2.6.3.3 does!?! Plus I can't install CM11 or 12 either, so it,s not just newer ROM's.
Click to expand...
Click to collapse
plug your phone into the computer whilst its booted into recovery main screen only, the internal storage of your phone should open on your computer, copy the rom.zip to your internal storge, unplug and flash it.
I'm pretty sure 2.8.6.0 supports usb otg, you may have to select it as a storage option first as it defaults to internal storage, cant quite remember as I'm on an M8 now.
edit: yes it does, select install and then at the top change from internal storage to usb otg.

I've re installed TWRP 2.8.6.0 and finally got it to see the USB stick (reformatted it). But when I try and install it seems to be going ahead, but after a minute or to I get the TeamWin splash screen flash up as though recovery is booting and it returns to the main menu. Oddly, the LED on the memory stick is still flashing!?!
I'll try installing from the phones internal memory like you suggested and hopefully that will work. Thank you so much for this, I'll update in a while.

Okay, I've got the ROM on the internal storage and am currently trying to install it. It has gone through to suggest it has installed so I am rebooting...
It has got further than I have with the OTG all day, so I have my fingers crossed...
Waiting...
Waiting...
And we have lift off, wow! It installed fine that time, thank bacon for that! I really didn't need the expense of getting another phone at the moment, what with car insurance, van insurance, van tax, and all the other bits I've just forked out for.. I would have been phoneless (and possibly homeless!) for the next several weeks!
So it was perhaps a dodgy flash drive or OTG cable maybe? Strange that it worked before.
I can not thank you enough! Strangely I did try to put the ROM on the internal storage earlier, but it said the ROM file was too large to transfer to internal storage!? Not sure why it suddenly let me, but very happy it has! Thank you again, without your suggestion I probably wouldn't have bothered trying that method again. :victory:
You're awesome.

Loafmanuk said:
Okay, I've got the ROM on the internal storage and am currently trying to install it. It has gone through to suggest it has installed so I am rebooting...
It has got further than I have with the OTG all day, so I have my fingers crossed...
Waiting...
Waiting...
And we have lift off, wow! It installed fine that time, thank bacon for that! I really didn't need the expense of getting another phone at the moment, what with car insurance, van insurance, van tax, and all the other bits I've just forked out for.. I would have been phoneless (and possibly homeless!) for the next several weeks!
So it was perhaps a dodgy flash drive or OTG cable maybe? Strange that it worked before.
I can not thank you enough! Strangely I did try to put the ROM on the internal storage earlier, but it said the ROM file was too large to transfer to internal storage!? Not sure why it suddenly let me, but very happy it has! Thank you again, without your suggestion I probably wouldn't have bothered trying that method again. :victory:
You're awesome.
Click to expand...
Click to collapse
you are very welcome, I just use my USB OTG for backup's and restores, never tried flashing a rom from it.

Used phone from Africa, EFS partition likely formatted, no backup, what can i do?

*I will try to provide as much information as I can, so this will probably be a long post. Sorry!*
Hi,
I've bought a used HTC One M7 from Ghana because I needed a replacement phone while I was working there. I noticed it didn't have a factory ROM on it, but I figured I would change that anyway. So I bought it.
First problem with it was a well documented issue with HTCs and their conflict with Google Play Services which resulted in the malfunctioning of voice calling. Since it wasn't a stock ROM, i was unable to get the OTA updates that eventually fixed this bug.
So I decided to flash a custom ROM on it.
The phone had SuperCID and was S-off. It turns out it was a US Sprint version, although its back cover had an ATT logo. Who knows what was done to this phone. Anyway, since I am far from being an expert at flashing custom ROMs and custom recoveries, I asked a friend to help.
He managed to install TWRP and a Cyanogen 12 nightly ROM (12-20151108-NIGHTLY-m7spr) but in the process something must have happened because now, even though the phone works fine and boots fine, it doesn't recognise my sim card and there is no network signal.
When I realised that the baseband, IMEI, MEID, ICCID and a few others said "unknown" instead of their values, i dug through this forum and concluded that the EFS partition must have been erased or damaged in the process. (is there a way to confirm that?) There was no backup, obviously.
I have read bits and pieces of information about this problem, but nothing that seemed helpful in my particular case.
I can't flash any other ROM on it because it says the MD-5 file is missing or something like this.
So I am stuck with an almost working phone, and no solution to my problem. I even called HTC service and they said they will not fix a phone sold in the US, since I live in Romania.
So this is basically my only hope of getting this phone to work again. If even possible. So, please, in layman terms, what can I do?
Thank you!

tudorv said:
*I will try to provide as much information as I can, so this will probably be a long post. Sorry!*
Hi,
I've bought a used HTC One M7 from Ghana because I needed a replacement phone while I was working there. I noticed it didn't have a factory ROM on it, but I figured I would change that anyway. So I bought it.
First problem with it was a well documented issue with HTCs and their conflict with Google Play Services which resulted in the malfunctioning of voice calling. Since it wasn't a stock ROM, i was unable to get the OTA updates that eventually fixed this bug.
So I decided to flash a custom ROM on it.
The phone had SuperCID and was S-off. It turns out it was a US Sprint version, although its back cover had an ATT logo. Who knows what was done to this phone. Anyway, since I am far from being an expert at flashing custom ROMs and custom recoveries, I asked a friend to help.
He managed to install TWRP and a Cyanogen 12 nightly ROM (12-20151108-NIGHTLY-m7spr) but in the process something must have happened because now, even though the phone works fine and boots fine, it doesn't recognise my sim card and there is no network signal.
When I realised that the baseband, IMEI, MEID, ICCID and a few others said "unknown" instead of their values, i dug through this forum and concluded that the EFS partition must have been erased or damaged in the process. (is there a way to confirm that?) There was no backup, obviously.
I have read bits and pieces of information about this problem, but nothing that seemed helpful in my particular case.
I can't flash any other ROM on it because it says the MD-5 file is missing or something like this.
So I am stuck with an almost working phone, and no solution to my problem. I even called HTC service and they said they will not fix a phone sold in the US, since I live in Romania.
So this is basically my only hope of getting this phone to work again. If even possible. So, please, in layman terms, what can I do?
Thank you!
Click to expand...
Click to collapse
First of all, sprint phones are CDMA phone. Once the sim is unlocked, it will work on GSM but you'll not get full connectivity i.e probably no LTE.
Is the IMEI MEID and Baseband correctly displayed when using "fastboot getvar all"? Also post the output of "fastboot getvar all" (don't shate your imei and meid). Sometimes, flashing a RUU can fix this problem, in some other cases its caused by an hardware defect.
And btw, HTC phone does not have an EFS partition.

alray said:
First of all, sprint phones are CDMA phone. Once the sim is unlocked, it will work on GSM but you'll not get full connectivity i.e probably no LTE.
Is the IMEI MEID and Baseband correctly displayed when using "fastboot getvar all"? Also post the output of "fastboot getvar all" (don't shate your imei and meid). Sometimes, flashing a RUU can fix this problem, in some other cases its caused by an hardware defect.
And btw, HTC phone does not have an EFS partition.
Click to expand...
Click to collapse
Thank you for your reply. I will get the information you mentioned and I will reply again as soon as I have it. If the HTCs don't have that partition, then this gives me a bit of hope, since I am sure that the baseband, IMEI and all the others were there before I flashed the CyanogenMod. So it might not be a hardware issue.
Thanks!

alray said:
First of all, sprint phones are CDMA phone. Once the sim is unlocked, it will work on GSM but you'll not get full connectivity i.e probably no LTE.
Is the IMEI MEID and Baseband correctly displayed when using "fastboot getvar all"? Also post the output of "fastboot getvar all" (don't shate your imei and meid). Sometimes, flashing a RUU can fix this problem, in some other cases its caused by an hardware defect.
And btw, HTC phone does not have an EFS partition.
Click to expand...
Click to collapse
Sorry for the delay. Overworking and having to do everything on a Mac makes these things a bit harder. Basically I have to read tutorials for every step I do. So..
I finally was able to get the fastboot command a try. You were right. The IMEI and MEID are there, but the baseband is not. What does that mean? Flashing a RUU will fix this? Can you point me to the right RUU to flash so I don't brick this troublesome phone?
Thank you again for your help. If anybody else has any suggestions, I'd love to hear them. Thanks!
Here's the fastboot result:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA34KS901953
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: XXXXXXXXXXXXX
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4107mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

tudorv said:
Sorry for the delay. Overworking and having to do everything on a Mac makes these things a bit harder. Basically I have to read tutorials for every step I do. So..
I finally was able to get the fastboot command a try. You were right. The IMEI and MEID are there, but the baseband is not. What does that mean? Flashing a RUU will fix this? Can you point me to the right RUU to flash so I don't brick this troublesome phone?
Thank you again for your help. If anybody else has any suggestions, I'd love to hear them. Thanks!
Here's the fastboot result:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA34KS901953
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: XXXXXXXXXXXXX
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4107mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
Try to flash the latest sprint RUU:
http://dl3.htc.com/application/RUU_...1.10.exe?_ga=1.245824013.849696128.1459511845

alray said:
Try to flash the latest sprint RUU:
http://dl3.htc.com/application/RUU_...1.10.exe?_ga=1.245824013.849696128.1459511845
Click to expand...
Click to collapse
Just wanted to let everyone know that it worked. I was able to flash a Sprint RUU (not the one from their website, because the exe utility crashed at some point. don't ask me why) I flashed a zip RUU using fastboot. Just like that. In two minutes I had my phone back.
So, again, thank you very much for your help.
T.

Deleted everything thread, for Bestbuy Blue At&t M7, can anyone help me fix this?

I have searched for the last 2 days a couple hours a day, but nothing seems to be working.
The issue is that when I go to usb-fastboot mode the computer can not recongize the device so I have no way to "re lock it" to use RUU
The next issue is that HTCDEV hasn't updated their RUU for windows 10 and I cant even run the installer, not that it matters, I know it would fail because of the first issue.
The third issue is that when I go into TWRP recovery mode I have the option to mount, when I click it my phone simple restarts, and if I am not quick enough it tries to normal boot and I have to wait for it to drain the battery to zelch to restart the process. (Because I can't power off from the white (w/ green logo) HTC screen )
I was trying to factory reset my phone, I actually clicked factory reset from the bootloader menu and it opened up TWRP recover mode, I clicked "full whipe" and it gave me some warning, and I decided it was best to use advance whipe, my phone is S-on and I had tried to root it many times all failures due to s-on prevent system files from changing... so I figured I could just check everything and S-on would prevent anything from being deleted that I needed..
Welp, I was wrong, and to top it off I didn't get a warning saying "This WILL wipe the OS spite the fact that your phone doesn't allow editing of system files" Honestly I didn't even know it was possible, and I don't have a back up saved on my computer as I never really needed to back anything up, I just wanted to factory reset my phone, because it was "unlocked" and I coudlnt play pokemon go.
I also didn't know it was because that it was unlocked I couldn't play pokemon go, I thought it was because if SuperSu ( that I refused to pay for, and spite following many guides, could not uninstall ( due to S-on))
So my experience with the stubborn s-on left me feeling as if my phone was invincible, to only find out that the safety net really didnt work that way.
So now I can't mount my phone else it restarts, and I can't fastboot-usb mode because my computer can not detect the device
I can not find any roms that are not RUU files are zip/rar for other companies, nor do I know if they are even compatible.
I found many threads like this but none with a resolution, but I seen a comment on a samsung page from 2 years ago of somsone saying they had done exactly what I described and had it fixed in a few hours, but I have had no luck , I figure there must be something I don't know or not doing that is really obvious.
Finally I tried to use Hasoons AIO kits but none of the download links work, and currently I am running at 100% cpu from all the fake download buttons I clicked, so I imagine I have virus hunting to do later, so I am a little tired and not sure where to go to resolve this issue or if Hasoons AIO even would help at this point.
What I do have is TWRP recovery mode, and a USB.
Starting from there can some help me out?

There are so much false statements/misinformation here that I don't know where to start... I'll just write in red in the below quote:
kiaph said:
I have searched for the last 2 days a couple hours a day, but nothing seems to be working.
The issue is that when I go to usb-fastboot mode the computer can not recongize the device so I have no way to "re lock it" to use RUU
The next issue is that HTCDEV hasn't updated their RUU for windows 10 and I cant even run the installer, not that it matters, I know it would fail because of the first issue.
HTCdev.com are no longer providing RUU, and its not something new, iirc they stopped in 2014. The only place where you can get RUU from HTC is http://www.htc.com/us/support/rom-downloads.html. Otherwise there are other places where you can find RUU like the sticky thread in the general sections (or directly on androidfilehost.com)
Don't really understand "hasn't updated their RUU for windows 10" because nothing need to be updated in order for ruu.exe to run on Windows 10. If its not working there is probably something wrong on your side. Anyway you'll probably be dealing with ruu.zip so it's not really importantto find why.
The third issue is that when I go into TWRP recovery mode I have the option to mount, What partition are you talking about? when I click it my phone simple restarts, and if I am not quick enough it tries to normal boot and I have to wait for it to drain the battery to zelch to restart the process. (Because I can't power off from the white (w/ green logo) HTC screen )
I was trying to factory reset my phone, I actually clicked factory reset from the bootloader menu and it opened up TWRP recover mode, I clicked "full whipe" and it gave me some warning, and I decided it was best to use advance whipe, my phone is S-on and I had tried to root it many times all failures due to s-on prevent system files from changing... S-ON is not needed to root and the system partition isn't protected by S-ON, unlocking the bootloader gives you full access of recovery, boot, system and radio partitions. The only thing left protecting the /system partition once the bootloader is unlocked is the stock kernel which isn't booted yet when in TWRP recovery (will only protect the /system partition when booted in the OS). so I figured I could just check everything and S-on would prevent anything from being deleted that I needed..
Welp, I was wrong, and to top it off I didn't get a warning saying "This WILL wipe the OS spite the fact that your phone doesn't allow editing of system files" First screen you got when booting in TWRP for the first time is a screen asking you if you want to keep your system partition in read only mode or ask you to swipe the bottom slider to allow system modification. Also first warning you'll get from HTC when unlocking the bootloader is that it will allow you to install custom operating system... so yes your /system partition is fully accessible once bootloader unlocked. Honestly I didn't even know it was possible, and I don't have a back up saved on my computer as I never really needed to back anything up, I just wanted to factory reset my phone, because it was "unlocked" and I coudlnt play pokemon go. Doing a factory reset will not relock your phone. A factory reset = wiping the /data partition. wiping /data is what you want to do with a custom recovery if you only want to "factory reset"
I also didn't know it was because that it was unlocked I couldn't play pokemon go, I thought it was because if SuperSu ( that I refused to pay for and you're not forced to pay for it btw, payment is completely optional, more like a donation... and that's exactly what is said on supersu page from the playstore, and spite following many guides, could not uninstall ( due to S-on)) Not S-ON related. Can be uninstalled from twrp using the uninstaller zip or manually. Uninstalling from the OS won't work since supersu is a system app and that the stock kernel is protecting the /system partition from modification when booted in the OS.
So my experience with the stubborn s-on left me feeling as if my phone was invincible, to only find out that the safety net really didnt work that way. The only way your phone can be "invincible" user bad actions is when it's S-ON and bootloader Locked. S-ON is protecting other crucial partition, yes much more important than your OS.
So now I can't mount my phone else it restarts, and I can't fastboot-usb mode because my computer can not detect the device
I can not find any roms that are not RUU files are zip/rar for other companies, nor do I know if they are even compatible.
I found many threads like this but none with a resolution, but I seen a comment on a samsung page from 2 years ago of somsone saying they had done exactly what I described and had it fixed in a few hours, but I have had no luck , I figure there must be something I don't know or not doing that is really obvious.
Finally I tried to use Hasoons AIO kits but none of the download links work, and currently I am running at 100% cpu from all the fake download buttons I clicked, so I imagine I have virus hunting to do later, so I am a little tired and not sure where to go to resolve this issue or if Hasoons AIO even would help at this point. Outdated toolkit, buttons are not fake buttons. Fastboot and adb commands is what you need to use.
What I do have is TWRP recovery mode, and a USB.
Starting from there can some help me out?
Click to expand...
Click to collapse
You'll need to find a way to communicate with your phone in fastboot usb mode. Make sure you have the latest HTC drivers installed and that no other drivers/app is interfering (i.e HTC sync). What is yout bootloader version? If your phone is running 1.44 you'll need a win7 pc (or linux/mac). Once you can communicate with your phone in fastboot mode, post the output of "fastboot getvar all" so we can know what we are dealing with exactly. You should also post every info from the bootloader screen.

Reply to helpful guy above
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4M.32.3218.06
OpenDSP-v35.120.274.0718
OS-7.23.502.9
eMMC-boot 2048MB
Apr 14 2016,23:32:50.0
C:\Android\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4M.32.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.23.502.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT391W901875
(bootloader) imei: 354439057007348
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4307mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.054s
Thank you for long response, sorry I was so miss informed, I gathered a lot of data from personal experience, and from many post ranging anywhere from 1y to 4y old so it all just became a coherrent mess, thanks again for your time emphasizing keyfacts for me

kiaph said:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4M.32.3218.06
OpenDSP-v35.120.274.0718
OS-7.23.502.9
eMMC-boot 2048MB
Apr 14 2016,23:32:50.0
C:\Android\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4M.32.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.23.502.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT391W901875
(bootloader) imei: 354439057007348
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4307mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.054s
Thank you for long response, sorry I was so miss informed, I gathered a lot of data from personal experience, and from many post ranging anywhere from 1y to 4y old so it all just became a coherrent mess, thanks again for your time emphasizing keyfacts for me
Click to expand...
Click to collapse
Sorry for late reply, I see you've posted in the RUU thread, is your phone working now?

Yes it is, thanks to you once I could communicate with it the rest came down to searching this forums
Though its battery life has some how taken a mega hit :/

Touch only working in TWRP - no response on any ROM

Dear beloved XDA community,
I was deep downunder with my personal life the past half year and likely lost a lot friends as well as access to the project my heart still beats for: AIMSICD. My secret dream is to continue work there this year.
My issue: In an attempt to slowly crawl my way back into the Android world, I am currently tinkering with a phone of a friend of mine, who had messed up his ROM. After a full wipe and a fresh instal of the unofficial LineageOS 14.1, it appears that the touch screen does not respond on any ROM that I try - but in recovery mode on TWRP everything works fine. Therefore, I guess that no connector cables are broken. But I am out of ideas and it never happened to me that no ROM detects the touch, yet TWRP does. What is your suggestion to solve this? Added information about this unlocked, but S-ON phone:
[email protected]:~$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.101.1102.17.0506
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.16.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: mem_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P8B20000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ea702fb0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.008s
Click to expand...
Click to collapse
Sending some love and inner peace to everyone who still knows me!

SecUpwN said:
Dear beloved XDA community,
I was deep downunder with my personal life the past half year and likely lost a lot friends as well as access to the project my heart still beats for: AIMSICD. My secret dream is to continue work there this year.
My issue: In an attempt to slowly crawl my way back into the Android world, I am currently tinkering with a phone of a friend of mine, who had messed up his ROM. After a full wipe and a fresh instal of the unofficial LineageOS 14.1, it appears that the touch screen does not respond on any ROM that I try - but in recovery mode on TWRP everything works fine. Therefore, I guess that no connector cables are broken. But I am out of ideas and it never happened to me that no ROM detects the touch, yet TWRP does. What is your suggestion to solve this? Added information about this unlocked, but S-ON phone:
Sending some love and inner peace to everyone who still knows me!
Click to expand...
Click to collapse
seems like a simple bad flash.
download the ROM again (just in case) and dont forget to Fully wipe your device from Recovery (Data, Dalvik and Cache!) and them install the LineageOS again.

Thank you for taking the time to answer, @kativiti. No, the strange thing is that no matter which custom OS has been installed, touch does not work - except for when I install the stock ROM. I now finally achieved S-OFF and Super-CID on the HTC One Mini 2 using SunShine in order to upgrade the firmware and everything, then did a full wipe of everything and installed Lineage OS 14.1 again. Same result. I wonder why the stock ROM is detecting touch correctly, but nothing else is?

UPDATE: I've just installed NomostroPop and touch works perfectly! So this really must be a driver Issue, I'm hoping that @nightcore500 updates his unofficial LineageOS 14.1 with the Himax touchscreen driver.

Which build of TWRP do you use?
And does your device feature the Himax touchscreen?
TWRP 3.0.2 by @nightcore500 does not yet support the Himax touchscreen (LOS 14.1 does!), so I assume you are on an older build, as this would contradict your experience.
Flashing LOS 14 with TWRP 2.x might cause problems and could be the reason.

Thanks for chiming in, @stkl. The problem has been identified and is about to be solved.