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
Related
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").
just flashed Viper rom and love it.
I noticed that in order to flash the newest version of Viper Rom you have to flash the firmware manually which is quite complicate for noobs like me
And it's confusing to choose the right firmware to flash, my M9 is in contract with Bell and I really don't want to brick my phone...
So is there any chance I can update form 1.9.1 to 2.x.x by OTA in the future?
Ducati Scar said:
just flashed Viper rom and love it.
I noticed that in order to flash the newest version of Viper Rom you have to flash the firmware manually which is quite complicate for noobs like me
And it's confusing to choose the right firmware to flash, my M9 is in contract with Bell and I really don't want to brick my phone...
So is there any chance I can update form 1.9.1 to 2.x.x by OTA in the future?
Click to expand...
Click to collapse
No there won't be an OTA because of the new rom base. But you can download the zip from their site and install it on the old firmware if you choose the option with the old kernel.
In regard to your firmware update "problem": What version are you on? If you don't know you can find out by booting into download mode. It's stated in the line with "OS". If you are S-ON and not on a firmware version with 1.32.401.XX then the firmware update is not possible for you since the file is unsigned. In that case you can use Sunshine S-OFF and follow one of the guides here on xda to update your phone. Another option would be staying S-ON, flashing the correct RUU for your CID and your firmware version (both stated in download mode*) and update via the official HTC OTA. But at the moment the second method is not possible since version 1.40.XXX has not been distributed officially until now. So depending on your choice you may have to wait some weeks.
* Since there has not been any aboot update you are able to use RUUs for older firmware versions, too. For example you could use 1.32.401.8 even if you were on 1.32.401.15.
Flippy498 said:
No there won't be an OTA because of the new rom base. But you can download the zip from their site and install it on the old firmware if you choose the option with the old kernel.
In regard to your firmware update "problem": What version are you on? If you don't know you can find out by booting into download mode. It's stated in the line with "OS". If you are S-ON and not on a firmware version with 1.32.401.XX then the firmware update is not possible for you since the file is unsigned. In that case you can use Sunshine S-OFF and follow one of the guides here on xda to update your phone. Another option would be staying S-ON, flashing the correct RUU for your CID and your firmware version (both stated in download mode*) and update via the official HTC OTA. But at the moment the second method is not possible since version 1.40.XXX has not been distributed officially until now. So depending on your choice you may have to wait some weeks.
* Since there has not been any aboot update you are able to use RUUs for older firmware versions, too. For example you could use 1.32.401.8 even if you were on 1.32.401.15.
Click to expand...
Click to collapse
Thank you for your reply! But Im still confused about which zip should I flash. In the download link there are firmware package for US carriers and international version. I bought my phone from Bell Canada under a 2-yr contract, can I flash the international one?
Ducati Scar said:
Thank you for your reply! But Im still confused about which zip should I flash. In the download link there are firmware package for US carriers and international version. I bought my phone from Bell Canada under a 2-yr contract, can I flash the international one?
Click to expand...
Click to collapse
As I said you need to know your actual firmware version and your CID. Both are stated in download mode (the firmware version is called "OS"). Without these information no one can tell you which RUU to use.
Flippy498 said:
As I said you need to know your actual firmware version and your CID. Both are stated in download mode (the firmware version is called "OS"). Without these information no one can tell you which RUU to use.
Click to expand...
Click to collapse
My CID num is BM_001 and OS is 1.3.2.66.30.
There is one on RUU site called "0PJAIMG_HIMA_UL_L50_SENSE70_ATT_BM_1.32.666.6_R2_Radio_01.01_U11440221_59.04.50303G_2_F_release_426170_signed.zip"
is this the correct one? What's difference bet. a "OPJAIMG" and a "RUU"? Sorry there are lots of things I don't know
Ducati Scar said:
My CID num is BM_001 and OS is 1.3.2.66.30.
There is one on RUU site called "0PJAIMG_HIMA_UL_L50_SENSE70_ATT_BM_1.32.666.6_R2_Radio_01.01_U11440221_59.04.50303G_2_F_release_426170_signed.zip"
is this the correct one? What's difference bet. a "OPJAIMG" and a "RUU"? Sorry there are lots of things I don't know
Click to expand...
Click to collapse
As you never stated it before I assume your phone is S-ON (again stated in download mode). So you can try that file without having to fear a brick since the worst case scenario is that it simply won't flash. All you have to do now is the following:
Warning all files and data except the ones on your external SD card are going to be deleted
Download the RUU
Rename it to 0PJAIMG.zip
Copy the file on an external SD card that is formatted to fat32 and not bigger than 32 gb
Boot into download mode
Follow the instructions that are shown on your M9's screen
Congratulation you are now back on stock rom and firmware
But just to clarify it again: The 1.40 firmware has not been distributed by HTC yet. All you can do for now is updating to the firmware version you had installed before running the RUU.
"0PJAXXX" (that's a zero not an O) is just the name of your device and I guess the "IMG" should indicate that the file is an image of the software. The XXX may differ depending on the model you own.
Hello everybody,
I got an issue. I recently updated my M9 to nougat and today I tried to downgrade (With OPJAIMG method from bootloader) but with no success. I also tried to push from adb and the ruu.exe method but none worked. You guys know any sollutions?? Obviously I changed MID and CID to international before doin' all this.
I noticed that I can't even install CM anymore (gives me fail 7 even if in the build.prop i see that himaulatt is supported.)
Hope someone can figure this out.
Thanks....
The reason for your problems is the same because of which people on any 3.x firmware can't flash the 4.x RUU. The encryption keys changed between the two firmware version. You need to flash one of the full wipe or no wipe firmware packs since they're not encrypted and contain the encryption key for their specific firmware. This way you restore the ability to flash a 3.x RUU.
Sent from my HTC One M9 using XDA Labs
All done...thank you so much... U just made my day
Flippy498 said:
The reason for your problems is the same because of which people on any 3.x firmware can't flash the 4.x RUU. The encryption keys changed between the two firmware version. You need to flash one of the full wipe or no wipe firmware packs since they're not encrypted and contain the encryption key for their specific firmware. This way you restore the ability to flash a 3.x RUU.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
hi,
Same things happened to me.
I flashed android 7.0 firmware(developer firmware and rom) and 7.0 RUU.exe. and I wanted to go back to android 5.0.2. I flashed 1.xx full wipe firmware and 5.0.2 custom rom. but it caused a bootlop until flashed a 6.0 firmware.
I think that you have to flash boot.img from the zip with fastboot.
Flippy498 said:
The reason for your problems is the same because of which people on any 3.x firmware can't flash the 4.x RUU. The encryption keys changed between the two firmware version. You need to flash one of the full wipe or no wipe firmware packs since they're not encrypted and contain the encryption key for their specific firmware. This way you restore the ability to flash a 3.x RUU.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Dear Bro,
could you tell us the link to download Firmware with full wipe or Firmware with No wipe.
also if you please, could you give us the tutorial to downgrade from Nougat.
thank you, Bro.
shahnaz said:
Dear Bro,
could you tell us the link to download Firmware with full wipe or Firmware with No wipe.
also if you please, could you give us the tutorial to downgrade from Nougat.
thank you, Bro.
Click to expand...
Click to collapse
Everything that isn't already explained somewhere else is explained in my last post. The firmware packs are located in this thread. If you don't know how to flash a RUU you might want to (re-)read the ReadMe thread.
Flippy498 said:
Everything that isn't already explained somewhere else is explained in my last post. The firmware packs are located in this thread. If you don't know how to flash a RUU you might want to (re-)read the ReadMe thread.
Click to expand...
Click to collapse
DONE!!
thanks bro, thanks for the firmware packs location.
for to flash RUU, i already know it.is, maybe there is friend in here doesnt know.
my HIMA already back to android 6.0
:good:
i am currently on nougat with s-on, can i do the full wipe restore for 3.x firmware? or can i flash directly with 3.x ruu using the sd card method?
can u provide to me the link to download full wipe firmware for my htc one a9 please?
samweli benjamin said:
can u provide to me the link to download full wipe firmware for my htc one a9 please?
Click to expand...
Click to collapse
You need to search for them in the forum that belongs to your device. This is the HTC One M9 forum. Chances are very high that no one here owns an A9 and therefore probably no one has the files you need.
Sent from my HTC One M9 using XDA Labs
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.
Downloaded the latest RUU for ATT (RUU_HIMA_UL_N70_SENSE80_ATT_MR_Cingular_US_4.27.502.7) and for unlocked/developer (RUU_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.30.617.12)and tried to run both on my ATT one m9 which is on 3.35.617.12. They both gave me an 132 error saying: "Signature error". How can I fix the error? I'm using ATT sim card if that matters.
Please read the ReadMe thread. It will explain why you can't flash RUUs with firmware 4.x on a device with firmware 3.x and lower.
Flippy498 said:
Please read the ReadMe thread. It will explain why you can't flash RUUs with firmware 4.x on a device with firmware 3.x and lower.
Click to expand...
Click to collapse
Thanks, Flippy. After reading the readme thread, I have a few more questions.
1. Do I need to change my CID in order to install 4.x firmware from 3.x? I have super CID now and Soff.
2. i want to install custom rom, so should I install ATT stock rom or unlocked/developer stock rom? Does it matter or as long as i'm on 4.x firmware, i'm ok.
3. 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 (or any lower) firmware. You either need to flash a NoWipe/Full-Wipe Firmware Pack beforehand (only possible with S-OFF). Can I install nowipe 4.30.617.12 from here? https://docs.google.com/spreadsheets/d/1ZaiJ3F_f76sVa4daU5H62OYi5Bj23LEBBv4xDTQ8y-M/pubhtml
4. Once I install the nowipe package in #3 above, do I need to install the stock rom downloaded from HTC then install any custom rom I want?
I'm going to re-use your numbering system for answering.
1. The CID has nothing to do with the incapability of flashing a 4.x firmware on a 3.x device. And as mentioned in the thread you either need to get back to stock and install the official OTA (not possible with the SCID - that's one of the reasons why I recommend in the ReadMe thread not to use it) or to use one of Sneakyghost's firmware packs for updating the firmware (only possible with S-OFF).
2. Some custom roms (only sense-based ones) support features of the US-carrier-branded firmwares. Aside from that difference it doesn't matter which 4.x firmware you use in the end.
3. That's Sneakyghost's spreadsheet that you can access from the thread that I linked in the sentence that you quoted.
4. Why would you want to waste time by flashing the stock rom if you want to replace it with a custom rom, anyway? Flashing a RUU isn't necessary. Sneakyghost's firmware packs are (more or less) the same as a RUU.zip but (intentionally) lack the system partition.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
I'm going to re-use your numbering system for answering.
1. The CID has nothing to do with the incapability of flashing a 4.x firmware on a 3.x device. And as mentioned in the thread you either need to get back to stock and install the official OTA (not possible with the SCID - that's one of the reasons why I recommend in the ReadMe thread not to use it) or to use one of Sneakyghost's firmware packs for updating the firmware (only possible with S-OFF).
2. Some custom roms (only sense-based ones) support features of the US-carrier-branded firmwares. Aside from that difference it doesn't matter which 4.x firmware you use in the end.
3. That's Sneakyghost's spreadsheet that you can access from the thread that I linked in the sentence that you quoted.
4. Why would you want to waste time by flashing the stock rom if you want to replace it with a custom rom, anyway? Flashing a RUU isn't necessary. Sneakyghost's firmware packs are (more or less) the same as a RUU.zip but (intentionally) lack the system partition.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Thanks, Flippy498. Regarding your response to #4 above, I can just flash Sneakyghost's firmware pack, then i can install any Android 7 custom rom? Do I understand it correctly?
Correct.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Correct.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Just want to report back that my phone is on Slim Rom 7 now by following Flippy's instruction. Thanks again, Flippy.