Develop Bugs

[Q] HTC One m8 unrooting

hi everyone.. i recently bought a used htc m8 and it is already rooted and therefore i cannot get the OTA lollipop update..
it is running android revolution HD 8.1 and clockworkmod..
I have no idea about rooting and unrooting and what the names i just mentioned above mean.. someone please help me get back to stock firmware... or help me convert my phone into google play edition lollipop...
please tell the method by which i can get rid of clockwordmod permanently and get back to stock firmware..
thanks in advance

hassaan08 said:
hi everyone.. i recently bought a used htc m8 and it is already rooted and therefore i cannot get the OTA lollipop update..
it is running android revolution HD 8.1 and clockworkmod..
I have no idea about rooting and unrooting and what the names i just mentioned above mean.. someone please help me get back to stock firmware... or help me convert my phone into google play edition lollipop...
please tell the method by which i can get rid of clockwordmod permanently and get back to stock firmware..
thanks in advance
Click to expand...
Click to collapse
Click this link. It will tell you how to convert your phone to GPE.

xunholyx said:
Click this link. It will tell you how to convert your phone to GPE.
Click to expand...
Click to collapse
sure
just help me please.. i have been trying for days now and i havent been able to fix my phone... every method i try i get stuck at one point or another....

hassaan08 said:
sure
just help me please.. i have been trying for days now and i havent been able to fix my phone... every method i try i get stuck at one point or another....
Click to expand...
Click to collapse
Okay. The instructions are in the link. Where are you getting stuck?

Telling someone that has no idea what they're doing to convert the phone isn't very good advice.
OP - do you understand anything about rooting and the commands used to root your phone?

EddyOS said:
Telling someone that has no idea what they're doing to convert the phone isn't very good advice.
OP - do you understand anything about rooting and the commands used to root your phone?
Click to expand...
Click to collapse
yes i do.. i tried a few things but got stuck in between cos i dont know this stuff in depth..
I tried to unroot by downloading the stock firmware for my phone..
the method i was following was to match my cid number etc which i got through getvar with the firmwares on xda.. that bit i did well but the method i was following said that now i had to copy and paste this firmware in my phone in the backups folder of clockwordmod.. now i couldnt find that folder.. even though the backup i made is occupying space on my phone but i cannot locate it when i try to copy paste the downloaded firmware..
can you tell me where i can find that or tell an alternate way to do this thing?

OK, can you connect your phone when in the bootloader and then use the command fastboot getvar all to get information about your phone and post it up here (making sure you hide the IMEI and serial number, of course)

EddyOS said:
OK, can you connect your phone when in the bootloader and then use the command fastboot getvar all to get information about your phone and post it up here (making sure you hide the IMEI and serial number, of course)
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.15.2133156.UA13G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: HTC__002
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: ab0efa49
hbootpreupdate: 11
gencheckpt: 0
is this what you were asking for?

Indeed! OK, if you want go back to 100% stock, running on Sense as if you just got it out the box you can do the following:
First, download these files to the same location as fastboot:
4.16.401.10 RUU ZIP - https://drive.google.com/file/d/0B17smFr95pleU2NqcVB3NWxoNnM/view (rename it ruu.zip - not ruu.zip.zip!)
htc_fastboot - https://www.androidfilehost.com/?fid=95897840722646249 (doesn't need renaming)
1. Relock your bootloader - fastboot oem lock
2. Once done, reboot the bootloader to confirm it says 'RELOCKED' - fastboot reboot-bootloader
3. Once relocked, reboot the phone into RUU mode - fastboot oem rebootRUU
4. Once in RUU mode, flash the RUU ZIP using the HTC fastboot app - htc_fastboot flash zip ruu.zip
5. It will go through a few passes but once complete reboot the phone to the bootloader - fastboot reboot-bootloader
6. Once back at the bootloader, go into recovery and you should get the stock recovery not CWM. Hold volume up and press power to get the recovery menu and do a factory reset
7. Once the reset has finished, reboot the phone
You should now be working again on 100% stock Lollipop

help needed, new to rooting stuff
Hi forum members. This is my first post and and i am an infant in unlocking and rooting stuff. The reason I am researching these things is because of my HTC one m8. I got this phone used from a seller 6 months ago. I was expecting OTA updates but did not receive any till date. I am still running on 4.4.2 . So, after a bit of searching on forums, I learned about a thing called boot loader. And checked mine. To my surprise it was TAMPERED , UNLOCKED AND S-ON. Now I really don't know what that means. Some suggested to check if it's rooted, installed root checker and it said "device is not rooted" .
Can anyone pLease help me And explain me what all this means as it will be greatly appreciated.I only want to have OTA updates And need stock android. Thanks in advance

Best to start your own thread, and post up the same details as the OP in post #8, rather than confusing things in someone else's thread

EddyOS said:
Telling someone that has no idea what they're doing to convert the phone isn't very good advice.
OP - do you understand anything about rooting and the commands used to root your phone?
Click to expand...
Click to collapse
Read his OP. He asked how to convert, so I linked him. How is that bad advice?
Sorry for being off topic.

xunholyx said:
Read his OP. He asked how to convert, so I linked him. How is that bad advice?
Sorry for being off topic.
Click to expand...
Click to collapse
That was the second request, the first being to get it back to stock. I was just saying that if they're not familiar with rooting HTC devices then converting to GPe could potentially brick the device

It worked... thank you so much..
i hope liverpool get into the top 4 this season

hassaan08 said:
It worked... thank you so much..
i hope liverpool get into the top 4 this season
Click to expand...
Click to collapse
I'm an Arsenal fan but thank you anyway!

hey again
i unrooted my device and it seemed fine then but since day one the device is highly unstable.. I did the hard reset several times but have not been able to fix the problem.. suddenly all the data vanishes from the device and some features get locked ( brightness, power saver and others too). Please suggest what i should do?

Is there a way I can re-flash the stock lollipop with a different RUU file?

Nope, if you still have issues when stock you have a faulty phone

these are definitely sofware issues.. for example one in ten times when i format my device it starts working totally fine... but after a few days the same problem re-appears... the problem is that htc zoe add keeps popping up again and again.. and when it starts i cant adjust the brightness or the power saver options.. the rest of the phone works fine....
can you please suggest if i should convert my phone to GPE? or will it be too difficult a process for a rookie like me?

Sounds like a faulty phone, get it replaced

[Q] Returning to stock, international M8

I unlocked the bootloader (offical version, S-ON) and flashed Dirty Unicorns Marshmallow ROM. The battery life is plain horrible, but I'm not sure if that's because of the ROM or the phone. Now I want to flash it back to stock, mainly because my M8 shut itself off twice yesterday when I used GPS due to overheating (had to hold it near AC in the car so it wouldn't shut down again).
I read a lot of guides, but I'm really confused because HTC complicated it so much (I'm not inexperienced in flashing, had two Sony devices and a Xiaomi). Can anyone help me out?
Sent from my One M8

sunbriel said:
I unlocked the bootloader (offical version, S-ON) and flashed Dirty Unicorns Marshmallow ROM. The battery life is plain horrible, but I'm not sure if that's because of the ROM or the phone. Now I want to flash it back to stock, mainly because my M8 shut itself off twice yesterday when I used GPS due to overheating (had to hold it near AC in the car so it wouldn't shut down again).
I read a lot of guides, but I'm really confused because HTC complicated it so much (I'm not inexperienced in flashing, had two Sony devices and a Xiaomi). Can anyone help me out?
Sent from my One M8
Click to expand...
Click to collapse
What does it say next to "OS" in your bootloader menu?

xunholyx said:
What does it say next to "OS" in your bootloader menu?
Click to expand...
Click to collapse
"OS-" so basically nothing.
Sent from my One M8

sunbriel said:
"OS-" so basically nothing.
Sent from my One M8
Click to expand...
Click to collapse
That's because you are using an old version of TWRP (2.7.x.x) that had a bug that the firmware version wouldn't be listed.
Hook up your phone to your PC and get into fastboot. Enter fastboot getvar all and post the readout here, minus your serial# and IMEI

xunholyx said:
That's because you are using an old version of TWRP (2.7.x.x) that had a bug that the firmware version wouldn't be listed.
Hook up your phone to your PC and get into fastboot. Enter fastboot getvar all and post the readout here, minus your serial# and IMEI
Click to expand...
Click to collapse
Code:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.29.214500021.1
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: HTC__032
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 76df2b54
hbootpreupdate: 11
gencheckpt: 0

First of all, update to the current TWRP version 3.0. As @xunholyx indicated, the OS number being blank means you used a really old TWRP version, which can cause a lot of issues. Then flash the ROM again (after default wipe in TWRP - data, cache and Dalvik) and see if that helps.
Or try another ROM.
If you still want to return to stock, you can get the TWRP stock backup here: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
What you want is 6.12.401.4
Although, standard operating procedure for any ROM flashing would have dictated that you made a nandroid (TWRP backup) of the stock ROM before flashing anything. If you had done so, you could have simply restore that backup to return to the stock ROM.

Thanks for the help.
Well, I didn't create a nandroid backup of stock ROM since I thought that going back to factory settings was as easy as with Sony or Xiaomi devices. This HTC stuff is way too messed up, and I don't understand why they made it that way. I didn't expect that, tbh.
Edit: just checked, the TWRP version I have is 3.0.2-0.

sunbriel said:
Thanks for the help.
Well, I didn't create a nandroid backup of stock ROM since I thought that going back to factory settings was as easy as with Sony or Xiaomi devices. This HTC stuff is way too messed up, and I don't understand why they made it that way. I didn't expect that, tbh.
Edit: just checked, the TWRP version I have is 3.0.2-0.
Click to expand...
Click to collapse
Your OS/version-main will remain blank until you flash firmware. Just flashing the newer recovery on its own won't do that

sunbriel said:
Well, I didn't create a nandroid backup of stock ROM since I thought that going back to factory settings was as easy as with Sony or Xiaomi devices. This HTC stuff is way too messed up, and I don't understand why they made it that way. I didn't expect that, tbh.
Click to expand...
Click to collapse
You should never assume anything is the same between Android manufacturers; they each have their own quirks. And you should always make a backup before flashing a ROM, root, or other mods.; doesn't matter what the manufacturer.
Returning to stock by flashing a stock TWRP backup is not complicated. Since you've already achieved unlocking the bootloader, flashing custom recovery, and custom ROM; you can certainly handle restoring to stock with a TWRP backup. You basically just download the backup file, unzip the folders, put the folders in the proper place on the phone, then Restore the backup in TWRP. The instructions in the thread I link just break it down into steps, for you convenience. But it all just boils down to getting the backup on the phone (since you didn't make one yourself) and restoring it. I even figured out what version number you needed, and told you. So how much easier do you want it?
Your version also has an RUU (HTC specific restore tool), which will return you to stock after relocking the bootloader. But to be honest, its not that complicated to restore the TWRP backup as already suggested.

I already restored everything to stock and sold the phone. The battery life was horrible even on stock (mostly below 3h SOT with very light usage).
You say I should always make a nandroid. That's true, but for instance with Sony, even if you soft brick your phone, you just downlpad a ftf file and flash it with Flashtool. Also, another reason why I didn't make a nandroid backup of stock is because I didn't have anything worth backing up - it was pure stock without any of my apps installed since the phone was freshly bought off craigslist.
Sent from my X98 Air II using Tapatalk

sunbriel said:
You say I should always make a nandroid. That's true, but for instance with Sony, even if you soft brick your phone, you just downlpad a ftf file and flash it with Flashtool. Also, another reason why I didn't make a nandroid backup of stock is because I didn't have anything worth backing up - it was pure stock without any of my apps installed since the phone was freshly bought off craigslist.
Click to expand...
Click to collapse
The point of making a nandroid prior to any mods is to backup the stock ROM, not just your personal data.
Always know how to revert to stock, before you start messing with the phone. And how to do that varies with each device. That's all I'm saying.

Bounty/Donation

If anyone can solve my problem, I've got a donation coming your way. I've got a Verizon HTC One M8 and cannot run GPE or AOSP based Roms without having intermittent cellular connectivity issues. Phone works fine on sense based though. I've tried all of the obvious things like RUU and factory reset from both bootloader as well as stock recovery. I also tried new sim cards too. If anyone has new ideas I'm all ears!
Sent from my HTC6525LVW using XDA-Developers mobile app

Is your firmware up to date?
If you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).

These issues have been posted a ton by users on AOSP based firmware. Not sure about GPE as I've never personally used it on this device. But it's just something that will eventually be fixed upstream.

redpoint73 said:
Is your firmware up to date?
If you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
Yes, FW is vzw up to date. I'll get other info too.
Sent from my HTC6525LVW using XDA-Developers mobile app

SeanHacker said:
These issues have been posted a ton by users on AOSP based firmware. Not sure about GPE as I've never personally used it on this device. But it's just something that will eventually be fixed upstream.
Click to expand...
Click to collapse
I'm on Sense firmware. It's there Roms, not the FW that I'm having issues with.
Sent from my HTC6525LVW using XDA-Developers mobile app

Dan Tekle said:
I'm on Sense firmware. It's there Roms, not the FW that I'm having issues with.
Click to expand...
Click to collapse
I think in this case, SeanHacker was (confusingly) using the term "firmware" to be synonymous with ROM. There is not such thing as AOSP firmware (such as firmware.zip with hboot, radio, etc.) in the sense you are I are talking about firmware.
I think he basically means its a ROM issue, that will hopefully be fixed.

redpoint73 said:
I think in this case, SeanHacker was (confusingly) using the term "firmware" to be synonymous with ROM. There is not such thing as AOSP firmware (such as firmware.zip with hboot, radio, etc.) in the sense you are I are talking about firmware.
I think he basically means its a ROM issue, that will hopefully be fixed.
Click to expand...
Click to collapse
Yea, I figured. However I'm in the very small minority (I think) with these issues. Others using cm13 and GPE roms don't have them.
Sent from my HTC6525LVW using XDA-Developers mobile app

redpoint73 said:
I think in this case, SeanHacker was (confusingly) using the term "firmware" to be synonymous with ROM. There is not such thing as AOSP firmware (such as firmware.zip with hboot, radio, etc.) in the sense you are I are talking about firmware.
I think he basically means its a ROM issue, that will hopefully be fixed.
Click to expand...
Click to collapse
Yeah. Not sure why I said firmware. I meant ROM. ?

Dan Tekle said:
I'm on Sense firmware. It's there Roms, not the FW that I'm having issues with.
Sent from my HTC6525LVW using XDA-Developers mobile app
Click to expand...
Click to collapse
Dan Tekle said:
Yea, I figured. However I'm in the very small minority (I think) with these issues. Others using cm13 and GPE roms don't have them.
Sent from my HTC6525LVW using XDA-Developers mobile app
Click to expand...
Click to collapse
Yep. I meant ROM. Not firmware issue. You're definitely not in a small minority. I have seen tons of posts on twitter, g+, XDA, ect with the same issues. I see the issue every day as I only use AOSP. I've been working on the issue myself trying to resolve the problem.

Dan Tekle said:
I'm on Sense firmware. It's there Roms, not the FW that I'm having issues with.
Sent from my HTC6525LVW using XDA-Developers mobile app
Click to expand...
Click to collapse
Of course you have Sense firmware. You have a Verizon M8 and can't have GSM.
Have you tried to flash back to stock to see if the problem persists? I'm not sure if there is a Verizon RUU available (there probably is), but running an RUU should fix everything.
If you do a restore after, and you get problems again, then you'll have to suss out the source to get it fixed.

xunholyx said:
Of course you have Sense firmware. You have a Verizon M8 and can't have GSM.
Have you tried to flash back to stock to see if the problem persists? I'm not sure if there is a Verizon RUU available (there probably is), but running an RUU should fix everything.
If you do a restore after, and you get problems again, then you'll have to suss out the source to get it fixed.
Click to expand...
Click to collapse
Already done several RUU's and and I was trying to help the previous person understand that the problem wasn't likely my firmware. If you have something to add that might shed some light or might help, lmk.
Sent from my HTC6525LVW using XDA-Developers mobile app

$25 bucks to anyone who figures it out.
Sent from my HTC6525LVW using XDA-Developers mobile app

Dan Tekle said:
Already done several RUU's and and I was trying to help the previous person understand that the problem wasn't likely my firmware. If you have something to add that might shed some light or might help, lmk.
Click to expand...
Click to collapse
I don't know what "several RUUs" means (be specific and list the file names), but if its non-VZN RUUs, they won't work and its a really bad idea, as they may even radio brick the phone.
Do fastboot getvar all, and post the results so I can see more info about the phone (delete IMEI and serial number before posting).

SeanHacker said:
Yeah. Not sure why I said firmware. I meant ROM. ?
Click to expand...
Click to collapse
No worries...

redpoint73 said:
I don't know what "several RUUs" means (be specific and list the file names), but if its non-VZN RUUs, they won't work and its a really bad idea, as they may even radio brick the phone.
Do fastboot getvar all, and post the results so I can see more info about the phone (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
Alright, here you go! And TIA if you figure this one out . As far as the RUU (Rom Update Utility) I use @dottat's VZWM8_S_OFF_SF_6.0_RUU.zip (File Name).
Please let me know if you need anything else.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.14.20.0930
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 99000429334796
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: VZW__001
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.266s

Dan Tekle said:
As far as the RUU (Rom Update Utility) I use dottat's VZWM8_S_OFF_SF_6.0_RUU.zip (File Name).
Click to expand...
Click to collapse
If you ran the RUU, and it installed fully and successfully, but you get the same result on AOSP ROMs; I would have to think its a ROM issue, as SeanHacker has already stated.

redpoint73 said:
If you ran the RUU, and it installed fully and successfully, but you get the same result on AOSP ROMs; I would have to think its a ROM issue, as SeanHacker has already stated.
Click to expand...
Click to collapse
So nothing out of place in the getvar? And yes no issues with RUU. However it's not just AOSP Roms, its also GPE which makes me think it's a device config issue. I'm stumped and frustrated[emoji16]
Sent from my HTC One_M8 using XDA-Developers mobile app

Dan Tekle said:
So nothing out of place in the getvar? And yes no issues with RUU. However it's not just AOSP Roms, its also GPE which makes me think it's a device config issue. I'm stumped and frustrated[emoji16]
Click to expand...
Click to collapse
Getvar looks okay, except that the OS number is missing. RUU should have normally have fixed that, but I'm not 100% on how the s-off RUU works.
The VZN and Sprint versions (CDMA versions) of the M8 have different kernels and different firmware. I've seen some folks with the CDMA versions have to play around with one thing or another to get the network to work correctly, even on Sense ROMs.

redpoint73 said:
Getvar looks okay, except that the OS number is missing. RUU should have normally have fixed that, but I'm not 100% on how the s-off RUU works.
The VZN and Sprint versions (CDMA versions) of the M8 have different kernels and different firmware. I've seen some folks with the CDMA versions have to play around with one thing or another to get the network to work correctly, even on Sense ROMs.
Click to expand...
Click to collapse
Yea I'm familiar with those issues and I've been able to fix initial problem on sense based Roms but never had anything work and stick on GPE or AOSP. The OS version normally shows with the RUU installed but goes blank after a custom ROM is loaded. I'm on the most recent OS though.
Sent from my HTC One_M8 using XDA-Developers mobile app

Dan Tekle said:
The OS version normally shows with the RUU installed but goes blank after a custom ROM is loaded. I'm on the most recent OS though.
Click to expand...
Click to collapse
The bug of OS being blank is usually due to an old version TWRP. Advise to use TWRP 3.0.2

No SIM Detected Suddenly

I know this is a common issue for the HTC One M8, but my phone stopped recognising any SIM card all of a sudden. It happened right after the battery got discharged fully (sudden power off), though I'm not ruling out the possibility that recent drops might have contributed to this.
I already tried the scotch tape solution to no avail as well as wiping cache and dalvik and rebooting a bunch of times with, without, and with other SIM cards in.
I'm running this Google Play Edition flashable ROM with the corresponding firmware, unrooted and s-on.
Should I go straight to re-flashing the same firmware and ROM? Is there anything I could attempt before having everything wiped?
One weird note that I've also noticed in another post: if I go to "phone info" the IMEI and phone number show as "unknown", but I can see them with fastboot getvar all. Also in "phone info", the "TURN OFF RADIO" button doesn't seem to be doing anything when pressed. Any alternative way to do it?
Thank you! :fingers-crossed:

AlexanderGrey said:
I'm running this Google Play Edition flashable ROM with the corresponding firmware, unrooted and s-on.
Should I go straight to re-flashing the same firmware and ROM? Is there anything I could attempt before having everything wiped?
Click to expand...
Click to collapse
The RUU provided in the GPE thread you linked, would be my suggestion. Should be same (or similar) to flashing the ROM and firmware. But with the RUU, you are sure to have all partitions (around 40) returned to "factory stock" (at least for GPE version) condition.
You might also try another RUU (return to Sense) or another ROM. But in any case, you should backup your data and prepared to fully wipe. Trying to migrate data across ROMs is only going to complicate matters, and you will never be sure that the SIM issue is due to the some incompatibility with your existing user data.

redpoint73 said:
The RUU provided in the GPE thread you linked, would be my suggestion. Should be same (or similar) to flashing the ROM and firmware. But with the RUU, you are sure to have all partitions (around 40) returned to "factory stock" (at least for GPE version) condition.
You might also try another RUU (return to Sense) or another ROM. But in any case, you should backup your data and prepared to fully wipe. Trying to migrate data across ROMs is only going to complicate matters, and you will never be sure that the SIM issue is due to the some incompatibility with your existing user data.
Click to expand...
Click to collapse
Thanks for the quick reply.
I haven't gone the GPe RUU route as that would require s-off, which I'm not planning to get. I forgot to mention I've been using this ROM & firmware for over 2 months without any issues.
I'm not very familiar with the topic of backup - although I've flashed ROMs in the past I've always done a clean install. Could you please elaborate? Would I be able to save installed apps with a backup via TWRP? Or would you advise against that?

AlexanderGrey said:
I haven't gone the GPe RUU route as that would require s-off, which I'm not planning to get. I forgot to mention I've been using this ROM & firmware for over 2 months without any issues.
Click to expand...
Click to collapse
You wouldn't have been able to flash the GPE firmware s-on, unless it is a signed zip and you have an actual GPE version M8 (correct CID and MID). The requirements for flashing the firmware are same as the RUU.
Please do fastboot getvar all, and post the results (delete IMEI and serial number before posting) so we can see more info about the device.
AlexanderGrey said:
I'm not very familiar with the topic of backup - although I've flashed ROMs in the past I've always done a clean install. Could you please elaborate? Would I be able to save installed apps with a backup via TWRP? Or would you advise against that?
Click to expand...
Click to collapse
There are lots of ways to backup data, each with their pros and cons. So how you do it is up to you.
A TWRP backup of app data is only going to work if you are just restoring the same ROM. So if you are flashing the RUU/ROM same as you have now, then it will work.
But if you try another ROM, it's usually not a good idea to try to "migrate" app data using TWRP. Different ROMs store their app data in different ways, and trying to migrate the data across different ROMs via TWRP backup is asking for trouble. In those cases, I use Titanium Backup for apps and app data (requires root). There are other options, but Titanium is tried and true (for most) and it is what I personally use.
Other data, like photos, videos you took, and any other media you want to keep (music, ringtones, porn) you can just copy to a computer, SD card, cloud solutions etc. Again, there are lots of options.

redpoint73 said:
You wouldn't have been able to flash the GPE firmware s-on, unless it is a signed zip and you have an actual GPE version M8 (correct CID and MID). The requirements for flashing the firmware are same as the RUU.
Please do fastboot getvar all, and post the results (delete IMEI and serial number before posting) so we can see more info about the device.
There are lots of ways to backup data, each with their pros and cons. So how you do it is up to you.
A TWRP backup of app data is only going to work if you are just restoring the same ROM. So if you are flashing the RUU/ROM same as you have now, then it will work.
But if you try another ROM, it's usually not a good idea to try to "migrate" app data using TWRP. Different ROMs store their app data in different ways, and trying to migrate the data across different ROMs via TWRP backup is asking for trouble. In those cases, I use Titanium Backup for apps and app data (requires root). There are other options, but Titanium is tried and true (for most) and it is what I personally use.
Other data, like photos, videos you took, and any other media you want to keep (music, ringtones, porn) you can just copy to a computer, SD card, cloud solutions etc. Again, there are lots of options.
Click to expand...
Click to collapse
Thanks for the info on backing up, I should have been more specific though. I've used Titanium Backup in the past a little bit, but recently I've opted to keep my phone unrooted mostly for some banking apps I use. Backing up with TWRP sounds good to me as I'd like to keep the same ROM (ideally) and would not want to go through reinstalling everything.
My phone is not a GPE version however the ROM I currently use is compatible with all M8 versions (except dual-sim) and with s-on. Here's the info:
(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__002
(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

AlexanderGrey said:
My phone is not a GPE version however the ROM I currently use is compatible with all M8 versions (except dual-sim) and with s-on. Here's the info:
(bootloader) version-main: 6.12.401.4
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__002
Click to expand...
Click to collapse
The GPE firmware never flashed (maybe you flashed it, and it failed to install). Otherwise, the version-main number would have changed to a GPE version number (5.07.1700.15 as noted in the firmwares you linked). And as mentioned, it isn't possible to flash GPE firmware while s-on (firmware for a different CID, MID).
Now, none of this explains your SIM issue. Maybe start by simply "dirty" flashing the GPE ROM (keep user data, just wipe cache and Dalvik) and see if there is any change.

redpoint73 said:
The GPE firmware never flashed (maybe you flashed it, and it failed to install). Otherwise, the version-main number would have changed to a GPE version number (5.07.1700.15 as noted in the firmwares you linked). And as mentioned, it isn't possible to flash GPE firmware while s-on (firmware for a different CID, MID).
Now, none of this explains your SIM issue. Maybe start by simply "dirty" flashing the GPE ROM (keep user data, just wipe cache and Dalvik) and see if there is any change.
Click to expand...
Click to collapse
Hmm you're right, my memory is playing tricks on me. I remember flashing a new firmware however, because I was having issues with the wi-fi and bluetooth before it. After some searching I think I used this one, am I right?
I'll try a quick firmware flash as you indicated, and will get back with the results a bit later. Thanks!

AlexanderGrey said:
Hmm you're right, my memory is playing tricks on me. I remember flashing a new firmware however, because I was having issues with the wi-fi and bluetooth before it. After some searching I think I used this one, am I right?
Click to expand...
Click to collapse
That would be my guess, yes.
AlexanderGrey said:
I'll try a quick firmware flash as you indicated, and will get back with the results a bit later. Thanks!
Click to expand...
Click to collapse
Flashing firmware requires you to relock the bootloader (since you are s-on) which will wipe your data.
As I mentioned in my last response, you might try to just "dirty flash" the GPE ROM (keep the current firmware) just to see what happens, before taking any measure which cause your data to be wiped.
I would still recommend to backup your data before even a dirty flash - you can't be too safe!

AlexanderGrey said:
Hmm you're right, my memory is playing tricks on me. I remember flashing a new firmware however, because I was having issues with the wi-fi and bluetooth before it. After some searching I think I used this one, am I right?
I'll try a quick firmware flash as you indicated, and will get back with the results a bit later. Thanks!
Click to expand...
Click to collapse
Unfortunately, no visible change . Still no SIM detected.

redpoint73 said:
That would be my guess, yes.
Flashing firmware requires you to relock the bootloader (since you are s-on) which will wipe your data.
As I mentioned in my last response, you might try to just "dirty flash" the GPE ROM (keep the current firmware) just to see what happens, before taking any measure which cause your data to be wiped.
I would still recommend to backup your data before even a dirty flash - you can't be too safe!
Click to expand...
Click to collapse
Sorry, I meant re-flashing the ROM. That's what I did so far.

AlexanderGrey said:
Sorry, I meant re-flashing the ROM. That's what I did so far.
Click to expand...
Click to collapse
You may consider flashing the Euro RUU 6.12.401.4 form here: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
This will put your phone on a fully stock software/firmware "baseline" (for your phone's original configuration). If the SIM problem persists after that, I would have to think it was a hardware issue.
RUU as you know, will wipe the phone. So backup your data accordingly, before relocking the bootloader and running the RUU.

redpoint73 said:
You may consider flashing the Euro RUU 6.12.401.4 form here: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
This will put your phone on a fully stock software/firmware "baseline" (for your phone's original configuration). If the SIM problem persists after that, I would have to think it was a hardware issue.
RUU as you know, will wipe the phone. So backup your data accordingly, before relocking the bootloader and running the RUU.
Click to expand...
Click to collapse
Thanks redpoint, that's the same one I have installed currently, right?
I guess ultimately I'll have to bite the bullet and try it if I want to figure out if it's a software or hardware issue.

AlexanderGrey said:
Thanks redpoint, that's the same one I have installed currently, right?
Click to expand...
Click to collapse
Same version number as the currently installed firmware. But what you flashed before is just firmware (about 80 MB) which includes hboot, radio, recovery, boot.img, and several others (maybe about 10 partitions?). The RUU (about 1.5 GB) will restore a complete factory image (every partition - about 40 of them).

redpoint73 said:
Same version number as the currently installed firmware. But what you flashed before is just firmware (about 80 MB) which includes hboot, radio, recovery, boot.img, and several others (maybe about 10 partitions?). The RUU (about 1.5 GB) will restore a complete factory image (every partition - about 40 of them).
Click to expand...
Click to collapse
Ah I understand now, I was not aware of that previously.
I was also planning to replace my battery so I might just do that first and have a look if anything looks unusual around the SIM card tray.
Thanks for all the help, I'll come back with a conclusion after a day or two when I get the chance .

redpoint73 said:
Same version number as the currently installed firmware. But what you flashed before is just firmware (about 80 MB) which includes hboot, radio, recovery, boot.img, and several others (maybe about 10 partitions?). The RUU (about 1.5 GB) will restore a complete factory image (every partition - about 40 of them).
Click to expand...
Click to collapse
Update: after replacing the battery I flashed the RUU and the same ROM back on.
Good news is the SIM card works now . I'm just a bit concerned about this happening again. Since you've seen quite a few cases on this forum I wanted to ask: do you think this is a common issue with that particular ROM?
I searched for SIM card issues in the thread of that ROM but the only legit ones I saw were the cases where people only installed the ROM without updating the firmware (so their wifi and bluetooth was not working either).
Cheers.

AlexanderGrey said:
Good news is the SIM card works now . I'm just a bit concerned about this happening again. Since you've seen quite a few cases on this forum I wanted to ask: do you think this is a common issue with that particular ROM?
Click to expand...
Click to collapse
Nothing that I am aware of. Running GPE ROM with Sense firmware might not be ideal. But I don't recall seeing any similar cases (no SIM).

HTC One M8 stuck at HTC logo screen

Hi,
First of all, this was supposed to be my first flash. So I am very new and confused. (I get that you probably have loads of those... I am sorry)
I got a HTC One M8 that was already rooted and S-OFF, had SuperCID and everything. And I hate the 4.4.4 Android, plus no OTA updates are available to me (when I tried to check, it gets stuck). So I wanted to flash in a LineageOS 16.0. I unlocked the bootloader, got TWRP 2.8.7.0, pasted the Lineage 16.0 ZIP file, and wanted to flash it. But, I got an error "Error executing updater binary in zip [zip filename]", and so I went to check the instructions to install.
https://forum.xda-developers.com/htc-one-m8/development/rom-lineageos-16-0-htc-one-m8-t3837538
Here it says this:
- Reboot to recovery (TWRP by @Captain_Throwback) - Direct link
- Wipe /system, /data and /cache
- Install LineageOS zip package
and I did that to see if it changes anything, Nope, it didn't. I tried to reboot the phone to get it fixed (someone in another thread suggested getting an md5 file for it).
And after the reboot I am stuck on HTC logo screen, can't shut it down at all. I can't use ADB because it doesn't see the device, so I can't getvar all. I do remember that my version-bootloader was 3.19.0.0000, but that's all.
I am not asking for a full guide on what to do, because it's probably impossible, but can anyone at least tell me how to proceed next? I'd love to turn off the phone and at least try to do something with TWRP. (I didn't have a backup, yes I am an idiot)
EDIT: Holding volume up and power button to do the reset just turns off the screen for a few secs then goes to HTC logo screen again.

Okay, I waited for it to discharge so I can get to the bootloader. I will post getvar when it charges.
EDIT: here we go
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.08.20.0916
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.30.651.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) imei2: Not Support
(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
I basically just want anything to work now, even stock will be okay (but 6.0 at least)

1st edit your last post & remove your IMEI/MEID unless you want it stolen...
when you wiped /system in TWRP & your zip didn't flash, u lost your ROM
easiest way to get the phone back up & working is to flash the RUU, looks like you currently have 3.30.651.2 (very old)
here is the 3.30.651.2 exe version: https://androidfilehost.com/?fid=95784891001604379
or to update to the latest version 6.20.651.3:
http://dl3.htc.com/application/RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3.exe

OMJ said:
1st edit your last post & remove your IMEI/MEID unless you want it stolen...
Click to expand...
Click to collapse
Yeah, I forgot, thanks for reminding.
So do I just run the .exe with my phone plugged in my PC while in bootloader? Or do you mean TWRP/adb flashing?

gr0za said:
Yeah, I forgot, thanks for reminding.
So do I just run the .exe with my phone plugged in my PC while in bootloader? Or do you mean TWRP/adb flashing?
Click to expand...
Click to collapse
yes, run exe from pc while connected to phone

OMJ said:
yes, run exe from pc while connected to phone
Click to expand...
Click to collapse
3.30.651.2 worked, 6.20.651.3 did not ( I tried it first). To be honest I'm so damn glad it works, because I ain't a Sprint user, but somehow Orange works. Got all the bloaty Google Aps that I don't give an f about, but at least it's working. Hopefully I can go to 6.20 next, I'm gonna try. BTW, will flashing GApps remove all the unnecessary Sprint apps? Or do I have to do something different with it? (I don't need neither the GApps not the Sprint apps, but this phone seems to be a Sprint one and I guess I have to deal with it)
EDIT: yeah, 6.20 doesn't work, it gives me Error 155 - Error updating ROM. I remember hitting up HTC live support once in desperation, and the guy told me I have to upgrade to Lollipop first. But where do I even find a RUU for that?

gr0za said:
3.30.651.2 worked, 6.20.651.3 did not ( I tried it first). To be honest I'm so damn glad it works, because I ain't a Sprint user, but somehow Orange works. Got all the bloaty Google Aps that I don't give an f about, but at least it's working. Hopefully I can go to 6.20 next, I'm gonna try. BTW, will flashing GApps remove all the unnecessary Sprint apps? Or do I have to do something different with it? (I don't need neither the GApps not the Sprint apps, but this phone seems to be a Sprint one and I guess I have to deal with it)
EDIT: yeah, 6.20 doesn't work, it gives me Error 155 - Error updating ROM. I remember hitting up HTC live support once in desperation, and the guy told me I have to upgrade to Lollipop first. But where do I even find a RUU for that?
Click to expand...
Click to collapse
yeah I vaguely recall the RUU checks your current version & must be a certain level, so you'll probably need to flash a 4.x.651.x RUU 1st
GApps probably only adds Google apps, I doubt it removes anything. once you get up to 6.20, you can root the phone (I recommend Magisk) then use a file explorer like Root Explorer to mount /system & then delete the bloat u dont want. You can also do this in twrp.
the other option is to flash a custom ROM that removes the bloat....my ROM removes bloat but retains pertinent Sprint apps

OMJ said:
yeah I vaguely recall the RUU checks your current version & must be a certain level, so you'll probably need to flash a 4.x.651.x RUU 1st
GApps probably only adds Google apps, I doubt it removes anything. once you get up to 6.20, you can root the phone (I recommend Magisk) then use a file explorer like Root Explorer to mount /system & then delete the bloat u dont want. You can also do this in twrp.
the other option is to flash a custom ROM that removes the bloat....my ROM removes bloat but retains pertinent Sprint apps
Click to expand...
Click to collapse
Alright, once I flashed the Sprint RUU, all of a sudden I have OTA updates. I'm getting to 6.20 now, so everything's fine.
Yeah, I will consider removing them the way you said. Also, I don't really need any Sprint apps, as I am not a Sprint client anyway, but I reckon some are better left unchecked. Much, much appreciated for the help and the links.

gr0za said:
(bootloader) version-main: 3.30.651.2
Click to expand...
Click to collapse
This was the main problem with flashing Lineage, your firmware (hboot, radio, etc.) was much too old. The current ROMs are not compatible with the old firmware. Now that you're updated to Marshmallow, I'll bet Lineage will install correctly (of course, you need to install TWRP again, etc.).
---------- Post added at 01:01 PM ---------- Previous post was at 12:59 PM ----------
gr0za said:
Holding volume up and power button to do the reset just turns off the screen for a few secs then goes to HTC logo screen again.
Click to expand...
Click to collapse
Hold vol up and power button to force a reboot. The moment the screen goes dark, signaling it is about to reboot, slide your finger from vol up, to vol down, and don't let go. This should get you into bootloader.
As long as the screen comes on, you can get into bootloader. Exception is, if your vol rocker is broken!
---------- Post added at 01:04 PM ---------- Previous post was at 01:01 PM ----------
OMJ said:
yeah I vaguely recall the RUU checks your current version & must be a certain level, so you'll probably need to flash a 4.x.651.x RUU 1st
Click to expand...
Click to collapse
Version check is okay if the RUU is same or greater version number (and skipping versions is usually okay). You can't go backwards (downgrade), is all.
There was a peculiar requirement on Marshmallow RUUs for US carrier versions of the M8. It is required to flash the appropriate Marshmallow firmware by fastboot, before the RUU would work, if coming from Lollipop or lower.

redpoint73 said:
This was the main problem with flashing Lineage, your firmware (hboot, radio, etc.) was much too old. The current ROMs are not compatible with the old firmware. Now that you're updated to Marshmallow, I'll bet Lineage will install correctly (of course, you need to install TWRP again, etc.)
Click to expand...
Click to collapse
Are you sure of this? I have a Sprint variant. And I found conflicting info whether Lineage works on Sprint or doesn't work.

gr0za said:
Are you sure of this? I have a Sprint variant. And I found conflicting info whether Lineage works on Sprint or doesn't work.
Click to expand...
Click to collapse
Not 100%, as I don't personally own the Sprint version M8. But what I can say:
1) The Lineage 16 thread says: "Builds are compatible with all M8 single SIM variants (m8ul, m8vzw and m8spr)."
Now the identifier "m8spr" isn't a correct one I've ever seen attached to the M8. But I think they mean the Sprint variant. Correct product ID would be M8_whl.
2) Instance of custom ROMs not working on M8 CDMA variants (Sprint and Verizon) are mainly due to the fact that those variants use a different Sense kernel. So mostly only applied to Sense ROMs. AOSP ROMs (in particular Lineage) which use their own kernel, work okay with the CDMA variants, far as I've seen.
3) Your firmware is so out to day, it will not work with any of the current ROMs. And when I say current, I mean any from the past several years. You should definitely update the firmware in any case, as it will cause lots of problems with custom ROMs, and no good reason to stay on the old firmware. Once firmware is updated, it is not hard to flash TWRP and try Lineage again. I think it will work, and there is certainly no harm in trying, even if it doesn't. The worst case scenario is that you flash a more updated (Marshmallow) version of the stock Sprint ROM. Which is still better than where you started with all this.

redpoint73 said:
2) Instance of custom ROMs not working on M8 CDMA variants (Sprint and Verizon) are mainly due to the fact that those variants use a different Sense kernel. So mostly only applied to Sense ROMs. AOSP ROMs (in particular Lineage) which use their own kernel, work okay with the CDMA variants, far as I've seen.
3) Your firmware is so out to day, it will not work with any of the current ROMs. And when I say current, I mean any from the past several years. You should definitely update the firmware in any case, as it will cause lots of problems with custom ROMs, and no good reason to stay on the old firmware. Once firmware is updated, it is not hard to flash TWRP and try Lineage again. I think it will work, and there is certainly no harm in trying, even if it doesn't. The worst case scenario is that you flash a more updated (Marshmallow) version of the stock Sprint ROM. Which is still better than where you started with all this.
Click to expand...
Click to collapse
I updated the firmware. I now have this:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-main: 6.20.651.3
But the SIM doesn't work with Lineage anyway, just flashed in anew and tried. The old Sprint 6.0 ROM that I RUU'd has the same issue. Could it be the radio version, or the firmware? Because it used to work, with some troubles, but still.

gr0za said:
Could it be the radio version, or the firmware? Because it used to work, with some troubles, but still.
Click to expand...
Click to collapse
The radio is part of the firmware. Not sure why your SIM would have troubles with the newer radio (if that is the case).
You can try this: https://forum.xda-developers.com/htc-one-m8/general/how-to-convert-cdma-m8-sprint-vzw-gsm-t3303812
Or you can try flashing back to RUU 3.30.651.2 and see if there is any change.

redpoint73 said:
The radio is part of the firmware. Not sure why your SIM would have troubles with the newer radio (if that is the case).
You can try this: https://forum.xda-developers.com/htc-one-m8/general/how-to-convert-cdma-m8-sprint-vzw-gsm-t3303812
Or you can try flashing back to RUU 3.30.651.2 and see if there is any change.
Click to expand...
Click to collapse
Omg, how come I didn't see this thread. Thanks so much, I will try once I get back home.
I hope this thread isn't problematic, because I moved the goalpost since creating it. But I'd rather not create a thread every time I have a problem...

gr0za said:
I hope this thread isn't problematic, because I moved the goalpost since creating it. But I'd rather not create a thread every time I have a problem...
Click to expand...
Click to collapse
The problems are all related, and probably the same root cause (Sprint version, firmware, etc.). I agree it is most appropriate to keep everything to this one thread.