Develop Bugs

wi-fi not working on M8

Hello,
I want to buy a second hand HTC M8 and it has a issue with wi-fi.. it won't turn on or connect to wi-fi. from the screen shots i see that it has network (3g network). the guy selling the m8 says that a friend of his tried to put a custom rom on the phone and after that the wifi stopped working. here are the printscreens send by him. could you tell me if i can repair it myself or it is the wi-fi chip damaged.

Wifi doesn't work because the ROM is 4.4.4 but device is still 4.4.2
(can see this from the baseband version)
You can easily fix this by put in correct ROM version

can it be done without s-off? with a ruu.exe?

This s the bootloader

cabasse_tronic said:
can it be done without s-off? with a ruu.exe?
Click to expand...
Click to collapse
No need S-Off.
Get info on fastboot getvar all for this device then we will know whether to use RUU or stock backup

i'll buy it tonight and after that we'll be talking here hope for the best. thanks guys.

cabasse_tronic said:
i'll buy it tonight and after that we'll be talking here hope for the best. thanks guys.
Click to expand...
Click to collapse
You better remove the 3rd pic where it shows the IMEI no. & Serial No. Those are sensitive data.
Anyway ... checked your IMEI, it is a EU version, so there is a RUU available which you can directly update it to the latest Lollipop version 4.16.401.10

thanks. will remove those pictures. i will but it tonight.

Is it for a good price due to WiFi not working? If so, the devil on my right shoulder says it serves them right for modding the phone without doing the proper research! Or researching properly to (easily) fix the problem, for that matter.

the price is ok. my old htc m7 + 100 euro

C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.00
(bootloader) version-baseband: 1.15.213315
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH4xxxxxxxxxxxxx
(bootloader) imei: 35xxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAP001
(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.053s
Help me to get it stock please !!

Remove serial no. in your post
I'll write simple guide on how to get back on stock and update to the latest lollipop when I'm home in next 3 - 4 hrs (if no one attend to this yet)

i see that the phone has Vodap001 CID but the soft on it (rooted one) is for the HTC_00x CID.. problem? i have got a stock backup, unzipped it, putted in TWRP backup folder, now i restore it and after that flash the stock recovery?? is that all?

It's a Vodafone UK M8, but still easy restored to stock
To be honest, I'd get it back to 1.54.161.x using the backups @ckpv5 will post, S-OFF with Sunshine and then convert it to the unbranded handset using the 4.16.401.10 RUU (using the guide in my signature)

skirmish please .. one m7 i could do it with no problem but this guy kills me

Can't write proper guide as I'm driving....
Follow this guide : http://forum.xda-developers.com/showpost.php?p=59034701&postcount=4
But don't use that 3.29.161.9, you need to restore 1.54.161.10 and its recovery then proceed multiple OTA up to lollipop 4.19.161.2
You can get the needed files here : http://forum.xda-developers.com/showpost.php?p=58606328&postcount=4278
Note : if you have plan to S-Off your device, do it after restore 1.54.161.10
if you want to keep it S-On, just proceed OTA. Later you can install any custom lollipop ROM if you want to

fastboot flash recovery open. img ... stuck on entering recovery.. sweet as hell

cabasse_tronic said:
fastboot flash recovery open. img ... stuck on entering recovery.. sweet as hell
Click to expand...
Click to collapse
Don't use version 2.8.4.0 or 2.8.5.0
Try 2.8.1.0

ckpv5 said:
Don't use version 2.8.4.0 or 2.8.5.0
Try 2.8.1.0
Click to expand...
Click to collapse
You are my guardian angel.. another one ) unrar the backup like in that short tutorial, putted in the backup folder.. twrp doen't see it.. can't restore..

cabasse_tronic said:
Hello,
I want to buy a second hand HTC M8 and it has a issue with wi-fi.. it won't turn on or connect to wi-fi. from the screen shots i see that it has network (3g network). the guy selling the m8 says that a friend of his tried to put a custom rom on the phone and after that the wifi stopped working. here are the printscreens send by him. could you tell me if i can repair it myself or it is the wi-fi chip damaged.
Click to expand...
Click to collapse
you could follow my guide on the viperone thread , steps 1 to 6 would get you onto stock android lollipop with a stock recovery , just do a full setup at step 6 , my guide proceeds past this point to then install a custom recovery and a custom rom but if you stop at step 6 after setting up the phone you will be unbranded stock
hope this helps
http://forum.xda-developers.com/showpost.php?p=59055916&postcount=20651

Various problems.!

Forget this sorted it all out, now running SRom ported lollipop with sense 7 from the M9. Hboot no red text and faux locked/original/son. Super CID.
For the record, it's always a firmware/dalvic cache problem (98%)
Hi Guys so Im rooted running Android Revoluton HD ROMs on an international O2 phone S-on
I thought I would wipe the entire phone, bleach it like a PC and reinstall.
Not a problem except various elements dont work.
I installed Stock ROM (I think KitKat)
I installed ARHD 22. (Kit Kat) everything worked
I installed ARHD 34.(Jellybean Sense 6) no wifi
I installed ARDH 40.(Jellybean Sense 7) no HTC TV
I installed ARHD 41.(Jellybean Sense7) no images in Blinkfeed?
I know its probably because I wiped the misc folder but up until I did a clean wipe I could use all of these roms without a glitch.
So is it firmware?
What do I need to put back on my phone for them all to work
I am S-on at the moment and I know that isnt whats stopping these roms working.
Any suggestions?

eskimosound said:
Hi Guys so Im rooted running Android Revoluton HD ROMs on an international O2 phone S-on
I thought I would wipe the entire phone, bleach it like a PC and reinstall.
Not a problem except various elements dont work.
I installed Stock ROM (I think KitKat)
I installed ARHD 22. (Kit Kat) everything worked
I installed ARHD 34.(Jellybean Sense 6) no wifi
I installed ARDH 40.(Jellybean Sense 7) no HTC TV
I installed ARHD 41.(Jellybean Sense7) no images in Blinkfeed?
I know its probably because I wiped the misc folder but up until I did a clean wipe I could use all of these roms without a glitch.
So is it firmware?
What do I need to put back on my phone for them all to work
I am S-on at the moment and I know that isnt whats stopping these roms working.
Any suggestions?
Click to expand...
Click to collapse
It's firmware. You most probably have kitkat firmware and lolipop based roms will mess up your wifi and stuff. Take an ota or stay on kitkat.

Thanks will try
Do I just flash the zip file?
Im sure I probs do

eskimosound said:
Thanks will try
Do I just flash the zip file?
Im sure I probs do
Click to expand...
Click to collapse
If you are S-ON don't flash firmware. Just don't. You can flash rom zips, recoveries, kernels. You can write on these partitions with s-on: recovery, boot, system and data.

I've just used Sunshine to get S-off, what a joy to use!
So now I can just flash them right?
I've got my cid number matched it up with the ota and bingo?
Right?

eskimosound said:
I've just used Sunshine to get S-off, what a joy to use!
So now I can just flash them right?
I've got my cid number matched it up with the ota and bingo?
Right?
Click to expand...
Click to collapse
well im come from HTC One M7, and as long as the M8 is pretty much the same, you dont need s-off to flash the same firmware which your already on, or the next one step up, after all, this is exactly what an OTA does for you.
However, now your s-off anyway, you canflash any RUU or firmware you like, just make sure cid and mid match first. :good:
EDIT: there ia also no need to lock or re-lock the bootloader to flash anything now that your S-off, leave it unlocked all the time for everything, its a common problem on the M7 forums at the moment, people who are s-off or even s-on, locking bootloaders with custom rom's or recovery's on thier phones.

Thanks, so with the ota there are two for O2 my cid is O2___001 am I right that I can take the 001 OR the 002?

eskimosound said:
Thanks, so with the ota there are two for O2 my cid is O2___001 am I right that I can take the 001 OR the 002?
Click to expand...
Click to collapse
in all honesty, I would of thought the CID 001 and 002 were in the same ota, have you checked the android-info.txt file within the OTA itself, its just a zip file.
possible to post your fastboot getvar all without imei and serial number please, also a link to the OTA's your downloading would be good.

Well I've just tried to flash both....I enter recovery instal zip right?
It's giving me an error.
Will tell you that info in a minute when I get on my pc

eskimosound said:
Well I've just tried to flash both....I enter recovery instal zip right?
It's giving me an error.
Will tell you that info in a minute when I get on my pc
Click to expand...
Click to collapse
personnaly, if your just trying to get to Lollipop, I would change my CID to HTC__001 (thats 2 underscores, CID is always 8 digits)
Change MID if required.
and then flash the WWE International Lollipop full RUU, piece of cake. http://forum.xda-developers.com/htc-one-m8/general/htc-one-m8-european-signed-ruu-0p6bimg-t2911563

But if the original isn't flashing what hope have I got with an HTC one. It's interesting to know though that I can change it.
So what next?
Oh hang on I will post my stats

OK Guys,
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.206.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: 0P6B10000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dcdaa6e0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.028s

eskimosound said:
But if the original isn't flashing what hope have I got with an HTC one. It's interesting to know though that I can change it.
So what next?
Oh hang on I will post my stats
Click to expand...
Click to collapse
Flashing an OTA manually is a different kettle of fish, its just an OTA not a full RUU, and you would still have to be full stock in order for it to succeed.
however, if you just require the firmware in order to use a custom LP rom, then just pull the firmware.zip out of the OTA and flash it.
you would then have to put a custom recovery back on your phone, copy a rom to your sdcard, and flash it from within TWRP recovery.

And im trying to flash O2 OTA
for here
http://forum.xda-developers.com/showthread.php?t=2701376

eskimosound said:
OK Guys,
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.206.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: 0P6B10000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dcdaa6e0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.028s
Click to expand...
Click to collapse
you already have the latest firmware on your phone !!!
I installed ARHD 41.( Sense7) no images in Blinkfeed? ------ pulled from your first post, this is a common problem, if you mean its face ache, there is a fix for it on playstore.

OK is tere an RUU for O2 uk?
So im extracting the firmware at the mo, then I will flash it then I will try and install ARHD 41....
Im right that the O2___002 is an upgraded version of the 001 and its what I need right?
Otherwise im just replacing like for like.

eskimosound said:
OK is tere an RUU for O2 uk?
So im extracting the firmware at the mo, then I will flash it then I will try and install ARHD 41....
Im right that the O2___002 is an upgraded version of the 001 and its what I need right?
Otherwise im just replacing like for like.
Click to expand...
Click to collapse
nope O2___002 is a different cid, you need to use the 001 files, however, its the same as you already have on your phone.
CID is just carrier ID, so O2___001 will be something like O2 UK and 002 might be something like O2 france, no difference in files, just different regions.

Seanie280672 said:
nope O2___002 is a different cid, you need to use the 001 files, however, its the same as you already have on your phone.
Click to expand...
Click to collapse
So if its the same and ive got a problem its not the firmware right?
Or is it just an update.
I will tell you this is really easy but telling people how to do it is confusing

eskimosound said:
So if its the same and ive got a problem its not the firmware right?
Or is it just an update.
I will tell you this is really easy but telling people how to do it is confusing
Click to expand...
Click to collapse
nope its not your firmware, just checked a cid list, 002 is O2 DE, 001 is O2 UK http://forum.gsmhosting.com/vbb/f485/archive-htc-cid-list-1604812/
Make sure of a couple of things when flashing a custom ROM, check for problems other are having with it, by reading some of the later posts is what I always do, just a few pages, also and this is a must, read the OP's flashing instructions, so many people bypass this step, the most important step is to make sure your using the dev's recommended custom recovery for flashing.
I always full wipe before flashing anything, so in TWRP first factory reset, and then goto wipe - advanced - select everything except your internal storage and SDcard, and then always reboot back into recovery after the wipes before flashing the rom, it will nag you and say you have no OS installed, ignore it and Do Not Intall to SuperSU, the custom rom flash will do that for you.
During the rom installation, again I always select full wipe when given the option, you then know you have a clean slate to build the rom on.

eskimosound said:
So if its the same and ive got a problem its not the firmware right?
Or is it just an update.
I will tell you this is really easy but telling people how to do it is confusing
Click to expand...
Click to collapse
Your firmware is already current, and should work with latest ARHD. Blinkfeed not showing image is a known issue reported by others.
No need to mess with RUUs or firmware zips.

Unable to flash roms?

Hey there.
I'm fairly new-ish to the Android modification scene. I've had android phones for a while but only recently started rooting etc one my One M8. I've got the Bootloader Unlocked with S-Off and am also on just the stock rom (or I was as I'm in the middle of attempting to get custom roms. :L). My custom recovery is TWRP 2.8.7.0, the latest and the roms I have been trying to install so far are the latest SkyDragon v10 Sense 7 and ViperOne 4.6.0 roms.
In TWRP, when doing this, it will go through the custom installation setup stuff and afterwards it will go into a never ending bootloop for around an hour before I decide to hold volume up and power to switch it off.
Now, before I do the initial installation of the rom, I have wiped data, system, cache and the Dalvik. Regardless, it still causes a boot loop. I have switched the phone off and waited 30 seconds. Still a bootloop. I have gone back into recovery and re-wiped the cache and dalvik and still get this bootloop.
Another thing to note, I have a pending update which is to fix the something which I received at the end of August for the OTA thing and when I put stock recovery back onto the phone to try and do an OTA for that as well, I get the same issue. The only difference is that due to that being the official rom, it also has sound during the bootup but one thing to note (aside from it doing exactly the same and doing a bootloop), the boot animation sound is also delayed by 5 seconds or so, unlike before the update where it plays at the same time as the boot animation.
I am able to successfully restore my TWRP backup of my OS before it attempts something like this and was last working but that's as far as it goes.
I am at a complete loss as I am following any and all tutorials I can find online to the letter and yet I am still having no luck here.
Can anyone assist me on this? It would be much appreciated. Thank you in advance and for reading.

ThatOneJoshy said:
I am able to successfully restore my TWRP backup of my OS before it attempts something like this and was last working but that's as far as it goes.
Click to expand...
Click to collapse
That show your TWRP backup is not stock enough or it is a rooted stock and that is why the OTA failed.
You need a pure non-rooted backup or RUU to successfully update.
What's your device details ?
Run command fastboot getvar all and post here minus the serial & imei no.. maybe someone will be able to point you to right direction.

ckpv5 said:
That show your TWRP backup is not stock enough or it is a rooted stock and that is why the OTA failed.
You need a pure non-rooted backup or RUU to successfully update.
What's your device details ?
Run command fastboot getvar all and post here minus the serial & imei no.. maybe someone will be able to point you to right direction.
Click to expand...
Click to collapse
It's stock firmware that came on the phone, although it is rooted with SuperSU. Whenever I looked online, every forum board said that having a rooted phone wouldn't prevent an OTA, although having a custom recovery would so I would flash the stock recovery back onto the phone and do the update that way which would in turn create this boot loop.
My RUU is/ should be exactly the same as I haven't done anything to change it and also, the updates still come through and are downloaded that way. It also installs (so I think as it goes through the normal process of updating that my phone has always done showing an image of an updating phone with a loading bar at the bottom whilst rebooting a couple of times).
In terms of the details requested, I'm not sure if it will be affected by the rom I just tried installing again for ViperOneM8, but they can be found below:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.401.13
(bootloader) version-misc: PVT SHIP S-OFF
(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: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: f063fb42
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
The version I am on on the stock rom is 4.16.401.10. I'm not sure why that is showing, unless it's because of the ViperoneM8 mod I installed which also features the same patch released by HTC apparently.

Yeah, almost everyone say the same thing and those forum are correct for ROMs prior to lollipop.
On lollipop .. root works differently that is why you can't do update on a rooted lollipop stock ROM.
The only suggestion I have is keep your TWRP backup.
Restore a non-rooted 4.16.401.10 TWRP backup and its stock recovery and do the update. After the update, restore your saved data and re-root or install any ROM that you like.
I have one backup in my thread : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Read these thread on how people solved their same problem as yours
http://forum.xda-developers.com/htc-one-m8/help/os-sos-t3192177
http://forum.xda-developers.com/htc-one-m8/help/stuck-boot-ota-update-t3192441

Soft bricked with S-On

I have an HTC One M8 (International) and I don't remember how, since this happened long ago, but while flashing some ROM I somehow switched my phone back to S-On while the bootloader stayed 'Unlocked' but it showed the 'Tampered' sign.
After an year, my new phone isn't working and I needed to get my old phone back so I took it out and decided to wipe everything because I didn't care about the data inside it and I just wanted all the storage space. Unwittingly I checked every box in the 'Advanced' section of the factory reset menu, including the 'System' checkbox.
Now my phone has no OS, it has an unlocked bootloader with the latest TWRP installed (not completely sure about the latest part) but it shows 'Tampered' below the unlocked text and I've got 'S-On'. I had the Viper ROM on it before if that matters. It wont boot past the HTC screen which has the red text below it that tells us that the version of HTC is for developers.
I really need some help here, I'd greatly appreciate it.

R3dact said:
I have an HTC One M8 (International) and I don't remember how, since this happened long ago, but while flashing some ROM I somehow switched my phone back to S-On while the bootloader stayed 'Unlocked' but it showed the 'Tampered' sign.
After an year, my new phone isn't working and I needed to get my old phone back so I took it out and decided to wipe everything because I didn't care about the data inside it and I just wanted all the storage space. Unwittingly I checked every box in the 'Advanced' section of the factory reset menu, including the 'System' checkbox.
Now my phone has no OS, it has an unlocked bootloader with the latest TWRP installed (not completely sure about the latest part) but it shows 'Tampered' below the unlocked text and I've got 'S-On'. I had the Viper ROM on it before if that matters. It wont boot past the HTC screen which has the red text below it that tells us that the version of HTC is for developers.
I really need some help here, I'd greatly appreciate it.
Click to expand...
Click to collapse
Download a ROM on your PC and transfer it to an SD card, then flash it in recovery. Wiping everything in recovery doesn't wipe recovery, so you should still have TWRP on your phone.
To get there after you've inserted the SD card with the ROM to flash, power up your phone by holding power+vol down. That will boot you to bootloader. Use the vol keys to navigate to hboot and the power button to select it, and there will be an option to boot to recovery. Navigate to that, then flash the ROM.

xunholyx said:
Download a ROM on your PC and transfer it to an SD card, then flash it in recovery. Wiping everything in recovery doesn't wipe recovery, so you should still have TWRP on your phone.
To get there after you've inserted the SD card with the ROM to flash, power up your phone by holding power+vol down. That will boot you to bootloader. Use the vol keys to navigate to hboot and the power button to select it, and there will be an option to boot to recovery. Navigate to that, then flash the ROM.
Click to expand...
Click to collapse
I tried that, but it doesn't flash the ROM. Instead it starts flashing and then restarts back into TWRP midway. I tried flashing superuser the same way but to no avail.

You may have outdated firmware and outdated TWRP version. Most of current ROM won't get installed on outdated TWRP.
Post fastboot getvar all result without serial & imei no. We'll see what you need.

R3dact said:
I don't remember how, since this happened long ago, but while flashing some ROM I somehow switched my phone back to S-On
Click to expand...
Click to collapse
Are you sure it was ever s-off? S-off isn't need to flash ROMs, root, or a great many other things.
The only way you could have gotten s-off is with the sunshine app ($25); unless you did s-off with firewater before that method was disabled in Dec 2014.
R3dact said:
After an year, my new phone isn't working and I needed to get my old phone back so I took it out and decided to wipe everything because I didn't care about the data inside it and I just wanted all the storage space. Unwittingly I checked every box in the 'Advanced' section of the factory reset menu, including the 'System' checkbox.
Click to expand...
Click to collapse
There is rarely ever a reason to go into the Advanced section. But if you do, its called "Advanced" for a reason. You shouldn't be wiping any partitions on this device without understanding what it means, and what the results will be.
R3dact said:
Now my phone has no OS, it has an unlocked bootloader with the latest TWRP installed (not completely sure about the latest part)
Click to expand...
Click to collapse
If you haven't installed a new TWRP version in a year, there is no way its the "latest".
There is also no reason to guess at this. It says the TWRP version number right on the main screen of TWRP. You're always better of giving the specific number, instead of just saying latest. Folks on here often post they have the "latest" TWRP. But once prompted for the actual version number, I often find its something very old, often 2 years old!

R3dact said:
I have an HTC One M8 (International) and I don't remember how, since this happened long ago, but while flashing some ROM I somehow switched my phone back to S-On while the bootloader stayed 'Unlocked' but it showed the 'Tampered' sign.
After an year, my new phone isn't working and I needed to get my old phone back so I took it out and decided to wipe everything because I didn't care about the data inside it and I just wanted all the storage space. Unwittingly I checked every box in the 'Advanced' section of the factory reset menu, including the 'System' checkbox.
Now my phone has no OS, it has an unlocked bootloader with the latest TWRP installed (not completely sure about the latest part) but it shows 'Tampered' below the unlocked text and I've got 'S-On'. I had the Viper ROM on it before if that matters. It wont boot past the HTC screen which has the red text below it that tells us that the version of HTC is for developers.
I really need some help here, I'd greatly appreciate it.
Click to expand...
Click to collapse
Can you plz post fastboot getvar all here without the imei or serial#. We may be able to find you an RUU that may be able to recover your device.
Sent from my Nook HD using XDA Labs

ckpv5 said:
You may have outdated firmware and outdated TWRP version. Most of current ROM won't get installed on outdated TWRP.
Post fastboot getvar all result without serial & imei no. We'll see what you need.
Click to expand...
Click to collapse
===
my phone HTC ONE M8_WHL is just stuck on either bootloader or htc logo and it doesnot allow to flash anything, what ever i do i get one error "error: not allowed" kind of, plz help me
==============================================================
C:\ADB_new>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.651.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA457SF00649
(bootloader) imei: 990004991183470
(bootloader) imei2: Not Support
(bootloader) meid: 99000499118347
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.238s
==============================================================

smub said:
===
my phone HTC ONE M8_WHL is just stuck on either bootloader or htc logo and it doesnot allow to flash anything, what ever i do i get one error "error: not allowed" kind of, plz help me
==============================================================
C:\ADB_new>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.651.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA457SF00649
(bootloader) imei: 990004991183470
(bootloader) imei2: Not Support
(bootloader) meid: 99000499118347
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.238s
==============================================================
Click to expand...
Click to collapse
Jesus. 1.54.651.8 OS? That phone has never been updated since forever.
Go to this thread for instructions and links to update your device.
You want the ones that aren't "Harman"
EDIT: You are S-Off, so keep that in mind (security: off from your getvar)
Feel free to send me a PM if you need further instructions.

Help me salvage my HTC One M8

Hello
Long story short: I tried to flash a custom image on my phone, and screwed it up somehow. I have a guess what it is, but not how to fix it.
To be honest, this is more a matter of principal at this point, because the amount of work hours I've spent on this are worth more than a new HTC.
But before I admit defeat, I thought it would be worth while to attempt to ask for help.
HTC One M8, dual-sim, mec_dugl
I updated to the latest and greatest OTA using the official ROM. My Chinese has improved tremendously in the process.
I successfully installed TWRP (so skipping the obvious)
I did NOT switch S-OFF (this is where I think I screwed up)
I successfully (e.g - without errors) burned a variety of custom 'ROMs'
--> I can't boot to system. It always boots to BOOTLOADER. <--
I think that the phone doesn't boot to system because something got wiped out, but it's replacement failed to burn because of S-ON. This is just a guess. (in fact, if 'S' was worth a goddamn thing, this should not have happened, so I don't know)
So I tried to switch S-OFF.
However, I quickly realized that I can't do that, because I need to boot to system as root for the regular options to work.
I found a way to hack it using shell.
Tried to install SuperSU using TWRP. It failed to update something. I finally used UPDATE-SuperSU, which seemed to have worked.
adb shell --> doesn't recognize 'su'. All my attempts failed (I'm guessing it's the selinux stuff, even though I set it to permissive).
If you managed to read this whole sad story, and think you have an idea of something I could try, I would be grateful.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.30306251.15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.07.1402.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei: some number
(bootloader) imei2: another number, but it doesn't matter because the phone is dead
(bootloader) meid: 00000000000000
(bootloader) product: mec_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0PAJ20000
(bootloader) cidnum: HTCCN703
(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: 5c9466dd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Your device is not a htc one M8, it is htc one E8 also known as htc one M8Ace or M8SW
Here is the thread for your device - https://forum.xda-developers.com/one-e8
See if it is still active and anyone can help you.
Also you can google for 3.07.1402.2 RUU, mostly chinese site has RUU for it
Don't know whether 3.06.1402.2 can work on your device but the 3.06.1402.2 RUU is available here - https://easy-firmware.com/home/browse/category/id/1124/
Good luck

@ckpv5
Thanks! I overlooked that detail.
I was able to revert back to the china unicom system.
Now, before I do anything stupid again - is it possible to flash custom roms, even with S-ON ?
I'm mainly interested in a newer Android (7 if possible), and NO bloatware.
Can you give me some direction?

yaron-r said:
@ckpv5
Thanks! I overlooked that detail.
I was able to revert back to the china unicom system.
Now, before I do anything stupid again - is it possible to flash custom roms, even with S-ON ?
I'm mainly interested in a newer Android (7 if possible), and NO bloatware.
Can you give me some direction?
Click to expand...
Click to collapse
back in the old days we used to pull the boot.img out from the rom.zip and than when the recovery-flash been finished to flash the boot.img separately within the bootloader
Code:
fastboot flash boot boot.img
and that be all. sure to check into bootloader -> fastboot

Silversniper said:
back in the old days we used to pull the boot.img out from the rom.zip and than when the recovery-flash been finished to flash the boot.img separately within the bootloader
Code:
fastboot flash boot boot.img
and that be all. sure to check into bootloader -> fastboot
Click to expand...
Click to collapse
Thanks!
After reverting to a backup with the right rom, I installed S.Team rom, which supports E8.
It works great.
As a fallback, I understand what you are suggesting, and it makes sense. Thank you!

Silversniper said:
back in the old days we used to pull the boot.img out from the rom.zip and than when the recovery-flash been finished to flash the boot.img separately within the bootloader
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
It was never required on the M8 to do this; even with s-on. Only on older (before the M8) HTC devices. TWRP supported flashing boot.img from the beginning (release of the M8).

redpoint73 said:
back in the old days we used to pull the boot.img out from the rom.zip and than when the recovery-flash been finished to flash the boot.img separately within the bootloader
It was never required on the M8 to do this; even with s-on. Only on older (before the M8) HTC devices. TWRP supported flashing boot.img from the beginning (release of the M8).
Click to expand...
Click to collapse
It is at all an E8.
Some, at least feels like, still demand that. I had that on my first Rom, after secondary Flash it handled just as fine.
It goes indeed without flashing the boot.