Related
Sorry, me again!
I needed to re-lock and ‘stockify’ my HTC M8 today for a few reasons. It ended up taking me 4 hours, and I still have no idea if it’s ‘back’ to the way it was before I rooted it. Before you carry on reading, please know I’m fully aware any lack of understanding is my fault, and perhaps I should have realised that compared to the N4s blissfully easy steps, the HTC was a massive can of worms. However, I’m going to ask the below anyway, so hopefully someone is friendly and helpful enough to aid me in my quest for enlightenment of android stuff without me having to spend more hours searching than actually reading useful stuff…
So coming from a Nexus 4, where the guide is super simple:
http://forums.androidcentral.com/ne...3923-guide-nexus-4-factory-image-restore.html
It turned out to be SERIOUSLY complicated. I’ve put down a ‘typical’ guide below, and put my questions about each step in bold. Sorry if it seems like I’m just complaining and being trite, but I’d like to know if A) I’ve missed a far easier way of doing this and if not B) is it just me that seems to have a massive amount of issues?
1. Made sure your device is S-Off. If not, download firewater and S-Off your device.
Assume this is just a thing that some phones have and some don’t?
2. Restore a nandroid of the stock Sense ROM, or find a stock ROM to flash. You'll have to dig around; I used a nandroid.
WHY? Is there no such thing as downloadable factory images for HTC One M8s? Also, where’s the step that says ‘run the commands fast boot erase user data, fast boot erase cache’ etc.?
3. Flash SuperSU.zip in recovery on top of the stock Sense ROM. You can find the SuperSU.zip here: http://download.chainfire.eu/396/SuperSU
Fair enough… still an another extra step compared to N4.
4. Use fast boot to flash the stock firmware zip to your device based on CID (this includes the stock recovery)
-This took SO MUCH EFFORT. Turns out I had to Super CID so that one of the recovery zips worked, because I was getting “FAILED (remote: 42 custom id check fail)” - and I’m now paranoid because I have no idea how important it is to get the correct CID-numbered ‘stock firmware’ etc. The ‘stock firmware’ zips seem to contain boot, radios, recovery .imgs, and with about 4 billion versions of the M8 apparently existing, could I have flashed a wrong boot or radio or something? ARE they even different per CID? Then I changed the CID back to O2___001 in case I need to take it in for warranty repairs, but is that trackable? Would someone know that I’ve messed around with the CID? Could someone going to look at my Nexus and be like “Oh this radio seems to be the one we’d expect on a HTC_001, NOT an O2___001 CID device, they must have tampered with it”.
—OH, and I had to boot into RUU mode as well, which apparently no one felt like explaining what the hell that’s for. So I’ve got and HBoot, a Fastboot, and RUU mode, which no clear way of knowing what to flash where…??
—-ALSO there was a HELL of a lot of faffing by people throwing around CID, MID, Verizon, Sprint, and comments like this doesn’t work on this AT&T model but will only work on non branded eu models with a flag attached to the speaker with an SSID of “600TZL” and a it MUST have a holographic projector otherwise your CID must equal the square root of the MID so that the factory image will know which ID your phone carrier provides through an inter web”.
5. Boot back up into sense, and follow this guide to remove the tampered banner in recovery. http://forum.xda-developers.com/show....php?t=2708565
-Is this just removing a banner? or is it ‘you’ve removed the banner from a visual point of view only, but if they actually look into it it will still appeared ‘tampered’.
6. Follow this guide to lock your boot loader and make it say **LOCKED** instead of **RELOCKED**. http://forum.xda-developers.com/show....php?t=2708571
-So ‘fast boot OEM lock’ doesn’t work on HTCs then- is that an N4 thing? Why all that complicated cmd line stuff? And on a side note, why is it that when referring to re-locking a N4 people call it just that- locking. But with an HTC people on XDA seem to say ‘to make the banner say locked’ as if its not actually locking it, just changing a bit of writing on the boot loader.
7. Boot your device back up, and open SuperSU. Go into settings and find the "full unroot" option and run that. Reboot your device like it suggests.
Does running the unroot zip (can’t find the thread) work? So I can make it appear like the HTC is brand new out of the box? Rather than having to go through the ‘first setup’ screen?
Other question: people seem to keep yammering on about modded RUUs, is there one? is there a couple? (i.e. should I view it a bit like TWRP and CWM- there’s others but there’s one everyone really uses). And if I ‘flash’ a modded RUU, again, is there an easily accessible stock one?
It's really not that complicated! I think the problem is comparing it to a Nexus 4 which is designed to be easily unlocked and locked, due to being a more developer orientated device.
An RUU is a stock image (like the Nexus images) and a modded one would just have the CID/MID requirement removed or something so it can be used on more phones. It would still be the stock, untampered image.
Also, the whole CID/MID thing is only applicable to American devices which vary between GSM and CDMA radios. ANY international modem will work in Europe and you will never find the wrong one.
S-Off is like unlocking the bootloader on a Nexus device except that in this case, its an extra step after unlocking the bootloader in order to be able to modify every partition and flash unsupported firmware in OEM mode. Every consumer phone is initially shipped S-On.
Thanks very much Veryone's v. helpful around here. Just a few more questions based on what you've said:
Matt said:
Also, the whole CID/MID thing is only applicable to American devices which vary between GSM and CDMA radios. ANY international modem will work in Europe and you will never find the wrong one.
Click to expand...
Click to collapse
Why did I have to Super-CID to install the stock recovery? And did I do the right thing by going back to my carrier CID afterwards?
Matt said:
S-Off is like unlocking the bootloader on a Nexus device except that in this case, its an extra step after unlocking the bootloader in order to be able to modify every partition and flash unsupported firmware in OEM mode. Every consumer phone is initially shipped S-On.
Click to expand...
Click to collapse
Although I've read in quite a few places I shouldn't have to S-On to take it in for a warranty repair, because some arrive to people S-off and they can't prove that you did it? Is that right?
Thank you for the step-by-step list. I am in the process of restoring my phone and all the guides say to look for "version-main", but that line is empty for me. What other information can I use to determine what recovery image to flash. Also the reason I want to go back to unrooted is so I can recieve OTA updates.
legolator said:
Thank you for the step-by-step list. I am in the process of restoring my phone and all the guides say to look for "version-main", but that line is empty for me. What other information can I use to determine what recovery image to flash. Also the reason I want to go back to unrooted is so I can recieve OTA updates.
Click to expand...
Click to collapse
this also happened to me- just another thing to confuse....
Can you not receive OTA updates if you're rooted? I thought it was just if you were running a different ROM?
tmorterlaing said:
this also happened to me- just another thing to confuse....
Can you not receive OTA updates if you're rooted? I thought it was just if you were running a different ROM?
Click to expand...
Click to collapse
I was under the impression that flashing a custom recovery removes the ability for the phone to install OTA updates. But I could of course be wrong about that.
Hello
My htc one m8 is the Asian version (HTC__044) , upon using getvar all, I noticed that my version-main was missing along with the os in hboot. If I were to flash a firmware, would I need to relock the bootloader? Would I lose my data on locking the bootloader? Also, im on base .401 , would I directly be able to flash a .707?
Thanks in advance.
wasdapple said:
If I were to flash a firmware, would I need to relock the bootloader?
Click to expand...
Click to collapse
If s-on, yes. Otherwise if s-off, no.
Also, be aware that with s-on you can only flash a firmware that is HTC signed/encrypted. Some are not, and require s-off.
wasdapple said:
Would I lose my data on locking the bootloader?
Click to expand...
Click to collapse
Yes.
wasdapple said:
Also, im on base .401 , would I directly be able to flash a .707?
Click to expand...
Click to collapse
How are you determining 401? From what I'm seeing, the stock software/firmware for your CID should be 707.
You should be able to flash 707 firmware (assume you want to update to Lollipop) on your version, provided the previously mentioned requirements are met.
redpoint73 said:
If s-on, yes. Otherwise if s-off, no.
Also, be aware that with s-on you can only flash a firmware that is HTC signed/encrypted. Some are not, and require s-off.
Yes.
How are you determining 401? From what I'm seeing, the stock software/firmware for your CID should be 707.
You should be able to flash 707 firmware (assume you want to update to Lollipop) on your version, provided the previously mentioned requirements are met.
Click to expand...
Click to collapse
Thanks for replying. I believe it may have been the rom ive installed that changed my firmware, along with the fact it writes .401 on my software information page. Yes the default firmware should be .707 which I believe is also the main cause of my inability to connect to 4g in my area.
So assuming I find a signed firmware for .707 I would simply be able to flash it on the .401? Or would I have to still relock my bootloader.
Also, would the empty os/ version-main be a problem and if so how do I fix it.
Thanks for replying as you've also helped me a great deal the previous time.
wasdapple said:
I believe it may have been the rom ive installed that changed my firmware, along with the fact it writes .401 on my software information page.
Click to expand...
Click to collapse
Flashing a ROM will not change your firmware. It does change software number, so if that is where you are getting 401 from, that is normal. Software number is just the base of your current ROM, not your firmware number.
Your firmware number is indicated on your bootloader screen under "OS" and also as "main version" when doing getvar all.
wasdapple said:
So assuming I find a signed firmware for .707 I would simply be able to flash it on the .401? Or would I have to still relock my bootloader.
Click to expand...
Click to collapse
Are you s-on or s-off?
If still s-on, there is no way you could have ever flashed a 401 firmware on your phone. I still think you are confused between software and firmware numbers, and I don't guess that you ever flashed a 401 firmware.
If you are s-on, I still think you are on 707 firmware, and there is some other factor causing your 4G problem.
Yes, you need to relock your bootloader to flash 707 firmware while s-on. If you are s-off, you don't need to relock the bootloader.
wasdapple said:
Also, would the empty os/ version-main be a problem and if so how do I fix it.
Click to expand...
Click to collapse
It shouldn't be a problem. It will be fixed if you flash a firmware.
This bug was caused by older versions of TWRP. If you flash a current version of TWRP after flashing firmware, the problem should not re-occur.
---------- Post added at 10:19 AM ---------- Previous post was at 10:17 AM ----------
wasdapple said:
Thanks for replying as you've also helped me a great deal the previous time.
Click to expand...
Click to collapse
We always like repeat customers, and satisfied ones.
So is it possible that I am actually on 707 but my rom is making it show 401? Im terribly sorry for my lack of understanding of this whole situation.
Would using the twrp app on the play store update twrp? It should fix the empty main-version ?
wasdapple said:
So is it possible that I am actually on 707 but my rom is making it show 401? Im terribly sorry for my lack of understanding of this whole situation.
Click to expand...
Click to collapse
I know in the past, folks have often used the word "firmware" to mean the same as the ROM. But you should probably erase that notion from your mind. On this device, the word "firmware" is used specifically to partitions that are not flashed when you flash a ROM, and include hboot, radio, WiFi, Bluetooth, and others.
Yes, your firmware may still be 707 (which can normally be found as OS number on hboot screen, or main version when doing getvar all); while your software (ROM) which is shown in Settings>About>Software information can be 401. Firmware and ROM are 2 completely different things.
I've asked twice now, are you s-on or s-off?
wasdapple said:
Would using the twrp app on the play store update twrp? It should fix the empty main-version ?
Click to expand...
Click to collapse
TWRP Manager app will update TWRP, yes.
You can also just download the latest version and flash with fastboot, which is my preferred method: https://twrp.me/devices/htconem8gsm.html
However, this alone won't fix the issue of main version missing, I don't believe. It will only stop if from re-occurring. But the only way to get the main version back is to flash a firmware. After that, having an updated TWRP will stop if from main version displaying "blank" again. If you use an old TWRP, it will blank out the main version again.
Get it?
I'm sorry I kept forgetting to reply to that, I am actually s-on.
So for instance I want to be back on 707 I should just revert to rooted stock?
wasdapple said:
I'm sorry I kept forgetting to reply to that, I am actually s-on.
Click to expand...
Click to collapse
Than its simply impossible for you to ever have flashed a 401 firmware. Some of the firmware partitions (hboot, radio) are write protected with s-on, and can only be flashed with your CID version firmware (707).
wasdapple said:
So for instance I want to be back on 707 I should just revert to rooted stock?
Click to expand...
Click to collapse
Yes, rooted or unrooted should be fine.
But you will want to make sure your firmware and software versions match up. What are your hboot and radio numbers? Do you remember if you were on Lollipop before unlocking the bootloader?
My hboot would be 3.19.0.0000 and my radio is 1.25.21331147A1.06G
Yep I was on lollipop before unlocking my bootloader.
wasdapple said:
My hboot would be 3.19.0.0000 and my radio is 1.25.21331147A1.06G
Yep I was on lollipop before unlocking my bootloader.
Click to expand...
Click to collapse
You can get the stock 4.19.707.2 nandrioid here (Post #2): http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Keep in mind, this is a TWRP "nandroid" backup, not a flashable ROM zip. So follow the directions carefully to restore this stock nandroid.
Also note that this is the stock ROM, not the firmware.
Would I get back my 707 if I flashed this instead http://forum.xda-developers.com/htc...-sd-14-19-707-21st-android-5-0-sense-t3010391 ?
im seeing an Asian wwe base and it is 707.
Also I wouldn't be able to dirty flash a completely different rom right?
wasdapple said:
Would I get back my 707 if I flashed this instead http://forum.xda-developers.com/htc...-sd-14-19-707-21st-android-5-0-sense-t3010391 ?
Click to expand...
Click to collapse
Not sure what you mean by "get back my 707", and you need to explain more clearly.
If the intent is to return to 707 firmware, its not needed, I'm confidant you already are on current 707 firmware. And flashing a ROM does not change your firmware (as I've already explained multiple times).
If the intent is to make the main version appear again, flashing a ROM won't do that either. As mentioned, you can only make that reappear by flashing a firmware.zip (not a ROM.zip).
If the intent is to just return to a 707 ROM base, then yes the ROM you linked will do that. But the only reason I see for you to do so, is to see if it helps your network issue. Using ROMs of other bases will not normally affect network service (as long as your carrier's APN is correct). And I've already linked you to stock 707 nandroid, which is probably the best baseline to troubleshoot from. Or are you not comfortable with the nandroid restore process?
Again, you haven't really explained what you are trying to accompish; so its hard to answer the question.
wasdapple said:
Also I wouldn't be able to dirty flash a completely different rom right?
Click to expand...
Click to collapse
If the ROM is a similar enough base, it might be possible to dirty flash. But its not recommended, and still possible to have various severe bugs, or not even boot. Therefore, full wipe is normally recommended when moving between different ROMs (and often even major updates of the "same" ROM).
Any person flashing ROMs should know how to backup and restore their personal data (using Titanium Backup and/or other means) when moving between ROMs.
Sorry for my vagueness in my previous post. Currently in my phone settings, the build number is 4.26.401. , which is the base of my current rom? So supposedly if I flash an Asian wwe would I get my software base back to a 707 as in the link.
Also, you mentioned for me to flash my firmware as per my cid, which could be found in most firmware dumps? Would be it be possible to link one to me? And if I am in fact on a 707, do I still flash 707 firmware?
The reason why I an unwilling to go through with nandroid is that I am not exactly looking to restore to stock, I like to have customs roms and the root capabilities. My ultimate objective is to get back to 707, or at least get it to appear on my software information screen. To my knowledge, 401 is for the European countries and the basebands for 4g LTE is different, thus I am unable to find out why if I am s-on with my firmware and radio intact I could not connect to my local 4g LTE, and to my point of view, only through flashing a firmware affect everything.
Im sorry for this large amount questions and extremely grateful you have taken the time to tend to it. I sincerely apologise if I seem to keep insisting that my firmware has changed despite your reminders.
I've actually been trying to update the firmware on my M8 today as well, but when I go to "flashboot flash zip firmware.zip" I am returned the message "not enough space."
I've cleared the cache successfully, and that didn't open up enough space. I tried to delete userdata, but it wouldn't let me do it remotely.
So I'm a little confused as to my next move here...
and I've relocked my phone and s-on.
wasdapple said:
Sorry for my vagueness in my previous post. Currently in my phone settings, the build number is 4.26.401. , which is the base of my current rom? So supposedly if I flash an Asian wwe would I get my software base back to a 707 as in the link.
Also, you mentioned for me to flash my firmware as per my cid, which could be found in most firmware dumps? Would be it be possible to link one to me? And if I am in fact on a 707, do I still flash 707 firmware?
The reason why I an unwilling to go through with nandroid is that I am not exactly looking to restore to stock, I like to have customs roms and the root capabilities. My ultimate objective is to get back to 707, or at least get it to appear on my software information screen. To my knowledge, 401 is for the European countries and the basebands for 4g LTE is different, thus I am unable to find out why if I am s-on with my firmware and radio intact I could not connect to my local 4g LTE, and to my point of view, only through flashing a firmware affect everything.
Im sorry for this large amount questions and extremely grateful you have taken the time to tend to it. I sincerely apologise if I seem to keep insisting that my firmware has changed despite your reminders.
Click to expand...
Click to collapse
Yes. You will get your software number back if you flash a 707 based ROM, such as stock.
So, here we go.
Download this 4.19.707.2 RUU onto your PC
When the download is finished, plug your phone into your PC, double click on the downloaded file, and follow the prompts. This will update you to Lollipop and you will be on the stock ROM again.
Since you are S-On, you will first need to relock the bootloader.
In fastboot (obviously) fastboot oem lock before you proceed with this.
Also, THIS WILL WIPE YOUR PHONE, so be sure to backup anything that is important to you.
Is the ruu rooted, or purely stock pre-root?
Kindrex said:
I've actually been trying to update the firmware on my M8 today as well, but when I go to "flashboot flash zip firmware.zip" I am returned the message "not enough space."
I've cleared the cache successfully, and that didn't open up enough space. I tried to delete userdata, but it wouldn't let me do it remotely.
So I'm a little confused as to my next move here...
and I've relocked my phone and s-on.
Click to expand...
Click to collapse
What is your current OS number on the bootloader screen, and what firmware are you trying to flash?
---------- Post added at 10:53 AM ---------- Previous post was at 10:21 AM ----------
wasdapple said:
Sorry for my vagueness in my previous post. Currently in my phone settings, the build number is 4.26.401. , which is the base of my current rom? So supposedly if I flash an Asian wwe would I get my software base back to a 707 as in the link.
The reason why I an unwilling to go through with nandroid is that I am not exactly looking to restore to stock, I like to have customs roms and the root capabilities. My ultimate objective is to get back to 707, or at least get it to appear on my software information screen. To my knowledge, 401 is for the European countries and the basebands for 4g LTE is different, thus I am unable to find out why if I am s-on with my firmware and radio intact I could not connect to my local 4g LTE, and to my point of view, only through flashing a firmware affect everything.
Im sorry for this large amount questions and extremely grateful you have taken the time to tend to it. I sincerely apologise if I seem to keep insisting that my firmware has changed despite your reminders.
Click to expand...
Click to collapse
If the intent it to return to 707 based ROM to see if that helps your 4G issue, then yes the custom ROM you previously posted will do that. It will also make 707 appear for software number in the phone Settings.
wasdapple said:
Also, you mentioned for me to flash my firmware as per my cid, which could be found in most firmware dumps? Would be it be possible to link one to me? And if I am in fact on a 707, do I still flash 707 firmware?
Click to expand...
Click to collapse
I was more talking "if" you can find the 4.16.707 firmware. The main firmware collection I refer to doesn't have 4.16.707, just old 707 firmwares (which you don't want)]: http://forum.xda-developers.com/showthread.php?t=2696282
If the firmware can't be found, the RUU listed by xunxholyx is your best bet if you really want to flash the 707 firmware. But I really don't think this is needed. As I'm nearly 100% sure you are already on the current 707 firmware, and the only benefit of flashing the 707 firmware (by RUU) is to get the OS number to appear again on the bootloader screen and on getvar all (which is really not that important).
On the other hand, RUU to full stock may be a good way to troubleshoot your 4G issue, especially if flashing the 707 based custom ROM still doesn't fix the issue. RUU is not just a stock ROM, but a complete factory image, complete with bootloader, radio, etc.
---------- Post added at 11:08 AM ---------- Previous post was at 10:53 AM ----------
wasdapple said:
Is the ruu rooted, or purely stock pre-root?
Click to expand...
Click to collapse
It appears to be 100% official and stock (unrooted). It will also wipe your phone.
---------- Post added at 11:09 AM ---------- Previous post was at 11:08 AM ----------
xunholyx said:
Yes. You will get your software number back if you flash a 707 based ROM, such as stock.
So, here we go.
Download this 4.19.707.2 RUU onto your PC
Click to expand...
Click to collapse
Nice find. I didn't know Asia version had any RUUs.
redpoint73 said:
Nice find. I didn't know Asia version had any RUUs.
Click to expand...
Click to collapse
Yeah, they are hard to come by. I was helping a user here six to eight weeks ago, and told him I didn't know of any Asia RUUs. He came back the next day replying that he found one, so I asked for the link and gave it to Sneakyghost and Alex (from AFH) to upload to androidruu.com
They have a few that aren't common there, and are always looking for more hard to find ones. If you come across one, you could PM me or Sneakyghost to have it added. Always nice to have a good RUU repository to go to.
Hey everyone. I'm having a similar issue, and I don't want to start a new thread, so I'm going to add on to this one.
I've been on AOKP since it was released for this phone, so I've missed out on some OTA updates. Every time I try to flash a Lollipop ROM I get all these weird issues (WiFi not working, systemUI crashes, etc.), and after reading a few threads, I believe its an issue with the firmware.
I tried going back to stock, but the only Nandroid backup I could find for my phone isn't compatible with my firmware (WiFi refuses to work, only data). So I was wondering what else I could do to update the firmware. Reading this thread, it looks like the RUU is another method, but I'm not too sure how to get started with that, or which one to use, as my OS in the Bootloader and my version-main is blank.
Any advice is appreciated, please let me know if you need more info.
My Device:
Rooted
TWRP 2.8.7.0
S-Off
CID-TELUS001
watidk said:
I tried going back to stock, but the only Nandroid backup I could find for my phone isn't compatible with my firmware (WiFi refuses to work, only data). So I was wondering what else I could do to update the firmware. Reading this thread, it looks like the RUU is another method, but I'm not too sure how to get started with that, or which one to use, as my OS in the Bootloader and my version-main is blank.
Any advice is appreciated, please let me know if you need more info.
My Device:
Rooted
TWRP 2.8.7.0
S-Off
CID-TELUS001
Click to expand...
Click to collapse
What are your hboot and radio numbers?
I am using AT & T HTC M8 S - OFF super CID. Can I install this recovery ?
[ROM][5.1] 9/17/2015-Lollipop Stock Rooted Google Play Edition LMY47O.H9
HTML:
http://forum.xda-developers.com/showthread.php?t=2706441
thanks alot!!!!! :good::good::good:
That's not a recovery, it's a ROM !
Mr Hofs said:
That's not a recovery, it's a ROM !
Click to expand...
Click to collapse
yes. i'm sorry but can i use it??
The short answer is yes. However, the longer answer is yes, but you need to think carefully about this before pulling the trigger.
Some people repartition their phones to fully convert to the GPE version, but I don't recommend this unless you are either certain you want a GPE ROM or are highly skilled in this area. In your case, since you aren't certain, I would install without altering your partitions. From what I read in the first post, it appears this ROM simply rewrites your existing Sense partitions with GPE code, so it should be perfectly safe.
Also, make sure you note the required firmware version. AT&T has released a Lollipop version of their ROM, so if you aren't sure, you might consider running their RUU as a way to ensure you have compatible firmware. (since you are S-off, you can also use the Developer Edition RUU, but since you are converting to GPE, it really doesn't matter) Attempting to run a Lollipop GPE build with KitKat firmware will not work well.
jshamlet said:
The short answer is yes. However, the longer answer is yes, but you need to think carefully about this before pulling the trigger.
Some people repartition their phones to fully convert to the GPE version, but I don't recommend this unless you are either certain you want a GPE ROM or are highly skilled in this area. In your case, since you aren't certain, I would install without altering your partitions. From what I read in the first post, it appears this ROM simply rewrites your existing Sense partitions with GPE code, so it should be perfectly safe.
Also, make sure you note the required firmware version. AT&T has released a Lollipop version of their ROM, so if you aren't sure, you might consider running their RUU as a way to ensure you have compatible firmware. (since you are S-off, you can also use the Developer Edition RUU, but since you are converting to GPE, it really doesn't matter) Attempting to run a Lollipop GPE build with KitKat firmware will not work well.
Click to expand...
Click to collapse
yes thank you very much. I just installed this ROM. first boot times appeared broken and I had to factory reset. so far has not detected any errors.
I used the AT & T version of the ROM, but I feel uncomfortable because of the bundled applications, which I never use because I was in Vietnam. So how to completely remove them?
minhtienls said:
yes thank you very much. I just installed this ROM. first boot times appeared broken and I had to factory reset. so far has not detected any errors.
I used the AT & T version of the ROM, but I feel uncomfortable because of the bundled applications, which I never use because I was in Vietnam. So how to completely remove them?
Click to expand...
Click to collapse
Since you have the AT&T variant, and you are S-off, this is easy. Install the Developer Edition RUU. They are the exact same phone (same MID) but the Developer Edition doesn't have any of the AT&T bloat.
You may have to change the CID back to match one or the other of the unlocked/developer phones for the RUU to install. (either BS_US001 for unlocked or BS_US002 for developer edition) but you don't have to alter the MID at all.
If you don't root, you will get OTA updates directly from HTC.
As an aside, you might also try the WWE (world-wide English) variant as well, though that WILL require altering the MID.
jshamlet said:
Since you have the AT&T variant, and you are S-off, this is easy. Install the Developer Edition RUU. They are the exact same phone (same MID) but the Developer Edition doesn't have any of the AT&T bloat.
You may have to change the CID back to match one or the other of the unlocked/developer phones for the RUU to install. (either BS_US001 for unlocked or BS_US002 for developer edition) but you don't have to alter the MID at all.
Click to expand...
Click to collapse
I agree, if the OP wants a relatively clean, unbranded Sense setup (including official OTAs, and band support same as AT&T version) that the Dev Edition RUU is the way to go.
OP stated the phone is SuperCID, so no need to change CID (and I'd recommend not to change the CID to flash the Dev Ed RUU
Although GPE and Sense are two completely different animals. Not sure if the OP prefers one or the other? Although OP's last post did make it sound like they wanted a Sense ROM, just without AT&T branding.
As an aside, I don't see the utility in super CID anymore. It no longer "unlocks" anything (you don't get a free SIM unlock), so really the only advantage is being able to install any another HTC ROM via RUU. On the flip side, super CID blocks OTA updates on official ROMs, which makes it more of a disadvantage now.
Since most people are going to need a specific HTC ROM (for band support), or they are going to go with a third-party ROM which doesn't care what your CID is, I'd actually suggest using the CID/MID for the appropriate Sense ROM instead of super CID to ensure there aren't problems down the road. If you do, your phone essentially becomes that model for all intents and purposes.
(The obvious exception being Sprint/Verizon devices, but that isn't applicable here)
jshamlet said:
super CID blocks OTA updates on official ROMs, which makes it more of a disadvantage now.
Click to expand...
Click to collapse
You sure of that? I've seen folks say that a lot, but others also contradict the statement. ckpv5 in particular, and that guy knows his stuff. He's stated it a number of times (SuperCID does not prevent OTA); just yesterday, in fact: http://forum.xda-developers.com/showpost.php?p=63075776&postcount=9
But I agree that SuperCID is very limited in its usefulness (since MID is also a requirement, and there are so many different MIDs) and probably only in specific circumstances. For instance, I made my M8 SuperCID to install the Dev Ed RUU, and be able to RUU back to ATT if I wanted. But also, like you mentioned, I also run custom ROMs often, in which case CID is fairly irrelevant.
In the OP's case, as long as SuperCID doesn't block OTA, it saves him from changing the CID (although its just a single fastboot command) and also go back to ATT if desired.
SuperCID is probably pretty useful for Euro M8 owners, as there are a ton of CIDs for the same MID.
redpoint73 said:
You sure of that? I've seen folks say that a lot, but others also contradict the statement. ckpv5 in particular, and that guy knows his stuff. He's stated it a number of times (SuperCID does not prevent OTA); just yesterday, in fact: http://forum.xda-developers.com/showpost.php?p=63075776&postcount=9
But I agree that SuperCID is very limited in its usefulness (since MID is also a requirement, and there are so many different MIDs) and probably only in specific circumstances. For instance, I made my M8 SuperCID to install the Dev Ed RUU, and be able to RUU back to ATT if I wanted. But also, like you mentioned, I also run custom ROMs often, in which case CID is fairly irrelevant.
In the OP's case, as long as SuperCID doesn't block OTA, it saves him from changing the CID (although its just a single fastboot command) and also go back to ATT if desired.
SuperCID is probably pretty useful for Euro M8 owners, as there are a ton of CIDs for the same MID.
Click to expand...
Click to collapse
I've read conflicting reports on SuperCID blocking OTA updates as well, so he may very well be right. I will say that when I first installed the KitKat DevEd ROM, it appeared to refuse to download the OTA update to 4.4.4 until I reverted to using the official CID (BS_US002), but it's also possible that I just didn't wait long enough. Maybe that has changed since Lollipop?
If it really doesn't block OTA updates, then it's probably a pure don't care. If you are S-off, it's a trivial change. Also, if you are rooted, it's a moot issue anyway, as that is more likely to foul up OTA updates than the CID.
jshamlet said:
I've read conflicting reports on SuperCID blocking OTA updates as well, so he may very well be right. I will say that when I first installed the KitKat DevEd ROM, it appeared to refuse to download the OTA update to 4.4.4 until I reverted to using the official CID (BS_US002), but it's also possible that I just didn't wait long enough. Maybe that has changed since Lollipop?
If it really doesn't block OTA updates, then it's probably a pure don't care. If you are S-off, it's a trivial change. Also, if you are rooted, it's a moot issue anyway, as that is more likely to foul up OTA updates than the CID.
Click to expand...
Click to collapse
SuperCID doesn't block OTAs. It allows you to flash firmware for any CID without the need to change it. The CID works with all.
Since the OP is S-Off, I would suggest using WWE/International firmware. It's updated sooner if a Sense ROM is what he is after. OP could run MaximusHD if he wishes to remain Stock.
I'm preparing to unlock/root my 10 and if I'm going to go S-OFF this would be the time to do it. I'm just trying to figure out how necessary it really is. Since my phone's CID is presumably something like HTC_001, that should be included in any OEM firmware updates that are released, right? Assuming the signed firmware updates are posted here when they are released, I can just flash them without issue as far as I understand it. So, why would I need to S-OFF if I'm on an unbranded device?
I believe, and someone correct me if I'm wrong, but one of the biggest advantages of S-Off'ing is being able to flash ROMs that can take more control over the ecosystem. You get more control over your phone basically. As long as you're smart about what you flash/install to your device, there's not really any downside as long as you're okay dropping the $25 for sunshine.
So some ROMs have features that require S-OFF? As far as I know, just being unlocked and rooted will allow you to fully take advantage of LeeDroid, for instance. I thought S-OFF just applied to flashing firmware.
goodtimes50 said:
So some ROMs have features that require S-OFF? As far as I know, just being unlocked and rooted will allow you to fully take advantage of LeeDroid, for instance. I thought S-OFF just applied to flashing firmware.
Click to expand...
Click to collapse
Correct rom-wise there is no real advantage. Everything will work flawlessly with s-on.
http://forum.xda-developers.com/showthread.php?t=1868181
http://www.androidbeat.com/2014/07/s-htc-device-mean/
The things you can't do without S-Off are:
*flash unsigned firmware packages
*flash firmware packages that don't match CID/MID
*flash RUUs that don't match CID/MID
*change CID/MID
*restore "locked" status (without you can only get "relocked" status)
*restore "software status: official" flag in bootloader (flag sets to "software status: modified" if you flash anything)
Want a custom splash screen? Need S-Off.
Want to get rid of the red text warning during boot? Need S-Off.
Want to flash a different radio? Need S-Off.
What you can do without S-Off:
*unlock bootloader (via HTCdev)
*flash recovery
*root (via superSU package or your favorite custom ROM)
*flash ROMs
Nosferatu. said:
Want a custom splash screen? Need S-Off.
Want to get rid of the red text warning during boot? Need S-Off.
Want to flash a different radio? Need S-Off.
Click to expand...
Click to collapse
Sure looks like a quote from a post I made a while ago ) Not sure if this is entirely accurate for HTC 10 either, I'm definitely not hex-editing the aboot before I know it's safe to do so.
Nosferatu. said:
The things you can't do without S-Off are:
*flash unsigned firmware packages
*flash firmware packages that don't match CID/MID
*flash RUUs that don't match CID/MID
*change CID/MID
*restore "locked" status (without you can only get "relocked" status)
*restore "software status: official" flag in bootloader (flag sets to "software status: modified" if you flash anything)
Want a custom splash screen? Need S-Off.
Want to get rid of the red text warning during boot? Need S-Off.
Want to flash a different radio? Need S-Off.
What you can do without S-Off:
*unlock bootloader (via HTCdev)
*flash recovery
*root (via superSU package or your favorite custom ROM)
*flash ROMs
Click to expand...
Click to collapse
Hey, this mixing of terminology is killing me
Isn't ROM and Firmware the same thing? If not then could you define both? I'm asking because to me those 2:
"flash unsigned firmware packages"
"flash ROMs"
look the same, no? Or by "firmware packages" you mean the images that are inside the zip package, like boot.img, recovery.img etc? But if so, then how can I flash the custom recovery (like TWRP) which I assume is not signed if I don't have S-off?
lukair1983 said:
Hey, this mixing of terminology is killing me
Isn't ROM and Firmware the same thing? If not then could you define both? I'm asking because to me those 2:
"flash unsigned firmware packages"
"flash ROMs"
look the same, no? Or by "firmware packages" you mean the images that are inside the zip package, like boot.img, recovery.img etc? But if so, then how can I flash the custom recovery (like TWRP) which I assume is not signed if I don't have S-off?
Click to expand...
Click to collapse
No, they're not the same. Think of the firmware as the level between the software (recovery/ROM) and the physical hardware. Firmware contains stuff like radios, CPU governors, camera drivers, etc.
I see. So when people receive OTA's they receive firmware ALONG with other stuff (boot, recovery, system images etc.) ?
lukair1983 said:
I see. So when people receive OTA's they receive firmware ALONG with other stuff (boot, recovery, system images etc.) ?
Click to expand...
Click to collapse
That's correct.
I see.
Alright, so to check on that I've downloaded one of the OTA's in the "[STOCK] Guides and Stock Backups/Recovery/OTA/RUU" thread and indeed there is firmware.zip inside. I assume that's what you guys meant. However I don't see there any boot.img, recovery.img etc. What am I missing here in my understanding?
Nosferatu. said:
The things you can't do without S-Off are:
*flash unsigned firmware packages
*flash firmware packages that don't match CID/MID
*flash RUUs that don't match CID/MID
*change CID/MID
*restore "locked" status (without you can only get "relocked" status)
*restore "software status: official" flag in bootloader (flag sets to "software status: modified" if you flash anything)
Want a custom splash screen? Need S-Off.
Want to get rid of the red text warning during boot? Need S-Off.
Want to flash a different radio? Need S-Off.
What you can do without S-Off:
*unlock bootloader (via HTCdev)
*flash recovery
*root (via superSU package or your favorite custom ROM)
*flash ROMs
Click to expand...
Click to collapse
This...
Except I haven't noticed red text on boot with this device.
Where you're going to really want s-off, is when Android N is released and you've got a carrier branded phone. Usually new Android versions require updated firmware to operate properly. If you're s-off, you can flash the first firmware that's available for the device. If not, you're stuck waiting for your carrier to update you. Real world example... AT&T JUST released marshmallow last week for the M9. With s-off, I've been on 6 since December. Otherwise I would have been stuck on lollipop.
To a slightly lesser degree is when HTC releases a major upgrade within an Android version. For example, there will probably be a 2.xx.xxx.x release that's still marshmallow. You could face issues trying to run a new base rom on older firmware, but sometimes it works fine. Having said that, you can always stay on the custom rom that's built on your base. Rom developers leave older versions available so you can find one that matches your device.
Basically, in a nut shell, s-on, you're tied to your carrier for firmware updates. S-off you're not.
---------- Post added at 09:17 AM ---------- Previous post was at 09:13 AM ----------
lukair1983 said:
I see.
Alright, so to check on that I've downloaded one of the OTA's in the "[STOCK] Guides and Stock Backups/Recovery/OTA/RUU" thread and indeed there is firmware.zip inside. I assume that's what you guys meant. However I don't see there any boot.img, recovery.img etc. What am I missing here in my understanding?
Click to expand...
Click to collapse
Those are inside firmware.zip.
Here is a link to the unsigned firmware.zip for us unlocked.
https://drive.google.com/file/d/0B8OH6sFjVE1ld1ptNTFEaEc3Rms/view?usp=drivesdk
Firmware was 80 something MB, entire ota was over 400, so there was a lot that was updated besides firmware.
Or, have the unbranded, unlocked version from HTC and not have to worry about too much.
Sent from my HTC 10 using XDA-Developers mobile app
jollywhitefoot said:
This...
Except I haven't noticed red text on boot with this device.
Where you're going to really want s-off, is when Android N is released and you've got a carrier branded phone. Usually new Android versions require updated firmware to operate properly. If you're s-off, you can flash the first firmware that's available for the device. If not, you're stuck waiting for your carrier to update you.
Click to expand...
Click to collapse
jollywhitefoot, what if you have unlocked phone bought direcly from htc? I assume at this point there will be no problem with Android N while being at the same time s-on, correct? (taking into account being unlocked and rooted and having custom recovery)
jollywhitefoot said:
Those are inside firmware.zip.
Here is a link to the unsigned firmware.zip for us unlocked.
https://drive.google.com/file/d/0B8OH6sFjVE1ld1ptNTFEaEc3Rms/view?usp=drivesdk
Firmware was 80 something MB, entire ota was over 400, so there was a lot that was updated besides firmware.
Click to expand...
Click to collapse
Thanks a lot for the image!
So, the thing that goodtimes50 said was not correct? Talking about a phrase: "No, they're not the same. Think of the firmware as the level between the software (recovery/ROM) and the physical hardware. Firmware contains stuff like radios, CPU governors, camera drivers, etc.". If the firmware contains the recovery, and clearly your image shows that, then the "firmware" can't be a bridge or a level between those things that goodtimes50 mentioned.
So would it be accurate if I said that firmware contains everything that doesn't have to do directly with the OS itself? Meaning, that when I say "ROM" I would think of a system image (being OS), maybe the data image as some additional applications etc?
The terminology is just crazy, somebody must do an encyclopedia for the Android terminology!
lukair1983 said:
jollywhitefoot, what if you have unlocked phone bought direcly from htc? I assume at this point there will be no problem with Android N while being at the same time s-on, correct? (taking into account being unlocked and rooted and having custom recovery)
Thanks a lot for the image!
So, the thing that goodtimes50 said was not correct? Talking about a phrase: "No, they're not the same. Think of the firmware as the level between the software (recovery/ROM) and the physical hardware. Firmware contains stuff like radios, CPU governors, camera drivers, etc.". If the firmware contains the recovery, and clearly your image shows that, then the "firmware" can't be a bridge or a level between those things that goodtimes50 mentioned.
So would it be accurate if I said that firmware contains everything that doesn't have to do directly with the OS itself? Meaning, that when I say "ROM" I would think of a system image (being OS), maybe the data image as some additional applications etc?
The terminology is just crazy, somebody must do an encyclopedia for the Android terminology!
Click to expand...
Click to collapse
What he said is correct and what you said is correct. Recovery and boot are always included in firmware packages but technically they're not firmware files.
As for us unlocked, you get updates directly from HTC, so you're not waiting for a carrier. The US unlocked version isn't always the first to get updated, though. A lot of times Europe and Asia get the update first.
Good thing I'm not in US then
(Just kidding I know it has to do with the phone version not a location)
Thanks a lot jollywhitefoot. I'm getting closer to grasping the whole HTC ecosystem. The last stop would be to understand what I will have to do to update my OS when next OTA's start appearing as I intend to unlock bootloader, flash TWRP and flash SU so that I get root. I do however intend to keep the s-on. From what I read s-off really is mostly used to change the cid, as almost everything else can be done with s-on (aside from messing with radio or splash screens but I don't care about that). Besides that s-on is more secure than s-off as I will not be able to brick my phone that way no matter what I do.
From my understanding I won't be able to update with OTA that easly afterwards. Well, I don't mind a bit of a hassle as long as I keep my OS setup, my apps, their settings and my data on internal storage. Is it possible that there will be a flashable zip's made by the scene that will do basicaly the same as the OTA, but I will not have to restore stock recovery, formware, flash the OTA, then reflash the TWRP as well as reroot or it's simply impossible to do and the "hassle thing" is unavoidable?
lukair1983 said:
jollywhitefoot, what if you have unlocked phone bought direcly from htc? I assume at this point there will be no problem with Android N while being at the same time s-on, correct? (taking into account being unlocked and rooted and having custom recovery)
Click to expand...
Click to collapse
That's basically what I'm trying to figure out. For an unbranded phone, wouldn't the signed firmware files get posted here as soon as they're available and we can just flash away?
lukair1983 said:
Is it possible that there will be a flashable zip's made by the scene that will do basicaly the same as the OTA, but I will not have to restore stock recovery, formware, flash the OTA, then reflash the TWRP as well as reroot or it's simply impossible to do and the "hassle thing" is unavoidable?
Click to expand...
Click to collapse
If you're S-OFF, yes. Otherwise, no.
Captain_Throwback said:
If you're S-OFF, yes. Otherwise, no.
Click to expand...
Click to collapse
Is that because when unlocked and s-on the only partitions I can modify are system, boot and recovery while the complete rom/ota might also contain other stuff like bootloader, radio, other firmare things etc. and those I will not be able to flash even in fastboot? Is that the reason?
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!.