Develop Bugs

[Q] Question about this handset and rooting

Hi all,
Have just got a HTC One M8 and it's been shipped already S-OFF, the phone still says locked and so far as i'm aware it should read S-ON ??
My question is, if I was to unlock the bootloader and root the device, install a custom recovery and eventually a ROM with it being already S-OFF would i encounter any issues?
The phone looks to be either a developer phone or just a factory S-OFF phone ?
Many thanks, screen shot attached.
PS: Apologies for the lack in quality apparently I can only upload 256KB pics to XDA.
Specs are as follows.
HTC M8 Silver
CID 11111111
UL PVT SHIP S-OFF
HBOOT 3.16.0.000
Radio - 1.16.213156.UA15G
Factory unlocked international M8.
Couldn't find any more information so hope this is enough.
Many thanks.

Did you buy the phone new (like from an official store or carrier) or used?
I'm guessing its used, and the previous owner unlocked the bootloader, SuperCID, S-off; then returned the phone to LOCKED status (possible with S-off).
Although its not unheard of for phones to ship S-off, its pretty rare. And I don't think I've heard of a phone S-off and SuperCID (11111111) direct from factory, so the combination of the 2 is rather suspicious.

redpoint73 said:
Did you buy the phone new (like from an official store or carrier) or used?
I'm guessing its used, and the previous owner unlocked the bootloader, SuperCID, S-off; then returned the phone to LOCKED status (possible with S-off).
Although its not unheard of for phones to ship S-off, its pretty rare. And I don't think I've heard of a phone S-off and SuperCID (11111111) direct from factory, so the combination of the 2 is rather suspicious.
Click to expand...
Click to collapse
Actually it wasn't it was brand new. I have no idea m8, i thought it was strange when i went into the bootloader.

never mind

(Solved) Can root and unlock bootloader, shouldn't pose an issue i'm told.
Sorted

dladz said:
(Solved) Can root and unlock bootloader, shouldn't pose an issue i'm told.
Sorted
Click to expand...
Click to collapse
Yeah, you should have two options here
(Only posting for reference)
Flash an ENG (engineering) HBOOT
Or
HTC Dev the phone
With either you can flash a recovery via Fastboot and flash a SuperSU.zip
And being as you're already S-off, then you can write to boot, so you can flash ROMs after doing the above as well
Sent from my m7spr

ajbiz11 said:
Yeah, you should have two options here
(Only posting for reference)
Flash an ENG (engineering) HBOOT
Or
HTC Dev the phone
With either you can flash a recovery via Fastboot and flash a SuperSU.zip
And being as you're already S-off, then you can write to boot, so you can flash ROMs after doing the above as well
Sent from my m7spr
Click to expand...
Click to collapse
nice one m8, think i'll go down the HTC Dev route, then recovery.
Great phone.

I have a similar problem , even after rooting the phone I was unable to update to any custom rom due to firmware status,
here is the fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.22.401.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA4xxxxxxxx
(bootloader) imei: ---------------
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(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: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Eeshaann said:
I have a similar problem , even after rooting the phone I was unable to update to any custom rom due to firmware status,
Click to expand...
Click to collapse
Please don't post the same question to multiple threads. You are already being helped in the "HELP THREAD".
Also, don't "zombie" threads that have been dead for almost 3 years. Your issue isn't that similar to the OP's (aside from s-off) anyway.

[Q] Can ANYBODY help me!?! No ROM showing installed....

I have tried a few newer RUU's since I'm on 3.16 bootloader and S-ON. When I go to flash using the RUU utility, it doesn't show any installed rom...because there IS no installed ROM!
Therefore, it fails. As you can see below...there is nothing showing in version-main. Any idea on how to fix this??? The phone isn't bricked...there's just no rom installed. Should I use TWRP instead??? What RUU should I be using???? (A friend came over trying to return this back to stock, after a bad Venom rom flash)
version-bootloader: 3.16.0.0000
version-baseband: 1.16.21331931.LA11G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: FA43SWM04387
imei: 358718050243422
imei2: Not Support
meid: 00000000000000
product: m8_ul_ca
platform: hTCBmsm8974
modelid: 0P6B12000
cidnum: CWS__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: c3d94491
hbootpreupdate: 11
gencheckpt: 0

........

jreed3786 said:
I have tried a few newer RUU's since I'm on 3.16 bootloader and S-ON. When I go to flash using the RUU utility, it doesn't show any installed rom...because there IS no installed ROM!
Therefore, it fails. As you can see below...there is nothing showing in version-main. Any idea on how to fix this??? The phone isn't bricked...there's just no rom installed. Should I use TWRP instead??? What RUU should I be using???? (A friend came over trying to return this back to stock, after a bad Venom rom flash)
version-bootloader: 3.16.0.0000
version-baseband: 1.16.21331931.LA11G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: FA43SWM04387
imei: 358718050243422
imei2: Not Support
meid: 00000000000000
product: m8_ul_ca
platform: hTCBmsm8974
modelid: 0P6B12000
cidnum: CWS__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: c3d94491
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
You have 4.4.2 firmware. The reason ViperOne caused you problems is because you need updated firmware.
You'll need to find an AT&T RUU. You'll also have to re-lock your bootloader before running it. It also will have to be a signed RUU. All three of these things are because you are S-On.
You could also download ViperOne 1.x.x (a 4.4.2 base), put that onto your extSD, and flash that as normal in recovery. It will get you back running, and is a compatible version of ViperOne for your phone.
You can download ViperOneM8 1.7.1 from this link.

xunholyx said:
You have 4.4.2 firmware. The reason ViperOne caused you problems is because you need updated firmware.
You'll need to find an AT&T RUU. You'll also have to re-lock your bootloader before running it. It also will have to be a signed RUU. All three of these things are because you are S-On.
You could also download ViperOne 1.x.x (a 4.4.2 base), put that onto your extSD, and flash that as normal in recovery. It will get you back running, and is a compatible version of ViperOne for your phone.
You can download ViperOneM8 1.7.1 from this link.
Click to expand...
Click to collapse
I tried doing fastboot oem lock....no luck. Any ideas? Is CWS__001 the correct CID for AT&T M8?

jreed3786 said:
I tried doing fastboot oem lock....no luck. Any ideas? Is CWS__001 the correct CID for AT&T M8?
Click to expand...
Click to collapse
It didn't work? That's weird. Does it show "unlocked" in your bootloader?
And yes it is the correct CID. I wondered why you asked, then saw saw your signature. I knew AT&T because of you being in the US and your CID.

Never mind. I figured it out on my own.
xunholyx said:
You have 4.4.2 firmware. The reason ViperOne caused you problems is because you need updated firmware.
You'll need to find an AT&T RUU. You'll also have to re-lock your bootloader before running it. It also will have to be a signed RUU. All three of these things are because you are S-On.
You could also download ViperOne 1.x.x (a 4.4.2 base), put that onto your extSD, and flash that as normal in recovery. It will get you back running, and is a compatible version of ViperOne for your phone.
You can download ViperOneM8 1.7.1 from this link.
Click to expand...
Click to collapse
Thank you very much, though! I'm just glad I chose a Samsung product! I remember the Hell says of my Sensation! Lol!

jreed3786 said:
Thank you very much, though! I'm just glad I chose a Samsung product! I remember the Hell says of my Sensation! Lol!
Click to expand...
Click to collapse
That's funny, I'm glad I chose to leave Samsung products.

M8 starting up in Fastboot, won't load installed ROM

I've stuffed something up along the way and now my M8 seems to refuse to load any ROM I've installed on it. What's the best way to go about fixing this? It's unlocked with S-Off.

Flashing an RUU is a silver bullet for starting over, as an RUU formats all your device's partitions and flashes them with stock images.
You'll need to provide CID & MID or your current firmware version (i.e. 4.16.401.10) if you need help locating a compatible RUU.
Cheers

Need some more details to see why the phone won't boot into OS after flashing a ROM.
Is an OS number indicated on the bootloader screen? If so, what is it?
What version TWRP?
What ROMs have you tried?

shirreer said:
Flashing an RUU is a silver bullet for starting over, as an RUU formats all your device's partitions and flashes them with stock images.
You'll need to provide CID & MID or your current firmware version (i.e. 4.16.401.10) if you need help locating a compatible RUU.
Cheers
Click to expand...
Click to collapse
I've tried flashing a few different RUUs and they all come out with an error 155. Googling it suggests I need to relock my bootloader but locking it and running the RUU again gives me the same error. I'm using SuperCID 11111111 and my MID is 0P6B70000. Currently on firmware 4.16.1540.8.
redpoint73 said:
Need some more details to see why the phone won't boot into OS after flashing a ROM.
Is an OS number indicated on the bootloader screen? If so, what is it?
What version TWRP?
What ROMs have you tried?
Click to expand...
Click to collapse
My OS number is 4.16.1540.8, I've tried TWRP 2.7.0.1, 2.8.7.0 and 3.0.0.0, roms I've tried include CM13, SkyDragon and a stock TWRP backup I found in another thread here.

roseyhead said:
I've tried flashing a few different RUUs and they all come out with an error 155. Googling it suggests I need to relock my bootloader but locking it and running the RUU again gives me the same error. I'm using SuperCID 11111111 and my MID is 0P6B70000. Currently on firmware 4.16.1540.8.
Click to expand...
Click to collapse
Your MID and firmware number don't jive; and it can indicate something pretty dangerous (and possibly a radio bricked phone).
Need more info on what you've done.
Do fastboot getvar all, and post the output (delete serial number and IMEI before posting).
Was the phone new and stock (unmodified) when you got it; or did it have a previous owner?
Please list all the mods you have applied (s-off, changed CID, changed MID? etc.).

Ok, here's what getvar all reports:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.1540.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: -snip-
(bootloader) imei: -snip-
(bootloader) imei2: Not Support
(bootloader) meid: 99000499014851
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.035s
I bought the phone second-hand, it was running a custom ROM (SkyDragon) with cid already set to 11111111 and I wanted to return it to stock. I got the Unlocked/Developer RUU from HTC's site but that didn't start up for me so I tried a bunch of stuff, fiddling with firmwares and unlocking/relocking bootloader and so on but in the end the RUU just hadn't downloaded properly. Once I managed to get the RUUs to run they've all come up with error 155 when they start the flash and flashing the rom.zip direct gives me an error (I forget if it's the same or different)
I've also tried restoring assorted TWRP backups, installing new roms and so on, directly flashing boot.img, things seem to flash ok but the phone just boots direct into fastboot.

Update: I'm not sure what went differently this time but I've installed the latest Cyanogenmod nightly and it's starting up as expected.
I'd like to get back to stock though. What's the best way to go about doing this? The phone was already modified when I got it so I'm not sure what it would've had on it when it was purchased originally.
Edit: A bit of googling suggests this is a Sprint handset (I dismissed this to begin with since I'm in Australia and didn't think it'd be an overseas handset, but ok) so I've flashed 6.20.651.3 firmware and am waiting for a matching RUU to download. Fingers crossed!
Edit again: All sorted now, thanks for your help!

roseyhead said:
Update: I'm not sure what went differently this time but I've installed the latest Cyanogenmod nightly and it's starting up as expected.
I'd like to get back to stock though. What's the best way to go about doing this? The phone was already modified when I got it so I'm not sure what it would've had on it when it was purchased originally.
Edit: A bit of googling suggests this is a Sprint handset (I dismissed this to begin with since I'm in Australia and didn't think it'd be an overseas handset, but ok) so I've flashed 6.20.651.3 firmware and am waiting for a matching RUU to download. Fingers crossed!
Edit again: All sorted now, thanks for your help!
Click to expand...
Click to collapse
I'm glad you're all set. But for other users' benefit, here is a link to HTC's official Sprint RUU page, with instructions for flashing the RUU as well as a download link for Sprint M8 marshmallow RUU 6.20.651.3
Sprint RUU instructions page:
http://www.htc.com/us/support/htc-one-m8-sprint/news/
Sprint M8 marshmallow RUU 6.20.651.3 Direct Link:
http://dl3.htc.com/application/RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3.exe
Cheers

i am having the same problem. i dont even know what carrier this phone was from. but the model number written on the back is OP6B110 M8x... and this is the result of getvar all..
(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: 2.16.654.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) imei2: Not Support
(bootloader) meid: 99000499165808
(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
(bootloader) gencheckpt: 0

roseyhead said:
I got the Unlocked/Developer RUU from HTC's site but that didn't start up for me so I tried a bunch of stuff, fiddling with firmwares and unlocking/relocking bootloader and so on but in the end the RUU just hadn't downloaded properly. Once I managed to get the RUUs to run they've all come up with error 155 when they start the flash and flashing the rom.zip direct gives me an error (I forget if it's the same or different)
Click to expand...
Click to collapse
Happy to see your sorted it out.
I agree it appears to be the Sprint version, based on the the MID (0P6B70000) and product name (m8_whl). While the MID can be modified, the product name is typically not (never seen a mod method for that - so the product name is very reliable).
That being said, I would strongly caution you moving forward, to not flash any firmware or RUU to this device except Sprint M8 firmware/RUU. Reason being, the partitioning on the Sprint phone is different from most other versions; and flashing another version's firmware can lead to a radio brick (phone boots, but nothing requiring the radio will work).
---------- Post added at 11:38 AM ---------- Previous post was at 11:30 AM ----------
mushfiq20 said:
i am having the same problem. i dont even know what carrier this phone was from. but the model number written on the back is OP6B110 M8x... and this is the result of getvar all..
(bootloader) version-main: 2.16.654.4
(bootloader) product: m8_whl
(bootloader) modelid: 0P6B70000
Click to expand...
Click to collapse
This is Sprint version, same as OP based on the model ID and product name. Although main version would indicate the Sprint Harmon Kardon version. RUU can be found at the bottom of the following webpage: http://www.htc.com/us/support/htc-one-m8-harman-kardon-edition-sprint/news/
The M8x designation on the back cover can't be trusted in this case. The back cover has been replaced to remove the "Sprint" logo branding. We've seen several phones like this (back cover replaced to remove evidence of branding) on the forum. You have to go by the getvar data.
Also, be sure to remove your IMEI and serial number from the getvar output. These are personal data, and should never be posted online.

redpoint73 said:
That being said, I would strongly caution you moving forward, to not flash any firmware or RUU to this device except Sprint M8 firmware/RUU. Reason being, the partitioning on the Sprint phone is different from most other versions; and flashing another version's firmware can lead to a radio brick (phone boots, but nothing requiring the radio will work).
Click to expand...
Click to collapse
Thanks a lot for the tip! I'll bear that in mind going forward.

Hi there I seem to be having similar issues. I purchased a refurbished M8. The case indicates 0P6B110 M8x however fastboot getvar all gives:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.09.20.0209
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.30.651.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: [REDACTED]
(bootloader) imei: [REDACTED]
(bootloader) imei2: Not Support
(bootloader) meid: 99000499237658
(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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Going off the info in the thread I downloaded RUU 6.20.651.3.
While verifying I want to update the ROM version it states:
From:
Image Version: 1.54.651.8
To:
Image Version: 6.20.651.3
After clicking next and progressing I get Error 155.
On the fastboot recovery screen shows:
*** LOCKED ***
m8_whl pvt ship s-off
cid-111111111
hboot-3.16.0.0000
radio-1.09.20.0209
opendsp-v38.2.2-00542-m8974.0311
os-3.30.651.2
eMMC-boot 2048
loading zip info fail
RUU
Any help with this would be greatly appreciated.

metalbassist33 said:
On the fastboot recovery screen shows:
*** LOCKED ***
m8_whl pvt ship s-off
cid-111111111
hboot-3.16.0.0000
radio-1.09.20.0209
opendsp-v38.2.2-00542-m8974.0311
os-3.30.651.2
eMMC-boot 2048
loading zip info fail
RUU
Any help with this would be greatly appreciated.
Click to expand...
Click to collapse
To run a Marshmallow RUU, you need to fastboot flash its firmware.zip first.
1. flash 6.20.651.3 firmware.zip
2. run RUU
You should be able to find the firmware.zip in Sprint section
Or you try to find one version lower (lollipop) than 6.20.651.3 RUU, run it then do OTA to 6.20.651.3

ckpv5 said:
To run a Marshmallow RUU, you need to fastboot flash its firmware.zip first.
1. flash 6.20.651.3 firmware.zip
2. run RUU
You should be able to find the firmware.zip in Sprint section
Or you try to find one version lower (lollipop) than 6.20.651.3 RUU, run it then do OTA to 6.20.651.3
Click to expand...
Click to collapse
Just to confirm, if I get a lollipop version, do I still need to fastboot flash a firmware.zip?

metalbassist33 said:
Just to confirm, if I get a lollipop version, do I still need to fastboot flash a firmware.zip?
Click to expand...
Click to collapse
No .. not needed, run Lollipop RUU then do OTA to Marshmallow

Problem going back to stock ROM after installing Google Play Edition with TWRP

Hello there.
I searched through several threads here (and other places) and I'm unable to solve the problem.
I have a HTC M8 European standard version (eg. Sense). I unlocked the bootloader using the official way and installed Marshmallow using OTA.
I was in the mood of trying Google Play Edition and reaching S-OFF (using Sunshine), rooting the terminal and with the help of TWRP, GPE was installed and it is working.
Now I want to go back to my senses keeping S-OFF and the terminal unlocked. And the problems began. Using any RUU, IMG or whatever I am unable to go back. A lot of links in some guides are broken and trying several RUUs in what seem to be the best places (below), I am unable to install it. With TWRP is the error 7 (that I am unable to solve) and with RUUs tells me the ROM is not the appropiate one:
The information about my terminal is as follows:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.29.214500021.12G
version-cpld: None
version-microp: None
version-main: 6.12.401.4
version-misc: PVT SHIP S-OFF
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: HTC__304
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 76df2b54
hbootpreupdate: 11
gencheckpt: 0
all: Done!
****************
M8_UL PVT SHIP S-OFF
CID-HTC__304
RADIO-1.29.214500021.12G
OpenDSP-v51.2.2-00593-M8974_FO.1015
OS-6.12.401.4
eMMC-boot 2048MB
Dec 17 2015,14:15:48.234
Somebody can help me, please?
Regards.
RUU Sources:
https://www.androidfilehost.com/?w=files&flid=13992
http://forum.gsmhosting.com/vbb/f48...-ruu-4-x-x-6-x-x-updated-19-3-2016-a-1940130/
http://androidruu.com/?developer=M8

Skip the relocking bootloader part ...
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6

ckpv5 said:
Skip the relocking bootloader part ...
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Click to expand...
Click to collapse
Thanks for answering.
If I understand you correctly I do not need to relock the telephone. Am I right?
Cheers.

aturdido said:
If I understand you correctly I do not need to relock the telephone. Am I right?
Click to expand...
Click to collapse
That is correct. With s-off, you never need to relock the bootloader in order to RUU. The bootloader lock check is bypassed with s-off.

Hello there.
Thanks for the help. I'm back to my senses.
Just two things related to the guide you suggest. As I had already installed HTC Sync I had both adb and fastboot so I used them.
Thanks again ckpv5 and redpoint73. :good:
Cheers.

Selfie camera problem

I bought my htc one m8 2 months ago.The selfie camera used to work,now it doesn't.I can't even click on the selfie button,when i go into dual mode the front camera appears black in colour and i can't take any photos using the dual camera anymore. so i don't know if the system updates affected the mode.My phone is updated to the newest system update after installing a custom rom ( skydragron v10)

wahab97 said:
My phone is updated to the newest system update after installing a custom rom ( skydragron v10)
Click to expand...
Click to collapse
How exactly was that update accomplished?

I have installed the skydragon custom rom

Is returning to a stock rom could be the solution?

redpoint73 said:
How exactly was that update accomplished?
Click to expand...
Click to collapse
@wahab97
You haven't really answered this question. How did you update - via OTA, via RUU or did you just install a MM backup and never updated your device's firmware? Or were you just flashing a ROM? Could you please post your getvar all? Remove imei and serial no. and post this here.

I flashed the custom rom by unloking the bootloader and installing TWRP the phone was in 4.4.2 androud version the rom contains android 5.0 lolipop this is how i have uptaded my htc

wahab97 said:
I flashed the custom rom by unloking the bootloader and installing TWRP the phone was in 4.4.2 androud version the rom contains android 5.0 lolipop this is how i have uptaded my htc
Click to expand...
Click to collapse
So you never updated firmware of your device. Can you please post getvar all as mentioned?

No. I don't know about getvar can you tell me how to do?

wahab97 said:
No. I don't know about getvar can you tell me how to do?
Click to expand...
Click to collapse
fastboot getvar all
adb, drivers etc should be installed already

You mean CID and MID?

wahab97 said:
You mean CID and MID?
Click to expand...
Click to collapse
That's what we'll get as well if you post the results. But getvar gives more information which is needed to help you.

I will post the results but can you tell me what do you search? what 's the relation about this and the selfie camera problem?

wahab97 said:
I will post the results but can you tell me what do you search? what 's the relation about this and the selfie camera problem?
Click to expand...
Click to collapse
According to your posts you never updated firmware, you just installed a MM ROM. So your firmware seems outdated. We need you to go back on stock (with right firmware as well in case you want to install other ROMs and most posted here need at least MM firmware) to determine if your phone works correctly on stock or you have a hardware issue

results
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.09.20.1112
version-cpld: None
version-microp: None
version-main: 3.30.651.2
version-misc: PVT SHIP S-OFF
meid: 99000499591940 product: m8_whl
platform: hTCBmsm8974
modelid: 0P6B70000
cidnum: 11111111
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 205bdca3
hbootpreupdate: 11
gencheckpt: 0

wahab97 said:
results
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.09.20.1112
version-cpld: None
version-microp: None
version-main: 3.30.651.2
version-misc: PVT SHIP S-OFF
serialno:
imei:
imei2: Not Support
meid: 99000499591940
product: m8_whl
platform: hTCBmsm8974
modelid: 0P6B70000
cidnum: 11111111
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 205bdca3
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
No wonder you have issues. Your phone is a sprint one and you use a newer ROM with old firmware.
To update your firmware etc follow this thread
https://forum.xda-developers.com/showthread.php?t=2729173
PS: edit your Post and remove imei and serial no.

what's the difeerence between HK an no HK? i didn't understand the steps

wahab97 said:
what's the difeerence between HK an no HK?
Click to expand...
Click to collapse
The HK is a variant of the sprint m8. For your phone you need the non hk. Follow instructions in the thread (firmware first, ruu second). If you run into issues post in the linked thread.

i will lose the root access after flashing this ? and another question i have to unistall the snapdragon ROM before flashing this or no?

wahab97 said:
i will lose the root access after flashing this ? and another question i have to unistall the snapdragon ROM before flashing this or no?
Click to expand...
Click to collapse
Of course you will lose root. But that's not an issue to get root back. But your main priority should be hardware and whether your phone works correctly or not.
Your installed rom is not an issue as well.

Last question can i flash the firmware only and let the skydragon rom?