Develop Bugs

Screwed Up Need Help URGENT

Hi. My phone has had issues with not being able to be mount backups on TWRP and have tried everything to fix the problem with no luck. I read somewhere on a post that the only way I can fix my problem is to relock my bootloader and flash a RUU which I'm in the process of doing now. This all started when I accidentally deleted my system files (which was stupid) in TWRP. Have I screwed up and will I be able to flash the RUU onto my phone.

NEVER do anything until you got the correct files. Who says there is a RUU ? we need info.....
Post the outcome of :
Fastboot getvar all (and del the IMEI & SERIAL)
Can you enter the bootloader and the recovery ?

Mr Hofs said:
NEVER do anything until you got the correct files. Who says there is a RUU ? we need info.....
Post the outcome of :
Fastboot getvar all (and del the IMEI & SERIAL)
Can you enter the bootloader and the recovery ?
Click to expand...
Click to collapse
Thanks for the quick response, it's really late right now but hopefully I can post those details tomorrow morn. I can enter bootloader/hboot which my computer recognizes. Though I have relocked the bootloader which I can easily unlock, it's status is relocked. My recovery (TWRP) was killing me though as every time I pushed a file through adb which was received the bloody program spat out an error every time about being unmountable to the system and cache. I know I shouldn't have rooted my device if I didn't know what I was doing and what did you mean about not having the correct files? I did have a cm11 stable backup but that wouldn't "mount to disk" either. From what I have heard I think this is a soft brick which would mean it is repairable? Or is it just a lost cause?

Also if this helps, I am s-on and wiped my dalvik, cache, data and accidents the system. I also have a 32 gb sd card installed on the device.

Cool. The easiest way is to unlock the bootloader, load a rom.zip (preferably) a sense 6 (close to stock rom like arhd or maximus) and perform a full wipe in the recovery and install the rom.zip via the recovery (external sd)
See if there are any errors in this process

Mr Hofs said:
Cool. The easiest way is to unlock the bootloader, load a rom.zip (preferably) a sense 6 (close to stock rom like arhd or maximus) and perform a full wipe in the recovery and install the rom.zip via the recovery (external sd)
See if there are any errors in this process
Click to expand...
Click to collapse
Tried this, if I try to load a rom onto my m8 it will automatically fail. The rom is not able to be mounted to anything. I also tried flashing a boot.img to try to get it to startup but it also failed from the same reasons as flashing a sense base rom and cm11. Also before I cleared the system partition I had a gpe rom installed if that helps.

Was it a complete gpe or just a Rom? Also if Roms are failing to install get the sdcard from the phone and use a card reader...then put the zip on it and flash it..normally a boot.img fastboot should be flashed without problems

Read this thread carefully, it has info about not mounting issues !
http://forum.xda-developers.com/showthread.php?t=2850470
Maybe this applies to you too

Mr Hofs said:
Read this thread carefully, it has info about not mounting issues !
http://forum.xda-developers.com/showthread.php?t=2850470
Maybe this applies to you too
Click to expand...
Click to collapse
Ok now I am able to do the fastboot getvar all cmd, here it is:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA15_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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: VODAP021
(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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.204s
Hope this helps
Also I have tried to fix using the solution mentioned though I don't know where to download the "mkfs.ext4 binary".

Mr Hofs said:
Who says there is a RUU ? we need info.....
Click to expand...
Click to collapse
There is an RUU for the AT&T Variant online. I used it to restore my M8 back to stock. There is a link here, you just got to look for it.

Oditius said:
There is an RUU for the AT&T Variant online. I used it to restore my M8 back to stock. There is a link here, you just got to look for it.
Click to expand...
Click to collapse
Hi, would I be able to flash an RUU onto my m8 International version with s-on?

jarrodli2 said:
Hi, would I be able to flash an RUU onto my m8 International version with s-on?
Click to expand...
Click to collapse
Yes,you can....find the ruu. And as for that file you could have taken the initiative to PM the user that has it !
Oditius said:
There is an RUU for the AT&T Variant online. I used it to restore my M8 back to stock. There is a link here, you just got to look for it.
Click to expand...
Click to collapse
LOL People rely on having a ruu to much. Good luck in finding one for him. Since he is s-on it has to match his official main too because downgrading is not an option (with a ruu)
1 ruu for the AT&T....does it work on a Sprint device ? Does it work on a international carrier branded device ?

Mr Hofs said:
Yes,you can....find the ruu first
---------- Post added at 04:46 AM ---------- Previous post was at 04:44 AM ----------
People rely on having a ruu to much. Good luck in finding one for him. Since he is s-on it has to match his official main too because downgrading is not an option (with a ruu)
Click to expand...
Click to collapse
GOD YES!, i've somehow managed to get the bloody device to boot up but now its stuck in a bootloop. I think i opened up a custom rom extracted the boot.img file and flashed it to something (not sure what). Does this mean i have to manually replace each partition (data, cache, system ect.) with a part of a rom?

I would install a fresh rom via the sdcard.
And you "think" you opened a rom.zip and flashed a boot.img ? Seriously .....

Mr Hofs said:
I would install a fresh rom via the sdcard.
And you "think" you opened a rom.zip and flashed a boot.img ? Seriously .....
Click to expand...
Click to collapse
Unfortunaly the problem still persists (log) ;
E: Can't mount /sdcard
E: Can't mount /data
E: Can't mount /cache
E: Can't mount /system
Installation aborted.
I really don't know how i've gotten to this point, should I just take my phone back to the manufacturer for repair?

Oditius said:
There is an RUU for the AT&T Variant online. I used it to restore my M8 back to stock. There is a link here, you just got to look for it.
Click to expand...
Click to collapse
Does it matter what m8 you have...like I have a international one m8 so can I use the at&t RUU
Sent from my HTC One_M8 using XDA Free mobile app

No you need to PM the guy with the mkfs file and fix that first.

ok just pm'ed him, hope he can respond soon. As for the state of my phone, is it soft or hard bricked? I just can't tell the difference because other people in the same situation as me have given up.

Its soft......as long as you can reach the bootloader it could be fixed.
ILIVE4HEAD said:
Does it matter what m8 you have...like I have a international one m8 so can I use the at&t RUU
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
If you want a phone that doesn't work.....then yes !

Mr Hofs said:
Its soft......as long as you can reach the bootloader it could be fixed.
If you want a phone that doesn't work.....then yes !
Click to expand...
Click to collapse
Lol thanks
Sent from my HTC One_M8 using XDA Free mobile app

HTC One m8 stuck in fastboot mode

Okay so.. In december i rooted my phone to Cyanogenmod. I lost the phone and got it back after 6 months.
I have reinstalled everything on my computer so i dont have the cyanogenmod left, unlock code or anything just so you know.
However.
Yesterday i tried to go back to stock android, HTC Sense.
So i searched on youtube how to do it, i followed the steps and i apparently had the wrong RUU.
What happend is weird..
Somehow i could startup my phone and it looked like i still had cyanogenmod. However this time i could not load up any applications without it crashing. I could not start my wifi or anything.
So i tried everything over again.
Installing twrp and.. after that i couldnt get into recovery.
Everytime i load up fastboot and try press recovert or factory reset it says "Entering recovery..." and then it reboots into android.
So i tried to install a new RUU.
Apparently still the wrong one, and this time im stuck in fastboot. No matter what i do i cant get out from fastboot.
So i'm asking you guys, do you have any idea of what i can do?
Oh and i managed to relock my phone, even though it said "failed" on CMD, it rebooted and then it said relocked.
So i cant unlock it either now. It just says "!!ERROR!!"
So im sitting here with what i think is a bricked phone, and im hoping for the best that it isnt..
So can you help me with this? Is it possible?
I can give you all information you need if you ask for it. For now i dont know what to say about this.
EDIT: Yes i have looked through 1000 different threads about beeing stuck in fastboot. But nothing helps.
If you need pictures of how it looks or anything i can fix that.

rambofreac said:
Okay so.. In december i rooted my phone to Cyanogenmod. I lost the phone and got it back after 6 months.
I have reinstalled everything on my computer so i dont have the cyanogenmod left, unlock code or anything just so you know.
However.
Yesterday i tried to go back to stock android, HTC Sense.
So i searched on youtube how to do it, i followed the steps and i apparently had the wrong RUU.
What happend is weird..
Somehow i could startup my phone and it looked like i still had cyanogenmod. However this time i could not load up any applications without it crashing. I could not start my wifi or anything.
So i tried everything over again.
Installing twrp and.. after that i couldnt get into recovery.
Everytime i load up fastboot and try press recovert or factory reset it says "Entering recovery..." and then it reboots into android.
So i tried to install a new RUU.
Apparently still the wrong one, and this time im stuck in fastboot. No matter what i do i cant get out from fastboot.
So i'm asking you guys, do you have any idea of what i can do?
Oh and i managed to relock my phone, even though it said "failed" on CMD, it rebooted and then it said relocked.
So i cant unlock it either now. It just says "!!ERROR!!"
So im sitting here with what i think is a bricked phone, and im hoping for the best that it isnt..
So can you help me with this? Is it possible?
I can give you all information you need if you ask for it. For now i dont know what to say about this.
EDIT: Yes i have looked through 1000 different threads about beeing stuck in fastboot. But nothing helps.
If you need pictures of how it looks or anything i can fix that.
Click to expand...
Click to collapse
In fastboot, issue the command fastboot getvar all, and post the readout here. Be sure to edit out the serial # and IMEI from it though. Never post those on a public forum.
I, or someone else here, will be able to direct you to the proper RUU with that information..

xunholyx said:
In fastboot, issue the command fastboot getvar all, and post the readout here. Be sure to edit out the serial # and IMEI from it though. Never post those on a public forum.
I, or someone else here, will be able to direct you to the proper RUU with that information..
Click to expand...
Click to collapse
I have now solved it, and i will post how i did it. Thx anyway, even if it was a bit late.

rambofreac said:
I have now solved it, and i will post how i did it. Thx anyway, even if it was a bit late.
Click to expand...
Click to collapse
Yeah. I scrolled the Q&A forum this morning looking for unanswered posts. Yours was one of them. I'm glad to hear that you have fixed it.

xunholyx said:
Yeah. I scrolled the Q&A forum this morning looking for unanswered posts. Yours was one of them. I'm glad to hear that you have fixed it.
Click to expand...
Click to collapse
same problem and i cant solve it . help plz

7anata said:
same problem and i cant solve it . help plz
Click to expand...
Click to collapse
Same info needed that I asked the last user for. fastboot getvar all results, minus your ser# and IMEI

xunholyx said:
Same info needed that I asked the last user for. fastboot getvar all results, minus your ser# and IMEI
Click to expand...
Click to collapse
version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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: 0P6B63000
(bootloader) cidnum: HTC__622
(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
and why there is no version main number

7anata said:
same problem and i cant solve it . help plz
Click to expand...
Click to collapse
Same problem, meaning you rooted the phone a year ago, put CM on it, then lost it and got it back 6 months later???
That's an incredible coincidence!!!!
Seriously, some constructive advice for a new forum user: DO NOT EVER say "same problem" then don't post any details on your phone and issue. It makes it virtually impossible to provide you any help. There are far too many variables such as carrier versions, software versions, and personal setups; that guarantee that issues may be similar, but never the "same". That's why its important to provide details, otherwise you just waste time us having to ask you for them.
Additionally, what were you doing with the phone that brought it to this point (stuck in fastboot)? Provide as much detail as possible (you can never really provide too much detail). Exact steps, what you were trying to flash, install or update, etc. Any error messages or other behaviors from the phone before it got stuck, etc. Also, what TWRP version? Do you have a nandroid (TWRP backup) available? Do you have a custom ROM installed?
---------- Post added at 10:40 AM ---------- Previous post was at 10:35 AM ----------
xunholyx said:
minus your ser# and IMEI
Click to expand...
Click to collapse
Also, xunholyx was very clear that you should delete your serial number and IMEI before posting getvar data. These are personal data, that should never be posted on open forums; so please delete them from the above post.
---------- Post added at 10:41 AM ---------- Previous post was at 10:40 AM ----------
7anata said:
and why there is no version main number
Click to expand...
Click to collapse
Known version caused by old TWRP builds.

---------- Post added at 10:41 AM ---------- Previous post was at 10:40 AM ----------
[/COLOR]
Known version caused by old TWRP builds.[/QUOTE]
thanx alot , but i have latest version of TWRP 2.8.7.0 , how can i know version-main , thanx in advance

7anata said:
thanx alot , but i have latest version of TWRP 2.8.7.0 , how can i know version-main , thanx in advance
Click to expand...
Click to collapse
If an older version of TWRP was used at any point in the past, it would have wiped out the main version, and the only way to make it reappear is to flash a firmware or RUU.
Based on your CID and radio number, I believe your main version is 4.18.708
If you want further help, you need to provide the information I asked for (and that you have ignored):
redpoint73 said:
Additionally, what were you doing with the phone that brought it to this point (stuck in fastboot)? Provide as much detail as possible (you can never really provide too much detail). Exact steps, what you were trying to flash, install or update, etc. Any error messages or other behaviors from the phone before it got stuck, etc. Do you have a nandroid (TWRP backup) available? Do you have a custom ROM installed?
Click to expand...
Click to collapse

redpoint73 said:
If an older version of TWRP was used at any point in the past, it would have wiped out the main version, and the only way to make it reappear is to flash a firmware or RUU.
Based on your CID and radio number, I believe your main version is 4.18.708
If you want further help, you need to provide the information I asked for (and that you have ignored):
Click to expand...
Click to collapse
sorry man i didn't ignore the info , i didn't see that , iam tring to update cm 13 17/12/2015 recovery , iam on cm13 15/12/2015 rom , i solved the stuck problem but can't get excat version main so i can uroot my phone .....
and according to this link there isn't main version is 4.18.708 with cid Htc__622

Please help for my HTC One M8 update

I write here because i can't write to he's thread.
I installed the 6.0 rom for my HTC One M8 from graffixnyc, but has not sound and it write's driver error, unknown problem. What's the problem?
I have S-on, custom recovery (twrp) and unlock bootloader. Plus the Hboot write's wrong image error.
I can't convert the cid to GOOGL_001, i have T-MOB101. That's the problem?
Thanks for the help!
Sorry for my bad English, I'm Hungarian!

Old firmware probably, you likely need to go back to stock and wait for all ota updates . BTW, this should be in q and a not general

timbohobbs said:
Old firmware probably, you likely need to go back to stock and wait for all ota updates . BTW, this should be in q and a not general
Click to expand...
Click to collapse
I can't back to stock because, not have original rom, firmware and ruu for this M8. It's a DE phone supposedly, but i can use it from Hungary with my Hungary sim card.
I wanna try to upgrade once and the phone bricked and i install twrp and a stock rooted rom from android revolution hd.

You'll probably run into problems if your firmware is out of date. S off may get you out of a hole

peti439 said:
I can't back to stock because, not have original rom, firmware and ruu for this M8. It's a DE phone supposedly
Click to expand...
Click to collapse
By DE you mean Developer's Edition? But your top post says T-MOB101.
If you don't know what your version is, you'll never get an RUU to work.
You can restore to stock nandroid from the collection posted on these threads, but again you need to know your correct CID version.
Do fastboot getvar all, and post the output (be sure to delete IMEI and serial numbers, as these are personal info) and we may be able to determine your actual CID version.
---------- Post added at 02:31 PM ---------- Previous post was at 02:31 PM ----------
peti439 said:
I can't convert the cid to GOOGL_001, i have T-MOB101. That's the problem?
Click to expand...
Click to collapse
You need s-off to change CID.

redpoint73 said:
By DE you mean Developer's Edition? But your top post says T-MOB101.
Click to expand...
Click to collapse
T-Mobile DE (Germany) - T-MOB101 - software version no. x.xx.111.x

ckpv5 said:
T-Mobile DE (Germany) - T-MOB001 - software version no. x.xx.111.x
Click to expand...
Click to collapse
Thanks! I thought that might be the case, but it was ambiguous. That's why its best for folks to be specific and detailed when asking for help!
To OP, still need getvar output to properly identify the right stock nandroid.

redpoint73 said:
Thanks! I thought that might be the case, but it was ambiguous. That's why its best for folks to be specific and detailed when asking for help!
To OP, still need getvar output to properly identify the right stock nandroid.
Click to expand...
Click to collapse
Agreed ... a typo is corrected - should read T-MOB101

redpoint73 said:
Thanks! I thought that might be the case, but it was ambiguous. That's why its best for folks to be specific and detailed when asking for help!
To OP, still need getvar output to properly identify the right stock nandroid.
Click to expand...
Click to collapse
I go to my computer and make a picture for the cidnum number. Wait a little

Here's what i got. My Hboot is 3.19.0.0000 and the Radio is 1.25.214500021.06G ( I don't know this are need )
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.111.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxx
(bootloader) imei: xxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: T-MOB101
(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

peti439 said:
Here's what i got.
Click to expand...
Click to collapse
I clearly posted previously (Post #5 above) to delete your IMEI and serial numbers from getvar output. These are personal data what should never be posted online. Please delete these numbers for your own protection.
---------- Post added at 09:37 AM ---------- Previous post was at 09:33 AM ----------
peti439 said:
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021
(bootloader) version-main: 4.19.111.2
Click to expand...
Click to collapse
The above info indicates that firmware shouldn't be an issue.
Did you do a full wipe (data, cache, Dalvik) when installing the GPE ROM?
---------- Post added at 09:41 AM ---------- Previous post was at 09:37 AM ----------
peti439 said:
Plus the Hboot write's wrong image error.
I can't convert the cid to GOOGL_001, i have T-MOB101. That's the problem?
Click to expand...
Click to collapse
It sounds like you are trying to do 2 different things:
- Flash the ROM zip in TWRP
- Flash the RUU (s-off required)
Which is it? You need to make up your mind, and understand the difference between the 2.

redpoint73 said:
I clearly posted previously (Post #5 above) to delete your IMEI and serial numbers from getvar output. These are personal data what should never be posted online. Please delete these numbers for your own protection.
---------- Post added at 09:37 AM ---------- Previous post was at 09:33 AM ----------
The above info indicates that firmware shouldn't be an issue.
Did you do a full wipe (data, cache, Dalvik) when installing the GPE ROM?
Click to expand...
Click to collapse
I make a full wipe before install the rom ( i make a full wipe before install any rom ). I installed the rom, make the setup steps ( login, etc ) and I can't hear any sound. I make a reboot and I looked the driver error.

peti439 said:
I make a full wipe before install the rom ( i make a full wipe before install any rom ). I installed the rom, make the setup steps ( login, etc ) and I can't hear any sound. I make a reboot and I looked the driver error.
Click to expand...
Click to collapse
Try to flash again.
Did you read the ROM thread to see if others had this issue?

redpoint73 said:
Try to flash again.
Did you read the ROM thread to see if others had this issue?
Click to expand...
Click to collapse
I flashed the rom three times and doesn't work. I not see others have any issues.

---------- Post added at 09:41 AM ---------- Previous post was at 09:37 AM ----------
redpoint73 said:
It sounds like you are trying to do 2 different things:
- Flash the ROM zip in TWRP
- Flash the RUU (s-off required)
Which is it? You need to make up your mind, and understand the difference between the 2.
Click to expand...
Click to collapse
I try to flash the ruu with 0p6bdiag.zip in HBoot and try to flash the rom with twrp. That was the problem to writes the error in Hboot?

peti439 said:
I try to flash the ruu with 0p6bdiag.zip in HBoot and try to flash the rom with twrp. That was the problem to writes the error in Hboot?
Click to expand...
Click to collapse
"Wrong image" means you are trying to run an RUU that doesn't match your CID. You need s-off to change CID.
---------- Post added at 10:16 AM ---------- Previous post was at 10:15 AM ----------
peti439 said:
I flashed the rom three times and doesn't work. I not see others have any issues.
Click to expand...
Click to collapse
Try downloading the ROM zip to eliminate the possibility that it was corrupted during download.
Did you cancel the option in TWRP to root the ROM, as directed in the ROM thread?

redpoint73 said:
"Wrong image" means you are trying to run an RUU that doesn't match your CID. You need s-off to change CID.
---------- Post added at 10:16 AM ---------- Previous post was at 10:15 AM ----------
Try downloading the ROM zip to eliminate the possibility that it was corrupted during download.
Did you cancel the option in TWRP to root the ROM, as directed in the ROM thread?
Click to expand...
Click to collapse
I canceled to root the rom because I tried to root the rom, i got bootloop everytime.

peti439 said:
I canceled to root the rom because I tried to root the rom, i got bootloop everytime.
Click to expand...
Click to collapse
Which is expected, and clearly indicated in the ROM instructions.
But it sounds like at least on the latest flash attempts, you properly cancelled the root option.
I don't seen much reason for the bugs you are experiencing. Did you try to download the ROM again as previously suggested?

redpoint73 said:
Which is expected, and clearly indicated in the ROM instructions.
But it sounds like at least on the latest flash attempts, you properly cancelled the root option.
I don't seen much reason for the bugs you are experiencing. Did you try to download the ROM again as previously suggested?
Click to expand...
Click to collapse
I downloaded two times. Once my computer and second time to my girlfriend laptop ( that was three days ago ) and doesn't work, the zip was not corrupted.

Phone Freezes Upon Booting (Android N ROMS)

Hello XDA,
I've made absolutely no changes to my phone settings, ROMS, Kernal ETC..
Recently, I've decided to upgrade to a new ROM which was CRDroid Android 7.0 (Name may be wrong)
I use Philz CWM recovery, while installing I noticed once it finished it said cannot mount /data.
Though the phone rebooted on it's own and started to boot, but once it reached the boot logo the phone froze.
Directly in the middle of the animation, it stopped and stayed that way for at least 15 minutes before I had to hard reset it.
I noticed I cannot install any type of Android N (7.0) ROM without freezing, I can only install Marshmellow or lower.
Can anyone explain why, is this a firmware issue perhaps?

Use the latest TWRP recovery
Philz is outdated now and most probably won't work
Sent from my HTC M8 using XDA Labs

Regardless of the recovery used, problem still persists. I believe it may be a firmware issue.

Trytohaxme said:
Regardless of the recovery used, problem still persists.
Click to expand...
Click to collapse
Does that mean you tried TWRP or not? And what version(s)?
In TWRP do you still get issue not mounting data? If so, try going to Wipe section of TWRP, and tap "Format data" which will often fix the mount data problem. Obviously, your data will be lost.
Please try to give as much detail and specific as possible when posting. Posting a 2 sentence response is rarely enough for us to work with.
Trytohaxme said:
I believe it may be a firmware issue.
Click to expand...
Click to collapse
We would need to know more about the firmware to say anything about that. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting0

Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.12.20.1211
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.17.605.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(bootloader) imei2: Not Support
(bootloader) meid: 99000499864898
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(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: f2489bd1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.098s
I've tried about 3 versions of TWRP, including the latest version.
I'm no longer able to format or install using TWRP which is the reason I have to use Philz.
I have major screen burn issues on the top portion of my phone, so touch is unresponsive so being able to use the volume rocker with Philz recovery is a life saver.
I've heard something about connecting the phone to a windows laptop, and formatting the partitions VIA > Device Manager helps with mounting the /Data partition though because I believe mine may be corrupt as I can only install ROMS that do not touch the data partition.

Trytohaxme said:
(bootloader) version-main: 4.17.605.5
(bootloader) product: m8_wlv
(bootloader) modelid: 0P6B20000
Click to expand...
Click to collapse
Your firmware is Lollipop. I'm not a user of the AOSP ROMs (as all Nougat ROMs are), but from what ahmed posted, LP ROMs can indeed cause problems with Hougat: https://forum.xda-developers.com/htc-one-m8/help/upgrade-5-1-1-to-7-x-x-to-firmware-t3580047
Also, your getvar output shows you have the Verizon M8. Did you verify the ROMs support the Verizon version?

redpoint73 said:
Your firmware is Lollipop. I'm not a user of the AOSP ROMs (as all Nougat ROMs are), but from what ahmed posted, LP ROMs can indeed cause problems with Hougat: https://forum.xda-developers.com/htc-one-m8/help/upgrade-5-1-1-to-7-x-x-to-firmware-t3580047
Also, your getvar output shows you have the Verizon M8. Did you verify the ROMs support the Verizon version?
Click to expand...
Click to collapse
I'm currently downloading MM firmware for my device, and yes I verify there is Verizon support.
Though my phones model is Verizon branded, the phone is unlocked and I use it with T-Mobile.

Trytohaxme said:
Though my phones model is Verizon branded, the phone is unlocked and I use it with T-Mobile.
Click to expand...
Click to collapse
What M8 version is important in this case (Verizon) for a variety of reasons, and I'm not talking about what carrier you are using it on. The Verizon version M8 is very unique in that it uses different kernel, partitioning, and antenna hardware due to CDMA support. Plus, you can only flash Verizon firmware or RUU (others won't work, and may even cause a permanent radio brick). The Sprint version has similar aspects (although the firmware is not even interchangeable between Sprint and Verizon M8 versions).

redpoint73 said:
What M8 version is important in this case (Verizon) for a variety of reasons, and I'm not talking about what carrier you are using it on. The Verizon version M8 is very unique in that it uses different kernel, partitioning, and antenna hardware due to CDMA support. Plus, you can only flash Verizon firmware or RUU (others won't work, and may even cause a permanent radio brick). The Sprint version has similar aspects (although the firmware is not even interchangeable between Sprint and Verizon M8 versions).
Click to expand...
Click to collapse
Well, I did a little more research and seem to have come to the conclusion that in order to flash the roms I'm trying to flash I need to use TWRP.
The problem is since my phone top portion of the screen is not touch responsive, I have no choice but to use Philz.
Is there a TWRP that would happen to work in landscape mode, otherwise I'm SOL.

Trytohaxme said:
Well, I did a little more research and seem to have come to the conclusion that in order to flash the roms I'm trying to flash I need to use TWRP.
The problem is since my phone top portion of the screen is not touch responsive, I have no choice but to use Philz.
Is there a TWRP that would happen to work in landscape mode, otherwise I'm SOL.
Click to expand...
Click to collapse
I understand you have some peculiar things going on causing you to use Philz. I don't think there is a harm in trying Philz (to flash an N ROM), after you have the firmware updated. But I just wouldn't expect Philz (which hasn't been updated for 2 years) to work well with the latest ROMs.
No landscape TWRP that I know of.

redpoint73 said:
I understand you have some peculiar things going on causing you to use Philz. I don't think there is a harm in trying Philz (to flash an N ROM), after you have the firmware updated. But I just wouldn't expect Philz (which hasn't been updated for 2 years) to work well with the latest ROMs.
No landscape TWRP that I know of.
Click to expand...
Click to collapse
Each ROM I tried installed give me basically the same output, maybe you can help figure them out.
Code:
detected filesystem ext4 for /dev/block/flatform/msm_sdcc. 1/by-name/system
unmount of /system failed
failed to mount /dev/block/flatform/msm_sdcc. 1/by-name/userdata at /data: device or resource busy
These are the 3 differents errors I receive during installation of a new ROM.
After those errors show the ROM continues with the installation, but as soon as the phone boots it freezes than reboots back to recovery.

Trytohaxme said:
Each ROM I tried installed give me basically the same output, maybe you can help figure them out.
Click to expand...
Click to collapse
Is this with Philz?
Is this on the LP firmware or MM firmware?
---------- Post added at 01:18 PM ---------- Previous post was at 01:17 PM ----------
Maybe adb sideload feature can help you to use TWRP in your condition?
https://twrp.me/faq/ADBSideload.html

redpoint73 said:
Is this with Philz?
Is this on the LP firmware or MM firmware?
---------- Post added at 01:18 PM ---------- Previous post was at 01:17 PM ----------
Maybe adb sideload feature can help you to use TWRP in your condition?
https://twrp.me/faq/ADBSideload.html
Click to expand...
Click to collapse
This is on LP and MM firmware, and the same output occurs even while using sideload sadly
Here is a photo I just took using my laptops webcam, as you see the boot animation starts than completely freezes.
http://imgur.com/BSZ2ZzD

HTC One M8 stuck on HTC screen

Hi all.
Got a HTC one m8 in and it appears to be stuck on the HTC screen, I can get into bootloader fine, have tried to reflash via SD card but i get a CID error.
Can anyone direct me to what ROM i need to be installing? Its a UK version.
Thanks in advance.

Jabbah said:
Hi all.
Got a HTC one m8 in and it appears to be stuck on the HTC screen, I can get into bootloader fine, have tried to reflash via SD card but i get a CID error.
Can anyone direct me to what ROM i need to be installing? Its a UK version.
Thanks in advance.
Click to expand...
Click to collapse
What does it say next to "OS" in your bootloader menu?

Jabbah said:
have tried to reflash via SD card but i get a CID error.
Can anyone direct me to what ROM i need to be installing? Its a UK version.
Click to expand...
Click to collapse
Tried to flash what? Can't troubleshoot what you did wrong, unless you tell is what you tried to flash. RUU, firmware.zip, or something else? What is the version number and file name?
That is in addition to the info requested in the previous reply.
Also, if you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting) so we can see more info about the device.

redpoint73 said:
Tried to flash what? Can't troubleshoot what you did wrong, unless you tell is what you tried to flash. RUU, firmware.zip, or something else? What is the version number and file name?
That is in addition to the info requested in the previous reply.
Also, if you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting) so we can see more info about the device.
Click to expand...
Click to collapse
Tried to flash a stock UK rom.
I have no idea how to use that command sorry.
os is 6.12.61.4

(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.61.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

Jabbah said:
Tried to flash a stock UK rom.
Click to expand...
Click to collapse
Still too vague for us to have any idea what you tried to flash.
I asked some specific questions for a reason; some of which you seem to have missed or ignored. I'm not just typing to exercise my fingers!
redpoint73 said:
RUU, firmware.zip, or something else?
What is the version number and file name?
Click to expand...
Click to collapse
"Stock UK ROM" can mean a number of things. If you are talking about RUU, then calling it a "stock ROM" is not the right term (and confusing) since RUU is a complete image containing something like 41 partitions, with the ROM being only one of those partitions.
In fact, if you are referring to RUU, I don't think your version M8 (or most UK versions, for that matter) has a valid RUU. So you are likely in fact not even trying to flash a stock UK ROM. Which also explains the CID error.
On a positive note, good work figuring out how to do fastboot getvar all. If you can provide more info on what you tried to flash, we can make some progress!

redpoint73 said:
Still too vague for us to have any idea what you tried to flash.
I asked some specific questions for a reason; some of which you seem to have missed or ignored. I'm not just typing to exercise my fingers!
"Stock UK ROM" can mean a number of things. If you are talking about RUU, then calling it a "stock ROM" is not the right term (and confusing) since RUU is a complete image containing something like 41 partitions, with the ROM being only one of those partitions.
In fact, if you are referring to RUU, I don't think your version M8 (or most UK versions, for that matter) has a valid RUU. So you are likely in fact not even trying to flash a stock UK ROM. Which also explains the CID error.
On a positive note, good work figuring out how to do fastboot getvar all. If you can provide more info on what you tried to flash, we can make some progress!
Click to expand...
Click to collapse
Thanks for the replies, ive actually gotten somewhere today, Ive installed twrp, and installed the latest Lineage ROM which booted fine .
But.... Not detecting sim card
Always something haha

Another option (especially now that you have unlocked the bootloader, and installed TWRP), is restore stock TWRP backup 6.12.61.4 from here:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
No need to do Step 3, nor Steps 10 or after (only relevant to get OTA updates - which no longer applies to this device). Just reboot.
Jabbah said:
Thanks for the replies
Click to expand...
Click to collapse
There is a button for that.

Quick update, Restored stock TWRP as you suggested, performed simunlock and am now a happy chappy with a working M8
Now, Whats the best ROM to use for it ? Is it worth installing Lineage ROM?
David.

Jabbah said:
Quick update, Restored stock TWRP as you suggested, performed simunlock and am now a happy chappy with a working M8
Now, Whats the best ROM to use for it ? Is it worth installing Lineage ROM?
Click to expand...
Click to collapse
Glad the TWRP restore worked out for you.
No such thing as a "best ROM". Each individual user has different preferences and tastes. That's the reason there are different ROM choices. If there was a "best ROM", nobody would ever need anything else, right?
I am not personally a Lineage user (so good example right there how one person's opinion may not apply to you). But if you flash it again, I assume you can (or will) have the same problem with SIM not detected. I think I've seen other folks with the problem on Lineage (again, I don't really keep up with that ROM), so you should check the thread to see if there is a fix for that issue.

redpoint73 said:
Glad the TWRP restore worked out for you.
No such thing as a "best ROM". Each individual user has different preferences and tastes. That's the reason there are different ROM choices. If there was a "best ROM", nobody would ever need anything else, right?
I am not personally a Lineage user (so good example right there how one person's opinion may not apply to you). But if you flash it again, I assume you can (or will) have the same problem with SIM not detected. I think I've seen other folks with the problem on Lineage (again, I don't really keep up with that ROM), so you should check the thread to see if there is a fix for that issue.
Click to expand...
Click to collapse
Got around the sim not detected issue, the phone was simlocked to orange, it just didnt pop up with the enter unlock code dialogue.
Ill try a few see what they are like
Thanks again for your help.

Jabbah said:
Got around the sim not detected issue, the phone was simlocked to orange.
Click to expand...
Click to collapse
Understood. I would not have expected the "SIM not detected" error in that case. So thanks for clarifying.
Jabbah said:
it just didnt pop up with the enter unlock code dialogue.
Click to expand...
Click to collapse
Stock (Sense) ROM is needed to unlock SIM. Which you either figured out, or stumbled upon the solution by luck! :good: