Develop Bugs

Flashing to stock rom,One X is this correct?

I've done my google searching, i really have. So I hope i didn't miss out on a sticky or anything else because i did check, if i didn't find it i must be blind. However,most guides I found to flash to stock rom were not on XDA. And just to be sure I've decided to come back over here and ask if this process is correct:
Also I am coming from ARHD 2.05.. so is a downgrade to 1.26 possible, do i need any kernels? Anyways here is how i'd proceed
1. Download stock recovery.img, put it in c:\fastboot
2. download the stock ruu for your specific phone
3. Boot phone into fastboot
4. open up cmd, in cmd type "cd\"
5. type "cd fastboot"
6. type in"fastboot flash recovery recovery.img"
7. type "fastboot oem lock"
(phone restarts in this case)
8. back in fastboot
9. open up stock RUU for your phone:
Agree to terms and just "next"(basically follow on-screen instructions)
... bla bla bla... and we have stock?
Is this processs correct?
Am I missing on anything, as i would be coming from ARHD.
Once again I apologize if this has been posted or if there's a guide on XDA, i've really done my searching, i just can't risk ruining this baby
Thanks in advance

This is roughly right yes. If you were on 1.26 before flashing a custom rom then you can flash the 1.26 RUU, and any higher version firmware (1.28, 1.29). if you were on 1.28 or 1.29 firmware then you cannot downgrade to 1.26, you will need to flash your current firmware version or higher. also with cmd, if you saved your fastboot file to c:\Android\fastboot then the command to get to that folder will be "cd c:\Android\fastboot"

teky said:
This is roughly right yes. If you were on 1.26 before flashing a custom rom then you can flash the 1.26 RUU, and any higher version firmware (1.28, 1.29). if you were on 1.28 or 1.29 firmware then you cannot downgrade to 1.26, you will need to flash your current firmware version or higher. also with cmd, if you saved your fastboot file to c:\Android\fastboot then the command to get to that folder will be "cd c:\Android\fastboot"
Click to expand...
Click to collapse
Does that mean I cannot get back to stock as of now? I found the 1.26 RUU and it's around 566.2 mb.
But before flashing I was on 1.29...

shadehh said:
Does that mean I cannot get back to stock as of now? I found the 1.26 RUU and it's around 566.2 mb.
But before flashing I was on 1.29...
Click to expand...
Click to collapse
you will need to find the 1.29 RUU for your phone then. have a search in HERE for the right RUU

teky said:
you will need to find the 1.29 RUU for your phone then. have a search in HERE for the right RUU
Click to expand...
Click to collapse
It's not released yet it seems. Okay, here my final question:
My final question:
So basically even though i am on ARHD 7.1.0 and have the latest firmware
I had 1.29 before flashing
I am only able to get back to stock if i have the 1.29 Ruu OR a NEWER version?(i know currently no newer official version present but assuming there is)
edit: me silly, i reread your first post and that's exactly what you stated. haha! Thank you anyway >_> guess i gotta wait for a RUU to be released

[HELP] - Need help running RUU - Getting Sig Error 132

Hi All,
I really hate running RUU's, but now I think I must run one, and use the newer kernel..
I have HTC_001 - with my version being the .401. one...
I have now downloaded two RUU's that both fail on the Signature Error - Error code 132.
I'm fastboot oem lock, then running the RUU... Is there anything I must do?
At the moment I'm restoring my nandroid backup from before trying (tried at least 10 since last night, 2 different computers too), as I need my phone...
Is there any other way to do it? I just want a newer hboot, but am on 0.43 now...
Any help apprciated...
Thanks, Matt
EDIT: I'm on <fastboot getvar mainver> 1.26.401.2 - I'm now downloading an ICS ruu, and if that works, will do the ota (hopefully)... Still any help appreciated..

Could you do: fastboot get main-version
If you wont to upgrade to JB with RUU i think your HBOOT version is to low, so you first need to upgrade firmware:
1. You can upgrade firmware to "middle" version if you use ICS RUU
2. Then you can use JB RUU, or only JB firmware
cid firmware for you :http://forum.xda-developers.com/showthread.php?t=1957376 this is the latest HBOOT.
But first post info after : fastboot get main-version

hpnxfox said:
Could you do: fastboot get main-version
If you wont to upgrade to JB with RUU i think your HBOOT version is to low, so you first need to upgrade firmware..
Click to expand...
Click to collapse
haha, just edited my post... 1.26.401.2
But how can I upgrade my firmware - this ruu is supposed to do that...
As said, I'm downloading an ICS ruu, then I guess will OTA if that works... - Only thing is... The ruu will take at least 1 Hour to download, with my bad download speeds...

So, yes you need first to use RUU with matching CID and main version, then you can do OTA upgrade all the way to JB and HBOOT 1.39..
But be aware if you do officially OTA upgrade to JB yours phone touch.img will be also updated and you have problems with touch in custom recoveries like CWM or TWRP!
If you do official update to JB:
1. TWRP 2.5.0.0 or 2.4.0.0 - reapcked version have touch but usb mass storage in recovery and adb isn't functional
2. CWM 6.0.3.0-have adb and usb mass storage but no touch because of developer restriction
So it is better to upgrade OTA to latest ICS version and manually just upgrade HBOOT to 1.39..

hpnxfox said:
So, yes you need first to use RUU with matching CID and main version, then you can do OTA upgrade all the way to JB and HBOOT 1.39..
But be aware if you do officially OTA upgrade to JB yours phone touch.img will be also updated and you have problems with touch in custom recoveries like CWM or TWRP!
If you do official update to JB:
1. TWRP 2.5.0.0 or 2.4.0.0 - reapcked version have touch but usb mass storage in recovery and adb isn't functional
2. CWM 6.0.3.0-have adb and usb mass storage but no touch because of developer restriction
So it is better to upgrade OTA to latest ICS version and manually just upgrade HBOOT to 1.39..
Click to expand...
Click to collapse
Thanks, will give it a go...
If anything, I will compile a touch version of CWM and use that for personal use... (I have done in the past (6.0.2.7)).
So if this ICS ruu works, then just the FW JB Flasher Tool to upgrade to latest hboot? If so, sounds good

To flash firmware with fastboot commands after you upgrade to latest ICS - i am not using tools ore similar one click tools , but for flashing firmware you cant just flash
You need to lock bootloader again for flashing firmware (it should bee locked already because you need to lock to flash RUU) and then when phone is in bootloader(fastboot usb mode actually):
1.fastboot oem rebootRUU
2.fastboot flash zip firmware.zip
After HBOOT upgrade boot to hboot to check is it really there, and then unlock bootloader again, and flash custom recoveries..
And here are the links for working custom recoveries(with mentioned restrictions in previous post) if you decide to upgrade via OTA all the way to JB
1.TWRP 2.5.0.0 http://forum.xda-developers.com/showpost.php?p=40120901&postcount=509
2.CWM 6.0.3.0 http://forum.xda-developers.com/showthread.php?t=1941630
3.CWM Advanced Edition] PhilZ Touch http://forum.xda-developers.com/showpost.php?p=40442326&postcount=1

hpnxfox said:
To flash firmware with fastboot commands after you upgrade to latest ICS - i am not using tools ore similar one click tools , but for flashing firmware you cant just flash
You need to lock bootloader again for flashing firmware (it should bee locked already because you need to lock to flash RUU) and then when phone is in bootloader(fastboot usb mode actually):
1.fastboot oem rebootRUU
2.fastboot flash zip firmware.zip
After HBOOT upgrade boot to hboot to check is it really there, and then unlock bootloader again, and flash custom recoveries..
And here are the links for working custom recoveries(with mentioned restrictions in previous post) if you decide to upgrade via OTA all the way to JB
1.TWRP 2.5.0.0 http://forum.xda-developers.com/showpost.php?p=40120901&postcount=509
2.CWM 6.0.3.0 http://forum.xda-developers.com/showthread.php?t=1941630
3.CWM Advanced Edition] PhilZ Touch http://forum.xda-developers.com/showpost.php?p=40442326&postcount=1
Click to expand...
Click to collapse
Thnaks for all the help here... I am now on the newer hboot (1.39) Yay!!
However, just tried to reflash a recvoery and it didnt work lol... It failed to write it... So will keep trying this, but any pointers? <- helps if I spell recovery properly, doesn't it... lol
Restoring my nandroid backup from when I locked the device.... and on newer hboot... thanks a lot!!

Did you unlock bootloader again with bootloader unlocking procedure with unlock key from htcdev? (you talking about flashing custom recovery.img?)

hpnxfox said:
Did you unlock bootloader again with bootloader unlocking procedure with unlock key from htcdev?
Click to expand...
Click to collapse
I edited my post;
Code:
c:\android\tools>fastboot flash recvoery "C:\Users\Webmaster\Documents\My Dropbox\Android\recoveries
\recovery-6.0.2.3-endeavoru.img"
sending 'recvoery' (6058 KB)...
OKAY [ 0.724s]
writing 'recvoery'...
FAILED (remote: not allowed)
finished. total time: 0.939s
All looks good to me...
Thanks a lot for your help...

Ah "recvoery"..yes, always the smallest things good luck with HOX
And "button thanks" to you also, it was one more new experience to me!

hpnxfox said:
Ah "recvoery"..yes, always the smallest things good luck with HOX
Click to expand...
Click to collapse
Yep, everything is working... Back into my rom now too, so im very happy!!
You say good luck with the HOX, I actually have a rom out (actually a few) for the HOX... I am a skilled user (if I do say so myself)... Just I hate RUU's, and with my previous HTC deivce (HTC Desire), I was always told it was a bad move to flash RUU's...
I must admit it is a bit of a pain, but all is working now... And I didnt even do the OTA to JB, just got the ICS main-version, and the JB hboot... as you suggested - Sweet
Again, thank you for all your help

mattmanwrx said:
Yep, everything is working... Back into my rom now too, so im very happy!!
You say good luck with the HOX, I actually have a rom out (actually a few) for the HOX... I am a skilled user (if I do say so myself)... Just I hate RUU's, and with my previous HTC deivce (HTC Desire), I was always told it was a bad move to flash RUU's...
I must admit it is a bit of a pain, but all is working now... And I didnt even do the OTA to JB, just got the ICS main-version, and the JB hboot... as you suggested - Sweet
Again, thank you for all your help
Click to expand...
Click to collapse
I see that you are "Big Boy" in android land You don't have so many thanks buttons because of nothing
I'm on beginning, i'm not in developers waters..i tried but i missing knowledge..

hpnxfox said:
Ah "recvoery"..yes, always the smallest things good luck with HOX
And "button thanks" to you also, it was one more new experience to me!
Click to expand...
Click to collapse
after reading this thread......Yeah it could have been easier

hpnxfox said:
I see that you are "Big Boy" in android land You don't have so many thanks buttons because of nothing
I'm on beginning, i'm not in developers waters..i tried but i missing knowledge..
Click to expand...
Click to collapse
Well I started off theme'ing, then moved to modding apps, now playing with source, it has only taken me 2 years lol!!!
Mr Hofs said:
after reading this thread......Yeah it could have been easier
Click to expand...
Click to collapse
What is the easier way Mr Hofs? Just for anyone else who might ask? or if I need to do it again etc?

You only needed to install the 1.26, 1.28, 1.29 or the 2.17 ruu....they will work right away. A JB ruu only works when you are on at least a 2.17 based software.
Or flash the JB firmware right away. This will actually lift the hboot directly to 1.39.....
It could be done in 2 posts ..... but we are all here to learn so this all has been a very good experience :thumbup:
Ow and losing the touch function on the official newer base is no problem at all, all the cwm recoverys can be controlled with the volume and power button !

I don't argue with Mr Hofs , he is expert and have all info in his head, i just can blindly follow his instructions without struggling :laugh:

Mr Hofs said:
You only needed to install the 1.26, 1.28, 1.29 or the 2.17 ruu....they will work right away. A JB ruu only works when you are on at least a 2.17 based software.
Or flash the JB firmware right away. This will actually lift the hboot directly to 1.39.....
It could be done in 2 posts ..... but we are all here to learn so this all has been a very good experience :thumbup:
Ow and losing the touch function on the official newer base is no problem at all, all the cwm recoverys can be controlled with the volume and power button !
Click to expand...
Click to collapse
But as I was on 0.43 hboot, I couldnt flash the firware.zip to bring hboot up? or could I... I was in the understanding of I needed newer than 0.43 to flash a newer hboot...
But also, it would have helped me to know that I cannot go straight to JB RUU from 0.43 - that would have saved me a lot of time lol!!
anyways, i flashed the 1.28, which bought me up to 0.96 (I think), then changed hboot to 1.39 - so all is fine for me now
Thanks for the suggestions though, I might need them for when I buy my HTC One lol

Yeah that's good too no problem there.
The thing is that the standalone firmware flash to upgrade the hboot can be done from any low hboot.
Only the JB ruu can be installed from the 1.12 or higher...

Well, all I know, is that is is done now!! lol...
So I'm happy... and I guess can make this thread as "Solved"

Very true ! And a :thumbup: up for hpn !
I will answer you PM tonight Mr Hpn

stock platform.xml

i modified my platform.xml to enable w/r access for the sdcard a few months back.
there was a copy of the original, er, 'somewhere' but i cant find it now.
i have removed the line added i in before but the 4.4.4 ota update is failing because of platform.xml.
anyone have a stock unmodified platform.xml they could upload here or pm?
my M8 is a dual sim version if that makes any difference.
thanks.

You should be able to find your RUU here and extract the file in question:
http://forum.xda-developers.com/showthread.php?t=2701376

berndblb said:
You should be able to find your RUU here and extract the file in question:
http://forum.xda-developers.com/showthread.php?t=2701376
Click to expand...
Click to collapse
Nope, dont see it. is there one? (its a dual sim version)
couldnt see one on htcdev either.
i already have a signed zip file
0P6BIMG_M8_DUGL_K44_SENSE60_HTC_Europe_1.45.401.12_R_Radio_1.18.30306251.05G_30.57.306251.00L_release_381655_combined_signed.zip
but as it is signed i cannot extract anything from it
winrar always say corrupt image, is there another way?

Solved?
Did you solve the problem? I have exactly the same issue . . .
gazzacbr said:
Nope, dont see it. is there one? (its a dual sim version)
couldnt see one on htcdev either.
i already have a signed zip file
0P6BIMG_M8_DUGL_K44_SENSE60_HTC_Europe_1.45.401.12_R_Radio_1.18.30306251.05G_30.57.306251.00L_release_381655_combined_signed.zip
but as it is signed i cannot extract anything from it
winrar always say corrupt image, is there another way?
Click to expand...
Click to collapse

simonvfr said:
Did you solve the problem? I have exactly the same issue . . .
Click to expand...
Click to collapse
Hi,
not exactly. but i am on 4.4.4
i was toying with the idea of winding back to stock using nandroid, rooting and copying out platform.xml, then having another go at OTA...
but, i thought i might as well give MaximusHD 4.4.4 for dual sim a go as i was going to wipe anyway.
i flashed TWRP latest 2.8.1 and updated firmware (link is on Maximus page) and then ROM.
so thats where i am now and happy with the rom.
100% stable, no issues noticed at all and aroma removed some bloat for me as i installed.
no need to go back now.
i will wait for lollipop from HTC and all those custom roms for M8 dual sim to try out (er, joke)

gazzacbr said:
Hi,
not exactly. but i am on 4.4.4
i was toying with the idea of winding back to stock using nandroid, rooting and copying out platform.xml, then having another go at OTA...
but, i thought i might as well give MaximusHD 4.4.4 for dual sim a go as i was going to wipe anyway.
i flashed TWRP latest 2.8.1 and updated firmware (link is on Maximus page) and then ROM.
so thats where i am now and happy with the rom.
100% stable, no issues noticed at all and aroma removed some bloat for me as i installed.
no need to go back now.
i will wait for lollipop from HTC and all those custom roms for M8 dual sim to try out (er, joke)
Click to expand...
Click to collapse
Thanks. As I am rooted, with TWRP, but S-ON, I think I can't flash the new firmware. Or am I wrong on that?
I have nandroid backup from my original stock, so could go back to that and re-lock and then do the OTA, but it's a long slow way of getting to 4.4.4!
An alternative would be Cyanogenmod - but although CM11 supports multi-sim phones I can find nothing clear about whether the official builds support the M8 dual-sim.
Finding the M8 ROM situation frustrating after messing around endlessly with custom ROMs on Acer dual sim phone . . . .

simonvfr said:
Thanks. As I am rooted, with TWRP, but S-ON, I think I can't flash the new firmware...
Click to expand...
Click to collapse
you can but you have to re-lock the boot loader which will wipe your phone.
i used these instructions (I am S-OFF already) and firmware from link on Maximus site:
-------------------------------------------------------
How to flash firmware
### If you are S-ON ---> Re-lock your bootloader (this will most probably wipe content of your device)
If you are S-OFF ---> no need to re-lock the bootloader.
Copy downloaded .zip to fastboot.exe location
Re-name .zip file to firmware.zip
Open command prompt
Boot your device in fastboot mode (vol DOWN + power ===> fastboot)
Connect device to the PC
In command prompt cd to fastboot.exe location
Make sure you have correct modeid and cidnum (type: fastboot getvar all)
### Type: fastboot oem lock (if your device is not relocked yet or in case it's S-ON)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware.zip and wait for process to complete
Flash firmware.zip again just to make sure.
Type: fastboot reboot-bootloader
-------------------------------------------------------
what i am sure of is that without the new firmware you will not have wifi
i thought i flashed the firmware first but didnt do it twice and it didnt stick. after the rom was installed i had no wifi but guessed that was the problem and re flashed the firmware. then it was ok.
as for cyanogenmod, unless it states it is for M8 Dual SIM then i wouldnt bother unless youve got time to experiment and hope for updates.
i know there are many arguments as to why you dont really need S-OFF for most normal operations but it a real fail-safe when things get messed up (my 2c)
just find the $25 for sunshine, its worth it.

gazzacbr said:
you can but you have to re-lock the boot loader which will wipe your phone.
i used these instructions (I am S-OFF already) and firmware from link on Maximus site:
-------------------------------------------------------
How to flash firmware
### If you are S-ON ---> Re-lock your bootloader (this will most probably wipe content of your device)
If you are S-OFF ---> no need to re-lock the bootloader.
Copy downloaded .zip to fastboot.exe location
Re-name .zip file to firmware.zip
Open command prompt
Boot your device in fastboot mode (vol DOWN + power ===> fastboot)
Connect device to the PC
In command prompt cd to fastboot.exe location
Make sure you have correct modeid and cidnum (type: fastboot getvar all)
### Type: fastboot oem lock (if your device is not relocked yet or in case it's S-ON)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware.zip and wait for process to complete
Flash firmware.zip again just to make sure.
Type: fastboot reboot-bootloader
-------------------------------------------------------
what i am sure of is that without the new firmware you will not have wifi
i thought i flashed the firmware first but didnt do it twice and it didnt stick. after the rom was installed i had no wifi but guessed that was the problem and re flashed the firmware. then it was ok.
as for cyanogenmod, unless it states it is for M8 Dual SIM then i wouldnt bother unless youve got time to experiment and hope for updates.
i know there are many arguments as to why you dont really need S-OFF for most normal operations but it a real fail-safe when things get messed up (my 2c)
just find the $25 for sunshine, its worth it.
Click to expand...
Click to collapse
Thanks for response. In the meantime I have gone S-OFF with Sunshine, but I have not yet flashed the new firmware or the ROM.
For firmware flashing, I was going to use the process described here on XDA. Seems very simple . . .

simonvfr said:
Thanks for response. In the meantime I have gone S-OFF with Sunshine, but I have not yet flashed the new firmware or the ROM.
For firmware flashing, I was going to use the process described here on XDA. Seems very simple . . .
Click to expand...
Click to collapse
But in the end I had to use the method you suggest, as once the ROM was installed I had no firmware and was therefore stuck in bootloader. With some fiddling I managed to sort it all out, and everything is now running.
Thanks for your help

[Q] New One M8, old HTC user: Need help understanding a few things

Hello All,
So I recently bought a M8 and I just need some help in getting the steps nailed down correctly. Be warned long post with lots of questions...
Code:
fastboot getvar version-main
version-main: 3.32.111.3
fastboot oem readcid
(bootloader) cid: T-MOB101
That is basically my device, now due to it being 4.4.4 from factory I am unable to use Sunshine & Weaksauce. I could wait until the new year but why
bother .
First step:
Get my factory firmware image after reading this thread: http://forum.xda-developers.com/showthread.php?t=2701376 due to it being a T-Mobile and
Germany and 4.4.4 I am unable to run the command listed there to get the stock recovery, so how do I get the stock recovery for my device? @BerndM14
Has provided me with a link to download the latest firmware for my device but it has the TWRP recovery inside it, link is this one: http://www.handy-
faq.de/forum/htc_one_m8_custom_roms/304821-htc_one_m8_firmwaresammlung_ruus_otas_backups.html#post2832636. I should point out that I do have a OTA
waiting to download and install, should I download and install it? The version listed on the screen is 3.32.111.9 and is only 183.73MB. Would it have a
viable stock recovery? Can I downgrade to a older version for the stock recovery?
Second step:
Once the above is done and dusted my next step is getting root & S-OFF & custom recovery. This is relatively simple because all I need to do is visit
HTCDev, unlock and then S-OFF with Sunshine and then a custom recovery. Correct? Sounds and looks simple enough.
Third step:
Download ROM of choice and flash away. So I am going with InsertCoin due to user loyalty from the Desire days . However I see people in the thread
mentioning that they flashed the latest firmware to sort out a couple of issues, I take it they mean the ROM file and not HTC firmware?
Fourth and probably not needed step:
Changing the phone to WWE and SuperCID? Do I really need to do this? Benefit of changing to WWE is changing the HBOOT to a more universal one? The
reason why I am thinking of converting is because I would want to get rid of the red text on the boot screen as listed here: http://forum.xda-
developers.com/showpost.php?p=51744965&postcount=1 however for T-Mobile Dutch the HBOOT CIDS are T-MOB003, if I flash that would it cause a problem?
I would also be looking at running the commands to change the flags showing tampered and unlocked but that looks simple to do. Am I missing anything? For warranty purposes I would use the instructions from this thread: http://forum.xda-developers.com/showthread.php?t=2710735 but download the recovery file for T-MOB Germany instead?
Thank you for reading the long post and I hope that I have made some sort of sense.

Yes it will have the firmware.zip with the recovery.img inside it. Even the small 47MB or so, OTA update for the WWE from 2.22.401.4 - 2.22.401.5 had the firmware.zip inside. So just download the OTA.zip copy to PC extract firmware.zip and grab the recovery.img.
Benefits to converting to WWE or even Developer edition also includes the fact that those devices will receive OTA updates before any carrier version, directly from HTC. It's a bonus if you're into the "latest & greatest" scene.
As for making a backup before flashing custom recovery, have you tried booting the custom recovery? Philz will probably be better if you want to use the booted custom recovery to make a backup of stock recovery. You could also try and boot either TWRP or Philz and see if you can root your device without flashing custom recovery, that way you can at least use the dd command to grab a copy of the recovery block. <My preferred method, though it's a terrible circle. Need to flash custom recovery to root, need root to make backup of stock recovery... So hopefully booting the custom recovery will work. That being said, easiest way still remains to grab it from the OTA.zip.
Perhaps you could even upload a copy of the OTA.zip and share it on here, I don't think the OP has a copy in the second post
ROM/Firmware. You need the latest firmware to run the latest ROM. For most it'll be firmware with 3.x. If you still run on 2.x(which you aren't) you'd have some problems with radio(bluetooth, gps, wifi, data etc)

Thank you for the reply .
To be honest I have not tried booting a custom recovery because I saw this in the first post of this thread: http://forum.xda-developers.com/showthread.php?t=2701376
fastboot boot recovery_filename.img (this does not work on the latest 3.xx firmwares !!! we need to get the stock recoveries from the OTA files)
Click to expand...
Click to collapse
So I am not sure what to try to be honest. This toolkit: http://forum.xda-developers.com/showthread.php?p=51383278&highlight=ota#post51383278 mentions getting root without S-OFF but with a unlocked bootloader. So I am thinking that if I follow those steps, maybe when I get to the reboot phase I can execute a nandroid instead which might get me the files I want?
I won't bother with WWE then. I will rely on the dev's to give me the latest & greatest .

Anakha56 said:
Thank you for the reply .
To be honest I have not tried booting a custom recovery because I saw this in the first post of this thread: http://forum.xda-developers.com/showthread.php?t=2701376
So I am not sure what to try to be honest. This toolkit: http://forum.xda-developers.com/showthread.php?p=51383278&highlight=ota#post51383278 mentions getting root without S-OFF but with a unlocked bootloader. So I am thinking that if I follow those steps, maybe when I get to the reboot phase I can execute a nandroid instead which might get me the files I want?
I won't bother with WWE then. I will rely on the dev's to give me the latest & greatest .
Click to expand...
Click to collapse
Hm, yeah I also had some problems booting a recovery, but I just tested it out again. I can at least boot TWRP version 2.8.3.0 so it still works for me. I'm on 3.28.1540.5 (Developer edition). Haven't tried Philz though, net a bit too slow to bother with even a small download

No problem. I am busy downloading the OTA.zip and once complete I will try the toolkit method and see what happens . Again, thank you for the reply.

I need some help... My phone seems to be stuck in fastboot mode and is not picked up in Device Manager of Windows. I can touch the fastboot screen and it vibrates but it does not nothing. I have held down the power button for 20 seconds with no result. I had just unlocked the bootloader and then tried pushing the Philz recovery image to the device with the command line:
Code:
C:\android\sdk\android\platform-tools>fastboot boot philz_touch_6.57.8-m8.img
downloading 'boot.img'...
OKAY [ 1.541s]
booting...
OKAY [ 0.002s]
finished. total time: 1.547s
*edit*
Holding volume up + power for 10 seconds helped *whew*...

Anakha56 said:
Thank you for the reply .
To be honest I have not tried booting a custom recovery because I saw this in the first post of this thread: http://forum.xda-developers.com/showthread.php?t=2701376
So I am not sure what to try to be honest. This toolkit: http://forum.xda-developers.com/showthread.php?p=51383278&highlight=ota#post51383278 mentions getting root without S-OFF but with a unlocked bootloader. So I am thinking that if I follow those steps, maybe when I get to the reboot phase I can execute a nandroid instead which might get me the files I want?
I won't bother with WWE then. I will rely on the dev's to give me the latest & greatest .
Click to expand...
Click to collapse
You don't need S-Off to root, just the unlocked bootloader, custom recovery, and superuser.

@xunholyx Thanks for the post . I am trying to get an image of my stock recovery file first, so I am trying to avoid flashing the custom recovery right now . BTW Does anyone know if TWRP makes a backup of the stock recovery before overwriting it like Philz does?

Anakha56 said:
@xunholyx Thanks for the post . I am trying to get an image of my stock recovery file first, so I am trying to avoid flashing the custom recovery right now . BTW Does anyone know if TWRP makes a backup of the stock recovery before overwriting it like Philz does?
Click to expand...
Click to collapse
http://www.handy-faq.de/forum/htc_o...resammlung_ruus_otas_backups.html#post2832635
oops sorry.. i see you already been their
your hboot 3.19 will prevent booting to recovery ... and no TWRP doesn't backup stock recovery
you just need to find the OTA.zip for your version it must be out their somewhere

@clsA I have the file
3.32.111.3 - TWRP
Click to expand...
Click to collapse
From that site but its recovery is TWRP. I am trying to grab the stock recovery currently on the device before going forward. When I unzip that file it has 6 items:
boot.emmc.win
boot.emmc.win.md5
system.ext4.win000
system.ext4.win000.md5
system.ext4.win001
system.ext4.win001.md5
Click to expand...
Click to collapse
I have downloaded the OTA that is ready for my phone but I had hit a snag. The file was corrupt, on redownload I have the small OTA but the recovery version number has incremented past mine, I don't know if it will be still useable with the ROM file from the link?

Anakha56 said:
@clsA I have the file
From that site but its recovery is TWRP. I am trying to grab the stock recovery currently on the device before going forward. When I unzip that file it has 6 items:
I have downloaded the OTA that is ready for my phone but I had hit a snag. The file was corrupt, on redownload I have the small OTA but the recovery version number has incremented past mine, I don't know if it will be still useable with the ROM file from the link?
Click to expand...
Click to collapse
it should work, recovery does not have to be exact just close
and the file you have doesn't include TWRP .. it was created with twrp ... big difference

Anakha56 said:
@clsA I have the file
From that site but its recovery is TWRP. I am trying to grab the stock recovery currently on the device before going forward. When I unzip that file it has 6 items:
I have downloaded the OTA that is ready for my phone but I had hit a snag. The file was corrupt, on redownload I have the small OTA but the recovery version number has incremented past mine, I don't know if it will be still useable with the ROM file from the link?
Click to expand...
Click to collapse
You can use any 3.32 based stock recovery for your phone. There are plenty of backups for that on this thread. No need to backup your own.

Thank you guys! That helps me a lot! Off I go to flash a custom recovery .

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