So i have a verizon m8 that is o operating on straight talk. It is on software version 1.55.605.2. It is stock with the ruu, rooted, s-off and bootloader locked right now. When i try to preform an ota it says it is up to date. Since i know that isnt true, how can i either get the ota to work or can i just grab the ruu for lollipop and skip all the others? Thanks for any help you can give
Related
I have a friend with a One S that's stuck on version 1.78.206.4. She's rooted the phone and unlocked the bootloader, since which OTA updates haven't been applying properly (I'm assuming this is by design on HTC's part). What's the correct way to go about upgrading to JB? My current plan is to have her reset to stock, lock her bootloader, and accept OTAs until she reaches the most current ICS before manually applying the JB OTA, but she was a weird cid (O2___001) as a result of having a carrier-branded model (she uses it unlocked on 3, if that's salient) and I'm not sure if she can safely apply the OTA, as it's not in the list of cids that work in the thread (http://forum.xda-developers.com/showthread.php?t=2063848). If she needs to be on the unbranded build, how can she achieve this?
I have a Telus evita phone on 4.1.1. I was wondering if I could flash the German O2 or T-Mobile OTA to receive 4.2.2. My phone is SuperCID and S-OFF. Phone is currently stock because I ran a RUU then updated to 4.1.1. Will I lose my data if I flash the OTA?
Thanks
dx99 said:
I have a Telus evita phone on 4.1.1. I was wondering if I could flash the German O2 or T-Mobile OTA to receive 4.2.2. My phone is SuperCID and S-OFF. Phone is currently stock because I ran a RUU then updated to 4.1.1. Will I lose my data if I flash the OTA?
Thanks
Click to expand...
Click to collapse
I would just flash TWRP back onto the phone, then flash Turge's stock T-Mobile Sense 5 ROM posted in Development. Install the 2.15 firmware if you experience signal drops or random reboots.
My typical recommendation is to stay away from official OTAs if you are modded.
I just don't want to flash anything on my phone that's not official. That's why I'm asking, I want to keep my phone stock and just get an official update not a rom from another source.
Your phone is already far from stock, with SuperCID and S-off. You're already down the rabbit hole. And putting an OTA for another version is also not going to be "stock" or "official" for your phone.
The stock ROM is just from the OTA dump, completely unmodified (not even rooted, in fact). Its what is on my phone, and is running great.
Running the OTA might be risky. OTA does not necessarily have all the components. For instance, the T-Mobile 5.05 OTA does not have all the hboot modules. It assumes you are coming for the most recent T-Mobile RUU or OTA. So depending on what is currently on your phone, you can brick.
In theory, I think what you are proposing will work if you RUU to the most recent T-Mobile Germany RUU, than T-Mobile Germany Sense 5 OTA.
But again, you're making it more complicated than need be. What is exactly the issue with "unofficial" ROMs? If you don't trust the devs here, you would not have done SuperCID and s-off to begin with.
It's not that I don't trust the devs I just want to use official carrier updates. I know my phone isn't stock what I meant is using stock/original files from carriers. So even though my phone is from Telus and I used a RUU from them to get back to stock firmware I can flash a T-Mobile RUU over top of it then use their OTA afterwards?
dx99 said:
So even though my phone is from Telus and I used a RUU from them to get back to stock firmware I can flash a T-Mobile RUU over top of it then use their OTA afterwards?
Click to expand...
Click to collapse
Yes, the only thing stopping the RUU from running would be the carrier ID check and hboot version check (might be some other checks). But since you have s-off, all security checks are bypassed by definition.
Alright, would there be any issues with the fact that I'm on 4.1.1 and going backwards in firmware first? Since most RUU are 4.0.
dx99 said:
Alright, would there be any issues with the fact that I'm on 4.1.1 and going backwards in firmware first? Since most RUU are 4.0.
Click to expand...
Click to collapse
Now that you mention it, it looks like you would have to run the most recent RUU from T-Mobile Germany (3.17.111.1) then run two OTAs (3.17.111.2, and then finally 5.08.111.2). Run them out of sequence, and you risk a brick.
RUUs can be installed out of sequence, but there isn't one for 5.08.
I retract my former idea to RUU then OTA. I can't personally recommend such action upon further consideration. Its more complicated than I originally thought. I go back to my former statement, in that you are making this much more complicated than it should be. You are actually creating a higher risk of bricking your phone due to some imagined fear of "unofficial software".
redpoint73 said:
Now that you mention it, it looks like you would have to run the most recent RUU from T-Mobile Germany (3.17.111.1) then run two OTAs (3.17.111.2, and then finally 5.08.111.2). Run them out of sequence, and you risk a brick.
RUUs can be installed out of sequence, but there isn't one for 5.08.
I retract my former idea to RUU then OTA. I can't personally recommend such action upon further consideration. Its more complicated than I originally thought. I go back to my former statement, in that you are making this much more complicated than it should be. You are actually creating a higher risk of bricking your phone due to some imagined fear of "unofficial software".
Click to expand...
Click to collapse
So then its not possible to use the T-Mobile RUU and OTA on my Telus phone?
dx99 said:
So then its not possible to use the T-Mobile RUU and OTA on my Telus phone?
Click to expand...
Click to collapse
I think its possible, but its needlessly complicated and possibly risky. If you do it wrong, you might brick.
I don't personally recommend it, and its my personal opinion that you don't have a particularly valid reason for going that route when simpler methods exist. So if you proceed, its at your own judgement and you take all responsibility if something goes wrong.
If it does manage to work so you think there might be compatability issues with the play store or region specific things?
I just bought a HTC One M8 from T-Mobile, that incidentally came with an older HBoot.
I was promoted with an OTA updated & an ignoramus like me was accepted the 3.16 OTA & now I cannot achieve S-OFF!
Whats the verdict? Do I need to wait until a new exploit comes out for 3.16? Is there an exploit already available (thats not firewater) but I just haven't searched deep enough?
I've unlocked my bootloader so no use in trying to return the phone now, any replies/information is much appreciated!
rowrz said:
I just bought a HTC One M8 from T-Mobile, that incidentally came with an older HBoot.
I was promoted with an OTA updated & an ignoramus like me was accepted the 3.16 OTA & now I cannot achieve S-OFF!
Whats the verdict? Do I need to wait until a new exploit comes out for 3.16? Is there an exploit already available (thats not firewater) but I just haven't searched deep enough?
I've unlocked my bootloader so no use in trying to return the phone now, any replies/information is much appreciated!
Click to expand...
Click to collapse
I am also having this issue. updated on day one not knowing it Patched the S-Off. any new updates would helpful.
I have the 3.16 hboot, and I had no problem getting s-off using this method:
http://firewater-soff.com/
I did not accept the ota update though.
rowrz said:
I just bought a HTC One M8 from T-Mobile, that incidentally came with an older HBoot.
I was promoted with an OTA updated & an ignoramus like me was accepted the 3.16 OTA & now I cannot achieve S-OFF!
Whats the verdict? Do I need to wait until a new exploit comes out for 3.16? Is there an exploit already available (thats not firewater) but I just haven't searched deep enough?
I've unlocked my bootloader so no use in trying to return the phone now, any replies/information is much appreciated!
Click to expand...
Click to collapse
theroot.ninja $25 but worth it, works with anyone who updated OTA
Hey, how is it going? Some months ago, I received an used HTC ONE M8 Harman/Kardon edition. It was almost new. The thing is that since I got it, it has a custom rom (Bad Boyz Sprint ONE M8 Harman v2.1 ART).
I recently want to update to Sense 7.0 (currently 6.0) and also update android to 5.0 (currently 4.4.4), but I just can't from the update software section. If I press to verify updates, it just never appears to find something. I think it has to be something related with the fact that it is not the original rom. The phone was bought in US but I'm not in the US. I'm just worried that the ROM was installed in order to function out of the US, I mean, with other network.
So, I'm asking if you think that uninstalling the custom ROM may affect negatively to my phone.
Hi.
It is a Sprint based ROM, so going back to stock shouldn't affect it.
You could run the RUU that is available on the official US HTC website. But please realize that Sense 7 isn't out yet. If you go back to stock you will get the update via OTA when it is available.
Here is a link for the Sprint Harman/Kardon RUU. Scroll down to the manual update instructions and read them. The RUU download is at the end of them.
All data on your phone will be erased, so make a backup of anything important to you.
Also, if you are S-On, you will have to relock your bootloader first. If S-Off it is not necessary. You can check if you are S-Off by booting to your bootloader (turn off your phone, then boot it by holding power+vol. down).
If you are S-Off, it will say at the top under where it says ***unlocked***.
If not you will have to use ADB/fastboot to relock it with this command:
fastboot oem lock
Then run the RUU, and you will be stock Lollipop.
xunholyx said:
Hi.
It is a Sprint based ROM, so going back to stock shouldn't affect it.
You could run the RUU that is available on the official US HTC website. But please realize that Sense 7 isn't out yet. If you go back to stock you will get the update via OTA when it is available.
(New user so can't post urls). Scroll down to the manual update instructions and read them. The RUU download is at the end of them.
All data on your phone will be erased, so make a backup of anything important to you.
Also, if you are S-On, you will have to relock your bootloader first. If S-Off it is not necessary. You can check if you are S-Off by booting to your bootloader (turn off your phone, then boot it by holding power+vol. down).
If you are S-Off, it will say at the top under where it says ***unlocked***.
If not you will have to use ADB/fastboot to relock it with this command:
fastboot oem lock
Then run the RUU, and you will be stock Lollipop.
Click to expand...
Click to collapse
Wow, really appreciate this! So, once I've done that and no more, will the phone be free of the custom ROM? And what about the root stuff, will it be gone as well?
NotCarlos said:
Wow, really appreciate this! So, once I've done that and no more, will the phone be free of the custom ROM? And what about the root stuff, will it be gone as well?
Click to expand...
Click to collapse
You will have the stock ROM and will be unrooted, yes.
Help with RUU
xunholyx said:
You will have the stock ROM and will be unrooted, yes.
Click to expand...
Click to collapse
Can't get my phone recognized in HTC Sync Manager, as the process of the manual update indicates. I already toggled debug usb, re-installed software, selected mode on the phone, etc. And nothing seems to happen. Can't find either the solution online. And the Sync manager is at the last update.
i just bought a used, AT&T variant HTC One A9 from eBay. the seller said that the phone is unlocked, and when i put my Rogers SIM card, it works fine. however, when i go to the bootloader menu (by pressing the volume down and power button simultaneously), the following information appears on the screen after the phone boots:
hTC download mode
*** LOCKED ***
htc_hiaeul PVT S-ON
LK-1.0.0.0000
[email protected]
OpenDSP-6.8.5.00190-8952_1013
OS-1.27.502.5
Nov 12 2015, 15:40:38(656287)
it's interesting that it says "LOCKED" (which i am assuming to mean bootloader-locked and not carrier-locked). unfortunately i didn't know that AT&T variants are not going to get any more updates before buying this phone. i am looking for guides on how to unlock an AT&T A9 and how to update it to the latest Android available for this phone. i am not interested in 3rd party ROMs and only would like to use original HTC ROMs, but updated to Nougat.
could anybody point me to the correct set of instructions to unlock the bootloader, (probably do a S-OFF, if needed), and install the latest HTC ROM for One A9? (FYI, i am comfortable with command line utilities and have previously rooted my HTC One S.)
I did this to my AT&T One A9 not to long ago, I got tired of waiting for AT&T to update the phone to Nougat.
Go here: https://www.htcdev.com/ and follow the instructions to unlock the bootloader.
S-Off using Sunshine (how I did it).
Change CID and MID to the appropriate values.
Flash latest RUU.
Not too bad a process all in all.
^ great! thank you very much.
did you flash an official HTC ROM or a custom ROM? and how do you find your phone with Nougat, in terms of compatibility/bugs/etc.?
i noticed that there is an option called "OEM Unlocking" in the Settings. i am guessing that i should check that option before proceeding with the unlocking process, am i right?
darxider said:
i am guessing that i should check that option before proceeding with the unlocking process, am i right?
Click to expand...
Click to collapse
Right
Also note that if you are going to flash a Nougat RUU, you'll need to update your firmware to 2.xx.xxx.x before flashing a 2.xx.xxx.x RUU. See the FAQ #4 in the RUU thread. ATM, this is only required when upgrading from M to N or when downgrading from N to M using a RUU.
alray said:
Right
Also note that if you are going to flash a Nougat RUU, you'll need to update your firmware to 2.xx.xxx.x before flashing a 2.xx.xxx.x RUU. See the FAQ #4 in the RUU thread. ATM, this is only required when upgrading from M to N or when downgrading from N to M using a RUU.
Click to expand...
Click to collapse
When I converted my phone to a retail unlocked version the Nougat update hadn't been released yet, so I actually got an OTA from 6.0.1 to 7.0 which did the firmware update for me. It should be possible for people to do the same thing if they are patient. But yeah I'm not entirely sure if I'd wait right now either.
megatomic said:
When I converted my phone to a retail unlocked version the Nougat update hadn't been released yet, so I actually got an OTA from 6.0.1 to 7.0 which did the firmware update for me. It should be possible for people to do the same thing if they are patient. But yeah I'm not entirely sure if I'd wait right now either.
Click to expand...
Click to collapse
thanks for the info. but could you elaborate on what you mean by "...if they are patient"?
darxider said:
thanks for the info. but could you elaborate on what you mean by "...if they are patient"?
Click to expand...
Click to collapse
It's possible to force the situation by flashing directly to a Nougat version but first you have to manually flash the firmware to the 2.x version before you can do that. I'm finding out the hard way that flashing the firmware is not a simple task like it is on devices like the OnePlus One.
^ ah, i see. so if i understood correctly, if i just convert my A9 from AT&T to retail (dev?) version but stay with Marshmellow and not do the switch to Nougat, i would be getting a OTA Nougat update which will take care of everything automatically, right?
That's what happened to my phone. I did the same exact thing.
I'm in the same situation, how exactly did you change from at&t to retail version?