Hello guys,
I just got a brand new HTC One M9 Developer Edition. It has Marshmallow version 3.35.617.12.
I see that Nougat already rolled out for some variants, so i was expecting to have the update available for my model since it is a "developer/unlocked" version... However, there are no updates available when clicking on Settings -> About -> Software update. I went to HTC website and found that there is a Nougat release for this model, version 4.23.617.1.
First i tried to update using the RUU exe downloaded from the HTC link above, but i got the error 132 (signature error).
Then i tried to update downloading the .zip file from "androidfilehost" website, placing it on SDCard and rebooting into download mode, but i got the message "ZIP error". I tried with two different files, and both resulted on same error.
My last try was to download an OTA from "androidfilehost" website, place it on the SDCard, reboot into recovery mode and select to apply update from SDCard. This time, i got the message "fingerprint error".
When i boot into download mode, i get:
*** LOCKED ***
htc_himaulatt PVT S-OFF
CID-BS_US002
I checked the IDs using fastboot and got this:
modelid: 0PJA11000
cidnum: BS_US002
I checked these IDs using a table that i found on another post, and they are correct. So, as far as i understand, these updates should be compatible with my phone.
Am i missing something? I appreciate if somebody can give me a hint.
Thanks!
Spike_Fire said:
Hello guys,
I just got a brand new HTC One M9 Developer Edition. It has Marshmallow version 3.35.617.12.
I see that Nougat already rolled out for some variants, so i was expecting to have the update available for my model since it is a "developer/unlocked" version... However, there are no updates available when clicking on Settings -> About -> Software update. I went to HTC website and found that there is a Nougat release for this model, version 4.23.617.1.
First i tried to update using the RUU exe downloaded from the HTC link above, but i got the error 132 (signature error).
Then i tried to update downloading the .zip file from "androidfilehost" website, placing it on SDCard and rebooting into download mode, but i got the message "ZIP error". I tried with two different files, and both resulted on same error.
My last try was to download an OTA from "androidfilehost" website, place it on the SDCard, reboot into recovery mode and select to apply update from SDCard. This time, i got the message "fingerprint error".
When i boot into download mode, i get:
*** LOCKED ***
htc_himaulatt PVT S-OFF
CID-BS_US002
I checked the IDs using fastboot and got this:
modelid: 0PJA11000
cidnum: BS_US002
I checked these IDs using a table that i found on another post, and they are correct. So, as far as i understand, these updates should be compatible with my phone.
Am i missing something? I appreciate if somebody can give me a hint.
Thanks!
Click to expand...
Click to collapse
Unfortunately, you can only update from Marshmallow to Nougat via the OTA. This and the reasons for it are explained in the readme thread.
I wonder if it would be worthwhile to flash the marshmallow RUU and check for updates then. It may be that something is goofy on your current setup - a RUU will reset your phone and perhaps clear out whatever issue is preventing your phone from seeing the OTA.
Hey, thanks for the tip. I managed to update successfully. Here is what i had to do:
1) Updated to the latest Marshmallow release using "0PJAIMG_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.31.zip" on SDCard and booting on download mode.
2) Updated to Nougat using "OTA_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.14.617.6_R-3.35.617.31_release_490897lkj8xif5v3eoiykd.zip" on SDCard and booting on recovery mode -> Apply update form SD Card.
3) Updated to latest Nougat using "RUU_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.30.617.2.exe"
Curiously, after step 1 and 2 i tried to check if there is a software update available on "settings -> about -> software update", but on both steps it says that there is no update available...
Thank you very much!
Easiest way is flashing nougat firmware.zip first then do your desired update option.
Spike_Fire said:
Hey, thanks for the tip. I managed to update successfully. Here is what i had to do:
1) Updated to the latest Marshmallow release using "0PJAIMG_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.31.zip" on SDCard and booting on download mode.
2) Updated to Nougat using "OTA_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.14.617.6_R-3.35.617.31_release_490897lkj8xif5v3eoiykd.zip" on SDCard and booting on recovery mode -> Apply update form SD Card.
3) Updated to latest Nougat using "RUU_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.30.617.2.exe"
Curiously, after step 1 and 2 i tried to check if there is a software update available on "settings -> about -> software update", but on both steps it says that there is no update available...
Thank you very much!
Click to expand...
Click to collapse
Hmm. I'm wondering about this upgrade path. According to the readme thread:
Flippy498 said:
It seems like HTC changed its encryption keys between firmware 3.x and 4.x. Therefore, you cant flash 4.x RUUs if your phone is currently using a 3.x firmware. [emphasis added] You either need to flash a NoWipe/Full-Wipe Firmware Pack beforehand (only possible with S-OFF) or you need to use a 3.x RUU for the same SKU and install the 4.x OTA, afterwards.
Click to expand...
Click to collapse
It sounds like you've got the Nougat software (woohoo!) but I'm wondering if the path you've taken means something didn't get installed that may be necessary in the future. Or maybe you somehow had the Nougat firmware but a Marshmallow OS. It's beyond me, but exceptions make me nervous and what you've described sounds rather exceptional.
But hey, if it's performing as expected, great! I'm glad it has (apparently) worked out. Enjoy Nougat!
@side_flip15: But that's not possible with S-ON.
@computerslayer: He did what I wrote in my ReadMe thread. He installed a 4.x OTA for updating the encryption keys and then a 4.x RUU. (Well, not exactly what I wrote since I personally don't recommend flashing OTAs manually if you can't install them via the software update function of the stock rom but it looks like the flashing process was successful.) I don't know what you expect to be missing...
OTAs are incremental. That means they can only be used on one specific firmware version. If he had no problems with manually flashing the OTA then he was using the correct initial firmware. RUUs on the other hand contain everything: the whole firmware + the system. Therefore the phone has everything that it needs, now.
When I wrote that part of the RUU section there only was one update for firmware 4.x. However, at this point HTC's already released some more 4.x updates. And just like on pre-4.x firmware you can skip installing several OTAs by using a RUU for the latest version.
@Flippy498 yes not possible on s-on devices. I'm just basing my comment on @Spike_Fire's situation.
My bad. I missed the fact that his phone is S-OFF... :silly:
Flippy498 said:
And just like on pre-4.x firmware you can skip installing several OTAs by using a RUU for the latest version.
Click to expand...
Click to collapse
This is what I was misunderstanding. I interpreted the section I quoted earlier as meaning the 4.x firmware was so unique (regarding the whole encryption key piece) that it absolutely couldn't be installed except by OTA. Thank you for the correction.
Spike_Fire said:
Hey, thanks for the tip. I managed to update successfully. Here is what i had to do:
1) Updated to the latest Marshmallow release using "0PJAIMG_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.31.zip" on SDCard and booting on download mode.
2) Updated to Nougat using "OTA_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.14.617.6_R-3.35.617.31_release_490897lkj8xif5v3eoiykd.zip" on SDCard and booting on recovery mode -> Apply update form SD Card.
3) Updated to latest Nougat using "RUU_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.30.617.2.exe"
Curiously, after step 1 and 2 i tried to check if there is a software update available on "settings -> about -> software update", but on both steps it says that there is no update available...
Thank you very much!
Click to expand...
Click to collapse
I'm in the exact same position as you were. Plus i'm a total noob since this is my first droid. Where did you download the 3 files necessary to update to nougat? Also is the file in step 3 the latest nougat firmware still and is the search for updates problem solved?
D35t5tr0k3 said:
I'm in the exact same position as you were. Plus i'm a total noob since this is my first droid. Where did you download the 3 files necessary to update to nougat? Also is the file in step 3 the latest nougat firmware still and is the search for updates problem solved?
Click to expand...
Click to collapse
Hello mate,
You can find the files on androidfilehost.
The file of step 3 is not the latest anymore. I guess the latest is 4.30.617.12. You can download it directly from HTC website: htc.com/us/support/rom-downloads.html#unlocked]
Tip: currently im using LeeDroid ROM ported from HTC10 (LeeDroid_10). There is thread for it on the main page of this forum. This ROM is fantastic. It keeps the main cosmetics of the stock HTC rom, adding several improvements over the original M9 ROM (camera app mainly IMO). I may give it a try.
Regarding the automatic system updates (settings -> about -> ...), unfortunately it didnt work even after installing the RUU firmware (which supposedly should bring the device to the absolute stock condition)... it simply says that "there is no update available...".
Good luck!
Spike_Fire said:
Hello mate,
You can find the files on androidfilehost.
The file of step 3 is not the latest anymore. I guess the latest is 4.30.617.12. You can download it directly from HTC website: htc.com/us/support/rom-downloads.html#unlocked]
Tip: currently im using LeeDroid ROM ported from HTC10 (LeeDroid_10). There is thread for it on the main page of this forum. This ROM is fantastic. It keeps the main cosmetics of the stock HTC rom, adding several improvements over the original M9 ROM (camera app mainly IMO). I may give it a try.
Regarding the automatic system updates (settings -> about -> ...), unfortunately it didnt work even after installing the RUU firmware (which supposedly should bring the device to the absolute stock condition)... it simply says that "there is no update available...".
Good luck!
Click to expand...
Click to collapse
Hi,
Same here regarding the no update available. Thanks for the tip, i'll take it into consideration. Firstly upgrade to stock nougat, finally, thx to you. I've been looking forever for solutions. I kept on getting signature error with ruu files from the htc site. I'm now on the latest marshmallow after reading your solution because it didn't even find that via settings. I will try to upgrade to nougat tomorrow and if that works i'll look into leedroid. I gotta say jailbroken ios is easier but Android is the best, much more freedom. Thanks again!
Spike_Fire said:
Hey, thanks for the tip. I managed to update successfully. Here is what i had to do:
1) Updated to the latest Marshmallow release using "0PJAIMG_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.31.zip" on SDCard and booting on download mode.
2) Updated to Nougat using "OTA_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.14.617.6_R-3.35.617.31_release_490897lkj8xif5v3eoiykd.zip" on SDCard and booting on recovery mode -> Apply update form SD Card.
3) Updated to latest Nougat using "RUU_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.30.617.2.exe"
Curiously, after step 1 and 2 i tried to check if there is a software update available on "settings -> about -> software update", but on both steps it says that there is no update available...
Thank you very much!
Click to expand...
Click to collapse
Is this method works on S-ON device ? Does SIMCARD is still unlock after update to Nougat ?
Courageux said:
Is this method works on S-ON device ? Does SIMCARD is still unlock after update to Nougat ?
Click to expand...
Click to collapse
Yeah works on s-on which is the standard mode. s-off means full root access. No sim issues here. I followed this guide and am now on the latest nougat for m9.
D35t5tr0k3 said:
Yeah works on s-on which is the standard mode. s-off means full root access. No sim issues here. I followed this guide and am now on the latest nougat for m9.
Click to expand...
Click to collapse
Well thank you. Im gonna try right now.
Courageux said:
Well thank you. Im gonna try right now.
Click to expand...
Click to collapse
tell me uf you got it to work, im going to do the same thing right now(S-ON stock). ill be back with my report later today
Edit: this method dont work for me, error 12 in download mode. *sigh* time to mess with s-off stuff, wish me luck
XsaucerX said:
tell me uf you got it to work, im going to do the same thing right now(S-ON stock). ill be back with my report later today
Edit: this method dont work for me, error 12 in download mode. *sigh* time to mess with s-off stuff, wish me luck
Click to expand...
Click to collapse
Yes i get Nougat right now with that method. Well good luck.
XsaucerX said:
tell me uf you got it to work, im going to do the same thing right now(S-ON stock). ill be back with my report later today
Edit: this method dont work for me, error 12 in download mode. *sigh* time to mess with s-off stuff, wish me luck
Click to expand...
Click to collapse
Did you manage to update to nougat on your m9?
D35th5tr0k3 said:
Did you manage to update to nougat on your m9?
Click to expand...
Click to collapse
I updated after rooting the device with the sunshine app(25$)
Related
Hi XDA,
I have a VZW HTC One m7 that is seriously outdated, as in, it is still on all original versions from when I bought the phone last year the day it was released on Verizon. That day I took the phone and unlocked it (before Verizon blocked the unlock from HTC Dev) and rooted it. I put CWM recovery on it (version 6.0.3.6). Much later I also got it S-Off.
Currently I have Android 4.2.2, Sense 5.0, firmware 1.10.605.8, and baseband 1.12.42.0731 (I assume this is the radio?).
Because I have been rooted all along I have not been able to take the OTA updates for the last year.
How do I go about getting updated to the current versions of everything? Need step by step please as I'm pretty much a noob beyond what I have already done.
Your help is greatly appreciated.
Thanks,
Steve
lostnsound said:
Hi XDA,
I have a VZW HTC One m7 that is seriously outdated, as in, it is still on all original versions from when I bought the phone last year the day it was released on Verizon. That day I took the phone and unlocked it (before Verizon blocked the unlock from HTC Dev) and rooted it. I put CWM recovery on it (version 6.0.3.6). Much later I also got it S-Off.
Currently I have Android 4.2.2, Sense 5.0, firmware 1.10.605.8, and baseband 1.12.42.0731 (I assume this is the radio?).
Because I have been rooted all along I have not been able to take the OTA updates for the last year.
How do I go about getting updated to the current versions of everything? Need step by step please as I'm pretty much a noob beyond what I have already done.
Your help is greatly appreciated.
Thanks,
Steve
Click to expand...
Click to collapse
this is the way i did it, just follow the method in this section! not my work, but it has helped me get to the latest update! http://forum.xda-developers.com/showthread.php?t=2485319
abrego47 said:
this is the way i did it, just follow the method in this section! not my work, but it has helped me get to the latest update! http://forum.xda-developers.com/showthread.php?t=2485319
Click to expand...
Click to collapse
Thanks for the response! This is exactly what I was looking for, however I am concerned that it says "Using CWM, may cause you to lose root!" I would like to keep CWM and not lose my root. Any suggestions?
lostnsound said:
Thanks for the response! This is exactly what I was looking for, however I am concerned that it says "Using CWM, may cause you to lose root!" I would like to keep CWM and not lose my root. Any suggestions?
Click to expand...
Click to collapse
You need to update firmware.
http://forum.xda-developers.com/showpost.php?p=46506621&postcount=2
From the thread above you most likely want this.
http://www.androidfilehost.com/?fid=23501681358539478
Instructions:
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip firmware.zip (rename file to firmware.zip)
It will say that the update did not finish, to flush again, so repeat the above step:
fastboot flash zip firmware.zip
andybones said:
You need to update firmware.
http://forum.xda-developers.com/showpost.php?p=46506621&postcount=2
From the thread above you most likely want this.
http://www.androidfilehost.com/?fid=23501681358539478
Instructions:
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip firmware.zip (rename file to firmware.zip)
It will say that the update did not finish, to flush again, so repeat the above step:
fastboot flash zip firmware.zip
Click to expand...
Click to collapse
Much thanks andybones!! This is very very helpful. Gonna give it a try tonight.
lostnsound said:
Much thanks andybones!! This is very very helpful. Gonna give it a try tonight.
Click to expand...
Click to collapse
Glad to help out whenever I can friend.
Let us know the results.
Best of luck,
Andy
Hey andybones,
So I just went through the steps you outlined (very very helpful btw, thanks again) but I have a question now. In the bootloader I can see that the OS version has now been updated to 4.10.605.3 and the radio to 1.13.41.0421. So it appears that it worked. However, when I boot into the UI and go to Settings>About>Software Information, I only see the radio version as being updated. The build version (I assume is the firmware version) still says 1.10.605.8. Is this to be expected? Did it actually work?
Thanks,
Steve
lostnsound said:
Hey andybones,
So I just went through the steps you outlined (very very helpful btw, thanks again) but I have a question now. In the bootloader I can see that the OS version has now been updated to 4.10.605.3 and the radio to 1.13.41.0421. So it appears that it worked. However, when I boot into the UI and go to Settings>About>Software Information, I only see the radio version as being updated. The build version (I assume is the firmware version) still says 1.10.605.8. Is this to be expected? Did it actually work?
Thanks,
Steve
Click to expand...
Click to collapse
If you are s-off you can now simply flash a stock rooted Rom. That will update your os for you. Your os is what's out of date now.
lostnsound said:
Hey andybones,
So I just went through the steps you outlined (very very helpful btw, thanks again) but I have a question now. In the bootloader I can see that the OS version has now been updated to 4.10.605.3 and the radio to 1.13.41.0421. So it appears that it worked. However, when I boot into the UI and go to Settings>About>Software Information, I only see the radio version as being updated. The build version (I assume is the firmware version) still says 1.10.605.8. Is this to be expected? Did it actually work?
Thanks,
Steve
Click to expand...
Click to collapse
The newest rom on this thread is the most recent stock rom for VZW m7. http://forum.xda-developers.com/showthread.php?t=2485319
Just flash it from recovery, like Andy said. You may want to wipe data going from an older sense version to a newer one though, just a warning. Not all apps will dirty flash over, and some can cause issues.
lostnsound said:
Hey andybones,
So I just went through the steps you outlined (very very helpful btw, thanks again) but I have a question now. In the bootloader I can see that the OS version has now been updated to 4.10.605.3 and the radio to 1.13.41.0421. So it appears that it worked. However, when I boot into the UI and go to Settings>About>Software Information, I only see the radio version as being updated. The build version (I assume is the firmware version) still says 1.10.605.8. Is this to be expected? Did it actually work?
Thanks,
Steve
Click to expand...
Click to collapse
Very welcome, Steve, glad you are up and running the latest firmware now!
As for the numbers you are right on the money, the baseband is controlled by the device so no matter the ROM, your baseband will always be the same as what is flashed. As for the ROM name this is dependent on the ROM, to be direct and specific, the build.prop found in /system folder.
So technically, that is why you see ROMs saying things like mine for ex: Bonestock ROM v4.3, etc..
then you will get the build number, you can always change this to w.e. you'd like and tell ppl they are running so and so and they are not, lol, just explaining, but anyway, yes the build number will change depending on the ROM you are using, since you are now on the 4.10.605.3 firmware, your best bet, is to either,
1) if you want Stock
use the stock base ROM for 4.10.605.3
link: http://forum.xda-developers.com/showthread.php?t=2485319
actually the same as the one used for the firmware
2) or others, here is link to my ROM.
http://forum.xda-developers.com/showthread.php?t=2479587
Thank you guys so much again for all the help. I have successfully upgraded everything now. Now running the current firmware, Philz Touch recovery version 6.48.4, and santod's 4.4.2, Sense 6.0 Stock ROM. Everything is working like a charm now! :laugh: You guys have been so helpful, couldn't have done it without you! I will save all this information for future use so I don't forget how I did it next time.
Thanks again,
Steve
Hello!
I recently bought a HTC One m8 used. Sadly i did not check up on the Software and it was pre-rooted and had some older version of Viper Rom on it (2.7 i think). It was also s-on and had that bug (i believe it was a TWRP one) so it would not show me the CID nor the current version it was on. So my thought was that id like to initially get to the point where i would recieve OTA Updates again so i could update the base system to install any ROM id like. After doing research for hours and trying various stuff it seemed i could not get back to stock without the CID. So what i initially did then was use Method 2 described in this thread to Upgrade the Firmware which is now 3.28.401.9. I then change the CID to the google OTA Update one and installed the Google Play Edition Rom. The ROM was kinda buggy and did not work properly tho (i assume its still an issue that the underlying Firmware is not up-to-date enough) so i went back, changed the CID to HTC__001 and installed the stock 3.28.401.9 Rom + Recovery hoping the OTA Updates would come. It has not yet happened and i am not sure it will.
So here is my question: Will OTA Updates come if my initial CID does not match the CID i currently have even if i set it with fastboot? Is there a way for me to figure out my initial CID at this point? All i really want are working OTA Updates, after that i can install any ROM anyway, but this seems to elude me.
Thanks you!
Best Regards
ly
lyeeth said:
Hello!
I recently bought a HTC One m8 used. Sadly i did not check up on the Software and it was pre-rooted and had some older version of Viper Rom on it (2.7 i think). It was also s-on and had that bug (i believe it was a TWRP one) so it would not show me the CID nor the current version it was on. So my thought was that id like to initially get to the point where i would recieve OTA Updates again so i could update the base system to install any ROM id like. After doing research for hours and trying various stuff it seemed i could not get back to stock without the CID. So what i initially did then was use Method 2 described in this thread to Upgrade the Firmware which is now 3.28.401.9. I then change the CID to the google OTA Update one and installed the Google Play Edition Rom. The ROM was kinda buggy and did not work properly tho (i assume its still an issue that the underlying Firmware is not up-to-date enough) so i went back, changed the CID to HTC__001 and installed the stock 3.28.401.9 Rom + Recovery hoping the OTA Updates would come. It has not yet happened and i am not sure it will.
So here is my question: Will OTA Updates come if my initial CID does not match the CID i currently have even if i set it with fastboot? Is there a way for me to figure out my initial CID at this point? All i really want are working OTA Updates, after that i can install any ROM anyway, but this seems to elude me.
Thanks you!
Best Regards
ly
Click to expand...
Click to collapse
as far as I know the stock 3.28.401.9 Rom + Recovery is the newest version. Your not getting updates because their are none
clsA said:
as far as I know the stock 3.28.401.9 Rom + Recovery is the newest version. Your not getting updates because their are none
Click to expand...
Click to collapse
That makes me happy to hear. I'll just wait and hope for an early Lollipop then. Thank you!
lyeeth said:
That makes me happy to hear. I'll just wait and hope for an early Lollipop then. Thank you!
Click to expand...
Click to collapse
I do see a 3.29.401.9 firmware but I think it was a small OTA fix
try pushing your date ahead and trying to find it
Hi,
I recently managed to root my HTC One M8s with TWRP recovery and everything works perfectly, except that I can't install the new OTA (1.16.401.1).
After searching I have flashed my recovery back to the stock for my version (which is 1.11.401.1) and tried applying the OTA again, but it still fails.
I downloaded the recovery from this website: ruu.lalleman.net/HTC_M8S%28QL_UL%29/Recovery/HTC%20Recovery/ (I can't post URLs yet).
Below is the error I receive when trying to update on stock recovery, TWRP recovery also gave the same error when I tried updating there.
(Code -1)
E:Find no match PARTITION: for package path @/cache/recover/block.map
Finding update package...
Opening update package...
Verifying update package...
Installing update...
L50QCT.01.105.019
Verifying current sytem...
Package expects build fingerprint of htc/m8qlul_htc_europe/htc_m8qlul:5.0.2/LRX22G/531284.2:user/release-keys or htc/m8qlul_htc_europe/htc_m8qlul:5.0.2/LRX22G/555949.10:user/release-keys;
This device has htc/m8qlul_htc_europe/htc_m8qlul:5.0.2/LRX22G/53128
E:Error in @/cache/recovery/block.map
(Status 7)
From what I can see my build fingerprint is incorrect, but I have no idea how to fix it...
Seems to me it's likely that you've altered some system files while rooted and the Ota doesn't like it.
Now, I don't own an M8s...i have an M8, but I'd say the easiest route would be to flash your stock ruu again. After that the OTA should work.
It's that or figure out what system changes have been made and correct it. Xposed can mess you up, Uninstalled system apps can stop the Ota... MODS that changed system files... Etc. The Ota us looking for a stock system, then it updates it.
Good luck!
Thanks for the answer, I will see if I can try this solution tomorrow. I just have 2 questions:
What does the RUU do exactly? Should I see it as a complete stock reset of my phone?
And can I simply flash it using fastboot or is there a special method for a RUU?
My previous phone had an automated root and I always updated with OTA afterwards so I never flashed before now.
Im on the same boat. Tried to sim unlock by rooting and playing with CID but didnt work, now ive a rooted m8s and no ota. Tried to ruu but kept getting an error something like not enough space although i had 10gb free, cleared cache rebooted. Cant even factory reset. If anyone know how to unroot it and bring it back to stock that would be fantastic. Kind of want to delete the "flag" too make it "LOCKED" and "OFFICIAL" incase for warranty. Any ideas?
You guys have flashed 1.16 before, haven't you...?
See here: http://forum.xda-developers.com/htc-one-m8/help/help-thread-htc-one-m8s-to-stock-howto-t3190238
Err, oops, posted too soon. You said you have flashed to 1.11. What is the full filename of the RUU you flashed?
voidzero said:
You guys have flashed 1.16 before, haven't you...?
See here: http://forum.xda-developers.com/htc-one-m8/help/help-thread-htc-one-m8s-to-stock-howto-t3190238
Err, oops, posted too soon. You said you have flashed to 1.11. What is the full filename of the RUU you flashed?
Click to expand...
Click to collapse
When I got my phone I updated with OTA to version 1.11, after that I flashed TWRP recovery and rooted my phone. Now that OTA 1.16 is out I tried to update but couldn't, so I tried to flash back to stock recovery but it still wouldn't work because of the error above. Now it would seem that I am doing this the wrong way, and you cannot use OTA on a rooted/unlocked/custom recovery M8s.
Manual OTA flash worked on my previous phone with root which was an ASUS Padfone Infinity A80 as ASUS would release them on their own website for you.
Apparently HTC does not do this, or I am not looking in the right place.
I have never flashed a RUU before, and I don't know how to lock my bootloader again. From what I understand, every time there is a new OTA I will have to lock my bootloader, flash original recovery, flash RUU and then update. That sounds like a lot of trouble every time a new OTA comes out.
Is there no way to manually flash the new OTA without losing root, custom recovery and locking the bootloader? Will I have to follow these steps every time? Also I use the built in back-up to Google as well as HTC back-up but I don't know if all my data is in those back-ups or if I will lose something.
Codyksp said:
(...) so I tried to flash back to stock recovery but it still wouldn't work because of the error above. Now it would seem that I am doing this the wrong way, and you cannot use OTA on a rooted/unlocked/custom recovery M8s.
(..)
I have never flashed a RUU before, and I don't know how to lock my bootloader again. From what I understand, every time there is a new OTA I will have to lock my bootloader, flash custom recovery, flash RUU and then update. That sounds like a lot of trouble every time a new OTA comes out.
(...)
Is there no way to manually flash the new OTA without losing root, custom recovery and locking the bootloader? Will I have to follow these steps every time? Also I use the built in back-up to Google as well as HTC back-up but I don't know if all my data is in those back-ups or if I will lose something.
Click to expand...
Click to collapse
If you restore a RUU, and afterwards don't flash your recovery and boot partitions, You will see "Software status: official" in fastboot.
Now here's the trick: if you just boot a custom recovery with "fastboot boot my_recovery.img" (TWRP for example) then it will boot TWRP, but you can make the modifications to your system partition without losing "Software status: official" in fastboot.
So: If you just boot your recovery with 'fastboot boot' and don't flash anything, you can make all the modifications you want and still be able to install OTAs later, I think. I've rooted my phone, even installed XPosed, done all kinds of funky things to it but Fastboot still shows me that I'm on official software.
How does that sound?
So since there is no decent guide at all about flashing RUU for a HTC One M8s (the s makes a difference!). I have assumed that I need to have the bootloader locked first, as I unlocked it. According to all the M8 guides I have to gain S-OFF before I can lock the bootloader again. So I followed a guide to wipe with TWRP and flash a ROM called InsertCoin so that I can S-OFF my phone.
Now after going through the ROM's setup my phone is stuck in a bootloop, constantly trying to boot up. There is NO way at all for me to get it to stop, it just keeps booting the entire time. Not a single combination of buttons is working. Good thing the battery is non removable. How am I supposed to fix this? I've tried every volume up/down/power combination possible. The phone just boots to the HTC - Power by Android screen, shuts off after about 5 seconds and then repeats the same thing over and over. I can't turn it off and I can't get to the bootloader either.
What I need is a guide that tells me all the steps required to get an HTC One M8s (NOT M8!) back to 100% stock. This means, stock ROM, stock recovery, locked bootloader and S-ON. I am getting extremely frustrated by the lack of information and the amount of redicilous things I need to do just so I can root my phone and have OTA as well.
All I want is root on my phone for 1 app that I use with my car radio and I want to be able to update to the newest OTA afterwards, is that really so much to ask?
I am fine with installing a custom ROM with root and easy updates too, as long as the damn phone will boot after installing it and it's actually made for the M8s.
Deleted......
Well I finally managed to get the damn thing to the bootloader, and I've used "fastboot oem lock" to relock my bootloader. It now shows ***Software status: Modified ***, *** RELOCKED *** and ***Security Warning ***.
I will now have to go to my parents where my laptop is to be able to copy the RUU to my SD card, from what I understand it has to be named 0PKVIMG.zip and then it should automatically install.
Now the phone says it can't find the image or the image is incorrect.... It searches for, 0PKVDIAG.zip, 0PKVDIAG.nbh, 0PKVIMG.zip or 0PKVIMG.img. and it seems to find 0PKVIMG.zip and loads it but it cannot find the .img file and does absolutely nothing. Am I supposed to have both?
So it turns out that the RUU zip from http://ruu.lalleman.net/HTC_M8S%28QL_UL%29/RUU/ is actually not correct and I had to use rom.zip which was inside the folder. The phone is now running the "update" as it calls it. Fingers crossed...
Yes, possible you need to use rom.zip inside the zip, depending on the version, but I think this applies to 1.16 which I advice against using for reasons previously specified.
---------- Post added at 07:47 PM ---------- Previous post was at 07:47 PM ----------
By the way, I did write an RUU restoration thread specifically for this subject. Did you not find it?
Apparently I also needed to use the rom.zip for the 1.11 version, in the meantime I have also updated with OTA to 1.16. Afterwards I also unlocked my bootloader, restored my settings and installed SuperSU by booting TWRP. Let's hope the next OTA still works...
I did read your thread but I got stuck at first on relocking the bootloader, as I couldn't find the exact instructions for a while. Afterwards I got stuck on flashing the RUU because I didn't know that I needed to use the rom.zip file to get it to work.
After all that I got quite frustrated and I just wished there was 1 thread with instructions for everything (unlocking, relocking, flashing, compatible ROMs, booting to keep OTA, etc.) which is why I was angry at the time and couldn't properly read everything or find solutions. In the end it all worked out so far though.
I would ask you to create a compilation thread though if you wanted to improve the available information. Either way, thanks for the information that you've already provided.
Codyksp said:
Apparently I also needed to use the rom.zip for the 1.11 version, in the meantime I have also updated with OTA to 1.16. Afterwards I also unlocked my bootloader, restored my settings and installed SuperSU by booting TWRP. Let's hope the next OTA still works...
I did read your thread but I got stuck at first on relocking the bootloader, as I couldn't find the exact instructions for a while. Afterwards I got stuck on flashing the RUU because I didn't know that I needed to use the rom.zip file to get it to work.
After all that I got quite frustrated and I just wished there was 1 thread with instructions for everything (unlocking, relocking, flashing, compatible ROMs, booting to keep OTA, etc.) which is why I was angry at the time and couldn't properly read everything or find solutions. In the end it all worked out so far though.
I would ask you to create a compilation thread though if you wanted to improve the available information. Either way, thanks for the information that you've already provided.
Click to expand...
Click to collapse
The next ota won't work because you rooted it. Root changes binaries which lead to a fail on ota.
You need a non rooted (read : never rooted before) stock rom.
Mr Hofs said:
The next ota won't work because you rooted it. Root changes binaries which lead to a fail on ota.
You need a non rooted (read : never rooted before) stock rom.
Click to expand...
Click to collapse
So in that case I just unroot it before updating then?
Codyksp said:
So in that case I just unroot it before updating then?
Click to expand...
Click to collapse
Read my post again...... "a never rooted rom" so that means you need a stock rom before its ever been rooted. NOT an unrooted one because it leaves traces which will cause the ota to fail !
People should learn to create a nandroid backup before flashing ANY mods/superuser.zip/roms etc......etc
Well developers shouldn't make this such a hassle... My previous phone was an ASUS Padfone Infinity (A80) and it didn't receive any OTAs after being rooted but ASUS simple lets you download the firmware updates on their website and then you can manually update it without any problems. If HTC provides a bootloader unlock, why can't they allow OTA or at least provide manual firmware updates?
I wouldn't mind using a custom ROM either but I have no idea which ROMs work for the HTC One M8s. Would any M8 ROM be compatible? The phones aren't identical, the "s" is there for a reason...
Codyksp said:
Well developers shouldn't make this such a hassle... My previous phone was an ASUS Padfone Infinity (A80) and it didn't receive any OTAs after being rooted but ASUS simple lets you download the firmware updates on their website and then you can manually update it without any problems. If HTC provides a bootloader unlock, why can't they allow OTA or at least provide manual firmware updates?
I wouldn't mind using a custom ROM either but I have no idea which ROMs work for the HTC One M8s. Would any M8 ROM be compatible? The phones aren't identical, the "s" is there for a reason...
Click to expand...
Click to collapse
I would say that M8 roms wouldn't be compatible, and could even mess up your device badly. Sorry!
Codyksp said:
Well developers shouldn't make this such a hassle... My previous phone was an ASUS Padfone Infinity (A80) and it didn't receive any OTAs after being rooted but ASUS simple lets you download the firmware updates on their website and then you can manually update it without any problems. If HTC provides a bootloader unlock, why can't they allow OTA or at least provide manual firmware updates?
I wouldn't mind using a custom ROM either but I have no idea which ROMs work for the HTC One M8s. Would any M8 ROM be compatible? The phones aren't identical, the "s" is there for a reason...
Click to expand...
Click to collapse
Your point of view is a bit off if you ask me. Developers (in this case HTC) do not have to support custom modding of your phone. They support the device in the state you buy it !
If you want to mod it that's YOUR call not theirs. Do some homework before modding it. Getting a phone back to stock for future updates is relatively easy but many people don't read first how to as they think it's not important.
HTC has no obligation at all towards you regarding custom software !
And indeed M8 roms do NOT work on your M8s !
I have a Dev edition M8 that i zip RUU'ed back to lollipop. i took a security update successfully, then the 3 preinstall updates in prep for marshmallow. however, I now get an error when taking the actual OTA for marshmallow. I am s-off and bootloader unlocked. I then downloaded the RUU from HTC to run the exe, but i always get error 155. I read @Sneakyghost post about firmware and it said it was either region ID's not matching, or the bootloader being unlocked. I don't see why the unlocked bootloader would be a problem when im s-off and its a dev edition, which is bootloader unlocked out of the box. Anyone know what is causing this?
fyarf said:
I have a Dev edition M8 that i zip RUU'ed back to lollipop. i took a security update successfully, then the 3 preinstall updates in prep for marshmallow. however, I now get an error when taking the actual OTA for marshmallow. I am s-off and bootloader unlocked. I then downloaded the RUU from HTC to run the exe, but i always get error 155. I read @Sneakyghost post about firmware and it said it was either region ID's not matching, or the bootloader being unlocked. I don't see why the unlocked bootloader would be a problem when im s-off and its a dev edition, which is bootloader unlocked out of the box. Anyone know what is causing this?
Click to expand...
Click to collapse
Haha nice man I just finished downloading that exact RUU and I have that exact phone in the exact same state. I got it from someone in the US.
I'll let you know how it goes on mine...
Sneakyghost said:
Haha nice man I just finished downloading that exact RUU and I have that exact phone in the exact same state. I got it from someone in the US.
I'll let you know how it goes on mine...
Click to expand...
Click to collapse
heres my recovery message, just to maybe help troubleshoot it. it mentions userdata being busy (i got an error in the zip ruu flash for userdata, had to flash the ruu zip twice to get an okay), then kidmode missing. not sure what to do besides flash the firmware from http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894
Modified system apps, sir. That's what it is. Did you root your system?
Edit:
Maybe not. Maybe just can't find those apps cuz it can't mount data.
Something wrong there.
No idea.
I'll see where I end up.
Sneakyghost said:
Modified system apps, sir. That's what it is. Did you root your system?
Edit:
Maybe not. Maybe just can't find those apps cuz it can't mount data.
Something wrong there.
No idea.
I'll see where I end up.
Click to expand...
Click to collapse
i did a factory reset from stock recovery, and kid mode is present now, maybe im onto something...
Edit: not rooted directly from a factory ruu zip (well, hopefully the zip creator did a factory dump and was unmodified) but kid mode wasnt an option before the factory reset
fyarf said:
i did a factory reset from stock recovery, and kid mode is present now, maybe im onto something...
Edit: not rooted directly from a factory ruu zip (well, hopefully the zip creator did a factory dump and was unmodified) but kid mode wasnt an option before the factory reset
Click to expand...
Click to collapse
Unfortunately, I'm with family tonight and won't be able to assist until much later. But note this: the factory reset could well help. I can explain later.
Sneakyghost said:
Unfortunately, I'm with family tonight and won't be able to assist until much later. But note this: the factory reset could well help. I can explain later.
Click to expand...
Click to collapse
ok so i got mine to work.. apparently the zip RUU isnt good. i ran the exe 4.16.1540.8 from here http://forum.xda-developers.com/showthread.php?t=2701376 and then updated ota from there without issue. so my guess is the RUU zip wasnt perfect system-wise,while the exe is straight from htc.
fyarf said:
ok so i got mine to work.. apparently the zip RUU isnt good. i ran the exe 4.16.1540.8 from here http://forum.xda-developers.com/showthread.php?t=2701376 and then updated ota from there without issue. so my guess is the RUU zip wasnt perfect system-wise,while the exe is straight from htc.
Click to expand...
Click to collapse
ok. Where you got that zip from? Cuz I downloaded the 6.xx RUU.exe straight from HTC USA...
Sneakyghost said:
ok. Where you got that zip from? Cuz I downloaded the 6.xx RUU.exe straight from HTC USA...
Click to expand...
Click to collapse
zip was from the same thread, i tried the exe instead because it was an HTC file instead of a contributor. now on MM sense. The 6.xx RUU refused to work no matter what i did, so i OTA'd to the latest version.
fyarf said:
zip was from the same thread, i tried the exe instead because it was an HTC file instead of a contributor. now on MM sense. The 6.xx RUU refused to work no matter what i did, so i OTA'd to the latest version.
Click to expand...
Click to collapse
I seem to be having an entirely different problem. After swapping cables, phones and laptop ports as well as updating drivers, it appears that the usb port of my M8 is broken. I'll have to see at someone else's computer, maybe tomorrow. Pretty frustrating right now as I'm liking the M8 better than my M9 and M7.
[EDIT]
I could stabilize the connection enough to run another, international RUU. The RUU worked fine while the 6.12.1540.4 kept getting stuck at either "checking header" or "sending" - both times with a successfully established connection. I already tweeted HTC asking to have that RUU checked. I assume your findings were correctly indicating a bad RUU, since a.) It also didn't work here and b.) people from my team have confirmed seeing several fail scenarios with that RUU spread over XDA.
Guess that's that then. Thanks for raising the issue. I would have messed around with it much longer otherwise since the error messages are not clearly pointing towards a broken RUU.
[EDIT]
More updates: searching the M8 forum for 6.12.1540.4 turned up this: http://forum.xda-developers.com/showthread.php?p=64320571
That'd mean the RUU fails at the hboot pre-update reboot. All that's needed apparently is to flash only the hboot manually first, so it can proceed. Hence also error 155 which usually indicates issues with the system image. You experienced that most likely because the older hboot couldn't extract the system.img from the rom.zip.
Usually, the procedure is:
RUU updates hboot
RUU reboots to boatloader
RUU updates rest of firmware
RUU sends over the system image in parts
Hboot now decrypts and flashes the part.zips
It just looks like mandatory hboot-first-flash didn't happen right, either not rebooting after it or not flashing it at all.
However, this seems to be fixable by running the hboot/firmware package first and then the complete RUU.
Sneakyghost said:
I seem to be having an entirely different problem. After swapping cables, phones and laptop ports as well as updating drivers, it appears that the usb port of my M8 is broken. I'll have to see at someone else's computer, maybe tomorrow. Pretty frustrating right now as I'm liking the M8 better than my M9 and M7.
[EDIT]
I could stabilize the connection enough to run another, international RUU. The RUU worked fine while the 6.12.1540.4 kept getting stuck at either "checking header" or "sending" - both times with a successfully established connection. I already tweeted HTC asking to have that RUU checked. I assume your findings were correctly indicating a bad RUU, since a.) It also didn't work here and b.) people from my team have confirmed seeing several fail scenarios with that RUU spread over XDA.
Guess that's that then. Thanks for raising the issue. I would have messed around with it much longer otherwise since the error messages are not clearly pointing towards a broken RUU.
[EDIT]
More updates: searching the M8 forum for 6.12.1540.4 turned up this: http://forum.xda-developers.com/showthread.php?p=64320571
That'd mean the RUU fails at the hboot pre-update reboot. All that's needed apparently is to flash only the hboot manually first, so it can proceed. Hence also error 155 which usually indicates issues with the system image. You experienced that most likely because the older hboot couldn't extract the system.img from the rom.zip.
Usually, the procedure is:
RUU updates hboot
RUU reboots to boatloader
RUU updates rest of firmware
RUU sends over the system image in parts
Hboot now decrypts and flashes the part.zips
It just looks like mandatory hboot-first-flash didn't happen right, either not rebooting after it or not flashing it at all.
However, this seems to be fixable by running the hboot/firmware package first and then the complete RUU.
Click to expand...
Click to collapse
I'm not sure about OP, but that worked perfectly for me. I wonder how HTC let a broken RUU.exe past testing?
Double_a2013 said:
I'm not sure about OP, but that worked perfectly for me. I wonder how HTC let a broken RUU.exe past testing?
Click to expand...
Click to collapse
They frequently do. Nothing exciting. That's why I notified HTC. They take their time with fixing them. The earlier the better.
Sneakyghost said:
They frequently do. Nothing exciting. That's why I notified HTC. They take their time with fixing them. The earlier the better.
Click to expand...
Click to collapse
Wow, I didn't realize that. Now if only they'd fix the ATT LTE issues on the dev rom :silly:
Double_a2013 said:
Wow, I didn't realize that. Now if only they'd fix the ATT LTE issues on the dev rom :silly:
Click to expand...
Click to collapse
My ota to the latest dev version got lte on at&t no problem, sure your apn settings are correct?
fyarf said:
My ota to the latest dev version got lte on at&t no problem, sure your apn settings are correct?
Click to expand...
Click to collapse
I've never had to reconfigure them before, regardless of if I'm using GPE or Sense RUUs. I'll give it another shot, and get back in a more timely manner
Edit: Apn settings seem fine. It's using the Nextgenphone one from ATT
Edit #2:
http://forum.xda-developers.com/att...ming-calls-lte-mode-m8-att-arhd-34-0-t3026710
Found this thread about a similar issue. I guess I'll disable HD Voice (Honestly, its borderline useless anyway) and see if that solves anything
Hi,
So a year ago a updated my HTC m8 which is an international unlocked model bought from the UAE to Lollipop from Kitkat. However, I never got notifications for an OTA update to marshmallow and until now, I still don't get them when I check for updates. So my question is simple, is it possible to somehow manually install the update without wiping anything? I think my bootloader is locked and I have S-ON if that's what it's called. Basically my phone is stock is every way and untampered. I just want to update it to marshmallow or find a way to force the OTA update to occur. I'm practically clueless as to how to go around it and I'm not familiar with the whole rooting process and key terms associated.
I attached screenshots of the build firmware etc. I'd really appreciate it if I could be provided with step by step instructions on how to update without wiping any data off my phone.
Thank you.
I've never personally done it, but if you can find the proper OTA file (6.12.401.4), you should be able to put it on the phone. Then boot to bootloader, and it should install automatically. I've seen other folks do it that way.
But really, you should always back up your personal data, and be prepared to have your data wiped. As even with an OTA file (which normally won't wipe data) you really never know, and should always be prepared for the worst case of having your data lost.
https://docs.google.com/spreadsheets/d/1aNd_nm4Em1wamRLFT7qHM2c3O9_sg_H3ztBrGq1u9Ws/pubhtml#Hey, thank you for replying! I found this link which has all the firmwares, the version you mentioned weighs in at around 80.9MB. Isn't that a bit too small? Also what are the steps I need to follow to start the process. I can back up with Sync Manager but I just need a confirmation that the procedure won't wipe the phone theoretically if it's done properly.
hemingway60 said:
https://docs.google.com/spreadsheets/d/1aNd_nm4Em1wamRLFT7qHM2c3O9_sg_H3ztBrGq1u9Ws/pubhtml#Hey, thank you for replying! I found this link which has all the firmwares, the version you mentioned weighs in at around 80.9MB. Isn't that a bit too small? Also what are the steps I need to follow to start the process. I can back up with Sync Manager but I just need a confirmation that the procedure won't wipe the phone theoretically if it's done properly.
Click to expand...
Click to collapse
Firmware is firmware. It is not the full ROM, and it is not the OTA.
Firmware isn't just a "bit small", the ROM/OTA is usually something like 1.5 GB. Firmware is just a small file that contains hboot, radio, kernel, recovery , and a few other "modules", but does not contain the ROM itself.
You need to be looking for a file that is specifically indicated as the OTA file (and may even have OTA in the file name). Anything else will not do what you want.
Manual install OTA only workable on S-Off device.
No choice, if to update ... backup all files in internal storage to somewhere else then either factory reset to get OTA or use RUU to update.
The OTA is posted here (direct HTC link): https://forum.xda-developers.com/showpost.php?p=64883695&postcount=6772
---------- Post added at 11:31 AM ---------- Previous post was at 11:22 AM ----------
ckpv5 said:
Manual install OTA only workable on S-Off device.
Click to expand...
Click to collapse
Hmm, was not aware of that. Thanks, as usual for the info!
Hey, thanks for the link redpoint73. Regarding ckpv5, is there a reason why it's not possible? OTAs download the file to the phone and then update it right? Isn't there a way for me to emulate the same? I would prefer getting the OTA the usual way but it just won't show up even after I cleared up space for it just now.
Also, what's the difference between 6.12.401.4 (european) vs 6.12.1540.4 (Unlocked/dev edition). HTC has an installer for the latter.
hemingway60 said:
Also, what's the difference between 6.12.401.4 (european) vs 6.12.1540.4 (Unlocked/dev edition). HTC has an installer for the latter.
Click to expand...
Click to collapse
You pretty much stated the difference:
6.12.401.4 is specifically for the Euro version M8.
6.12.1540.4 is for the (US) Developer's Edition. The "Unlocked" part is confusing - it does not mean it will work for all unlocked M8 versions. This RUU is only for the US Dev Edition.
The RUU/OTA/firmware needs to match your version M8. Otherwise it will fail with wrong version error, and not install.
The number "401" in the position x.xx.401.x is what you need to look at. "401" specifically means the Euro version. Note that your current version is 4.16.401.13 as noted on your bootloader screen shot. SO that means that 6.12.401.4 is what you need to upgrade to (what RUU to use).
The "1540' number in 6.12.1540.4 specifies it is for the US Developer's Edition.
There is an RUU for 6.12.401.4 . But it is in zip format (HTC didn't release a .exe format version). So you have to use the instructions as indicated. Note, this is an RUU and will wipe the phone:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
hemingway60 said:
is there a reason why it's not possible? OTAs download the file to the phone and then update it right?
Click to expand...
Click to collapse
It is downloaded to specific folder in data/data & unzipping is done before rebooting which you cannot stimulate the same on S-On as you can't place the OTA in correct location.
redpoint73 said:
There is an RUU for 6.12.401.4 . But it is in zip format (HTC didn't release a .exe format version). So you have to use the instructions as indicated. Note, this is an RUU and will wipe the phone:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Click to expand...
Click to collapse
So I literally just follow this procedure and everything should be fine?
Yeah .. it will update your device to Marshmallow.
Again .. please note it will wipe everything on your phone. So make backup anything that important to you like photos, music & etc