Database Develop

Updating and restoring to stock issues

I have an HTC One by T-Mobile, Our update was released Monday. I tried to update but when it rebooted it went to install and failed to install, I looked up some information that say usually the cause of the failed install for software system updates is because of an unlocked bootloader and custom recovery. So I've tried to restore to factory OEM settings but every time it fails to up restore to the factory update as well. I'm at a loss here and no Idea what to do. I can flash any custom roms I want and those seem to work and flash just fine but If I try anything else like reverting to OEM stock it doesn't work. Anyone have any Ideas?
Before anyone asks, I've tried doing a RRU restore from desktop and .Zip on my phone and neither work. Both fail.

TaintedCross said:
I have an HTC One by T-Mobile, Our update was released Monday. I tried to update but when it rebooted it went to install and failed to install, I looked up some information that say usually the cause of the failed install for software system updates is because of an unlocked bootloader and custom recovery. So I've tried to restore to factory OEM settings but every time it fails to up restore to the factory update as well. I'm at a loss here and no Idea what to do. I can flash any custom roms I want and those seem to work and flash just fine but If I try anything else like reverting to OEM stock it doesn't work. Anyone have any Ideas?
Before anyone asks, I've tried doing a RRU restore from desktop and .Zip on my phone and neither work. Both fail.
Click to expand...
Click to collapse
Get s-off and restore any RUU.. After restore, better get s-off before you update, you won't be able to get it after the update.
Sent from my iPod touch using Tapatalk

TaintedCross said:
I have an HTC One by T-Mobile, Our update was released Monday. I tried to update but when it rebooted it went to install and failed to install, I looked up some information that say usually the cause of the failed install for software system updates is because of an unlocked bootloader and custom recovery. So I've tried to restore to factory OEM settings but every time it fails to up restore to the factory update as well. I'm at a loss here and no Idea what to do. I can flash any custom roms I want and those seem to work and flash just fine but If I try anything else like reverting to OEM stock it doesn't work. Anyone have any Ideas?
Before anyone asks, I've tried doing a RRU restore from desktop and .Zip on my phone and neither work. Both fail.
Click to expand...
Click to collapse
you need to flash the stock recovery and lock your bootloader to be able to do the update.

[email protected] said:
you need to flash the stock recovery and lock your bootloader to be able to do the update.
Click to expand...
Click to collapse
I'm pretty sure you don't need to relock the bootloader for OTAs, you do however need 100% stock ROM and (a very close) stock recovery for that ROM.

nkk71 said:
I'm pretty sure you don't need to relock the bootloader for OTAs, you do however need 100% stock ROM and (a very close) stock recovery for that ROM.
Click to expand...
Click to collapse
i stand corrected.
a stock recovery will do

[email protected] said:
i stand corrected.
a stock recovery will do
Click to expand...
Click to collapse
Only for OTAs, to run a full RUU exe, I do think the bootloader has to be locked/relocked

nkk71 said:
Only for OTAs, to run a full RUU exe, I do think the bootloader has to be locked/relocked
Click to expand...
Click to collapse
Not going to matter anyway, I accidently wiped my whole OS. I've tried using adb Sideload but it wont detect my device.

TaintedCross said:
Not going to matter anyway, I accidently wiped my whole OS. I've tried using adb Sideload but it wont detect my device.
Click to expand...
Click to collapse
Restart your computer, also update to latest HTC drivers and adb sdk.
Alternate method, use an OTG cable with a USB stick with a ROM.ZIP on it, and mount "external sdcard" (or whatever it's called) in custom recovery.

nkk71 said:
Restart your computer, also update to latest HTC drivers and adb sdk.
Alternate method, use an OTG cable with a USB stick with a ROM.ZIP on it, and mount "external sdcard" (or whatever it's called) in custom recovery.
Click to expand...
Click to collapse
I have restarted like 20 times, still doesn't detect it. And I don't have an OTG cable

TaintedCross said:
I have restarted like 20 times, still doesn't detect it. And I don't have an OTG cable
Click to expand...
Click to collapse
Does fastboot work?
Sent from my HTC One using Tapatalk

nkk71 said:
Does fastboot work?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I can boot into fastboot on my phone but I've no idea what to do from there.
Edit: HELLS YEAH! I got it! lol had to relock bootloader using fastboot and then go back into fastboot on my phone and run the RUU.exe and it worked this time! SOOO freaking stoked and happy! I've been up for 7 hours straight trying to fix this!

Nice. Please update the thread and put SOLVED
Sent from my HTC One using xda app-developers app

No OS on phone, can't install a rom

I am hoping someone can help with this, my son completely wiped his Google Edition HTC One. When I asked him what he did he stated that he flashed TWRP and did a full wipe checking all of the boxes under the advanced tab. Then when he tried to flash Cyanogenmod 10.2 it keeps failing. I asked him why he did this and he said his friend told him how cool Cyanogenmod is so naturally he want it to! (By the way my son is 13).
I know very little about this phone but I would like to get the phone back to the way it was before he messed with it as it cost me $650 to buy it. I started reading about RUU files but from what I can tell the RUU will not work with S-ON. And I can't seem to flash any ROM as it keeps failing. Any suggestions would be a big help!

Don't worry this is fixable
First relock your bootloader
Then download a RUU.zip for GPe
boot into fastboot
and type this command (in your pc of course with adb) fastboot oem rebootRUU
A silver htc logo should show
copy the RUU you downloaded to your adb folder and rename to ruu.zip
and type this command fastboot flash zip ruu.zip
this command should be typed twice (ignore the error that shows up)
after the second time it's done
type fastboot reboot
should turn right up
Good luck

Then make him use a flip phone for a week as punishment lol

I had the same. In my case I started ruu for another version (international), of course ruu failed to install but it did fix partitions, after that I was able to sideload rom. I will try to find my topic and provide You with my solution.
This is my BLS/ALS with HTC One, patient is alive and well now, only camera has pink tint...
http://forum.xda-developers.com/showthread.php?t=2322851
Try with CWM instead of TWRP... and finally pass some information about progress.

Thealshear said:
Don't worry this is fixable
First relock your bootloader
Then download a RUU.zip for GPe
boot into fastboot
and type this command (in your pc of course with adb) fastboot oem rebootRUU
A silver htc logo should show
copy the RUU you downloaded to your adb folder and rename to ruu.zip
and type this command fastboot flash zip ruu.zip
this command should be typed twice (ignore the error that shows up)
after the second time it's done
type fastboot reboot
should turn right up
Good luck
Click to expand...
Click to collapse
Will the ruu method work if the phone is S-ON? All of the XDA posts I read state that you need to be S-OFF?

Give it a shot the phone is already bricked what you got to lose

crixley said:
Then make him use a flip phone for a week as punishment lol
Click to expand...
Click to collapse
For now until I can fix the phone he is back to two cans and string!
Sent from my Nexus 5 using Tapatalk

woody970 said:
For now until I can fix the phone he is back to two cans and string!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
You can run an ruu but it has to be newer..
See here:
http://forum.gsmhosting.com/vbb/f485/understanding-s-off-super-cid-s-read-b4-u-run-ruu-1505916/

crixley said:
You can run an ruu but it has to be newer..
Any idea where to download the RUU? The build number that was on the phone before all this started was KRT16S.H5 release-keys
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse

woody970 said:
I am hoping someone can help with this, my son completely wiped his Google Edition HTC One. When I asked him what he did he stated that he flashed TWRP and did a full wipe checking all of the boxes under the advanced tab.
Click to expand...
Click to collapse
The good news are that the phone isn't bricked, imho. The bad ones are that you will have to play with ROMs recoveries and RUU's a bit in order to have a working phone back. First of all I would focus to succeed in flashing a ROM in order to boot your phone. Googling I found a user with your same error showed in the pic that solved the issue "checking the signature box then flash a ROM where he got the error then unchecked the same signature box and reflash with success". If this process doesn't work for you, I suggest to flash a different recovery such as CWM and try to flash the ROM through it. Anyway you'll need an unlocked bootloader for the entire process. Let me know if you succeed.
Sent from my HTC One using Tapatalk

Delgra said:
The good news are that the phone isn't bricked, imho. The bad ones are that you will have to play with ROMs recoveries and RUU's a bit in order to have a working phone back. First of all I would focus to succeed in flashing a ROM in order to boot your phone. Googling I found a user with your same error showed in the pic that solved the issue "checking the signature box then flash a ROM where he got the error then unchecked the same signature box and reflash with success". If this process doesn't work for you, I suggest to flash a different recovery such as CWM and try to flash the ROM through it. Anyway you'll need an unlocked bootloader for the entire process. Let me know if you succeed.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
when your son was flashing CM mod was he using the correct version? I don't recall but I tried flashing my ATT HTC one but I am running a WWE firmware so that made me have to flash the GSM version of CM mod. http://www.cmxlog.com/11/m7ul/ Try downloading the latest zip file there and than try mounting to his phone with the USB mount or if you have a USB OTG you can install it from a USB. It shouldn't matter if your S-ON or S-OFF for installing some roms it just helps you avoid taking extra steps to get the ROM to install.
When your flashing with TWRP make sure to do a advanced wipe and check everything that is on there. After you do a advanced wipe do a regular factory reset. I'm hoping that the new CM11 rom will flash for his phone. You can also use ADB sideload to send the zip files over to your phone if you cannot mount the phone. What ADB sideload does is open up a connection from your phones USB and lets you transfer zips over onto the internal SD card basically in DOS command.

I want to thank everyone for there guidance in this. After googling for a couple of days and a few failed attempts with the RUU command I was finally able to restore the phone. I was able to flash a nandroid backup using TWRp from another google edition HTC which brought the phone back to life. Then I flashed a stock recovery and OTA's became available to the phone. The once dead HTC is now back up and running stock 4.4 android. The only issue I with the phone now is that there is a popping sound after a notification comes in that I can't get rid of... Anyone have any ideas?
Sent from my Nexus 5 using Tapatalk

The popping noises seem to come after I updated to kit Kat I don't know but a lot of people might have that issue too.
Sent from my HTC One using Tapatalk

How do I fix my phone?

I successfully had Cyanogenmod installed, but now when I turn my phone on it stays stuck at the loading screen and goes back and forth to the HTC start up (the screen before the Cyanogen loading screen). I tried reverting back to stock using the RUU but it fails every. single. time. and there's nothing I can find that will help me at least get my phone back working.
Any help? My carrier is T-Mobile

moneyhbags said:
I successfully had Cyanogenmod installed, but now when I turn my phone on it stays stuck at the loading screen and goes back and forth to the HTC start up (the screen before the Cyanogen loading screen). I tried reverting back to stock using the RUU but it fails every. single. time. and there's nothing I can find that will help me at least get my phone back working.
Any help? My carrier is T-Mobile
Click to expand...
Click to collapse
Sounds like possibly you need to flash the boot.img on it. I think , a senior member will correct me, but if your S-On and rooted, you should do that , S-Off don't require the boot.img.

leesumm said:
Sounds like possibly you need to flash the boot.img on it. I think , a senior member will correct me, but if your S-On and rooted, you should do that , S-Off don't require the boot.img.
Click to expand...
Click to collapse
I don't know what S-On or S-Off means, but it's been like 20 minutes and it's now stuck at the HTC quietly brilliant screen.
I did do a back-up before I rooted it. I tried re-installing Cyanogenmod but the installer says my phone is unrecognizable.
edit: still stuck at Cyanogen loading screen =(

moneyhbags said:
I don't know what S-On or S-Off means, but it's been like 20 minutes and it's now stuck at the HTC quietly brilliant screen.
I did do a back-up before I rooted it. I tried re-installing Cyanogenmod but the installer says my phone is unrecognizable.
edit: still stuck at Cyanogen loading screen =(
Click to expand...
Click to collapse
S-ON or off means security is on or off, If you haven't done the mod to S-Off , your still stock S-On. To see for sure though , in the bootloader mode at the top it will say Tampered first line , then the second should say something like M7 ??? PVT ship. S-On
What recovery are you using? CWM or TWRP . Do you know or use ADB?
I just reread your OP and you said you RUU'd. why? I think too with S-On you have to relock the bootloader to RUU then unlock after boot. You can use the same unlock.bin code that you used to unlock the first time if you still have it too . Best if you done the root and everything else , do some reading on S-Off procedure and do that .

leesumm said:
S-ON or off means security is on or off, If you haven't done the mod to S-Off , your still stock S-On. To see for sure though , in the bootloader mode at the top it will say Tampered first line , then the second should say something like M7 ??? PVT ship. S-On
What recovery are you using? CWM or TWRP . Do you know or use ADB?
Click to expand...
Click to collapse
Just checked, it's Tampered, Unlocked, M7, and S-On.
I used CWM for recovery and I have ADB.

moneyhbags said:
Just checked, it's Tampered, Unlocked, M7, and S-On.
I used CWM for recovery and I have ADB.
Click to expand...
Click to collapse
I have had better luck with TWRP the latest one which is I think 2.6.3.

leesumm said:
I have had better luck with TWRP the latest one which is I think 2.6.3.
Click to expand...
Click to collapse
Yeah well I'll switch to that once I figure out how to get my phone to at least start working...
any help?

moneyhbags said:
Just checked, it's Tampered, Unlocked, M7, and S-On.
I used CWM for recovery and I have ADB.
Click to expand...
Click to collapse
I had the same problem like you... I have installed first twrp 2.6.3.3 then root the VIPER ROM, so I finelly got into the phone... Then I have flashed again vith ARHD 41.0 ROM and my phone is working perfect But I had the same problem as you... this is becouse of the S-ON and you stuck in boot-loop

moneyhbags said:
Yeah well I'll switch to that once I figure out how to get my phone to at least start working...
any help?
Click to expand...
Click to collapse
IF you can get to recovery, do you have a backup that is working ? If not you may have to unzip the CM rom, look for the boot.img , put that into the adb folder then run adb with fastboot flash boot.img , then reboot and it should go. If you have a back up of the Cm rom you might be able to go to recovery and do a restore from the backup there. And another thing you might do. Not sure if it will mess it up but/ fastboot erase cache then boot

peca_slo said:
I had the same problem like you... I have installed first twrp 2.6.3.3 then root the VIPER ROM, so I finelly got into the phone... Then I have flashed again vith ARHD 41.0 ROM and my phone is working perfect But I had the same problem as you... this is becouse of the S-ON and you stuck in boot-loop
Click to expand...
Click to collapse
I just fixed it. I downloaded the stock T-Mobile recovery.img for HTC One, then opened the command line used fastboot uploaded the recovery.img then used that to recover and it just magically reinstalled the Cyanogenmod.

moneyhbags said:
I just fixed it. I downloaded the stock T-Mobile recovery.img for HTC One, then opened the command line used fastboot uploaded the recovery.img then used that to recover and it just magically reinstalled the Cyanogenmod.
Click to expand...
Click to collapse
Good glad to know it works again.. Now do some reading on S-Off sounds like you have some idea of ADB so it really isn't that hard and it will make flashing easier in the future. You might even consider a full GPE conversion. I did it and like the Kit Kat but running Elegancia and once in a while revert back to the GPE with Xposed and Gravity Box KK for a mod. Super good battery.

moneyhbags said:
Yeah well I'll switch to that once I figure out how to get my phone to at least start working...
any help?
Click to expand...
Click to collapse
boot to recovery
clear cache and delvik
reboot to bootloader
fastboot USB and type
fastboot erase cache
now see if your phone will bootup
If no, find a different rom to flash
and here is a recovery flashable version of TWRP, flash it the same you do a rom and reboot to recovery to see it

moneyhbags said:
I just fixed it. I downloaded the stock T-Mobile recovery.img for HTC One, then opened the command line used fastboot uploaded the recovery.img then used that to recover and it just magically reinstalled the Cyanogenmod.
Click to expand...
Click to collapse
whoops looks like i got here late ..

Stuck in boot loop and soft brick

My friend's phone is stuck in bootloop and I believe it's soft bricked.
It's a stock brand new HTC One M7.
It was updating one day and he said it might have got corrupted because it just shut down and when it booted back up it was stuck at the HTC Screen and wouldn't do anything.
Over the last week I have been trying to unbrick it.
It's LOCKED and S-ON Sprint HTC One M7.
I did a factory reset, wiped cache, dalvic cache, reboot. I tried putting in fastboot and flashing RUU on it but it kept failing because the RUU I had was a lower version of the image than the current one on the phone and I read online that I can only flash backwards if it's S-OFF.
Any help?
Thanks!

technocrat7 said:
My friend's phone is stuck in bootloop and I believe it's soft bricked.
It's a stock brand new HTC One M7.
It was updating one day and he said it might have got corrupted because it just shut down and when it booted back up it was stuck at the HTC Screen and wouldn't do anything.
Over the last week I have been trying to unbrick it.
It's LOCKED and S-ON Sprint HTC One M7.
I did a factory reset, wiped cache, dalvic cache, reboot. I tried putting in fastboot and flashing RUU on it but it kept failing because the RUU I had was a lower version of the image than the current one on the phone and I read online that I can only flash backwards if it's S-OFF.
Any help?
Thanks!
Click to expand...
Click to collapse
if the phone is new (never tampered with) and still under warranty, send it back for repair or replacement
s-off and run the ruu
unlock bootloader, flash a custom recovery and flash a rom or a nandroid backup
post in the sprint htc one forum for more detailed info

So the first step is S-OFF because I don't think k the warranty is on it.
And then custom recovery and what was the part with a custom nandroid backup? Can I run someone else's nandroid?
And if I put S-OFF on it, I can flash an older version of RUU right?
Sent from my HTC One_M8 using XDA Free mobile app

I'm pretty sure that in order to S-off you will need to be booted up first? The good news is that you can flash the full factory RUU with a s-on boot loader locked device so you may need to figure out how to do that first. Do you have an adb/fastboot environment set up? If so you are practically there. On a side note, I have seen no less than 3 m7s fail and softbrick on the first attempt at applying an ota, but it was always after S-off and a conversion to fully stock gpe (these were gsm models). I figured it was just because of the mods but who knows. Anyway, if you can locate and install a fully stock sprint RUU you should be back to where you were before the ota at which point you can proceed with whatever else you want to do.

technocrat7 said:
So the first step is S-OFF because I don't think k the warranty is on it.
And then custom recovery and what was the part with a custom nandroid backup? Can I run someone else's nandroid?
And if I put S-OFF on it, I can flash an older version of RUU right?
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
sorry for the confusion, this was not steps to follow (1-2-3-4) but either 1 or 2 or 3 or 4
if you go for option 2, yes you can flash older ruu.
for option 3, yes you can flash someone else nandroid, but it must be for your phone variant (sprint) and the ideal nandroid backup should be the same OS version.
---------- Post added at 02:34 PM ---------- Previous post was at 02:29 PM ----------
dougeedug said:
I'm pretty sure that in order to S-off you will need to be booted up first?
Click to expand...
Click to collapse
Right, you need a booted rom to s-off. (at least for the M7_UL dont know for the srpint variant)
The good news is that you can flash the full factory RUU with a s-on boot loader locked device so you may need to figure out how to do that first.
Click to expand...
Click to collapse
Not exactly, you can only flash ruu with a s-on device (and locked/relocked bootloader) if the ruu is same of higher version. In that case the OP need to find another ruu (if any available)

Yeah, I have a 4.2 image when loading RUU, therefore I'm not able to use an RUU.
So what else do I need to do?
And I do have an adb and fastboot environment set up, yes.
Should I instead just S-OFF It, put a custom bootloader on it and then flash a custom recovery?

Yes if you can achieve s-off you can put any RUU you want on it and that will rule out software issues.

Okay so I unlocked it.
However I looked online how to do S-OFF and all the articles I found said the phone has to be on an functional to enable USB debugging mode and to run the appropriate programs to make it S-OFF.
Is there any other way to do it?

Now that you are bootloader unlocked, flash a custom recovery and from there a rom. That should get you back to life so you can proceed however you wish.

I have a custom recovery.
TWRP 2.6.0.0 or something. And I loaded into it and my phone got stuck and the touch wouldn't work. It says "slide to unlock" and sliding doesn't work.
What do I do now? I can't even reboot the light keeps flashing and I even tried under a bright light and still nothing.
I'm letting the battery die to restart. When u do restart it, what do I do about the bad bootloader? Can I just put another one on there? I want Philz now after that terrible experience.

technocrat7 said:
I have a custom recovery.
TWRP 2.6.0.0 or something. .
Click to expand...
Click to collapse
This is very alarming! Be double sure you are flashing exactly what you need. The CWM you would need is 6.0.4.8 found on this page. I'm not sure what TWRP version is suitable as I don't use it. I don't dislike it. I have used it and it has worked.

Can I just do the same thing I did before to install a custom recovery?
Will it override the one I have currently?
Thanks!

technocrat7 said:
Can I just do the same thing I did before to install a custom recovery?
Will it override the one I have currently?
Thanks!
Click to expand...
Click to collapse
We will have to see what it does after you let it die. The way your phone is acting is not good. Unfortunately, we must keep in mind that it may be a hardware fault causing all of this from the start. If it will still charge offline, then you'll get a chance to see if you can power it up into the bootloader and get fastbootUSB.

technocrat7 said:
Can I just do the same thing I did before to install a custom recovery?
Will it override the one I have currently?
Thanks!
Click to expand...
Click to collapse
why are you waiting for it to die ? if you want to get out of recovery and tough isn't working, just hold down the power button and the volume down until the lights on the bottom flash 10 to 15 times, when it goes off, release the power button but continue to hold the volume down, you are now in the bootloader, or should be.
and yes, if you flash another recovery it will overwrite the one that's on there, unfortunately, most rom's require TWRP
---------- Post added at 03:28 AM ---------- Previous post was at 03:22 AM ----------
I also just noticed you have the Sprint M7, you cant use the normal recoveries or rom's, they wont work, you need to use the ones built for your phone, which is different to the normal gsm version.

I would try twrp 2.6.3.3 or this http://mdmower.cmphys.com/twrp-m7spr/ a newer custom compiled twrp so your os version dont get wiped on bootloader.

Dang, being with Sprint complicates things?
So will that one be safe to put on my phone? And that means I can't get Philz huh?

technocrat7 said:
Dang, being with Sprint complicates things?
So will that one be safe to put on my phone? And that means I can't get Philz huh?
Click to expand...
Click to collapse
No it doesn't complicate things, it's the same procedure, it's like with anything, you just have to make sure you get the right files. Your phone is cdma not gsm.
---------- Post added at 04:28 AM ---------- Previous post was at 04:17 AM ----------
http://forum.xda-developers.com/sprint-htc-one?nocache=1&z=1858146956656128
You can find all of those right files there

Okay thank you!
It is unlocked, rooted and had a custom recovery on it!
Now the last thing I need help with is, getting S-OFF because I still can't boot up the phone.
So now I just need to get S-OFF and then flash a custom ROM image on there and flash a custom image on it or something.
All I see when it boots up is the HTC screen.

technocrat7 said:
Okay thank you!
It is unlocked, rooted and had a custom recovery on it!
Now the last thing I need help with is, getting S-OFF because I still can't boot up the phone.
So now I just need to get S-OFF and then flash a custom ROM image on there and flash a custom image on it or something.
All I see when it boots up is the HTC screen.
Click to expand...
Click to collapse
You need a working Rom on it to go s-off, all s-off tools are run from an android booted phone, so download a Rom of your choice, in your case a sense Rom, make sure you get it from the link I supplied earlier for your particular phone, move it to the same folder where your adb and fastboot are on your computer, boot your phone into recovery (main screen only, no sub menus) and plug it into your computer, the type
adb push NAME_OF_ROM.zip /sdcard/
Takes a while so be patient, the command window will let you know when it's done.
Unplug your phone and in recovery select install, select your Rom from the list and follow the instructions

Seanie280672 said:
You need a working Rom on it to go s-off, all s-off tools are run from an android booted phone, so download a Rom of your choice, in your case a sense Rom, make sure you get it from the link I supplied earlier for your particular phone, move it to the same folder where your adb and fastboot are on your computer, boot your phone into recovery (main screen only, no sub menus) and plug it into your computer, the type
adb push NAME_OF_ROM.zip /sdcard/
Takes a while so be patient, the command window will let you know when it's done.
Unplug your phone and in recovery select install, select your Rom from the list and follow the instructions
Click to expand...
Click to collapse
So there's a slight problem.
"ADB Devices" doesn't show anything, it says "Devices not found"
The reason I would say is because it does not have USB Debugging enabled.
And I can't get into the phone to enable it because i'm not at that point yet.
Is there anything else I can do besides "adb push" to get the file on there?
Fastboot stuff works fine.
I went to the link you provided and found CynogenMod 11 I wanted to put on there.
After looking inside of the ZIP I downloaded there's a .img file inside called "boot.img" can I do anything with that?
Thanks!

M7 Totally Messed up

I really messed my phone up its got no OS and its stuck in bootloop iv tried pushing cm-12 onto it and installing it but i keep getting error codes with what you see in the picture. can anyone help.

Burky1996 said:
I really messed my phone up its got no OS and its stuck in bootloop iv tried pushing cm-12 onto it and installing it but i keep getting error codes with what you see in the picture. can anyone help.
Click to expand...
Click to collapse
Try re download the zip (or try an other rom)maybe you just got an false download. i also had some trouble with my m7 back in the day.
But in your case now you are stuck with no os or bootloop, i give you as advice to follow an soft unbrick method it worked for me, or if you have an usb otg cable and usb or and usb otg thumbstick, put the rom on that usb and connect it to your phone and then try to flash it (if your using twrp you have an option to choose from wich storage you want to use)
Also a piece of advice, when flashing roms, kernels etc please have your phone charged above 50% (just in case).
Sent from my HUAWEI P7-L10 using XDA Free mobile app
---------- Post added at 09:28 PM ---------- Previous post was at 09:27 PM ----------
its the peanut said:
Try re download the zip (or try an other rom)maybe you just got an false download. i also had some trouble with my m7 back in the day.
But in your case now you are stuck with no os or bootloop, i give you as advice to follow an soft unbrick method it worked for me, or if you have an usb otg cable and usb or and usb otg thumbstick, put the rom on that usb and connect it to your phone and then try to flash it (if your using twrp you have an option to choose from wich storage you want to use)
Also a piece of advice, when flashing roms, kernels etc please have your phone charged above 50% (just in case).
Sent from my HUAWEI P7-L10 using XDA Free mobile app
Click to expand...
Click to collapse
Also make sure you downloaded the rom made for your phone model!
Sent from my HUAWEI P7-L10 using XDA Free mobile app

Burky1996 said:
I really messed my phone up its got no OS and its stuck in bootloop iv tried pushing cm-12 onto it and installing it but i keep getting error codes with what you see in the picture. can anyone help.
Click to expand...
Click to collapse
Can you please post the output of
Code:
fastboot getvar all
please remove your imei and serial number.
Depending on which variant of the M7 you have you probably just need a different version of recovery to install a CM rom. I think they prefer TWRP 2.7.x.x. Post the getvar and we can see what you have. then I can give you a better informed instruction. :good:
P.s also check the md5 of the rom zip you downloaded. Use this tool www.winmd5.com the correct md5 should be listed with the link you downloaded the rom from

failed to mount /dev/block/blah blah blah = needs "block:by-name" support which twrp 2.6.3.3 doesn't have
everything explained here
So update your recovery
and do what danny said above so he can confirm you have the right rom/recovery for your device.

Burky1996 said:
I really messed my phone up its got no OS and its stuck in bootloop iv tried pushing cm-12 onto it and installing it but i keep getting error codes with what you see in the picture. can anyone help.
Click to expand...
Click to collapse
Your getvar looks fine this rom should work fine with your device. Download this version of TWRP https://www.androidfilehost.com/?fid=23501681358561860 (2.7.1.2). dropthe file in your fastboot folder and flash it with fastboot.
Code:
fastboot flash recovery "name-of-recovery".img
fastboot erase cache
fastboot reboot-bootloader
Once thats done reflash the rom with the new version of TWRP. It should flash just fine :good:

iv managed to flash cm12.1 now, thanks guys, is there anyway i could get the HTC software back on.

Burky1996 said:
iv managed to flash cm12.1 now, thanks guys, is there anyway i could get the HTC software back on.
Click to expand...
Click to collapse
There are a number of ways to return to stock software. You can simply flash a stock rom through twrp or use a stock nandroid. look for rom that match your version main. 7.19.401.22
I think there is even an lollipop 7.19.401.22 RUU for your device but I'm not sure if it will work with s-on though because it's a zip but it certainly wouldnt hurt to try it though. You will need to relock your bootloader and flash it with fastboot.
I'll edit this post with links when I find them unless some one beats me to it

Hey Dan do you think we could skype and you could talk me through it, it would be much easier?

Burky1996 said:
Hey Dan do you think we could skype and you could talk me through it, it would be much easier?
Click to expand...
Click to collapse
Sorry I am at work so availability is scetchy. I found the ruu but it's for the older 7.19.401.2 lollipop, this won't work for you because your s-on. Downgrading firmware is only possible with s-off.
You can use this stock rom though http://forum.xda-developers.com/htc-one/development/rom-100-pure-stock-5-0-2-7-19-401-2-t3044041 just flash it with twrp. The thread recommends TWRP 2.8.5.X no need to relock the bootloader or anything silly, just flash it like any other rom :good:
You'll notice that this rom is also for the older 7.19.401.2 so you will need to install the last OTA update to bring your rom in line with your firmware. Flash this recovery with the same method as twrp. (Stock recovery required for installing the OTA) http://sourceforge.net/projects/htcone/files/Recovery/STOCK/7.19.401.2_recovery.img/download reboot then just go to Settings>About>Check for updates.

Danny201281 said:
Sorry I am at work so availability is scetchy. I found the ruu but it's for the older 7.19.401.2 lollipop, this won't work for you because your s-on. Downgrading firmware is only possible with s-off.
You can use this stock rom though http://forum.xda-developers.com/htc-one/development/rom-100-pure-stock-5-0-2-7-19-401-2-t3044041 just flash it with twrp. The thread recommends TWRP 2.8.5.X no need to relock the bootloader or anything silly, just flash it like any other rom :good:
You'll notice that this rom is also for the older 7.19.401.2 so you will need to install the last OTA update to bring your rom in line with your firmware. Flash this recovery with the same method as twrp. (Stock recovery required for installing the OTA) http://sourceforge.net/projects/htcone/files/Recovery/STOCK/7.19.401.2_recovery.img/download reboot then just go to Settings>About>Check for updates.
Click to expand...
Click to collapse
i did what you said when i applied the system update my phone turned on booted to a white screen with the green htc logo then it turned off the battery symbol came up its like its turned off. i tryed to lock the boot loader to see if it would work then but it never, when i appy the update it dosent even boot into the recovery.

i did what you said when i applied the system update my phone turned on booted to a white screen with the green htc logo then it turned off the battery symbol came up its like its turned off. i tryed to lock the boot loader to see if it would work then but it never, when i appy the update it dosent even boot into the recovery.

Burky1996 said:
i did what you said when i applied the system update my phone turned on booted to a white screen with the green htc logo then it turned off the battery symbol came up its like its turned off. i tryed to lock the boot loader to see if it would work then but it never, when i appy the update it dosent even boot into the recovery.
Click to expand...
Click to collapse
Okay try this. Download the OTA but select the option "Install Later" connect your m7 to your pc and browse your storage. In the download folder on your phone you should find the OTA in zip format. Copy it to your pc.
Now open the OTA zip on your pc. Inside you'll find another zip called "firmware.zip" extract it then open it. Inside you'll find a recovery.img. extract the recovery file and flash it with fastboot. Now reboot to android and continue to install the OTA. :fingers-crossed:
Sent from my SM-T230 using Tapatalk

im going to have to unlock the boot loader again and then do it

Burky1996 said:
im going to have to unlock the boot loader again and then do it
Click to expand...
Click to collapse
Yes you will need to unlock the bootloader to flash the recovery, Dont forget to fastboot erase cache after flashing the recovery that is cruicial. You don't need to be relocked to install the OTA though.
When you select install now, the device should reboot to the Stock Recovery. At first the screen will just be black for a short while. Then you'll see an image of a phone with a Green ring and download arrow. If you hold Volume up and press the power button you will see the Stock Recovery and its progress in installing the OTA.
I'm not sure why your device was hanging on boot after installing the OTA. Maybe a bad recovery.img. that's why I say to get the recovery from the OTA file.

its still not working so i mite just install twrp and restore to cm12.1

Burky1996 said:
im going to have to unlock the boot loader again and then do it
Click to expand...
Click to collapse
Yes you will need to unlock the bootloader to flash the recovery, Dont forget to fastboot erase cache after flashing the recovery that is cruicial. You don't need to be relocked to install the OTA though.
When you select install now, the device should reboot to the Stock Recovery. At first the screen will just be black for a short while. Then you'll see an image of a phone with a Green ring and download arrow. If you hold Volume up and press the power button you will see the Stock Recovery and its progress in installing the OTA.
I'm not sure why your device was hanging on boot after installing the OTA. Maybe a bad recovery.img. that's why I say to get the recovery from the OTA file.

Danny201281 said:
Sorry I am at work so availability is scetchy. I found the ruu but it's for the older 7.19.401.2 lollipop, this won't work for you because your s-on. Downgrading firmware is only possible with s-off.
You can use this stock rom though http://forum.xda-developers.com/htc-one/development/rom-100-pure-stock-5-0-2-7-19-401-2-t3044041 just flash it with twrp. The thread recommends TWRP 2.8.5.X no need to relock the bootloader or anything silly, just flash it like any other rom :good:
You'll notice that this rom is also for the older 7.19.401.2 so you will need to install the last OTA update to bring your rom in line with your firmware. Flash this recovery with the same method as twrp. (Stock recovery required for installing the OTA) http://sourceforge.net/projects/htcone/files/Recovery/STOCK/7.19.401.2_recovery.img/download reboot then just go to Settings>About>Check for updates.
Click to expand...
Click to collapse
could it be not working coz my hboot has changed to 1.51.

Burky1996 said:
could it be not working coz my hboot has changed to 1.51.
Click to expand...
Click to collapse
Your still stuck with this? Try starting the process over, but do not relock your bootloader at any point.
Wipe system data and cache partitions with TWRP Advanced wipe
Flash the Rom with twrp as a clean install.
Reboot and download the OTA. Choose install later, then copy the OTA to your pc. Extract the Stock Recovery and flash it with fastboot. Reboot and install the OTA.
But do not relock your boot loader. Because when you unlock the bootloader, it wipes the device including the data/preload folder. If the preload folder is not intact the OTA will fail
Sent from my M7 Running ARHD 92.x