Develop Bugs

[Q] AT&T One M8. Can't successfully flash/boot recovery image or boot to system.

So! My phone is Tampered, Unlocked, and S-ON. I don't have a usable recovery image. I've tried the most recent Snapshot Cyanogen Recovery and the most recent TWRP for the M8, neither work by trying fastboot flash recovery <thing> or fastboot boot <thing>. The TWRP one vibrated when I touched the screen in where I presume the buttons are, but neither actually showed anything on screen.
What I can do: get to the bootloader. It's unlocked, as I said. I can also stare at the Google logo, taunting me, if I try to boot to recovery or to system.
What I would like to do: get a custom recovery that works, flash a ROM that works, and get on with my life without spending $XXX on another phone.
What I have already tried: an RUU. Didn't work. Not one bit. Error'd immediately, saying it can't do anything.
Here's the bootloader header:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1.14.21331931.LA02_2G
OpenDSP-v32.2.2-00542-M8974.0213
OS-2.12.1700.1
eMMC-boot 2048MB
Jun 16, 2014,18:47:55.0
And the infodump:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.12.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

BaconSupreme said:
HBOOT-3.18.0.0000
Click to expand...
Click to collapse
Your hboot is pretty old. Try an older version TWRP (old hboot does not work with current TWRP, and vice versa new hboot does not work with older TWRP).
Try TWRP 2.7.something.
Better yet, relock the bootloader and RUU to Lollipop to update the firmware (hboot, radio, etc.). Then unlock the bootloader again, and flash current TWRP 2.8.7. If your goal is to flash custom ROMs, this is what you want anyway. Lollipop custom ROMs won't function properly on your old KitKat firmware.
---------- Post added at 12:51 PM ---------- Previous post was at 12:45 PM ----------
BaconSupreme said:
What I have already tried: an RUU. Didn't work. Not one bit. Error'd immediately, saying it can't do anything.
Click to expand...
Click to collapse
Those sentences lack so much detail, as to be virtually useless in us helping you.
"An RUU" ??? What RUU did you try (exact file name)? It needs to be an RUU for AT&T M8.
What was the error message? It states the reason the RUU failed.
The latest AT&T RUU can be found at the bottom of the following webpage: http://www.htc.com/us/support/htc-one-m8-att/news/
---------- Post added at 12:53 PM ---------- Previous post was at 12:51 PM ----------
BaconSupreme said:
What I would like to do: get a custom recovery that works, flash a ROM that works, and get on with my life without spending $XXX on another phone.
Click to expand...
Click to collapse
You don't even remotely need to worry about buying a new phone yet. You're just going about a couple things wrong, easily correctable.

So!
TWRP 2.7.1.0 was successfully flashed and started. Thanks for the suggestion. Successfully flashed and booted CM 11.
In regards to the RUU, the exact one that you linked is the one I tried to use. The error code I got was 155: Unknown Error. I've never had much success with RUUs in general.
Do you know if there's a Lollipop firmware.zip floating around for my MID/CID? I tried to find one for a bit but was unsuccessful. If I understand things right, I could relock my bootloader, flash a firmware.zip matching my MID/CID, re-unlock my bootloader, and flash updated versions of TWRP/CM.

BaconSupreme said:
In regards to the RUU, the exact one that you linked is the one I tried to use. The error code I got was 155: Unknown Error. I've never had much success with RUUs in general.
Click to expand...
Click to collapse
You need to relock the bootloader to RUU. That is the common reason for Error 155.
The main reason you've "never had much success with RUUs" may be due to lack of knowledge. An RUU will run as long as:
1) Correct RUU for your CID and MID
2) Equal or later RUU version than main version on the phone (this restriction does not apply with s-off)
3) RELOCKED or LOCKED bootloader (this restriction does not apply with s-off)
4) Some glitches may arise due to USB connectivity (re-installing HTC drivers or trying a different PC will usually solve this). But if you have an error message, USB connectivity is good.
BaconSupreme said:
Do you know if there's a Lollipop firmware.zip floating around for my MID/CID? I tried to find one for a bit but was unsuccessful. If I understand things right, I could relock my bootloader, flash a firmware.zip matching my MID/CID, re-unlock my bootloader, and flash updated versions of TWRP/CM.
Click to expand...
Click to collapse
I've never seen a signed Lollipop firmware zip for AT&T. And to flash an unsigned firmware, you need s-off.
Reason signed firmware is not common, is that its easy to just run the RUU.

redpoint73 said:
You need to relock the bootloader to RUU. That is the common reason for Error 155.
The main reason you've "never had much success with RUUs" may be due to lack of knowledge. An RUU will run as long as:
1) Correct RUU for your CID and MID
2) Equal or later RUU version than main version on the phone (this restriction does not apply with s-off)
3) RELOCKED or LOCKED bootloader (this restriction does not apply with s-off)
4) Some glitches may arise due to USB connectivity (re-installing HTC drivers or trying a different PC will usually solve this). But if you have an error message, USB connectivity is good.
I've never seen a signed Lollipop firmware zip for AT&T. And to flash an unsigned firmware, you need s-off.
Reason signed firmware is not common, is that its easy to just run the RUU.
Click to expand...
Click to collapse
The bootloader was relocked when I tried. I'll try reinstalling drivers and trying again later tonight.
Another potential reason might be what was on the phone at the time I just tried again (TWRP recovery / nonfunctional CM 12). Should I flash a stock recovery/ROM before trying the RUU, or does that not matter?

BaconSupreme said:
The bootloader was relocked when I tried. I'll try reinstalling drivers and trying again later tonight.
Click to expand...
Click to collapse
I already mentioned: drivers aren't the problem if you are getting error 155.
BaconSupreme said:
Another potential reason might be what was on the phone at the time I just tried again (TWRP recovery / nonfunctional CM 12). Should I flash a stock recovery/ROM before trying the RUU, or does that not matter?
Click to expand...
Click to collapse
Was that on my list of requirements for running an RUU? No, it was not. So NO, it does not matter. RUU re-images the phone to stock. It doesn't care what ROM or recovery is on the phone.
OTA is a different story. You need stock ROM and stock recovery. But OTA and RUU are 2 completely different things.
Are you sure the RUU file is the exact same one (same file name) that my link contains? I'm a bit skeptical when I link something, and response is "yeah yeah that's the one".
Try to relock the bootloader and the file I linked. Maybe you just forgot something, or mixed something up when you did it last time.
As long as the bootloader is relocked, and you use that file, it should work fine. But you can also use this one (also Lollipop, just without the Stagefright patch): http://dl3.htc.com/application/RUU_M8[email protected]50319A_40.45.C33065.00_F_release_426617_signed_2.exe
---------- Post added at 03:37 PM ---------- Previous post was at 03:27 PM ----------
WHOA. Hold the phone (no pun intended).
I just realized your main version number (firmware) is for GPE. It seems at some point the phone was converted to GPE. Did you do that?
That is probably why the RUU is failing.
You may need to s-off the phone again to get out of the hole. I think the phone must have been s-off at some point, in order to run a GPE firmware or RUU, then made s-on again.
Did you buy this phone used?

UNKNOWN BASEBANDE HTC ONE M8q NO CARD SIM DETECTED!!!! PLEASE HELP

Hi guys, i realy need some help; can't install any working rom in my device ; i've tray a lot of solution but cant fixe problem ( no basebande no imei )
im CID 11111111 / Unlocked
M8_UL PVT SHIP S-OFF
CID-11111111
HBOOT-3.19.0.0000
RADIO-1.29.214500021.12G
OpenDSP-v51.2.2-00593-M8974_FO.1015
OS-
eMMC-boot 2048MB
Jan 26 216,15:50:09.0
PLEASE HELP

Your post is really unclear, making it impossible to help without further info.
Did you have the issue of no SIM before, causing you to try to fix it? Or were you playing around with ROMs, and broke the baseband/SIM? In other words, what was the exact sequence of events that led to the current condition.
Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Also, is the bootloader locked, unlocked or relocked?
Do you have TWRP installed? If so, what version number?
Also:
morphus3x said:
can't install any working rom in my device
Click to expand...
Click to collapse
What exactly did you try to install (file names, ROM names, version numbers - provide as much detail as possible)?
morphus3x said:
i've tray a lot of solution
Click to expand...
Click to collapse
This isn't useful statement, unless you describe exactly what you tried (again, with exact file names, version numbers, etc.) and what the specific result of each was (description of results, error messages, etc.).

i have TWRP 3.1.1-0 just installed today, unlocked s-off
getvar 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:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: *******************
(bootloader) imei: ******************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
i broke it for real

i try to install many roms , this some ones :
0P6BIMG_M8_UHL_M60_SENSE70_MR_hTC_Asia_India_6.15.720.2_Radio_1.29.214500021.12G_20.72.4196t.01_F_release_469495_signed_2_4_gsmdevelopers.com
M8_UL_M60_SENSE70_MR_hTC_Asia_TW_6.20.709.2
HTC_One_M8_GPE_5.07.1700.11_MRA58K.H11_022
SkyDragonM8v4.0.0Sense8MM
I DELETE THIS OTHERS
there's no errors, just the device dont start, stock at one image and no menu, only start botton work

Your post #1 said you installed ROM but no baseband & no imei
Your post #3 said stuck on bootanimation (I guess)
So which ROM for no. 1 ?
0P6BIMG_M8_UHL_M60_SENSE70_MR_hTC_Asia_India_6.15. 720.2_Radio_1.29.214500021.12G_20.72.4196t.01_F_re lease_469495_signed_2_4_gsmdevelopers.com should be correct RUU for your device.
If you can boot ROM as no.1 and no baseband & imei, try install 6.15.720.2 firmware only to see whether it can fix your problem
https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5

ckpv5 said:
Your post #1 said you installed ROM but no baseband & no imei
Your post #3 said stuck on bootanimation (I guess)
So which ROM for no. 1 ?
0P6BIMG_M8_UHL_M60_SENSE70_MR_hTC_Asia_India_6.15. 720.2_Radio_1.29.214500021.12G_20.72.4196t.01_F_re lease_469495_signed_2_4_gsmdevelopers.com should be correct RUU for your device.
Click to expand...
Click to collapse
**********************************************************
only GPE rom can be installed to the end , the others stuck
this one ( 0P6BIMG_M8_UHL_M60_SENSE70_MR_hTC_Asia_India_6.15. 720.2_Radio_1.29.214500021.12G_20.72.4196t.01_F_re lease_469495_signed_2_4) dont wont install , stuck in TWRP, it's said the file is corrumpted

morphus3x said:
**********************************************************
only GPE rom can be installed to the end , the others stuck
this one ( 0P6BIMG_M8_UHL_M60_SENSE70_MR_hTC_Asia_India_6.15. 720.2_Radio_1.29.214500021.12G_20.72.4196t.01_F_re lease_469495_signed_2_4) dont wont install , stuck in TWRP, it's said the file is corrumpted
Click to expand...
Click to collapse
That is a RUU not flashable rom zip, you can't install RUU in twrp.
You installed GPE ROM in twrp ? So I guess you didn't install GPE RUU.
Try any other Sense ROM like ICE, if can boot but no baseband & imei, install firmware as I said above.
Another thing.. your bootloader is white and not black, right ?

ckpv5 said:
That is a RUU not flashable rom zip, you can't install RUU in twrp.
You installed GPE ROM in twrp ? So I guess you didn't install GPE RUU.
Try any other Sense ROM like ICE, if can boot but no baseband & imei, install firmware as I said above.
Another thing.. your bootloader is white and not black, right ?
Click to expand...
Click to collapse
*************************************************************************
yes bootloader is white , i tried the RUU method but it's stuck to, i had some errors. and i must phone must be relocked , i lost S-off when i did it.
i tried to get a backup like u say in ur post but not working
please can u help, what's the rom i may install can u give me all tutoriel

I never say any backup to try, only the firmware.
No need to relock bootloader to install RUU and no need to change to S-On (same for installing firmware too)
Install again GPE rom as you said you can install and working but no baseband
Then after install firmware, fw_6.15.720.2.zip only
then tell if baseband is fixed or not.

morphus3x said:
i tried the RUU method but it's stuck to, i had some errors. and i must phone must be relocked , i lost S-off when i did it.
Click to expand...
Click to collapse
What format is the RUU, is it zip or exe?
If it got stuck, what was the specific error message? Only telling us it "had some errors" is not useful. I shouldn't have to be telling you this again. Provide as much detail as possible, if you expect us to help.
You don't need to relock the bootloader to RUU when you have s-off.
Relocking the bootloader does not make the device s-on. Never seen it. It just makes the bootloader RELOCKED, which restricts a lot of other things (can't flash TWRP, etc.).

ckpv5 said:
I never say any backup to try, only the firmware.
No need to relock bootloader to install RUU and no need to change to S-On (same for installing firmware too)
Install again GPE rom as you said you can install and working but no baseband
Then after install firmware, fw_6.15.720.2.zip only
then tell if baseband is fixed or not.
Click to expand...
Click to collapse
*******************************************
it's not working , no imei no basebande to

i install GPE and flashing fw_6.15.720.2_recovery.img but not working no imei no basebande ,
last error when i tray RUU.exe was 179
thanks for ur help

morphus3x said:
i install GPE and flashing fw_6.15.720.2_recovery.img but not working no imei no basebande ,
Click to expand...
Click to collapse
Firmware and recovery nor two different things. I'm skeptical if you flashed the right thing, or did it properly.
Did you get the file, and follow the instructions exactly as listed in the link that ckpv5 gave your for the firmware?
Did you flash it twice, as the instructions say?
Do fastboot getvar all, again, and post (delete IMEI and serial number before posting).

morphus3x said:
i install GPE and flashing fw_6.15.720.2_recovery.img but not working no imei no basebande ,
last error when i tray RUU.exe was 179
thanks for ur help
Click to expand...
Click to collapse
It's not easy to help you when you don't understand the suggestion.
I never say 6.15.720.2_recovery.img, no such file in the link that I gave you. Please read again the filename is fw.15.720.2.zip and you need to install it using fastboot method or ext_sd method.
https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
I have to say good night now .. it's 3.15 am here.

morphus3x said:
last error when i tray RUU.exe was 179
Click to expand...
Click to collapse
Are you sure? I can't find error code 179.
Maybe you mean Error 170, which is USB connection error. Which often just means you need to put the phone in fastboot mode. Or try another USB cable, another USB port on the PC, or re-install the HTC drivers.

ckpv5 said:
It's not easy to help you when you don't understand the suggestion.
I never say 6.15.720.2_recovery.img, no such file in the link that I gave you. Please read again the filename is fw.15.720.2.zip and you need to install it using fastboot method or ext_sd method.
https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
I have to say good night now .. it's 3.15 am here.
Click to expand...
Click to collapse
OOOOOOOOOH IT'S WORKING ? THANKS GUYS? I'M VERY THINKFUL
i miss my my phone
one more think plzzzzzzzzzz; what rom can i install; i don't like GPE

morphus3x said:
one more think plzzzzzzzzzz; what rom can i install; i don't like GPE
Click to expand...
Click to collapse
Any of the ROMs from the M8 development section should work. You will need to unlock the bootloader again, and flash TWRP to the device again (suggest current TWRP version 3.1.1-0). This is due to the fact that firmware over-wrote TWRP with stock recovery.
Most of the "ROMs" you were trying to flash before were RUUs, not TWRP-flashable ROMs. So hopefully, you won't have any issue flashing ROMs now.

redpoint73 said:
Any of the ROMs from the M8 development section should work. You will need to unlock the bootloader again, and flash TWRP to the device again (suggest current TWRP version 3.1.1-0). This is due to the fact that firmware over-wrote TWRP with stock recovery.
Most of the "ROMs" you were trying to flash before were RUUs, not TWRP-flashable ROMs. So hopefully, you won't have any issue flashing ROMs now.
Click to expand...
Click to collapse
********************************************
im confused, can u give me direct link for best roms please ; i dont wont to brake it again !!
wanna use dual cam and htc sense
thanks to all XDA's staff ; you're the BEST

morphus3x said:
********************************************
im confused, can u give me direct link for best roms please ; i dont wont to brake it again !!
wanna use dual cam and htc sense
Click to expand...
Click to collapse
I don't personally do "best ROM" recommendations for 2 main reasons:
1) There is no such thing as a "best ROM" for everyone. Each user has drastically different preferences and usage patterns. What is "best" for me, may not even be any good for you. You need to decide for yourself what is "best". If you want some ROM suggestions, there are plenty (IMO, too many) of existing threads with such discussions.
2) The notion of a "best ROM(s)" is insulting to the developers, most of whom do all this work for no compensation. If everyone kept recommending the "best" ROM(s), what point would there ever be for devs to introduce new ROMs or ideas? The variety/choice in ROMs is a good thing. Don't rob yourself of the potential "hidden gems" by being a sheep and doing what everyone else does, or just doing what a stranger tells you is "best".
You won't do anything to the phone by flashing ROMs, that isn't recoverable. We all occasionally run into bad ROM flashes, no boot situations, and other bugs. It's just part of the game. If you flash ROMs, root, or otherwise mod these phones; you have to live with the fact that sometimes things go wrong, and you have to know how to recover from those things.
If you stick with the M8 development section, and look for Sense ROMs, you will find what you seek. Don't flash any RUUs or firmware, unless you know what you are doing.
https://forum.xda-developers.com/htc-one-m8/development

thanks again, i'll tray this ont SkyDragon M8 v 9.0 Sense 7
skydragon creations are smooth and i like to use it ; not booting fast but propose all i want

Which RUU can i flash?

So, I had a marshmallow update on my phone, and later i converted into GPE, but didn't like it. Went back to Sense, but it just doesn't feel as good as before. One day, the battery died, and when i tried turning it on, it would give me all sorts of errors. This never happened while i was on marshmallow before conversion to GPE. Had to reset it from the recovery. I think it hasn't returned to Sense properly.
As i am S-Off, i was thinking of flashing it with a RUU which is compatible with my device. Please suggest me which is compatible.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.21450002
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.16.708.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: -------------------
(bootloader) imei: --------------------
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B63000
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.090s

Based on your MID, looks like you're on a GSM M8? I'd go to HTC Dev and download their stock ROM, or go the appropriate carrier sub section for the M8 and use an RUU there.

I have read here that flashing carrier RUU can brick the device radio for good. So, this is why I wanted to confirm.

cytherian said:
I'd go to HTC Dev and download their stock ROM, or go the appropriate carrier sub section for the M8 and use an RUU there.
Click to expand...
Click to collapse
HTC does not post the RUU for his version on HTC Dev.com (many versions are not posted there)
OP's version doesn't have a carrier forum sub-section.
---------- Post added at 09:38 AM ---------- Previous post was at 09:36 AM ----------
xexux said:
(bootloader) version-main: 6.16.708.1
Click to expand...
Click to collapse
I don't know if there is an RUU for this version number.
One alternative, is to restore the TWRP backup 6.16.708.1 from here: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
---------- Post added at 09:42 AM ---------- Previous post was at 09:38 AM ----------
xexux said:
Went back to Sense, but it just doesn't feel as good as before.
I think it hasn't returned to Sense properly.
Click to expand...
Click to collapse
How exactly did you go back to Sense?

I tried the guide here, but I just couldn't complete it, as i received some modelid error. Tried multiple times to no avail. So, i tried the TWRP nandroid method, and restored to Sense that way.

xexux said:
I tried the guide here, but I just couldn't complete it, as i received some modelid error. Tried multiple times to no avail. So, i tried the TWRP nandroid method, and restored to Sense that way.
Click to expand...
Click to collapse
Good to hear that it worked out and thanks for posting. :good:

cytherian said:
Good to hear that it worked out and thanks for posting. :good:
Click to expand...
Click to collapse
This is how I got Sense back, and after that, I started experiencing bugs with M8 as explained in my first post.

xexux said:
So, i tried the TWRP nandroid method, and restored to Sense that way.
Click to expand...
Click to collapse
Which TWRP backup did you restore? Did you flash firmware, or only restore the TWRP backup?

redpoint73 said:
Which TWRP backup did you restore? Did you flash firmware, or only restore the TWRP backup?
Click to expand...
Click to collapse
I restored it with the latest TWRP backup for my model. About firmware, I am not sure, but i do see that firmware version in 'fastboot var all' data.
Since I am S-off, is there any Marshmallow RUU which i can try without bricking anything? May be a developer version or RUU for european/asian variant? Or the ones linked at gsmhosting M8 page? I have read people experiencing LTE radio problem with that. I hope that's not the case anymore, and there is a work around.

xexux said:
I restored it with the latest TWRP backup for my model.
Click to expand...
Click to collapse
What version number exactly? Perhaps you still have the files on your computer, and can look?
I've seen a number of times, folks say and think they restored the right version for their model, and once we ask for version numbers, we see they actually got it wrong.
xexux said:
About firmware, I am not sure, but i do see that firmware version in 'fastboot var all' data.
Click to expand...
Click to collapse
I can see it too. But doyou actually remember manually download and flash the firmware in RUU mode?
Did you convert to GPE using the RUU?
xexux said:
Since I am S-off, is there any Marshmallow RUU which i can try without bricking anything? May be a developer version or RUU for european/asian variant? Or the ones linked at gsmhosting M8 page? I have read people experiencing LTE radio problem with that. I hope that's not the case anymore, and there is a work around.
Click to expand...
Click to collapse
It's possible. But flashing another region's RUU will also change the radio baseband, and therefore changes the specific bands supported. It may have undesirable results (not support the 3G or LTE band or bands used by your local carrier).

My htc one m8 has no os due to an unsuccessful update, I have s-on, boot loader unlocked and not fully rooted. I have twrp as recovery. What are my options to get the official ruu to flash

Bukss said:
My htc one m8 has no os due to an unsuccessful update, I have s-on, boot loader unlocked and not fully rooted. I have twrp as recovery. What are my options to get the official ruu to flash
Click to expand...
Click to collapse
First of all, the phone won't update with TWRP installed (need stock recovery) so that is one reason for the update to fail.
Also, if the ROM is not stock (such as custom ROM, root) in any way, it needs to be returned to stock in order to update. I don't know what "not fully rooted" means. But if it was rooted, you need to re-install the stock ROM (such as stock TWRP backup) as most other "unroot" methods do not work (update will still fail).
RUU will update the phone, and bypasses the above requirements. But we would need to know more about the phone to know if your version M8 has an RUU. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).

redpoint73 said:
First of all, the phone won't update with TWRP installed (need stock recovery) so that is one reason for the update to fail.
Also, if the ROM is not stock (such as custom ROM, root) in any way, it needs to be returned to stock in order to update. I don't know what "not fully rooted" means. But if it was rooted, you need to re-install the stock ROM (such as stock TWRP backup) as most other "unroot" methods do not work (update will still fail).
RUU will update the phone, and bypasses the above requirements. But we would need to know more about the phone to know if your version M8 has an RUU. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
Hello guys. I took my M8 to someone to repair and they completely messed up the phone. Now no matter how you try to boot up the phone, a black screen with a silver HTC logo in the middle and 4 silver triangles in the corner shows up. I cannot reboot into bootloader, it brings me back to the same screen. Here is a getvar of my htc one m8, i was wondering if you could point me to the right RUU to use.
c:\miniadb_m7>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.23.213311491.A13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.07.1700.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid: 99000499834418
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(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: RUU
(bootloader) commitno-bootloader: 11459804
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.036s

Abnova said:
Hello guys. I took my M8 to someone to repair and they completely messed up the phone. Now no matter how you try to boot up the phone, a black screen with a silver HTC logo in the middle and 4 silver triangles in the corner shows up. I cannot reboot into bootloader, it brings me back to the same screen. Here is a getvar of my htc one m8, i was wondering if you could point me to the right RUU to use.
(bootloader) version-main: 5.07.1700.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m8_wlv
(bootloader) modelid: 0P6B12000
Click to expand...
Click to collapse
Wow, this is quite a mess!
Was this a repair shop, or just some person you knew that tried to "fix" the phone. Either way, it is probably apparent that they shouldn't be trusted, and don't seem too knowledgeable (at least with this specific device).
Although there are a few details I'm not clear on, and you should clarify:
1) If you can't get to bootloader, how did you do fastboot getvar all?
2) What exactly was wrong with the phone that the shop/person tried to "fix" for you (and the specific condition before you gave it to them)? Was it able to boot to OS? Something else wrong (no SIM, etc.)?
What is clear, is that your device is the US Verizon version M8 (as shown by the product ID m8_wlv). But at some point (not completely clear if it was the repair person, or before that) it had its MID changed to that of the US Developer's Edition (0P6B12000). And had the Google Play Edition (GPE) firmware and/or RUU installed.
Those last two things (changing to Dev Ed MID, and running GPE RUU/firmware) are a very bad idea on the Verizon version M8. Reason being, the Verizon M8 is peculiar, and can only run firmware/RUU intended for the Verizon variant M8 (so Verizon RUU or firmware). Installing any other RUU/firmware will result in a radio brick, possibly permanent. And is probably also the reason the phone won't boot to OS now. It may be fixable. But first, I'd like more information (items above) on the history of the phone, and exactly what was done to it before the repair person worked their "magic" (as much as you know).

redpoint73 said:
Wow, this is quite a mess!
Was this a repair shop, or just some person you knew that tried to "fix" the phone. Either way, it is probably apparent that they shouldn't be trusted, and don't seem too knowledgeable (at least with this specific device).
Although there are a few details I'm not clear on, and you should clarify:
1) If you can't get to bootloader, how did you do fastboot getvar all?
2) What exactly was wrong with the phone that the shop/person tried to "fix" for you (and the specific condition before you gave it to them)? Was it able to boot to OS? Something else wrong (no SIM, etc.)?
What is clear, is that your device is the US Verizon version M8 (as shown by the product ID m8_wlv). But at some point (not completely clear if it was the repair person, or before that) it had its MID changed to that of the US Developer's Edition (0P6B12000). And had the Google Play Edition (GPE) firmware and/or RUU installed.
Those last two things (changing to Dev Ed MID, and running GPE RUU/firmware) are a very bad idea on the Verizon version M8. Reason being, the Verizon M8 is peculiar, and can only run firmware/RUU intended for the Verizon variant M8 (so Verizon RUU or firmware). Installing any other RUU/firmware will result in a radio brick, possibly permanent. And is probably also the reason the phone won't boot to OS now. It may be fixable. But first, I'd like more information (items above) on the history of the phone, and exactly what was done to it before the repair person worked their "magic" (as much as you know).
Click to expand...
Click to collapse
Yeah I realised how big of a mess I was in when I got it back. Anyway
1.)On further investigation it seems like the the phone is in a wierd RUU mode. So it still can interface with the laptop through fastboot. Like I said earlier, trying to reboot to bootloader brings you to the same black screen with the silver Logo (see attached). When the phone is plugged in to the laptop or switches to the HTC silver Logo screen however when it's unplugged, it goes to a wierd bootloader like screen but black and only has the option for RUU. ( See attached)
2.) I took it to them to replace the battery because . The phone would switch off even at 100% battery. It only worked when it stayed plugged in , like a PC. I'm guessing the repair guys saw I had modified the software (I was running Dirty Unicorns, Android 7.1.2, Latest TWRP with a relocked Bootloader, S-Off) and had thought the problem actually had to do with the software. I live in Kenya and the HTC model available here is the international Gsm model so im guessing it seemed reasonable for them to RUU the Google play edition to try to bring it to a stable, stock, state. It most likely previously worked on the other M8's brought to them. I doubt they realized that I had imported the phone from the US, so they were probably shocked when it failed.
Anyway I hope this information helps. Thanks for your help.

Abnova said:
I live in Kenya and the HTC model available here is the international Gsm model so im guessing it seemed reasonable for them to RUU the Google play edition to try to bring it to a stable, stock, state. It most likely previously worked on the other M8's brought to them. I doubt they realized that I had imported the phone from the US, so they were probably shocked when it failed.
Click to expand...
Click to collapse
"Because it worked before" is not a good philosophy when working with these devices. Different models have their own nuances, for any smartphone. Any repair shop should be smart enough to know that different models/versions of the same phone can have major differences. And assuming otherwise can have catastrophic results!
Abnova said:
1.)On further investigation it seems like the the phone is in a wierd RUU mode.
Click to expand...
Click to collapse
Not a bad thing, if it is in fact RUU mode. You can try the Verizon RUUs. As mentioned, these are the only RUUs you should try on your device!
https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
You will likely need to change back to the Verizon MID to run those RUUs. Otherwise the RUU will fail with wrong MID.
https://forum.xda-developers.com/showthread.php?t=2708581
If the phone boots to OS, but with no SIM or no signal, the repair shop flashing the wrong RUU may have bricked the radio. You can try to flash an older (Kitkat) Verizon RUU, which sometimes will fix the problem. If it does fix the radio, then you can update up to something more recent (Marshmallow).
Of course, I don't know if any of this will help your original problem of the phone shutting off when not on charger. If it is a software problem, then the original factory image (Verizon RUU) has the best chance of fixing it!

Thanks for your contribution, will definitely try tomorrow

redpoint73 said:
"Because it worked before" is not a good philosophy when working with these devices. Different models have their own nuances, for any smartphone. Any repair shop should be smart enough to know that different models/versions of the same phone can have major differences. And assuming otherwise can have catastrophic results!
Not a bad thing, if it is in fact RUU mode. You can try the Verizon RUUs. As mentioned, these are the only RUUs you should try on your device!
https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
You will likely need to change back to the Verizon MID to run those RUUs. Otherwise the RUU will fail with wrong MID.
https://forum.xda-developers.com/showthread.php?t=2708581
If the phone boots to OS, but with no SIM or no signal, the repair shop flashing the wrong RUU may have bricked the radio. You can try to flash an older (Kitkat) Verizon RUU, which sometimes will fix the problem. If it does fix the radio, then you can update up to something more recent (Marshmallow).
Of course, I don't know if any of this will help your original problem of the phone shutting off when not on charger. If it is a software problem, then the original factory image (Verizon RUU) has the best chance of fixing it!
Click to expand...
Click to collapse
I'm having trouble changing the MID Because adb is not working. However, fastboot is. So I've been stuck and I don't know what to do

Abnova said:
I'm having trouble changing the MID Because adb is not working. However, fastboot is. So I've been stuck and I don't know what to do
Click to expand...
Click to collapse
Ah, yes. Good point. You need adb to change the MID.
Try booting TWRP custom recovery, which should give you adb access.
Download TWRP (I suggest the latest, version 3.2.1-0). Put it in the same folder as fastboot.exe
Then do command: fastboot boot twrp.img
Where "twrp.img" has to match the exact file name of what you downloaded (you can change the name of the file to twrp.img or else type the whole/exact file name as downloaded).
Hopefully, you will see TWRP boot on the phone. Once it does, you should have adb access.
I also believe you should be able to run root (su) commands in TWRP (which is necessary to change MID). But I don't remember if there is an extra step of not to that.
Basically, the repair shop really screwed you by changing the MID and flashing the wrong RUU. Extra steps/tricks to do now, but hopefully we can get some progress anyway.

redpoint73 said:
Ah, yes. Good point. You need adb to change the MID.
Try booting TWRP custom recovery, which should give you adb access.
Download TWRP (I suggest the latest, version 3.2.1-0). Put it in the same folder as fastboot.exe
Then do command: fastboot boot twrp.img
Where "twrp.img" has to match the exact file name of what you downloaded (you can change the name of the file to twrp.img or else type the whole/exact file name as downloaded).
Hopefully, you will see TWRP boot on the phone. Once it does, you should have adb access.
I also believe you should be able to run root (su) commands in TWRP (which is necessary to change MID). But I don't remember if there is an extra step of not to that.
Basically, the repair shop really screwed you by changing the MID and flashing the wrong RUU. Extra steps/tricks to do now, but hopefully we can get some progress anyway.
Click to expand...
Click to collapse
I tried that, it would flash then refuse to reboot to the recovery. I've tried so many things but none of them worked. My only hope is if someone edited the Android.txt file inside the Rom Zip so that the model ID is the same as that of my corrupt phone. That way it'll flash and hopefully fix it. I've tried myself but everytime I tried to edit it says the zip/archive is corrupt on WinRAR. I don't know whether it's a problem with my laptop or if it's a complication related to the rom.zip. I've downloaded it again but it still does the same thing. So basically I'm stuck because there is no way I can change the MID. This probably means the phone is bricked.

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:

htc one m8 no sim/ network mode after Ruu install

hi all
the mother in law gave me her broken htc one m8 phone too look at as it was stuck on the htc boot screen.
after abit of searching around i got the phone into bootloader and managed to get the phone back up and running after following the below page to get it working again well mostly.
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860.
the problem i am now having is that the phone wont let me choose a network mode as its blanked off and not able to choose, which also means when i enter a sim it just doesnt work.
i have done a fastboot getvar all and details follow
(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__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
any help would be greatfully appreciated

First of all, you posted in the General M8s section. The M8s is a variant with different hardware. You have the M8 (no "s") which has it's own General forum section, but you should post questions like this in the M8 Q&A section, anyway. Don't make another post, I'll ask the mods to move this one to the right place.
s84taylo41984 said:
after abit of searching around i got the phone into bootloader and managed to get the phone back up and running after following the below page to get it working again well mostly.
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860.
Click to expand...
Click to collapse
Those are not RUU (as your thread title states). An RUU is an official HTC tool, which is run from bootloader. What you linked are stock TWRP backups, which are flashed using TWRP.
Which TWRP backup version number did you flash? What version TWRP did you use?
---------- Post added at 01:02 PM ---------- Previous post was at 12:59 PM ----------
s84taylo41984 said:
(bootloader) imei:
Click to expand...
Click to collapse
Is there an IMEI number listed? I know it's the right thing to leave this out, when posting online. But just want to make sure that is the case (and it is not actually missing from the getvar output as you see it). I don't want or need to know the IMEI number, just whether you can actually see it or not.

I realised i posted in the wrong section about 1 hour ago when i was looking through some other posts on here and noticed there was a differnce in the m8 and m8s.
yes IMEI is there. i just blanked it off when posting

Quote:
Originally Posted by s84taylo41984
after abit of searching around i got the phone into bootloader and managed to get the phone back up and running after following the below page to get it working again well mostly.
https://forum.xda-developers.com/htc...-twrp-t3086860.
Those are not RUU (as your thread title states). An RUU is an official HTC tool, which is run from bootloader. What you linked are stock TWRP backups, which are flashed using TWRP.
Click to expand...
Click to collapse
Oh i thought that they all worked the same, didnt realise they was so different!
Which TWRP backup version number did you flash? What version TWRP did you use?
Click to expand...
Click to collapse
I used TWRP 3.3.1-0 amd followed the whole of that guide, i thought it was RUU not stock.

s84taylo41984 said:
after abit of searching around i got the phone into bootloader and managed to get the phone back up and running after following the below page to get it working again well mostly.
Click to expand...
Click to collapse
What does that mean "mostly" working?
Seems you are going about this a bit haphazardly. You didn't answer all my questions, but instead decided to search around for you own solutions (we may have gotten you there faster).

redpoint73 said:
What does that mean "mostly" working?
Seems you are going about this a bit haphazardly. You didn't answer all my questions, but instead decided to search around for you own solutions (we may have gotten you there faster).
Click to expand...
Click to collapse
Mostly working as in i wasnt able to get the wifi to enable on the phone until i flashed the TWRP Backup collection in 3, and then flashed the stock recovery image's from post 4 and the signed firmware in post 5 all with the 6.12.401.4 and CID HTC__001
MID 0P6B10000

s84taylo41984 said:
Mostly working as in i wasnt able to get the wifi to enable on the phone until i flashed the TWRP Backup collection in 3, and then flashed the stock recovery image's from post 4 and the signed firmware in post 5 all with the 6.12.401.4 and CID HTC__001
MID 0P6B10000
Click to expand...
Click to collapse
WiFi not turning on is due to restoring the wrong stock TWRP backup which does not correspond to the installed firmware. As I mentioned, this is something we could have identified much earlier, if you supplied the requested info (questions I asked days ago).

what questions did you want me to answer to answer days ago??
is there anything that can be done for me to get the phone working again???

s84taylo41984 said:
what questions did you want me to answer to answer days ago??
Click to expand...
Click to collapse
redpoint73 said:
Which TWRP backup version number did you flash?
Click to expand...
Click to collapse
s84taylo41984 said:
is there anything that can be done for me to get the phone working again???
Click to expand...
Click to collapse
Not clear to me what doesn't work now. You already said the WiFi was fixed once you flashed the signed firmware.

redpoint73 said:
Not clear to me what doesn't work now. You already said the WiFi was fixed once you flashed the signed firmware.
Click to expand...
Click to collapse
Yes the WIFI started working after flashing the signed firmware but as posted in my original post, i am unable to select network mode to choose a network even with a sim card inserted it just says no sim card, emergency calls only!
The TWRP backup version i flashed was 6.12.401.4

s84taylo41984 said:
Yes the WIFI started working after flashing the signed firmware but as posted in my original post, i am unable to select network mode to choose a network even with a sim card inserted it just says no sim card, emergency calls only!
Click to expand...
Click to collapse
Not sure I necessarily have an answer for you. But at least so if I understand the sequence of events correctly:
1) You received the phone in "no boot" condition.
2) (Unlocked bootloader?). Restored stock TWRP backup 6.12.401.4 using TWRP 3.3.1-0.
3) Able to boot the phone, but no SIM and no WiFi.
4) (Relocked bootloader presumably). Flashed firmware 6.12.401.4. Also flashed stock recovery.
5) WiFi is not working, still no SIM.

redpoint73 said:
Not sure I necessarily have an answer for you. But at least so if I understand the sequence of events correctly:
1) You received the phone in "no boot" condition.
2) (Unlocked bootloader?). Restored stock TWRP backup 6.12.401.4 using TWRP 3.3.1-0.
3) Able to boot the phone, but no SIM and no WiFi.
4) (Relocked bootloader presumably). Flashed firmware 6.12.401.4. Also flashed stock recovery.
5) WiFi is not working, still no SIM.
Click to expand...
Click to collapse
i never unlocked the bootloader just booted the phone into bootloader
the WiFi is working, just no SIM

s84taylo41984 said:
i never unlocked the bootloader just booted the phone into bootloader
Click to expand...
Click to collapse
Was the phone already bootloader unlocked when you received it? Does it say LOCKED, UNLOCKED, or RELOCKED near the top of the bootloader screen?
You can't install TWRP with a locked bootloader (while s-on).

It says RELOCKED now when i put the phone in to bootloader. I have no idea if the bootloader was unlocked when i recieved the phone i cant remember

s84taylo41984 said:
It says RELOCKED now when i put the phone in to bootloader. I have no idea if the bootloader was unlocked when i recieved the phone i cant remember
Click to expand...
Click to collapse
The only way it could have been bootloader unlocked when you got the device, and relocked after, is if you relocked it yourself, with fastboot command: fastboot oem lock
Did your mother-in-law or someone she know, mod the phone? Or did she obtain it used or from a 3rd party vendor? If it was RELOCKED when you received it, it was definitely modded by someone at some point.
The only way the bootloader can be locked (or relocked) and you can still flash TWRP, is if the device is s-off, but has the security flag spoofed to say it is s-on.

redpoint73 said:
The only way it could have been bootloader unlocked when you got the device, and relocked after, is if you relocked it yourself, with fastboot command: fastboot oem lock
Did your mother-in-law or someone she know, mod the phone? Or did she obtain it used or from a 3rd party vendor? If it was RELOCKED when you received it, it was definitely modded by someone at some point.
The only way the bootloader can be locked (or relocked) and you can still flash TWRP, is if the device is s-off, but has the security flag spoofed to say it is s-on.
Click to expand...
Click to collapse
I did relock it using the fastboot oem lock command.
She did have somebody look at it before me and it was the same thing.