Develop Bugs

Phone Stuck

All of a sudden my phone hang up.
I booted into the stock recovery - factory reseted and everything and then this happened:
The optimizing started like when I made a wipe and data reset through recovery. xxx out of 164
but as soon as it finished I got the same problem as before:
"Android is starting.. starting apps"
and there it gets stuck
So I unlocked the phone, installed custom recovery and ROM, tried 3 different ones but still get the same issue. What might be the problem?! what can I do... I really dont know what else to do... :/

Do fastboot getvar all, and post the results (delete IMEI and serial number).
What ROMs did you try (and what version numbers)?

redpoint73 said:
Do fastboot getvar all, and post the results (delete IMEI and serial number).
What ROMs did you try (and what version numbers)?
Click to expand...
Click to collapse
(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.12.1540.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT444******
(bootloader) imei: 358718**********
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.018s
I tried the
Venom Viper (which is my favorite on the HTCs)
Android Revolution HD
Maximus HD
all the latest versions!
TWRP have the latest v3 installed too!

Did you wipe data, cache and Dalvik (this is the "default" wipe option in TWRP) before flashing the ROMs?
If so, I can't see anything that is obviously wrong. You might consider running the 6.12.1540 RUU to start from a completely "clean" baseline image, and see if the problem persists. Be aware, RUU will wipe the phone.

redpoint73 said:
Did you wipe data, cache and Dalvik (this is the "default" wipe option in TWRP) before flashing the ROMs?
If so, I can't see anything that is obviously wrong. You might consider running the 6.12.1540 RUU to start from a completely "clean" baseline image, and see if the problem persists. Be aware, RUU will wipe the phone.
Click to expand...
Click to collapse
I have done that 100 times... this crap doesnt boot at all... flashed the stock RUU multiple times! and of course multiple times clean the cache and internal data etc etc... it just wont start... :/
the only thing I didnt do is unlocking the CID... but I dont think this is that important?!

greek_lover_69 said:
I have done that 100 times... this crap doesnt boot at all... flashed the stock RUU multiple times! and of course multiple times clean the cache and internal data etc etc... it just wont start... :/
Click to expand...
Click to collapse
The response makes it sound like you are mad for me asking?
We can't know what you did, if you don't tell us. We aren't mind readers. And what may seem like an obvious thing to you, is a common mistake by many others.
Additionally, the simple answer is often (while not always) the correct one.
greek_lover_69 said:
the only thing I didnt do is unlocking the CID... but I dont think this is that important?!
Click to expand...
Click to collapse
You mean changing the CID? No, I don't see why that would make a difference.
If you've successfully installed the RUU, and the issue persists, I tend to believe this is a random hardware failure (such as emmc going bad). This theory would also explain why this happened "all of a sudden".

redpoint73 said:
The response makes it sound like you are mad for me asking?
We can't know what you did, if you don't tell us. We aren't mind readers. And what may seem like an obvious thing to you, is a common mistake by many others.
Additionally, the simple answer is often (while not always) the correct one.
You mean changing the CID? No, I don't see why that would make a difference.
If you've successfully installed the RUU, and the issue persists, I tend to believe this is a random hardware failure (such as emmc going bad). This theory would also explain why this happened "all of a sudden".
Click to expand...
Click to collapse
no no sorry.. why should I be mad at you.. you are just trying to help... I^m mad at my PHONE!
i^m guessing hardware failure too... can explain it else..
thanks! will have to sent it back.
I bought it from china.. maybe it had a problem and was fixed or something..

greek_lover_69 said:
no no sorry.. why should I be mad at you.. you are just trying to help... I^m mad at my PHONE!
Click to expand...
Click to collapse
No worries. I thought that might be the case (frustrated at the phone) which is why I posed it as a question. You'd be surprised at what folks here can sometimes take as an insult.
In any case, good luck and sorry we couldn't do more to help.

HTC M8: failed to load drivers (wifi and sim)

Hi all,
My gfs phone has had some recent issues with her phone.
First: wifi would be dropped, unable to even turn on the wifi. Error: unable to load drives, reason unknown (19)
So I rooted, unlocked, and flashed with GPE. Worked fine for a few months. Then the same issue occurred, so I flashed again....it got fixed again.
Then last night, it dropped the mobile network. Just kept saying install SIM card.
I did full wipe with TWRP. Tried to reload a GPE rom and it gets to the setup stage. Right away I get "unable to load driver" error. The phone keeps asking me to install SIM card; eventhough there is one in there. And if I skip that step, it won't let me turn wifi....
Is the phone dead? It was originally locked to Rogers in Canada...
Tried GPE, S-ROM, Viper....all coming up with same error of not being able to detect SIM or turn on WIFI during setup....
Any help would be appreciated!
Thanks

Would more info be helpful here?
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.631.7
(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: 0P6B16000
(bootloader) cidnum: ROGER001
(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!
I was able to get sim recognition working by doing a data format, factory wipe, then GPE-ROM re-install, but WIFI still knocked out.
Any suggestions?

So, tried flashing back with a TWRP stock backup
CID ROGER001
MID 0P6B16000
6.13.631.7
Then reverted to stock 6.13.631.7 recovery.
Everything booted fine, then "unable to load driver error 19" came up again.
Wifi and bluetooth basically greyout and freeze everytime I try to turn them on.
Any suggestions as to what I can try next?

So figured out the issue.
Needed to update to latest firmware. Thought I had done that when I flashed back to stock.
Missed the step to relock bootloader before flashing firmware with fastboot.
Firmware update went through, and voila....everything up and running...for now.

I'm experiencing very similar problem myself. It seems like the phone was updated ota but it just bugs way too much. When i try to turn on wifi it says failed to load driver, if i turn the air plane mode on and off, and then try to connect to wifi i again get the error, the phone freezes and is stuck in bootlops.
I'm not experienced in flashing but i would like to try to troubleshoot the problem myself. I've heard about the ruu but i'm not sure about my phone variant, and also, do i need root or any type of unlock to reflash my phone to stock ? Tnx.
PS: I bought phone on ebay and it seems like it is running the correct version of stock sense rom.

petarcrncec said:
I'm experiencing very similar problem myself. It seems like the phone was updated ota but it just bugs way too much. When i try to turn on wifi it says failed to load driver, if i turn the air plane mode on and off, and then try to connect to wifi i again get the error, the phone freezes and is stuck in bootlops.
I'm not experienced in flashing but i would like to try to troubleshoot the problem myself. I've heard about the ruu but i'm not sure about my phone variant, and also, do i need root or any type of unlock to reflash my phone to stock ? Tnx.
PS: I bought phone on ebay and it seems like it is running the correct version of stock sense rom.
Click to expand...
Click to collapse
Bro did you read sticky on top which says FREQUENTLY ASKED QUESTIONS ? Much of what you want to know is already there?
Anyway to start off , You turn off the the phone and hold volume down + power button for a few (say 10) seconds and note what it says and post it here.and before you ask,no its not that dangerous

Knightofrepublic said:
Bro did you read sticky on top which says FREQUENTLY ASKED QUESTIONS ? Much of what you want to know is already there?
Anyway to start off , You turn off the the phone and hold volume down + power button for a few (say 10) seconds and note what it says and post it here.and before you ask,no its not that dangerous
Click to expand...
Click to collapse
I have read FAQ and there is no specific question related to my problem there. I have found a few people having wifi issues and unexpected shutdowns but non of them were able to fix it. Most of them just returned the phone which led me to believe the problem might be coming from the hardware side. I've already tried cleaning the cache partition and multiple hard resets, and nothing helped. I know it is not dangerous to enter recovery, as I said, I have read the FAQ. The only method of retrieving the phone variant i found was typing getvar in the cmd thingy which can again be false, depending on the flashed software/kernel/radio or whatever (yes i don't distinguish between radio and kernel really. I'm a noob as I said). I tried googling about the RUU and the root permition and didn't find anything usefull accept for the fact that phone has to be S-on, which my phone is.
So, I did do my research, but i can't go through 400 or so pages of help thread to find a specific question, that might not be even there in the first place so i asked it here.
Sorry for your time and long post, but I will return the phone tomorow, because I really can't know whether the device is defected or not, better safe than sorry.

well if you can return it then its a good way to do be safe,but as the OP said he solved his problem by updating his firmware . I was going to do suggest just that.l,but as you said you did your research it turned out nothing useful and you have it all figured out anyway ,so good luck

Knightofrepublic said:
well if you can return it then its a good way to do be safe,but as the OP said he solved his problem by updating his firmware . I was going to do suggest just that.l,but as you said you did your research it turned out nothing useful and you have it all figured out anyway ,so good luck
Click to expand...
Click to collapse
Thanks, I'll need it in case the seller tries to scam me again

I experience same problem with my HTC Desire 826 it also says that it fails to load driver unknown reason I have multiple times hard reset it I have not rooted I have upgraded to Marshmallow but also experiencing the same problem it's also get heated my WiFi and bluetooth is not working please help me

sabir.786 said:
I experience same problem with my HTC Desire 826 it also says that it fails to load driver unknown reason I have multiple times hard reset it I have not rooted I have upgraded to Marshmallow but also experiencing the same problem it's also get heated my WiFi and bluetooth is not working please help me
Click to expand...
Click to collapse
You are in the wrong forum
Anyway this issue on the m8 fixed by updating the firmware ask in your device forum about the firmware
Sent from my HTC M8 using XDA Labs

ahmed.ismael said:
You are in the wrong forum
Anyway this issue on the m8 fixed by updating the firmware ask in your device forum about the firmware
Click to expand...
Click to collapse
I have search for my device its not in ur forum plz help me

What is the solution to this erorr? Error: unable to load drives, reason unknown (19)? i have the same

Slow booting

My M8 is a spare phone. Most time it's just sitting in the drawer. However once every one or two months I'm doing the GP updates and checking my other sim for text etc.
Couple days ago I wanted to repeat this. However I was not able to turn on the phone so I thought that battery was drained so I plugged in the charger. Red led did not lit. This is when I started worrying about the phone. I thought that battery is dead but then the phone turned on itself. Phone was operational again and I was happy.
I decided to give another restart and the same happened- phone was not responding for 10min and then was again working.
So the issue is: phone is booting very slow: 10-15 minutes
What I have done so far:
- multiple reboots
- factory reset
- wiping cache partition
- tested with sim and SD card removed
Stock Android 6.0 software number 6.12.401.4. UK model, not branded.
Anyone have seen something like this?
Any suggestion how to fix it?
Thanks in advance
Kruk
Sent from my HTC 10 using Tapatalk

Kruk07 said:
Stock Android 7.0, not rooted. Software number 2.41.401.41.
Click to expand...
Click to collapse
Are you aware that you described the HTC 10, not the M8 there?
Anyway, seems like a battery issue to me, try this:
Turn off Fast Boot in settings. Power off phone.
Plug phone into HTC charger and charge for two minutes or more
While charging, hold down volume up+volume down+power button and continue holding
Phone will turn on and off repeatedly every 15 seconds or so while continuing to hold all three buttons
Keep this going for 2 minutes, then release buttons when phone is ON
Now, let phone charge fully normally (with phone either on or off--doesn't matter) and battery level reporting, charging and battery life should be normalized.
Click to expand...
Click to collapse

You are right. I was posting this on my HTC 10 and automatically checked the version.
Correct version is Android 6.0 software number 6.12.401.4
I think I tried what you're suggesting but the thing is that it takes ages when holding this buttons as booting is slow even in the early stage of the boot. I will give a try again.
One more thing - I do not have option for fastboot in power settings.
Edit
First try - phone turned on the turned off and then nothing despite pressing buttons
Second try - nothing happened at all with pressed buttons for 3 minutes. Once released after 3 minutes phone booted.
Sent from my HTC 10 using Tapatalk
Third try - I hold the buttons for 6 minutes. Phone restarted twice and third time booted into bootloader.
When the screen is black during holding the buttons I can hear static noise so definitely something is happening but very slow.
Any other ideas?

That's weird.
I'd try a RUU to make sure it's not software related. Maybe a partition got corrupted.
Also, the phone fully works then it finally boots up?

Kruk07 said:
Correct version is Android 6.0 software number 6.12.401.4
Click to expand...
Click to collapse
I suspect your firmware is outdated, as this is the main reason for extreme long boot times. The charge/battery events may be a red herring, and unrelated.
Tell us what is says in bootloader for OS number. And if OS numbers is blank, what does it say for hboot and radio baseband numbers?
If you know how (or can figure out how), do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
---------- Post added at 09:25 AM ---------- Previous post was at 09:23 AM ----------
Kruk07 said:
One more thing - I do not have option for fastboot in power settings.
Click to expand...
Click to collapse
"fast boot" hasn't been a power option setting in HTC devices since Kitkat. The feature doesn't exist anymore, and therefore does not need to be "turned off" for any reason.
This "fast boot" option is also not to be confused with the fastboot/adb tool I just mentioned (they are completely different things with very similar names), which is still fully working.
---------- Post added at 09:33 AM ---------- Previous post was at 09:25 AM ----------
Kruk07 said:
Stock Android 7.0, not rooted. Software number 2.41.401.41. UK model, not branded.
Click to expand...
Click to collapse
Is the M8 stock unrooted? Since the details you gave are for the M10, I can't tell if the same (stock unrooted) also applies to the M8 we are trying to fix.

Thanks for the suggestions. I will check later and provide the info.
Just to confirm once fully booted phone is working fine as far as a can see and the system is stock unrooted.
Sent from my HTC 10 using Tapatalk

Please see below info from 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) serialno: FA48xxxx
(bootloader) imei: xxxx
(bootloader) imei2: Not Support
(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
6-8 months ago I have had an issue with GP Services so I flashed the phone with:
0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip
fw_6.12.401.4.zip
There was no issue after the flash. So not sure what is the reason for this problem.

Strange, I haven't seen an issue with slow boot like this, except from outdated firmware. Your firmware is up to date (and this is typically an issue of custom ROM, root, etc.)
I would suggest run the RUU again. If the issue persists, it may be a hardware issue.

Ok, I managed to find link I used previously: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
I flashed the RUU and all seems to be working fine, booting is now taking 30sec to the set up screen. I now need to recover the apps and settings.
Any idea what caused this problem?
Thanks for all suggestions.

Kruk07 said:
Ok, I managed to find link I used previously: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
I flashed the RUU and all seems to be working fine, booting is now taking 30sec to the set up screen. I now need to recover the apps and settings.
Any idea what caused this problem?
Thanks for all suggestions.
Click to expand...
Click to collapse
Like I've said, maybe a partition got corrupted and caused those problems or something inside might be slowly dying.
As long as it works it's okay I guess.

During set up phone did not asked to restore from GP backup. Is there any way to force this restore especially the home screen settings?
Sent from my HTC One_M8 using Tapatalk

HTC M8 stuck on HTC One logo boot

Hi, I'll keep this short and simple. The phone is locked, with S-ON and everything is stock, it's running Lollipop 5.0 with stock sense. I've had my M8 since Oct 2014, served me well until Dec 2017 when I switched to the HTC 10. At any rate, I've migrated the majority of my content to the new phone except for a few like telegram secret chat etc. Since I made the switch, I usually keep the M8 switched off and I used it like 4-5 times only since December. My last usage was around early March.
Anyway, come last week. I turned it on and it got stuck on the HTC logo (first time ever). So I booted into recovery which is when I noticed that the software status is now modified vs Official despite never tampering with it. I cleared the cache and attempted a reboot and it got stuck on the "HTC One" logo but that' about it. The only way out of this state is power button + vol up which reboots it again and on and on this goes. It just refuses to go past that stage. Occassionally "android is optimising apps" appears for like 2 sec before the htc One logo shows up again and remains there indefinitely.
Any idea on what I could do to make it startup? Preferably without factory resetting. Thank you
(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.13
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__J15
(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: f063fb42
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

So just an update, it seems that right now, my device goes straight into fastboot regardless if I choose power down (powering it on again boots it back into fastboot) or restart it (again goes into fastboot).

hemingway60 said:
Any idea on what I could do to make it startup? Preferably without factory resetting. Thank you
Click to expand...
Click to collapse
Probably unlikely to get the phone working and keep your data.
It appears your OS has become corrupted or damaged in some way (it happens). This would explain why it goes straight to bootloader instead of booting to OS. It may also explain why it says software "modified" when you haven't done any mods. Although I haven't seen that happen specifically (showing "modified" due to OS damage on an otherwise stock device); but it does seem logical it would say this (it is possibly reading the damage as some unknown "modification").
Your best bet is to restore factory image using RUU, following the instructions on the following post: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
RUU will wipe all data on the phone. But in the current condition (as mentioned), I don't think you have much choice anyway.
The RUU should restore the OS, in addition to updating it to Marshmallow (the last version HTC released for this device).

Hey, appreciate the reply. That's disappointing, considering the phone was literally just sitting inside a desk. Anyway, I recalled seeing this post : https://forum.xda-developers.com/showpost.php?p=64883695&postcount=6772 and noticed the OTA release code was 464427 vs 464360 on the RUU file. Is there any significance to this? Ironed bugs perhaps? If it's a better build, can I upgrade to that instead?
Thanks.

hemingway60 said:
I recalled seeing this post : https://forum.xda-developers.com/showpost.php?p=64883695&postcount=6772 and noticed the OTA release code was 464427 vs 464360 on the RUU file. Is there any significance to this? Ironed bugs perhaps? If it's a better build, can I upgrade to that instead?
Click to expand...
Click to collapse
Both are build number 6.12.401.4.
So I doubt there is any actual difference. If there was any change, it would have a different build number (6.12.401.5 or whatever).

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