Related
I was wondering how I will be getting my update, I have a debranded sensation, was virgin mobile. I am on rogers but I was thinking how will I get the update if rogers doesn't Carry this phone so I'm thinking they will not push the version for my phone? So how do I get it? I doubt ill get the virgin ota?
dr mcknight said:
I was wondering how I will be getting my update, I have a debranded sensation, was virgin mobile. I am on rogers but I was thinking how will I get the update if rogers doesn't Carry this phone so I'm thinking they will not push the version for my phone? So how do I get it? I doubt ill get the virgin ota?
Click to expand...
Click to collapse
you are soff right?
you know for sure that virgin in your region rolling out ICS for sensation?
anyways here is the guide to debrand/rebrand
debrand/rebrand guide
ganeshp said:
you are soff right?
you know for sure that virgin in your region rolling out ICS for sensation?
anyways here is the guide to debrand/rebrand
debrand/rebrand guide
Click to expand...
Click to collapse
no, im stock other than debrand... i bought it second hand so im not 100%sure
dr mcknight said:
no, im stock other than debrand... i bought it second hand so im not 100%sure
Click to expand...
Click to collapse
just check the soff status on bootloader
(to go to bootloader first uncheck fastboot [settings->power->fastboot]
then switch off phone
then hold power + vol down button...it would take you to bootloader)
if in bootloader your device says soff then follow the guide ive linked to rebrand it...or change the brand to virgin
if not tell me your HBOOT version (it will be there at bootloader too)
ganeshp said:
just check the soff status on bootloader
(to go to bootloader first uncheck fastboot [settings->power->fastboot]
then switch off phone
then hold power + vol down button...it would take you to bootloader)
if in bootloader your device says soff then follow the guide ive linked to rebrand it...or change the brand to virgin
if not tell me your HBOOT version (it will be there at bootloader too)
Click to expand...
Click to collapse
s-on hboot 1.18.0000
dr mcknight said:
s-on hboot 1.18.0000
Click to expand...
Click to collapse
ok also you are on stock GB rom right...so probably nothing got changed...
I have a debranded sensation, was virgin mobile. I am on rogers
Click to expand...
Click to collapse
by this did you mean you got a debranded sensation (World Wide) and just changed the sim of virgin and using rogers sim ?
then all is fine for you ...just check for the OTA updates...you will get it when they roll out ICS.
PS:
To confirm 100% that your phone is debranded or not...
you need to give me small info.
if you have adb/fastboot setup...(if you dont have setup use this guide )
then run the command "fastboot getvar cid" and post the cid back...I'll verify it
ganeshp said:
ok also you are on stock GB rom right...so probably nothing got changed...
by this did you mean you got a debranded sensation (World Wide) and just changed the sim of virgin and using rogers sim ?
then all is fine for you ...just check for the OTA updates...you will get it when they roll out ICS.
PS:
To confirm 100% that your phone is debranded or not...
you need to give me small info.
if you have adb/fastboot setup...(if you dont have setup use this guide )
then run the command "fastboot getvar cid" and post the cid back...I'll verify it
Click to expand...
Click to collapse
Cid bm __001
dr mcknight said:
Cid bm __001
Click to expand...
Click to collapse
Based on the cid database provided ..it is called BM network..so anyways.it seems like your phone hasn't been modified a bit..so you'll get ics OTA irrespective of the sim you are using now..if you want ICS OTA of other countries like Europe etc then you need to do first SOFF(which is possible for your HBOOT ) then you need to follow the guide I've provided to rebrand it..you need to rebrand it with cid HTC___001(verify this) which is Europe unbranded cid and it has got ICS ota.so if you rebrand it with the above mentioned cid you'll automatically get ota..the only downside to this is you'll lose SOFF..which is a immense requirement to fully support installing custom roms.
sent from my blazing fast pyramid through sonic waves
OKAY so this might be an odd question, mods can delete as soon as I get an answer that's ok but I have this situation:
I live in South Africa, where the HTC One S has not yet been released. On holiday in the Netherlands I decided to buy a SIM lock free HTC One S. With my old South African SIM card cut to size, the roaming features worked fine but I received the first OTA system update via a Dutch WiFi Network while still on holiday. This brought my device to software version 1.78.401.2 with Android 4.0.3. However I am now back in South Africa and although the HSDPA works fine here and such, I've seen the new 2.21 Android 4.0.4 update has since been released for Euro devices. I have checked my CID which is HTC__E11 or similar but checking under settings doesn't show any updates. Will the update become available to my device and can I receive the OTA update from South Africa?
I'm stock unrooted.
Thanks in advance. If suggested ideas include checking HBOOT please advise as I don't know how to check on this device, just came from an HTC Wildfire with CM.
AFAIK you'll get OTA updates based on your CID and it doesn't matter which carrier you're on. I'd imagine you'll get your OTA soon even if you pull your SIM out and move to Antarctica as long as you have Wifi. Never mind your hboot version it doesn't matter if you're on stock software, but if you want to check hold volume down for a while when powering on
Matt,
If the CID is HTC__E11 it means it is Europe unbranded. You should receive the OTA soon. But if you're like me and you're impatient, you can run the 2.21 RUU. But this will update your HBOOT and is currently not rootable. Checking for the HBOOT is the same as the Wildfire - Vol Down + Power.
Sent from pixels to more pixels
usaff22 said:
Matt,
If the CID is HTC__E11 it means it is Europe unbranded. You should receive the OTA soon. But if you're like me and you're impatient, you can run the 2.21 RUU. But this will update your HBOOT and is currently not rootable. Checking for the HBOOT is the same as the Wildfire - Vol Down + Power.
Sent from pixels to more pixels
Click to expand...
Click to collapse
Not true, I ran the RUU and rooted it. It's what I'm running on my phone at the moment.
T-MobileUS HTC One S running Stock Rooted 2.21.
fmedrano1977 said:
Not true, I ran the RUU and rooted it. It's what I'm running on my phone at the moment.
T-MobileUS HTC One S running Stock Rooted 2.21.
Click to expand...
Click to collapse
But your phone was also rooted before the HBOOT upgrade? Other people have said they can't root it after the upgrade, if they haven't rooted before.
usaff22 said:
But your phone was also rooted before the HBOOT upgrade? Other people have said they can't root it after the upgrade, if they haven't rooted before.
Click to expand...
Click to collapse
The first thing I did with my new device was run the 2.21 RUU followed by unlocking the bootloader and rooting it.
The only problem I had was running CWM recovery (probably my error) but no problems at all with TWRP recovery.
usaff22 said:
But your phone was also rooted before the HBOOT upgrade? Other people have said they can't root it after the upgrade, if they haven't rooted before.
Click to expand...
Click to collapse
Correct, but isn't root system related and not firmware related?
T-MobileUS HTC One S running Stock Rooted 2.21.
usaff22 said:
Matt,
If the CID is HTC__E11 it means it is Europe unbranded. You should receive the OTA soon. But if you're like me and you're impatient, you can run the 2.21 RUU. But this will update your HBOOT and is currently not rootable. Checking for the HBOOT is the same as the Wildfire - Vol Down + Power.
Sent from pixels to more pixels
Click to expand...
Click to collapse
Hey Usaff
Thanks for the advice, was slow to realize it was vol down+ power until the softkey lights flash
The RUU flashes and wipes the phone, correct? Strangely I remember using an RUU to get Froyo on my old Wildfire when it was still stock and somehow that functioned like an OTA and never wiped my data, might be remembering incorrectly, was a long time ago...
EDIT
Correct, but isn't root system related and not firmware related?
Click to expand...
Click to collapse
Is that the distinction between S-OFF and rooting? I know rooting gains access to Android system files and stuff, then is S-OFF just a security flag for HTC devices? Noob questions I know...
fmedrano1977 said:
Correct, but isn't root system related and not firmware related?
T-MobileUS HTC One S running Stock Rooted 2.21.
Click to expand...
Click to collapse
It is system related but firmware also greatly affects rooting, especially if a firmware upgrade upgrades your HBOOT version.
Sent from pixels to more pixels
Hi, guys.
I'm using a HOX AT&T with stock rom 1.85, and yes I did the deed, root, spoof CID and unlock bootloader, install TWRecovery. Now I live in Asia so no LTE here, and I don't like the ATT's bloatware at all, also I read some complaints about LTE radio constantly drains battery if not in coverage. Some flashing is in order, but before diving in I have some questions:
1./ Is the spoofed CID permanent? I mean now my HOX is 11111111 CID - like a retail/generic one's, what will happen if I flash a RUU from another operator? Does a RUU from AT&T make my phone's CID go back to before and I need to start the whole nine yards again?
2./ I understood flashing a stock rom will un-root the phone okay, but what about bootloader? A RUU flashing wont re-lock the bootloader, or will it?
3./ Like I said, I can't stand bloatware, in the roms section I saw this RUU_EVITA_UL_ICS_40_S_hTC_Asia_WWE_2.23.707.2_Radio_0.19as.32.09.09_L_10.104b.32.25L_release_271654_signed and a newer RUU 2.29 Asia somewhere else, are those unbrand roms - like the ones come with retail/operator-free One XL?
4./ I saw warnings about this specific rom, 2.20 of AT&T, no root, new hboot... all basically spells trouble, but what about branded roms with higher version number like O2 DE 2.29 or Vodafone DE 2.33, are they kosher?
5./ AFAIK, Europe and Asia has no LTE capability, so if I flash a radio rom from European operators or Asia does it disable the LTE radio in my AT&T HOX?
That's all, thank you guys in advance.
6./ In the thread radio & RIL , I read that update 2.2x will replace HBOOT and make old radio not compatible, is it because new HBOOT resize the radio partition smaller? So if I flash a custom rom based on Asia RUU 2.29 for example (not the dreaded 2.20 ATT), my current HBOOT will be replaced by new HBOOT as well? With no S-OFF, we can not flash HBOOT so will I be stuck with the new HBOOT and therefore, new radio roms only?
Looking forward to hearing from HOXL gurus. Thanks.
linhldz said:
Hi, guys.
I'm using a HOX AT&T with stock rom 1.85, and yes I did the deed, root, spoof CID and unlock bootloader, install TWRecovery. Now I live in Asia so no LTE here, and I don't like the ATT's bloatware at all, also I read some complaints about LTE radio constantly drains battery if not in coverage. Some flashing is in order, but before diving in I have some questions:
1./ Is the spoofed CID permanent? I mean now my HOX is 11111111 CID - like a retail/generic one's, what will happen if I flash a RUU from another operator? Does a RUU from AT&T make my phone's CID go back to before and I need to start the whole nine yards again?
2./ I understood flashing a stock rom will un-root the phone okay, but what about bootloader? A RUU flashing wont re-lock the bootloader, or will it?
3./ Like I said, I can't stand bloatware, in the roms section I saw this RUU_EVITA_UL_ICS_40_S_hTC_Asia_WWE_2.23.707.2_Radio_0.19as.32.09.09_L_10.104b.32.25L_release_271654_signed and a newer RUU 2.29 Asia somewhere else, are those unbrand roms - like the ones come with retail/operator-free One XL?
4./ I saw warnings about this specific rom, 2.20 of AT&T, no root, new hboot... all basically spells trouble, but what about branded roms with higher version number like O2 DE 2.29 or Vodafone DE 2.33, are they kosher?
5./ AFAIK, Europe and Asia has no LTE capability, so if I flash a radio rom from European operators or Asia does it disable the LTE radio in my AT&T HOX?
That's all, thank you guys in advance.
Click to expand...
Click to collapse
1. Spoofed CID is permanent unless you go in and change it back. For all intents and purposes, it's permanent.
2. Actually to run an RUU, you must relock your bootloader or it will fail. As long as you have your unlock token or Super CID, you can re-unlocked your bootloader once you are done and flash SuperSU to get root back. Or just flash a pre-rooted stock ROM.
3. Not sure. Make sure to fully read the post. I have never run an RUU for a phone with an RUU from a different carrier. Again, make sure you read about that one.
4. You just don't want to run the 2.20 RUU for AT&T. It will make it so you can not flash radios at all and you must flash boot.img from adb or from Android terminal emulator. It is just the 2.20 RUU that will do this. A custom ROM will not, so no need to worry.
5. It will not disable LTE, but if you don't have an LTE APN in your phone it shouldn't be looking for LTE and you can also turn off the LTE radios on any non-AT&T ROM.
My recommendation after all of your questions would be to flash a pre-rooted stock ROM or a cleaned up debranded ROM (like Clean Rom, but there are more out there). Change the APN to what ever country you are in and do the *#*#4636#*#* thing to turn off your LTE radio. Again, the *#*#4634#*#* to turn off the radio will not work on a stock AT&T ROM.
Thank you, Butters. Still I've got one more question - added in the first post.
linhldz said:
Thank you, Butters. Still I've got one more question - added in the first post.
Click to expand...
Click to collapse
If you are flashing a custom ROM, you do not have to worry about your HBOOT being changed. It doesn't matter what the custom ROM is based on. You only have to worry about that with running an RUU (which is from HTC for a specific carrier).
If you have 1.85 on your phone, just keep a 1.85 RUU on your computer and flash away any ROM you want. If something gets messed up and you need to RUU, you'll always have that 1.85 RUU with the old hboot.
Running the 2.20 RUU, you will lose all ability to flash any radios, so you will be stuck with the AT&T 2.20 radio. Being that you are overseas, I would not recommend this because it may not (probably isn't) the best radio for your use case.
If you want a stock ROM, there are pre-rooted versions posted in Development that are flashable from TWRP. Easier then relocking the bootloader and running the RUU, and no threat of hboot changes (or having to research what was changed in the hboot).
Or just install a custom ROM. They are often based on recent firmware versions, but already de-bloated, and with awesome customizations added.
After all, if you want to run a stock RUU, why did you unlock the bootloader in the first place?
Thank guys, really appreciate. Just flashed CR5 with confidence, so far so good.
Early assessment: Quite smooth, the LTE problem with AT&T stock rom has disappeared, battery life improves greatly.
I have a rooted S One that seems to have lost its root access and signal after OTA update from Bell - the phone was bought on eBay as an "unlocked sealed" item, which wasn't the case. I want to restore the phone to stock and SIM unlock it for use with Telus, but there's no 1.84 RUU for Rogers available. I just want to confirm I can't restore the phone to stock without the 1.84 RUU. Or, if there's an alternative to get it working again, what that alternative might be and where to start. Thanks for any help.
tykidd66 said:
I have a rooted S One that seems to have lost its root access and signal after OTA update from Bell - the phone was bought on eBay as an "unlocked sealed" item, which wasn't the case. I want to restore the phone to stock and SIM unlock it for use with Telus, but there's no 1.84 RUU for Rogers available. I just want to confirm I can't restore the phone to stock without the 1.84 RUU. Or, if there's an alternative to get it working again, what that alternative might be and where to start. Thanks for any help.
Click to expand...
Click to collapse
Post is a bit confusing. You talk about Bell, Rogers, and Telus all at once. Also, if you got an OTA update from Bell, you will only be able to execute an RUU that has an hboot version equal to or higher than your current one.
If you are looking for a more recent RUU than the ones posted on http://forum.xda-developers.com/showthread.php?t=1543588
then I suggest you send a private message to Football, the user who started that post. He helped me find newer Bell Mobility RUUs (which have since been posted to the thread).
Your other option is to do a bootloader downgrade (see the dev post on this, its a bit complicated), and then you can flash other radios from http://forum.xda-developers.com/showthread.php?t=1998270
If you dont want to downgrade your bootloader, you can always flash to a CM10 base (AOSP type) ROM, such as PAC Man, or Jelly Bam, etc. Then you can flash radios without having to downgrade.
Again, though this is all assuming that your true problem is with you baseband radio and now switching carriers has made your reception poor...
Also remember you will have to relock your bootloader before you execute an RUU, otherwise it wont take (that and a correct bootloader version)
AKToronto
Thanks for the info. The phone is a sim-unlocked Fido unit. It was running on Bell before the OTA update.
Here are the specs:
Android version: 4.0.3
HTC Sense version: 4.0
Software number: 1.84.631.9
HTC SDK API level: 4.11
HTC Extension version: HTCExtension_403_1_GA_4
Build number: 1.84.631.9 CL64348 release-keys
Is the "build number" the RUU? I'll try Football, but do I need the Rogers (Fido) RUU?
Thanks.
you can not execute an rogers ruu on a bell phone, the cid wont match
there is an app on play who will display you the cid and the original network; like that you'll know exactly what phone do you have in hand
you just have to unlockit after and you will be able to useit in whatever network you want
Thanks. Ran CID getter and says it's ROGER001. So I've confirmed that I need a Rogers file. And I would like to unlock it, but from what I've read I cannot restore back to Rogers 1.70 because the unit has been updated to 1.84. I have read that if I can find a 1.84 Rogers file, I can use that to restore the unit. This is the next thing I need to confirm. I appreciate your help.
I think that is almost correct. You can change the CID to the Rogers one using the same technique as posted in the super Cid thread in the development section. Normally though you can't flash an older ruu as the hboot version can't be older. But You may also want to try posting a message in the bootloader downgrade thread that is stickied to n the development section. I think if you downgrade your bootloader and also do a minor hex edit to a partition you can flash an older RUU. I have downgraded my bootloader but haven't tried flashing an older ruu so I can't say for sure.
Sent from my HTC One S using xda premium
Thanks again. So I can assume the CID is already Rogers, yes? I don't want to change it. My hope is that I can use the All in One Toolkit (one of the sticky posts) to bring the phone back to stock and then SIM unlock it for use with Telus. If I run the Toolkit, and use cbetso's instructions from the "How to Return to Stock" post (after adding the stock recovery to the folder). If I locate the Rogers 1.84 RUU, can I run it without downgrading?
don't assume, your cid is rogers ROGER001, so there is absolutely no way your phone could download and execute an update from bell.
so I can not understand what has bell to do in this.
if you just want to use it on telus network, you just have to unlock it, you don't even need root for this. and the phone will work just fine.
the root is needed when you want to change ROM, radio, debloat and others.
one of the others will be tweaking the build.prop file to achieve maximum capacities of your 3g/4g desired network
Thanks - it's a difficult story to tell, really. It was a Rogers unit, SIM unlocked to work with Bell. It was on Bell's network for two months, and an OTA update caused major radio and reception problems. It will not keep a network signal anymore. I have tried other SIMs in the unit and it will not recognize them, nor start up with the "Enter Unlock Code" screen to SIM unlock it. It's my understanding that I need to return it to stock by finding the Rogers RUU file that matches the software version on the unit, which is 1.84. This is my very limited understanding of the issue, but it's what I've been able to figure out.
if it was a rogers device, and you did not change the CID, you get the ROGER001 cid with the app, your phone is still a rogers device
doesn't matter in which networks was used, for the two months before you get it, and by you after
as long the cid stays ROGER001, your phone will remain a rogers device, unlocked to be used in different networks.
so there is absolutely no way an OTA update, from bell or telus could be the source of your problems, because your phone will not download or execute an ota update from other networks
same for rogers ota update, as long the phone was unlocked, will not execute OTA updates, even the updates will be downloaded on the phone
your connection problem came from other reasons;
however it you want to return the phone to rogers stock, the key number is HBOOT version;
you can execute any RUU with HBOOT version higher or equal with your present version on the phone
if somehow you're on a very high version and you can not find the appropriate RUU, we can always downgrade RUU, check development section for tutorial
it's not very simple, but as long you're ok and you understand the steps, go for it, it is doable.
if you have root, you might try different radios before all above, or maybe a custom rom; just an ideea; as long the phone is not soft bricked or physically damaged, there is no reason a custom rom will not work
Thanks for the information. There seems to be other problems with the unit, including it won't delete all data after hard reset, it won't recognize other networks when other SIMs are put in, it has been upgraded past the 1.70 stock Rogers RUU. I wish I could get it figured out or I may have to sell it as is. Appreciate your help.
factory reset in fastboot didn't work?
means you're on some custom rom with non stock recovery?
have you tried to flash a stock recovery? any of them, whatever you'll find around here; there are no much difference in term of facilities between them;
then you should be able to restore phone to factory defaults
try find somewhere All in one kitt one S v1.0; there is stock recovery in it, and flashing is easy
in v1.1 there is no more stock recovery
donwload ruu or open up ruu..when it first starts go into your windows manager and in the link section delete what you have in that section like c:/program files and replace it with %temp% and it will find two encrypted folders with a big letter/digit name and they will show you what time they were opened . open them up and find rom.zip copy it to your desktop and then extract it somewhere safe .. in the folders in rom.zip you will see recovery_signed.img rename it recovery.img and flash it via hasoons tool kit provided in the development section..just in case you ever run into this again
Thanks. Can I flash a stock recovery in the All in One Toolkit without having the proper RUU version I need? Will this allow me to factory reset the phone, and the radio issue is another unrelated problem? The unit is supposed to be SIM unlocked, but when I put another carrier's SIM in, I still have no radio and I do not see the screen that says "unrecognized SIM" with an "enter unlock code" option.
tykidd66 said:
Thanks. Can I flash a stock recovery in the All in One Toolkit without having the proper RUU version I need? Will this allow me to factory reset the phone, and the radio issue is another unrelated problem? The unit is supposed to be SIM unlocked, but when I put another carrier's SIM in, I still have no radio and I do not see the screen that says "unrecognized SIM" with an "enter unlock code" option.
Click to expand...
Click to collapse
Not sure about your radio issue, that would require testing out different radios. You can do that on a higher hboot by trying AOSP ROMS and using the Radio flasher in the dev forums.
As for flashing stock recovery you can also just use the following link: http://loadbalancing.modaco.com/down...ery_signed.img
The stock recovery doesnt really change from RUU to RUU. You dont need a particular recovery to use a particular RUU, as far as I know.
Thanks - you wanna take another look at that link? It didn't seem to be anything. Or do I need to change the extension?
tykidd66 said:
Thanks - you wanna take another look at that link? It didn't seem to be anything. Or do I need to change the extension?
Click to expand...
Click to collapse
http://loadbalancing.modaco.com/download.php?file=ville_recovery_signed.img
Try that. Sorry about the other link
I maybe miss it, but you never said what is the exact status of the phone right now;
it is booting? it is working on some network? at least partially like voice only? what ROM are you on? what HBOOT?
Hi there - thanks for getting back to me and asking. The phone seems to be booting normally and always has been. It is not able to recognize any new SIM card. It's a Rogers unit, and when I add my Telus SIM it does not go to the "Unrecognized SIM" screen, it actually registers the TELUS network for a moment, then the radio gives no signal.
How can I check the ROM, 'cause I have no idea. Is the HBOOT in these specs?
Android version: 4.0.3
HTC Sense version: 4.0
Software number: 1.84.631.9
HTC SDK API level: 4.11
HTC Extension version: HTCExtension_403_1_GA_4
Build number: 1.84.631.9 CL64348 release-keys
Thanks again.
for the Hboot version you have to reboot in fastboot
for recovery reboot into recovery
for the ROM version, once booted normaly you have to go into about phone > software
are you sure you have the right settings for Telus APN? for some reasons, the phone will not registered to network, if apn setting are wrong;
at least for me, which I'm opposite to you as I have a telus phone and using it in fido network, if I dont have Fido APN setted up, the phone does not register to network
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?