yashsingh1/xdaforums huggingface dataset:
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
The post you quoted is over a year old you may not get a response. What exactly is your issue maybe I can help?
[One (M7) Q&A, Help & Troubleshooting] jakir01:
Hi,

Thankyou for your replay.

Phone details:

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.54.0000

(bootloader) version-baseband: 4A.21.3263.04

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main:

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno: xxxxxxxxxxx

(bootloader) imei: xxxxxxxxxxxxxxxx

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0710000

(bootloader) cidnum: HTC__J15

(bootloader) battery-status: good

(bootloader) battery-voltage: 4284mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-d16dc66985

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

Currently no OS installed on my system.

Trying to install through adb sideload (i.e. cyanogenmod 10.2, cyanogenmod 11) os installed but keep restarting in a minutes.

Trying to install through adb push (Stock Rom from Android Revolution HD site One_5.11.401.10_odexed and Guru_Reset_M7_2.24.401.8) installed successfully but keep restarting from HTC One with Beats Logo.

Try to reset with RUU Zip M7_UL_JB_50_HTC_Europe_1.29.401.16 but signature verified failed with boot loader unlock. When boot loader lock error code 99 unknown error.

Waiting for your replay.
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
Did you flash a new recovery before this problem started? What recovery do you have currently?

I'm gonna guess TWRP 2.7.1.1?
[One (M7) Q&A, Help & Troubleshooting] jakir01:
I was on ARHD since last four month. Then suddenly the phone restarting from boot logo.

Now I have TWRP 2.6.3.
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
Do you erase cache after flashing recovery, your problem seems to be an issue with dirty recovery cache causing boot loops.

When you flash recovery you should

fastboot flash recovery "name-of-recovery".img
fastboot erase cache

If you don't erase cache after flashing recovery it can cause the kind of boot loops. You may not need to flash recovery again so just connect fastboot usb and run the Fastboot erase cache command and see if it improves.
[One (M7) Q&A, Help & Troubleshooting] jakir01:
I did that with stock recovery as well as TWRP but no luck.
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
Ok good, so possibly could be some sort of partition error.

Boot your phone into recovery and connect usb.

adb devices

to check for connection

adb shell
e2fsck -fvy mmcblk0p35
e2fsck -fvy mmcblk0p36
e2fsck -fvy mmcblk0p37

exit

Reboot check for improvement.
[One (M7) Q&A, Help & Troubleshooting] jakir01:
G:\Fastboot>adb devices

List of devices attached

HT378W902007 recovery

G:\Fastboot>adb shell

~ # ←[6ne2fsck -fvy mmcblk0p35

e2fsck -fvy mmcblk0p36

e2fsck -fvy mmcblk0p37e2fsck -fvy mmcblk0p35

e2fsck 1.41.14 (22-Dec-2010)

e2fsck: No such file or directory while trying to open mmcblk0p35

Possibly non-existent device?

~ # e2fsck -fvy mmcblk0p36

e2fsck 1.41.14 (22-Dec-2010)

e2fsck: No such file or directory while trying to open mmcblk0p36

Possibly non-existent device?

~ # ←[6n
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
Sorry my bad should be

e2fsck -fvy dev/block/mmcblk0p35
e2fsck -fvy dev/block/mmcblk0p36
e2fsck -fvy dev/block/mmcblk0p37
[One (M7) Q&A, Help & Troubleshooting] jakir01:
G:\Fastboot>adb shell

~ # ←[6ne2fsck -fvy dev/block/mmcblk0p35

e2fsck -fvy dev/block/mmcblk0p35

e2fsck 1.41.14 (22-Dec-2010)

Pass 1: Checking inodes, blocks, and sizes

Pass 2: Checking directory structure

Pass 3: Checking directory connectivity

Pass 4: Checking reference counts

Pass 5: Checking group summary information

2834 inodes used (2.39%)

26 non-contiguous files (0.9%)

2 non-contiguous directories (0.1%)

# of inodes with ind/dind/tind blocks: 0/0/0

Extent depth histogram: 2546/1

442597 blocks used (93.15%)

0 bad blocks

0 large files

2466 regular files

80 directories

0 character device files

0 block device files

0 fifos

0 links

279 symbolic links (279 fast symbolic links)

0 sockets

--------

2825 files

~ # ←[6ne2fsck -fvy dev/block/mmcblk0p36

e2fsck -fvy dev/block/mmcblk0p36

e2fsck 1.41.14 (22-Dec-2010)

e2fsck: Device or resource busy while trying to open dev/block/mmcblk0p36

Filesystem mounted or opened exclusively by another program?

~ # ←[6ne2fsck -fvy dev/block/mmcblk0p37

e2fsck -fvy dev/block/mmcblk0p37

e2fsck 1.41.14 (22-Dec-2010)

e2fsck: Device or resource busy while trying to open dev/block/mmcblk0p37

Filesystem mounted or opened exclusively by another program?

~ # ←[6n
[One (M7) Q&A, Help & Troubleshooting] sethishivam5:
I did that only. , I dragged the file from folder and dropped it after writing fastboot flash zip

I don't know whether I'm properly using drag and drop confused!
[One (M7) Q&A, Help & Troubleshooting] alray:
then simply type everything yourself:

fastboot flash zip your_file_name.zip
[One (M7) Q&A, Help & Troubleshooting] sethishivam5:
I did that only but it's still I'm getting errors!
[One (M7) Q&A, Help & Troubleshooting] sethishivam5:
Still getting error bootloader signature failed
[One (M7) Q&A, Help & Troubleshooting] fuanax:
can someone help me i bricked my htc one m7 after installing superSU v1.65 with twrp. it keeps rebooting to recovery.

info about the phone:

*Htc m7 s-on

*Hboot 1.61

* OS 7.18.111.51

tried to flash recovery recovery 2.24.401.8.img didn't help
[One (M7) Q&A, Help & Troubleshooting] alray:
would you please post a screenshot or copy/paste your command windows when you get errors? Its hard to tell whats wrong without any information. Is your bootloader locked, relocked or unlocked?

---------- Post added at 06:33 AM ---------- Previous post was at 06:30 AM ----------

You must use 2.46 on lollipop, anything below that will make your phone bootloop. Try to reflash the correct version, if it still bootlooping after that you'll need to reflash your rom.

Why 2.24.401.8? Your phone is running 7.18.111.51..... so you need 7.18.111.51.

If reflashing the correct supersu didn't help then flash this ruu: https://www.androidfilehost.com/?fid=24385226645962876

---------- Post added at 06:39 AM ---------- Previous post was at 06:33 AM ----------

Then better to ask in the M8 forum, not M7.

Probably resetting everything to stock with RUU could fix your problem...
[One (M7) Q&A, Help & Troubleshooting] theevildevil:
Hi. My M7 is rooted, S-Off, running TWRP (2850 i guess) and Android Revolution 93.0. Its an AT&T device. Sorry but no idea of PID nor CID (didnt store it)

Everything was working fine and one fine day, the phone just died. Wont turn on, doesnt indicate the LED light when plugged in. Tried fooling the proximity sensor but didnt work. From what i read, the phone is soft bricked.

There is an unbrick package here but its on Linux. Anything available on Windows 8.1 or 10 ?
[One (M7) Q&A, Help & Troubleshooting] alray:
This is only avaialbe on linux and will only work if your phone went in qususb_dload mode after flashing a bad firmware. Is your phone is qhsusb_dload mode? If yes and if it went in this mode by itself then its an hardware failure.
[One (M7) Q&A, Help & Troubleshooting] theevildevil:
Oh darn! Thank you for the reply. No, I wasnt flashing anything. Just died on its own. I suspected fooling the proximity sensor would revive this piece for the nth time but it didnt show any sign of life! The only sign it shows is the USB plugin and plug off sound the PC makes when I plug the device in the computer. Any chance of revival without tinkering with hardware?
[One (M7) Q&A, Help & Troubleshooting] alray:
Is it detected in your device manager when you plug it to your computer? qhsusb_dload?
[One (M7) Q&A, Help & Troubleshooting] theevildevil:
Unfortunately no :(
[One (M7) Q&A, Help & Troubleshooting] alray:
So if I understand correctly, you can't turn it on at all (screen is black) and your ocmputer makes a sound when you connect the phone to it but its not detected in windows device manager? Doesn't sound good.
[One (M7) Q&A, Help & Troubleshooting] theevildevil:
Yes thats correct. The piece has survived my 3 years of brutal usage. So I can peacefully put it to rest but any idea why it would have happened? If battery had died, it shouldn't have made the USB plugin/plugoff sound (but again, i do not claim to understand how the low level functionality of USB)
[One (M7) Q&A, Help & Troubleshooting] alray:
Well I guess it simply a dead motherboard due to worn out components or maybe a faulty battery. Looks like phones are not made to last very long anymore (well like anything else nowadays). 3 years seems a reasonable lifetime for this kind of devices, I expect mine to die soon since its also 3 years old. At this point I don't think it will worth it to open the phone and replace any component :(
[One (M7) Q&A, Help & Troubleshooting] sethishivam5:
Danny also try to do that but unfortunately got error!
[One (M7) Q&A, Help & Troubleshooting] Pradeep321:
Hello All, Anyone who can help me out??
[One (M7) Q&A, Help & Troubleshooting] alray:
Well try to unlock the bootloader (htcdev.com/bootloader), flash twrp recovery and then install a custom rom.

---------- Post added at 03:07 AM ---------- Previous post was at 03:00 AM ----------

Are you aware (just in case) that your phone variant (M7CDUG) is different than the M7_UL? Pretty much everything you'll find here is for the M7_UL (there are some exceptions) so you must make sure that you are using files (rom, recovery, etc) specifically made for the M7CDUG, if not specified, then its probably for the M7_UL and won't work on your phone.

You might want to go back to stock using this RUU, then update your phone to the latest version and try to root again from there using the correct files.
[One (M7) Q&A, Help & Troubleshooting] Pradeep321:
Thanks Alray..!!!

As advised in my last post, i'm a newbie with installing RUUs so can you provide me a step to step guide?? Would be a great help for me..!!!
[One (M7) Q&A, Help & Troubleshooting] Pradeep321:
Added to same, please provide me a link to update RUU for Lollipop and i guess below is the link through which usually the RUU is updated

http://www.andromods.com/unroot-locking/how-to-restore-to-stock-unbrick-unrooting-htc-one-m7.html
[One (M7) Q&A, Help & Troubleshooting] alray:
Simply rename the RUU file to "PN071IMG.zip", save it at the root of an external sd card (FAT32 formatted). Insert the card in your phone and reboot in bootloader mode. The bootloader should ask you if you want to update, select yes.

Another method is by using fastboot commands.

Make sure the ruu zip file is in the same folder where you have fastboot installed on your computer

Boot your phone in bootloader mode and select the "fastboot" menu so you see "FASTBOOT USB" in red.

Open a command window from your fastboot folder

fastboot oem rebootRUU
fastboot flash zip file_name.zip
fastboot reboot

replace "file_name.zip" by your ruu file name
[One (M7) Q&A, Help & Troubleshooting] Pradeep321:
Do i need to relock my Bootloader for these steps??
[One (M7) Q&A, Help & Troubleshooting] alray:
No because your phone is s-off.
[One (M7) Q&A, Help & Troubleshooting] fuanax:
Many thanks! Worked like a charm (when you say it like that i thought well thaa dumb question, but i'm not familiar with these bootloaders, rom't etc. haha)

off topic is there an easy/ safe way with my version (lolipop , s-on) to root my Phone?
[One (M7) Q&A, Help & Troubleshooting] sethishivam5:
I think in this condition I can't even unlock my bootloader! If I can. I would have done it earlier but unfortunately it's s-on plus bootloader locked.

Danny told me that he's gonna contact you upon this! We had remote session
[One (M7) Q&A, Help & Troubleshooting] Pradeep321:
Hi Alray,

As advised in your Above written steps, i tried to follow them both but neither the bootloader install the RUU nor does the cmd works up.

While running with the cmd commands it always say, waiting for device but in fastboot mode on phone, it says "Fastboot AC"

What else can be done??
[One (M7) Q&A, Help & Troubleshooting] bayusuputra:
Hi guys, I really need your help.

My M7 suddenly died. It is totally stock with locked bootloader and S-On. When I connect it to my charger, the phone's LED lights up and I can feel some vibrations. But the screen is dark.

At first I thought it is the screen that dies out, but after looking at the screen using flashlight, I can see that actually the screen is turning on, but the backlight is off (screen is very dim). The phone cannot go past the HTC logo (it doesn't even go into bootanimation) before turning itself off and on to the HTC logo again. I've managed to go into bootloader screen but cannot go into recovery. I've tried running the latest RUU (correct one, my MID is PN0714000 and CID HTC__044 i.e. Asian WWE RUU) but to no avail. It will not boot up and just goes into HTC logo screen and starts doing that on-off sequence again. I've tried to unlock the bootloader hoping that I can install custom recovery, but again, it will just do bootloop (without even going into the bootanimation screen). Turning the phone off and plugging it into the charger will turn it on and make it goes into the loop sequence again.

So, the only thing I can boot up into is the bootloader, and that is with a very dim screen. I guess my hardware is still okay since it can still boot up into bootloader. But other than that, it's a very expensive brick.

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.61.0000

(bootloader) version-baseband: 4T.35.3218.16

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 7.21.707.5

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno: ***************

(bootloader) imei: *************

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0714000

(bootloader) cidnum: HTC__044

(bootloader) battery-status: good

(bootloader) battery-voltage: 3909mV

(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
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
Power off the device. Then power it back on holding Power+Volume Up while a bright light is shining on the sensors next to the top speaker grill.

It could be the proximity sensor preventing the screen from coming on that should sort that ?

Although the bootloop problem you describe does sound like hardware. If the RUU flashed correctly and the problem persists it normally means there's a hardware fault.

We're you successfull in unlocking the bootloader? Have you flashed a custom recovery?
[One (M7) Q&A, Help & Troubleshooting] bayusuputra:
Tried that. The screen doesn't light up. It's still dark.

I have managed to unlocked the bootloader and flash custom recovery, my bootloader is now showing "tampered and unlocked", but still I cannot enter recovery. It will always boot loop after the HTC logo screen with "entering recovery..." message. I would then have to press power+voldown to get back to bootloader.

so this is how it looks like:

https://goo.gl/photos/nNKyuGyMaxiKx6Ze9
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
What recovery did you flash? Did you erase cache when flashing the recovery? i.e

fastboot erase cache
fastboot flash recovery "recovery".img
fastboot reboot-bootloader

Not erasing cache can cause recovery bootloops :good:
[One (M7) Q&A, Help & Troubleshooting] bayusuputra:
Yes, I did all those. Standard procedures...

The phone still can't boot into any other mode other than bootloader. :crying:
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
Then I guess it's some sort of emmc damage. Are you able to issue any fastboot commands.

If so try

fastboot oem last_dmesg

the output will be very long so you may need to increase buffer size to see it all. Look for emmc entry's that have errors.
[One (M7) Q&A, Help & Troubleshooting] bayusuputra:
This is what I get.

C:\android>fastboot oem last_dmesg
...
(bootloader) [8] check_ramlog_region: Backup last hboot ramlog.
OKAY [ 0.006s]
finished. total time: 0.007s
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
I expected a longer output :s

Try

fastboot oem dmesg
[One (M7) Q&A, Help & Troubleshooting] alray:
Unlock your bootloader

flash twrp recovery

flash supersu 2.46 (any version lower than that will cause bootloop)

---------- Post added at 08:02 AM ---------- Previous post was at 07:55 AM ----------

"Fastboot AC" is definitively a problem. When it this mode the phone will charge only (no data connection).

It can be caused by a bad usb cable (or using a usb cable that only have the ''power +'' and ''power -'' connections ---> no data connection)

It can also be caused by a defective usb port, either on the computer side or directly on the phone.

You must try to fix that first, everything else is useless if it doesn't say ''FASTBOOT USB'' instead of ''FASTBOOT AC''
[One (M7) Q&A, Help & Troubleshooting] Pradeep321:
But as advised by you, i tried the same with external SD card but my card is not able to mount and when i try to mount it through recovery, it says "Unable to mount external SD card"

In case if it cannot mount the memory, then it would not be possible for the bootloader to move on with further process

---------- Post added at 03:25 PM ---------- Previous post was at 02:26 PM ----------

Hii Alray

Okay, while trying with another cable, i finally got "fastboot USB" and while running the commands as advised by you, below written was the issue

C:\adb>fastboot oem rebootRUU

...

(bootloader) Start Verify: 0

OKAY [ 0.048s]

finished. total time: 0.051s

C:\adb>fastboot flash PN071IMG.zip

unknown partition 'PN071IMG.zip'

error: cannot determine image filename for 'PN071IMG.zip'

can you provide me further details or steps??

---------- Post added at 03:33 PM ---------- Previous post was at 03:25 PM ----------

My bad, i just read your tutorial once again and below is the result:

C:\adb>fastboot oem rebootRUU

...

(bootloader) Start Verify: 0

OKAY [ 0.048s]

finished. total time: 0.051s

C:\adb>fastboot flash PN071IMG.zip

unknown partition 'PN071IMG.zip'

error: cannot determine image filename for 'PN071IMG.zip'

C:\adb>
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
You have not specified a file type in you fastboot flash command ;)

Your command

fastboot flash PN071IMG.zip

Correct command

fastboot flash zip PN071IMG.zip

See the difference :good:
[One (M7) Q&A, Help & Troubleshooting] Pradeep321:
Yes my bad, but even after trying the same i received the following error

C:\fastboot>fastboot oem rebootRUU

...

(bootloader) Start Verify: 0

OKAY [ 0.047s]

finished. total time: 0.047s

C:\fastboot>fastboot flash zip PN071IMG.zip

error: cannot load 'PN071IMG.zip'

C:\fastboot>

Just a question, it is PN "alphabet O" 71IMG.zip or PN"Numerical Zero"71IMG.zip
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
There are am SD errors who h would be normal. Also some error MDATA.CFG errors and some errors that seem to relate to the backlight.

After you flashed the RUU how long did you wait for it to boot. It can stay stuck for up to 20mins on the first boot. I'm clutching at straws really if the ruu flashes successfully and the device doesn't boot after 20 mins it's probably safe to say there's a hardware problem.

---------- Post added at 12:53 PM ---------- Previous post was at 12:44 PM ----------

Correct it is a numerical 0. The command now is correct but fastboot doesn't see the PN071IMG.zip file.

Put the PN071IMG.zip in your fastboot folder. C:/fastboot
[One (M7) Q&A, Help & Troubleshooting] Pradeep321:
Hello Alray,

I have already placed the file into C;/fastboot but even after that i received the above mentioned error

All what i did was, downloaded the file from your given link, renamed it as advised by you and copied the file to my fastboot folder.
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
Ok when you renamed the file did you name it "PN071IMG.zip"

Windows appends file extensions. So I file called "PN071IMG.zip" Windows will see "PN071IMG.zip.zip"

A file named "PN071IMG" Windows will see "PN071IMG.zip"

If the .zip file extension is in the file name remove it so the true file name is "PN071IMG"
[One (M7) Q&A, Help & Troubleshooting] bayusuputra:
It didn't boot up at all. It will just go to the HTC boot up screen, then got turned off again, then into the HTC screen again, then off again and so on from night till morning. The screen is completely dark. I can only see the HTC logo if I shine torchlight onto the screen. The RUU flashing turned out okay, though. No problem whatsoever in cmd output.

I guess it's hardware, eh? :eek::crying:
[One (M7) Q&A, Help & Troubleshooting] v1k1ng0:
Can someone help me with this thread please? Thanks beforehand.

http://xdaforums.com/htc-one/help/htc-one-m7-restarting-t3305805
[One (M7) Q&A, Help & Troubleshooting] Pradeep321:
Hey Alray,

Finally the phone started and it felt like my heartbeat came back..!! Thanxx a tonn man, but after sometime i noticed that my SIM card is not readable in the phone.

Can u please tell me like how can I get the job done??
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
I'm not Alray ;) Although the outcome would have been the same if I was. He's a great guy but I'm not him lol :good:

Anyway can you check your android settings.

Settings>About>Phone Identity. Is the IMEI displayed correctly?

Also Settings>About>Software information>More. Is the baseband displayed correctly?
[One (M7) Q&A, Help & Troubleshooting] Pradeep321:
I don't know whether they are correct or not but yes, they both are displayed. Added to that, even my WIFI signal is too weak , is that a point of concern??
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
As long as there not displayed as Unknown. In wanted to rule that out.

Try removing this SIM tray and inserting it. How long was the device out of action?
[One (M7) Q&A, Help & Troubleshooting] alray:
Just FYI, if you want to avoid these kind of errors in the future, start to type your command:

"fastboot flash zip PN"

then hit your "TAB" key on your keyboard and the CMD window will auto-complete the file name for you to:

"fastboot flash zip PN071IMG.zip"

or "fastboot flash zip PN071IMG.zip.zip" if you have mistakenly added a second ".zip" like explained by Danny.

If you have more than 1 file starting with "PN" in your folder then hit the TAB key until the right one is shown in the CMD window.

:good:
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
That's a new one on me. Worth adding to the memory bank. Thanks [MENTION=4654136]alray[/MENTION]
[One (M7) Q&A, Help & Troubleshooting] Pradeep321:
The phone has been out of action for last 20 days approx..!! Is it a point of concern??
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
Not really, I ask in case it was for sometime maybe the SIM was cancelled by the carrier.

Have you a different SIM you can try?
[One (M7) Q&A, Help & Troubleshooting] Pradeep321:
Well I tried 3 different sim from 3 different carriers but nothing worked out well. Added to that, i evenly tried connecting my phone through different WIFI networks but it wasn't working. It either does not scans or in case if it does then it does not stays connected for more than a minute