Database Develop

[Q] Unable to install software update

I have the HTC One Dev edition and have unrooted the device and installed RUU so I can apply OTA updates. The problem is when I try to apply OTA update to 1.29.1540.17 the phone reboots to Fastboot. Bootloader shows Tampered relocked Hboot is at version 1.44.0000. If I reboot the phone it's not updated and is asking me to install update again. I would like to install this update and stay unrooted so I can receive the update to 4.2.2 which should be coming shortly.
Any help would be greatly appreciated.

You've the stock recovery, right?

As far as I know. I ran the ruu utility from the htc dev site which is supposed to return the phone to stock. If that's not the case then maybe not.

The ruu only restores stock ROM only ,but you have to flash stock kernel and recovery manually

tonztime said:
I have the HTC One Dev edition and have unrooted the device and installed RUU so I can apply OTA updates. The problem is when I try to apply OTA update to 1.29.1540.17 the phone reboots to Fastboot. Bootloader shows Tampered relocked Hboot is at version 1.44.0000. If I reboot the phone it's not updated and is asking me to install update again. I would like to install this update and stay unrooted so I can receive the update to 4.2.2 which should be coming shortly.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Hey, RUUs generally flash stock recovery!!
I got the problem,
You have htcDEV edition
So your bootloader UNLOCKED initially right??
So i think you should keep it unlocked
Try and reply what happens
HIT THANKS IF I HELPED YOU

prunzzz said:
Hey, RUUs generally flash stock recovery!!
I got the problem,
You have htcDEV edition
So your bootloader UNLOCKED initially right??
So i think you should keep it unlocked
Try and reply what happens
HIT THANKS IF I HELPED YOU
Click to expand...
Click to collapse
Yes I have Dev edition and the bootloader was unlocked initially. Are you saying to keep bootloader unlocked and run the RUU?

tonztime said:
Yes I have Dev edition and the bootloader was unlocked initially. Are you saying to keep bootloader unlocked and run the RUU?
Click to expand...
Click to collapse
NO NO NO
after RUU, before OTA try keeping BL unlocked and get OTA
I think mostly it will work
You got my point!!

prunzzz said:
NO NO NO
after RUU, before OTA try keeping BL unlocked and get OTA
I think mostly it will work
You got my point!!
Click to expand...
Click to collapse
Ok. I ran RUU and tried running OTA with BL unlocked and got the same problem of booting to bootloader when trying to install OTA.

Do you have stock recovery ?
Sent from my Nexus 7 using xda app-developers app

tonztime said:
Ok. I ran RUU and tried running OTA with BL unlocked and got the same problem of booting to bootloader when trying to install OTA.
Click to expand...
Click to collapse
The TAMPERED is gone from fastboot, ya??
If not may be stock recovery wasnt flashed correctly
This is it
Thats all i can think
May be reflash stock recovery,
Even then if you cant get OTA its strange

If the TAMPERED is still there, the OTA won't install AFAIK.

Omg fkn hell
First grab the appropriate ruu for your phone,then start it up,but dont put in the phone ,while its still open,go to the windows search bar on the menu and type %temp% you will see a folder,search in the first 2 folders you will find ROM.zip inside that is all the **** you need,so extract from it boot.IMG(kernel) and recovery.IMG(recovery),
Now boot your phone to boot loader flash those 2 files,relock bootloader,(fastboot oem lock ) something like this i forgot,make sure to double check it then boot your phone up,unroot it with supersu app ,reboot then flash the update ....,that's assuming you're on stock rom,if on a custom one, after flashing the img files,run the ruu so it can restore the stock software ..

Sorry to hijack, i bought the one yesterday, immediately rooted. Does this mean I won't get ota updates? It's running 4.1.
Will I have to unroot and install stock recovery to update?
Sent from my HTC One using xda app-developers app

X82X said:
Sorry to hijack, i bought the one yesterday, immediately rooted. Does this mean I won't get ota updates? It's running 4.1.
Will I have to unroot and install stock recovery to update?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Exactly

BigJoey010 said:
Exactly
Click to expand...
Click to collapse
I've seen here that there is a list of RUU's. My phone is the following:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm not sure which RUU to use. Also, the page gives a list of OTA. Can I just install the correct OTA to upgrade?
I'm just worried I'll screw this phone up, barely had it a day. Again, apologies for hijacking.

BigJoey010 said:
Do you have stock recovery ?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I have the RUU straight from htcdev for the HTC One Dev edition of the phone. This should be all I need to get back to stock. Is this not the case?

So I ran RUU utility after relocking phone and superuser apk still shows as installed. I then downloaded ES file explorer and gave it superuser permission, mounted the filesystem as rw and deleted the su file in system/bin and system/xbin and then deleted the superuser.apk file from system/app. After that I tested to make sure I no longer had root access. The test showed I no longer had root access and then I rebooted and all the su and superuser files were back again. Does anyone have an explanation for what I'm doing wrong? I just want to get back to stock so I can install OTA updates from HTC again and get 4.2.2 update.

Bro why are you doing it manually ? You must go into the app and press unroot,that's it
Sent from my Nexus 7 using xda premium

BigJoey010 said:
Bro why are you doing it manually ? You must go into the app and press unroot,that's it
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I don't see that option in the superuser app. I do see that option on my GN that has su installed but not on my HTC one with superuser installed.

BigJoey010 said:
The ruu only restores stock ROM only ,but you have to flash stock kernel and recovery manually
Click to expand...
Click to collapse
Lie. The RUU flash EVERYTHING back to 100% stock - kernel, recovery, ROM, the lot

[Guide] How to Downgrade from KK to JB S-OFF Required

Okay Guys. here is a guide how to downgrade back to JB from using KK. You will need to be S-OFF and also will to have a locked or relocked bootloader. and just follow my steps. You will need adb and fastboot and you will need the 3.05.651.6 decrypted you will find the file here http://forum.xda-developers.com/showthread.php?t=2576995
(1) From fastboot you need to first re-lock your bootloader. using this command
fastboot oem lock
then you reboot your device into bootloader. make sure your device shows relocked or locked on top of the screen. once you see that then go to step #2
(2) now type this command fastboot oem rebootRUU after that you should see black screen with green HTC logo.
if you got this far go to step #3
(3) now the file you downloaded please rename it too rom.zip (make sure you have it named correctly) my advice i would just found the file you downloaded and right click it and look for rename and i would just type the word rom and hit enter to ensure it is correct. If you did that go to step #4
(4) Now, type this command fastboot flash zip rom.zip , let it run it course during the process you will see this message . " pre hboot 90 " if you see that then just press the up arrow on the keyboard and press enter and let the process run again and then let it run it will flush your device at this point and will lose everything on your storage. once you have done that sit back 10-20 mins. and wait for the process to finish. after that go to Step #5
(5) type this command in command prompt fastboot reboot-bootloader and press enter . Once your at bootloader menu select factory reset and press power button and let it do reset and when it done. your device will reboot and your done.
Credits - Go to O.M.J for the files
P.S. Hopefully this will help you for anyone that needs this.

Pretty sure it's just a matter of running the RUU you want if you're s-off...

Indirect said:
Pretty sure it's just a matter of running the RUU you want if you're s-off...
Click to expand...
Click to collapse
According to recent reports, no it is not that simple

It does work been working with O.M.J and I did this with two devices already.

Indirect said:
Pretty sure it's just a matter of running the RUU you want if you're s-off...
Click to expand...
Click to collapse
Yeah I just ran a jb RUU without relocking boot loader and s-off without any issues.

I'm trying this now. I'll report back soon!
---------- Post added at 08:42 PM ---------- Previous post was at 08:41 PM ----------
Kraizk said:
According to recent reports, no it is not that simple
Click to expand...
Click to collapse
I'm here to agree! I can't get an older RUU to flash and I'm S-OFF. I've tried on multiple computers and done everything I can think of... With no luck. I've tried the whole "tricking" the bootloader to thinking you're using an older base and everything.

wwjoshdew said:
I'm trying this now. I'll report back soon!
---------- Post added at 08:42 PM ---------- Previous post was at 08:41 PM ----------
I'm here to agree! I can't get an older RUU to flash and I'm S-OFF. I've tried on multiple computers and done everything I can think of... With no luck. I've tried the whole "tricking" the bootloader to thinking you're using an older base and everything.
Click to expand...
Click to collapse
It works .

DUDE, you are FREAKING AWESOME! After trying and failing so many times by using different RUU's, zip's, and etc...
You're guide got my HTC One back to 4.3!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

wwjoshdew said:
DUDE, you are FREAKING AWESOME! After trying and failing so many times by using different RUU's, zip's, and etc...
You're guide got my HTC One back to 4.3!
Click to expand...
Click to collapse
Your Welcome ! I didn't have time too make the rom.zip , thanks O.M.J . He help me with that file.

wwjoshdew said:
DUDE, you are FREAKING AWESOME! After trying and failing so many times by using different RUU's, zip's, and etc...
You're guide got my HTC One back to 4.3!
Click to expand...
Click to collapse
Where's the video of this process Josh?

BD619 said:
Where's the video of this process Josh?
Click to expand...
Click to collapse
Whats going on boss?

tommyjoesanders said:
Whats going on boss?
Click to expand...
Click to collapse
Just giving Josh a hard time

BD619 said:
Just giving Josh a hard time
Click to expand...
Click to collapse
He good guy. Just been trying to help out on the forum with some people having issues with KK Update. and needing to downgrade. I am just glad O.M.J file was here.

milesb3 said:
Yeah I just ran a jb RUU without relocking boot loader and s-off without any issues.
Click to expand...
Click to collapse
I haven't had such luck running the JB RUU. Currently I have an HTC One brick and back on the HTC EVO LTE until I can get it figured out.

weidnerj said:
I haven't had such luck running the JB RUU. Currently I have an HTC One brick and back on the HTC EVO LTE until I can get it figured out.
Click to expand...
Click to collapse
If you can get into bootloader just try this method I think it will work for you

weidnerj said:
I haven't had such luck running the JB RUU. Currently I have an HTC One brick and back on the HTC EVO LTE until I can get it figured out.
Click to expand...
Click to collapse
It's odd that some are having issues while others are not. I just ruu'd again from stock kk to make sure I wasn't going crazy with a 3.04 encrypted zip I extracted from the official ruu. Did it in mac os x and went off without a hitch.

Does 4.4.2 perform worse?

milesb3 said:
It's odd that some are having issues while others are not. I just ruu'd again from stock kk to make sure I wasn't going crazy with a 3.04 encrypted zip I extracted from the official ruu. Did it in mac os x and went off without a hitch.
Click to expand...
Click to collapse
i thought that was teh whole point of s-off.

tommyjoesanders said:
If you can get into bootloader just try this method I think it will work for you
Click to expand...
Click to collapse
I am willing to try anything about now... But going to take a few hours to download the file so won't be able to try until tomorrow after work.
Thanks for the suggestion!!!

weidnerj said:
I am willing to try anything about now... But going to take a few hours to download the file so won't be able to try until tomorrow after work.
Thanks for the suggestion!!!
Click to expand...
Click to collapse
Keep me posted. I will do what I can to help anyone

HTC One M8 With TWRP: Trouble With ROMs

Huge amount of frustration with trying to deal with my phone
I soft bricked my HTC One M8 HK not too long ago, and had left it sitting in the dust for a while as I had no options of fixing it because I wiped the memory on accident (how I did, I don't know. Guess I'm dumb. That's not the point though). It's been sitting on my dresser for about 2 months being unused as I had no microSD cards in hand. All it had was an unlocked bootloader and working TWRP.
As of right now, I've tried to install 4 ROMs. All 4 did not work. I followed the instructions and unlocked my bootloader and did all other essential things. I installed ViperOneM8 before being ignorant that my WiFi wouldn't work. It was the only ROM I installed that actually booted properly. The only issue was that I had no WiFi. Had it worked, I wouldn't be making this thread. Then I got Android Revolution HD, installed it and it installed properly. I booted it into system, and it brought me to bootloader. This was the same issue I had while trying to install my first ROM, and still happens. Then I got CyanogenMod, and it didn't even install. TWRP told me it failed right off the bat. Same thing with whenever I tried to install a stock firmware recovery of the variant I have, HK Sprint.
Right now, I'm getting the 4.2.5 HK RUU in hopes that it works. I tried it previously, and it was a literal waste of time. I've been here for 5 hours trying different ROMs and to no success. I was very faithful I would get to use my phone again, although unless this RUU actually works, I don't have a lot of positive faith for my phone.
Are there any fixes for getting something like CyanogenMod to work? I actually really wanted this ROM after I remembered it, and was quite let down after it failed to work. Also, is there anything I should do with the phone before I go farther with anything?
Thanks for any help you all can give, I would greatly appreciate it. Sucks not having a phone, so I'll take any help I can get. Thanks once again!
EDIT: The RUU did not work. It failed to update. Waiting for answers I guess..

F0rZ3r0 said:
I soft bricked my HTC One M8 HK not too long ago, and had left it sitting in the dust for a while as I had no options of fixing it because I wiped the memory on accident (how I did, I don't know. Guess I'm dumb. That's not the point though). It's been sitting on my dresser for about 2 months being unused as I had no microSD cards in hand. All it had was an unlocked bootloader and working TWRP.
As of right now, I've tried to install 4 ROMs. All 4 did not work. I followed the instructions and unlocked my bootloader and did all other essential things. I installed ViperOneM8 before being ignorant that my WiFi wouldn't work. It was the only ROM I installed that actually booted properly. The only issue was that I had no WiFi. Had it worked, I wouldn't be making this thread. Then I got Android Revolution HD, installed it and it installed properly. I booted it into system, and it brought me to bootloader. This was the same issue I had while trying to install my first ROM, and still happens. Then I got CyanogenMod, and it didn't even install. TWRP told me it failed right off the bat. Same thing with whenever I tried to install a stock firmware recovery of the variant I have, HK Sprint.
Right now, I'm getting the 4.2.5 HK RUU in hopes that it works. I tried it previously, and it was a literal waste of time. I've been here for 5 hours trying different ROMs and to no success. I was very faithful I would get to use my phone again, although unless this RUU actually works, I don't have a lot of positive faith for my phone.
Are there any fixes for getting something like CyanogenMod to work? I actually really wanted this ROM after I remembered it, and was quite let down after it failed to work. Also, is there anything I should do with the phone before I go farther with anything?
Thanks for any help you all can give, I would greatly appreciate it. Sucks not having a phone, so I'll take any help I can get. Thanks once again!
EDIT: The RUU did not work. It failed to update. Waiting for answers I guess..
Click to expand...
Click to collapse
Flashing RUU requires locked bootloader.

Alright, I'm seriously about to just throw this thing in the dumpster. I've been here another 2 hours trying to get Cyanogen to work, and I figured out the issue with it. The updater script file wasn't accepting m8_whl. I'm still unaware how in the Mod Edit I'm supposed to put m8_whl into the script for it to be accepted.
To be more specific, the actual updater script has m8whl, while my phone recognizes as m8_whl. It denies it.
I thought I put it into the script correctly, although it is not accepting it. I found a quote not saying the location, and I assumed in the latest release of Cyanogen 12 for M8s, it was in /META-INF/google/android/updater-script
Please, someone help me before I have an anger episode. This thing has literally wasted my whole Mod Edit day.

F0rZ3r0 said:
Alright, I'm seriously about to just throw this thing in the dumpster. I've been here another 2 hours trying to get Cyanogen to work, and I figured out the issue with it. The updater script file wasn't accepting m8_whl. I'm still unaware how in the Mod Edit I'm supposed to put m8_whl into the script for it to be accepted.
To be more specific, the actual updater script has m8whl, while my phone recognizes as m8_whl. It denies it.
I thought I put it into the script correctly, although it is not accepting it. I found a quote not saying the location, and I assumed in the latest release of Cyanogen 12 for M8s, it was in /META-INF/google/android/updater-script
Please, someone help me before I have an anger episode. This thing has literally wasted my whole Mod Edit day.
Click to expand...
Click to collapse
Don't toss it, it's still worth something, even if not to you. But as @popthosegaskets said, you need to relock the bootloader to flash the RUU. If it's been sitting for awhile, what version of firmware and hboot was it on prior to not working? Perhaps the issue is that it's older, also try flashing the newest version of TWRP if you still want to install a custom OS.
If you want to RUU, just use the fastboot command "fastboot oem lock" while in fastboot and then run the RUU. I think it reboots after locking.

dopy25 said:
Don't toss it, it's still worth something, even if not to you. But as @popthosegaskets said, you need to relock the bootloader to flash the RUU. If it's been sitting for awhile, what version of firmware and hboot was it on prior to not working? Perhaps the issue is that it's older, also try flashing the newest version of TWRP if you still want to install a custom OS.
If you want to RUU, just use the fastboot command "fastboot oem lock" while in fastboot and then run the RUU. I think it reboots after locking.
Click to expand...
Click to collapse
Alright, doing this now. I'm a lot calmer today, so I can do this.

dopy25 said:
Don't toss it, it's still worth something, even if not to you. But as @popthosegaskets said, you need to relock the bootloader to flash the RUU. If it's been sitting for awhile, what version of firmware and hboot was it on prior to not working? Perhaps the issue is that it's older, also try flashing the newest version of TWRP if you still want to install a custom OS.
If you want to RUU, just use the fastboot command "fastboot oem lock" while in fastboot and then run the RUU. I think it reboots after locking.
Click to expand...
Click to collapse
Didn't work, the RUU gave me the same error as last time, it tells me its the wrong RUU. Got both the stock RUUs just to see if I got it wrong about HK, both failed. Please help...

F0rZ3r0 said:
Didn't work, the RUU gave me the same error as last time, it tells me its the wrong RUU. Got both the stock RUUs just to see if I got it wrong about HK, both failed. Please help...
Click to expand...
Click to collapse
[Mod hat on] I know it can be frustrating at times but please take it easy with the swearing. [/Mod hat off]
You might try flashing the Full firmware that matches the RUU that you are trying to flash, the past couple updates require hboots to match on both your device and the RUU or you will get an error.

Sloth said:
[Mod hat on] I know it can be frustrating at times but please take it easy with the swearing. [/Mod hat off]
You might try flashing the Full firmware that matches the RUU that you are trying to flash, the past couple updates require hboots to match on both your device and the RUU or you will get an error.
Click to expand...
Click to collapse
My apologies for the swearing, was angry at the time.
Also, my hboot version seems to be 3.18. Not sure what to do in order to be able to flash firmware. My OS version seems to be 2.16.651.4 as well if that helps.
What would I have to do in order to install a ROM and how?

If you are not flashing the full firmware to begin with, that's the issue. From your OP it looks like you only have an unlocked BL and had TWRP.
You must relock the BL and then run the full RUU, you can get it in the thread here, or get it from HTC. Either way you need the full one, it flashes the FW and Software as well as bootloader and radios.
HTC: http://dl3.htc.com.s3.amazonaws.com..._NV_SPCS_1.52_003_release_446220_signed_2.exe
Thread with all and modified FW
http://forum.xda-developers.com/showthread.php?t=2729173
Are you S-Off or On? If you are running the *.651* then that's the non HK version. It's ok if you flashed a modified stock, but if you got that from an RUU, that would be what the issue is. I think

dopy25 said:
If you are not flashing the full firmware to begin with, that's the issue. From your OP it looks like you only have an unlocked BL and had TWRP.
You must relock the BL and then run the full RUU, you can get it in the thread here, or get it from HTC. Either way you need the full one, it flashes the FW and Software as well as bootloader and radios.
HTC: http://dl3.htc.com.s3.amazonaws.com..._NV_SPCS_1.52_003_release_446220_signed_2.exe
Thread with all and modified FW
http://forum.xda-developers.com/showthread.php?t=2729173
Are you S-Off or On? If you are running the *.651* then that's the non HK version. It's ok if you flashed a modified stock, but if you got that from an RUU, that would be what the issue is. I think
Click to expand...
Click to collapse
I believe I'm S-OFF.

F0rZ3r0 said:
I believe I'm S-OFF.
Click to expand...
Click to collapse
look in bootloader it will tell you if you are s-off or s-on.

Sloth said:
look in bootloader it will tell you if you are s-off or s-on.
Click to expand...
Click to collapse
Never mind, S-ON.

F0rZ3r0 said:
Never mind, S-ON.
Click to expand...
Click to collapse
Ok re-lock your bootloader if you have not already.
Flash this for Non HK 4.25.651.18 Full Firmware
Flash this for HK 4.25.654.18 Full Firmware
Instructions:
-rename firmware to firmware.zip
-copy firmware.zip to your sdk folder
-boot into bootloader
-plug in usb
-select fastboot option (screen should say fastboot usb)
-type fastboot oem rebootRUU
-when u see the black screen w/ HTC, type fastboot flash zip firmware.zip
-when it's done, type fastboot reboot
Once done flash the latest Non HK or HK RUU found here... http://forum.xda-developers.com/showthread.php?t=2729173
Then unlock your bootloader again using the unlock code you got from HTC.
Re-flash the latest TWRP found here... https://dl.twrp.me/m8/
This will give you a fresh start then you can try to flash the rom you want.

Sloth said:
Ok re-lock your bootloader if you have not already.
Flash this for Non HK 4.25.651.18 Full Firmware
Flash this for HK 4.25.654.18 Full Firmware
Instructions:
-rename firmware to firmware.zip
-copy firmware.zip to your sdk folder
-boot into bootloader
-plug in usb
-select fastboot option (screen should say fastboot usb)
-type fastboot oem rebootRUU
-when u see the black screen w/ HTC, type fastboot flash zip firmware.zip
-when it's done, type fastboot reboot
Once done flash the latest Non HK or HK RUU found here... http://forum.xda-developers.com/showthread.php?t=2729173
Then unlock your bootloader again using the unlock code you got from HTC.
Re-flash the latest TWRP found here... https://dl.twrp.me/m8/
This will give you a fresh start then you can try to flash the rom you want.
Click to expand...
Click to collapse
Umm...I don't have anything called SDK :/
What do I do then?

F0rZ3r0 said:
Umm...I don't have anything called SDK :/
What do I do then?
Click to expand...
Click to collapse
If you have a platform-tools you can use that or use the folder attached.
Unzip it and copy the files to a folder.

Sloth said:
If you have a platform-tools you can use that or use the folder attached.
Unzip it and copy the files to a folder.
Click to expand...
Click to collapse
Alright, I did it all, but it doesn't seem to be changing once I send over the zip. Is it meant to take a while or is there something wrong?
EDIT: 20 minutes later and still at the sending. Something probably went wrong.
EDIT 2: 30 minutes later, still sending.

F0rZ3r0 said:
Alright, I did it all, but it doesn't seem to be changing once I send over the zip. Is it meant to take a while or is there something wrong?
EDIT: 20 minutes later and still at the sending. Something probably went wrong.
EDIT 2: 30 minutes later, still sending.
Click to expand...
Click to collapse
Should only be a few seconds.

Sloth said:
Should only be a few seconds.
Click to expand...
Click to collapse
Not sure what the issue here is then. As I write this, it is still sending. I'm not sure what the issue is...

Check PM.

SOLVED Soft or hard bricked - What do you guys think? (PICTURES INCLUDED)

Hi guys,
I got a second hand HTC One M8 Sprint and can keep it if I make it work. I spent the whole night reading forums and trying to flash custom ROMs but end up stuck in bootloader. Is it "just" soft bricked and I need to flash the RUU? I only tried flashing ROMs (ARHD,Viper,BadBoyz,ICE), I'm scared I might give him the final blow if I mess up the firmware.
I would appreciate it if somebody can help me fix the phone (and reward you with beer money to say thanks)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

My Friend Just got one in the same condition from the Craiglist and her's was NOT S-OFF so your good to go.
FYI ((((( In order the flash the stock RUU it has to be RELOCKED )))))
I would recommend TWRP 3.0 at least for recovery.
I have used Philz in the past with my older phones and its worked well but Now I use TWRP because the text is so small its hard to see at times and I seem to touch the wrong thing on the list.
Maybe its my age catching up to me but Me personally like the TWRP because it user and touch friendly Recovery.
I would also recommend using the ((( Hasoon2000's HTC One 2014 (M8) All-in-one Toolkit )))
I have used the Squabbi's HTC One (M8) Toolkit- 2.0.0.1 and had many problems with it. ( Screen Freeze,Program lockup, adb commands NOT working, output token Not good,side load did not work for me either so I only had one choice was to try the older software and terminal window OLD SCHOOL WAY took me longer but in the end the older software worked.
Please I do NOT knock someone's else's software because I am sure it works well for most people it just did not work for me.
These guys on here put a lot of time and effort into there software and many of them only get money from donations but others use advertisements
I have been here from the very beginning of XDA but never really contributed in the past but am doing a little more now to help others if I can.
The problem with the new software maybe my machine i am running Windows 7 Pro 64Bit 24gigRam/Samsung240 SSD
Dale

Thank you Dale for the quick and kind reply. I sent you a PM, please take a look when you get the time.
If somebody here could guide me through the steps of fixing it via Skype, I would return the favor with a paypal donation. Thank you in advance

@zxhwk are you sure the phone has to be relocked in order to flash RUU? I know that s-off makes that irrelevant on other HTC phones, so that could be the case with M8 too
dey tuuk ur juurbs

Ohh Donkeykong, second reply pa vec netko od nasih Imas li ti mozda vremena i volje pomoci mi da sredim mob? (writing in Croatian)

DemesHTC said:
Ohh Donkeykong, second reply pa vec netko od nasih Imas li ti mozda vremena i volje pomoci mi da sredim mob? (writing in Croatian)
Click to expand...
Click to collapse
PMed [emoji6]
dey tuuk ur juurbs

donkeykong1 said:
@zxhwk are you sure the phone has to be relocked in order to flash RUU? I know that s-off makes that irrelevant on other HTC phones, so that could be the case with M8 too
dey tuuk ur juurbs
Click to expand...
Click to collapse
Yes POSITIVE it has to be RELOCKED in order to run the stock RUU
I still have all the original Stock RUU KitKat in my archives and even the original BadBoyz Rom Version 1
---------- Post added at 01:43 PM ---------- Previous post was at 01:32 PM ----------
DemesHTC said:
Thank you Dale for the quick and kind reply. I sent you a PM, please take a look when you get the time.
If somebody here could guide me through the steps of fixing it via Skype, I would return the favor with a paypal donation. Thank you in advance
Click to expand...
Click to collapse
In the mode you have right now its easy to flash it
All you have to do is COPY the ROM you would like on the phone to a Micro SD card and then place sd card in phone and boot into recovery mode .
Then do a complete wipe of everything including internal storage so you can do a CLEAN flash.
After wipe use back button to go back to main screen and choose INSTALL ZIP ( make sure you choose external SDCARD ) where you put the Rom and choose it and follow instructions on screen when done and all worked well it will ask to reboot .
If it did NOT work it will tell you that there is NO OS so you will have to try againif still Not working then relock and run the STOCK RUU and from that point its pretty easy to do connect phone to PC and connect to HTC site and get NEW TOKEN STRING and unlock bootloader again and then flash new recovery then choose rom you like.
There are many threads here that show you step by step on how to flash from a stock phone. But your in a much better position than a stock one Most of the work has already been done for you just a simple flash is all you have to do as I have stated earlier in the post.
PSSSSSSSSSSSS: MAKE SURE YOU HAVE POWER CONNECTED TO PHONE and BATTERY IS at LEAST 50 % before FLASHING
Dale

At the risk of sounding rude - you're wrong about relocking bootloader with s-off for RUU flashing. You need to relock the bootloader only if your phone is s-on. For s-off it doesn't matter
http://venomroms.com/ruu/
This proves I'm right
dey tuuk ur juurbs

donkeykong1 said:
At the risk of sounding rude - you're wrong about relocking bootloader with s-off for RUU flashing. You need to relock the bootloader only if your phone is s-on. For s-off it doesn't matter
http://venomroms.com/ruu/
This proves I'm right
dey tuuk ur juurbs
Click to expand...
Click to collapse
I never mentioned about having the S-OFF or ON while flashing the STOCK RUU just the BootLoader has to be RELOCKED so I do not know where you get that from
This is one of the main reasons I have NOT helped very many people on the forum because people assume things in the postings and try and prove a point or something while they ask for your help on the other hand. As stated in this posting I NEVER mentioned anything about FLASHING while having (( S-OFF or S-ON )) Just RELOCKING BOOTLOADER so have a NICE day I will fade bad out again like I was before. First time I try and help this is what happens ( No Thank You )

zxhwk said:
I never mentioned about having the S-OFF or ON while flashing the STOCK RUU just the BootLoader has to be RELOCKED so I do not know where you get that from
Click to expand...
Click to collapse
OK. I thought you will think I'm rude. Thing is - his phone is s-off, and he can flash ay kind of RUU without locking or relocking his bootloader. That means he can even flash unsigned RUUs and downgrade his firmware which is not possible with s-on. If security flag is on, i.e. s-on then, and only then you need to relock bootloader in order to flash RUU, and you can flash only signed RUUs, and you can't downgrade your firmware. You got some things mixed up, sorry
dey tuuk ur juurbs

donkeykong1 said:
OK. I thought you will think I'm rude. Thing is - his phone is s-off, and he can flash ay kind of RUU without locking or relocking his bootloader. That means he can even flash unsigned RUUs and downgrade his firmware which is not possible with s-on. If security flag is on, i.e. s-on then, and only then you need to relock bootloader in order to flash RUU, and you can flash only signed RUUs, and you can't downgrade your firmware. You got some things mixed up, sorry
dey tuuk ur juurbs
Click to expand...
Click to collapse
Go ahead and take over I am telling you it will NOT FLASH STOCK RUU when BOOTLOADER is UNLOCKED S-off or S-on has no bearings on flashing. except the Radio
I was just trying to help I am NOT here to tell anyone about the simple things they should already know like the Signed RUU downgrading and such.
If they are willing to flash a phone then I am sure they have read all of this and should not have to spell those simple things out that is COMMON SENSE

zxhwk said:
Go ahead and take over I am telling you it will NOT FLASH STOCK RUU when BOOTLOADER is UNLOCKED S-off or S-on has no bearings on flashing. except the Radio
Click to expand...
Click to collapse
I thought I was rude, but you take the flag my friend.
Over and out
dey tuuk ur juurbs

OP if you are trying to use one of the last 2-3 RUU's you will need to flash the matching firmware first then the RUU should run fine.

Try installing any of the roms you tried with TWRP v3, make sure you wipe Data partition (cache and dalvik should wipe with rom install)
Flash the recovery from the bootloader
I'm also curious why the release date shows 27 Jan on bootloader(it should say 7 Jan unless I used the wrong ruu), what firmware did you flash ?

Thank you guys for the replies and useful tips, I'm currently in touch with @donkeykong1 and we are working on it. I will keep you updated and post the solution once we fix it, so anybody else with the same problem can find it in the future.
@Vcek - I didn't flash any firmware myself, I got it already bricked and just tried flashing ROMs ((ARHD,Viper,BadBoyz,ICE). It run the instalation, but after it was all done and the phone rebooted it still was stuck in the bootloader (I even left it 30min alone since I read somewhere that it might take longer to boot after flashing the ROM).
@Sloth @zxhwk - Thank you for the tips guys, I hope we will figure it out and flash that bastard

SOLUTION: We flashed the RUU over fastboot with UNLOCKED bootloader and the phone is working again!
Thank you all for your help and I hope this thread will help save more bricked phones in the future

zxhwk said:
My Friend Just got one in the same condition from the Craiglist and her's was NOT S-OFF so your good to go.
FYI ((((( In order the flash the stock RUU it has to be RELOCKED )))))
I would recommend TWRP 3.0 at least for recovery.
I have used Philz in the past with my older phones and its worked well but Now I use TWRP because the text is so small its hard to see at times and I seem to touch the wrong thing on the list.
Maybe its my age catching up to me but Me personally like the TWRP because it user and touch friendly Recovery.
I would also recommend using the ((( Hasoon2000's HTC One 2014 (M8) All-in-one Toolkit )))
I have used the Squabbi's HTC One (M8) Toolkit- 2.0.0.1 and had many problems with it. ( Screen Freeze,Program lockup, adb commands NOT working, output token Not good,side load did not work for me either so I only had one choice was to try the older software and terminal window OLD SCHOOL WAY took me longer but in the end the older software worked.
Please I do NOT knock someone's else's software because I am sure it works well for most people it just did not work for me.
These guys on here put a lot of time and effort into there software and many of them only get money from donations but others use advertisements
I have been here from the very beginning of XDA but never really contributed in the past but am doing a little more now to help others if I can.
The problem with the new software maybe my machine i am running Windows 7 Pro 64Bit 24gigRam/Samsung240 SSD
Dale
Click to expand...
Click to collapse
BTW, an s-off phone does NOT need to be locked to flash an ruu. Only an s-on phone needs that done. I probably a couple dozen ruu (stock and custom) threads posted on xda.
The newer phones even allow a s-off but locked phone to flash recovery directly without any tricks. (M8 s-off but locked requires an ruu mode zip)
BTW, your friend with the s-on phone...if you can't get it sorted I have a Java card that can s-off any HTC phone.
Sent from my SM-T810 using Tapatalk

Re-locked Bootloader and now facing problems

Hi there this is my first post so excuse me if i'm unclear about stuff. if you need any info just gimme a shout and i can find it for you!
I have an M7 on O2 (UK), I've had it pretty much since it release in 2013.
Upon getting the phone i immediately rooted whilst on Android Version 4.4.3, it's the Sense Version too (i don't know if that's relevant or not).
Anyway it's been a while since this, and i've lost a lot of the knowledge i had on Android & Rooting etc.
I'm looking to un-root my phone to get the OTA Updates which have been alerting my (very annoying) since 2013!
Last week i began watching tutorials and reading up, a few days in and i gave it my first attempt..
I first re-locked my Bootloader successfully and then tried using the RUU Software but was unlucky with numerous versions (i'm still unsure about how to find the RIGHT one). After hours & hours i was at and end and couldnt seem to find the right one for my phone and i gave up.
Since "re-locking" my Bootloader i've been facing an issue where every time i power up or restart my phone it boots in the Bootloader's Fastboot mode, from here i have to navigate to 'reboot'... the phone then restarts and this time round i get my usual home screen.
I'm unsure as to what direction to go now as i'm scared i will brick my phone, i guess i have 2 options;
A. Continue to try and return to stock and then decide if i wish to re-root (probably not)
B. Unlock the Bootloader once again (only this will wipe my phone, and i can't find the original stock rom thus leading to a brick i expect?)
Hope someone can help, any questions please do not hesitate to ask!

gemodubz said:
Hi there this is my first post so excuse me if i'm unclear about stuff. if you need any info just gimme a shout and i can find it for you!
I have an M7 on O2 (UK), I've had it pretty much since it release in 2013.
Upon getting the phone i immediately rooted whilst on Android Version 4.4.3, it's the Sense Version too (i don't know if that's relevant or not).
Anyway it's been a while since this, and i've lost a lot of the knowledge i had on Android & Rooting etc.
I'm looking to un-root my phone to get the OTA Updates which have been alerting my (very annoying) since 2013!
Last week i began watching tutorials and reading up, a few days in and i gave it my first attempt..
I first re-locked my Bootloader successfully and then tried using the RUU Software but was unlucky with numerous versions (i'm still unsure about how to find the RIGHT one). After hours & hours i was at and end and couldnt seem to find the right one for my phone and i gave up.
Since "re-locking" my Bootloader i've been facing an issue where every time i power up or restart my phone it boots in the Bootloader's Fastboot mode, from here i have to navigate to 'reboot'... the phone then restarts and this time round i get my usual home screen.
I'm unsure as to what direction to go now as i'm scared i will brick my phone, i guess i have 2 options;
A. Continue to try and return to stock and then decide if i wish to re-root (probably not)
B. Unlock the Bootloader once again (only this will wipe my phone, and i can't find the original stock rom thus leading to a brick i expect?)
Hope someone can help, any questions please do not hesitate to ask!
you can also contact me here [email protected]
Click to expand...
Click to collapse
Post the output of "fastboot getvar all" (hide your imei and sn)

alray said:
Post the output of "fastboot getvar all" (hide your imei and sn)
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

gemodubz said:
Click to expand...
Click to collapse
If you want to return to stock, you can use the 7.18.206.51 ruu (its the latest version for your phone)
Instructions as post #1, ruu at post #2:
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Once the RUU flashed you can unlock the bootloader again and re-root. Be sure to use the latest version of supersu.

alray said:
If you want to return to stock, you can use the 7.18.206.51 ruu (its the latest version for your phone)
Instructions as post #1, ruu at post #2:
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Once the RUU flashed you can unlock the bootloader again and re-root. Be sure to use the latest version of supersu.
Click to expand...
Click to collapse
Thanks a bunch man! Please could you tell me how you found the specific RUU for my phone?
Please could you tell me the method you used to locate the RUU as i had so much trouble before, i was wondering if there is an easy way find the correct RUU (by looking for certain codes etc) ?

alray said:
If you want to return to stock, you can use the 7.18.206.51 ruu (its the latest version for your phone)
Instructions as post #1, ruu at post #2:
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Once the RUU flashed you can unlock the bootloader again and re-root. Be sure to use the latest version of supersu.
Click to expand...
Click to collapse
won't unlocking the bootloader after flashing RUU just wipe the phone again?

gemodubz said:
won't unlocking the bootloader after flashing RUU just wipe the phone again?
Click to expand...
Click to collapse
Unlocking will wipe user data only.
Sent from my HTC One using XDA Labs

alray said:
Unlocking will wipe user data only.
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
So would that be my media files like photos, music, apps etc?

gemodubz said:
So would that be my media files like photos, music, apps etc?
Click to expand...
Click to collapse
Exactly
Sent from my HTC One using XDA Labs