Develop Bugs

[Q] Flashing Stock RUU

Hi Everyone,
I have become slightly frustrated as I seem to be unable to flash the stock rom back onto my HTC One X. I have a CID of HTC__001 which seems to be perfect and I am with Orange Uk. I have downloaded the correct RUU for the specific radio I have (2.1204.135.20) and when I run the exe in windows. It starts to work and then says my USB is not connected.
Previously I have been rooted and have flashed the recovery image, which does mean I am connected via use and in fastboot mode. Not sure what is causing this issue. If anyone could provide any assistance that would be fantastic.
Thanks
Andy

Andy,
Ruus need stock recovery. Are you back on stock recovery? Also, phone must be booted up into rom and respond to adb commands such as
Adb devices
This should list your devices serial number as connected. If you see that, then try running the ruu.
Sent from my HTC One X using xda premium

1. If you have HTC__001 then download the 2.17.401.2 RUU from here - http://d-h.st/HoB
2. Relock your bootloader!!
3. Boot the phone into fastboot and connect to the PC
4. Run the RUU
That's it, no stock recovery required

Thanks
Thanks for both of your replies. I have since managed to install the sense jelly bean roms from Insert Coin and also Maximum, realised that I did not need to install the RUU, just need to flash the boot.img. All is now great. The RUU that you posted was the one i tried but failed :s Its ok now though as now I am unable to return to ICS roms

EddyOS said:
1. If you have HTC__001 then download the 2.17.401.2 RUU from here - http://d-h.st/HoB
2. Relock your bootloader!!
3. Boot the phone into fastboot and connect to the PC
4. Run the RUU
That's it, no stock recovery required
Click to expand...
Click to collapse
Hello
Im on the same situation, but i cant get the RUU to install. I flashed the stock recovery, i relock the bootloader, but im always getting Error 155 Im with full batery, i run as administrator but i cant get thr RUU to flash. Any idea? Thanks in advance:fingers-crossed:

DropePT said:
Hello
Im on the same situation, but i cant get the RUU to install. I flashed the stock recovery, i relock the bootloader, but im always getting Error 155 Im with full batery, i run as administrator but i cant get thr RUU to flash. Any idea? Thanks in advance:fingers-crossed:
Click to expand...
Click to collapse
How far does the RUU installer get? I had problems on the weekend where it got to the install shield then stopped. This was resolved by turning off norton and running as administrator.

shadwell_lad said:
How far does the RUU installer get? I had problems on the weekend where it got to the install shield then stopped. This was resolved by turning off norton and running as administrator.
Click to expand...
Click to collapse
I only get into the black screen with HTC logo:silly: I have Microsoft Security Essentials, already flashed RUU without problems, this was the 1st time. Meanwhile, flashed now with football rom, Revolution without any problems. Just wonder if when OTA will be available, if i can install it

thanks so much guys, this helped me a lot!

Help needed!
Hi guys. I'm very new to this so forgive me if I seem a bit stupid at times. I've been reading a lot and trying to learn things about the phone but I've got myself a bit stuck.
I have a HOX with the following;
*** relocked ***
CID HTC__001
Hboot 1.12.0000
radio-2.1204.135.20
Everything was stock, I unlocked and rooted. All went well, everything worked fine. Didn't install any ROM's. Installed CWM. Then JB was released so I unrooted and relocked and flashed stock recovery.
The phone now has;
Android 4.0.4
HTC Sense 4.1
Software 2.17.401.2
API 4.23
HTC Extension 403_1_GA_20
Everything works. I can boot the phone and everything works as it should. The only issue I can see is that it won't boot into recovery. I get the green arrows, press power and up volume, some errors are reported on the screen - Cannot find /cache/recovery/command and Failed to open loopdevice, no such file or directory. The phone then restarts and boots the OS.
My question is, what should I do next to be able to receive the OTA JB update? I assume I'll need to do some combination of flashing the boot.img and recovery.img but I'm unsure what the process is, or even if my assumptions are correct? Help??
EDIT 1 : I found this. http://forum.xda-developers.com/showthread.php?t=1193540
I think it's what I need. I just need to read some more and find out what ROM I need to download. Can anyone advise if this is in fact what I need to do and what ROM I should be looking for?
EDIT 2 : I also found this RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
Can anyone confirm for me this is the process and the ROM I need to return to stock before I go ahead and run this?
In advance, thank you for any help/advice that's offered.

The RUU should work.
That guide is for a different phone. Check the stickies in the dev section of this forum.

BenPope said:
The RUU should work.
That guide is for a different phone. Check the stickies in the dev section of this forum.
Click to expand...
Click to collapse
Thanks for the reply BenPope. Yea, I saw the guide was for a different device, but the steps are virtually identical. I went ahead and ran the RUU. Everything flashed OK, no errors, no issues. Re-locked the bootloader. Still can't run recovery tho. Still getting the same errors. As I understand it I won't be able to get OTA updates installed if Recovery isn't working correctly. Have I got this right? Any ideas?

You're saying everything in the wrong order. Please be more clear.
To run the RUU, your hboot needs to be locked. If after the RUU you can't access recovery something went wrong and the RUU failed. What errors are you getting?

g12__ said:
EDIT 2 : I also found this RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
Can anyone confirm for me this is the process and the ROM I need to return to stock before I go ahead and run this?
In advance, thank you for any help/advice that's offered.
Click to expand...
Click to collapse
Take boot_signed.img and recovery_signed and Rom.zip from the RUU. Boot to fastboot, flash boot_signed.img and recovery.img . Boot to recovery and flash the rom.zip.
Sent from my HTC One X using xda premium

Your problem was due to flashing stock recovery AFTER relock.
Try this:
1. Unlock again.
2. Fastboot flash stock recovery.
3. Then, relock.
4. Boot your phone.
Try to update then.
Sent from my HTC One X using XDA Premium HD app

EddyOS said:
1. If you have HTC__001 then download the 2.17.401.2 RUU from here - http://d-h.st/HoB
2. Relock your bootloader!!
3. Boot the phone into fastboot and connect to the PC
4. Run the RUU
That's it, no stock recovery required
Click to expand...
Click to collapse
is this RUU same for cid_032????????????????

yode said:
is this RUU same for cid_032????????????????
Click to expand...
Click to collapse
2.17.401.2 RUU is for :
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__M27
cidnum: HTC__032
cidnum: HTC__016
cidnum: HTC__J15

I have a stupid question.
I've flashed my device with the official European JB RUU 3.14.401.27 (if i'm correct).
I've relocked my bootloader etc, and RUU update is done.
But the bootloader said it's **RELOCKED**.
Is there a way to remove that text without SuperCID?
And will it be a problem to send my device back to HTC repair center? (for the G-sensor.. )
Thanks in advance!

****head said:
I have a stupid question.
I've flashed my device with the official European JB RUU 3.14.401.27 (if i'm correct).
I've relocked my bootloader etc, and RUU update is done.
But the bootloader said it's **RELOCKED**.
Is there a way to remove that text without SuperCID?
And will it be a problem to send my device back to HTC repair center? (for the G-sensor.. )
Thanks in advance!
Click to expand...
Click to collapse
It's impossible to change or remove that text .
You will have to pay for repair unless you are extremely lucky.
Sent from my HTC One X

TToivanen said:
It's impossible to change or remove that text .
You will have to pay for repair unless you are extremely lucky.
Sent from my HTC One X
Click to expand...
Click to collapse
sigh ....
thanks for the info.
do you know how much they will ask for the repair?

****head said:
do you know how much they will ask for the repair?
Click to expand...
Click to collapse
No but there is a slight chance it could be covered by warranty since it is a hardware fault. Sorry for your loss man.
Sent from my HTC One X

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

RUU Error 155 despite relocked bootloader

Phone specs:
Code:
RELOCKED
M8_UL PVT SHIP S-OFF
CID-11111111
HBOOT-3.16.0.0000
RADIO-1.23.213311491.05G
OpenDSP-v48.2.2-00564-M8974_FO.1211
OS-4.20.531.4 (1.54.401.5)
eMMC-boot 2048MB
So I'm trying to update my One M8, and I think I messed up pretty bad. I tried running the RUU updater for my T-Mobile variant (found on HTC's ROM Download page), but got the infamous "error 155." However, my bootloader is re-locked. Therefore, according to all the forum posts I could find, I shouldn't be getting that error. I've run a few commands since then, including fastboot oem writecid 11111111 and fastboot erase cache. Somehow, I've managed to get to the point where my phone won't even boot into recovery, it just gets stuck at the "Entering recovery..." screen. However, while stuck on this screen, the phone does respond to ADB commands. I can get root shell access, but I'm not sure what to do with it.
I've tried flashing TWRP 3.0.0.0 to no avail. I've tried running fastboot boot <twrp filename here>, also to no avail. I'm pretty much stuck with a phone that only boots into fastboot, and a weird purgatory-recovery where I can achieve shell access. The RUU file fails to update no matter what I do.
Is there a way I can fix this, or have I completely bricked my phone?
Thank you for your time.

RalphORama said:
Phone specs:
Code:
RELOCKED
M8_UL PVT SHIP S-OFF
CID-11111111
HBOOT-3.16.0.0000
RADIO-1.23.213311491.05G
OpenDSP-v48.2.2-00564-M8974_FO.1211
OS-4.20.531.4 (1.54.401.5)
eMMC-boot 2048MB
So I'm trying to update my One M8, and I think I messed up pretty bad. I tried running the RUU updater for my T-Mobile variant (found on HTC's ROM Download page), but got the infamous "error 155." However, my bootloader is re-locked. Therefore, according to all the forum posts I could find, I shouldn't be getting that error. I've run a few commands since then, including fastboot oem writecid 11111111 and fastboot erase cache. Somehow, I've managed to get to the point where my phone won't even boot into recovery, it just gets stuck at the "Entering recovery..." screen. However, while stuck on this screen, the phone does respond to ADB commands. I can get root shell access, but I'm not sure what to do with it.
I've tried flashing TWRP 3.0.0.0 to no avail. I've tried running fastboot boot <twrp filename here>, also to no avail. I'm pretty much stuck with a phone that only boots into fastboot, and a weird purgatory-recovery where I can achieve shell access. The RUU file fails to update no matter what I do.
Is there a way I can fix this, or have I completely bricked my phone?
Thank you for your time.
Click to expand...
Click to collapse
Have you flashed both stock recovery for the RUU in particular youre flashing and re-locked BL, and are you installing a version number that is equal to or higher than the one you already have installed.
Completely stock phone should flash RUU, as long as its not a version down from whats installed, ie, trying to flash LP when MM is already flashed on phone, UNLESS of course youre s-off and supercid, because with supercid you should be able to flash any RUU .
But i had similar issues, im s-on, so i had to revert to stock LP completely, then flashed HTC__001 Stock MM for my phone, failing all that there is always the option of copying a nandroid on here to ur sd card, boot into twrp and restore the Nandroid just to get it up and running again.
I would run the RUU, let it sit at first screen, goto start button and type in %temp%, find the folder inside temp that ruu just created, (sort by date), pull the rom.zip from that to ur desktop, Unzip it and get the files recovery and boot.img, flash them both to ur phone via fastboot, if it still works, then restart ur phone and it should load up, you could then try to install the RUU from windows again, failing that after flashing recovery and boot, goto ur stock recovery and wipe and reset then reboot phone.
It doesnt sound like hard brick, just soft brick, it should be ok.

If you try to flash a Android MM ruu i suggest to flash a lower ruu first. Usually the big jump from the 3.16 boot loader to a 3.19 boot loader is too much.
Or flash the standalone firmware first and then the full ruu.
The high version of TWRP doesn't work because your bootloader is too low (3.16) if you want a working TWRP then use a 2.7 version.
If you can get to the bootloader then it's just a softbrick. A hardbrick is only when the bootloader is not accessible anymore or when the phone doesn't boot up in any way anymore.
Cheers

Mr Hofs said:
Or flash the standalone firmware first and then the full ruu.
Click to expand...
Click to collapse
This is most likely the solution. In particular, if OP is trying to install MM RUU, there is a new peculiarity (requirement?) with all MM RUUs, where you need to have MM firmware in order to run the RUU, or else you will have Error 155.
Find the firmware.zip that matches the version number of the RUU, flash it; then try the RUU again.
---------- Post added at 09:42 AM ---------- Previous post was at 09:35 AM ----------
gazza35 said:
Have you flashed both stock recovery for the RUU
Click to expand...
Click to collapse
You don't need stock recovery to RUU. Folks keep saying this, and its not true.
You need stock recovery to OTA, but you do not need it for RUU. OTA and RUU are two very different things.
gazza35 said:
because with supercid you should be able to flash any RUU .
Click to expand...
Click to collapse
This is also not true. You need to match MID and CID (or SuperCID) in order to flash an RUU. SuperCID bypasses the CID check, but you still need to pass the MID check.
---------- Post added at 09:44 AM ---------- Previous post was at 09:42 AM ----------
gazza35 said:
But i had similar issues, im s-on, so i had to revert to stock LP
Click to expand...
Click to collapse
Same peculiarity with the MM RUU I mentioned above (need to flash the MM firmware if coming from LP) also applies if you try to downgrade back to LP. Meaning, you need to flash the LP firmware, then LP RUU.

Mr Hofs said:
If you try to flash a Android MM ruu i suggest to flash a lower ruu first. Usually the big jump from the 3.16 boot loader to a 3.19 boot loader is too much.
Or flash the standalone firmware first and then the full ruu.
The high version of TWRP doesn't work because your bootloader is too low (3.16) if you want a working TWRP then use a 2.7 version.
If you can get to the bootloader then it's just a softbrick. A hardbrick is only when the bootloader is not accessible anymore or when the phone doesn't boot up in any way anymore.
Cheers
Click to expand...
Click to collapse
Thank you (and everyone else) for your replies! Out of curiosity, where can I find a lower RUU? I can only find the most recent one from HTC's website.
EDIT: I flashed TWRP 2.7 and I was able to boot into recovery! I love progress.

RalphORama said:
Out of curiosity, where can I find a lower RUU? I can only find the most recent one from HTC's website.
Click to expand...
Click to collapse
You can find the links for older T-Mob RUUs here: http://forum.xda-developers.com/showthread.php?t=2714456

OTA to 4.19.617.1, this package is for htc_himaulatt devices; this is a htc_himauh

Hi Folks,
I wonder if anyone can point me in the right direction please. Here's the story:
I bought a T-mobile branded HTC One M9
Changed it to WWE and ran with a it for a while without issue
Changed to Dev edition and applied the Android7OTA.zip (4.14.617.6) then TWRP, currently running without issue.
I got a notification of another OTA (4.19.617.1) earlier this evening.
Flashed the stock recovery I extracted from the android 7 dev RUU
Downloaded the OTA on the phone and once the phone booted into the stock recovery, I'm told:
'this package is for "htc_himaulatt" devices; this is a "htc_himauhl". Installation aborted'
Fastboot getvar all currently shows:
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) serialno: xxxx
(bootloader) current-slot:
(bootloader) imei: xxxx
(bootloader) version-main: 4.14.617.6
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440971_103.00.61018G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: BS_US001
I've read of using a cid of BS_US002, I've changed to that and retried applying the OTA, but it did the same (so I changed it back).
Assuming the Product reported by fastboot is what's being checked... fastboot's reporting it's already set to what the stock recovery seems to be saying it needs to be. It was happy flashing the first RUU, I'm not sure what might be different this time round.
I bet there's a small thing I might need to change, but I don't know what.
Does anyone else please?
Also.. I've not found much info at all about the OTA to 4.19.617.1. Is it new enough that me somehow getting it off the phone (will probably need brief instructions) could be useful to anyone?
TIA!

Currently having the same problem.
Will post here if i have any luck.

Thanks philicibine.
I've just tried it with supercid too (fastboot oem writecid 11111111), but it didn't do the trick.
Before the phone reboots into the stock recovery, it says ''we have determined that your phone may be running a modified version of its system software....'.

ok so my phone is currently accepting the update!
The problem for me was I had installed TWRP. In trying to restore the stock recovery i was restoring the one from the NoWipe firmware file i used to upgrade to Nougat.
To solve, I extracted the recovery.img from the OTA.zip and flashed that.
Almost finished updating!
here is the recovery.img if you want to try it >> https://drive.google.com/open?id=0BzkydKcZdx9YWW55UDlIOV95UDA

philicibine said:
ok so my phone is currently accepting the update!
The problem for me was I had installed TWRP. In trying to restore the stock recovery i was restoring the one from the NoWipe firmware file i used to upgrade to Nougat.
To solve, I extracted the recovery.img from the OTA.zip and flashed that.
Almost finished updating!
here is the recovery.img if you want to try it >> https://drive.google.com/open?id=0BzkydKcZdx9YWW55UDlIOV95UDA
Click to expand...
Click to collapse
It was the stock recovery from the first android7 devRUU that I've been trying this with. Which OTA did you get this one from?
I've flashed it and the newest OTAs downloading again as I type..
edit: the file you posted a link to (thanks!) and the recovery I was originaly using are definitely different... My phones just failed to apply the update again, but given a different reason 'system parition has unexpected contents'. Guess I've not left system untouched as I thought.
I've just tried extracting system from the original devAndroid7RUU.zip and now I'm getting errors about it not being able to decrypt the .zip.. so must have somehow taken the recovery from another RUU.zip earlier this evening (which wouldn't have been a devRUU, but a WWE-explaining why it reported my phone didnt match the dev edition details). I was doing it remotely form work, while working-must be more careful, I guess.
This means I cant extract system from the right RUU.zip though.
I think I could flash the RUU.zip again (wiping everything, grrr), then let it install the later OTA before doing anything that could amend system.
I'd realy like to not wipe it if posible though.
How did you get the recovery you posted out of the OTA.zip please?

It maybe the same recovery then as I got it from the Dev ota. Seemed to work for me. Maybe you could flash the nowipe firmware and then this if it doesn't work?
---------- Post added at 10:53 PM ---------- Previous post was at 10:40 PM ----------
mad_tunes said:
How did you get the recovery you posted out of the OTA.zip please?
Click to expand...
Click to collapse
I simply unzipped it. It was in the firmware.zip archive inside the OTA.zip

I'm pretty confident the two recovery's are different, my phone does different things with the OTA depanding on which of the recovery's I've flashed.
I used 'HTC_RUU_Decrypt_Tool_3.1.0-WINDOWS64' to extract the recovery from what I thought was the devRUU.zip. This wont open the devRUU.zip now though, so I must have had it extract the wrong RUU earlier.
I've just flashed the stock android7 firmware and the recovery you posted a link to and the OTAs re-downloading
Edit:
I'm still in the same situation, it's reporting system's modified
I think I might just RUU it again. I need my phone running and set up over the next few days though, so it'll have to wait until Christmas is out the way.
Many thanks for your help though.
Do you see many differences after you've applied it?
(And I managed to type ota instead of ruu in the op, I've amended)

Hey guys,
I'm having the exact same issue. The way I was working it around was flashing the update via RUU from laptop but now I'm tired kf doing that every time when there is an update. I will restore my factory recovery and will try it again. After I've done so, I'll get back to you about it.
Best Regards

I couldn't sleep last night, so went for it with the DevRUU.zip I originally used..
It flashed fine as before, then my phone downloaded and applied the OTA just fine.
I couldn't get SuperSU to install properly afterwards though, so restored a TWRP backup so I could use my phone today.
I've been getting the OTA notification repeatedly during the day today though. Seems you can only postpone it for up to 4 hours, rather than dismiss it or turn off checking entirely. It's annoying.
So, I might give it another go pretty soon!

I just RUUd again and then did the OTA.
SuperSU-v2.65 (that I was using pre-OTA) woudn't install, showing 'Patching secpol. Failed. Arborting'
SuperSU-v2.79 installed just fine.
Sorted.

Hey guys. Just went to stock recovery. Unzipped from ota.zip>installed it>recovery works>phone reboot into system>finds the new update>starts to install>rebokts to recovery>starts updating up to 24%25% and then gets me back to recovery saying there is some error. What should I do? I don't want to update via RUU. Thanks

dohcvtec said:
Hey guys. Just went to stock recovery. Unzipped from ota.zip>installed it>recovery works>phone reboot into system>finds the new update>starts to install>rebokts to recovery>starts updating up to 24%25% and then gets me back to recovery saying there is some error. What should I do? I don't want to update via RUU. Thanks
Click to expand...
Click to collapse
100% working method. keep these conditions and everything is working and updated - unlocked cid BS__US001 S-OFF mid 0PJA11000. then install from sd card 0PJAIMG nougat download the update OTA 4.19.617.1 and everything is fine to install without errors!!!!!!!!!!!! check for yourself!!!!!

asar201 said:
100% working method. keep these conditions and everything is working and updated - unlocked cid BS__US001 S-OFF mid 0PJA11000. then install from sd card 0PJAIMG nougat download the update OTA and everything is fine to install without errors!!!!!!!!!!!! check for yourself!!!!!
Click to expand...
Click to collapse
But if I follow those steps, this means fresh new install of the os which is basically the same as RUU install. Or you nent something else? Thanks
P. S. I just fully unrooted my phone so now it is exactly the way you described above but the new update still doesn't install. It gives me this error and I don't understand why: 'system parition has unexpected contents'

dohcvtec said:
But if I follow those steps, this means fresh new install of the os which is basically the same as RUU install. Or you nent something else? Thanks
P. S. I just fully unrooted my phone so now it is exactly the way you described above but the new update still doesn't install. It gives me this error and I don't understand why: 'system parition has unexpected contents'
Click to expand...
Click to collapse
hi.a poor understanding of English and how to correctly put on this site files. I had the same problem. phone-htc__a07 no rooted android 6.0 twrp recovery. OTA updates do not come to android 7.0. write step by step what did was changed the cid to BS__US001,mid on 0PJA11000.restored twrp backup http://forum.xda-developers.com/one-m9/development/one-m9-4-14-617-6-stock-root-twrp-backup-t3518149 then came the notice about the ota updates until they 4.19.617.1 but I have not installed the same as yours.https://drive.google.com/drive/folders/0BwrbLN0SdCTgQ2NseVMtdDhXV3c?usp=sharing I flashed these recovery and firmware and after that everything was installed.try. flash a twrp backup of course is not necessary if you already is 7.0 skip this step...

Hello,
Reporting back.
So what I did was, I took the RUU, flashed RUU, then updated to the newest update with no problem. Had no issues restoring my phone exactly how it was before to flash the RUU. Phone restored automatically from google account. The only thing which didn't restore was my wallpaper (like I care about it ). So that's it. Thank you very much for your help.
Best Regards

dohcvtec said:
Hello,
Reporting back.
So what I did was, I took the RUU, flashed RUU, then updated to the newest update with no problem. Had no issues restoring my phone exactly how it was before to flash the RUU. Phone restored automatically from google account. The only thing which didn't restore was my wallpaper (like I care about it ). So that's it. Thank you very much for your help.
Best Regards
Click to expand...
Click to collapse
couldn't tell what ruu was flashed? and what was your cid and mid?

asar201 said:
couldn't tell what ruu was flashed? and what was your cid and mid?
Click to expand...
Click to collapse
The RUU that I flashed is the official version from HTC website. Flashed it through laptop. CID BS_US001 MID 0PJA11000

dohcvtec said:
The RUU that I flashed is the official version from HTC website. Flashed it through laptop. CID BS_US001 MID 0PJA11000
Click to expand...
Click to collapse
thanks for inform ))))

I just wanted to add to the list of install methods. Here is what I attempted.
All attempts with MID 0PJA11000:
Rooted 4.14.617.6 with TWRP recovery and CID BS_US001 - OTA failed (doesnt hurt to try )
Flashing RUU 4.14.617.6.exe with CID BS_US001 - OTA failed
Flashing RUU 4.14.617.6.exe with CID 11111111 - OTA failed
Flashing RUU 4.14.617.6.zip with CID 11111111 - OTA failed
After the above line and changing the CID to BS_US001 - successful
It appears you must run an ruu.zip to accept the OTA no matter what. Strange the exe's will not work. It also appears the master CID no longer works. Surprisingly I was able to change the CID after running the .zip install and still accept the OTA with no problems.
asar201 said:
100% working method. keep these conditions and everything is working and updated - unlocked cid BS__US001 S-OFF mid 0PJA11000. then install from sd card 0PJAIMG nougat download the update OTA 4.19.617.1 and everything is fine to install without errors!!!!!!!!!!!! check for yourself!!!!!
Click to expand...
Click to collapse
asar201 I did want to ask and make sure, did you use double __ in your CID or just one _?

BrownEye02 said:
I just wanted to add to the list of install methods. Here is what I attempted.
All attempts with MID 0PJA11000:
Rooted 4.14.617.6 with TWRP recovery and CID BS_US001 - OTA failed (doesnt hurt to try )
Flashing RUU 4.14.617.6.exe with CID BS_US001 - OTA failed
Flashing RUU 4.14.617.6.exe with CID 11111111 - OTA failed
Flashing RUU 4.14.617.6.zip with CID 11111111 - OTA failed
After the above line and changing the CID to BS_US001 - successful
It appears you must run an ruu.zip to accept the OTA no matter what. Strange the exe's will not work. It also appears the master CID no longer works. Surprisingly I was able to change the CID after running the .zip install and still accept the OTA with no problems.
asar201 I did want to ask and make sure, did you use double __ in your CID or just one _?
Click to expand...
Click to collapse
Hello...a double underline!!! you and all who can help spread the link twrp backup, installed the OTA to 4.19.617.1. those who are not from Russia in the file, replace gps.conf data on your country,because in my backup it changed to ru.pool.ntp.org for a quick search of satellites in twrp recovery without installing a root file Manager copy the modified gps.conf (system\etc). p.s. Change CID (only if S-OFF) fastboot oem writecid BS__US001 reboot fastboot Change MID (only if there is S-OFF) fastboot oem writemid 0PJA11000 fastboot reboot. there's also posted the stock recovery and firmware. if you wish to flash from sd card file rom.zip folder 4.14.617.6 RUU rename 0PJAIMG.zip and copy to sd card restart your device in download mode. don't know what else to add... ))) if you have any questions...write. https://drive.google.com/drive/folders/0BwrbLN0SdCTgQ2NseVMtdDhXV3c?usp=sharing

HTC M8(TMOB101) Revert to Stock Issue

Sorry..if it's an already solved issue.
I'm using an unlocked HTC M8 which I rooted, unlocked bootloader and installed the latest Lineage OS (Android 7.1.2).
I got a good offer for the device and would like to sell it. So I want to revert it back to stock.
The device information are :
version-main: 6.12.111.4
version-misc: PVT SHIP S-ON
modelid: 0P6B10000
cidnum: T-MOB101
I could only find a Lollipop firmware for my CID which I copied into my SD card as OP6BIMG.zip
But the bootloader gives error as "Large Image Update Failed..Press power to reboot"
This goes on until I remove my SD card.
The RUU I used is "0P6BIMG_M8_UL_L50_SENSE60_MR_TMO_DE_4.19.111.3_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_449335_combined_signed.zip"
Is this because I'm trying to downgrade Android version?
Also should I try after re-locking the bootloader (which is something I'm a bit worried to do because I think I will end up in an even worse condition if it doesn't work...because in my experience with an M9 it never unlocks again after relocking in a custom rom.)
Please help.

If you can't find 6.12.111.4, restore fully stock backup
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
You don't need to relock bootloader to restore nandroid
Edit : here is RUU.zip - https://www.androidfilehost.com/?fid=24399965296001026
You need to relock bootloader to install RUU

ckpv5 said:
If you can't find 6.12.111.4, restore fully stock backup
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
You don't need to relock bootloader to restore nandroid
Edit : here is RUU.zip - https://www.androidfilehost.com/?fid=24399965296001026
You need to relock bootloader to install RUU
Click to expand...
Click to collapse
OK..will try the RUU zip after relocking bootloader.
Hope it works.
Will update about the same after.

Downloading...

So I relocked my bootloader.. downloaded the RUU zip.. renamed it to 0P6BIMG and put in my SD card.
Booted into bootloader and voila.. it flashed right away and now am back to pure stock.
Thank you..ckpv5 for all the help.
You saved my day.

[email protected] said:
I'm using an unlocked HTC M8 which I rooted, unlocked bootloader and installed the latest Lineage OS (Android 7.1.2).
I got a good offer for the device and would like to sell it. So I want to revert it back to stock.
Click to expand...
Click to collapse
Just good practice: Always make a TWRP backup before flashing a custom ROM, root, etc.
I personally never start messing with these phones, without beforehand having some strategy to get back to stock.
[email protected] said:
The device information are :
version-main: 6.12.111.4
I could only find a Lollipop firmware for my CID which I copied into my SD card as OP6BIMG.zip
But the bootloader gives error as "Large Image Update Failed..Press power to reboot"
This goes on until I remove my SD card.
The RUU I used is "0P6BIMG_M8_UL_L50_SENSE60_MR_TMO_DE_4.19.111.3_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_449335_combined_signed.zip"
Is this because I'm trying to downgrade Android version?
Click to expand...
Click to collapse
Correct. You cannot "downgrade" by RUU with s-on.
[email protected] said:
Also should I try after re-locking the bootloader (which is something I'm a bit worried to do because I think I will end up in an even worse condition if it doesn't work...because in my experience with an M9 it never unlocks again after relocking in a custom rom.)
Click to expand...
Click to collapse
Typically, no problem unlocking the bootloader on the M8 again, after relocking it.
Locked or Relocked bootloader is required to RUU with s-on.

redpoint73 said:
Just good practice: Always make a TWRP backup before flashing a custom ROM, root, etc.
I personally never start messing with these phones, without beforehand having some strategy to get back to stock.
Correct. You cannot "downgrade" by RUU with s-on.
Typically, no problem unlocking the bootloader on the M8 again, after relocking it.
Locked or Relocked bootloader is required to RUU with s-on.
Click to expand...
Click to collapse
Thanks for all the information.
Will definitely keep these in mind the next time I try to mess with software;

Hello a quick question, instead of reverting to stock by RUU, can I flash a Sense-based rom via TWRP? I am presently on Lineage 15.1 with latest TWRP and S on. Thank you.

Babakkardan said:
Hello a quick question, instead of reverting to stock by RUU, can I flash a Sense-based rom via TWRP? I am presently on Lineage 15.1 with latest TWRP and S on. Thank you.
Click to expand...
Click to collapse
If you are looking to go back to stock..you can use Stock RUU zip of your model to flash via recovery.

[email protected] said:
If you are looking to go back to stock..you can use Stock RUU zip of your model to flash via recovery.
Click to expand...
Click to collapse
You can't flash RUU.zip with recovery. It will fail if you try to do so. You need to flash RUU.zip with htc_fastboot in RUUmode. Otherwise use the SD card method (auto install in bootloader). Another alternative is to flash the RUU executable (.exe).

redpoint73 said:
You can't flash RUU.zip with recovery. It will fail if you try to do so. You need to flash RUU.zip with htc_fastboot in RUUmode. Otherwise use the SD card method (auto install in bootloader).
Click to expand...
Click to collapse
Oops my bad...I actually meant the sd card method renaming the rom to OP6BIMG.
:angel:
(Thanks for correcting)