Hi
Will i get OTA's with SuperCID, especially Oreo OTA?
Thanks
If the phone is rooted, no.
AFAIK Supercid is no longer valid so the cid must match the firmware you're flashing.
I'd take a shot in the dark and say no.. Good question though..
I just tested it, and can't say definitely.
Flashed 1.27.401.5 RUU with superCID, so i guess it's still kinda valid.
After first boot i got instantly notified for 401.12 update, which ran without problems.
Oreo update notification doe never showed up, the update search always said i'm on the latest
version. I then changed the CID to international unlocked, and instantly recieved oreo update.
So i don't know, probably better sticking with offical CID's when it comes to OTA's.
Related
Guys,
I have found a definite issue regarding trying to debrand and flash the 2.3.4 OTA update to my Bell debranded sensation...Here are my steps and results...
1. Performed Revolutionary on shipping Bell Canada Sensation
2. Changed CID to 11111111 via fastboot.
3. Flashed generic UK 1.35.401.1 software via RUU file.
4. Downloaded 2.3.4 OTA update.
5. Try to install the OTA update.zip from recovery, it errors out with Status 7 error. No matter what CID I use, I always get this error status 7.
6. Change CID to HTC__E11 to try and get the OTA update automatically, Downloads and then gives me a "variant system software" error when it goes to install. I've never heard of or seen this error before.
7. Run Revolutionary again and then flash the update.zip. It appears to successfully flash, but when the phone reboots, all I get is a black screen. the phone makes noises and appears to be functioning somewhat, but screen is black.
8. I am now thinking, great, I just bricked my phone...
9. Reboot into hboot. It still shows Bootloader of 1.17.0011, which is strange because the OTA is supposed to update it to 1.18.0000.
10. I then change the CID to 11111111 and reflash with the 1.35.401.1 RUU and thank god the phone is back to working condition.
It appears that there is either a hardware difference or something really low level that is being changed with this new update and it might not work properly with the different radio from the Bell Canada version with the 850/1900 radio, but I don't understand why flashing to the 1.35.401.1 RUU works fine. If anyone else can shed any light on this or give me any hints, I would appreciate. I thought my experiences might help the devs out there further understand the new OTA and the Sensation software/hardware. My end goal is to have the most up to date stock unbranded software installed on my Sensation. I am using with AT&T if anyone is wondering.
Y2J
y2jdmbfan said:
Guys,
I have found a definite issue regarding trying to debrand and flash the 2.3.4 OTA update to my Bell debranded sensation...Here are my steps and results...
1. Performed Revolutionary on shipping Bell Canada Sensation
2. Changed CID to 11111111 via fastboot.
3. Flashed generic UK 1.35.401.1 software via RUU file.
4. Downloaded 2.3.4 OTA update.
5. Try to install the OTA update.zip from recovery, it errors out with Status 7 error. No matter what CID I use, I always get this error status 7.
6. Change CID to HTC__E11 to try and get the OTA update automatically, Downloads and then gives me a "variant system software" error when it goes to install. I've never heard of or seen this error before.
7. Run Revolutionary again and then flash the update.zip. It appears to successfully flash, but when the phone reboots, all I get is a black screen. the phone makes noises and appears to be functioning somewhat, but screen is black.
8. I am now thinking, great, I just bricked my phone...
9. Reboot into hboot. It still shows Bootloader of 1.17.0011, which is strange because the OTA is supposed to update it to 1.18.0000.
10. I then change the CID to 11111111 and reflash with the 1.35.401.1 RUU and thank god the phone is back to working condition.
It appears that there is either a hardware difference or something really low level that is being changed with this new update and it might not work properly with the different radio from the Bell Canada version with the 850/1900 radio, but I don't understand why flashing to the 1.35.401.1 RUU works fine. If anyone else can shed any light on this or give me any hints, I would appreciate. I thought my experiences might help the devs out there further understand the new OTA and the Sensation software/hardware. My end goal is to have the most up to date stock unbranded software installed on my Sensation. I am using with AT&T if anyone is wondering.
Y2J
Click to expand...
Click to collapse
I would venture to guess you're not aware that you should probably not (at least not now), do an official FOTA/OTA on an unauthorized S-OFF Sensation.
The official HTC 2.3.4 OTA that came out a few days ago, LOCKS your device. It puts it back into an S-ON state.
Unless something has changed, if you have S-OFF via Revolutionary....stay far away from official HTC updates.
Something has changed...revolutionary now supports the new "locked" bootloader!
Hoggles said:
I would venture to guess you're not aware that you should probably not (at least not now), do an official FOTA/OTA on an unauthorized S-OFF Sensation.
The official HTC 2.3.4 OTA that came out a few days ago, LOCKS your device. It puts it back into an S-ON state.
Unless something has changed, if you have S-OFF via Revolutionary....stay far away from official HTC updates.
Click to expand...
Click to collapse
I'm well aware that the the official HTC 2.3.4 OTA locks the device. As long as I have a debranded Sensation running the latest and greatest firmware/software, that is all I am looking for. And now that Revolutionary works on the new HBOOT there shouldn't be much trouble getting back to the original shipping software. I still am curious as to what is causing this "Error Status 7" error code.
So how can I update my sensation with s-off?
A bug in me from being updated.
That would really interest me too! don't want to be S-ON again to make this update. Another question (maybe off topic): how can i update to new S-OFF version 04pre4? I'm now on 03pre7.
Hi
I have the exact same problem as yours, what can we do to update it?
Same on Swisscom-branded phone
I tried the OTA on my swisscom phone, it reboots and I get an exclamation mark with a blue droid. Waited 10 minutes just in case, but no change.
Removed battery and rebooted. Phone still ok, but not updated obviously.
I'm not sure it will remove S-OFF, but I don't care, HTC provides an official procedure for that and we have what we need.
But I need this update to work on my rooted, S-OFF stock sensation. Will try again anyway...
EDIT: I tried going into recovery and manually flashing the OTAxx.zip file, but it gave me an assert_failed: check_cid!? Though I never changed the phone CID! So why propose me an update on my phone if it's the wrong one??? Not sure I want to change the CID of my phone now.
Ive been trying to find out why my phone (with the 2.21 RUU currently installed) wont receive OTA's
The bootloader is relocked and it has the stock recovery, so it should work
Ive been reading a lot of posts (more ore less about this) some are hinting that RUU's dont give OTA's
Does anyone have a definitive answer, does a RUU get OTA's or not?
Thanks
Lacuna666 said:
Ive been trying to find out why my phone (with the 2.21 RUU currently installed) wont receive OTA's
The bootloader is relocked and it has the stock recovery, so it should work
Ive been reading a lot of posts (more ore less about this) some are hinting that RUU's dont give OTA's
Does anyone have a definitive answer, does a RUU get OTA's or not?
Thanks
Click to expand...
Click to collapse
Yes RUU are stock HTC roms. It's like a super factory reset. But you can only receive an OTA if the region your phone is in offers an OTA. More specifically if there is an OTA offered to CID that your phone has.
dc211 said:
Yes RUU are stock HTC roms. It's like a super factory reset. But you can only receive an OTA if the region your phone is in offers an OTA. More specifically if there is an OTA offered to CID that your phone has.
Click to expand...
Click to collapse
OK, thanks, that was exactly the kind of info i needed !
Check the build number on the phone.
If there is a r2 behind it then you wont get the update since there are ni developed paths from a r2 to something else.
M9x3mos said:
Check the build number on the phone.
If there is a r2 behind it then you wont get the update since there are ni developed paths from a r2 to something else.
Click to expand...
Click to collapse
Thanks fo the info, i allready now have a ruu 2.31 installe which DOES get ota's, but if i run into this problem again, i'll check that !
Or type
*#*#CHECKIN#*#* into the dialer. Then check for updates.
Sent from my locked, tampered ville
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 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?