Develop Bugs

[Q] [Help!] Bricked One X

I wanted to flash LeeDroid's rom. After I flashed the boot image I realized that I haven't put the rom into the root of the phone's storage! silly me. I tried rebooting the system but it won't boot. Then I tried the unbrick methods on the forum but found no luck. At last I tried relocking it and restore it using RUU but it still won't work! It is saying that I got the wrong version of RUU, but where can i find the RUU for 1.28? Hope someone can help!!

chowdyg said:
I wanted to flash LeeDroid's rom. After I flashed the boot image I realized that I haven't put the rom into the root of the phone's storage! silly me. I tried rebooting the system but it won't boot. Then I tried the unbrick methods on the forum but found no luck. At last I tried relocking it and restore it using RUU but it still won't work! It is saying that I got the wrong version of RUU, but where can i find the RUU for 1.28? Hope someone can help!!
Click to expand...
Click to collapse
What country are you in, which network are you on and did you buy your phone sim free?
If you go into fastboot mode and then boot into CWM using the command:
fastboot boot <CWM img file>.img
You'll then be able to use adb to push the rom zip onto your device which you can then flash with CWM.
If the RUU says you have the wrong version you probably have the RUU for another region/carrier.
It's pretty much impossible to permanently brick the one x (without s-off) so don't worry, you'll get it working eventually.

Thanks man. I am in Hong Kong and i am pretty sure it is sim free. after I tried running the RUU i have relocked the bootloader. for some reason I can't even get into recovery right now! When I try the RUU it saids the image version is 1.28.708.10 and I get error140

chowdyg said:
Thanks man. I am in Hong Kong and i am pretty sure it is sim free. after I tried running the RUU i have relocked the bootloader. for some reason I can't even get into recovery right now! When I try the RUU it saids the image version is 1.28.708.10 and I get error140
Click to expand...
Click to collapse
Which RUU did you download?

rogersnm said:
Which RUU did you download?
Click to expand...
Click to collapse
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_HK_1.26.708.2
I guess it is not the right one is it

chowdyg said:
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_HK_1.26.708.2
I guess it is not the right one is it
Click to expand...
Click to collapse
You can't install the 1.26 RUU after you've updated hboot with the 1.28 OTA.
Try installing this RUU: http://hoxroms.serveftp.com/RUU_END...Radio_1.1204.103.14_release_257077_signed.exe, it's the same region but a newer version.
Flash the stock 1.28 recovery image and relock your bootloader before trying to install the RUU.
The 1.28 recovery image can be found here: http://hoxroms.serveftp.com/Asia_1.28_RUU/recovery_signed.img

rogersnm said:
You can't install the 1.26 RUU after you've updated hboot with the 1.28 OTA.
Try installing this RUU: http://hoxroms.serveftp.com/RUU_END...Radio_1.1204.103.14_release_257077_signed.exe, it's the same region but a newer version.
Flash the stock 1.28 recovery image and relock your bootloader before trying to install the RUU.
The 1.28 recovery image can be found here: http://hoxroms.serveftp.com/Asia_1.28_RUU/recovery_signed.img
Click to expand...
Click to collapse
Thanks so much!!
but i have already relocked the bootloader without flashing the recovery image ... would that make a difference?

If the RUU runs successfully then don't worry about it, if it throws another error then flash the stock recovery and try again.

rogersnm said:
If the RUU runs successfully then don't worry about it, if it throws another error then flash the stock recovery and try again.
Click to expand...
Click to collapse
Thanks again. but how do i do it with the bootloader locked

chowdyg said:
Thanks again. but how do i do it with the bootloader locked
Click to expand...
Click to collapse
Just unlock it by running "fastboot flash unlocktoken Unlock_code.bin" like you did before and then relock it after

rogersnm said:
Just unlock it by running "fastboot flash unlocktoken Unlock_code.bin" like you did before and then relock it after
Click to expand...
Click to collapse
now it is saying error 170. whenever i try to flash something it just says waiting for device

chowdyg said:
now it is saying error 170. whenever i try to flash something it just says waiting for device
Click to expand...
Click to collapse
Disconnect and reconnect your phone, reboot your phone and your pc, try again.
ps. Make sure you relocked your bootloader

rogersnm said:
Disconnect and reconnect your phone, reboot your phone and your pc, try again.
ps. Make sure you relocked your bootloader
Click to expand...
Click to collapse
Thank you so much!! problem solved!!

[Q] Unable to reset to stock

I've been trying to reset my HOX to stock for OTA JB update, but it keeps going into boot loops in which the only solution is to hold down the vol_down to go into bootloader.
I've been following vladnosferatu's method 2:
Extract the rom.zip from RUU of your CID (google how extract ruu.exe)
-fastboot oem readcid (to know your CID)
Extract boot.img, system.img, signed_recovery.img from rom.zip
Flash
-fastboot flash recovery signed_recovery.img
-fastboot flash boot boot.img
-fastboot flash system system.img
-fastboot erase cache
-fastboot oem lock
Power on the phone
Run the RUU exe file (of your CID) and upgrade your phone
Click to expand...
Click to collapse
the bootloops start after oem lock.
I tried ClydeB1's noob-friendly method first, but it won't work since I'm already on 2.xxxxxxxx, and it refuses to downgrade to 1.xxxxxxxx
and I was on Renovate rom before this.
I have reset to Stock from Renovate once before, but now I can't seem to do it again. I have adb, fastboot and RUU(and extracted rom.zip)
What should I do? I've considered re-flashing CWM, flashing a Renovate again and restart the entire process, but I would like to confirm whether it would work first.
Thanks in advance for all responses!
UPDATE: I have just realised that there are 2.14 and 2.17 RUUs for my .707. I am now downloading those and trying if re-applying the steps using the updated RUUs will work.

Seriously .......WHY DIDN'T YOU TAKE 2 MINUTES TO MAKE A NANDROID BACKUP !!!!

if you upgraded the hboot you can only revert to stock when JB OTA is availabe for download an flash.

donhashem.dh said:
Seriously .......WHY DIDN'T YOU TAKE 2 MINUTES TO MAKE A NANDROID BACKUP !!!!
Click to expand...
Click to collapse
Because I have done this before perfectly fine, so I didn't expect anything to go wrong. I'd be sure to do it next time.
Seelendrache said:
if you upgraded the hboot you can only revert to stock when JB OTA is availabe for download an flash.
Click to expand...
Click to collapse
My hboot is 2.x, but it's not even the JB hboot of 3.x. I have been able to flash ROMs just fine on 2.x, so why can't I revert to stock? The 2.x hboot is obtained from stock OTA in the first place, too.

Just download the 2.17.707.3 RUU, then put your device is fastboot mode, relock the bootloader - fastboot oem lock
Then in fastboot mode too, run the RUU... you will for sure be on stock rom; there is no need to extract this and that and bla bla bla
And there is a JB OTA awaiting for your device
---------- Post added at 11:16 PM ---------- Previous post was at 11:15 PM ----------
donhashem.dh said:
Seriously .......WHY DIDN'T YOU TAKE 2 MINUTES TO MAKE A NANDROID BACKUP !!!!
Click to expand...
Click to collapse
What are you doing here, Don ? Change phone ?

ckpv5 said:
Just download the 2.17.707.3 RUU, then put your device is fastboot mode, relock the bootloader - fastboot oem lock
Then in fastboot mode too, run the RUU... you will for sure be on stock rom; there is no need to extract this and that and bla bla bla
And there is a JB OTA awaiting for your device
Click to expand...
Click to collapse
Hi ckpv5, I have also noticed that the 3.14.707 and 3.17.707 RUU has been uploaded. Can I just RUU the 3.17.707, skipping the manual 2.17.707? Because the only reason why I'm reverting to stock, is to update my hboot to 3.x, so that I can flash JB ROMs. Bypassing the 2.17-3.17 OTA would save quite some time.

Ya... I would do that if I were you... straight away run the 3.14 RUU instead of 2.17; but the RUU comes out after I did the OTA. So not so sure if it works that way but theoretically it should.
Just a note, the JB RUU, you cannot do the extract thingy.. so just relock the bootloader and run the RUU.

-- question deleted cause I saw some numbers wrongly that caused confusion =/ --

Hehe no ....just got bored from the one v forums ...nothing new happening :thumbdown:

ckpv5 said:
Ya... I would do that if I were you... straight away run the 3.14 RUU instead of 2.17; but the RUU comes out after I did the OTA. So not so sure if it works that way but theoretically it should.
Just a note, the JB RUU, you cannot do the extract thingy.. so just relock the bootloader and run the RUU.
Click to expand...
Click to collapse
Unfortunately this doesn't seem to work. The 3.14 gives me an error saying something about finding the right RUU for my device. Now downloading 2.17.707. Man htcruu downloads keep timing out halfway and I have to restart over and over :crying:
UPDATE: Yeah so it seems I had to RUU 2.17, and manually get 3.14 from OTA in order to upgrade. Can't skip that step.

[Q] Installing RUU

Hi
i'm currently using ViperX 2.7.1 , ICS
cid is HTC_044
i did this command "fastboot getvar version-main" and got "version-main: 1.29.707.11"
i would like to relock the bootloader by installing ruu , and then upgrade it to JB
which one shall i install?
RUU_ENDEAVOR_U_*ICS_40_S_hTC_As*ia_WWE_2.14.707*.3_Radio_2.1204*.123.18_release*_270370_signed.*exe , and then upgrade to JB
or
RUU_ENDEAVOR_U_*JB_45_S_hTC_Asi*a_WWE_3.14.707.*24_Radio_5.1204*.162.29_release*_296434_signed.*exe , immediately
thanks in advance

Does not matter. Updating top jb right away would be the easiest method.
Sent from my One X

Problem with CID 044
abunawwaf said:
Hi
i'm currently using ViperX 2.7.1 , ICS
cid is HTC_044
i did this command "fastboot getvar version-main" and got "version-main: 1.29.707.11"
i would like to relock the bootloader by installing ruu , and then upgrade it to JB
which one shall i install?
RUU_ENDEAVOR_U_*ICS_40_S_hTC_As*ia_WWE_2.14.707*.3_Radio_2.1204*.123.18_release*_270370_signed.*exe , and then upgrade to JB
or
RUU_ENDEAVOR_U_*JB_45_S_hTC_Asi*a_WWE_3.14.707.*24_Radio_5.1204*.162.29_release*_296434_signed.*exe , immediately
thanks in advance
Click to expand...
Click to collapse
Hi, my one x cid is 044 and i couldnt install JB on it because of that cid, and now i see u r workin on it, please put the link for download the rom (second RUU)
but my main problem is :
i wiped everything, only ClockWorkMod recovery remained, with unlocked bootloader, ROM is removed, i tried to install several roms but everytime it gives error, for custom roms gives: "archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt"
and for RUUs it gives "UNKNOWN ERROR", i dont know what to do, please help.

safaenet said:
Hi, my one x cid is 044 and i couldnt install JB on it because of that cid, and now i see u r workin on it, please put the link for download the rom (second RUU)
but my main problem is :
i wiped everything, only ClockWorkMod recovery remained, with unlocked bootloader, ROM is removed, i tried to install several roms but everytime it gives error, for custom roms gives: "archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt"
and for RUUs it gives "UNKNOWN ERROR", i dont know what to do, please help.
Click to expand...
Click to collapse
What is your main version ?
Fastboot getvar version-main
Its important to get the right info first ....
Also do
Fastboot oem readcid
I don't have much faith in apps like cidgetter if you used that

Mr Hofs said:
What is your main version ?
Fastboot getvar version-main
Its important to get the right info first ....
Also do
Fastboot oem readcid
I don't have much faith in apps like cidgetter if you used that
Click to expand...
Click to collapse
Fastboot getvar version-main gave version-main: 2.17.707.3
Fastboot oem readcid gave INFODEBUG: cid: HTC__044

Then try to restore the matching nandroid from here
http://forum.xda-developers.com/showthread.php?t=1975140
I say flash the custom recovery again, flash the boot.img from the nandroid, do a FULL wipe in recovery and restore the nandroid backup
Check if that works !

safaenet said:
Hi, my one x cid is 044 and i couldnt install JB on it because of that cid, and now i see u r workin on it, please put the link for download the rom (second RUU)
but my main problem is :
i wiped everything, only ClockWorkMod recovery remained, with unlocked bootloader, ROM is removed, i tried to install several roms but everytime it gives error, for custom roms gives: "archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt"
and for RUUs it gives "UNKNOWN ERROR", i dont know what to do, please help.
Click to expand...
Click to collapse
if the bootlooder is unlocked , please re-lock it by doing this command "fastboot oem lock"
make sure your battery is charged well , then install the stock room
this is JB link
http://shipped-roms.com/download.ph...Radio_5.1204.162.29_release_296434_signed.exe
for more downloads
http://www.shipped-roms.com/index.php?category=android&model=Endeavor
hope this will solve your issue
Regards

Mr Hofs said:
Then try to restore the matching nandroid from here
http://forum.xda-developers.com/showthread.php?t=1975140
I say flash the custom recovery again, flash the boot.img from the nandroid, do a FULL wipe in recovery and restore the nandroid backup
Check if that works !
Click to expand...
Click to collapse
http://forum.xda-developers.com/images/smilies/victory.gif
hi again, i downloaded my matching backup file and restored it and now its working well, thanks alot.

And if you want to upgrade you have to flash back the matching stock recovery !
This one
http://db.tt/U5CK4noo
After this you are able to fully update the phone to JB :thumbup:

Error occured when updating to JB.
ERROR[159]: Image error
The rom update utility cannot update your android phone.
please get the correct ROM update utility and try again.
I wonder if there be any "correct rom" for my phone. i downloaded the stock recovery and installed it. but the ruu for JB cant be installed.
RUU = RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_WWE_3.14.707.24_Radio_5.1204.162.29_release_296434_signed.exe

you dont have to install a RUU, you must update the phone by using the official update in the phone....
go to settings - info - softwareupdates and check for updates manually

Mr Hofs said:
you dont have to install a RUU, you must update the phone by using the official update in the phone....
go to settings - info - softwareupdates and check for updates manually
Click to expand...
Click to collapse
yes i realized it abit late, i downloaded the official uodate (364 MB) in the system update and installed it, but when installed it the phone just restarted and nothing was changed ! i think its because the downloaded update was for 3.14.707.24 software version but mine is 2.17.707.3

so to get this strait, you restored the 2.17.707 nandroid, reflashed the stock 2.17 recovery. did an update to install to 3.14.707 but the software did not change....and you did not have any errors on installing the update ?
check for updates manually again and update again....

Mr Hofs said:
so to get this strait, you restored the 2.17.707 nandroid, reflashed the stock 2.17 recovery. did an update to install to 3.14.707 but the software did not change....and you did not have any errors on installing the update ?
check for updates manually again and update again....
Click to expand...
Click to collapse
hi, i downloaded the sys update and installed it again and now phone is updated to 4.1.1 successfully, thank u very much.
i will flash the CWM recovery and get backup of this ROM, in this recovery i dont know how to take backup.

Flash back the custom clockworkmod 5.8.4.0 recovery and enter it and then select
Backup & restore - backup
It runs a complete backup and puts it on the sdcard in the clockworkmod folder.
your sincere........
Mr Hofs

Ow and now that its all sorted i forgot to say ......
CASE CLOSED !

HTC One M8 Canadian RUU

I need an HTC One M8 Telus/Koodo RUU for my phone. I flashed GPE Rom and it works great but i want the 5.0 update of my carrier but i can't flash it because i am on a custom rom so i would like to revert back to stock in order to flash the 5.0 update.
Any help or suggestion would be appreciated

marawan31 said:
I need an HTC One M8 Telus/Koodo RUU for my phone. I flashed GPE Rom and it works great but i want the 5.0 update of my carrier but i can't flash it because i am on a custom rom so i would like to revert back to stock in order to flash the 5.0 update.
Any help or suggestion would be appreciated
Click to expand...
Click to collapse
Go back to stock, and take the OTAs. Then re-root and enjoy your new firmware.
Visit this thread:
http://forum.xda-developers.com/showthread.php?t=2701376
or this thread:
http://forum.xda-developers.com/showthread.php?t=2710735

I cant do that because i am not s-off

marawan31 said:
I cant do that because i am not s-off
Click to expand...
Click to collapse
Incorrect. This is the method that you use if you are not S-Off.
If you were S-Off, you would just update firmware manually, with no need to go back to stock.

thanks for your help!
ok the second link you posted led me to a canadian nandroid backup.
thanks a lot for your help man
Edit: my hboot is 3.18 and its the only one missing
what should i do?

marawan31 said:
thanks for your help!
ok the second link you posted led me to a canadian nandroid backup.
thanks a lot for your help man
Edit: my hboot is 3.18 and its the only one missing
what should i do?
Click to expand...
Click to collapse
I would suggest asking if anyone has a link to one in that thread.
I'm on Telus too, but I am running WWE firmware. I ALWAYS have the new firmware before Telus. Just sayin.
S-Off is a good thing to have. I know it seems like $25 is a lot to pay to get it, but if you think of all the hassle it saves trying to update firmware, and the other freedom it gives you (I'm using the Sprint Harman/Kardon version's audio files and ADSP) it is very reasonably priced.

xunholyx said:
I would suggest asking if anyone has a link to one in that thread.
I'm on Telus too, but I am running WWE firmware. I ALWAYS have the new firmware before Telus. Just sayin.
S-Off is a good thing to have. I know it seems like $25 is a lot to pay to get it, but if you think of all the hassle it saves trying to update firmware, and the other freedom it gives you (I'm using the Sprint Harman/Kardon version's audio files and ADSP) it is very reasonably priced.
Click to expand...
Click to collapse
i just flashed the one saying 3.x. its a 5.0 nandroid backup and all is working except wifi for some weird reason. looks like the firmware wasnt updated.
i have nothing against paying 25$ its just that sunshine never worked for me. It always said it didnt like my kernel and that i should try with a stock and i was too lazy tbh

marawan31 said:
i just flashed the one saying 3.x. its a 5.0 nandroid backup and all is working except wifi for some weird reason. looks like the firmware wasnt updated.
i have nothing against paying 25$ its just that sunshine never worked for me. It always said it didnt like my kernel and that i should try with a stock and i was too lazy tbh
Click to expand...
Click to collapse
Use 3.34.661.4 backup for 4.4.4 but wifi will not work on your device yet because you have hboot 3.18.0000
Find the 2.23.661.2 -> 3.34.661.4 - thanks @shaboobla on this thread : http://forum.xda-developers.com/showthread.php?t=2701376
Extract out firmware.zip from that OTA zip (with 7-zip)
then you can flash this firmware in RUU mode (but you need to relock bootloader because your device is S-On)
Later .. you can check software update and accept OTA to 4.20.661.2

ckpv5 said:
Use 3.34.661.4 backup for 4.4.4 but wifi will not work on your device yet because you have hboot 3.18.0000
Find the 2.23.661.2 -> 3.34.661.4 - thanks @shaboobla on this thread : http://forum.xda-developers.com/showthread.php?t=2701376
Extract out firmware.zip from that OTA zip (with 7-zip)
then you can flash this firmware in RUU mode (but you need to relock bootloader because your device is S-On)
Later .. you can check software update and accept OTA to 4.20.661.2
Click to expand...
Click to collapse
how would i flash a firmware in RUU mode? you mean like renaming it to some weird name like PG.... and placing it in root of sdcard and going in fasboot? or is it something else because tbh i have never heard of flashing something in RUU mode
thanks for your help, really appreciate it.
EDIT: I just found out i can go to RUU mode with "fastboot oem rebootRUU".
so i can flash the firmware with "fastboot flash zip firmware.zip"
thanks again for all your help guys

marawan31 said:
how would i flash a firmware in RUU mode? you mean like renaming it to some weird name like PG.... and placing it in root of sdcard and going in fasboot? or is it something else because tbh i have never heard of flashing something in RUU mode
thanks for your help, really appreciate it.
EDIT: I just found out i can go to RUU mode with "fastboot oem rebootRUU".
so i can flash the firmware with "fastboot flash zip firmware.zip"
thanks again for all your help guys
Click to expand...
Click to collapse
You found it
1. Make sure you restore the 3.34.661.4 backup first and reboot
2. Boot to bootloader
3. relock bootloader - fastboot oem lock
4. flash the firmware in RUU mode
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip <---- again for the 2nd time
fastboot reboot
5. check software update
6. accept, download, install
7. done
Flash TWRP 2.8.5.0 if you want to flash a custom ROM

ckpv5 said:
You found it
1. Make sure you restore the 3.34.661.4 backup first and reboot
2. Boot to bootloader
3. flash the firmware in RUU mode
fastboot oem rebootRUU
fastboot flash zip hbootMOD3.zip
fastboot flash zip hbootMOD3.zip <---- again for the 2nd time
fastboot reboot
4. check software update
5. accept, download, install
6. done
Flash TWRP 2.8.5.0 if you want to flash a custom ROM
Click to expand...
Click to collapse
You renamed the firmware to hbootMOD3.zip? or do i also need to flash the hboot? if so which hboot do i flash?
lol sorry im easily confused

marawan31 said:
You renamed the firmware to hbootMOD3.zip? or do i also need to flash the hboot? if so which hboot do i flash?
lol sorry im easily confused
Click to expand...
Click to collapse
Ahh.. sorry ... I was in a hurry ... just copy paste from my own note that meant for my personal modded firmware. Edited the post.
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip <---- again for the 2nd time
fastboot reboot

ckpv5 said:
Ahh.. sorry ... I was in a hurry ... just copy paste from my own note that meant for my personal modded firmware. Edited the post.
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip <---- again for the 2nd time
fastboot reboot
Click to expand...
Click to collapse
oh ok thanks man!!
ill post back with the result

marawan31 said:
oh ok thanks man!!
ill post back with the result
Click to expand...
Click to collapse
Just don't forget to relock bootloader before flashing firmware.zip
fastboot oem lock

ckpv5 said:
Just don't forget to relock bootloader before flashing firmware.zip
fastboot oem lock
Click to expand...
Click to collapse
yea i was going to do it and also for the sake of completeness flashing the stock recovery(3.34.661.4) after the restore, just in case someone else has the same problem

You can do that but not really needed because the signed firmware.zip will restore stock recovery.

ckpv5 said:
You can do that but not really needed because the signed firmware.zip will restore stock recovery.
Click to expand...
Click to collapse
oh didnt know that, i guess i wont then

I just wanted to thank you guys for helping me out!
I did everything and now i am on android 5.0.1 (although i ran into a small problem: process com.android.phone is not responding, factory reset from recovery fixed it)
Hope this thread helps someone else with similar problems

https://photos.google.com/album/AF1QipNmb1q2tT6uldWZLHQSLD1fsauQYRMlkHmA5y1g/photo/AF1QipPXGvhZ063BpX0f30U4O7d6ZYQgTkgeowCWDywd
Sorry for reviving such an old thread, but I'm trying to get my htc one m8 up and running again. It was functioning on lineage os but wasn't very stable, couldn't find any other roms that would successfully flash on it, I decided to try and go back to stock after a few beers one night night, now the phone has been sitting in a drawer with no os or recovery on it. There doesn't seem to be any still functioning links to any Canadian RUU's that I can use. I'm not s-off, bootloader is "relocked". I'd like to go back to stock marshmallow because I only use this thing to play music and as a tv remote. I'm hoping someone might have an old RUU lying around.
I guess if not my best option is just to unlock the bootloader again and try flashing the same lineage os again. Since I relocked does that mean I have to go through the htc website to get the unlock token again like I did ages ago? They probably don't even have this phone on there anymore. Hopefully I didn't actually turn this thing into a brick.

Please see my comments in red font below:
350Rocket said:
https://photos.google.com/album/AF1QipNmb1q2tT6uldWZLHQSLD1fsauQYRMlkHmA5y1g/photo/AF1QipPXGvhZ063BpX0f30U4O7d6ZYQgTkgeowCWDywd
Photo link is coming up with 404 error for me. Better to do fastboot getvar all, then post the results (cut and paste from command prompt), so we can see all the info on the phone (delete IMEI and serial number before posting).
Sorry for reviving such an old thread, but I'm trying to get my htc one m8 up and running again. It was functioning on lineage os but wasn't very stable, couldn't find any other roms that would successfully flash on it,
If you can be more specific about which ROMs you tried (plus info about your device from getvar as noted above), then we might be able to advise why they did not flash. Did you get error messages, and if so, what exactly were they?
I decided to try and go back to stock after a few beers one night night, now the phone has been sitting in a drawer with no os or recovery on it.
What exactly did you do (step by step, with any relevant file names, etc. - more detail is better).
I presume you intentionally relocked the bootloader in attempt to run some RUU. But would like clarification on this (and where that happened in the sequence of events)
There doesn't seem to be any still functioning links to any Canadian RUU's that I can use. I'm not s-off, bootloader is "relocked". I'd like to go back to stock marshmallow because I only use this thing to play music and as a tv remote. I'm hoping someone might have an old RUU lying around.
Far as I know, Canadian versions don't have RUU.
I guess if not my best option is just to unlock the bootloader again and try flashing the same lineage os again. Since I relocked does that mean I have to go through the htc website to get the unlock token again like I did ages ago? They probably don't even have this phone on there anymore. Hopefully I didn't actually turn this thing into a brick.
One option (maybe the best one) is to restore a stock TWRP back from the collection: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
You will need to unlock the bootloader to do this. You can either reuse the unlock bin code you used originally (if you still have it). Otherwise, you should be able to request a new bin code from HTCDev.com. Far as I know, that still works for this phone.
Click to expand...
Click to collapse

Help me with my first Ruu

Hello guys. I was having problems getting the update. Then I found out , you can Ruu with S-ON but needs Bootloader Re Locked. Anyway, as it's my first time I wanna ask few question so I don't end up with a dead phone.
So, what I understood is Ruu will update all the other partition except System/ROM. On S-ON it needs Re Locked bootloader, the Ruu needs to be higher version than the Hboot OS version, the Ruu needs to be fully stock and it'll wipe the Internal Storage.
So, I first use "fastboot oem lock" then " fastboot rebootRuu" "fastboot flash zip xxx.zip" then it'll stuck on 75%-90% and I'll have to use "fastboot reboot-bootloader".
And I'll get the Android M Bootloader, recovery and other stuffs, right?
Now I'll be at Bootloader, have to use that Token_Unlocker.bin to Unlock again, flash twrp and flash a Marshmallow ROM and It'll be fully Android M.
This is what I understood. Please tell me if I'm right or not. Correct me if I'm wrong. I can't S-OFF , so this is only way. I also don't want a hard brick. So, please help.
I have some questions though. I've currently Viperone 5.0 ROM on Lollipop base. Do I have to go back to stock ROM before I can use Ruu? Do I have to get Stock recovery before I can start Ruu? Will Ruu erase the ROM? If Ruu erase everything, will my memory card be safe or should I remove it before Ruu and insert it to flash ROM after Ruu is done?
Thanks in advance for replying.

You have the proper RUU for your CID?
My responses below in red font:
Saikat.mondol1 said:
So, what I understood is Ruu will update all the other partition except System/ROM. RUU will wipe the System (ROM) partition as well. Not sure why you would think otherwise.
So, I first use "fastboot oem lock" then " fastboot rebootRuu" "fastboot flash zip xxx.zip" then it'll stuck on 75%-90% and I'll have to use "fastboot reboot-bootloader". It might get stuck, but doesn't always. Of course, its good to know what to do, in case it does get stuck.
And I'll get the Android M Bootloader, recovery and other stuffs, right? The phone will be formatted to MM stock condition, all partitions.
Now I'll be at Bootloader, have to use that Token_Unlocker.bin to Unlock again, flash twrp and flash a Marshmallow ROM and It'll be fully Android M. You will already be on the stock MM ROM after RUU (as I've somewhat mentioned above). If you want to unlock the bootloader, TWRP, and install a MM custom ROM, you can do that.
Alternately, if you want to root the stock MM ROM, unlock bootloader, TWRP, and flash SuperSU 2.64 or later.
I have some questions though. I've currently Viperone 5.0 ROM on Lollipop base. Do I have to go back to stock ROM before I can use Ruu? NO
Do I have to get Stock recovery before I can start Ruu? NO
Will Ruu erase the ROM? YES
If Ruu erase everything, will my memory card be safe or should I remove it before Ruu and insert it to flash ROM after Ruu is done? Removable SD should be safe. But remove it before RUU, just to be safe.
Click to expand...
Click to collapse

redpoint73 said:
You have the proper RUU for your CID?
My responses below in red font:
Click to expand...
Click to collapse
Thanks a lot man. I've tried but it said "Error 12: Signature failed" Need a signed Ruu

Saikat.mondol1 said:
Thanks a lot man. I've tried but it said "Error 12: Signature failed" Need a signed Ruu
Click to expand...
Click to collapse
What is your device's CID, and what RUU are you trying to run?

redpoint73 said:
What is your device's CID, and what RUU are you trying to run?
Click to expand...
Click to collapse
htc_002 . And look at this thread http://forum.xda-developers.com/htc...ess-fuu-m8-t2813792/post64916167#post64916167

redpoint73 said:
What is your device's CID, and what RUU are you trying to run?
Click to expand...
Click to collapse
"Error 12: Signature failed" -- He needs htc_fastboot.exe not google fastboot.exe
http://forum.xda-developers.com/showpost.php?p=64893560&postcount=17