[Q] Soft bricked, can't boot after flashing any Rom - One (M8) Q&A, Help & Troubleshooting

Hi everyone! My problem is that if I flash any rom (I've tried ARHD, Viper), the phone gets stuck at the boot screen. I've left it in that state for almost an hour and it hasn't progressed further. Restoring my nandroid backups also yields the same result. My fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331831.A15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT45
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.163s
The phone is currently unlocked, s-off. I tried flashing with both, philz and twrp, none work. Also, these roms worked before on the same phone with the same recovery so I really have no idea of what went wrong. The firmware on the phone is 1.56.720.6 (Asia-India). I have tried clearing the cache partition multiple times, but it doesn't help.

n1234d said:
Hi everyone! My problem is that if I flash any rom (I've tried ARHD, Viper), the phone gets stuck at the boot screen. I've left it in that state for almost an hour and it hasn't progressed further. Restoring my nandroid backups also yields the same result. My fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331831.A15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT45
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.163s
The phone is currently unlocked, s-off. I tried flashing with both, philz and twrp, none work. Also, these roms worked before on the same phone with the same recovery so I really have no idea of what went wrong. The firmware on the phone is 1.56.720.6 (Asia-India). I have tried clearing the cache partition multiple times, but it doesn't help.
Click to expand...
Click to collapse
The attached image is where it gets stuck. Adb works
E:\m8\>adb devices
List of devices attached
HT45NWM07703 device
@EddyOS, @nkk71 please see this. I think there's something wrong with my /data partition..

Did you recently do the GPE conversion?

May be you should try to flash the stock rom and stock recovery then flash the ruu.

Sir-Fix-a-Lot said:
Did you recently do the GPE conversion?
Click to expand...
Click to collapse
This, the partitions get altered so you can't just simply flash back

According to the OP's getvar output they've NOT done the GPe conversion as the HBOOT version included in the RUU is 3.18.0.0000 and the OP is still on 3.16.0.0000
OP, I'd follow my guide linked in my signature and you should be good to go

Sir-Fix-a-Lot said:
Did you recently do the GPE conversion?
Click to expand...
Click to collapse
Nope
Jyotirdeb said:
May be you should try to flash the stock rom and stock recovery then flash the ruu.
Click to expand...
Click to collapse
I hadn't touched the firmware, so there shouldn't be any problem related to that. Anyways, a rom and recovery do Not affect an RUU flash.
ashyx said:
This, the partitions get altered so you can't just simply flash back
Click to expand...
Click to collapse
Again, nope, I didn't do gpe
EddyOS said:
According to the OP's getvar output they've NOT done the GPe conversion as the HBOOT version included in the RUU is 3.18.0.0000 and the OP is still on 3.16.0.0000
OP, I'd follow my guide linked in my signature and you should be good to go
Click to expand...
Click to collapse
I flashed the international fw zip, and ARHD, (I had checked the hash of the file) and it still didn't work. Also, when I would reboot, some random artefacts would appear during the boot animation (different each time, sometimes wouldn't appear), such as there would be a random flash of purple across the screen or the boot animation would leave a trail behind it (like the effect you get web you would drag a stuck window in win98) etc. sometimes TWRP would act extremely sluggish while sometimes it would be fast and snappy. Quite a few times, while flashing any rom, the screen would go black and reboot to TWRP at random (even after disabling the display timeout). I tried formatting all the partitions on the internal storage. Still gave me problems. I tried to repair file system of each partition in TWRP. The data partition could never get repaired. All of these random problems lead me to believe that this was 99% the fault of the phone/hardware. Luckily I was within the 14 day replacement period and so I went out today after flashing the faux locked/s-on bootloader (I know I should not mess with firmware unless required, and I hadn't till now but I didn't care anymore since I was getting it replaced anyway. I also had 2 dead pixels and a scratch on my camera glass. Now I just have to sit back and wait for a new phone

We've seen this issue on Viper a few times and it usually happened after someone installed e.g. a VZW recovery to the GSM phone or vice versa.
A wrong recovery would flash stuff into the wrong partitions.
A RUU for your device, really just any, should fix it. You should run a RUU and then factory reset right afterwards from bootloader BEFORE flashing another custom recovery.
There is a cingular (AT&T) RUU out right now from HTC here: http://dl3.htc.com/application/RUU_...G_20.31A.4145.02L_release_368350_signed_2.exe which you could try - it is a GSM RUU. We don't really have WWE 401 RUU yet.
Just make sure you don't grab a SPRINT or Verizon RUU if you find any!!!!!!

Sneakyghost said:
We've seen this issue on Viper a few times and it usually happened after someone installed e.g. a VZW recovery to the GSM phone or vice versa.
A wrong recovery would flash stuff into the wrong partitions.
A RUU for your device, really just any, should fix it. You should run a RUU and then factory reset right afterwards from bootloader BEFORE flashing another custom recovery.
There is a cingular (AT&T) RUU out right now from HTC here: http://dl3.htc.com/application/RUU_...G_20.31A.4145.02L_release_368350_signed_2.exe which you could try - it is a GSM RUU. We don't really have WWE 401 RUU yet.
Just make sure you don't grab a SPRINT or Verizon RUU if you find any!!!!!!
Click to expand...
Click to collapse
Too late for trying a fix , I just want to know what caused it, and I'm 1000% sure I had the right recovery, because as I said, I flashed many other roms in the past with the same recovery, and the problem came after I tried ARHD. And this is the gsm phone.

Yeah well no idea then. Just know I've seen this happen from wrong recoveries. Also not the time to dig into it any further if you've gotten that resolved already I'll leave it as is. Thanks for asking me though. Just keep in mind I've been out of XDA since months and am only slowly reading my way back in so I'm sure there are way more knowledgeable guys around regarding firmware, softbricks and the like.
mobile post... lazy typing...

n1234d said:
Too late for trying a fix , I just want to know what caused it, and I'm 1000% sure I had the right recovery, because as I said, I flashed many other roms in the past with the same recovery, and the problem came after I tried ARHD. And this is the gsm phone.
Click to expand...
Click to collapse
In such a big mess! I have the same problem as the OP - same to the last dot. I am on India version of device, and was just trying to update firmware to 4.4.3 and in that quest i flashed firmware from here http://forum.xda-developers.com/showpost.php?p=54899772&postcount=1392.
Post that camera and wi-fi stopped working - so I thought may be I screwed up with boot.img and reflashing Viper/ADHD would solve it. While on my way to install Viper I cleaned/wiped data in recovery and hit reboot accidentally which got the phone to stuck in bootloop. I pushed in back in recovery however, since then I have not been able to install either Viper or ADHD. I even tried doing a nandroid back-up from here: http://forum.xda-developers.com/showpost.php?p=54940131&postcount=1419, however nothing brings me past the splash screen.
Off-late (few hours) I am not been able to do a back-up (nandroid) as my recovery throws cant mount sdcard or sdcard1 both. Please help!
Here is the "getvar all" log:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.16G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.720.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT469WM02625
(bootloader) imei: xxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(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: 42372cde
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

7mojo said:
In such a big mess! I have the same problem as the OP - same to the last dot. I am on India version of device, and was just trying to update firmware to 4.4.3 and in that quest i flashed firmware from here http://forum.xda-developers.com/showpost.php?p=54899772&postcount=1392.
Post that camera and wi-fi stopped working - so I thought may be I screwed up with boot.img and reflashing Viper/ADHD would solve it. While on my way to install Viper I cleaned/wiped data in recovery and hit reboot accidentally which got the phone to stuck in bootloop. I pushed in back in recovery however, since then I have not been able to install either Viper or ADHD. I even tried doing a nandroid back-up from here: http://forum.xda-developers.com/showpost.php?p=54940131&postcount=1419, however nothing brings me past the splash screen.
Off-late (few hours) I am not been able to do a back-up (nandroid) as my recovery throws cant mount sdcard or sdcard1 both. Please help!
Here is the "getvar all" log:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.16G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.720.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT469WM02625
(bootloader) imei: xxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(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: 42372cde
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Did you re-unlock your phone?
Sent from my HTC One_M8 using Tapatalk

n1234d said:
Did you re-unlock your phone?
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Yes, I did. Using HTCDev.
At the moment, I would be just happy with someway of going back to the clean slate. Is there a way I could go back to original/stock using ADB/Fastboot as recovery also doesnt seem to work.
Thanks

7mojo said:
Yes, I did. Using HTCDev.
At the moment, I would be just happy with someway of going back to the clean slate. Is there a way I could go back to original/stock using ADB/Fastboot as recovery also doesnt seem to work.
Thanks
Click to expand...
Click to collapse
Bump!
Anyone?

Related

[Q] HTC One S-Off, and Unlocked boot looping

Hello,
I have accidentally flashed a GSM rom on my CDMA device(I know stupid of me), and I also did not take a nandroid(very stupid of me). I have access to Recovery, Bootloader, Fastboot, and Adb Sideload. I have tried Sideloading a rom, but I get "This package is for "m7wlv,m7vzw" devices; this is a "m7""
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 1.13.41.0109_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.605.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA37TS914979
(bootloader) imei: 990004281570899
(bootloader) meid: 99000428157089
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4006mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.068s
I have tried everything, and I'm pulling at straws here. Help would be super appreciated, and I'd owe you for a lifetime!
Thanks,
Have a wonder night!
I would grab one of Hawk's stock Roms and flash it in philz's recovery.
But it sounds like your CID or something is screwed up.
GrayTheWolf said:
I would grab one of Hawk's stock Roms and flash it in philz's recovery.
But it sounds like your CID or something is screwed up.
Click to expand...
Click to collapse
I ended up fixing it with an RUU I found, however, when I try to install Viper 6.1.0 it successfully installs, but just boot loops. It will get to the htc logo, and just reboot.
meatwad63 said:
I have tried Sideloading a rom, but I get "This package is for "m7wlv,m7vzw" devices; this is a "m7""
Click to expand...
Click to collapse
I think you're using the wrong recovery, make sure that you've downloaded the the m7vzw version. I made this mistake the first time I went to download CWM.
meatwad63 said:
I ended up fixing it with an RUU I found, however, when I try to install Viper 6.1.0 it successfully installs, but just boot loops. It will get to the htc logo, and just reboot.
Click to expand...
Click to collapse
Do you mind giving the steps on how you fixed this problem? I am getting the same error you had in your OP and can't seem to get anything to work.
Thanks

[Q] Trouble getting back to stock on German One m8

Hello xda-Community!
First off, I have posted this a couple of weeks ago in the general help thread, however it quickly got swarmed and lost, so I wanted to try again.
I have run into some trouble with my O2 HTC One M8. First, my readout from fastboot:
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: O2___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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I have been running CM11 for some months and am pretty happy with it, but I want to upgrade to Lollipop. However, the phone won't let me do that, as hboot is only version 3.16.0.0000 and Lollipop needs 3.19 (apparently). The version_main is empty for some reason, I did not erase that part.
But now comes the kicker: To upgrade hboot, I need to return to stock (or set the CID to SuperCID), right?
Now, I cannot return to stock, because there is no RUU / nandroid backup for my CID (O2___102).
As I don't have S-OFF, I cannot install any other RUU. To get S-OFF with SunShine, I need to be on stock though, because right now I get the following error message: "Your device has a debuggable ramdisk (ro.debuggable=1). You need to flash a non-debuggable boot.img, stock would be best."
So basically: I need to get back to stock to go back to stock, or am I reading this wrong?
Is there a way out of this?
In the general help thread, someone said I should flash a ROM close to stock (he/she suggested Maximus HD) for this to go away, but I cannot flash any ROM besides the CM11 one I am already on, as none of the other ROMs allow me to boot - I simply get stuck during boot-up and have to reflash CM11 to use the phone.
The recovery I am using is TWRP 2.7.0.2 if that information is necessary or helpful.
Thanks in advance for anybody who can help me.
Have you try stock nandroid backup 1.54.206.5 or 1.12.206.17 from this thread ?
http://forum.xda-developers.com/showthread.php?t=2701376
ckpv5 said:
Have you try stock nandroid backup 1.54.206.5 or 1.12.206.17 from this thread ?
http://forum.xda-developers.com/showthread.php?t=2701376
Click to expand...
Click to collapse
Well god damn it. I had tried those but apparently, they got corrupted in the download. Just tried again (from my laptop) and it worked marvellously. Thank you for your reply!

Bricked to the Max... (Maybe)

Prologue:
So there I was, caressing my shiny and smooth M8.
At the beginning of the year I S-Offed, and added DigitalHigh's awesome Beyond Stock...
Later on, I used a standard RUU GPE Rom.
After repeated Wi-Fi password amnesia, I wanted Beyond Stock Back.
Flashing "GPE_5.1_M8_DH_080215.zip" gives me an "Error 7" even with repeated wipes... hehe... wipes
Searching didn't give me a coherent answer.
So I though, let's update TWRP... and...
Now
The thing's only usable in Bootloader.
If I go to recovery or ANYTHING, the "Google" logo stares at me in disgust.
Odd detail: I'm using fastboot and when it's stuck on the "Google" logo, entering "adb devices" detects the phone in recovery mode.
I flashed TWRP 2.8.7.0, but all I see is the "Google" logo. (I can still feel vibrations on the screen as if I'm hitting a menu button)
I also tried to "fastboot -w" and it gave me the "remote: not allowed" result.
Actually, I tried to fastboot a lot of things and the result came the same.
Anyways, I'll give a detailed log as soon as I remember how, but the reason I post this is 'cause searching for this doesn't give an understandable or reliable result.
Thanks
C:\WINDOWS\system32>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.057s
Give the output of :
Fastboot getvar all
But delete the serial and imei before posting ! If you have an old bootloader you have to use the 2.7 series of TWRP. if you have the latest bootloader (3.18-3.19) you have to use 2.8 series of TWRP !
OOOOOOOOOHHHH, Where I get new M8 bootloader?
Hold Up, going to work, will post 'getvar' later today.
It's there, brah.
Take a look if you can.
It's an AT&T device, you are using it with AT&T ? And you fully converted it from sense to GPE ? You could also :
1: run the GPE ruu again. It will get you on GPE stock again and since you are s-off that should not be a problem of any kind.
2: convert back to sense (original AT&T with software number x.xx.502.x)
i am not sure if the AT&T RUU will cover the "back to sense conversion" so this might be interesting too as it involves the standalone flashing of the firmware first (you need a AT&T firmware, NOT the one posted there !!!)
here is more conversion info :http://forum.xda-developers.com/showthread.php?t=2733523
and here you can get firmwares : http://forum.xda-developers.com/showthread.php?t=2701376
if you want number 2 here is more info with a download link to the latest android L RUU : http://www.theandroidsoul.com/download-att-htc-one-m8-lollipop-ruu-4-28-502-1-75822/
Didnt want to start my own thread due to the shame..
Hi,,
I have managed to remove my OS, without making a backup. All i have running is TWRP. Was going to install CM12.1, but didnt update the M8 to the latest software that contains relevant bootloader. From here it went downhill - fast.
Ended up with no OS, no backkups, and no ability to flash other ROMS i think.
If someone could give me a few ideas, i would really appreciate it.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__203
(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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Mike
Sheriff1972 said:
Hi,,
I have managed to remove my OS, without making a backup. All i have running is TWRP. Was going to install CM12.1, but didnt update the M8 to the latest software that contains relevant bootloader. From here it went downhill - fast.
Ended up with no OS, no backkups, and no ability to flash other ROMS i think.
If someone could give me a few ideas, i would really appreciate it.
Click to expand...
Click to collapse
Your case is different and you should start your own thread but there are many same case as yours.
Here is one and the solution is in there.. run RUU - http://forum.xda-developers.com/htc-one-m8/help/os-sos-t3192177
Anything you're not sure, ask there. Don't hijack this thread.
UPDATE: Thanks to ckpv5 and the links that were provided i was able to complete the reinstall - thank you so much!!
Opps - sorry - didnt mean to offend!
Will take a look.
Thanks
Mike
The RUU got me an OS and, right now, that is all I need.
Thank you!!

M8 stuck in bootloop(?)

Hey guys,
First off, any help here would be more than appreciated as I am at my wits' end.
So, i shall try and inform you guys as much as I can and hope it suffices. My M8 seems to be stuck in a bootloop. I can get to the bootloader (hboot & fastboot) and that's about it. I tried to flash a new recovery and kernel through fastboot but that doesn't seem to help either. My phone has been unlocked a long time ago but never had any problems until this suddenly happened.
Here is my oem info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA03_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.12.114.18
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *********
(bootloader) imei: ***************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: T-MOB003
(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: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
PS- It is also interesting to note that when my phone is stuck on the white HTC screen, i can hear message notifications and such implying that the phone is still running ( I even mirrored my phone to the pc using USB and I can see my home screen on my laptop but just the HTC screen on the phone.
Thanks a ton in advance
xyzzyx666 said:
I tried to flash a new recovery and kernel through fastboot but that doesn't seem to help either. My phone has been unlocked a long time ago but never had any problems until this suddenly happened.
Click to expand...
Click to collapse
Were you trying to flash anything (such as a custom ROM) to make this happen? If not, why would changing the recovery make a difference? If yes, what did you flash?
Phone was on stock or custom ROM when this started to happen?
Do you have a nandroid backup you can restore?
Also, newer versions of TWRP won't work with your (ancient) hboot, so depending on what TWRP build you flashed, you can just be adding to the problem.
No, I wasn't trying to flash anything which is what baffles me more. My phone just froze all of a sudden and I had to use Power+Volume Up to reboot and it hasn't been starting up ever since.
I'm current;y running a custom ROM (skydragon if I remember well).
The last significant change I remember making was giving the "Clean Master" app accessibility permissions through the settings. Idk why it didn't just ask me to do it through SuperUser there.
As I asked before:
Do you have a nandroid backup you can restore?
If so, try to restore that backup.
Otherwise, try to re-flash the custom ROM.
What version TWRP are you currently on?

HTC One M8 - No Sound at all

Hi, I recently installed lineage os rom (from sense-rom). So after the installation I was really pleased that the phone was back to normal but later i realize the audio has completely vanished. I can't play any songs, videos start but they are as on mute. same goes for playing videos on Instagram and YouTube. Actually on YouTube I get the error message '' There was a problem while playing Touch to retry''. Even there is no ringtone volume sound, i also tired to change it but its says unable to play. I also tried to recover my recovery of stock 4.4.4 and also did factory reset later but the problem still persists.
Any support would be appreciated. Thank you.
aweshlakhani said:
Hi, I recently installed lineage os rom (from sense-rom). So after the installation I was really pleased that the phone was back to normal but later i realize the audio has completely vanished. I can't play any songs, videos start but they are as on mute. same goes for playing videos on Instagram and YouTube. Actually on YouTube I get the error message '' There was a problem while playing Touch to retry''. Even there is no ringtone volume sound, i also tired to change it but its says unable to play. I also tried to recover my recovery of stock 4.4.4 and also did factory reset later but the problem still persists.
Any support would be appreciated. Thank you.
Click to expand...
Click to collapse
Flash RUU or firmware only .
Sent from my htc_m8 using Tapatalk
sonnu0100 said:
Flash RUU or firmware only .
Click to expand...
Click to collapse
Agreed. Sound issues like this are usually a result of outdated or damaged firmware.
@ sonnu0100 @redpoint73
Thanks! can you provide me link as i dont know which firmware is correct for my device.
Here is the details of my phone
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.08.20.0916
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.30.651.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 99000499166745
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 8a0f02ff
(bootloader) hbootpreupdate: 11
aweshlakhani said:
can you provide me link as i dont know which firmware is correct for my device.
(bootloader) version-main: 3.30.651.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m8_whl
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: 11111111
Click to expand...
Click to collapse
Sure, here you go: https://forum.xda-developers.com/showthread.php?t=2729173
Firmware 6.20.651.3 is what you want. Modified vs. full or signed is up to you. But since you have s-off, the easiest is probably the one with recovery and boot removed. Otherwise, stock recovery and boot will be installed when you flash the firmware; and you will need to flash TWRP again, and also flash the custom ROM (or at least it's boot.img) again.
I'm glad you provided the getvar data in this case. From the results I can see you have the US Sprint variant, with s-off. This combination is a little dangerous. Whatever you do, do NOT try to flash firmware for another (non-Sprint) version. They are not compatible, and doing so won't work, and may even result in a permanent radio brick!
Hello Guys !!
So my brother had htc one m8 for like 4 years he was studying in uk he came back to india in 2016 and purchased one plus 3 and unfortunately he passed away after 15 days but thats not the point, so my dad kept the oneplus , this htc was somewhat dead and was kept in the cupboard for two years and i had my eyes on it a week back i tried to charge it and it actually did show a sign of life though it was stuck on htc screen, wasnt booting up i put some effort and managed to boot it up i wanted to listen to legendary boom sound but strangely their was no sound at all and tried to listen to ringtones but still no sound thought that it must be hardware issue but headphones werent working either, i came on xda read some threads found out that this can be case when rom is damaged it was running on MM sense 7 so i unlocked bootloader and flashed twrp and installed lineage os 17 but still there was no sound so i tried to get it back on stock but all i get is errors , I tried many RUU versions most of the time error was "error 12 signature verify fail i feel pretty helpless cause i wanted get my brother's memories back
i ve got so much expectations with you people
here is info about my device
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH4AVWM00613
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
xostrator said:
i tried to get it back on stock but all i get is errors , I tried many RUU versions most of the time error was "error 12 signature verify fail i feel pretty helpless cause i wanted get my brother's memories back
Click to expand...
Click to collapse
Signature verify fail usually means you still have the bootloader unlocked. The bootloader needs to be relocked in order to run RUU. Relock with fastboot command: fastboot oem lock
You also aren't going to find the right RUU by guessing. It needs to match your CID and version number. In your case, there also isn't an exe version RUU for your M8 variant. But you can use the zip format RUU from the following post, using the instruction found there as well: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Also, I'm not sure what you mean by wanting your brother's memories back. Not sure if you are being literal (the actual data) or more figurative. But if you are talking data, that got wiped when you unlocked the bootloader.
Another thing, delete serial number for your post. This is personal data, that should not be posted on a public forum.

Categories

Resources