Develop Bugs

[Q] Unfortunately camera stopped

Hi there,
I am using an HTC One M8. I was using a SkyDragon ROM (SkyDragon+M8+v+3.1+WWE+Sense+7.zip). It was buggy as hell, the phone seemed to be happy for a while but as time went on it just slowed down and slowly camera performance started to degrade. Eventually the camera simply wouldn't work. I view this as a software related issue. I thought maybe it would be better to change to a different more recent ROM so I installed ViperOneM8 4.3.0 and got the phone running again. The camera still doesn't work.
I've searched on Google for a fix to this issue but most posts either suggest a clearing of the camera cache (which didn't work) OR a factory reset (which I didn't do because I just installed a new ROM, so same thing right??) OR they suggest tweaking some setting in your LastPass Manager or other password management tools (I don't have these installed).
I've tried other camera apps to see if it can get working but no other camera app works either, they all give similar errors, "Camera not working", OR "Can't connect to camera", and so on....
I don't believe this to be a hardware failure, it must be a software fault because everything was fine until I unlocked the boot loader and started installing custom ROM's. Any help will be greatly appreciated. Oh and in case anyone is curious I am on the latest version of TWRP, and I have repaired permissions (not that its necessary). Thanks for the help guys
Regards,
Saragn

Did you make a nandroid of you stock ROM? If so, restore it and see if the camera issue persists.
If not, why the heck not???

redpoint73 said:
Did you make a nandroid of you stock ROM? If so, restore it and see if the camera issue persists.
If not, why the heck not???
Click to expand...
Click to collapse
Hi...I didn't make a NANdroid backup of the stock ROM. In hind sight I probably should have.

Try ruu to go back to stock and see if that makes a difference.... If in stock it doesn't work then you might have a hardware defect

danial.aw said:
Try ruu to go back to stock and see if that makes a difference.... If in stock it doesn't work then you might have a hardware defect
Click to expand...
Click to collapse
It's a hardware fault. I have a 3rd party app that is not a camera app BUT allows you to upload pics into the app via a camera function. When you hit the button to take a pic it connects to the camera but the picture is just stripes and purple haze. It's heat damage, I think.

Saragn said:
It's a hardware fault.
Click to expand...
Click to collapse
There is no way you can be sure of that, if you don't return to stock. It doesn't seem you've done any troubleshooting to confirm its not software or firmware. In particular, the firmware is the bridge between software and hardware, and can be fooling you into thinking its a hardware issue. And the fact the problem arose after flashing ROMs (and going from old ROMs to recent ROMs) is highly suspicious, and almost certainly means you firmware is outdated.
What is your hboot number?

redpoint73 said:
There is no way you can be sure of that, if you don't return to stock. It doesn't seem you've done any troubleshooting to confirm its not software or firmware. In particular, the firmware is the bridge between software and hardware, and can be fooling you into thinking its a hardware issue. And the fact the problem arose after flashing ROMs (and going from old ROMs to recent ROMs) is highly suspicious, and almost certainly means you firmware is outdated.
What is your hboot number?
Click to expand...
Click to collapse
Hi,
HBOOT number is: HBOOT-3.19.0.0000
Ok so maybe I should have mentioned why I thought its a hardware failure issue. When I unlocked the bootloader and installed the SkyDragon ROM the camera was fine, there was no issue with it whatsoever. That was for about a month. Then as time went on the camera app would cause the phone to seriously slow down when I tried using the camera. It would hang for up to two minutes, you would not be able to switch the phone off or do anything. When it did that you had to leave it to let it get over what ever was going on and then a restart would get the phone back to normal.
Then, after weeks and weeks of that, the camera eventually just died and would not start at all and that's where I am now with it. The next problem I have is that I do not know how to return to stock, I made no "NANDroid" backup of it before I installed the SkyDragon ROM. I didn't see anything on any of the forum "how-to" documents speak about doing a NANDroid backup, had I seen it I'd have done it.
So in short, I have done "some" troubleshooting, maybe just not to the level that you are comfortable with. So do you understand now why I think it's a hardware fault?
Thanks for the replies.
Saragn

Saragn said:
So do you understand now why I think it's a hardware fault?
Click to expand...
Click to collapse
Do you understand why I might be skeptical of that? See from your first post:
Saragn said:
I don't believe this to be a hardware failure, it must be a software fault because everything was fine until I unlocked the boot loader and started installing custom ROM's.
Click to expand...
Click to collapse
It seems your story is changing. Or at the least, you didn't give the full story to begin with, which makes it hard for us to help.
I'd still recommend returning to full stock. It certainly doesn't hurt, and helps to eliminate the possibility that its a software issue. You've now probably spent more time giving excuses to not return to stock; than it would have actually taken to do so.
Either find your stock nandroid for your CID from the collection here: http://forum.xda-developers.com/showthread.php?t=2701376
Or run the RUU if there is one for your CID.

redpoint73 said:
Do you understand why I might be skeptical of that? See from your first post:
It seems your story is changing. Or at the least, you didn't give the full story to begin with, which makes it hard for us to help.
I'd still recommend returning to full stock. It certainly doesn't hurt, and helps to eliminate the possibility that its a software issue. You've now probably spent more time giving excuses to not return to stock; than it would have actually taken to do so.
Either find your stock nandroid for your CID from the collection here: http://forum.xda-developers.com/showthread.php?t=2701376
Or run the RUU if there is one for your CID.
Click to expand...
Click to collapse
Well, yes, of course the story is changing because what I have experienced with the phone since posting this has made me think otherwise. It's been some time since the first post. At first I thought it was software but then the cues I got from the device seemed more hardware related. Being human my mind is allowed to change. My follow up posts have clearly explained everything.
I never discounted the idea of returning to stock, neither did I make excuses for not wanting to I don't think. You have a very funny way of helping someone mate, either way I do appreciate it, maybe not your tone, but that's irrelevant. Thank you for responding and helping out I do appreciate it.

@Saragn: a custom rom is just that. its been modified, hacked, changed, upgraded. it was built on the devs own phone which means it works perfect (unles he says why it doesnt) on that exact model.
even if you have that model its possible that there are minor differences that cause that rom to not work perfect on yours.
as @redpoint73 says, the only way really now is to go back completely to stock and try it again.
if it works then you will just have to try different roms until you find one that works for you.
if it doesnt, its almost certianly hardware and you need to return it. which will require it to be stock anyway.
this is a good time to learn how to take a nandroid backup so you can easily swap back again to try something else.
p.s. check out @redpoint73 thanks count. at least 3834 people on here appreciate what hes doing to help here and are obviously not bothered about his 'tone'

gazzacbr said:
@Saragn: a custom rom is just that. its been modified, hacked, changed, upgraded. it was built on the devs own phone which means it works perfect (unles he says why it doesnt) on that exact model.
even if you have that model its possible that there are minor differences that cause that rom to not work perfect on yours.
as @redpoint73 says, the only way really now is to go back completely to stock and try it again.
if it works then you will just have to try different roms until you find one that works for you.
if it doesnt, its almost certianly hardware and you need to return it. which will require it to be stock anyway.
this is a good time to learn how to take a nandroid backup so you can easily swap back again to try something else.
p.s. check out @redpoint73 thanks count. at least 3834 people on here appreciate what hes doing to help here and are obviously not bothered about his 'tone'
Click to expand...
Click to collapse
Hi,
Pardon the length of time it has taken me to reply. I was away on business for a while so couldn't really pay much attention to the phone. Ok so my CID number is HTC__016. Also, if I do a "getvar all" I get the following:
C:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.401.10
(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: HTC__016
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.173s
I've looked for an RUU exe or zip that works. The RUU packages for this specific version (4.16.401.10) all come out corrupt. I've downloaded various versions from all over this forum, other forums, I think I've downloaded over 10GB in total, 7 or 8 different downloads and they all come out corrupt and so the RUU process doesn't work. I'm not sure where else to get an actual RUU file that works and that isn't corrupt.
Any ideas? Not sure what to do next. Thanks guys.
PS...Never mind about the tone, its how I read it....doesn't matter!

Saragn said:
Hi,
Pardon the length of time it has taken me to reply. I was away on business for a while so couldn't really pay much attention to the phone. Ok so my CID number is HTC__016. Also, if I do a "getvar all" I get the following:
C:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.401.10
(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: HTC__016
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.173s
I've looked for an RUU exe or zip that works. The RUU packages for this specific version (4.16.401.10) all come out corrupt. I've downloaded various versions from all over this forum, other forums, I think I've downloaded over 10GB in total, 7 or 8 different downloads and they all come out corrupt and so the RUU process doesn't work. I'm not sure where else to get an actual RUU file that works and that isn't corrupt.
Any ideas? Not sure what to do next. Thanks guys.
PS...Never mind about the tone, its how I read it....doesn't matter!
Click to expand...
Click to collapse
ALSO....I've checked this thread: http://forum.xda-developers.com/showthread.php?t=2735235 and it doesn't seem to work. I can't get the device to be S-OFF as the thread suggests and it also doesn't show up as LOCKED....it still shows UNLOCKED. So I'm a bit lost now.

Saragn said:
ALSO....I've checked this thread: http://forum.xda-developers.com/showthread.php?t=2735235 and it doesn't seem to work. I can't get the device to be S-OFF as the thread suggests and it also doesn't show up as LOCKED....it still shows UNLOCKED. So I'm a bit lost now.
Click to expand...
Click to collapse
hi, the thread you are quoting there is for going completely back to stock for selling or rtm for repair.
you dont need to go that far.
S-ON/OFF is the security lock, you dont need to bother with that for what you are doing.
LOCKED/UNLOCKED is for the bootloader. you unlocked it to flash a custom rom now you have to relock it to go back to stock.
you will need to relock the bootloader for this if you are still S-ON but this can be done easily through fastboot usb on the phone and 'fastboot oem lock' from a command prompt.
if you have the right stock zip file for your phone you can flash it back to stock anyway by renaming it to 0P6BIMG.zip, copying it to the sd card and booting to hboot.
hboot it will check the file then ask if you want to install it.
note that you can open and view the zip file but cannot safely extract anything from it. it is probably not corrupt.
check the MD5 if you want to be really sure.
an ruu.exe can be done from windows but there are not many of those around.
(anyone else reading here please correct me if i am wrong)

gazzacbr said:
hi, the thread you are quoting there is for going completely back to stock for selling or rtm for repair.
you dont need to go that far.
S-ON/OFF is the security lock, you dont need to bother with that for what you are doing.
LOCKED/UNLOCKED is for the bootloader. you unlocked it to flash a custom rom now you have to relock it to go back to stock.
you will need to relock the bootloader for this if you are still S-ON but this can be done easily through fastboot usb on the phone and 'fastboot oem lock' from a command prompt.
if you have the right stock zip file for your phone you can flash it back to stock anyway by renaming it to 0P6BIMG.zip, copying it to the sd card and booting to hboot.
hboot it will check the file then ask if you want to install it.
note that you can open and view the zip file but cannot safely extract anything from it. it is probably not corrupt.
check the MD5 if you want to be really sure.
an ruu.exe can be done from windows but there are not many of those around.
(anyone else reading here please correct me if i am wrong)
Click to expand...
Click to collapse
Hi...Thanks for the response.
Ok so I've done all of that, oem lock...I have confirmed on multiple ROM's that I cannot open the zip file. When you try open it simply to view the contents windows says it cannot open the file as it is corrupt. I'm fairly certain I know how a zip file works and how to tell when the archive is corrupt. I tried each file on more than one computer and they all say the same thing so the file locations, mostly listed on threads on this forum, all result in faulty downloads. I have a big pipe at the office so can download anything fairly quickly. So I don't know where to find a zip file that works....I have done the whole renaming to 0P6BIMG.zip but the file does not work, none of them do...I've tried several downloads from several different locations and they are all corrupt.
Really, it can't be that much of a challenge to get back to stock. I don't know why the oem lock doesn't work but they device stays unlocked...the bootloader screen confirms this.

Hi,
not sure why the bootloader will not relock.
only other alternative is to pay $25 for sunshine and get S-OFF then you can install the rom without relocking the bootloader.
maybe if you mention the exact names of the stock roms you have tried, i assume they were from the xda rom collection, in that thread and check if someone has already used one of them.
did get the MD5 and check that out?
there is only one rom for mine (dual sim) which i downloaded before and that works perfectly, but as i said, i can actually open the zip file but just not extract it.

My HTC M8 developed random reboot after a failed factory reset

My HTC M8 run into problem since after failed to upgrade to marshmallow via OTA. It was stuck at HTC logo but manage to revive after follow instructions at http://forum.xda-developers.com/htc-one-m8/help/htc-one-m8-htc044-stuck-htc-logo-ota-t3303043 as i have the same exact model in post. I follow everything except flash back stock recovery image which is optional as suggested in post. I kept TWRP just in case it bricked again. Yes, i do relocked the bootloader and it is all fine.
After few weeks for good running, i come to the point that i need restore it from my previous backup. So,i do a factory reset from HTC settings. It reset and rebooted but nothing nothing change. Then, i try to go recovery mode but just it just reboot. Then, i suspect it is the relocked cause the reset cant complete as not possible to get into recovery mode. So, i do unlocked again and reboot to recovery and it does continue the factory reset but failed with message "openrecovery script failed". So, i just use the TWRP to reset and all goes well again but random reboot happened. sometime happen in few mins, sometime hours.
i tried to restore it again as the steps i revive from bricked but random reboot still there. Even restore the stock recovery and relocked and reset again and random reboot still happened. I'm really completely no idea what to do fix it. move to custom rom? Root it and fix the write permission problem? Please guide me what i can do next. I just need to get it back to working condition regardless what rom as long as stable. thank you.

chyeoh said:
My HTC M8 run into problem since after failed to upgrade to marshmallow via OTA. It was stuck at HTC logo but manage to revive after follow instructions at http://forum.xda-developers.com/htc-one-m8/help/htc-one-m8-htc044-stuck-htc-logo-ota-t3303043 as i have the same exact model in post. I follow everything except flash back stock recovery image which is optional as suggested in post. I kept TWRP just in case it bricked again. Yes, i do relocked the bootloader and it is all fine.
After few weeks for good running, i come to the point that i need restore it from my previous backup. So,i do a factory reset from HTC settings. It reset and rebooted but nothing nothing change. Then, i try to go recovery mode but just it just reboot. Then, i suspect it is the relocked cause the reset cant complete as not possible to get into recovery mode. So, i do unlocked again and reboot to recovery and it does continue the factory reset but failed with message "openrecovery script failed". So, i just use the TWRP to reset and all goes well again but random reboot happened. sometime happen in few mins, sometime hours.
i tried to restore it again as the steps i revive from bricked but random reboot still there. Even restore the stock recovery and relocked and reset again and random reboot still happened. I'm really completely no idea what to do fix it. move to custom rom? Root it and fix the write permission problem? Please guide me what i can do next. I just need to get it back to working condition regardless what rom as long as stable. thank you.
Click to expand...
Click to collapse
Here is the getvar all and hope someone can suggest what i can do next. Thank you in advance.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.14.707.1
(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: 0P6B11000
(bootloader) cidnum: HTC__044
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.260s

You can certainly try a custom ROM. Its not any more invasive that what you've already done. Just unlock the bootloader again (leave it unlock - more on this later), flash TWRP (even if its still installed, it looks like it has some issues and can use a fresh install) and flash a custom ROM.
In any case, don't worry about relocking the bootloader, its not doing you any favors; and just creating more steps for yourself. Relocked bootloader is only needed to flash RUU or stock firmware (not required for OTA or anything else you are doing).

[Solved] random reboot on my M8
Thanks redpoint73 and ckpv5, i quite confirmed that i just manage to fix my random reboot problem. the solution i do the the alternative way to unbricked M8 on the same post at http://forum.xda-developers.com/showpost.php?p=66274104&postcount=18.
Anyway, here i would like to add more finding about my problem which i has spent this few weeks to observed. the problem that i has is actually corrupted radio baseband. there are few hints i get indicating my M8 having radio based problem.
1. in M8, go to settings > About > Software information > More. there you will see all OS related info and baseband version but my baseband version showed "Unknown" instead of 1.29.214500021_2G.
2. then, back to About and go to Phone identity. there i suppose can see my IMEI and IMEI SV but in my case also showed "Unknown".
3. whenever after the M8 rebooted, it will ask to send error Report to HTC. there you can get to page where it shows the M8 detail and also the Log. just tap on Log and it will open up the error log first. there is where i get to know my problem is in the radio baseband. at almost end of stock, there is 1 log like reboot-reason=modem-crash and something like "oem-98". both also indication radio or modem has problem. this is where i think i should fix the baseband problem and guess it will fix this random reboot problem.
after restore the 1 version earlier stock rom and recovery and upgrade via OTA and not radio baseband is fix and first 2 item above can be view at about page now.
i hope my sharing can help others and avoid go through so much of hassle and time to figure out what's wrong.

HELP, m8 stuck in bootloop at "starting apps."

hi i've got a huge problem with my htc m8. it wont boot anymore and always keeps on beeing stuck on "android is starting... starting apps." after an optimization of 167 apps. have been pulling an all nighter and im at the end of the rope unfortunatly =(.
i alrdy hard reset it several times. through bootloader factory reset, as well as recovery and wipe data/fac reset. i only can stop the bootloop by pressing power+volume up and switching into bootloader. it also takes forever to optimize the 167 apps....
after having read a few threads here and elsewhere i also did 2 recoverys with 0P6BIMG.zip with an miniSD card through bootloader/fastboot and once through htc_fastboot with RUU.zip through the CMD in win10. in all 5 cases the phone tells me it successfully "recovered"/reset its system but it still always starts again with optimizing 167 apps and then beeing stuck on "starting apps...".
the m8 is ***locked*** and S-ON with software status official. OS- 6.12.401.4. i never customized the android os and bought it brand new.
(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:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.051s
im grasping for straws here guys (desperately). appreciate all the help i can get. there are a lot of people here who seem to be experts in this. i am totally new to this and really hoping for guidance. thanks in advance!

I`ve had a similar issue today, while trying to revert my phone from an update to GPE Rom.
I was able to reboot my phone, and get back to the bootloader, and from there I flashed to a stock rom.
What I did was, volume up + power, and just when the phone turned black, I pushed the volume down button, and it entered the bootloader instantly.
Sorry if it didn`t help you out much, but I was stuck in the updating apps, and was able to get off rebooting loop only like that, I was stuck for about an hour on that!
Good luck!

Chubbiebr said:
I`ve had a similar issue today, while trying to revert my phone from an update to GPE Rom.
Click to expand...
Click to collapse
The OP has a stock device, so the situation is really not similar, nor have the same solution.
In addition, what the OP neglected to post here (but posted in another thread) is that his issue was caused by dropping the phone, and going major physical damage. No amount of software fixes is going to help the OP:
http://forum.xda-developers.com/showpost.php?p=67417831&postcount=1761
Chubbiebr said:
I was able to reboot my phone, and get back to the bootloader, and from there I flashed to a stock rom.
What I did was, volume up + power, and just when the phone turned black, I pushed the volume down button, and it entered the bootloader instantly.
Sorry if it didn`t help you out much, but I was stuck in the updating apps, and was able to get off rebooting loop only like that, I was stuck for about an hour on that!
Click to expand...
Click to collapse
What exactly did you try to flash (file name) and flash it how (TWRP, fastboot, etc.).?
What was the original condition? "revert from an update to GPE Rom" really isn't specific enough.
Were you on a GPE ROM, or did you fully convert to GPE using RUU (2 very different things)/ Bootloader screen is black or white?
Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).

redpoint73 said:
In addition, what the OP neglected to post here (but posted in another thread) is that his issue was caused by dropping the phone, and going major physical damage. No amount of software fixes is going to help the OP:
http://forum.xda-developers.com/showpost.php?p=67417831&postcount=1761
Click to expand...
Click to collapse
i didnt drop the phone. a 2.5 kg plate dropped on it. and i also dont think its interior is broken because of that. only the display glass is broken. the phone was working fine for hours until i tried to use the front camera and the camera app froze up. up to that point all functions were normal apart from the visuals of the broken display glass. even the touchpad/digitizer and colours of the display are working at 100%.
because of that frozen camera app i rebooted the phone. thats when it started to bootloop. the bootloader is also working fine. dislay is still working fine. it just wont boot beyond optimizing apps....
the only hardware problem that could be is: if the front camera is mailfuntioning. can it stop the android os from booting? thats the only explanation it could have for a bootloop hardware wise. if thats not the case its purely a software problem

HTC M8 Logo loop issue
Hi There
Were u able to find a fix for the below issue. Am also having the same problem with M8.

nithinrv said:
Hi There
Were u able to find a fix for the below issue. Am also having the same problem with M8.
Click to expand...
Click to collapse
You dropped a 2.5 kg plate on your M8, and caused physical damage also, like the OP? You tried to flash the RUU through htc_fastboot and SD card methods?
Please don't just post you have the "same problem" without giving any details. My experience, that these issues are never exactly the same (simply too many variables: different CIDs, version numbers, causes for the issue) and if you don't give any details, nobody can provide the proper help.
At a minimum, describe what events led to the current condition (and what that condition is), what you've tried (specific steps, file names, etc.) and the specific outcomes (error messages, other outcomes). Also do fastboot getvar all, and post the output (delete IMEI and serial number before posting).

even i had the same prob..i fixed it by wiping the cache partition..
get into bootloader menu ..go to recovery..and then after the red exclamatory sign appears..keep pressing power button and hold and release volume up button..you will get the wipe cache partition option.
do dat and ur phone will reboot

power and volume up press.

roker22 said:
power and volume up press.
Click to expand...
Click to collapse
Is this a question or a statement? The last post already says power + vol up.
Do you realize you responded to a thread that hasn't been active for over 2 years (August 2016)? Worthwhile contribution is always appreciated. But you decided to make this your first post to xda?

Help needed with HTC m8 (root succeeds, stuck at htc login)

Hello dear xda users,
Sometime ago, I have posted questions about my htc m8 being unable to read sim card. Unfortunately, I have still not been able to solve the issue and it stands as a wifi device at present Anyway, this post im posting is about a friend's m8 which she passed to me to inquire if i knew of a solution to fix it. Her phone, if I am not mistaken (though she says that she bought it off a phone dealer locally), is theoretically not a local device. I did a check on it and it says m8_ul. I'm currently residing in Taiwan and after looking around, m8_ul either belongs to europe or australia. She was experiencing com.process.gapps error issues and made it impossible to use the device in any and every way. Googling around, I found threads regarding this issue (or similar) asking the user to clear the cache of all google services. I proceeded to do it and the result was no different. So I thought about rooting the device and maybe even flashing to stock (or modified stock) to get the phone working again.
The problem that I have at hand is that flashing TWRP works fine. It boots into the system and I could use adb to reboot into fastboot (despite the errors popping up). After that, I rooted the phone and now it just stays on the HTC logo until the battery dies out (by leaving it for as long as need be). It is also impossible to do a normal force shutdown(holding power for x number of secs *tried using power + vol up/down/both) or the "under a bright light" method.
So is there anyone who is kind enough and willing to extend a helping hand here? With a guide or something? :crying: Thanks in advance.
Here's what I got from her my getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.709.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT4BLWM04185
(bootloader) imei: 358716054985352
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.030s

you need to back to stock
download the stock TWRP backup and stock recovery for this device
restore the backup and flash the recovery may be you will get one OTA to the latest
here is the TWRP backup
https://mega.nz/#!u5ImFT5R!WZTC0Pi5Dw67xkTEoOxmezJ526WeL3EwEjrKuQgDdHU
and the stock recovery
https://mega.nz/#!rkxSAJCS!8ZFGp7AXMK_gP0Cmoj-vkqjw8VLARx82Be8cwErZwbs
and all the info you need and the instruction is here
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Sent from my HTC M8 using XDA Labs

Thank you ahmed.Ismael. I'll be downloading those in a couple. I hope it goes well. Will post here if it works fine. Thank you.

pacer3 said:
Thank you ahmed.Ismael. I'll be downloading those in a couple. I hope it goes well. Well post here if it works fine. Thank you.
Click to expand...
Click to collapse
there is no reason it will not work
GOOD LUCK
Sent from my HTC M8 using XDA Labs

pacer3 said:
She was experiencing com.process.gapps error issues and made it impossible to use the device in any and every way.
So I thought about rooting the device and maybe even flashing to stock (or modified stock) to get the phone working again.
Click to expand...
Click to collapse
To be clear, and for your information, there is no reason that root alone would fix the issue. There is something wrong with the OS (system processes) so the previous suggestion to restore the stock ROM, is a good one.
Root is just a permission change, it won't "fix" anything in itself besides that (root permissions).
Also, the symptom of rooting and being stuck on HTC logo screen is most usually because you used the wrong version TWRP and/or wrong version SuperSU to root (its common folks are trying to use really old versions of either/both). Since the device is on Marshmallow, you need to use TWRP 3.0.2 and current stable version SuperSU is 2.78.
But again, rooting even properly won't fix the core issue. Restoring the stock ROM is your best bet.

@redpoint73:
Thank you for replying as well. I guess I have to put this away till the next day as I was kinda piled with work today. Really pooped out now, so I'ma go get me some shut eyes. As for what you mentioned, yea.. (1) TWRP was working fine after flashing.. it booted normally and is still functioning properly as of now. (2) It's only after I flashed UPDATE-SuperSU-v2.37 that the m8 wouldnt get past boot screen and stays there frozen till battery drains out. (3) Well, I was thinking of removing the app that was causing the errors and fixing them by installing those applications again from scratch without touching the os and since it said something like com.process.gapps or something of the kind, I'm guessing that it's already related to the os and hence, rooting to remove the corrupted file(s) or replacing new ones (in this case, I'm guessing adb and fastboot to push the files might probably work; which would make rooting unnecessary). So yep, that's my train of thought; to make as little changes to the system, no matter how unstable it might be during the time, and working out the kinks one by one. You know, just so if my friend would need to suddenly use the phone, I might/would have fixed a portion of it for her to be able to use it at that moment. Thanks so much to the both of you. I'm hoping it'll turn out well. I mean, like ahmed.ismael said, what's there for it not to work. Having hopeful thoughts here ^.^

pacer3 said:
[MENTION=660462] It's only after I flashed UPDATE-SuperSU-v2.37 that the m8 wouldnt get past boot screen and stays there frozen till battery drains out.
Click to expand...
Click to collapse
As I guess, that version SuperSU is really old. No boot is the expected result.
pacer3 said:
[MENTION=660462] I was thinking of removing the app that was causing the errors and fixing them by installing those applications again from scratch without touching the os and since it said something like com.process.gapps or something of the kind, I'm guessing that it's already related to the os and hence, rooting to remove the corrupted file(s) or replacing new ones (in this case, I'm guessing adb and fastboot to push the files might probably work; which would make rooting unnecessary).
Click to expand...
Click to collapse
Definitely would not work. Its a system app, part of the OS, and therefore can't be modified without root. Even with root, system is write protected and requires kernel mod.
---------- Post added at 12:22 PM ---------- Previous post was at 12:20 PM ----------
pacer3 said:
I'm hoping it'll turn out well. I mean, like ahmed.ismael said, what's there for it not to work. Having hopeful thoughts here ^.^
Click to expand...
Click to collapse
I too see no reason for it not to work. Its just a software bug, and RUU will return the OS software to its original, intended condition.

sorry for not replying. im reattempting this again now and just a quick question. would rerooting with latest supersu at least fix booting? cause i dont really want to wait till battery dies out everytime i forget to boot directly into bootloader

pacer3 said:
sorry for not replying. im reattempting this again now and just a quick question. would rerooting with latest supersu at least fix booting? cause i dont really want to wait till battery dies out everytime i forget to boot directly into bootloader
Click to expand...
Click to collapse
you don't have to wait for the battery to die!!! when you boot and it boootloops just press the power button and volume up until in restarts and when it restarts quickly press the volume down and power for entering in bootloader...

pacer3 said:
sorry for not replying. im reattempting this again now and just a quick question. would rerooting with latest supersu at least fix booting?
Click to expand...
Click to collapse
It should fix the no-boot issue, yes. But you need to use the correct, up-to-date version TWRP (3.0.2) and SuperSU 2.78.

Hi all and thank you for the replies so far and sorry for the late reply. Been outstation for work again so I haven't been able to get on to reply to you guys.. Anyway, I have just completed all the steps until step 11 and now waiting on step 12 (after reboot in this tutorial http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860). Thank you for all your replies and will keep you guys posted on the progress. Hope it turns out well (crosses fingers). ^.^

Hey all. Thank you guys for assisting me with this problem. It has been fixed. ^.^ I dont know how i can repay you guys for assisting me, especially ahmed.ismael for providing the links and guide. It has been a big help for me. I deeply thank you guys for giving a helping hand here. Wish it could fix my problem with my own m8 HK edition.

Soft bricked? HTC M8

Hello!
A few years ago i got the HTC One M8 through my carrier here in sweden, 3 (tre).
All was good until my phone started crashing as soon as I opened my camera so i sent it to the 3s tech and they changed camera or smthn..
The phone was shipped back to me and it still did the same thing and now it showed error messages (stopped unexpectedly xx) on every app that was running. So I told them and then sent it back to them and they changed a bunch of **** and told me they couldnt recreate the issue.
I got the phone back again and started it up. Would barely start-up at all, stuck on HTC screen, after a while it started and i opened the camera, crashed. So I sent them an angry message of how hard it can be to open the camera and get a crash, since I myself did it so many times and it crashed every time.
Sent it back and they switched battery. Now the phone started to not get pass HTC even worse and needs a few restarts before it boots, it dies after maybe 1-2 hours from no battery and i get constantly spammed with errors from every app saying "stopped unepectedly".
Sent the phone back to them again (phone was sent back and forth for like 6 months) and they said the warranty had ran out. So i said **** you and got a new phone.
Now though.. I want to get my HTC One M8 running again, and im thinking that maybe it will run properly if i dont open the camera etc if i can flash it with a correct RUU since it now gets stuck on HTC and wont boot at all unless i restart it like 15 times.. But maybe its some weird outdated software issue and if i flash it with to start with the correct RUU it will run better again, if that doesnt work, maybe a custom ROM will? ..
I will post the getvar or w/e after my meeting now, but any ideas in the meanwhile?
Thanks beforehand
From Samsung Galaxy S8

Well, we can try to help you to find the right ruu, but we need a getvar all first.

lucyr03 said:
Well, we can try to help you to find the right ruu, but we need a getvar all first.
Click to expand...
Click to collapse
How do i do that? Ive never done **** with phones before and tried googling but nothing anywhere..

Czelious said:
How do i do that? Ive never done **** with phones before and tried googling but nothing anywhere..
Click to expand...
Click to collapse
I highly doubt that is a true statement. You either aren't searching the right terms (fastboot getvar all) or don't understand what you found, and want folks to spoon feed you the information.
You will find plenty of info on how to do this on both the XDA search function (recommended), or using Google.
I understand that working with these devices is new to you. But I would suggest starting with search, read and learn. The information is all here, if you take the time to look.

redpoint73 said:
I highly doubt that is a true statement. You either aren't searching the right terms (fastboot getvar all) or don't understand what you found, and want folks to spoon feed you the information.
You will find plenty of info on how to do this on both the XDA search function (recommended), or using Google.
I understand that working with these devices is new to you. But I would suggest starting with search, read and learn. The information is all here, if you take the time to look.
Click to expand...
Click to collapse
I figured it out, the issue for me is that my phone is wrecked by the Tech team at my carrier, so I look for several issues at the same time and that makes me overlook some info on the sites I find.
Before this I had an issue saying "protocol fault version (31) client (40)" or something and ended up deleting adb from my HTC Manager folder which removed that issue.

lucyr03 said:
Well, we can try to help you to find the right ruu, but we need a getvar all first.
Click to expand...
Click to collapse
Here it is
(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.13.771.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xx
(bootloader) imei: xx
(bootloader) imei2: Not Support
(bootloader) meid: xx
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: H3G__G04
(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!
From what ive read, this is what i need?
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Post #3
CID H3G__001, H3G__106, H3G__402, H3G__G04
MID 0P6B10000
6.13.771.4
https://mega.nz/#!P4IVSALR!-tbQNWwnQI2U25Rd3wGYO6bYKOiLwKSJQs9FhEDAJHE
This happened though since I can't authorize my PC on the phone
C:\Users\totte\AppData\Local\Android\Sdk\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (20304 KB) OKAY [ 2.130s]
Writing 'recovery' (bootloader) signature checking...
FAILED (remote: signature verify fail)
Finished. Total time: 2.895s

Czelious said:
From what ive read, this is what i need?
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Click to expand...
Click to collapse
This is different from an RUU. But I don't think your version has an official RUU, so the method you found is the best you can do. This just restores 2 partitions (system + boot.img) versus RUU which is a complete factory image (40+ partitions).
Czelious said:
This happened though since I can't authorize my PC on the phone
C:\Users\totte\AppData\Local\Android\Sdk\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (20304 KB) OKAY [ 2.130s]
Writing 'recovery' (bootloader) signature checking...
FAILED (remote: signature verify fail)
Finished. Total time: 2.895s
Click to expand...
Click to collapse
You need to unlock the bootloader to flash TWRP. Go to HTCDev. com and follow the process to unlock the bootloader.

redpoint73 said:
This is different from an RUU. But I don't think your version has an official RUU, so the method you found is the best you can do. This just restores 2 partitions (system + boot.img) versus RUU which is a complete factory image (40+ partitions).
You need to unlock the bootloader to flash TWRP. Go to HTCDev. com and follow the process to unlock the bootloader.
Click to expand...
Click to collapse
Ok thnx, ill try (Y)
Been wrestling with the issue to give my PC authority over my phone which seems impossible unless i could get my phone stable :/
If all of this doesnt work out, would a custom ROM be able to fix my issue? My activity bar and back/home buttons aint even working anymore.. since Everything the phone tries to start up "stopped unexpectedly"

Czelious said:
Been wrestling with the issue to give my PC authority over my phone which seems impossible unless i could get my phone stable :/
If all of this doesnt work out, would a custom ROM be able to fix my issue? My activity bar and back/home buttons aint even working anymore.. since Everything the phone tries to start up "stopped unexpectedly"
Click to expand...
Click to collapse
Processes "stopped unexpectedly" will usually be fixed by restoring the stock ROM, or flashing a custom ROM.
But if you have problems with the phone being stable even in bootloader, then you have bigger problems, that flashing a ROM won't fix.

redpoint73 said:
Processes "stopped unexpectedly" will usually be fixed by restoring the stock ROM, or flashing a custom ROM.
But if you have problems with the phone being stable even in bootloader, then you have bigger problems, that flashing a ROM won't fix.
Click to expand...
Click to collapse
Yeah its fixed, only issue now is that my phone keeps restarting on its own randomly, so must be a battery issue :/ Thnx for your help!
Nah, the bootloader was always fine just kept spamming unexpectedly stopped 24/7, and as i said in the original post i left it at the tech with that being the only issue, came back with that issue + random restarts + bad battery time of like 1 hour or so..
Only issue now seems to be the random restarts, havent tested battery time