OK so I know I'm late to upgrading to marshmallow but i haven't gotten it to work on my htc one m9. may carrier is AT&T. Before the marshmallow update was released, I rooted and installed viper one on my m9 in hopes of recieving the update quicker. When Marshmallow was released, I was able to flash new marshmallow roms successfully, but my phone would never boot into the rom. It would always send me back to the bootloader. I realized that I would need a firmware update in order to run marhsmallow successfully, but I am having trouble updating the firmware. Since i rooted my phone and have a custom recovery and custom rom, I am no longer receiving OTA updates from htc. How will I be able to update the firmware manually. Also my phone is S-On, if that makes a difference.
Thanks for the help.
Why not upgrade using an RUU. AT & T is available from HTC's site.
Sent from my HTC One M9 using Tapatalk
shaqman89 said:
Why not upgrade using an RUU. AT & T is available from HTC's site.
Click to expand...
Click to collapse
I tried this but idiesnt work. Always says my device was disconnected mid installation.
Did you try to restart the ruu without disconnecting the cable?
Sent from my HTC One M9 using Tapatalk
castallion said:
I tried this but idiesnt work. Always says my device was disconnected mid installation.
Click to expand...
Click to collapse
Please read the readme thread that is pinned above the normal threads in this section. This way you'll learn how to find the correct RUU for your phone and how to flash it.
Flippy498 said:
Please read the readme thread that is pinned above the normal threads in this section. This way you'll learn how to find the correct RUU for your phone and how to flash it.
Click to expand...
Click to collapse
Ok so i found the correct RUU file. sku 502 firmware 2.11.502.18. thats what it says on my phone in download mode. once i flash this ruu I will have the stock htc rom and be able to recieve ota upgrades for marshmallow, correct?
Correct. Alternatively you could extract the RUU.zip from the latest 502 M9 RUU.exe which can be found on HTC's website and flash it with the instructions in the readme thread. A guide for the extraction is linked in the RUU section of the readme thread, as well. This was you wouldn't need to install the OTAs.
Sent from my HTC One S using XDA Labs
Flippy498 said:
Correct. Alternatively you could extract the RUU.zip from the latest 502 M9 RUU.exe which can be found on HTC's website and flash it with the instructions in the readme thread. A guide for the extraction is linked in the RUU section of the readme thread, as well. This was you wouldn't need to install the OTAs.
Click to expand...
Click to collapse
OK so I installed the ruu successfully but I haven't been prompted to upgrade to marshmallow yet. What should I do
castallion said:
OK so I installed the ruu successfully but I haven't been prompted to upgrade to marshmallow yet. What should I do
Click to expand...
Click to collapse
Which RUU? The 2.x one or the one from HTC's website? What is your current firmware version?
Flippy498 said:
Which RUU? The 2.x one or the one from HTC's website? What is your current firmware version?
Click to expand...
Click to collapse
The 2.x ruu from the forums
castallion said:
The 2.x ruu from the forums
Click to expand...
Click to collapse
Have you tried searching for the update via settings>about?
castallion said:
The 2.x ruu from the forums
Click to expand...
Click to collapse
Since my carrier is att, I believe all the updates come through that. I clicked the art update button and it says I'm up to date
That is more than odd. You should be able to receive and install the missing OTAs if you manually search for them.
Can you please download the latest 502 RUU from HTC's website, extract the *.zip file with the instructions that are linked in the readme thread and flash the *.zip as you did with the 2.x one?
Related
I need to know this before i brick the device or something.
The device is running the 1.54.401.10 software (4.4.2).. I believe this is the oldest there is. It also has a unlocked bootloader, S-OFF and a CID of 111111... How can i update this phone to the 4.4.4 version? I've tried with the inbuilt OTA update, by searching for updates from the about -> software updates menu, but this does not find any updates, so i must find another way to update it.
Can you guys help?
Thanks!
Da9L said:
I need to know this before i brick the device or something.
The device is running the 1.54.401.10 software (4.4.2).. I believe this is the oldest there is. It also has a unlocked bootloader, S-OFF and a CID of 111111... How can i update this phone to the 4.4.4 version? I've tried with the inbuilt OTA update, by searching for updates from the about -> software updates menu, but this does not find any updates, so i must find another way to update it.
Can you guys help?
Thanks!
Click to expand...
Click to collapse
Connect your phone to your PC, download this RUU, double click it after the download if finished, then follow the prompts.
xunholyx said:
Connect your phone to your PC, download this RUU, double click it after the download if finished, then follow the prompts.
Click to expand...
Click to collapse
Thanks that worked great !
xunholyx said:
Connect your phone to your PC, download this RUU, double click it after the download if finished, then follow the prompts.
Click to expand...
Click to collapse
I'd use this link instead:
https://docs.google.com/file/d/0B17smFr95pleeTQ5U1NzNkZzM0U/
It's the proper file name so more likely to be the original file
EddyOS said:
I'd use this link instead:
https://docs.google.com/file/d/0B17smFr95pleeTQ5U1NzNkZzM0U/
It's the proper file name so more likely to be the original file
Click to expand...
Click to collapse
It's actually the same file.
http://forum.xda-developers.com/showpost.php?p=58482793&postcount=716
xunholyx said:
It's actually the same file.
http://forum.xda-developers.com/showpost.php?p=58482793&postcount=716
Click to expand...
Click to collapse
The one you linked is a custom repack using the ZIP. The one I've linked to is the official HTC RUU exe file
Hello currently I am using a T-Mobile m9 with a custom Rom. I used to own an m7 before I ditched it for my nexus 5. Today I noticed a security patches released and realized I can't remember how to update when not stock. I was wondering does flashing new firmware still work the same as it did on the m7?
As far as I know, there are RUU files in 2 different formats: exe file which runs form your computer, or .zip files, which are saved on the SD card and then once you boot in download mode it will automatically ask if you want to apply the RUU file; I think you need to be S-OFF for this method though (as soon as I got back to S-ON, flashing the RUU zip outputs an error)
MrGriffdude said:
Hello currently I am using a T-Mobile m9 with a custom Rom. I used to own an m7 before I ditched it for my nexus 5. Today I noticed a security patches released and realized I can't remember how to update when not stock. I was wondering does flashing new firmware still work the same as it did on the m7?
Click to expand...
Click to collapse
I would look to the thread for the rom you are using, there will be the rom updates and info that will point you in the correct direction.
You need to be aware of the phone status (cid/locked/unlocked/S status) but the thread is the correct place to get all the info
Since you are using a custom Tom I'm assuming you've installed twrp and rooted?
If so, and you didn't follow the procedure to properly backup your system for OTAs then RUU is your way to go (assuming you're not soft).
Anyway head to twrp thread in original m9 development forum and see what are your options.
Sent from my HTC One M9 using Tapatalk
Jhonys said:
Since you are using a custom Tom I'm assuming you've installed twrp and rooted?
If so, and you didn't follow the procedure to properly backup your system for OTAs then RUU is your way to go (assuming you're not soft).
Anyway head to twrp thread in original m9 development forum and see what are your options.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
i am s-off but i do not have a stock back up
MrGriffdude said:
i am s-off but i do not have a stock back up
Click to expand...
Click to collapse
In that case just follow this thread
Hi,
Have just got a 2nd hand m9 that I'd like to update to Nougat. It is rooted but not s-off and on lollipop custom rom. Am I right in thinking that I need to install the latest ruu for lollipop, then the same for marshmallow and then lastly for nougat before I can install a nougat ROM?
Thanks
Yes. Updates are incremental. You need to have a stock phone before you can flash ruu's. You need s-off otherwise, which is well worth the money!.
Beamed in by telepathy.
pinn___________ said:
Hi,
Have just got a 2nd hand m9 that I'd like to update to Nougat. It is rooted but not s-off and on lollipop custom rom. Am I right in thinking that I need to install the latest ruu for lollipop, then the same for marshmallow and then lastly for nougat before I can install a nougat ROM?
Thanks
Click to expand...
Click to collapse
RUUs are not incremental. However, HTC changed the encryption key between firmware 3.x and 4.x. You therefore need to flash a 3.x ruu and to install the non-encrypted OTA afterwards. Be aware that you can't change your sku without S-OFF. That means if you don't own the developer edition (sku 617) you won't be able to update to android 7 since that version is the only one that received the update, yet.
shivadow said:
Yes. Updates are incremental. You need to have a stock phone before you can flash ruu's. You need s-off otherwise, which is well worth the money!.
Beamed in by telepathy.
Click to expand...
Click to collapse
That's not correct. A RUU doesn't care whether your phone is stock or that. It reflashes every partition of your phone as long as your download mode is working.
Sent from my HTC One S using XDA Labs
Flippy498 said:
RUUs are not incremental. However, HTC changed the encryption key between firmware 3.x and 4.x. You therefore need to flash a 3.x ruu and to install the non-encrypted OTA afterwards. Be aware that you can't change your sku without S-OFF. That means if you don't own the developer edition (sku 617) you won't be able to update to android 7 since that version is the only one that received the update, yet.
That's not correct. A RUU doesn't care whether your phone is stock or that. It reflashes every partition of your phone as long as your download mode is working.
Sent from my HTC One S using XDA Labs
Click to expand...
Click to collapse
So am I right in assuming that I can't flash any RUU without s-off? Also, how would I know if it's a dev edition or not? Thanks
pinn___________ said:
So am I right in assuming that I can't flash any RUU without s-off? Also, how would I know if it's a dev edition or not? Thanks
Click to expand...
Click to collapse
The dev edition is indicated by the sku (617) which is part of the firmware version: x.xx.SKU.xx
Please read the HTC One (M9) Readme Thread. All needed information should be located on its first page.
Flippy498 said:
The dev edition is indicated by the sku (617) which is part of the firmware version: x.xx.SKU.xx
Please read the HTC One (M9) Readme Thread. All needed information should be located on its first page.
Click to expand...
Click to collapse
Hi Flippy,
Thank for the links. As I mistakenly tried to flash a custom nougat rom on my lollipop device, I'm trying to get it back up and running. I still have access to TWRP and was looking at the back ups that you provided. However, I'm uncertain which to flash as I don't know which is the SKU of my mob. How can this be found out?
The readme thread should contain steps (in the RUU section and the twrp section II) for finding out the current firmware version of your phone. Did I forget to add them to the flashing instructions?
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
The readme thread should contain steps (in the RUU section and the twrp section II) for finding out the current firmware version of your phone. Did I forget to add them to the flashing instructions?
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
No,,that's there but I already know what f/w I'm on - 1.32.401.15. Tried flashing a custom ROM of that version but it's sticking at the HTC logo. I would have thought reflashing a ROM of the same version would have worked but did I bork something when flashing a N rom?
I'm uncertain how to find the SKU but guessing it's 61 (EE UK). Is that going to be my only way forward - ruu or twrp backup?
Thanks for the help!
pinn___________ said:
No,,that's there but I already know what f/w I'm on - 1.32.401.15. Tried flashing a custom ROM of that version but it's sticking at the HTC logo. I would have thought reflashing a ROM of the same version would have worked but did I bork something when flashing a N rom?
I'm uncertain how to find the SKU but guessing it's 61 (EE UK). Is that going to be my only way forward - ruu or twrp backup?
Thanks for the help!
Click to expand...
Click to collapse
Flippy498 said:
The dev edition is indicated by the sku (617) which is part of the firmware version: x.xx.SKU.xx
Please read the HTC One (M9) Readme Thread. All needed information should be located on its first page.
Click to expand...
Click to collapse
Re-read what I wrote before and pay attention to the part I highlighted in my quotes.
Btw, since many users make the same mistake I need to ask the following: You checked your firmware in download mode and not in settings>about, correct? The latter only shows you the base of the (custom) rom you're currently using and not your actual firmware.
You're firmware is quite old. I'd suggest you to flash the 3.35.401.12 RUU and to start from scratch. In general, you can't use roms that are based on a different firmware version than your current one. (Sidenote: I'm only talking about the major version number here - in this case the 3.)
There is no Nougat for SKU 401 at the moment but it should get released in the near future.
Flippy498 said:
Re-read what I wrote before and pay attention to the part I highlighted in my quotes.
Btw, since many users make the same mistake I need to ask the following: You checked your firmware in download mode and not in settings>about, correct? The latter only shows you the base of the (custom) rom you're currently using and not your actual firmware.
You're firmware is quite old. I'd suggest you to flash the 3.35.401.12 RUU and to start from scratch. In general, you can't use roms that are based on a different firmware version than your current one. (Sidenote: I'm only talking about the major version number here - in this case the 3.)
There is no Nougat for SKU 401 at the moment but it should get released in the near future.
Click to expand...
Click to collapse
Ahah, yep , I get it now!
Yes, checked as suggested in your very helpful thread. I'll follow your suggestion re. flashing also. Thanks for all your help.
Flippy498 said:
Re-read what I wrote before and pay attention to the part I highlighted in my quotes.
Btw, since many users make the same mistake I need to ask the following: You checked your firmware in download mode and not in settings>about, correct? The latter only shows you the base of the (custom) rom you're currently using and not your actual firmware.
You're firmware is quite old. I'd suggest you to flash the 3.35.401.12 RUU and to start from scratch. In general, you can't use roms that are based on a different firmware version than your current one. (Sidenote: I'm only talking about the major version number here - in this case the 3.)
There is no Nougat for SKU 401 at the moment but it should get released in the near future.
Click to expand...
Click to collapse
BTW, I had the issue you described here:-
Copy the file to the root directory of a SD card which is formatted to fat32. (If you're on firmware version 3.x you can use an exfat formatted SD card, too. It would be nice if a firmware 4.x user could confirm whether the exception apllies to the new version, as well.) Sometimes this is only possible if the SD card is directly connected to your PC and not put into your phone. I don't know why some M9s refuse the copy process.
If you delete the file extension , the phone will allopw the copy and then you can rename after.
pinn___________ said:
BTW, I had the issue you described here:-
Copy the file to the root directory of a SD card which is formatted to fat32. (If you're on firmware version 3.x you can use an exfat formatted SD card, too. It would be nice if a firmware 4.x user could confirm whether the exception apllies to the new version, as well.) Sometimes this is only possible if the SD card is directly connected to your PC and not put into your phone. I don't know why some M9s refuse the copy process.
If you delete the file extension , the phone will allopw the copy and then you can rename after.
Click to expand...
Click to collapse
Nice to know. Thanks. I'll add that info to the instructions.
I just got an M9 dev edition (OPJA110) off Amazon, and it is on Android 5.0.2
Running the OTA updates gives the Status 7 error which I found means the partition was modified by a previous owner.
I do not have a 32GB microSD, so is there any way to get it back to stock without one so I can go through the process of updating to Nougat? I looked for a link for an RUU I could run through my computer to reflash it, but couldn't find one.
Thanks for any and all help!
@Aj6627
http://www.htc.com/us/support/htc-one-m9/news/
The RUU for the Dev Edition should be available here. It's a 2GB file and includes the entire RUU for the M9.
murtaza02 said:
@Aj6627
The RUU for the Dev Edition should be available here. It's a 2GB file and includes the entire RUU for the M9.
Click to expand...
Click to collapse
I downloaded and tried that, but it won't work due to "signature error" which I read is caused by encryption keys changing between firmware versions.
Aj6627 said:
I downloaded and tried that, but it won't work due to "signature error" which I read is caused by encryption keys changing between firmware versions.
Click to expand...
Click to collapse
You have android 5.0.2 right? You can't jump directly to the latest os version, you need to get the ruu for 5.1 then 6 and then you should use the OTA update to get 7.0
Sent from my HTC One (M9) using XDA Labs
XsaucerX said:
You have android 5.0.2 right? You can't jump directly to the latest os version, you need to get the ruu for 5.1 then 6 and then you should use the OTA update to get 7.0
Sent from my HTC One (M9) using XDA Labs
Click to expand...
Click to collapse
I ended up finding the RUU for 6.0 and getting it to install, and now I've been OTA updating all last night and this morning to get up to date. Thank you.
I have 3 more to go I think.
So I've been trying the past couple weeks to root and flash my M9 (AT&T) to no avail. I have ADB, fastboot, sdk and the htc drivers installed on my computer. Thing is, moonshine keeps giving me an error after checking for updates, sunshine is unable to gain temproot, adb won't flash twrp because I have s-on, RUU updates keep failing and I can't get OTA updates to install. I'm on android 5.0.2 with firmware version 1.32.502.9 and did the HTC DEV process to unlock the bootloader. Any help will be much appreciated.
re-lock your bootloader with "fastboot oem lock" then you can run RUU and update it to latest firmware.
After that write a message and I'll help you with root, twrp, etc..
Thanks for the response. I'll get on it sometime this evening. All I'm concerned about is getting twrp installed so I can use it to flash a custom rom with su already installed and all the bloat are removed.
Donnie267 said:
Thanks for the response. I'll get on it sometime this evening. All I'm concerned about is getting twrp installed so I can use it to flash a custom rom with su already installed and all the bloat are removed.
Click to expand...
Click to collapse
Yeah, but first you need to update the firmware to latest(nougat) because with 5.0.2 firmware you can flash only lollipop and maybe some marshmallow roms and I don't think you want an old rom.
Also you don't need S-OFF for root, twrp, custom roms, so don't buy it if you really don't need it.
That's the thing. Every time I've tried flashing twrp, adb spat an error saying that it couldn't because I have S-on.
Donnie267 said:
That's the thing. Every time I've tried flashing twrp, adb spat an error saying that it couldn't because I have S-on.
Click to expand...
Click to collapse
Hmm that's weird, maybe you did something wrong.
You need to boot in download mode(download not bootloader) and do this command "fastboot flash recovery path/to/recovery.img" but first you need unlocked bootloader with htcdev.
Two important information:
A) The bootloader doesn't need to be locked or relocked for flashing a RUU on the M9. (Due to FRP I actually highly discourage everyone from relocking if you tinkered with this phone and don't know whether the RUU you want to flash is actually flashable on your phone. In other words, everytime you haven't already flashed the RUU successfully on your phone, before.)
B) You can't flash Nougat RUUs on a M9 with a non-Nougat firmware due to the different encryption keys.
Please take a look at the ReadMe thread if you need/are interested in more details.
Edit: And yes, that error always appears if you try to flash TWRP while the phone is booted to the bootloader.
Sent from my HTC One M9 using XDA Labs
1: I did some poking around on other threads here and found that I need to go to marshmallow to be able to go to nougat. Only ruu I've been able to find is the Verizon version and I need the one for AT&T if any of you have a link to one.
2: all I need is to get twrp on my phone and I'll he gravy. If any of you know how or where to find the process of flashing twrp WITHOUT rooting. That would be great.
Have you read the ReadMe thread? It contains a huge collection of RUUs and instructions for flashing TWRP. BTW, rooting is never needed for flashing TWRP. It's the other way round. You need TWRP for being able to flash SuperSU or Magisk.
Sent from my HTC One M9 using XDA Labs
Of course I have. Every last one of them says to use adb to flash twrp which 100% of the time says it failed because I have S-on as stated in my original post.
As mentioned before, that error occurs if you booted your phone to the bootloader instead of the download mode. Follow the instructions in the ReadMe thread and flash TWRP while your phone is booted to the download mode.
Sent from my HTC One M9 using XDA Labs
Finally got twrp installed and flashed the rooted developer edition running lollipop. Problem now is when I try a ton running marshmallow or nougat, my phone boots directly to bootloader. Any ideas why?
Android M roms require firmware 3.x and Android N can be used on at least firmware 3.x but are recommended to be used on firmware 4.x.
If you use older firmware versions the roms won't boot as @lucyr03 explained in one of the first replies in this thread.
Sent from my HTC One M9 using XDA Labs
Right. Now, would I be able to just jump right to the latest firmware, or do incremental updates and where can I get the necessary files?
The files are in the ReadMe thread.
You can jump to the latest 3.x firmware via a RUU. Due to the new encryption keys you can't use 4.x RUUs, though. You'll need to update from 3.x to 4.x via the software update function of the phone settings. Be aware that AT&T only let's you download updates for their branded phones if you own an AT&T sim card.
Sent from my HTC One M9 using XDA Labs
I'm using rooted developer edition Ron and every time I try updating, I get a message saying that my phone has been modified and can't update and the only ruu files on the HTC site are for nougat.
You can't update that custom rom you're using because its rom base doesn't match your phone's firmware. That's why you face that error message.
As written before, read the ReadMe thread.
Sent from my HTC One M9 using XDA Labs
I'm using rooted developer edition Ron and every time I try updating, I get a message saying that my phone has been modified and can't update and the only ruu files on the HTC site are for nougat.
Can you comment the link to the Readme?