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").
Related
My M8 has the CID of HTC_044 and I would like to flash latest ROM. However it requires latest firmware, ie 2.22.401.4, I am wondering if it is safe to flash the firmware to my device being with different CID as the firmware's android-info does not contain my device CID.
I have S-OFF on my device, I am wondering if I change mt CID to supercid would allow my device to run the firmware without issue.
Thanks in advance.
Yep,if your phone is supercid,u can flash that firmware...
hellcommando said:
My M8 has the CID of HTC_044 and I would like to flash latest ROM. However it requires latest firmware, ie 2.22.401.4, I am wondering if it is safe to flash the firmware to my device being with different CID as the firmware's android-info does not contain my device CID.
I have S-OFF on my device, I am wondering if I change mt CID to supercid would allow my device to run the firmware without issue.
Thanks in advance.
Click to expand...
Click to collapse
If your firmware for CID HTC__044 is 2.22.707.3, it is not necessary for you to flash another firmware to run a 2.22.401.4 ROM.
As long as the firmware is 2.22.xxx.x ... you're good to go.
Anyway it's up to you if you want to flash 2.22.401.4 firmware but your Radio will be the EU region if the firmware that you flash come with radio image. If you currently in Asia, it's best to keep 2.22.707.3 firmware
hdorius said:
Yep,if your phone is supercid,u can flash that firmware...
Click to expand...
Click to collapse
Thank you!
ckpv5 said:
If your firmware for CID HTC__044 is 2.22.707.3, it is not necessary for you to flash another firmware to run a 2.22.401.4 ROM.
As long as the firmware is 2.22.xxx.x ... you're good to go.
Anyway it's up to you if you want to flash 2.22.401.4 firmware but your Radio will be the EU region if the firmware that you flash come with radio image. If you currently in Asia, it's best to keep 2.22.707.3 firmware
Click to expand...
Click to collapse
Thank you! However I have heard there was one 2.22.7xx posted but was meant for M7, and at the moment I could not find 2.22.707.3 firmware from any firmware repository. I'm from Asia, could you please kindly post the link so that I wont brick my phone? Thank you!!
hellcommando said:
Thank you! However I have heard there was one 2.22.7xx posted but was meant for M7, and at the moment I could not find 2.22.707.3 firmware from any firmware repository. I'm from Asia, could you please kindly post the link so that I wont brick my phone? Thank you!!
Click to expand...
Click to collapse
When we read firmware we look at x.xx.707.x not 2.22.7xx.x
You don't need 2.22.707.3 firmware if you already done the OTA update.
Please advise your current firmware that you have ... check what is written on the bootloader ... is it 1.54.707.7 or 2.22.707.3 ?
If it is 1.54.707.7 then you need to do OTA update.
If it is 2.22.707.3 then you're good to flash any ROM.
ckpv5 said:
When we read firmware we look at x.xx.707.x not 2.22.7xx.x
You don't need 2.22.707.3 firmware if you already done the OTA update.
Please advise your current firmware that you have ... check what is written on the bootloader ... is it 1.54.707.7 or 2.22.77.3 ?
If it is 1.54.707.7 then you need to do OTA update.
If it is 2.22.707.3 then you're good to flash any ROM.
Click to expand...
Click to collapse
Couldn't check my firmware version as the OS field is empty in the bootloader.
Hboot: 3.16.0.0000
Radio: 1.16.2133156.UA10G
But I highly doubt my firmware is 2.22.707.3, I would think it is more likely to be 1.54.707.7 as I have rooted by phone before newer firmware roll out.
So can I use your firmware in http://forum.xda-developers.com/showthread.php?t=2701376&page=141
and flash it by using this guide? http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
hellcommando said:
Couldn't check my firmware version as the OS field is empty in the bootloader.
Hboot: 3.16.0.0000
Radio: 1.16.2133156.UA10G
But I highly doubt my firmware is 2.22.707.3, I would think it is more likely to be 1.54.707.7 as I have rooted by phone before newer firmware roll out.
So can I use your firmware in http://forum.xda-developers.com/showthread.php?t=2701376&page=141
and flash it by using this guide? http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
Click to expand...
Click to collapse
Right ... your current hboot is 3.16 so it's 1.54.707.7
I suggest that you restore 1.54.707.7 stock Backup, flash back stock recovery and do the OTA (no need to relock bootloader or S-On .. OTA update work on unlocked bootloader and S-Off)
I don't post firmware on XDA. Those that I posted are recovery and stock backup.
If you insist to update firmware without OTA update .. that's you call. Someone maybe will guide you how to do it as I don't feel comfortable telling how to update firmware.
ckpv5 said:
Right ... your current hboot is 3.16 so it's 1.54.707.7
I suggest that you restore 1.54.707.7 stock Backup, flash back stock recovery and do the OTA (no need to relock bootloader or S-On .. OTA update work on unlocked bootloader and S-Off)
I don't post firmware on XDA. Those that I posted are recovery and stock backup.
If you insist to update firmware without OTA update .. that's you call. Someone maybe will guide you how to do it as I don't feel comfortable telling how to update firmware.
Click to expand...
Click to collapse
Awesome! I just followed your advice by doing the safe way, flashed stock recovery and backup. I'm running on 2.22.707.x now! Thanks a lot :good:
hellcommando said:
Awesome! I just followed your advice by doing the safe way, flashed stock recovery and backup. I'm running on 2.22.707.x now! Thanks a lot :good:
Click to expand...
Click to collapse
Great
Now you can flash any Sense 6 custom ROM that you like.
Only remember that you don't need to flash another firmware, your current one is good enough.. just flash ROM.
I am having the same issue - I have the HTC__044 and need new firmware to get the newest ROM.
I am S-On and CANT get S-off (s-off needed to flash firmware)...firewater does not work with my phone after multiple tries.
I tried getting Sunshine to work for s-off, but I need to be on a stock Sense ROM (I am on Viper 1.8) and don't have a stock backup. I can't find ANY stock ROM's online! Once I have supercid i was going to flash firmware, but without S off...I'm going nowhere (it seems)
anyone have an idea where I should start?
charkswitlazers said:
I am having the same issue - I have the HTC__044 and need new firmware to get the newest ROM.
I am S-On and CANT get S-off (s-off needed to flash firmware)...firewater does not work with my phone after multiple tries.
I tried getting Sunshine to work for s-off, but I need to be on a stock Sense ROM (I am on Viper 1.8) and don't have a stock backup. I can't find ANY stock ROM's online! Once I have supercid i was going to flash firmware, but without S off...I'm going nowhere (it seems)
anyone have an idea where I should start?
Click to expand...
Click to collapse
Stock ROMs and recoveries for HTC__044
http://forum.xda-developers.com/showthread.php?t=2701376
charkswitlazers said:
anyone have an idea where I should start?
Click to expand...
Click to collapse
Everything that you need is here : http://forum.xda-developers.com/showthread.php?t=2701376
1. Restore nandroid backup 1.54.707.7
2. flash stock recovery 1.54.707.7
3. reboot and check for OTA
4. install OTA
5. done .. your ROM will be 4.4.3 - 2.22.707.3
6. flash any 4.4.3 custom ROM that you like if any
All above no need to relock bootloader or S-Off, it works on S-On
If you want to S-Off with sunshine, step 1 & 2 then sunshine
or after step 5 then sunshine (both way should work)
ckpv5 said:
Everything that you need is here
1. Restore nandroid backup 1.54.707.7
2. flash stock recovery 1.54.707.7
3. reboot and check for OTA
4. install OTA
5. done .. your ROM will be 4.4.3 - 2.22.707.3
6. flash any 4.4.3 custom ROM that you like if any
All above no need to relock bootloader or S-Off, it works on S-On
If you want to S-Off with sunshine, step 1 & 2 then sunshine
or after step 5 then sunshine (both way should work)
Click to expand...
Click to collapse
I'm still a little on the noob side with rooting/flashing..I am at work and don't have time to read much - i will go home and give it a go... I'm sure I will have lots of questions
A quick look at the site, i saw lots of recoveries but not very many stock ROMs. I mainly just need a plain/rooted stock Sense rom to run Sunshine. After which i can flash new firmware, then the new custom ROM i've been wanting. Also, does a nandroid HAVE to be HTC__044, or can it be any WWE cid? (like anything that's "HTC__xxx")?
Excuse my ignorance...trying to learn as much as possible
I just got my m8 from Tmobile today, and I am on firmware 157.531.7
I've checked several times for updated firmware, but always comes back nothing.
Am I stuck on this, or will it take awhile for the network to "see me" and send it?
not rooted, fully stock for now
thanks so much!
charkswitlazers said:
I'm still a little on the noob side with rooting/flashing..I am at work and don't have time to read much - i will go home and give it a go... I'm sure I will have lots of questions
A quick look at the site, i saw lots of recoveries but not very many stock ROMs. I mainly just need a plain/rooted stock Sense rom to run Sunshine. After which i can flash new firmware, then the new custom ROM i've been wanting. Also, does a nandroid HAVE to be HTC__044, or can it be any WWE cid? (like anything that's "HTC__xxx")?
Excuse my ignorance...trying to learn as much as possible
Click to expand...
Click to collapse
If your main purpose to restore to stock to get SunShine working, then any nandroid backup will do either HTC__044 or WWE. You don't really need a rooted stock as SunShine works on non-rooted ROM too.
As you said you're a noob, that is why I suggest to restore to 1.54.707.7 then OTA to 2.22.707.3 so you don't need to manually flash firmware to get other custom ROMs running flawlessly. It is not necessary to have 2.22.401.4 firmware but it is necessary to have a 2.22.xxx.x firmware for those custom ROMs, unless you're not in Asia.
As you can see in my sig, I'm on 2.22.707.3 firmware, I can run any ROM without problem.
Being a noob, you may make a stupid mistake when flashing firmware.
There is also by mike or so a stock Rom as a zip.
Flash it like a custom Rom Flash the stock kernel and better the recovery and do sunshine...easier then with getting nandroid backup etc
Slow Booting & Sense 6 Toolbox Not Working On ARHD v10.2
One-M8-Master said:
There is also by mike or so a stock Rom as a zip.
Flash it like a custom Rom Flash the stock kernel and better the recovery and do sunshine...easier then with getting nandroid backup etc
Click to expand...
Click to collapse
Hi One-M8-Master,
I've read quite a few of your posts & given that your moniker seems appropriate, I'm wondering if you might be able to help me?
I've posted this on another thread but haven't got very far as yet, so am hoping that you might be able to get me out of the stupid hole I've dug myself into :fingers-crossed:
It is quite a long description but if you don't fall asleep reading it, I'd really appreciate any help you might be able to give me.....Here goes:
"Hi Guys,
Now I know you're all already thinking that I didn't update my firmware before I flashed ARHD & now I'm getting all the problems that come along with not doing that......& you'd be correct....kind of. HOWEVER, as it turns out, I already seem to have it. Let me explain.
As you can see, I'm relatively new to all this but successfully unlocked, rooted & installed a custom ROM on my ASUS TF700T tablet, so I wanted to do it with my One M8. I always do loads of reading before I start anything (I even read the instructions for new games before I attempt to play them because I'm a bit weird like that!) but what happened on this occasion was that I did the reading, unlocked the phone, flashed TWRP, & rooted it but then ran into the problem that some people appear to have had when trying to s-off via the adb commands & Firewater, that is, my pc could see the phone but when I gave the reboot command, it told me it wasn't connected.
I then got into hours of reading to try & solve this issue, discovered that (without Sunlight) on some devices it just doesn't work once you've accepted the 'should we allow this pc to connect every time' message (which I NEVER normally say 'yes' to), unless you install the Android Studio & Java Develpers Kits, update your version of adb, & force the phone to ask again (which I did but it turned out that I already had the latest version of adb, so that route proved fruitless!). I actually missed a night's sleep trying to resolve the problem, so work wasn't good the next day! but I think it is here is where my problems started because I was so tired & frustrated that I just picked a ROM & flashed it. I had even read the warning about not flashing it if you didn't have the correct firmware but I think that being so tired, it didn't really sink in, or I'd forgotten about it by the time I just flashed the ROM.
By this point, I'd been sat in front of my pc for about 30 hours & needed to go to work but the phone was actually booting through to ARHD, so I was relatively happy in the knowledge that at least I hadn't bricked it! On starting to use the phone that evening, I noticed the long boot times & then that my Sense 6 Toolbox didn't seem to be making any changes, even if I rebooted the device, so I went back to the beginning of this thread & started reading again. Thus, I re-read the firmware warning & panicked (my 2nd mistake!), thinking that I was getting the problems because I hadn't updated the firmware (it still didn't occur to me to just check because I think I just assumed that I wouldn't have it). So.....I tried to restore my TWRP backup of the stock ROM that I made after I had unlocked/rooted, with the intention of reverting to the stock ROM, getting the OTA update & then re-flashing ARHD but despite TWRP telling me that the backup had been successful, the phone went into a bootloop back into TWRP. I solved this by re-flashing the ARHD ROM that I knew at least would get my phone out of the bootloop & back into KitKat, which it did. I then checked what version of the firmware I had & to my surprise, my Build Number in About\Software Information\More says "2.22.401.4 CL365360 release-keys", so it looks like I had the correct firmware version all along?
The above being the case, I'm now puzzled as to why I'm getting the problems that I'm getting with ARHD? Does anyone have any clues/answers that might get me out of this hole I've dug for myself & get my awesome One M8 working like it should?
I know I've caused this problem by doing things when I was too tired to think straight but I'm fresh as a daisy now (still fairly noobish but fresh ) & now I need your help to sort myself out. I would be so grateful for any help anyone can give me to get me back on track.
I hope all of that makes sense & thanks in advance."
@dan5001
The firmware you speak of is the displayed version main number of the flashed rom. It has no relation to your actual installed firmware. Check your bootloader and post here what it says. I bet it is still hboot 3.16 and if that's the case your firmware is not updated.
Mr Hofs said:
@dan5001
The firmware you speak of is the displayed version main number of the flashed rom. It has no relation to your actual installed firmware. Check your bootloader and post here what it says. I bet it is still hboot 3.16 and if that's the case your firmware is not updated.
Click to expand...
Click to collapse
Hi.
This is my own fault but I'm getting really frustrated with it because I've probably spent a total of 40 hours on it so far
I tell you that because I know that I needed S-OFF & SUPER CID to be able to update my firmware, so I just thought "screw it" & I paid for Sunshine. I now have S-OFF & following Vomer's guide here:
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
I now have S-OFF & SUPER CID. I thought that would be the end of my issues but it would appear not!
Looking at my bootloader, you are correct, HBOOT is 3.16.0.0000!
However, I've tried to upgrade this firmware by downloading what I think is the correct update .zip from the list at the bottom of the aforementioned Vomer's guide (v2.22.401.5 (Rename to firmware.zip after downloading)), renaming it as suggested, & then flashing it in TWRP but it just keeps telling me that the update has failed!
Do I have to do it using the adb commands on Vomers guide? I didn't think so but it's just not working??
I appreciate any help you can give me with this. Given that I've spent so long on this & have paid for Sunshine, you can see that I'm trying to help myself but I've still got rain!!
EDIT
Just a thought, I do still have ARHD v10.2 installed at the moment because even though it's not working properly without the correct firmware, it's the only ROM I've got at the moment, so it means I can use the M8 to a degree; would that cause the problem with upgrading the firmware?
Firmware flash can be done via fastboot commands, that's how i did it
Installed rom has no influence on the to flash firmware, try it via fastboot
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.
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 guys i'll explaine what happened:
1. I was on nougat rom rooted trying to get back to stock.
2. I run an old lollipop ruu.exe from my computer but it reboots the phone to bootloader mode without going on.
3. I manually reboot to bootloader to see it if does move on but nothing.
4. I disconnect the phone.
Now there's no OS and recovery and flashing TWRP succeeds but when I try to reboot to recovery it say that's not possible.
I tried to flash via sdcard the OPJAIMG but it seems like it doesn't see it (screenshot in attachements).
I can access download mode
I'm S-OFF on Nougat firmware.. what can i do?
EDIT: I tried to live-boot TWRP but it stays forever on booting in cmd and flashing in phone
@Flippy498 maybe you have an idea? You have so much knowledge on this!
I haven't seen a 4.x RUU for the SKU 401, yet. You therefore would need to flash one of Sneakyghost's 3.x firmware packs before you're able to use a 3.x RUU, again. The encryption key changed between firmware 3.x and 4.x. Therefore you can't use 4.x RUUs on firmware 1.x to 3.x and vice versa.
In contrast to the flashing command the command for booting TWRP via fastboot needs to be used while the phone is booted to the bootloader instead of the download mode. However, since I haven't seen a publicly available TWRP backup for the latest 401 firmware, yet, TWRP won't help you much in your situation. (Or do you have your own backup?)
That means on the other hand that you currently need to downgrade to 3.35.401.12 and to re-install the OTAs for 3.35.401.32 and 4.14.401.7 since the latest RUU is for version 3.35.401.12.
Edit: Oh, and the only RUU.exe for SKU 401 that I know is for that 1.x firmware wird the 17 at the end. You shouldn't use that one. The corresponding OTA only got distributed for one single CID (I forgot which one it was). That means that you won't receive OTAs if you aren't using that specific CID on your phone. That means you would need to flash another RUU afterwards for getting away from that firmware version. And instead of flashing two RUUs you could save some time and directly flash the second one.
Sent from my HTC One M9 using XDA Labs
mrsmtt said:
Hi guys i'll explaine what happened:
1. I was on nougat rom rooted trying to get back to stock.
2. I run an old lollipop ruu.exe from my computer but it reboots the phone to bootloader mode without going on.
3. I manually reboot to bootloader to see it if does move on but nothing.
4. I disconnect the phone.
Now there's no OS and recovery and flashing TWRP succeeds but when I try to reboot to recovery it say that's not possible.
I tried to flash via sdcard the OPJAIMG but it seems like it doesn't see it (screenshot in attachements).
I can access download mode
I'm S-OFF on Nougat firmware.. what can i do?
EDIT: I tried to live-boot TWRP but it stays forever on booting in cmd and flashing in phone
Click to expand...
Click to collapse
1 - Try 0(zero)PJAIMG and not O
2 - Restore to stock recovery
3 - Start phone in download mode and push volume UP
benshoes said:
1 - Try 0(zero)PJAIMG and not O
Click to expand...
Click to collapse
Oh, I missed that typo.
benshoes said:
2 - Restore to stock recovery
Click to expand...
Click to collapse
That's actually not needed. The RUU will flash the stock recovery by its own. You only need a working download mode.
Flippy498 said:
Oh, I missed that typo.
That's actually not needed. The RUU will flash the stock recovery by its own. You only need a working download mode.
Click to expand...
Click to collapse
Tried to live-boot TWRP from bootloader since I have my own backup but it fails with the following message:
FAILED (remote: dtb not found)
About 0PJAIMG it is named correctly in SD it's just me that made a mistake writing here.
So last chance for me is to head to Sneakyghost's thread and flash the 3.35.401.32 fullstock firmware then head to your google sheet and pick the 3.35.401.12 RUU and flash it right?
mrsmtt said:
Tried to live-boot TWRP from bootloader since I have my own backup but it fails with the following message:
FAILED (remote: dtb not found)
About 0PJAIMG it is named correctly in SD it's just me that made a mistake writing here.
So last chance for me is to head to Sneakyghost's thread and flash the 3.35.401.32 fullstock firmware then head to your google sheet and pick the 3.35.401.12 RUU and flash it right?
Click to expand...
Click to collapse
Correct. Although you can use the 3.35.401.12 firmware pack, as well. It doesn't matter which one of the two firmware versions you choose.
Flippy498 said:
Correct. Although you can use the 3.35.401.12 firmware pack, as well. It doesn't matter which one of the two firmware versions you choose.
Click to expand...
Click to collapse
Thanks for your support! Anyway i'm going to do the whole thing tomorrow.. I was reading the instructions on Sneakyghost's thread and he recommend to use his tool because it contains the htc_fastboot that works better than google's one but I don't see any option to lunch the flash zip firmware command from the tool so I decided to get the htc_fastboot.exe file and move it inside another folder (a new one) in wich i'll put both firmware and rom zip to flash. I'm saying this because i'm not 100% sure this is correct so just to clear all doubts..
Once again @Flippy498 you saved me and I say thank you a million times I promise i'll take a break at trying to destroy my m9 so you'll definitely not hear me / see me here anymore hehe
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