Dear All,
My M9 is S-OFF and i converted it to a dev Edition from WWE when it was working on android 5 , can I downgrade to lollipop ? Is it safe ?
ShawEgypt said:
Dear All,
My M9 is S-OFF and i converted it to a dev Edition from WWE when it was working on android 5 , can I downgrade to lollipop ? Is it safe ?
Click to expand...
Click to collapse
Yes with s-off you can change your device to any version you want
You only need the correct CID and MID and a twrp backup or a RUU
Sent from my Lenovo TAB 2 A10-70F using Tapatalk
clsA said:
Yes with s-off you can change your device to any version you want
You only need the correct CID and MID and a twrp backup or a RUU
Sent from my Lenovo TAB 2 A10-70F using Tapatalk
Click to expand...
Click to collapse
I don't think simply restoring a backup is a good idea if you want to downgrade since it doesn't contain the corresponding firmware. It's never good to use a rom that is not optimsed for the installed firmware. Flashing one of Sneakyghost's firmware packs and restoring a corresponding backup should be fine, though.
Nevertheless the most recommended way would be flashing a RUU just like clsA already said.
I read in one of the threads earlier that the firmware generally is OK being the latest, even if you go back to lollipop. Maybe not always but that seems to be the case. Can't remember if sneaky ghost said it in the venom thread or where I saw it though. Problems occur running new software on old firmware. I guess.
Sent from my HTC One M9 using Tapatalk
Yes newer firmware is OK to run on older version of Android.
It's recommended not to run newer versions of Android on older firmware as it usually leads to issue's.
Sent from my HTC One M9 using Tapatalk
Related
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 guys, i am running the latest marshmallow on my htc m8 dev edition. i tried to install 4.4.3 and 4.4.4 RUU and both gave me the same error, error 159. how can i solve this?
I downgraded from lollipop multiple times using the same RUU but now is not working.
Are you s-off?
redpoint73 said:
Are you s-off?
Click to expand...
Click to collapse
Yes, s-off, unlocked, supercid. did the same procedure many times already. Downloaded the ruu twice to see if wasn't a corrupted file and no luck.
Maybe marshmallow changed something?
I already was in marshmallow in gpe and reverted to sense lollipop to receive the OTA to marshmallow in sense version, ruu worked fine too.
Find an older hboot and get that installed. Should be able to downgrade after that is installed. That's what I figured out a while back.
Sent from my HTC One_M8 using Tapatalk
tony_5309 said:
Find an older hboot and get that installed. Should be able to downgrade after that is installed. That's what I figured out a while back.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I did a bigger route than this just to be sure, but worked.
Converted to GPE, and reverted the way i always did but this time using the 4.4.3 ruu. it worked fine.
tony_5309 said:
Find an older hboot and get that installed. Should be able to downgrade after that is installed.
Click to expand...
Click to collapse
That's what I was going to suggest, old firmware, than the old RUU.
The MM DevEd RUU has been finicky for some. Some folks have had to run the MM firmware before the RUU will work. So it wouldn't surprise me if similar was required to downgrade.
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.
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.