Related
Hello,
Usually i don't write messages on English forums, but nobody in Poland is able to help me. My friend asked me to update hes stock software of HTC ONE M9 by manufacturer update from 2.10.206.2 to 2.10.206.180. because this update is available. He couldn't do it by himself because somebody flash this phone with TWRP. I've installed stock recovery, but phone still does not allow me to install update or force install it by flashing with bootloader (OTA and recovery software downloaded from xda). I wanted to post some pictures but forum rules doesn't allow me to do it. So I will just point you guys to my polish thread so you can look at the photos. forum.android.com.pl/topic/273151-aktualizacja-stockowego-romu-z-twrp/
You need an untouched system image. File-based OTAs aren't used anymore on "newer" devices like the M9. Block-based OTAs can't be installed anymore as soon as you flash anything via twrp. Either use one of the backups or the Android M RUU for the SKU 206 which you can find both in my google sheet (link can be found in my signature).
Sent from my HTC One M9 using XDA Labs
I know that probably for you it is a stupid question but which file would be the best for me? can you paste this file name? And would I be able to install it by standart ''fastboot oem rebootRUU ;htc_fastboot flash zip firmware.zip'' commands?
Boot to Download Mode and look at the line with OS at the beginning. That's your current firmware version. Either restore the corresponding backup and then install the updates via the OTA function in settings>about or flash a RUU that has at least the same firmware version (in this case you need to install the OTAs via settings>about) or a newer one (in this case the phone will get updated automatically). [Hint: There only is one O2/206 RUU which fulfills this requirement.] Flashing instructions or restoring instructions can be found directly above the downloads.
You could flash a RUU via fastboot but I personally prefer recommending the SD card method since there are so many reasons why fastboot can fail (missing drivers, still installed Sync Manager, general problems with Win 8/8.1/10 - just to name a few) and it's easier for me to help if you use more fail-safe method.
I've tried to install two stock backups Stock_Backup_2.10.206.180.zip and Stock_Backup_2.10.206.2.zip, neither of them didnt want to flash. I've tried two ways, first in recovery partition via update from sd and second from download mode via 0PJAIMG.ZIP and this is what i got.
postimg.org/image/xz9gtdrdv/
and
postimg.org/image/mnrdgk8vv/
After trying to update from recovery i got:
postimg.org/image/ma887fuub
I didn't do any RUU because i dont see any that would fit my phone, if I'm wrong please correct me. And please help me
I actually don't understand why you completely ignore the instructions above the download links. I'm not going to rephrase every step you have to make since they're all explained in the google sheet.
As mentioned in the sheet those are TWRP backups so you have to restore them with TWRP. Neither the stock recovery nor the SD card method are able to handle them. (The latter is only meant to be used for RUUs.) Besides I told you to look at the line with OS at the beginning when you boot to Download Mode. I highly doubt that it states 2.10.206.8 and 2.10.206.180 at the same time. Choose the one that corresponds to your current firmware version and restore it via TWRP.
Concerning your search for the correct RUU: I told you that the SKU has to match and that you need to look at the 206 RUUs. There are only four RUUs which can be found in the sheet and fulfill this requirement [in chronological order]: 1.32.206.6, 1.32 206.15, 1.40.206.8 and 3.35.206.13. I told you to choose the one that has at least the same firmware version as your phone or a higher one. From your previous posts I know that your firmware is 2.10.206.x. So which of the four has the same or a newer version?
Sent from my HTC One M9 using XDA Labs
No its not 2.10.206.8 or 2.10.206.180 its 2.10.206.2, as I shown in my first post. Ok I will give it another try, thanks for help.
galusxx said:
No its not 2.10.206.8...
Click to expand...
Click to collapse
That was a typo. I was referring to the backup versions you tried to use and mentioned in the post above mine.
Sent from my HTC One S using XDA Labs
You are my savior, thanks mate for you help
I really don't know where you see that eight mate, but it doesn't matter everything is working now, if you'll ever come in to uk let me know I need to buy you a beer
Good to hear that your problem is solved now. As said before I made a typo. The version 2.10.206.8 doesn't even exist.
Sent from my HTC One S using XDA Labs
Hey all, im not very software proficient, and I need some help in updating my HTC One M9 to Marshmallow.
I recently purchased it from my friend, and apparently, its an International version that is also the developers edition.
It came with TWRP already installed, but I flashed the stock recovery so that I could install the update from HTC itself, But everytime it finishes downloading the update, it gives me an error about it not downloading the correct file. I dont get it, cause its pretty much downloading it by itself, how can it not download the right version.
Is there anyway for me to check and find out exactly what version of the phone this is. Can someone please send me a reliable download link for the official Marshmallow update (already tried using the file on the official HTC website, but apparently had a file size flash limit, this was when using TWRP, not the official recovery) and detailed steps on how to flash it. I have tried multiple ways and have always stumbled upon several errors. Really hoping that nothing is wrong with my phone.
Thank you in advance.
Are you sure it's a developer edition, how do you know this?.
Beamed in by telepathy.
shivadow said:
Are you sure it's a developer edition, how do you know this?.
Beamed in by telepathy.
Click to expand...
Click to collapse
I dont know if it is or not, because when I got the phone, on startup it would give me text in red saying "developers edition, this phone is not for resale of distribution outside blah blah" I dont remember the exact text. But after I flashed the official recovery file, it doesnt give me that anymore.
So lets say its not a developers edition, how do I go about updating it?
Trafalgar747 said:
...on startup it would give me text in red saying "developers edition, this phone is not for resale of distribution...
Click to expand...
Click to collapse
That text is an indication that the bootloader got unlocked and that someone flashed something so that the phone is modified and not stock, anymore. It has nothing to do with the developer edition of the M9. The developer edition is just a US version of the M9 which gets delivered with a factory unlocked bootloader. Therefore chances are high that you flashed the wrong (in other words an incompatible) stock recovery. You need to find out the current firmware version of the phone and restore everything to stock by using a TWRP backup or a RUU. My signature contains a link to my google sheet. There you'll find instructions how to find and flash the correct RUU or how to find and correctly restore a corresponding TWRP backup. If you don't follow the instructions you won't be able to update your phone. Updates for the M9 and every other HTC phone that is newer are different than the ones for older HTC phones. My sheet might not contain a RUU for your firmware or a corresponding backup since I don't support every existing firmware. However you can find additional files in my thread (which is linked in the sheet, too, or can be found by visiting the general section). If no one contributed the files you need here on xda you'll need to use Llabtoofer's RUU service. Be aware that it's not for free.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
That text is an indication that the bootloader got unlocked and that someone flashed something so that the phone is modified and not stock, anymore. It has nothing to do with the developer edition of the M9. The developer edition is just a US version of the M9 which gets delivered with a factory unlocked bootloader. Therefore chances are high that you flashed the wrong (in other words an incompatible) stock recovery. You need to find out the current firmware version of the phone and restore everything to stock by using a TWRP backup or a RUU. My signature contains a link to my google sheet. There you'll find instructions how to find and flash the correct RUU or how to find and correctly restore a corresponding TWRP backup. If you don't follow the instructions you won't be able to update your phone. Updates for the M9 and every other HTC phone that is newer are different than the ones for older HTC phones. My sheet might not contain a RUU for your firmware or a corresponding backup since I don't support every existing firmware. However you can find additional files in my thread (which is linked in the sheet, too, or can be found by visiting the general section). If no one contributed the files you need here on xda you'll need to use Llabtoofer's RUU service. Be aware that it's not for free.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Sorry for sounding so noobish, but how do I find the exact firmware of my phone, I can move forward from there then. If its in about device, what particular detail do I need to keep in mind when finding the exact stock rom for my phone?
Trafalgar747 said:
Sorry for sounding so noobish, but how do I find the exact firmware of my phone, I can move forward from there then. If its in about device, what particular detail do I need to keep in mind when finding the exact stock rom for my phone?
Click to expand...
Click to collapse
It's explained in my sheet. And no, "settings > about" is not (always) the correct place if you want find out your firmware version.
Sent from my HTC One S using XDA Labs
Flippy498 said:
It's explained in my sheet. And no, "settings > about" is not (always) the correct place if you want find out your firmware version.
Sent from my HTC One S using XDA Labs
Click to expand...
Click to collapse
So according to your chart, and my software number which is 1.32.61.15 it would mean that I have the a.bb.61.d - Orange UK (United Kingdom) version? Am I deducing this correctly?
Trafalgar747 said:
So according to your chart, and my software number which is 1.32.61.15 it would mean that I have the a.bb.61.d - Orange UK (United Kingdom) version? Am I deducing this correctly?
Click to expand...
Click to collapse
Correct. You're lucky. There is a RUU for your version on androidruu. Just google for "androidruu" and "HTC M9". You can use the instructions in my sheet for flashing it.
Sent from my HTC One S using XDA Labs
Flippy498 said:
Correct. You're lucky. There is a RUU for your version on androidruu. Just google for "androidruu" and "HTC M9". You can use the instructions in my sheet for flashing it.
Sent from my HTC One S using XDA Labs
Click to expand...
Click to collapse
Just to be sure, if my friend who was previously using this phone, flashed another rom on it with the incorrect version, wouldnt the software number also change? Is there no other way to confirm the version of the phone?
Also, do I use the official TWRP download link in your sheet, is it the correct version for my phone?
Trafalgar747 said:
Just to be sure, if my friend who was previously using this phone, flashed another rom on it with the incorrect version, wouldnt the software number also change? Is there no other way to confirm the version of the phone?
Click to expand...
Click to collapse
The number in settings > about changes with the rom you're flashing. The one located in the download mode only changes if you update the phone with an official OTA or if you set your phone S-OFF via sunshine (which costs 25 bucks) and flash a RUU (or one of sneakyghost's firmware packs) with a different sku afterwards. However if the phone is S-OFF it wouldn't matter which RUU he flashed since with S-OFF almost every RUU can be used with your phone. Only CDMA versions (e.g. Verizon ones) stay incompatible.
Tl;dr: Just flash the 1.32.61.15 one. It's either way compatible with the phone.
Sent from my HTC One S using XDA Labs
Flippy498 said:
The number in settings > about changes with the rom you're flashing. The one located in the download mode only changes if you update the phone with an official OTA or if you set your phone S-OFF via sunshine (which costs 25 bucks) and flash a RUU (or one of sneakyghost's firmware packs) with a different sku afterwards. However if the phone is S-OFF it wouldn't matter which RUU he flashed since with S-OFF almost every RUU can be used with your phone. Only CDMA versions (e.g. Verizon ones) stay incompatible.
Tl;dr: Just flash the 1.32.61.15 one. It's either way compatible with the phone.
Sent from my HTC One S using XDA Labs
Click to expand...
Click to collapse
You are a helpful genius mate, thank you. Just waiting for the download to finish, then will follow your steps. Will let you know how it goes. Thank you again.
Hi all,
Just took the 3.35.401.32 update and now I'd like to grab the stock recovery and RUU for the same version (3.35.401.32). I've checked the usual suspects but they don't seem to have the files, so are they available for download or I have to hold off a little longer until they are?
Cheers all.
I'm pretty sure that the recovery is already available here on xda. However even if it wasn't you could have grabbed it by yourself while creating a backup for that firmware version (and providing it for others afterwards ). There's a guide how to do so in my google sheet. (And that is linked in my signature.)
Unless it's made for a US carrier, every RUU is leaked and not provided by HTC officially. That means that no one knows if or when a RUU for a new firmware version gets available. (E.g. the SKU 708 has only one single RUU for one of the 1.x firmware versions.) Therefore you shouldn't waste your time and wait too long for a RUU but look for other methods that can get you back to stock.
Edit: And here's the link to the recoveries that have been contributed so far.
Sent from my HTC One S using XDA Labs
Thanks for the info Flippy.
Flippy498 said:
I'm pretty sure that the recovery is already available here on xda. However even if it wasn't you could have grabbed it by yourself while creating a backup for that firmware version (and providing it for others afterwards ). There's a guide how to do so in my google sheet. (And that is linked in my signature.)
Unless it's made for a US carrier, every RUU is leaked and not provided by HTC officially. That means that no one knows if or when a RUU for a new firmware version gets available. (E.g. the SKU 708 has only one single RUU for one of the 1.x firmware versions.) Therefore you shouldn't waste your time and wait too long for a RUU but look for other methods that can get you back to stock.
Edit: And here's the link to the recoveries that have been contributed so far.
Sent from my HTC One S using XDA Labs
Click to expand...
Click to collapse
i extracted the file name before updating my device but have no idea about the correct address to be added before
/OTA_HIMA_UHL_M60_SENSE70_MR_HTC_Europe_3.35.401.32-3.35.401.12_release_4872506s7i993jqhhc4rv7.zip
maemow said:
i extracted the file name before updating my device but have no idea about the correct address to be added before
/OTA_HIMA_UHL_M60_SENSE70_MR_HTC_Europe_3.35.401.32-3.35.401.12_release_4872506s7i993jqhhc4rv7.zip
Click to expand...
Click to collapse
That's the OTA not a RUU. Both, recovery and OTA, are already available in my thread.
Sent from my HTC One M9 using XDA Labs
Hello,
I have bought HTC One M9 off Aliexpress.
I bought it as developer version. When it came I started OTA upgrade. It downloads and then it says update cannot be performed because of modified system.
I cant even use RUU to get it working, I receive error 132. While chatting to HTC support their run my IMEI by their system. It came back as T-Mobile (US) version. Even though on back of my phone is engraved -
Model: OPJA110 which should mean it is developer version.
On my download mode it states: S-on, official system and locked bootloader.
Can anyone give me some tips how to get the newest system installed?
I have been trying for past 2 days without any luck to figure it out.
Any help is appreciate.
EDIT: Forgot CID:11111111 MID: 0PJA11000
Thank you very much.
Please read the ReadMe thread. It'll explain the causes of your issues and contains the needed files and instructions for fixing it. (C.f. the conversion guide, the RUU and the OTA section)
The most important infos: OTAs aren't installable while the phone is using the SuperCID and firmware 4.x RUUs aren't flashable on phones with firmware 3.x or lower due to new encryption keys.
Sent from my HTC One M9 using XDA Labs
Thanks for your time.
Flippy498 said:
Please read the ReadMe thread. It'll explain the causes of your issues and contains the needed files and instructions for fixing it. (C.f. the conversion guide, the RUU and the OTA section)
The most important infos: OTAs aren't installable while the phone is using the SuperCID and firmware 4.x RUUs aren't flashable on phones with firmware 3.x or lower due to new encryption keys.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
I have read ReadMe.
So that means I need to S-OFF my phone using SunShine (other oprions?)
Then changing CID to BS_US001 (because Im running .617. system)
Then I can flash RUU (3.35.617.31)
And after that I can use OTA updates?
Do I need to unlock bootloader through HTCdev or is enough to check OEM Unlocking under developer options?
Thank you again for your time.
Oh, I missed that you're S-ON. Follow the unlocking/rooting guide in the same thread.
If you're lucky the previous owner used Sunshine, as well, so that you don't have to pay, again. (The license is saved on their servers and gets linked to the device.) The alternatives to Sunshine are a Java card, an XTC clip or similar tools which are way more expensive.
It doesn't matter which of the CIDs that belong to SKU 617 you use. They both work fine.
Alternatively, you could send the device back to the seller and ask for a refund. He obviously modified the phone and didn't restore the phone to a stock state properly before he sold it. The phone definetly was S-OFF in the past since no HTC phone gets shipped with the SuperCID. And if the IMEI belongs to a T-Mobile M9 according to HTC then the MID got changed with the help of S-OFF, as well. The backside can actually get replaced, too, if you know how to do it.
After you restored a CID that corresponds to your SKU you should be able to receive OTAs, again. Just for safety reasons I'd flash a 3.x RUU, as well, if I were you. The differences between the GSM versions of the M9 are so minor that you can convert the phone from one version to another. Therefore, you don't need to use the T-Mobile firmware and can stick with the dev one if you want.
Flippy498 said:
Oh, I missed that you're S-ON. Follow the unlocking/rooting guide in the same thread.
If you're lucky the previous owner used Sunshine, as well, so that you don't have to pay, again. (The license is saved on their servers and gets linked to the device.)
It doesn't matter which of the CIDs that belong to SKU 617 you use. They both work fine.
Alternatively, you could send the device back to the seller and ask for a refund. He obviously modified the phone and didn't restore the phone to a stock state properly before he sold it. The phone definetly was S-OFF in the past since no HTC phone gets shipped with the SuperCID. And if the IMEI belongs to a T-Mobile M9 according to HTC then the MID got changed with the help of S-OFF, as well. The backside can actually get replaced, too, if you know how to do it.
After you restored a CID that corresponds to your SKU you should be able to receive OTAs, again. Just for safety reasons I'd flash a 3.x RUU, as well, if I were you. The differences between the GSM versions of the M9 are so minor that you can convert the phone from one version to another. Therefore, you don't need to use the T-Mobile firmware and can stick with the dev one if you want.
Click to expand...
Click to collapse
Ok, Im gona pay that 25 bucks, it doesnt really matter.
So, I should start with unlocking bootloader via HTCdev.
After that I need to use SunShine.
Changing CID.
Flashing 3.x RUU.
And then doing OTA.
Is that all correct?
And should I install TWRP or stay on stock recovery after unlocking bootloader?
Really appreciate your time.
Correct.
Just follow the guides in the ReadMe thread starting from this post till the end of the conversion guide. (Theoretically, you can skip the backup part and save some time since you should be able to use the 3.x RUU even with the SuperCID on your phone.)
Flippy498 said:
Correct.
Just follow the guides in the ReadMe thread starting from this post till the end of the conversion guide. (Theoretically, you can skip the backup part and save some time since you should be able to use the 3.x RUU even with the SuperCID on your phone.)
Click to expand...
Click to collapse
Thanks,
is there a point in TWRP backup? Wont it stop OTA updates? On my other phone (Ulefone Metal) It is not possible to get OTA with custom recovery.
It actually is possible on the M9 and newer HTC phones as long as the system partition doesn't get modified, beforehand. (Further info can be found in the OTA section of the ReadMe thread.)
However, flashing a RUU restores everything on the phone back to stock (including the recovery). That's why I suggested flashing one after changing the CID.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
It actually is possible on the M9 and newer HTC phones as long as the system partition doesn't get modified, beforehand. (Further info can be found in the OTA section of the ReadMe thread.)
However, flashing a RUU restores everything on the phone back to stock (including the recovery). That's why I suggested flashing one after changing the CID.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Thank you, I did as I said.
After flashing 3.x RUU OTA was successful.
That updated my system to: 4.16.617.6.
After that I continued by flashing latest RUU (4.30.617.12).
Everything went well. Until this point. When I booted the device I got to choose language. But there are just few (20 or so) available.
Unfortunately no Czech which I want. On previous version (4.16.617.6) there was huge list to choose from, including Czech.
Im still using 617 edition.
Where is the problem? Is here a way to get Czech lang. working again?
One again thank you for your time and effort
HTC probably removed the languages from the selection. Don't ask me why. I have no clue.
You could try setting up the phone in English and then switching to Czech via the app MoreLocal2. There's a thread about the app somewhere hidden on xda (sorry, I don't have a direct link at hand). You should be able to find it via google.
Sent from my HTC One M9 using XDA Labs
I've gone through the (extremely confusing) readme thread several times but would appreciate a concrete answer on dev edition conversion.
My phone is hima_ulatt / firmware v3.38.502.12 / OPJA11000 / CWS_001.
So my question is, once i:
unlock bootloader > s-off > write cid BS_US001,
can i install ruu 4.30.617.12 or would i have to stay within 3.xx.617.xx versions?
jbonetwo said:
I've gone through the (extremely confusing) readme thread several times but would appreciate a concrete answer on dev edition conversion.
My phone is hima_ulatt / firmware v3.38.502.12 / OPJA11000 / CWS_001.
So my question is, once i:
unlock bootloader > s-off > write cid BS_US001,
can i install ruu 4.30.617.12 or would i have to stay within 3.xx.617.xx versions?
Click to expand...
Click to collapse
As far as I know you can't install a 4.x Ruu on 3.x firmware.
The encryption is different.
bubba1601 said:
As far as I know you can't install a 4.x Ruu on 3.x firmware.
The encryption is different.
Click to expand...
Click to collapse
Is there no way to update to the 4.xx versions then? The AT&T software update won't let me upgrade at all (says no updates found).
jbonetwo said:
Is there no way to update to the 4.xx versions then? The AT&T software update won't let me upgrade at all (says no updates found).
Click to expand...
Click to collapse
Download a 4.x based rom, there are several in the rom thread including the latest development rom.
They are stock ROMs that you can flash through twrp.
This one I've used and had no issues with.
https://forum.xda-developers.com/on...m9-4-14-617-6-stock-root-twrp-backup-t3518149
But if you are locked to ATT (unlike me because I'm in Europe and the European M9 is a GSM version.
You might want to try this version (ATT)
https://forum.xda-developers.com/one-m9/development/rom-stock-nougat-4-23-617-1-unlocked-t3553470
bubba1601 said:
Download a 4.x based rom, there are several in the rom thread including the latest development rom.
They are stock ROMs that you can flash through twrp.
This one I've used and had no issues with.
https://forum.xda-developers.com/on...m9-4-14-617-6-stock-root-twrp-backup-t3518149
But if you are locked to ATT (unlike me because I'm in Europe and the European M9 is a GSM version.
You might want to try this version (ATT)
https://forum.xda-developers.com/one-m9/development/rom-stock-nougat-4-23-617-1-unlocked-t3553470
Click to expand...
Click to collapse
Thank you!!
Please elaborate a bit further which part of the ReadMe thread confuses you. It's meant to be a helpful resource and if it's confusing at some point then it might need to get overhauled.
Flashing a rom won't update the firmware. Therefore, the linked roms won't help you much. (C.f. the article that is linked as "the difference between rom and firmware" in the further reading section of the ReadMe thread.)
You need to update the phone with an unencrypted firmware pack (that means an OTA or one of Sneakyghost's firmware packs). As already explained in this thread, RUUs with firmware 4.x use new encryption keys and therefore can't be used for updating from firmware 3.x. In addition, AT&T won't let you install OTAs on their branded phones if you aren't using one of their sim cards.
Either you convert to the 3.x version of the dev firmware and install the available OTAs afterwards or you need to flash a 4.x AT&T firmware pack from Sneakyghost's thread before you convert if you want to directly use the latest dev edition RUU.
Sent from my HTC One M9 using XDA Labs
I got confused too. It's confusing because the paragraphs digress and don't just follow the basic procedures. Probably because the information is necessary but not formatted into idiot speak.. idiot speak is what i needed.
So i thought "fk it my phone is dying anyway so how bad can it get"?.
If you're changing the cid and mid via fastboot do it first and get the firmware.zip of the region you want, at the phones CURRENT firmware level.
Flash the zip version of the firmware from external sdcard. To do that you need to
S-OFF: DONT NEED TO CHANGE ANYTHING.
S-ON: LOCK BOOTLOADER?? (CLARIFY)/CHANGE NOTHING?
rename the firmware.zip* file to whatever the filename asks for at the bottom of download mode (voldown+power), eg 0PJA***.ZIP.
copy it to the external Sdcard (not in a folder, just on its own), reboot phone to download mode, follow prompts.
THE PHONE WILL REBOOT MANY TIMES AND SHOULD TAKE AROUND 30 MINS TO 1 HOUR TO COMPLETE. DO NOT TOUCH THE PHONE. DO NOT TURN IT OFF. DO NOT UNPLUG IT FROM THE CHARGER. Leave it alone!!.
Once that completes you can take the ota.
Well, not everyone owns an SD card and there are other methods for flashing RUUs. That's why the RUU section describes all methods and the conversion guide only has a link to the RUU section. (The steps you describe are all mentioned in the guide for the SD card method.) This way users can choose which method they want to use. And describing all methods in both posts doesn't seem to make sense in my eyes, either.
The infos above the instructions of each post are actually needed for understanding why things are how they are if you've never owned an HTC device before. I can add a title "general info" for making clearer that the posts don't start with instructions, though.
The fact that you don't need to re-lock or lock the bootloader (neither for RUUs nor for OTAs) is e.g. explained in these additional infos. It's not mentioned in the instructions since that info itself is not an instruction.
Btw, a RUU reboots the phone only once and the flash shouldn't take longer than a couple of minutes. OTAs on the other hand can take up to am hour and reboot the phone several times.
Sent from my HTC One M9 using XDA Labs
Yes you are correct as always flippy. The reflash back to stock takes minutes while ota takes an age. Forgot that bit.
You also redefined what i said.. the posts digress to cover all eventualities but it is overwhelming to eejits like myself.
If it was laid out basic THEN cover the eventualities it'd be easier to follow. The english can be a tad broken too, which confuses the fk out of native English speakers like myself.
My post is just the basic. Nothing more, nothing less. If you bork your phone with my instruction it will be a hardware or user fault.
The only thing I'm not sure of, because my phone is s-off, is whether or not the bootloader must be locked or relocked with s-on. Otherwise with s-off they dont matter.
Don't get me wrong, I'm not saying you're feeding false info, I'm just saying that non native english speakers seem to have better results following your instructions better than native speakers, for some reason..
Flippy498 said:
Please elaborate a bit further which part of the ReadMe thread confuses you. It's meant to be a helpful resource and if it's confusing at some point then it might need to get overhauled.
Click to expand...
Click to collapse
Thanks for the info @Flippy498. I'll be re-reading everything thoroughly before attempting anything as i don't want to end up with a brick.
The readme is indeed confusing. It captures the evolution of the m9 since fw 1.xx and the corresponding changes to modding procedures. While this makes for a great catalogue of all info, even a seasoned flash-o-phile would find it difficult to navigate the veritable minefield of do's and don't's.
I'd love to redo the logic of the thread myself but don't know enough about this device yet. but perhaps something that determines one's fw/mid/cid through fastboot first, followed by targeted instructions for achieving different goals based on those differences would be much more legible. (e.g. if fw v 3.xx, do this to unlock but warning about flashing 4.xx). As it stands, coming from v 3.xx, one has to read several disjointed notes peppered around the thread only some of which are relevant and this only adds to the confusion via information overload.
If you have s-off youre good to go in any circumstances. Just check the os that it is on and return it to stock of that version os OR
If you change the cid and mid just flash to stock of THAT version AND the region you change to. Like changing from 401 to 617 you flash the 617 because it matches the cid and mid you changed to. It must still match the os version the phone is on ie marshmallow 3.35.xxx.xx, making it the 3.35.617.xx firmware you'd be looking to flash to get stock marshmallow..
Then you just take the ota updates as far as you like.
I flashed 2 s-off phones back to stock in the last week in one sitting and it was easy, just as I explained.
It's just bootloader in s-on conditions that I personally don't know and that throws me a bit. I don't know if it's a requirement or not. I'd highly recommend buying s-off via sunshine in all cases but otherwise flippy would have to answer a simple yes or no to "bootloader locked for s-on flashing?" or you'd have to dredge it up on a search site. The other option is bite the bullet and flash anyway hoping it boots you out with an error.
shivadow said:
flippy would have to answer a simple yes or no to "bootloader locked for s-on flashing?"
Click to expand...
Click to collapse
It doesn't matter whether the bootloader is locked, re-locked or unlocked.
Sent from my HTC One M9 using XDA Labs
shivadow said:
If you have s-off youre good to go in any circumstances. Just check the os that it is on and return it to stock of that version os OR
Click to expand...
Click to collapse
Your method worked great! changed cid & mid to dev edition, flashed dev edition and then used 'software update' to catch up to latest version. couldn't be easier, thanks!
Now for that obnoxious red text...
I take no credit for anything. All I did was make the process clearer. Glad you're sorted!.