Develop Bugs

[Q] Recovery Issues... No Backup

I Recently Rooted And S-off'd my HTC One M8 (Sprint)
No problems there.
I was being a dumb ass and installed a new radio frequency without backing mine up..
This caused my phone to start a boot loop, so I reset it.
I have no OS so I can't turn on debugging
When I attempt to sideload or push a zip ADB tells me it can't find my device.
I am using Clockwork Mod Recovery.
Do I need to use RUU?
I can boot into recovery or bootloader.
I'm looking to go back to stock and lock my bootloader.
Any help is welcome.
I'll update if I can get anything working here

BrettMike said:
I Recently Rooted And S-off'd my HTC One M8 (Sprint)
No problems there.
I was being a dumb ass and installed a new radio frequency without backing mine up..
This caused my phone to start a boot loop, so I reset it.
I have no OS so I can't turn on debugging
When I attempt to sideload or push a zip ADB tells me it can't find my device.
Do I need to use RUU?
I can boot into recovery or bootloader.
I'm looking to go back to stock and lock my bootloader.
Any help is welcome.
I'll update if I can get anything working here
Click to expand...
Click to collapse
If you can boot into recovery, download a ROM onto your PC, then transfer it to your extSD. Flash that and you will have a working phone again. Since you are S-Off, you can then find the appropriate firmware package to get you radio back to normal (which it still may be).

xunholyx said:
If you can boot into recovery, download a ROM onto your PC, then transfer it to your extSD. Flash that and you will have a working phone again. Since you are S-Off, you can then find the appropriate firmware package to get you radio back to normal (which it still may be).
Click to expand...
Click to collapse
I don't have an extSD to do that with. HTC One m8's don't have them (as far as I'm aware) and do you have any links to the firmware packages I can use? If not. I'm sure I can look around for them.

well I found the External SD Card so Thanks! I will try this method for sure

BrettMike said:
I don't have an extSD to do that with. HTC One m8's don't have them (as far as I'm aware) and do you have any links to the firmware packages I can use? If not. I'm sure I can look around for them.
Click to expand...
Click to collapse
Hook up your phone to your PC, get into ADB/fastboot, and enter the command fastboot getvar all. Post the readout here (minus your IMEI and serial# for your own protection), and I'll direct you to the proper firmware.

xunholyx said:
Hook up your phone to your PC, get into ADB/fastboot, and enter the command fastboot getvar all. Post the readout here (minus your IMEI and serial# for your own protection), and I'll direct you to the proper firmware.
Click to expand...
Click to collapse
Thanks Give Me A Bit here. I AM The OP Btw.
(Different Account)
---------- Post added at 10:17 PM ---------- Previous post was at 10:08 PM ----------
xunholyx said:
Hook up your phone to your PC, get into ADB/fastboot, and enter the command fastboot getvar all. Post the readout here (minus your IMEI and serial# for your own protection), and I'll direct you to the proper firmware.
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.14.21331931.LA21G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.651.10
(bootloader) version-misc: PVT SHIP S-OFF
(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: 6400afe2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.030s

fundipz said:
Thanks Give Me A Bit here. I AM The OP Btw.
(Different Account)
---------- Post added at 10:17 PM ---------- Previous post was at 10:08 PM ----------
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.14.21331931.LA21G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.651.10
(bootloader) version-misc: PVT SHIP S-OFF
(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: 6400afe2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.030s
Click to expand...
Click to collapse
If you are not having radio issues, then don't bother worrying about it. If you are having them, flash the official RUU from HTC's website to fix your stuff.
Also, having two accounts is against XDA rules (rule #14). You should delete one of them.

xunholyx said:
If you are not having radio issues, then don't bother worrying about it. If you are having them, flash the official RUU from HTC's website to fix your stuff.
Also, having two accounts is against XDA rules (rule #14). You should delete one of them.
Click to expand...
Click to collapse
Thanks! And I Dont Exactly Have 2. It Was My Dads Account.
---------- Post added at 10:51 PM ---------- Previous post was at 10:37 PM ----------
xunholyx said:
If you are not having radio issues, then don't bother worrying about it. If you are having them, flash the official RUU from HTC's website to fix your stuff.
Also, having two accounts is against XDA rules (rule #14). You should delete one of them.
Click to expand...
Click to collapse
SOLVED! Thanks! Got Everything Fixed! :laugh::laugh::laugh:

How to update to stock marshmallow from custom rom?

Hey guys..
I've been on cyanogenmod cm 12.1 for about six months now.. And completely out of touch with the entire process
So I'm s-on and wanted to go back to stock marshmallow from cm12.1
Which is the best way to go About it? Would really appreciate any help/advice.
Thank you so much!
Sent from my m8 using Tapatalk

Relock your bootloader and run your RUU (hopefully you have a RUU for your device). Make sure your MID and CID match to that of your RUU. You are back to complete stock (Marshmallow).

androidindian said:
Hey guys..
I've been on cyanogenmod cm 12.1 for about six months now.. And completely out of touch with the entire process
So I'm s-on and wanted to go back to stock marshmallow from cm12.1
Which is the best way to go About it? Would really appreciate any help/advice.
Thank you so much!
Sent from my m8 using Tapatalk
Click to expand...
Click to collapse
A RUU would be an ideal start.
To better assist, how exactly did you get CM12.1 on that HTC to begin with? I'm s-off so I have no idea whether there are more or less steps involved.
I want to make sure the info I dig up applies to your situation and device. Take your time to gather any details you recall.
Sent from my HTC M8 GPE
? Mass Transit Honchkrow ?

harihacker said:
Relock your bootloader and run your RUU (hopefully you have a RUU for your device). Make sure your MID and CID match to that of your RUU. You are back to complete stock (Marshmallow).
Click to expand...
Click to collapse
Awesome! Thank you! Any link to where I can get the right ruu mate? Thanks a lot!
Sent from my m8 using Tapatalk

That depends on which device you have. What is the MID/CID of your device?
---------- Post added at 11:47 AM ---------- Previous post was at 11:46 AM ----------
RUU's can be downloaded directly from HTC.

androidindian said:
Awesome! Thank you! Any link to where I can get the right ruu mate? Thanks a lot!
Sent from my m8 using Tapatalk
Click to expand...
Click to collapse
Post the results of fastboot getvar all. Make sure to delete the serial# and IMEI from your post (that's private info)
With your getvar it will be easiest to direct you on the proper RUU for your device.

xunholyx said:
Post the results of fastboot getvar all. Make sure to delete the serial# and IMEI from your post (that's private info)
With your getvar it will be easiest to direct you on the proper RUU for your device.
Click to expand...
Click to collapse
Thank you so much mate! sure here are the details:
(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.10
(bootloader) version-misc: PVT SHIP S-ON
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
please advice the right ruu to be used to get back to stock? thank you so so much!!

androidindian said:
Thank you so much mate! sure here are the details:
(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.10
(bootloader) version-misc: PVT SHIP S-ON
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
please advice the right ruu to be used to get back to stock? thank you so so much!!
Click to expand...
Click to collapse
Here is the 4.16.401.10 RUU. This will take you back to stock so that you can receive the Marshmallow OTA.
Download that to your PC, then hook up your phone. Since you are S-On, you will need to relock your bootloader first. In fastboot: fastboot oem lock
Then double click on the RUU.exe that you downloaded and follow the prompts.
After you are back to stock, check in settings > about > software updates. You should get an OTA to update to Marshmallow. It might not come right away. Be patient. It might take a couple of days to receive the OTA notification.
Good luck!

Also Check this thread: http://forum.xda-developers.com/showthread.php?t=2735235

xunholyx said:
Here is the 4.16.401.10 RUU. This will take you back to stock so that you can receive the Marshmallow OTA.
Download that to your PC, then hook up your phone. Since you are S-On, you will need to relock your bootloader first. In fastboot: fastboot oem lock
Then double click on the RUU.exe that you downloaded and follow the prompts.
After you are back to stock, check in settings > about > software updates. You should get an OTA to update to Marshmallow. It might not come right away. Be patient. It might take a couple of days to receive the OTA notification.
Good luck!
Click to expand...
Click to collapse
Amazing!! Thank you so so much mate.. everything went super smoothly and now im updating to marshmallow soon, back on the above stock.. yay!

wiped my OS, flashed a poop ROM need help

Long story short, I forgot my screen lock and wiped as a last resort. Realizing too late that a factory reset wouldn't complete, I was left with a paperweight. I was able to get a rooted stock ROM from XDA, flashed it and it seems to be working. I want to get back to viper ROM, preferably marshmallow (I'm currently on lollipop) but I am having a lot of trouble. Attempts to get s-off have been thwarted, and flashing viper (5.0.2) has failed. Any help would be appreciated. I can answer any questions.

What stock ROM did you flash, exactly?
How exactly are you trying to s-off, and what step did you get stuck (error messages, or other results?)?
When the ROM failed, did it give you an error message (or list any other outputs or results)?
Your statements on these last 2 points if far too vague, for us to help properly.
Also, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).

Lmy470.h6 is the ROM I flashed. I've been trying to push firewater via adb to get s off. I can't/won't pay for a sunshine. When flashing other stock Roms, the error is no error. It just says install aborted. When trying to flash viper, it says there's a permission error. When trying to run firewater, it gives me the PIE error. Getvar coming later.

Firewater won't work, Period. It had an online component (had to connec to a server), which the devs stopped supporting in Dec 2014. Nothing you do will make it work, and is a complete waste of time.
That said, you don't need s-off to flash ROMs. And whatever is wrong with flashing ROM, s-off is probably not going to fix.
The fact that multiple ROMs work, indicates user error, and you're incorrectly trying to blame the ROMs ("poop ROM").
What TWRP version? Need that info, and getvar data. But I'm guessing you just have an old version of TWRP (or try another slightly different build TWRP).

I'm actually using philz touch recovery. I only call it a poop ROM because I don't like what it came with and how it looks. Also. The ROM I'm using is the only ROM that works thus far. Most other Roms simply abort. Viper ROM tells me it doesn't have to permissions necessary which indicates the need for s off. I attempted getvar, however the command window just sat idle and wouldn't let me type anything. Am I missing something there?

I should also mention I've been using recovery to flash Roms. Perhaps flashing via adb would work better? Or work at all?

One last thing. Flashing the ROM I'm currently using created new 0 directories. I now have 0/0/0. Any safe way to fix that?

enviouss said:
I'm actually using philz touch recovery.
Click to expand...
Click to collapse
That's the problem right there. Philz hasn't been updated in a long time, maybe 2 years. Its almost certainly the cause for the ROM flashes failing.
Use TWRP, but exact version depends on your current firmware version, indicated in getvar. But probably TWRP 2.8.7 since you indicated you were using Lollipop ROMs okay.
enviouss said:
I only call it a poop ROM because I don't like what it came with and how it looks.
Click to expand...
Click to collapse
So its your personal opinion and preference, and I would recommend you not insulting the work of devs that work so hard (usually for no compensation) to post their work here.
---------- Post added at 10:09 AM ---------- Previous post was at 10:06 AM ----------
enviouss said:
I should also mention I've been using recovery to flash Roms. Perhaps flashing via adb would work better? Or work at all?
Click to expand...
Click to collapse
Sideload adb still needs the proper recovery, adb can't flash a ROM by itself. Sideload just adds move points of failure, not less. I don't recommend it, as I've seen it cause more problems than it solves (fails when simply flashing in recovery works).
---------- Post added at 10:11 AM ---------- Previous post was at 10:09 AM ----------
enviouss said:
I attempted getvar, however the command window just sat idle and wouldn't let me type anything. Am I missing something there?
Click to expand...
Click to collapse
Are you in bootloader-fastboot mode when issuing the command?
If so, try another cable, another USB port, or re-install HTC drivers.

I haven't been I boot loader mode. Will try shortly. Also. Will change to twrp. And yes, I'm on lollipop 5.1. I will change recoveries and attempt getvar. Results will be posted.

Getvar results follow.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.21331147A1.19_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.1540.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.048s

Getvar results follow.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.21331147A1.19_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.1540.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.048s

enviouss said:
Getvar results follow.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.21331147A1.19_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.1540.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.048s
Click to expand...
Click to collapse
Also, flashed your recommended version of TRWP recovery. It is up and running. I am ready for the next phase.

enviouss said:
Also, flashed your recommended version of TRWP recovery. It is up and running. I am ready for the next phase.
Click to expand...
Click to collapse
I'm glad I asked for the getvar data. Your firmware (hboot, radio, etc.)is woefully outdated as its still on kitkat firmware, which I can tell from the radio number and version-main 3.28.1540.5. This alone will prevent LP and MM ROMs from working (no boot or broken WiFi).
There are various ways to update the firmware:
- Restore stock TWRP backup for 3.28.1540.5, and corresponding stock recovery, and perform OTA updates which will also update the firmware.
- Relock bootloader, and flash full stock 6.12.1540.4 firmware following the Method 2 here. After flashing firmware, you can then unlock bootloader again, flash TWRP and flash the desire ROM.

I would greatly prefer not to relock my boot loader,as it requires HTC correspondence to unlock. That could take a while. Can you walk me through your first method? Possibly with links to other threads and downloads?

I messed up. big time. So i found and downloaded your recommended recovery image. Downloaded flashify for root, and flashed the image. Now whenever I try to boot, or enter recovery mode, i get the red triangle of death. Please help! I tried reflashing twrp via adb, but adb doesnt recognize my device anymore! I dont know what to do...

update: performed a factory reset. Was able to get device up and running again. Impatiently awaiting further instruction.

enviouss said:
I messed up. big time. So i found and downloaded your recommended recovery image. Downloaded flashify for root, and flashed the image.
Click to expand...
Click to collapse
What did you download, and from where? Its not clear what you were trying to do here, exactly. You don't need root to flash ROMs or TWRP backups; and I personally dislike using apps like Flashify, for things that are easily accomplished with fastboot, TWRP, etc.

I found the stock nandroid backup suggested and flashed it using flashify. I have an idea what needs to be done here, but if an expert like yourself could leave me some detailed instructions as well ad download links it would really help.

enviouss said:
I found the stock nandroid backup suggested and flashed it using flashify. I have an idea what needs to be done here, but if an expert like yourself could leave me some detailed instructions as well ad download links it would really help.
Click to expand...
Click to collapse
He did give you expert advice, and you didn't follow it. Don't use Flashify. Any instructions you get from anyone here will tell you to use ADB/fastboot.
Also, you are going ahead without proper instructions and you can go ahead and do that, but go to where you got those other instructions from to ask for help.

Actually, in reference to the nandroid backup, he (we are assuming here) never said exactly how to use the files. Just what to do. I need precise instructions with links to fix this issue. This is one I've never dealt with before.

HTC one M8 problem while updating to M

Hi all,
First of all, I found a thread describing the problem that I have, entitled : "(solved)Help with update To android M" . It was actually solved by "ckpv5". But my device is different, i.e. has different "fastboot getvar all" output, so I don't know how I should proceed.
The problem came up after my efforts, trying to update to Android 6. My device came initially with Android 5.1, OS version 4.16.401.. Via HTC sync manager and the RUU update process described in HTC's website, I was trying to update to Android 6, but without success. The device was initially registered in AT&T, but now it is on Q-Telecom, a provider in Greece. I did several things, obviously bad ones, and the problem is that I can no longer boot. I can access the bootloader only.
Below is the output of "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.12.1540.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: < empty >
(bootloader) imei: < empty >
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: BS_US001
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Please note that I changed the CID from 11111111 to BS_US001, after I got in contact with HTC group. This was their suggestion
What should I do to update the device to Android 6?
Which .zip file should I use? I found a link with a suggestion on the proper .zips (I cannot post it here, as I am a new user)
Should I rename the .zip?
Should I put it to the microSD, in the root directory?
Best
khtc

Since you are S-OFF, if you know if your device was originally a GSM or a CDMA variant, you could flash any S-OFF RUUs found here. you may have to change your MID and CID to suit the RUU you would be flashing.
Alternately, you can flash just the appropriate firmware, TWRP and flash any CM/AOSP too.

Based on the main version 6.12.1540.4, it appears the firmware was updated (Developer's Edition MM firmware) at some point. You may be able to now run the 6.12.1540.4 RUU:
http://dl3.htc.com/application/RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe
Try the above, and see what happens. If it doesn't work, take note of the specific error message, and any other observations, and post them for us to look at.
If the 6.12.1540.4 firmware was not correctly installed you may need to find and re-flash it, before you can RUU.
---------- Post added at 10:04 AM ---------- Previous post was at 09:59 AM ----------
rln_xda said:
Since you are S-OFF, if you know if your device was originally a GSM or a CDMA variant, you could flash any S-OFF RUUs found here. you may have to change your MID and CID to suit the RUU you would be flashing.
Click to expand...
Click to collapse
This would be another valid alternative, to "convert" to another M8 version (such as Euro) by RUU. Although for any official, signed RUU, the CID at least will definitely need to be changed. SuperCID should also work for most RUUs. So the advice from HTC to change from SuperCID was actually not necessarily great advice. Just the advice they give - since they don't really want you to modify the device.

This is actually a duplicate post. He solved his problem - https://forum.xda-developers.com/showpost.php?p=70463082&postcount=36

ckpv5 said:
This is actually a duplicate post. He solved his problem - https://forum.xda-developers.com/showpost.php?p=70463082&postcount=36
Click to expand...
Click to collapse
Thanks for clarifying.
To the OP, I know you are pretty new to the forums. But please read and follow the forum rules; which expressly instruct not to post the same issue in multiple places (cross posting).
Also, please be courteous, and if you've solved your problem, mark so in the thread you made. Although this point pretty much goes with the first one (you wouldn't need to mark it as "solved" if you hadn't posted to 2 different places, in the first place).

Thread closed, answer. bellow.
ckpv5 said:
This is actually a duplicate post. He solved his problem - https://forum.xda-developers.com/showpost.php?p=70463082&postcount=36
Click to expand...
Click to collapse

Htc one M8 Os problem

Htc one m8
fastboot getvar all
(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: HT46PWM03644
(bootloader) imei: 3578710********
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__102
(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
all: Done!
finished. total time: 0.158s
Is there a solution without s-off
Tried Stock rom:
RUU_M8_UL_L50_SENSE60_MR_BrightstarUS_WWE_4.16.154 0.8_Radio_1.24.21331147A1.09G_20.68.4196.01_F_rele ase_411207_signed.exe
RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Ra dio_1.25.214500021.06G_20.68.4196t.01_F_release_41 7003_signed.exe
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.154 0.4.exe
with bootloader locked/unlocked state;
with s-on:
Failed
Tried zip
0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4 _Radio_1.29.214500021.12G_20.72.4196t.01_release_4 64360_signed.zip
Failed
Tried nandroid backup
M8_UL_TWRP_Nandroid_6.12.401.4.zip
succefully flashed backup but stuck on htc logo
Failed
Please help

What is the problem? Is it not booting into the ROM?

when there was boot.the phone at the startup gave (unfortunately------- has stopped)error and also no back key home key visible.
wiped the device. it was all same.
tried RUU it was the same
unlocked the boot loader
and flashed
stock recovery
twrp recovery
then tried nandroid backup restore
the restore was succefull but the phone wont reach startup (tried 1Hour max)
one peculiar thing i notice.earlier when it was booting to startup i was unable to copy anything to internal or external memory as it would say device not ready or disconnected.but i was able to browse the folders.
My opinion partition problem.Need others help to sort out
Note all the files i have mentioned is checked with md5

My comments below in red font:
raffazila said:
Tried Stock rom:
RUU_M8_UL_L50_SENSE60_MR_BrightstarUS_WWE_4.16.154 0.8_Radio_1.24.21331147A1.09G_20.68.4196.01_F_rele ase_411207_signed.exe
RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Ra dio_1.25.214500021.06G_20.68.4196t.01_F_release_41 7003_signed.exe
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.154 0.4.exe
None of these will ever work on your device, in the s-on configuration. The RUUs containing "BrightstarUS" are for the US Developer's Edition. They won't run on your phone, as they will fail CID and MID checks (your device has CID and MID - can't change these with s-on).
The one labeled "Europe" is for an older version (Lollipop) than what is installed on the phone (Marshmallow). This will fail version check. By definition, you can't "downgrade" by RUU with s-on
with bootloader locked/unlocked state;
with s-on:
Failed
with s-on, its absolutely mandatory to have a locked or relocked bootloader to flash RUU. Unlocked bootloader will make it fail
Tried zip
0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4 _Radio_1.29.214500021.12G_20.72.4196t.01_release_4 64360_signed.zip
Failed
This is the correct RUU for your version, and should run with s-on. Saying it "Failed" with no other info, is not enough. Were their any error messages, other outputs, etc.? What commands did you use to run it? Were you in fastbootRUU mode?
I would suggest trying to run this again, with the bootloader RELOCKED, and you also need to use htc_fastboot, as the "generic" fastboot will not work with RUU.
Click to expand...
Click to collapse

Firstly it is good someone with good knowledge is answering my doubts.
Secondly i want to tell you something which i noticed in most of the forum is irrelevant posts.I want to avoid those kind of post.
Finaly to say you have found the nearest problem which i was thinking too.
I will check and post.

@redpoint73 Problem soilved.Silly mistake.Thanks.

raffazila said:
Secondly i want to tell you something which i noticed in most of the forum is irrelevant posts.I want to avoid those kind of post.
Click to expand...
Click to collapse
I can't tell what you are referring too, as the statement is really vague. Can you give more details?
---------- Post added at 09:31 AM ---------- Previous post was at 09:28 AM ----------
raffazila said:
Problem soilved.Silly mistake.Thanks.
Click to expand...
Click to collapse
Its best if you posted the solution, and what the mistake was. Useful for those helping (to see whether we sent you on the right path), as well as anyone else reading which may have the same or similar issue.
No mistake is that silly when it comes to these devices. Its often just specific knowledge that was missing, or a detail you didn't catch before (which is an honest mistake, either way).