[Q] Would like to update my One M8 - One (M8) Q&A, Help & Troubleshooting

I'd like to update my One M8 to the latest iteration of Android available, but I haven't kept up with development since its release and am very confused as to my options and procedure.
To start with, I have a original release unlocked HTC One M8 GPE model, which I immediately converted to a stock T-Mobile Sense rom. In doing so, I obtained S-Off and SuperID as at the time it was necessary. It was also what seemed to be a one-way conversion from GPE to Sense, as trying to convert back would be very difficult (though not impossible). Ever since then, I have not bothered with any upgrades to the OS (other then a radio update), so afaik, it's still at the original rom/software versions of that initial release.
Reading from my Settings menu, I an on Android 4.4.2, Sense 6.0, ROM version 1.57.531.7, Kernal version 3.4.0-ga23aecb, Baseband 1.16.21331931, and Build number 1.57.531.7.
Reading from the boot screen, I am Unlocked, S-Off, CID-11111111, HBoot-3.16.0.0000, Radio-1.16.21331931.LA24G, and running with TWRP 2.7.1.0.
What I am confused about is, what would be the best and easiest option for me to update to the latest version. In reading some of the requirements for various roms, I can't tell which is using the latest available Android version, or if I need to do any updates to my M8 before I can even attempt to install the rom. I'm just looking to go back to a regular GPE rom, though I wouldn't mind any of the tweaks the custom roms bring, as well as having Xposed usage and root, both being a must!
Any advice or help to my upgrade path is much appreciated.

The fastest, easiest, and safest way to upgrade is to flash the latest stock, official HTC RUU for your device.
The link below will take you to HTC's page with instructions on how to flash the latest RUU for your T-Mobile M8 (SKU 531) and a download link for the latest marshmallow RUU - rom version 6.20.531.5 - at the very bottom.
http://www.htc.com/us/support/htc-one-m8-t-mobile/news/
Best of luck

Related

[Q] Flashing Asian firmware in a European version or vice versa

Hi I would like to know if there would be a problem if I flash the official rue of an Asian desire z with a european version or vice versa?
I bought my phone second hand and I decided to flash the 1.34.707.1 version into my originally 1.72 desire z. Now my phone cannot find updates. It keeps telling me that there is no update even if check manually.
I know that I can flash a higher version by downloading a higher rue version but what I wanted to find out if I can no longer receive ota updates because of what I did.
Since when I was in 1.72 my phone did not notify me of the 1.82 update too...
I don't know what's wrong.. Please help. Thank you.
I think if you are SuperCID and S-Off, it would work. Otherwise, it won't let you flash the ROM from another region.
Also, if you flash an official ROM, you will lose root, and you can't get it back on any ROM version higher than 1.34. For this reason, if you downgraded to 1.34 for purposes of rooting, you don't want the OTA updates, anyway.
If you're rooted and S-Off, and you want a more updated ROM version, just flash the Virtuous custom ROM. Its mostly stock 1.85, but rooted, and with a few cool added features and some optimizations.
Hi, the thing is I'm not very knowledgeable when it comes to rooting. I read the posts here specifically in the wii section and I don't think I have the skills to pull it off and risk bricking my phone.
I think my phone is not rooted or it was before but not anymore, since as mentioned I flashed an official ruu.
So basically, I should still be able to receive OTA's from HTC right? I was wondering why my phone keeps telling me there's no update when the software number is 1.34 stock and not rooted. Shouldn't it notify me that there's an update at least regardless of whether I want to or not?
If you are not rooted, why did you downgrade to 1.34?
I also don't understand why you want to flash the RUU from a different region. If you aren't SuperCID and S-Off it won't work. Why not just flash the latest official RUU for your phone versions/region if you want to be updated and don't care about root?
I'm not sure why your OTA's don't work. I'm still on 1.34 (well, back to it), and I still get notifications to update.
redpoint73 said:
If you are not rooted, why did you downgrade to 1.34?
I also don't understand why you want to flash the RUU from a different region. If you aren't SuperCID and S-Off it won't work. Why not just flash the latest official RUU for your phone versions/region if you want to be updated and don't care about root?
I'm not sure why your OTA's don't work. I'm still on 1.34 (well, back to it), and I still get notifications to update.
Click to expand...
Click to collapse
@redpoint73
I bought the phone from a friend of mine. I noticed that it had eng hboot and had s-off.
I have zero knowledge about rooting. When the gingerbread test rom for the desire z came out, I flashed the pc10img.zip via the bootloader, however since it was very buggy and laggy, I decided to flash stock desire z rom.
Having no knowledge about rooting I read some of the threads in this forum and learned that flashing an official rom i.e. the RUU would be the easiest way to return back to stock.
It worked, I am using stock rom. I experimented and found out that I can flash any of the RUU, so I chose any of the WWE release. I decided to flash an older firmware version specifically, the 1.34.707.1.
Now the problem is my phone doesn't prompt me with an update, even after checking in about phone > check for update.
I still have s-off but eng hboot is gone. To clarify I was not the one who rooted the phone, so I have no idea what to do.
Is it possible that the previous owner tweaked something in the phone that would absolutely prevent it from receiving OTA?
I am just worried since I have a feeling that the gingerbread OTA will be released in a few weeks since the update for the Desire HD is already out.
Please help and thank you again. I extremely as a NOOB!
qtlestat said:
I am just worried since I have a feeling that the gingerbread OTA will be released in a few weeks since the update for the Desire HD is already out.
Click to expand...
Click to collapse
I wouldn't worry about getting the official Gingerbread ROM OTA. It will probably be posted here or at shipped-roms.com long before you would get it OTA.

[Q] Wrong CID with wrong software number > unable to update

Hello XDA community,
I have the following problem. I bought an unbranded HTC Desire HD but when the Gingerbread update was released and I did not receive it and got curious what was going on.
Using CID Getter, I found out that the CID of my phone is T-MOB101 whereas it should be HTC_001 on an unbranded phone. The software information on my phone is as follows:
Android: 2.2.1
Software number: 1.72.405.3
Using the search function in this forum, I found out that the T-MOB101 CID only exists with the software number 1.32. As far as I know this means that the phone I bought was a branded phone which was overwritten with another stock rom with the software version 1.72. That means I can wait until kingdom comes regarding the Gingerbread update.
I'd really like to update to Gingerbread and fix my phone in this respect. Having conducted some research, I found out that (1) changing the CID requires to downgrade to 1.32 because I'd need to root the phone and that is not possible with 1.72. If I wanted to back up my phone, e.g. with Titanium Backup, (2) I'd need to root it as well and, thus, downgrade to 1.32. Also, if I wanted to backup my current ROM with ROM Manager, I'd need the required privilidges and root and, therefore before, downgrade the phone.
If I have to go through this trouble, I think, I could install a custom rom as well (e.g. Virtuous Unity as I'd like to have Sense 3.0). I've found out that I always have to downgrade no matter which option I choose because I need to be able to root the phone and, apparently, that's not possible with 1.72. - Is all of the above concluded correctly?
In fact, I'd just like to install a custom rom with sense 3.0 now and be able to flash back to the stock rom, just in case I'd ever need to meet the requirements for warranty, and backup the files I need to backup (except for data which I can synchronize from the Google server, of course).
Does anyone have an optimal procedure of solution at hand? - I'd be very grateful. - Thank you very much in advance.
Cheers,
B-Ball
ok...if you say you're phone is branded you need to create a goldcard first to downgrade and i believe it already exists a thread for downgrading...just do a search
Well, I am not sure if you can still call my phone a "branded" one due to the above facts. I assume it was branded and then an unbranded stock rom with the software version 1.72 was installed but the CID was not changed.
However, do you think there is a way for me to be able to install a custom rom with sense 3.0 and be able to flash back to a strock rom at a later point if I have to downgrade first in order to get root rights?
Yes you will have to downgrade first to be able to get root rights and change the CID.
To get back to stock you have to use a RUU. These are official HTC utilities that wipe out all the changes (just about) that you made to your phone and make it stock. There is a thread somewhere for these. I think in Development.
Ev1dence said:
Well, I am not sure if you can still call my phone a "branded" one due to the above facts. I assume it was branded and then an unbranded stock rom with the software version 1.72 was installed but the CID was not changed.
However, do you think there is a way for me to be able to install a custom rom with sense 3.0 and be able to flash back to a strock rom at a later point if I have to downgrade first in order to get root rights?
Click to expand...
Click to collapse
You need the official RUU to go back to stock and if you want to change the CID you still need to root your device

[Q[ Questions on RUU

Hey Guys,
I just had some questions regarding RUU's and sort of trying to understand them.
Do RUU's update everything that normal custom ROM's cannot, i.e. like the OTA's? So updating drivers and hboot etc?
Main reason is that if it does update everything then on the next big update I would probably want to do an RUU install even if it means loosing all data.
With regards to the RUU do I need all three of the following:
- Stock ROM
- Stock Recovery
- Locked bootloader
Or do I need JUST a locked bootloader?
Thanks
Yes you will get updates if you flash a ruu and ruu 's are pure stock ruu's are used when we need to put the stock Rom back on our device when we need to send it in for repair's and also when we prefer the stock Rom over a custom Rom I my self prefer custom Rom over a stock Rom and sometimes when a custom Rom isnt performing the way it should some people will simply go back to stock by flashing a ruu
Sent From My Viper S 1.2.0 with true s off by alpha revolutionary
jslim38 said:
Yes you will get updates if you flash a ruu and ruu 's are pure stock ruu's are used when we need to put the stock Rom back on our device when we need to send it in for repair's and also when we prefer the stock Rom over a custom Rom I my self prefer custom Rom over a stock Rom and sometimes when a custom Rom isnt performing the way it should some people will simply go back to stock by flashing a ruu
Sent From My Viper S 1.2.0 with true s off by alpha revolutionary
Click to expand...
Click to collapse
Thanks, my main reason is actually not to say on an RUU but I was hoping to install an RUU, get all the updates to my firmware and drivers, then unlock bootloader again and install a custom ROM.
They should be updated by a custom rom. Only thing that isnt touched is the HBOOT i think. But reflash stock recovery relock the bootloader then run the ruu.
Flashing an RUU first if available is the way to go personally
Sent from my HTC One X using xda premium
I readin a lot on here and I read somewhere updateing with ruu updates hboot and hboot is some sort of security so updateing it could make getting s-off harder
Sent from my HTC One X using xda premium
Updating the HBoot means adding more layers of security, which imo is not something we enjoy here on XDA
Personally, I prefer going with a custom ROM that is almost like stock (preferably ARHD) which with every update brings the improvements brought to us by HTC and even more.
Also with ARHD for example, upgrading from one version to a newer one rarely requires you to wipe all your data which is very annoying imo.
I've been on Custom roms since I had my phone so I had missed the OTA update for 1.xxx.11 and the 2.xx versions, now with the a big 3.xx version on the horizon, my main concern is if my Custom ROM's are not updating some critical firmware drivers and such that would have benefitted my phone.
Tbh it's still not clear to me what Custom ROM's cannot update, at first I thought it was just the HBOOT but then I read on a recent thread that apparently things like GPU drivers and other essential hardware firmware drivers may not get updated either which sounds like a big deal. Hence I was thinking with the release of 3.xx I should do an RUU install just to be sure and then go ahead to a Custom ROM.
I understand that having my HBOOT updated could mean S-OFF is harder but the way things are, it doesn't look like were any close to getting it either, who knows maybe even a future HBOOT update might have an easier S-OFF is HTC decide to relax it a bit from consumer pressure?
When developers get their hands on new RUUs they base their custom Roms on them, and therefore you will get the new updates in terms of drivers and other software related things.
Also, kernels bring new improvements as they are updated, and developers also build their ROMs on these kernels. However, you can flash custom kernels separately if you find one that has additional "improvements" you like.
In short, custom ROMs that are maintained/updated regularly (ARHD is one of the best imo) is all you need to stay up to date with all the new improvements.
The only reason I ever download any RUU is in case something went wrong with my phone, and I wanted to temporarily return to stock.
Ah right, I was thinking more of the S-ON security restriction not letting custom ROM's fully update everything except radio, kernel and ROM but RUU's are given the full access to update everything?
iq-dot said:
Ah right, I was thinking more of the S-ON security restriction not letting custom ROM's fully update everything except radio, kernel and ROM but RUU's are given the full access to update everything?
Click to expand...
Click to collapse
I don't think there is consensus on what can be updated and what cannot.
Here's my take: an OTA has access to everything, as does an RUU, but the point is that they flash signed images, and the phone will allow signed images to be flashed (subject to matching CID, etc.).
It's possible to flash kernel with the boot.img, and also possible to flash kernel modules, which means that drivers can be updated.
It's possible to flash "radios" (often as part of the ROM), and there is an app to get updated RILs, so it would seem that the RIL has not been confused with the radio. However, since the bootloader appears to get the radio version from a text file, rather than the radio, there's some doubt as to whether the radio is really updated (since the bootloader disagrees).
Obviously we can unlock and gain access to flashing unsigned recovery, boot (kernel/ramdisk) and ROM images.
Outside of this, it's not impossible that there are areas of the phone that still require flashing of signed images, such as for firmware updates of other bits of hardware not previously mentioned (speculatively: lower level bits of "radio", cpu microcode, gpu firmware, etc.), which may or may not be flashable with an RUU (or maybe even an OTA). However, there is nothing in an RUU that cannot be done with tools we already have, so if there was a "fastboot flash cpu_microcode" option, somebody would have found it. I haven't looked at full list of fastboot commands, but I don't recall coming across anything like that.
xbiggyl said:
When developers get their hands on new RUUs they base their custom Roms on them, and therefore you will get the new updates in terms of drivers and other software related things.
Also, kernels bring new improvements as they are updated, and developers also build their ROMs on these kernels. However, you can flash custom kernels separately if you find one that has additional "improvements" you like.
In short, custom ROMs that are maintained/updated regularly (ARHD is one of the best imo) is all you need to stay up to date with all the new improvements.
The only reason I ever download any RUU is in case something went wrong with my phone, and I wanted to temporarily return to stock.
Click to expand...
Click to collapse
There are some parts of the firmware/drivers that custom ROMs cannot change so flashing an RUU first does have it's benefits to get a true experience of a custom ROM
EddyOS said:
There are some parts of the firmware/drivers that custom ROMs cannot change so flashing an RUU first does have it's benefits to get a true experience of a custom ROM
Click to expand...
Click to collapse
Do you know what, specifically?
I don't, no, it's just a personal preference I suppose. I updated to the 2.17 RUU (UK unbranded) and then went onto a custom ROM based on the same RUU so I know everything is compatible. Whether it has any real affect I don't know but seeing as Mike used to have 'firmware' packages for other HTC handsets it would lead me to believe he would with the One X if we had S-OFF
EddyOS said:
Mike used to have 'firmware' packages for other HTC handsets it would lead me to believe he would with the One X if we had S-OFF
Click to expand...
Click to collapse
...there are a lot of masked partitions, eh? Who knows.
A lot of the partitions were listed in the S-OFF thread but as to what they actually contain/do is open to discussion - it could be a custom ROM it's own is enough but without S-OFF we'll never really know
EddyOS said:
There are some parts of the firmware/drivers that custom ROMs cannot change so flashing an RUU first does have it's benefits to get a true experience of a custom ROM
Click to expand...
Click to collapse
Have you read anywhere of any improvements offered exclusively by RUUs or you're simply speculating?
I know some partitions (that appeared to be in the HOX) are not accessible by Custom Roms, but has anyone ever claimed to have experienced an improvement in any way by flashing an RUU that people flashing custom Roms haven't?
Sent from my HTC One X using Tapatalk 2

[Q] Stuck in somewhere with not wifi

Decided to take the last Software update from HTC and messed up everything.
I am unlocked with S-ON so decided to relock and start the process, now after 3 days on reading and testing different way i have this:
unlock S-on Hboot 3.18.00000
invalide radio and os info. Tried Android revolution and Maximus latest ROM on both wifi don't work.
Tried to go s-off till i got the message that my device has been patched by HTC
I don't mind to go with a ROM or full back to stock but need some help getting the device working with wifi
This has been discussed in many (probably dozens) of existing threads.
The latest ARHD and Maximus require the latest firmware, which corresponds with hboot 3.19.
You either need to update the firmware manually with S-off, or install the newest OTA (if available for your version). Alternately, use a 2.xx software based ROM to get WiFi working.
redpoint73 said:
This has been discussed in many (probably dozens) of existing threads.
The latest ARHD and Maximus require the latest firmware, which corresponds with hboot 3.19.
You either need to update the firmware manually with S-off, or install the newest OTA (if available for your version). Alternately, use a 2.xx software based ROM to get WiFi working.
Click to expand...
Click to collapse
Been reading more than the dozen mentioned and in any case thank you for the information.
Got the Wifi working installing a previous ROM as you suggest and now will start the process to get s-off and proceed. Even tried Sumshine do not mind to pay for it but can't install the apk on the phone.....
Is not my day probably
redpoint73 said:
This has been discussed in many (probably dozens) of existing threads.
The latest ARHD and Maximus require the latest firmware, which corresponds with hboot 3.19.
You either need to update the firmware manually with S-off, or install the newest OTA (if available for your version). Alternately, use a 2.xx software based ROM to get WiFi working.
Click to expand...
Click to collapse
want to update also the other that faced the same issues.
Loaded MaximusHD 7 and got wifi working
Through sunshine got s-OFF now wante to try to get all the best to have all the upgrade.
Will have to ready dozens more ot threads, if someone has help and suggestion is welcome
succe said:
want to update also the other that faced the same issues.
Loaded MaximusHD 7 and got wifi working
Through sunshine got s-OFF now wante to try to get all the best to have all the upgrade.
Will have to ready dozens more ot threads, if someone has help and suggestion is welcome
Click to expand...
Click to collapse
Just look in the Development section for the firmware collection. Or just read through the ARHD or Maximus threads (starting from the most recent posts and going back from there), and they will probably lead you to the same place. Seriously, its not that hard to search for info on XDA. I never once after modding 6 Android and 2 Windows Mobile devices before that, had to ask folks to lead me to the info. Most of us just search and find it ourselves. Reading through the thread for the ROM you are having problems with will lead you to the answer 99% of the time; and you should do this when you flash any ROM.

[Q] Telus M8 Return to Stock / OTA / Firmware Update

Hi there,
I have a Telus HTC M8, which I got when it first came out and threw TWRP and Cyanogenmod on it. Great decision.
The only delema I have now, is I am at a point with the cyanogenmod updates that I can not pass a certain one, as it requires a firmware update.
I am on HBoot 3.16
I can not find a nandroid backp of the stock OS for my phone for the correct Hboot
I also can not find the stock recovery for my Hboot
These would be needed to do the OTA update, then go back to TWRP and cyanogenmod.
The other way of updating the firmware (from what I know) is to push the .zip through fastboot.
Although I can not find the firmware update for my Telus device (661 I believe).
I also can not put S-Off to obtain super CID (curently S-On) as firewater is gone, and sunshine requires the factory android.
Any help, links, etc, are appreaciated.
Bump
johndom4774 said:
Hi there,
I have a Telus HTC M8, which I got when it first came out and threw TWRP and Cyanogenmod on it. Great decision.
The only delema I have now, is I am at a point with the cyanogenmod updates that I can not pass a certain one, as it requires a firmware update.
I am on HBoot 3.16
I can not find a nandroid backp of the stock OS for my phone for the correct Hboot
I also can not find the stock recovery for my Hboot
These would be needed to do the OTA update, then go back to TWRP and cyanogenmod.
The other way of updating the firmware (from what I know) is to push the .zip through fastboot.
Although I can not find the firmware update for my Telus device (661 I believe).
I also can not put S-Off to obtain super CID (curently S-On) as firewater is gone, and sunshine requires the factory android.
Any help, links, etc, are appreaciated.
Click to expand...
Click to collapse
If you really want S-Off (your best option IMO ~ never wait for Telus to update *my carrier also*) I can help you. Of course, Sunshine is the only way now.
Flash the Maximus HD ROM. It is best if you look for one that matches your firmware/hboot (4.4.2)
A lot of users have reported success with gaining S-Off using this ROM. It is near stock and I can almost 99.9% guarantee it will work.
If you want to take the S-Off route, you can download the Maximus HD 4.4.2 version by clicking this link.
You can also install Rogers or bell from 3.16 hboot. To continue with soff after.
thank you very very much. I will give it a shot and touch base with the results!
wow. Thank you so much!
Life-fu*****-saver!
Much love! <3
p.s. It worked

Categories

Resources