Hi
I have a problem with a UK M8 which originally had a cracked screen and I replaced it. All good except for some issue of which I cant remember what it was as it was a long time ago. I assumed a sw fault so did OTA update to Marshmallow. However I think it failed during install and then got stuck on htc logo. Factory resets etc had no effect.
So after doing extensive searching I decided to try other methods so unlocked the bootloader and tried to install a rom. To cut a long story short, I have tried everything that I can but I cannot get the phone to boot into OS. I can get it to do the optimizing apps and then it changes to starting apps but sticks on the starting apps screen even if I leave it all day. I have tried various methods but always end up with a phone which will not boot to OS. It did briefly boot into os (partly) butapart from the background and the battery info and couple of other top line details nothing else, then it rebooted itself and htc logo stuck again. I have over the course of time wiped everything from the phone so it has nothing original on it.
The last thing I have done is flashed a signed firmware and have tried using ckpv5s nandroid backups on sd card and also the renaming to 0P6BIMG and sd card flash that way. Same result.
I am now fed up and so need some help. I just want the bloody thing to work again.
Huge thanks in advance
Details as follows
(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.61.4
(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: ORANG001
(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
I am betting that I have made a schoolboy error. I am also suspecting a hardware fault.
I have twrp 3.0.2.0 installed. Unlocked bootloader.
Hazlo99 said:
The last thing I have done is flashed a signed firmware and have tried using ckpv5s nandroid backups on sd card and also the renaming to 0P6BIMG and sd card flash that way. Same result.
I have twrp 3.0.2.0 installed. Unlocked bootloader.
Click to expand...
Click to collapse
restoring nandroid backup is solve the issue of faulty OS if your device doesn't have an official RUU ( as your device )
so try to restore your devices backup ( again if you do it following OP instruction ) from ckpv5 thread i doubt it will fail if it's software issue
Good luck
Related
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?
Hi guys,
I received my AT&T HTC M8 last week.
I wanted to flash the Android Revolution HD rom so I unrooted the device, installed TWRP, super CID it and S-Off it.
I tried to install the Rom but the WIFI didn't work so I rolled back to the Stock using TWRP.
I did some reaches and realize I need to update the Firmware so I did. The messaged at the end of the process was "completed successfully" but when I rebooted the device it got stuck at the splash screen. I can hear the ATT load chime but the AT&T icon is not displayed and that's it, stuck!!!!
I entered the HBoot and tried to access the recovery. The screen gets black with a red triangle icon in the center and the device reboot after several minutes. I think the Hboot message is no image.
When I connect the device to the computer it is recognized and I can access the files etc. but the ADB doesn't see the device any more.
I'm really lost and frustrated after hours and hours of reading and research without any luck.
Any help will be truly appreciated.
This is the device variables before I updated the firmware:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT453WM01167
(bootloader) imei:
(bootloader) imei2: Not Support
(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: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I look forward to your advice.
Thanks a lot in advance.
ronf0303 said:
Hi guys,
I received my AT&T HTC M8 last week.
I wanted to flash the Android Revolution HD rom so I unrooted the device, installed TWRP, super CID it and S-Off it.
I tried to install the Rom but the WIFI didn't work so I rolled back to the Stock using TWRP.
I did some reaches and realize I need to update the Firmware so I did. The messaged at the end of the process was "completed successfully" but when I rebooted the device it got stuck at the splash screen. I can hear the ATT load chime but the AT&T icon is not displayed and that's it, stuck!!!!
I entered the HBoot and tried to access the recovery. The screen gets black with a red triangle icon in the center and the device reboot after several minutes. I think the Hboot message is no image.
When I connect the device to the computer it is recognized and I can access the files etc. but the ADB doesn't see the device any more.
I'm really lost and frustrated after hours and hours of reading and research without any luck.
Any help will be truly appreciated.
This is the device variables before I updated the firmware:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT453WM01167
(bootloader) imei:
(bootloader) imei2: Not Support
(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: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I look forward to your advice.
Thanks a lot in advance.
Click to expand...
Click to collapse
You have old, 4.4.2 firmware. That is the issue. Get new firmware and instructions on installing it here or here.
Thanks for getting back to me.
The firmware you see in the var. list I placed above is before I changed the Firmware.
As a result the phone is stuck on the splash screen.
I found post Firmware Flashing without the panic attacks... ; (you recommended) and followed the instructions.
The firmware update was complete...
Since that point the phone doesn't boot.
I did a Factory Reset yet still no change.
The most annoing fact is that I can get to the device with ADB.
When I type ADB Devices I get empty list
ronf0303 said:
Thanks for getting back to me.
The firmware you see in the var. list I placed above is before I changed the Firmware.
As a result the phone is stuck on the splash screen.
I found post Firmware Flashing without the panic attacks... ; (you recommended) and followed the instructions.
The firmware update was complete...
Since that point the phone doesn't boot.
I did a Factory Reset yet still no change.
The most annoing fact is that I can get to the device with ADB.
When I type ADB Devices I get empty list
Click to expand...
Click to collapse
ADB only works in custom recovery or when booted into OS
Fastboot will work on fastboot mode.
Do flash a custom recovery using fastboot. And also erase cache position before booting into custom recovery
It's working - I'm so happy
Hi guys,
Thanks for your support.
Bottom line - The phone is up and running ARHD Ver 21.
I repeated the whole process (flashing the firmware and the rom) but this time instead of flashing the FW I downloaded from the Revolution site (3.32.531.2) I flashed 3.32.531.2_Firmware_TMUS.ZIP I downloaded from
http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
So thanks so much for your support.
I'm really really happy
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?
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.
So my htc is 2 years old and it's starting to have some problems. Right now when I tried to restart it it just got stuck on the android logo. I've read a lot on the internet but since I am entirely new to this I decided to come here so i can get a valid answer on my current options. Do i have to use ruu to make it alive and if yes which version to download? Are there any there any other options? I got adb and fastboot on my windows. Right now the phone is connected to the pc with usb in bootloader mode. Here are some pieces of info about my phone
fastboot getvar all
(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) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__032
(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
all: Done!
Also , if i install the ruu, is there anything left to do after? or can i just reboot my phone and watch it open finally?
therzvsm said:
Right now when I tried to restart it it just got stuck on the android logo. I've read a lot on the internet but since I am entirely new to this I decided to come here so i can get a valid answer on my current options. Do i have to use ruu to make it alive and if yes which version to download? Are there any there any other options?
Also , if i install the ruu, is there anything left to do after? or can i just reboot my phone and watch it open finally?
Click to expand...
Click to collapse
You can try to do factory reset, wipe cache and Dalvik, all within bootloader/stock recovery. But if that doesn't help, we see a good amount of reports like yours, where it seems like the OS has been damaged or corrupt. In which case, simply doing factory reset or wiping cache, is not going to fix it.
In that case, RUU is certainly an option, and probably the easiest. The correct RUU for your device, plus instructions how to flash, can be found here: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Once RUU is installed, nothing else to really do. Just boot up the phone (hopefully will boot to Android OS) and setup the phone again. Note that RUU will wipe all personal data on the phone.
Another option is to unlock the bootloader, flash TWRP, and install a stock TWRP backup (stock ROM) as outlined in the following thread: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
But note that unlocking the bootloader also wipes all user data. So you aren't gaining anything with this method, and it is a significantly longer and more complicated process. So again, I think RUU is your best bet.