Related
Hello,
I am looking for the stock ROM for my HTC ONE M8 because I had a few issues before and I put the first ROM that worked. Because my phone is S-On still it was difficult to find a ROM.
I am currently on a 4.4.4 ROM which has no check for updates feature so when Android L is pushed onto my device I won't be able to get it.
My HTC One M8 is a European version and is currently unlocked to all networks. I've tried to install the official HTC ROM from the website but it hangs and nothing updates, on my task manager I can see the CPU is busy but it does nothing.
Android Version : 4.4.4
HTC Sense version : 6.0
Software number : Android Revolution HD 22.1 by mike1986
Baseband bersion 1.22.2133147A1
Build number : 3.28.401.9
have you read this page: http://forum.xda-developers.com/showthread.php?t=2701376 ?
nathankk said:
I am looking for the stock ROM for my HTC ONE M8 because I had a few issues before and I put the first ROM that worked. Because my phone is S-On still it was difficult to find a ROM.
Click to expand...
Click to collapse
Why? You can flash any M8 ROMs with s-on. And since it appears your firmware is up to date, you can flash any of the latest ROMs with any firmware mismatch issues.
nathankk said:
I am currently on a 4.4.4 ROM which has no check for updates feature so when Android L is pushed onto my device I won't be able to get it.
Click to expand...
Click to collapse
Custom ROMs won't get official OTAs.
Also, in addition to returning to stock ROM, you need to revert to stock recovery to install any OTAs. Its all described in the thread linked in the previous response.
redpoint73 said:
Why? You can flash any M8 ROMs with s-on. And since it appears your firmware is up to date, you can flash any of the latest ROMs with any firmware mismatch issues.
Custom ROMs won't get official OTAs.
Also, in addition to returning to stock ROM, you need to revert to stock recovery to install any OTAs. Its all described in the thread linked in the previous response.
Click to expand...
Click to collapse
I was under the impression with,S-On you can't flash any ROM onto it. Can I literally choose any of those CIDs and it will be compatible with my phone? Instead of messing around can I just wait for the release of lollipop and then flash the ROM that gets posted on here. I just got a little confused because on that post it has carrier names and my phone is unlocked to all networks.
nathankk said:
I was under the impression with,S-On you can't flash any ROM onto it. Can I literally choose any of those CIDs and it will be compatible with my phone? Instead of messing around can I just wait for the release of lollipop and then flash the ROM that gets posted on here. I just got a little confused because on that post it has carrier names and my phone is unlocked to all networks.
Click to expand...
Click to collapse
I think you are talking about flashing firmware or a RUU ? No... If you're s-on, you can only flash your CID. But that has nothing to do with custom roms... Which is what the others have been talking about. ?
Darth said:
I think you are talking about flashing firmware or a RUU ? No... If you're s-on, you can only flash your CID. But that has nothing to do with custom roms... Which is what the others have been talking about.
Click to expand...
Click to collapse
I'm on a custom ROM now I believe and I'm wanting to return to stock, I want to be sure before I do anything so I don't brick the phone. How do I find which CID I need to download?
nathankk said:
I was under the impression with,S-On you can't flash any ROM onto it. Can I literally choose any of those CIDs and it will be compatible with my phone?
Click to expand...
Click to collapse
Any of the stock nandroids should work (meaning they will function). But if you want the stock ROM for your CID, than obviously you need to determine the CID and restore the corresponding stock nandroid.
One reason to restore to your stock nandroid, is that if you also restore the corresponding stock recovery you will be able to receive official OTAs.
nathankk said:
Instead of messing around can I just wait for the release of lollipop and then flash the ROM that gets posted on here.
Click to expand...
Click to collapse
Yes and no. You can flash any custom ROM, including upcoming LP Sense ROMs. But what complicates the issue is that HTC has updated the firmware (hboot, radio, WiFI, etc.) for every major OS software update. If you don't update the firmware accordingly, flashing a ROM that depends on that firmware will result in some major issues (such as long boot times and broken WiFi).
Updating firmware manually requires s-off (which may be the reason why you are under the impression that ROMs can't be flashed with s-on). Or alternately, you can return to stock ROM and recovery and OTA when the LolliSense update rolls out; and this will also update the firmware.
Keep in mind, as previously mentioned your current firmware will work with any current custom ROMs that depend on 3.x firmware.
nathankk said:
I just got a little confused because on that post it has carrier names and my phone is unlocked to all networks.
Click to expand...
Click to collapse
Regardless of the fact your phone is not carrier branded, it still has a CID, probably HTC__ something or other.
fastboot getvar all will yield your CID. No need to post your getvar data, just look for where it says CID. If you post getvar data, be sure to delete IMEI and serial number, as these are personal data that should not be posted on the internet.
redpoint73 said:
Any of the stock nandroids should work (meaning they will function). But if you want the stock ROM for your CID, than obviously you need to determine the CID and restore the corresponding stock nandroid.
One reason to restore to your stock nandroid, is that if you also restore the corresponding stock recovery you will be able to receive official OTAs.
Yes and no. You can flash any custom ROM, including upcoming LP Sense ROMs. But what complicates the issue is that HTC has updated the firmware (hboot, radio, WiFI, etc.) for every major OS software update. If you don't update the firmware accordingly, flashing a ROM that depends on that firmware will result in some major issues (such as long boot times and broken WiFi).
Updating firmware manually requires s-off (which may be the reason why you are under the impression that ROMs can't be flashed with s-on). Or alternately, you can return to stock ROM and recovery and OTA when the LolliSense update rolls out; and this will also update the firmware.
Keep in mind, as previously mentioned your current firmware will work with any current custom ROMs that depend on 3.x firmware.
Regardless of the fact your phone is not carrier branded, it still has a CID, probably HTC__ something or other.
fastboot getvar all will yield your CID. No need to post your getvar data, just look for where it says CID. If you post getvar data, be sure to delete IMEI and serial number, as these are personal data that should not be posted on the internet.
Click to expand...
Click to collapse
Fantastic reply! let me buy you a beer.
nathankk said:
Fantastic reply! let me buy you a beer.
Click to expand...
Click to collapse
Heh, while I love beer, gratitude by clicking the "Thanks" button is enough!
OP, check the link in my signature. Full guide to go back to stock with the EU M8 (most of it will work with S-ON as well)
redpoint73 said:
Yes and no. You can flash any custom ROM, including upcoming LP Sense ROMs. But what complicates the issue is that HTC has updated the firmware (hboot, radio, WiFI, etc.) for every major OS software update. If you don't update the firmware accordingly, flashing a ROM that depends on that firmware will result in some major issues (such as long boot times and broken WiFi).
Updating firmware manually requires s-off (which may be the reason why you are under the impression that ROMs can't be flashed with s-on). Or alternately, you can return to stock ROM and recovery and OTA when the LolliSense update rolls out; and this will also update the firmware.
Keep in mind, as previously mentioned your current firmware will work with any current custom ROMs that depend on 3.x firmware.
Click to expand...
Click to collapse
Heads up, as of early this week (Monday?) the Dev Edition M8 is rolling out Lollipop Sense via OTA. Some custom ROMs have now updated to this base, which is 4.16 software, and requires 4.16 firmware.
But as mentioned, any 3.x software based ROM will work on your current firmware.
Before I begin, I have already read through a lot of the guides but almost of all them are not updated enough for my case. If I am wrong please direct me to it.
I would like to restore AT&T stock rom on my phone which was previously converted to GPE Lollipop 5.1 (with root, bootloader unlocked and s-off).
Here's what I have already done.
Restored MID and CID to 0P6B12000 and CWS__001 (for AT&T) respectively.
Relocked the bootloader.
Restoring from a nandroid (before going GPE) fails.
Downloaded the most latest RUU file for AT&T model, and ran the process.
But RUU fails with error 155. And after reading online, any of the following could be cause of the problem.
Partition size difference in GPE and AT&T stock rom.
Difference in firmware version or may be HBOOT version.
GPE is lollipop 5.1 and I think AT&T's latest rom is 5.0.1. So may be this downgrade is causing the problem
The RUU file I was using: RUU_M8[email protected]50319A_40.45.C33065.00_F_release_426617_signed_2.exe
I think my first step would be to flash some correct firmware to be able to successfully run RUU, but I don't know how which one. Plus, will downgrading firmware cause problems?
I would appreciate any help in resolving this problem. At minimum, I would like to be able to flash some stock rom with all the sense and AT&T stuff.
My responses below in red font:
lief.erl said:
I would like to restore AT&T stock rom on my phone which was previously converted to GPE Lollipop 5.1 (with root, bootloader unlocked and s-off).
Here's what I have already done.
Restored MID and CID to 0P6B12000 and CWS__001 (for AT&T) respectively. correct
Relocked the bootloader. Not required, since you are s-off. Just making more work for yourself needlessly.
Restoring from a nandroid (before going GPE) fails. No way this would ever work. nandroid is just a backup of ROM and user data. Since the partition sizes are different, the Sense ROM won't fit on the system partition, and failure is a certainty. You need to re-partition via firmware/RUU.
Downloaded the most latest RUU file for AT&T model, and ran the process.
But RUU fails with error 155. And after reading online, any of the following could be cause of the problem.
Partition size difference in GPE and AT&T stock rom. This is most likely the cause.
Difference in firmware version or may be HBOOT version. Only a "downgrade of hboot is prohibited (trying to flash the same or higher number hboot is ok), and that is with s-on. Downgrade is even allowed with s-off.
GPE is lollipop 5.1 and I think AT&T's latest rom is 5.0.1. So may be this downgrade is causing the problem This also would not matter with s-off. Downgrades are ok
The RUU file I was using: RUU_M8[email protected]50319A_40.45.C33065.00_F_release_426617_signed_2.exe
I think my first step would be to flash some correct firmware to be able to successfully run RUU, but I don't know how which one. Plus, will downgrading firmware cause problems?
Click to expand...
Click to collapse
Find the 4.28.502.1 firmware zip and flash it in fastboot first. Then flash the RUU.
Some folks have been able to just RUU to get back to the Sense partition scheme. But many folks have to flash the firmware first, then RUU. Not sure why folks have different experiences.
redpoint73 said:
My responses below in red font:
Find the 4.28.502.1 firmware zip and flash it in fastboot first. Then flash the RUU.
Some folks have been able to just RUU to get back to the Sense partition scheme. But many folks have to flash the firmware first, then RUU. Not sure why folks have different experiences.
Click to expand...
Click to collapse
Thanks a lot.
Before I proceed, I have following questions.
How do I make sure that a RUU and the suggested firmware are compatible. Should I be looking at some thing in particular.
I was also curious about how do we decide which firmware to flash?
One again, thanks.
lief.erl said:
Before I proceed, I have following questions.
How do I make sure that a RUU and the suggested firmware are compatible. Should I be looking at some thing in particular.
I was also curious about how do we decide which firmware to flash?
Click to expand...
Click to collapse
You want the firmware that matches the RUU, they will have the same number (4.28.502.1).
The firmware was posted here: http://forum.xda-developers.com/att-htc-one-m8/general/lollipop-ota-twrp-backup-firmware-t3075835
redpoint73 said:
You want the firmware that matches the RUU, they will have the same number (4.28.502.1).
The firmware was posted here: http://forum.xda-developers.com/att-htc-one-m8/general/lollipop-ota-twrp-backup-firmware-t3075835
Click to expand...
Click to collapse
Looks like there are three[4.28.502.1] different firmware files.
4.28.502.1 OTA.ZIP
4.28.502.1 TWRP backup
4.28.502.1 Firmware
None of them say they are mirrors (ones which are have "mirror by" as prefix), so I am assuming some difference. Which one should I go with.
BTW, is it possible to go back to earlier android os, for example kit kat. I am asking this because going back might mean downgrading firmware.
lief.erl said:
Looks like there are three[4.28.502.1] different firmware files.
4.28.502.1 OTA.ZIP
4.28.502.1 TWRP backup
4.28.502.1 Firmware
None of them say they are mirrors (ones which are have "mirror by" as prefix), so I am assuming some difference. Which one should I go with.
Click to expand...
Click to collapse
Those aren't all firmware. Just the one that says "firmware" is firmware.
OTA.zip is the actual official OTA form AT&T, which would only work if you were on the Sense version directly preceding this update (so this is to go from stock Sense 3.42 > 4.28), and also stock recovery.
TWRP backup is just a backup of the ROM, and doesn't include firmware. Obviously, restore with TWRP as you would your own TWRP backup.
lief.erl said:
BTW, is it possible to go back to earlier android os, for example kit kat. I am asking this because going back might mean downgrading firmware.
Click to expand...
Click to collapse
Sure, you would just need the RUU for the desired version, and the matching firmware.
Downgrading firmware is only prohibited with s-on (version check prevents it).
You can find the RUUs here: http://forum.xda-developers.com/showthread.php?t=2751432
Some of the unmodified firmwares can be found at the bottom of the 1st post of the following thread: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
redpoint73 said:
Those aren't all firmware. Just the one that says "firmware" is firmware.
OTA.zip is the actual official OTA form AT&T, which would only work if you were on the Sense version directly preceding this update (so this is to go from stock Sense 3.42 > 4.28), and also stock recovery.
TWRP backup is just a backup of the ROM, and doesn't include firmware. Obviously, restore with TWRP as you would your own TWRP backup.
Sure, you would just need the RUU for the desired version, and the matching firmware.
Downgrading firmware is only prohibited with s-on (version check prevents it).
You can find the RUUs here: http://forum.xda-developers.com/showthread.php?t=2751432
Some of the unmodified firmwares can be found at the bottom of the 1st post of the following thread: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
Click to expand...
Click to collapse
Do you know which version of android os will ruu 1.58.502.1 install?
Some guides say to rename the firmware file to SOMETHINGfirmware.zip, while others say to rename to 0P6BIMG.zip. Does it depend on how I am flashing. For the first one I will flash using fastboot, and for the other one I will flash by putting the file on the sd card.
lief.erl said:
Do you know which version of android os will ruu 1.58.502.1 install?
Click to expand...
Click to collapse
Android 4.4.2
Software 1.x = Android 4.4.2
2.x = 4.4.3
3.x = 4.4.4
4.x = 5.0
lief.erl said:
Some guides say to rename the firmware file to SOMETHINGfirmware.zip, while others say to rename to 0P6BIMG.zip. Does it depend on how I am flashing. For the first one I will flash using fastboot, and for the other one I will flash by putting the file on the sd card.
Click to expand...
Click to collapse
Yes, it depends on how you flash (fastboot vs. putting file on the phone).
redpoint73 said:
Android 4.4.2
Software 1.x = Android 4.4.2
2.x = 4.4.3
3.x = 4.4.4
4.x = 5.0
Yes, it depends on how you flash (fastboot vs. putting file on the phone).
Click to expand...
Click to collapse
I am sorry to bother you again, but I can't seem to find RUU and a firmware for android 4.4.2 for AT&T.
The closest thing I have found is http://forum.xda-developers.com/att-htc-one-m8/general/att-1-58-501-1-bootable-ruu-hboot-t2818556
which is a bootable zip.
I am trying to avoid using any method other than official RUU.
lief.erl said:
I am sorry to bother you again, but I can't seem to find RUU and a firmware for android 4.4.2 for AT&T.
The closest thing I have found is http://forum.xda-developers.com/att-htc-one-m8/general/att-1-58-501-1-bootable-ruu-hboot-t2818556
which is a bootable zip.
I am trying to avoid using any method other than official RUU.
Click to expand...
Click to collapse
Link to the 1.58 RUU is in my Index thread, which I indicated in Post #6 above (1st link).
On my Index thread, under RUUs, its the 1st link under "Official" RUUs.
I'll see if I can find the firmware zip for that RUU.
EDIT: Here you go: http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC%2FHTC_One_M8%2F502%2F
Linked from here (so you know its a reliable XDA source): http://forum.xda-developers.com/showthread.php?t=2696282
redpoint73 said:
Link to the 1.58 RUU is in my Index thread, which I indicated in Post #6 above (1st link).
On my Index thread, under RUUs, its the 1st link under "Official" RUUs.
I'll see if I can find the firmware zip for that RUU.
EDIT: Here you go: http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC%2FHTC_One_M8%2F502%2F
Linked from here (so you know its a reliable XDA source): http://forum.xda-developers.com/showthread.php?t=2696282
Click to expand...
Click to collapse
One last question (I think), how do I determine what should be the name of the firmware zip, if I am going to be flashing from PC.
lief.erl said:
One last question (I think), how do I determine what should be the name of the firmware zip, if I am going to be flashing from PC.
Click to expand...
Click to collapse
I actually do not think it matter, as long as its a zip.
Some instructions will say firmware.zip. Others will call it something else, such as the specific file name including software number. And in fact, this guide says: fastboot flash zip 2.22.1540.3_firmware.zip or whatever the latest builds firmware zip is called.
If you look at the syntax of the command, its simply flashing a zip and not even specific to firmware: "fastboot flash zip blahblahblah.zip" and its what is inside the zip that determines what is being flashed to what partition on the phone.
Just make sure if you rename the file, that you don't have the Windows option enabled to hide file extensions. Otherwise you may name the file firmware.zip.zip and not realize it. This is a common error, since hiding the file extensions is typically enabled by default in Windows.
redpoint73 said:
I actually do not think it matter, as long as its a zip.
Some instructions will say firmware.zip. Others will call it something else, such as the specific file name including software number. And in fact, this guide says: fastboot flash zip 2.22.1540.3_firmware.zip or whatever the latest builds firmware zip is called.
If you look at the syntax of the command, its simply flashing a zip and not even specific to firmware: "fastboot flash zip blahblahblah.zip" and its what is inside the zip that determines what is being flashed to what partition on the phone.
Just make sure if you rename the file, that you don't have the Windows option enabled to hide file extensions. Otherwise you may name the file firmware.zip.zip and not realize it. This is a common error, since hiding the file extensions is typically enabled by default in Windows.
Click to expand...
Click to collapse
Thanks for all the help, but this method didn't work for me. After I was successful in flashing older firmware, M8 refused to the go in the the actual android os which is required for RUU (.exe) to work its magic (needs adb). May be because older firmware and latest OS (GPE 5.1) weren't compatible with each other. So I ended up using a bootable RUU with excellent result. Though the deed is done and I have returned the phone (Color banding was too much bear), I am curious whether it would have worked if adb was enabled inside TWRP.
lief.erl said:
Thanks for all the help, but this method didn't work for me. After I was successful in flashing older firmware, M8 refused to the go in the the actual android os which is required for RUU (.exe) to work its magic (needs adb). May be because older firmware and latest OS (GPE 5.1) weren't compatible with each other. So I ended up using a bootable RUU with excellent result. Though the deed is done and I have returned the phone (Color banding was too much bear), I am curious whether it would have worked if adb was enabled inside TWRP.
Click to expand...
Click to collapse
You can RUU with the phone in fastboot mode as well as booted into the OS. The only difference with booted into OS, is that the RUU will reboot into fastboot anyway. RUU will not work in TWRP (with adb enabled).
And yes, running "newer" version of OS with older firmware will result in issues. Extreme long boot times (and broken WiFi) are the most common issues. So its possible the phone would have booted eventually (just taking a really long time, and not completely "stuck").
Dears,
I am currently using Viper Rom 3.5 the lastest version but suffering from bad battery life,
I want to return to Stock my CID is HTC__J15
my current base version is 1.95.401.4
any help.
thanks
Easiest way is to ruu
I also returned to stock from Viper, not because of battery issue, but felt tired on cat-and-mouse game for hiding modified bootloader and root when using Android Pay...
You need to do is to search Internet and find the exact OS version RUU (1.95.401.4). If only have earlier version (e.g. 1.50.401.4) then you need to S-Off first, then you can flash earlier version for your variant. (I also purchased Sunshine to s-off before flashing earlier version of RUU).
my CID is HTC__J15 ,
1.95.401.4
i tried the ruu zip but show me an error message (didnt even flash )
any idea. thanks guys
How are you flashing it? SD card in download mode? Or using ruu.exe? If from SD card did you make sure to rename the package to 2ps6img.zip?
Tarima said:
How are you flashing it? SD card in download mode? Or using ruu.exe? If from SD card did you make sure to rename the package to 2ps6img.zip?
Click to expand...
Click to collapse
yes mate i did that , didnt work
moe111 said:
yes mate i did that , didnt work
Click to expand...
Click to collapse
Let check carefully what version of your ruu is? From Internet I can only find this one (1.21.401.4):
2PS6IMG_PERFUME_UHL_M60_SENSE80GP_HTC_Europe_1.21.401.4_R_Radio_1.0.U01001360331.4_41.13_F_release_477256_signed_2_4.zip
https://www.androidfilehost.com/?fid=24591023225177702
If you are still S-ON, you can't flash earlier version of RUU, the only way is to either find the exact version of RUU (1.95.401.4) or S-OFF first. You can purchase Sunshine to S-OFF, then are able to flash back to stock ROM with version 1.21.401.4. Once back, you can through OTA to update to latest 1.95.401.4.
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.
Hi,
I have an HTC M9 with firmware version 1.32.15 , unlocked bootloader, S-OFF.
Can I go straight to 3.xx or 4.xx ? (Or only to 3.xx because 3->4 is only possible via OTA?)
Or is this risky? I tried to read all the ReadMes, but still not sure about this
And I want to flash LineageOS 14 after upgrading the firmware - do I have to do it at the same time?
The answer depends on the method with which you want to update your firmware. RUUs contain the full firmware that belongs to their corresponding version so that you can skip older ones. OTAs and the official firmware packs that get extracted from them on the other hand are incremental so that it's not safe to skip one of them. And with S-OFF (like in your case) you can directly use one of the custom made full firmware packs (which unlike a RUU don't contain a rom/system) for firmware 4.x since they're not encrypted.
The new encryption keys prevent you from flashing a 4.x RUU on a 3.x (or lower) firmware and vice versa. Flashing a non-encrypted file (OTAs or custom made firmware packs) isn't a problem, though.
Unless you use a custom firmware pack (the pack is custom made not the firmware - that one is official) you can flash Lineage whenever you want. However, if you use a custom firmware pack then you need to directly flash a rom via TWRP or the phone won't boot since (as mentioned above) those packs don't contain a system/rom.
Nevertheless, you should never flash GSM files on a CDMA device or vice versa. The partition layouts differ between those two technologies and you'll damage your phone (if you're unlucky unrecoverably) by doing so.
Hi Flippy,
thanks for your answer.
I forgot to specify, my phone is GSM (SKU 771).
If I understand right from Sneakyghosts' firmware flashing guide, RUUs are not an option because they only get released for US models.
And the OTA approach seems very painful as I'm coming from 1.xx and want to go all the way to 4.xx .
So I guess I would go with one of the custom full firmware packs linked in Sneakyghost's post.
Some more questions so I can understand the risks better:
Flippy498 said:
However, if you use a custom firmware pack then you need to directly flash a rom via TWRP or the phone won't boot since (as mentioned above) those packs don't contain a system/rom.
Click to expand...
Click to collapse
Does that mean the phone would be bricked? Or still be able to boot into the bootloader, recovery and/or download mode?
Could I also go with a NoWipe ZIP instead of a FullWipe ZIP and then flash Lineage?
Did you take a look at the ReadMe thread? If I'm not mistaken then you'll find some 771 RUUs there. I don't think that Sneakyghost provides 771 packs so that you would need to change your CID and flash a pack for a different SKU if you choose this method.
Yes, that would mean that the device is soft bricked. But a soft brick is recoverable since bootloader, download mode, etc are still accessible. You just aren't able to boot the system since there is none. Only hard bricks are bricks that you need to worry about.
Of course you can use a NoWipe pack but there's no benefit in doing so. You'll loose all data anyway since you need make a full wipe in twrp before you flash lineage since the stock rom you're currently using is sense-based and lineage isn't. The exact difference between the two types of firmware packs (full wipe vs. no wipe) is explained somewhere in Sneakyghost's thread.
Sent from my HTC One M9 using XDA Labs
Thank you for clarifying. Yes there is one 771 RUU in the ReadMe Thread, but it's a 3.xx .
So changing the CID to get a newer firmware version seems worth it
Of course you can change your SKU if you want to.
However, you don't need to change it for getting android 7. Since OTAs are independent from RUUs the fact that there is no 4.x RUU for 771 doesn't mean that there is no OTA, yet. And even if there was a 4.x RUU you wouldn't be able to flash it due to the new encryption keys. You would still need to flash the 3.x RUU and then to install the 4.x OTA.
Sent from my HTC One M9 using XDA Labs
right, got confused with RUU vs. custom firmware packs (where it would be possible to go straight to 4).
I will report what I end up doing and maybe ask for more advice... thank you!
I flashed a NoWipe package (4.14.401.7 from Sneakyghost download section), then Lineage 14.1 and OpenGapps 7.1
Everything looking fine until now. Thank you again for your advice!
Does anyone have the link to sneakyghost's NoWipe package download section?
riddell said:
Does anyone have the link to sneakyghost's NoWipe package download section?
Click to expand...
Click to collapse
Here is a newer one: https://androidfilehost.com/?fid=817550096634760161
You need S-OFF for this file.
THANKS LUCY !
But I'd really love to get the link to sneakyghost's NoWipe package download section page.
Looking for a no-wipe 4.38.502.xx
Yes I have S-Off
---------- Post added at 08:41 AM ---------- Previous post was at 07:42 AM ----------
I'm downloading that file now and will try to change the SKU to 502. Is 401 for the International?
NoWipe RUU
lucyr03 said:
Here is a newer one: https://androidfilehost.com/?fid=817550096634760161
You need S-OFF for this file.
Click to expand...
Click to collapse
Hi Lucy,
I used the M9_4.28.401.3_NoWipe_TWRP3100.zip file with GREAT SUCCESS!
I had to change the android-info text first as I was using SKU 502.
I notice that after the install it still showed the old version number in download mode but I continued on to install ViperOneM9 6.2.0
I'm now a proud user of ViperOneM9 6.2.0 !!! Ya-a-a
Antigua Guy
riddell said:
Hi Lucy,
I used the M9_4.28.401.3_NoWipe_TWRP3100.zip file with GREAT SUCCESS!
I had to change the android-info text first as I was using SKU 502.
I notice that after the install it still showed the old version number in download mode but I continued on to install ViperOneM9 6.2.0
I'm now a proud user of ViperOneM9 6.2.0 !!! Ya-a-a
Antigua Guy
Click to expand...
Click to collapse
You don't need to change sku, your phone is AT&T which is a GSM one, so you can flash the international firmware.
If the download mode still shows the old firmware then the flash wasn't successful.
And the SKU gets changed automatically if you flash the international firmware on an AT&T phone since they don't use the same SKU.
Sent from my HTC One M9 using XDA Labs