Develop Bugs

H3G__001 stock lollipop nandroid

Hi im trying to update to lollipop on my 3 UK branded m8 but im having serious issues upgrading to 4.4.4 eye experience version 3.32.771.3 was wondering if anyone has or could get a nandroid of the stock 4.20.771.2 ROM. I can see an OTA in http://forum.xda-developers.com/showthread.php?t=2701376 but I have no idea how to use those OTA files. Any help would be appreciated.

Post your fastboot getvar all result (minus serial no. & imei no.)
then we know which backup that you really need.
No point to give you 4.20.771.2 backup for now.

ckpv5 said:
Post your fastboot getvar all result (minus serial no. & imei no.)
then we know which backup that you really need.
No point to give you 4.20.771.2 backup for now.
Click to expand...
Click to collapse
(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.771.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: H3G__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: dcdaa6e0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
hmmm it says OS version 4.20.771.2 there but in about phone --> software info. it says 2.22.771.5 for software number. not sure what that means?!

Try restore my backup and see how it goes : http://forum.xda-developers.com/showpost.php?p=58781201&postcount=4598

ckpv5 said:
Try restore my backup and see how it goes : http://forum.xda-developers.com/showpost.php?p=58781201&postcount=4598
Click to expand...
Click to collapse
cool thanks. I tried your nandroid backup and it starts up fine but I cant connect to my wifi network. It sees the network but it wont connect. It does allow me to connect to another open network I can see but not my own. This happened on one of the stock updates I did too. Any ideas why this might be? or how it might be fixed?

f_padia said:
cool thanks. I tried your nandroid backup and it starts up fine but I cant connect to my wifi network. It sees the network but it wont connect. It does allow me to connect to another open network I can see but not my own. This happened on one of the stock updates I did too. Any ideas why this might be? or how it might be fixed?
Click to expand...
Click to collapse
There are two options :
1. Restore 3.32.771.10 backup and its stock recovery image then do OTA to 4.20.771.2
You can have all the needed files here : http://forum.xda-developers.com/showpost.php?p=55322461&postcount=1897
Or
2. Reflashed the untouched 4.20.771.2 firmware that linked here : http://forum.xda-developers.com/showpost.php?p=58781201&postcount=4598
but you need to relock bootloader in order to do that.
a. put your device in bootloader/fastboot mode
b. relock bootloader - fastboot oem lock
c. run these commands
fastboot oem rebootRUU
fastboot flash zip 4.20.771.2_firmware.zip
fastboot flash zip 4.20.771.2_firmware.zip .....( again for the 2nd time)
fastboot reboot
d. check your wifi
For me .. 1st option is a better choice

ckpv5 said:
There are two options :
1. Restore 3.32.771.10 backup and its stock recovery image then do OTA to 4.20.771.2
You can have all the needed files here : http://forum.xda-developers.com/showpost.php?p=55322461&postcount=1897
Or
2. Reflashed the untouched 4.20.771.2 firmware that linked here : http://forum.xda-developers.com/showpost.php?p=58781201&postcount=4598
but you need to relock bootloader in order to do that.
a. put your device in bootloader/fastboot mode
b. relock bootloader - fastboot oem lock
c. run these commands
fastboot oem rebootRUU
fastboot flash zip 4.20.771.2_firmware.zip
fastboot flash zip 4.20.771.2_firmware.zip .....( again for the 2nd time)
fastboot reboot
d. check your wifi
For me .. 1st option is a better choice
Click to expand...
Click to collapse
so I tried option 2 first and that didnt work Then I tried option 1. Flashing 3.32.... worked ok wifi working etc. I then did the OTA that popped up. That flashed and it boots up but system ui force closes and wifi doesnt turn on at all Is there anyway to flash your OTA update specifically and avoid downloading and flashing the one that pops up on screen?

f_padia said:
so I tried option 2 first and that didnt work Then I tried option 1. Flashing 3.32.... worked ok wifi working etc. I then did the OTA that popped up. That flashed and it boots up but system ui force closes and wifi doesnt turn on at all Is there anyway to flash your OTA update specifically and avoid downloading and flashing the one that pops up on screen?
Click to expand...
Click to collapse
You can't flash OTA manually because your device is S-On.
When you have system ui force close and wifi doesn't turn on at all ... that's a good sign.
What you need to do now is unlock bootloader again with unlock_code.bin that you received from HTC. Then install TWRP 2.8.5.0. Boot to TWRP recovery, select mount - advance - format data - yes
Reboot - check your wifi again - system ui should work and wifi should work too.
Then restore my 4.20.771.2 backup (reason is when re-unlock bootloader and format data .. all data files such as calculator & flashlight & etc are removed)
EDIT : before you do the above, please try boot to recovery where you see the red triangle .. press & hold volume up & press power once.
In stock recovery, select factory reset/wipe data ... reboot

ckpv5 said:
You can't flash OTA manually because your device is S-On.
When you have system ui force close and wifi doesn't turn on at all ... that's a good sign.
What you need to do now is unlock bootloader again with unlock_code.bin that you received from HTC. Then install TWRP 2.8.5.0. Boot to TWRP recovery, select mount - advance - format data - yes
Reboot - check your wifi again - system ui should work and wifi should work too.
Then restore my 4.20.771.2 backup (reason is when re-unlock bootloader and format data .. all data files such as calculator & flashlight & etc are removed)
EDIT : before you do the above, please try boot to recovery where you see the red triangle .. press & hold volume up & press power once.
In stock recovery, select factory reset/wipe data ... reboot
Click to expand...
Click to collapse
before I saw your message I did a factory rest from stock recovery as you suggested in your edit and system ui force close was fixed and wifi does turn on... but im back to the problem of not being able to connect to my wifi network. I've managed to connect to 2 separate open (public) networks fine but cant connect to mine for some reason. I cant understand why this might be happening.
Thanks for all the help by the way really appreciate it!

That's something I'm not familiar with as I never have that problem before. I read a few thread of this kind of wifi problem .. there are a few suggestions such as reset the router, try change wifi password and a few more like 2.4GHz & 5.0 GHz problem
Maybe someone else more familiar with this kind of problem will step in.

ckpv5 said:
That's something I'm not familiar with as I never have that problem before. I read a few thread of this kind of wifi problem .. there are a few suggestions such as reset the router, try change wifi password and a few more like 2.4GHz & 5.0 GHz problem
Maybe someone else more familiar with this kind of problem will step in.
Click to expand...
Click to collapse
I had a look around and came across this http://www.pcadvisor.co.uk/how-to/g...llipop-solve-wi-fi-problems-on-nexus-devices/ where it suggests changing wifi router channel. I did and it works
Cant thank you enough dude. i've tried to thank all your posts to reflect how many thanks you deserve! At one point when one of the software updates went bad and the screen wouldnt turn on I was told HTC would charge around £200 to fix it! so yeah, thanks

Great :good::good:
Will keep that in mind in case someone else has same problem

-deleted-

Lost RUU backup
Hi I to am trying to revert back to stock on my HTC one M8 (Three UK H3g__00)1 but I have lost my original backups do to an hdd fail the RUU files you posted on here I believe I could have used but the links no longer work
My phone is in a bad way at the moment it is softbricked with the latest version of CWRM on and no OS currently installed, is this why my version main appears blank?
My phone has ended up in this state after trying to install the latest android revolution rom (5.0.1). The rom seemed to install ok booted and setup fine but my Wifi wouldn't turn ON at all. After I rebooted the phone for the first time it got stuck in a boot loop.
I deally would like to get lollipop on the phone and doing some reading I believe with the situation I'm in I have to go back to stock and do the OTA updates to raise my hboot version to 3.18 or above, that way I could install cyanogen 12.1
Apologies for noob question still learning.
My bootloader (3.16) is tampered, unlocked and S-ON
D:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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: H3G__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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.054s

lv426HuDz said:
Hi I to am trying to revert back to stock on my HTC one M8 (Three UK H3g__00)1 but I have lost my original backups do to an hdd fail the RUU files you posted on here I believe I could have used but the links no longer work
My phone is in a bad way at the moment it is softbricked with the latest version of CWRM on and no OS currently installed, is this why my version main appears blank?
My phone has ended up in this state after trying to install the latest android revolution rom (5.0.1). The rom seemed to install ok booted and setup fine but my Wifi wouldn't turn ON at all. After I rebooted the phone for the first time it got stuck in a boot loop.
I deally would like to get lollipop on the phone and doing some reading I believe with the situation I'm in I have to go back to stock and do the OTA updates to raise my hboot version to 3.18 or above, that way I could install cyanogen 12.1
Apologies for noob question still learning.
My bootloader (3.16) is tampered, unlocked and S-ON
Click to expand...
Click to collapse
First - remove the serial no. & imei no. on your above post.
Second - install TWRP 2.8.1.0, don't use CWM recovery.
Third - read this thread - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
for how-to and restore 1.54.771.9 backup & its matching recovery then do multiple OTAs up to the latest 4.xx.771.x

ckpv5 said:
First - remove the serial no. & imei no. on your above post.
Second - install TWRP 2.8.1.0, don't use CWM recovery.
Third - read this thread - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
for how-to and restore 1.54.771.9 backup & its matching recovery then do multiple OTAs up to the latest 4.xx.771.x
Click to expand...
Click to collapse
Hi ckpv5, thanks I will give this a try now, I did try to flash TWRP 2.8.7.0 recently but when I tried to enter the recovery it just hung and I never figured out why. I will give 2.8.1.0 a go now.
Last night, just to get my phone working I flashed on cm-11-20141112-SNAPSHOT-M12-m8 with open_gapps-arm-4.4-mini-20151203. It all seemed to be working fine and I liked the look and feel of the KitKat cyanogenmod but after I received my first phone call my phone speaker went crazy and gave some nasty distortion out, I rebooted the phone to stop it and now I have the noise on everything if I turn my volume up to mid/high, I'm worried my speakers are damaged. I followed a couple of threads to install the viperapp but with no success, any ideas on this one?
Cheers,

Thanks
CHeers ckpv5 Ifollowed the guide used the files and its all sorted now.
Looks like CM11 has damaged my bottom speaker though i have ordered a replacement.
I do have 1 last question, after all the updating i have now put cm12.1 on and it seems to be running ok however when im booted into the OS my SD card is not being detected. If i drop back into TWRP recovery it does recognise the SD card, any ideas? im searching for a solution now.

I can't comment anything on CM as I never use one .. no experience on CM .. sorry.

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

[Q] Unable to flash some ROMs I think its my internal storage

Hello,
Grab a drink and settle in, this ones lengthy!
My HTC one XL (UK, EE, Evita, CID: ORANG001) has been uber slow recently and I'd been wanting to have a tinker, remove bloatware for a while. So I set about investigating unlocking bootloader, rooting and flashing a funky ROM.
I first created a backup of phone using a couple of apps (to be safe, easy backup & Helium), then I copied all of the phone folders to my PC (to be safe), then I installed CWRom Manager and then from there installed CWM Recovery (6.0.2.8), unlocked the bootloader through HTCdev, no issues, booted back into CWM and made a backup.
Then I rooted my device using "BETA-SuperSU-v2.66-20160103015024" via the command line prompt, no issue there, took another backup in CWM Recovery.
Then I booted my phone, went into CWMRom manager, chose to flash a ROM "CM 10.0.0" and rebooted, phone got stuck at cyanogen mod screen and restarted x2 (realised I hadn't flashed the boot.img)
flashed the boot img via cmd line and phone booted into the initial set up screen (happy as a pig in dirt I was)...then I realised the touch screen wasn't working, bit of googling, found it a common problem, bit too late @ night to resolve, plus I couldn't find the correct file to replace the screen drivers, so I thought I would just revert.
I think (because I can't exactly remember this pattern of choices) that I chose the wipe/factory reset in CWM thinking that I would simply undo all that I'd done, re-do (as I quite enjoyed it) and select a different ROM, so when I booted into bootloader I think I then chose "clear data", the phone rebooted but got stuck at the white HTC quietly brilliant screen.
Realising there was no O/S, into Bootloader again and this time chose fastboot, went onto my PC but it wouldn't recognise the SD card in the phone and wanted me to format it. So I did so, I chose FAT32 and did a quick format.
Looking for a stock 4.2.2 ROM to return to I downloaded this "EVITA_UL_JB_50_S_TMO_DE_5.08.111.2_By_Turge", then flashed the boot img and it worked fine and got me my phone back to life, albeit T-Mobile and German bloatware.
I then tried to flash CM12.1 via CWM recovery, but it failed due to no file contexts and mounting issues (see attched pic) and at the end of it was status 7 error. I then maually mounted all points in CWM (/system /data /cache etc) and re-run, this time status error 0 message. Bit more googling led me to replacing the "META-INF" file from a working ROM (so I chose the ze German one) into the non-working CM12.1, and it worked. Phone booted, but it was back into the German ROM, not CM12.1.
So today, found my original nandroid backup from CWM recovery and restored to it. Phone back alive and working again. I downloaded CM11 (thinking it was better suited to my bootloader 2.18) but again, I get the mounting issues present with /system /data etc, BUT...when I tried to re-flash the german ROM, that worked. So it can flash something, just not everything.
So it can flash - but it seems that something just isn't right with my storage and I can't place it. I'm not sure of what commands to run to identify what partitions do and don't exist on the damn thing, so I could do with some help there. It feels like if I sort my storage issue out and get over that hurdle, I can flash a ROM. Do I need to re-create any -ext partitions?? I have downloaded an app, retrieved partition and usage info and have posted it also.
My current state as of writing;
Botloader unlocked
rooted with SuperSU
I have installed TWRP App, however I have NOT yet installed recovery, this is because it was asking me to confirm that /dev/block/mmcblk0p22 is the correct something - I just don't know how to confirm this and do not want to cause an irreversable change. I would prefer to resolve with CWM as I am used to using that now.
So many thanks if someone can help me.
Key info:
build number: 5.14.61.2 CL275436 release keys
I am aware of an update to firmware 5.18 (recommended for AT&T users) but I am a UK, EE user and no updates have been pushed to me. So I don't want to upgrade this yet either. I would rather remain at 5.14, get the thing working than risk bricking it with firmware while it's not 100% happy.
CWM recovery 6.0.2.8
Images of useful info I hope + disk usage - (Unable to post an external link to Drop box as I'm new, please PM me for images.)
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.18.0000
(bootloader) version-baseband: 1.34a.32.45.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8311000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4101mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c20bff6f
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.135s

[Solved]
So,
An update in case anybody else has this same issue. I solved it myself!
I twigged that CWM Recovery had become stuck/confused/corrupt as when I downloaded CWMROM and tried to reflash to the latest version, it advised me it had completed, but actually when I then booted in CWM recovery, it still showed the old version.
So I reflashed TWRP over CWM
Wiped the SD card
then proceeded to flash CM 12.1 & Gapps - worked first time
Rebooted - nowt, got stuck
Reflashed boot.img
Rebooted - success
it may help somebody else

HTC ONE M8 HTC_044 stuck at HTC logo after OTA (marshmallow)

MY HTC one M8 is stuck at boot screen. Tried reset etc. does not work.
Following are details of device:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.14.707.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__044
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Can you please help me :
1. Do i need to get stock rom and flash. if yes where do i get it.
2. Is there any other way to resolve this issue.
Thanks a lot

First question is, are you on stock ROM or not (unlocked/relocked/all stock ?!) ?
Please tell us what you did before and how you did the OTA or even give some more info at all

KODEC.4 said:
First question is, are you on stock ROM or not (unlocked/relocked/all stock ?!) ?
Please tell us what you did before and how you did the OTA or even give some more info at all
Click to expand...
Click to collapse
Yes Sir,
I am on stock rom. It shows "locked" and software status"official"
I did update over Wifi once i received a new update version notification. Download of update finished on Mobile, after which i initiated install and then it was stuck forevr on White boot screen with HTC logo.
I tried reboot and factory rest options as well, still same.
thanks for your prompt response.

rashmixda said:
Yes Sir,
I am on stock rom. It shows "locked" and software status"official"
I did update over Wifi once i received a new update version notification. Download of update finished on Mobile, after which i initiated install and then it was stuck forevr on White boot screen with HTC logo.
I tried reboot and factory rest options as well, still same.
thanks for your prompt response.
Click to expand...
Click to collapse
If you didn't do anything to the phone, i would say the best idea would be to send it back for repair if you still have warranty on it... (any other way of fixing it by yourself would maybe void your warranty)

KODEC.4 said:
If you didn't do anything to the phone, i would say the best idea would be to send it back for repair if you still have warranty on it... (any other way of fixing it by yourself would maybe void your warranty)
Click to expand...
Click to collapse
Warranty is over and i am in a remote town in uae, so sending to repair is the last option.
where can i get stock rom or RUU for my phone version.

ok read trough here: http://forum.xda-developers.com/htc-one-m8/general/guide-restore-european-htc-one-m8-to-t3072235
Best would be if you read every page because the guy at the last page hast the same CID like you (could be helpfull infos for you)
But BEFORE you start trying this method (or the method mentioned at the end with nandriod backups) you first have to unlock your bootloader (wich voids your warranty)

rashmixda said:
MY HTC one M8 is stuck at boot screen. Tried reset etc. does not work.
Following are details of device:
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-main: 6.14.707.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__044
Can you please help me :
1. Do i need to get stock rom and flash. if yes where do i get it.
2. Is there any other way to resolve this issue.
Thanks a lot
Click to expand...
Click to collapse
As you mentioned your warranty is over and you don't need to send your phone for repair.
What you need to do :
1. unlock bootloader thru http://www.htcdev.com/bootloader
2. install TWRP 2.8.7.0
3. restore Marshmallow 6.14.707.1 non-rooted backup
4. don't accept root offered by TWRP
5. install stock 6.14.707.1 recovery.img (optional)
6. reboot & done.
All files & How-To, see : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
This will get you back to your stock ROM
Or you can unlock bootloader, install TWRP and install any custom ROM that you like to try.

I did the following instead already:
1. unlock bootloader thru http://www.htcdev.com/bootloader
2. install TWRP 2.8.7.0
3. Root using TWRP
4. ?
Can u ley me know the next step now. Can i use the twrp backup from the below post now ?
http://forum.xda-developers.com/showpost.php?p=60211240&postcount=3
Thanks for your simple and step by step process.
You guys rock.

Yes ... 6.14.707.1 backup on post #3 & 6.14.707.1 stock recovery on post #4
For all the steps, read post #1 ... I don't want to repeat them here.

hey all, great to see this post and i have exact identical situation here and want to try the step here to fix my M8. rashmixda, do you successfully revive your m8?
p/s: sorry that i edit the post twice to correct the name i ask and a typo. realize i asking wrong person after i saw the backup file name after ckpv5. thanks for your backup and it is my life saver for my M8.

ckpv5 said:
As you mentioned your warranty is over and you don't need to send your phone for repair.
What you need to do :
1. unlock bootloader thru http://www.htcdev.com/bootloader
2. install TWRP 2.8.7.0
3. restore Marshmallow 6.14.707.1 non-rooted backup
4. don't accept root offered by TWRP
5. install stock 6.14.707.1 recovery.img (optional)
6. reboot & done.
All files & How-To, see : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
This will get you back to your stock ROM
Or you can unlock bootloader, install TWRP and install any custom ROM that you like to try.
Click to expand...
Click to collapse
I follow the steps and successfully revived my bricked HTC M8. The backup files are really handy in my case. Thank you.

Help: Cannot turn on wifi/bluetooth. Phone no longer have cellular signal.
Hi ckpv5,
I followed this guide and I was somehow able to revive my phone. Before, it no longer boots --it goes straight to the bootloader after the HTC logo. Unfortunately, my wifi, bluetooth, and cellular signal issues have remained unresolved -- I still can't turn on wifi and bluetooth and I still don't have cellular signal) . Before my phone went into bootloop, I already had these issues and they have persisted until now.
Is there a chance that these are just due to a software/firmware issue? And if so, please advise on what to do to resolve these issues. Thanks in advance for your help. My phone is not supported in my country. In fact, it was returned to me by the authorized service center unrepaired after a month of being with them.
Please see below additional info regarding my phone.
C:\Program Files\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.14.707.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA48EWM02822
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__044
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.140s
ckpv5 said:
As you mentioned your warranty is over and you don't need to send your phone for repair.
What you need to do :
1. unlock bootloader thru http://www.htcdev.com/bootloader
2. install TWRP 2.8.7.0
3. restore Marshmallow 6.14.707.1 non-rooted backup
4. don't accept root offered by TWRP
5. install stock 6.14.707.1 recovery.img (optional)
6. reboot & done.
All files & How-To, see : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
This will get you back to your stock ROM
Or you can unlock bootloader, install TWRP and install any custom ROM that you like to try.
Click to expand...
Click to collapse

ebaustero said:
Hi ckpv5,
I followed this guide and I was somehow able to revive my phone. Before, it no longer boots --it goes straight to the bootloader after the HTC logo. Unfortunately, my wifi, bluetooth, and cellular signal issues have remained unresolved -- I still can't turn on wifi and bluetooth and I still don't have cellular signal) . Before my phone went into bootloop, I already had these issues and they have persisted until now.
Is there a chance that these are just due to a software/firmware issue? And if so, please advise on what to do to resolve these issues.
Click to expand...
Click to collapse
I don't know whether the problem is hardware issue. Based on your info, it looks like hardware problem.
What you can try is restore one version lower 4.19.707.4 backup and install 4.19.707.4 stock recovery then do OTA again to 6.14.707.1. When doing this, it will reinstall the firmware too and see whether this will fix your problem.
You can get the files from : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860

Hi ckpv5,
Thanks a lot. I am now downloading the files.
I'll be probably be doing the OTA update manually since I cannot turn wifi on on my phone. Can I use the 6.14.707.1_ckpv5.zip file that I previously downloaded? Or probably I have to root my phone so that I can share my pc's internet to it through reverse tethering. Will rooting not cause issues during OTA updates. Thanks...
ckpv5 said:
I don't know whether the problem is hardware issue. Based on your info, it looks like hardware problem.
What you can try is restore one version lower 4.19.707.4 backup and install 4.19.707.4 stock recovery then do OTA again to 6.14.707.1. When doing this, it will reinstall the firmware too and see whether this will fix your problem.
You can get the files from : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Click to expand...
Click to collapse

ebaustero said:
Hi ckpv5,
Thanks a lot. I am now downloading the files.
I'll be probably be doing the OTA update manually since I cannot turn wifi on on my phone. Can I use the 6.14.707.1_ckpv5.zip file that I previously downloaded? Or probably I have to root my phone so that I can share my pc's internet to it through reverse tethering. Will rooting not cause issues during OTA updates. Thanks...
Click to expand...
Click to collapse
As I wrote above, you need to restore 4.19.707.4 and its stock recovery. Don't use 6.14.707.1 and don't root.
After you restore 4.19.707.4 you can connect to PC and use Internet Pass-Through feature to check and download OTA .. don't root because OTA will fail on a rooted ROM. We expect the OTA from 4.19.707.4 to 6.14.707.1 will fix your problem. If it does not fix it, then it is hardware problem.
Note : you can't manually install OTA on a S-On device

Hi ckpv5,
Thanks a lot for your help. My phone is now working fine after the OTA update from 4.19.707.4 to 6.14.707.1.
ckpv5 said:
As I wrote above, you need to restore 4.19.707.4 and its stock recovery. Don't use 6.14.707.1 and don't root.
After you restore 4.19.707.4 you can connect to PC and use Internet Pass-Through feature to check and download OTA .. don't root because OTA will fail on a rooted ROM. We expect the OTA from 4.19.707.4 to 6.14.707.1 will fix your problem. If it does not fix it, then it is hardware problem.
Note : you can't manually install OTA on a S-On device
Click to expand...
Click to collapse

ebaustero said:
Hi ckpv5,
Thanks a lot for your help. My phone is now working fine after the OTA update from 4.19.707.4 to 6.14.707.1.
Click to expand...
Click to collapse
Great ... it's not hardware problem ... it just firmware matter :good::good:

ckpv5 said:
As I wrote above, you need to restore 4.19.707.4 and its stock recovery. Don't use 6.14.707.1 and don't root.
After you restore 4.19.707.4 you can connect to PC and use Internet Pass-Through feature to check and download OTA .. don't root because OTA will fail on a rooted ROM. We expect the OTA from 4.19.707.4 to 6.14.707.1 will fix your problem. If it does not fix it, then it is hardware problem.
Note : you can't manually install OTA on a S-On device
Click to expand...
Click to collapse
ckpv5, you had just save me once again. my problem already posted in http://forum.xda-developers.com/htc-one-m8/help/htc-m8-developed-random-reboot-failed-t3345745 but cant really fixed because im not exactly know where goes wrong and how to fix. Anyway, i just try to restore version 4.19.707.1 with recovery and let it upgrade with OTA as this is 2nd way to restore my M8 with latest OS. now, quite confirmed it fixed and no more random reboot for pass 5 hours. usually reboot happened 3 to 4 times in an hour. the detail about finding the cause will be posted on my thread.
thanks again for valuable help.

Marshmallow OTA failed

Hi All,
I'd like a bit of advice/help.
I went to update my phone to Marshmallow OTA and it did it's thing. I left the phone for hours and it appeared to be stuck on android is starting. I restarted the phone and it's now stuck on the HTC splash screen. Recovery options don't work etc.
I've searched around and there are loads of guides but these tend to lean towards rooting. I'm not looking to root but instead looking to get the phone back to factory software that it was originally on.
It's a UK model locked to the 3 network. See below for info taken from the phone.
Thanks in advance.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.771.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH46HWM04949
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: H3G__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

Can anyone assist? I'm desperate here. I've not had a working phone for days here. The guides I've seen appear to apply to either previously rooted phones or suggest I get the file from the HTC us site but my software versions is newer than those listed.
I have HTC tool kit installed and android studio so any tips would be greatly appreciated.
Thanks.

Is the bootloader UNLOCKED ? or LOCKED or RELOCKED ?
If it is UNLOCKED, I can suggest to restore a non-rooted stock backup.
If it is LOCKED, you can try going to recovery and do data wipe from there (provided that is stock recovery)
and don't use Toolkit .. it brings more harm for less experience user

I've managed to unlock the boot loader. How do restore using a non rooted standard backup? Thanks for replying.

1. You need these files adb/fastboot and HTC USB drivers installed
Read this for the files : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
2. Read this thread post #1 on How-To restore a backup and install stock recovery
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
3. Install TWRP 3.0.0.1 - https://dl.twrp.me/m8/
4. Download and restore 6.13.771.4 backup (from post #3 from link on no.2)
5. Download and install 6.13.771.4 stock recovery (from post #4 link on no.2)
6. Reboot and see whether it works or not

Thanks for that.
It's now at the stage where the apps have been optimized and it's now just hanging at the "Android is starting..." "Starting Apps...".
This was my original issue I had when the software was updated first time round.
Any clues on how to get past that?
Thanks

Mcbane16 said:
Any clues on how to get past that?
Thanks
Click to expand...
Click to collapse
No clues ... hopefully it's not hardware problem.
What you can try .. restore one version lower, then do OTA becuase OTA will reinstall the firmware.
Restore 4.25.771.6 backup & its recovery.img then check for OTA, download and install.

The downgrade worked and I updated to Marshmallow but for some reason, the phone still hangs on Android is upgrading and starting apps. I'm at a loss as to what to do next. I don't want to use a phone on an old version of software and never upgrade.

So you can boot the lollipop but not Marshmallow ?
I don't know whether you can find htc signed 6.13.771.4 firmware.zip .. this is the only thing I have in mind. Maybe manually flashing the firmware.zip will fix your problem.
I'm already in bed as I will be outstation in the morning. If you can wait, just run the lollipop for the time being. I will give you the firmware.zip on Sunday night (GMT +8) to try to fix it.
Hopefully someone else will be able to help you while I'm not around.

Would changing the CID and MID and selecting a different software package work perhaps?

You only can change CID & MID on a S-Off device.
To S-Off your device you need to pay usd25 for the Sunshine app.
Why don't you try a Marsmallow custom ROM to see whether you can boot it.
If you can at least you can run a Marshmallow ROM until you fix your problem.
I'm signing off now .. goodnight & good luck

Thanks, if anyone else could assist that would be appreciated. I've installed a custom marshmallow rom and all went well but it still suffers with the same fault. It hangs on starting apps. No matter what I do this phone doesn't like Marshmallow!

ckpv5 said:
You only can change CID & MID on a S-Off device.
To S-Off your device you need to pay usd25 for the Sunshine app.
Why don't you try a Marsmallow custom ROM to see whether you can boot it.
If you can at least you can run a Marshmallow ROM until you fix your problem.
I'm signing off now .. goodnight & good luck
Click to expand...
Click to collapse
Hi, I'll wait for your offer of the firmware zip and try that. For some reason this phone doesn't like anything to do with marshmallow.

Mcbane16 said:
Hi, I'll wait for your offer of the firmware zip and try that. For some reason this phone doesn't like anything to do with marshmallow.
Click to expand...
Click to collapse
Sure can .. I get back to you once I'm back from outstation tomorrow evening.
1. Restore the Marshmallow 6.13.771.4 backup if you're on different ROM
2. Download firmware.zip
3. Put your device on bootloader/fastboot mode and put the firmware.zip in your fastboot/adb folder and open a command prompt from this folder
4. Run below commands
fastboot oem lock - to relock your bootloader because your device is S-On
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip firmware.zip
You'll see -
if failed : FAILED (remote: 90 hboot pre-update! please flush image again immediately)
repeat fastboot flash zip firmware.zip
fastboot reboot
check whether your wifi is working now ..

Thanks for that, what I did in the mean time was use the sunshine app to S-Off and change my CID and MID to a deveolper phone. All was fine until the phone upgraded to marshmallow. It still hangs on the Android is upgrading starting apps. It seems no matter what I do this phone will not accept marshmallow.
Any other ideas as to why? So odd why marshmallow doesnt boot past this screen.

Since now your device is S-Off .. instead of updating it to Marshmallow, have you tried running a Marshmallow RUU on it ?
(Assuming your current firmware installed is 6.12.1540.4)
Here is the RUU : http://www.htc.com/us/support/htc-one-m8/news/
If after running the RUU and still the same problem .. I have to say that I'm out of idea.

ckpv5 said:
Since now your device is S-Off .. instead of updating it to Marshmallow, have you tried running a Marshmallow RUU on it ?
(Assuming your current firmware installed is 6.12.1540.4)
Here is the RUU : http://www.htc.com/us/support/htc-one-m8/news/
If after running the RUU and still the same problem .. I have to say that I'm out of idea.
Click to expand...
Click to collapse
I'm downloading one now. I'll update you with the outcome. I'm at a loss as to why this is happening. What does the RRU contain?

It has every images that a device need. Means it removes everything on your device and replace them with new images that come from the RUU.
One thing to note, other that those drivers and HTC USB Drivers that you need (in my previous post), you need a PC with USB2.0

It's currently optimizing apps so we'll see if it boots up. Is there much difference between doing an OTA through all the various updates and going straight via an RRU?

Mcbane16 said:
It's currently optimizing apps so we'll see if it boots up. Is there much difference between doing an OTA through all the various updates and going straight via an RRU?
Click to expand...
Click to collapse
Sadly, it still does the same thing. Would a hardware fault possibly cause this?