Database Users

XT1684 (UK) - Returning to Stock

Hi all.
I've asked this question in numerous threads so, to be fair to all the others whose questions I'm getting in the way of, I thought I'd post it here and wait with baited breath for a potential solution.
I very recently bought an XT1684 (3GB/32GB) UK G5 Plus. I installed all the official OTAs and got myself up to firmware version NPNS25.137-33-11. All was well, amazing battery life, but needed root for some apps. The steps I followed are roughly as follows:
1. Unlocked bootloader: I did this the usual way, got my code, chucked it into fastboot etc voila, job done.
2. BOOTED Twrp: I did this so I could attempt to back everything up without modifying, for purpose of returning to stock. It didn't work, I could not back anything up nor could I install magisk or a custom kernel. My Twrp would not read the internal storage and said something about formatting data. I ended up formatting data, which actually formatted the whole damn thing, losing my stock ROM completely.
3. FLASHED Twrp: By this point I had to, as I had limited access to the internet outside of my phone so put a lineage ROM on my phone and some gapps and flashed it.
4. Installed magisk 15.3
5. Installed Alize kernel: I did this because I was looking for improved battery life over the lineageos kernel. It hasn't been better.
So that's where I am. I have two main reasons I need to return to stock:
1. The battery life was better on my stock firmware.
2. Whenever I use lineage, I find my signal not to be as strong, and it seems to randomly lose all signal for a few seconds several times an hour, usually affecting my data more than voice calls. This is absolutely not something that happened on stock. I dunno if it's related to baseband or something, but it happens and I don't like it.
My main issue is I have seen several retUS versions of the firmware above, and lots about many other XT16xx models but nothing about my XT1684 and no fastboot images for retGB. I'm comfortable flashing pretty much anything via Twrp as I have a full backup of all partitions including OEM, system image etc but these were taken after installing lineage. I'm just totally not comfortable fastboot flashing anything except the exact correct firmware, as I've had this phone literally a week.
If anyone can help me locate the right firmware, or advise me how I could possibly return totally to stock, that would be amazing. I can provide any logs or other information required, but may need walking through more obscure commands as I am only technically proficient enough to do a basic fastboot flash, Twrp, etc.
Many thanks for reading and my apologies to all of those whose threads I've muscled in on up to this point.

Filmware is here https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/
And there is a tool that automates flashing in the development section here..
https://forum.xda-developers.com/g5-plus/development/toolkit-moto-g5-plus-toolkit-root-t3605203

Firmware - https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/
How to flash - https://forum.xda-developers.com/g5-plus/how-to/solution-to-flash-stock-romfactory-t3691396
?hope it helps.

Thing is, there's no xt1684 version or retgb version. I fear it could be the wrong one, can't afford to replace phone so can't risk hard bricking it.
Could someone confirm that these are safe to flash for me? Thanks for the replies, though.

Your filmware is there yes? Having said that mine is a xt1685 the same filmware number as yours but mine is euret dual SIM. Sold by Amazon UK

My confusion is that I thought they were for US models.

Well US version has no NFC but had a compass.
Has yours?

Mine has NFC and no compass lol!

darkglobe87 said:
Mine has NFC and no compass lol!
Click to expand...
Click to collapse
Seems to be typical for EU G5+ devices, NFC but no compass.
The retail firmwares don't appear to have region restrictions, hence no labelling for retEU/retGB/retUS etc. However, as you may have noticed, flashing the incorrect build for your region causes all sorts of headaches, including loss of SIM network.
That being said, you know what firmware you need (NPNS25.137-33-11) and that particular firmware was only released for EU/UK devices to the best of my knowledge. India/Brazil, US and other territories had different firmware builds released.
So, you should be okay with flashing that particular firmware - but please verify you have the correct firmware downloaded and the correct flashing instructions, and take your time in flashing.
Also, if you choose to re-lock your bootloader, re-locking your bootloader will unfortunately not restore your warranty with Motorola (which is 2 years now for EU/UK users at least). However, UK consumer laws may cover you in the eventuality of hardware repairs, just be careful. Also, re-locking will erase your device and requires firmware of the same build or newer than what is currently on your device.
Good luck whatever you decide.

I have the UK version and have gone back to stock a few times, I used this thread, and the linked firmware is the same as UK one. The guide is for bootloader locking, but ignore that part if you only wish to return to stock.
https://forum.xda-developers.com/g5-plus/how-to/how-to-lock-bootloader-potter-version-t3694952

Problem with my G935A

Hi, I got a S7 Edge SM-G935A from AT&T at the end of December.
That same night I tried to root my phone(i got a bootloop), and I didn't know the bootloader was locked.
So I re-flashed a SM-G935U rom, but I would like to go back to the basic one in order to get a new start(SM-G935A), without root and nothing.
Knowing that I have a problem connecting to the wifi, maybe because of the rom that doesn't match.
And also i dont have samsung updates, i'd like to have the latest one im currently on 7.0.
If someone could help me to get my phone with original firmware, I'd be grateful.

Ok, first off, you can run any US/Qualcomm variant software on your device. Unless you just have a hankering for AT&T firmware, the U firmware will work just fine. Either way, find a full copy of either A or U firmware and ODIN it down, and you will essentially factory reset your device in the process.
There are links to both in this forum. I personally prefer U because it is faster and less bogged down with carrier crap, but if you are an AT&T customer, there are decent enough reasons to stick with A.
NOTE: you may need to use Prince Comsy's ODIN tool if you get a mismatch error. Unfortunately, there is no universal ODIN tool, but as a general rule, if you are CHANGING variants you need Prince's. If you are writing over the same version, you need the official.

jshamlet said:
Ok, first off, you can run any US/Qualcomm variant software on your device. Unless you just have a hankering for AT&T firmware, the U firmware will work just fine. Either way, find a full copy of either A or U firmware and ODIN it down, and you will essentially factory reset your device in the process.
There are links to both in this forum. I personally prefer U because it is faster and less bogged down with carrier crap, but if you are an AT&T customer, there are decent enough reasons to stick with A.
NOTE: you may need to use Prince Comsy's ODIN tool if you get a mismatch error. Unfortunately, there is no universal ODIN tool, but as a general rule, if you are CHANGING variants you need Prince's. If you are writing over the same version, you need the official.
Click to expand...
Click to collapse
Im not living in the USA and AT&T doesnt exist where i live, but sometime i have a issue with my wifi "internet may not be available" is because of the rom?

Leqz said:
Im not living in the USA and AT&T doesnt exist where i live, but sometime i have a issue with my wifi "internet may not be available" is because of the rom?
Click to expand...
Click to collapse
Then this is easy. Go download the U firmware and use Prince's ODIN to convert it to a G935U. If you aren't on an AT&T network there is zero reason to keep your device on A firmware, starting with the fact that you will never get updates. (AT&T firmware will only update if you have an AT&T SIM installed.)

jshamlet said:
Then this is easy. Go download the U firmware and use Prince's ODIN to convert it to a G935U. If you aren't on an AT&T network there is zero reason to keep your device on A firmware, starting with the fact that you will never get updates. (AT&T firmware will only update if you have an AT&T SIM installed.)
Click to expand...
Click to collapse
Only add-on is to perform this from a Windows 7 pc and not 10. Prince kept crashing on 10 and worked fine on 7.

Bricked Axon 7, no phone functions just Data

I have an A2017U but since changing from stock rom B35 to B01, I have lost all sim card and phone functions. I've tried all these - B05, B15, B10, B35, B20,, B19, but all firmwares are identified as "not for this machine" error, and all relevant apps and "About Phone" information now indentifies the model as A2017G, which it certainly isn't. Is there a rollback set of firmwares I could use to regain mobile network functions back to this phone. Firmware installed is B01, and when I bought the phone it had B35 installed. I don't have a PC just mac, so all those nifty workarounds, I can't do.
Please Help

@Pigeon357
Hello,
Assuming you have stock recovery, you can get ZTE_A2017UV1.1.0B35 firmware here:
https://www.getdroidtips.com/zte-axon-7-stock-firmware-collections/
Normally the download file should be a zip, unzip it, you will find update.zip file. Put update.zip on the root
of your SD card. Then go to Phone Settings, search for update, it should tell you your current phone version
and the update it finds and suggests. Then tap on update : it will update for you then reboot automatically. First reboot
should be a little long (< 5 min). Then you should be back all right to B35 and phone OK since the right modem for A2017U is included
in the ZTE_A2017UV1.1.0B35 firmware.
Note : I guess you have applied incorrect A2017G firmware to your A2017U, this would explain the phone problem (incorrect modem).

Fixed!
dnlilas said:
@Pigeon357
Hello,
Assuming you have stock recovery, you can get ZTE_A2017UV1.1.0B35 firmware here:
https://www.getdroidtips.com/zte-axon-7-stock-firmware-collections/
Normally the download file should be a zip, unzip it, you will find update.zip file. Put update.zip on the root
of your SD card. Then go to Phone Settings, search for update, it should tell you your current phone version
and the update it finds and suggests. Then tap on update : it will update for you then reboot automatically. First reboot
should be a little long (< 5 min). Then you should be back all right to B35 and phone OK since the right modem for A2017U is included
in the ZTE_A2017UV1.1.0B35 firmware.
Note : I guess you have applied incorrect A2017G firmware to your A2017U, this would explain the phone problem (incorrect modem).
Click to expand...
Click to collapse
I used B03 stock room and still had no phone functions, then I did another SD Card update with the B20 and it worked, I have all the phone functions back and am on the latest stock Oreo build too, I'm so glad to get it back, as I was using a spare Android phone on version 5, it was so slow, but it's fixed now.

Pigeon357 said:
I used B03 stock room and still had no phone functions, then I did another SD Card update with the B20 and it worked, I have all the phone functions back and am on the latest stock Oreo build too, I'm so glad to get it back, as I was using a spare Android phone on version 5, it was so slow, but it's fixed now.
Click to expand...
Click to collapse
The key part of the method was to remove the Google account before updating in recovery mode

G981U and G981U1 Firmware Links and Flashing Discussion Here

For those who aren't already aware, G981U is the model number of all of the US carrier versions of the S20. The G981U1 is the model number of the same device, but sold by Samsung SIM unlocked and with no carrier bloatware. Firmware is 100% interchangeable among these models: any U or U1 firmware version can be flashed to any U or U1 device at any time, assuming that you're not trying to downgrade the bootloader. A "U to U" or "U1 to U1" flash does not require a factory reset, but changing from one firmware to the other will require one. Also, U firmware is identical for the 4 base files (AP, BL, CP, CSC) for each individual build, no matter which carrier it comes from. So if you download 2 different carrier versions of the exact same build, the 4 base files will be identical. Where the firmware differs is in the USERDATA file - that's where the carrier bloatware and customizations reside.
Manual Odin flashing is designed for those who:
- want to manually update to a newer version of U firmware on their U device, either because they don't want to wait for their carrier's OTA or because OTAs aren't working on their device, or a different carrier got a new feature/patch before they did
- want to flash U1 firmware to their U device
- want to convert from U1 firmware to carrier U firmware
- want to convert from one carrier's U firmware (with all apps and bloatware) to a different carrier's U firmware (with all apps and bloatware)
For those who aren't already aware, anyone can now download firmware for almost any Samsung device any time that they want, via SamFirm or Frija. There are threads and info about them here on XDA so I won't waste time explaining - do a search if you're not already familiar with these tools. But they only provide whatever the latest/newest/current version is - nothing older. I pay for a subscription to a site that gets the official releases (usually) before they hit SamFirm/Frija, so that's where my files come from. However, I don't have unlimited bandwidth on the site, and it's also quite time consuming to download the files, zip them up, and upload them to AFH. And, I do threads like this for every single Sx and Note x model - so I won't be uploading every single version. The only full builds that I upload are ones where I get access to a new bootloader and/or Android version early, before they hit SamFirm/Frija.
This is not a "beginner's guide to Odin flashing" -type post/thread, so I won't list basic, step-by-step flashing instructions. My threads are geared towards those who already know what they're doing. If you're new to manually flashing Samsung firmware (or haven't done it in a long time), I recommend you consult one of those "beginner's" guides- there are tons of them here on XDA.
Happy flashing!
U firmware: https://www.androidfilehost.com/?w=files&flid=305577
U1 firmware: https://www.androidfilehost.com/?w=files&flid=305578
(Quebec tends to be the fastest download mirror, if it gives you that option)
Notes:
- DON'T QUOTE THE OP WHEN YOU REPLY, kthx
- I have lots of threads just like this one for other Samsung flagships, if it interests you. For those who have already made use of my previous threads for a different device and are upgrading to an S20, welcome back
- My zips are compressed extra small for space and bandwidth savings. The default Windows extractor can't handle it, so you'll need a 3rd party tool like 7zip, WinRAR, etc
- My naming method for folders on AFH is: build - bootloader - Android version
So "SAT - 1 - 9.0" means the full build number ends in SAT, it's bootloader version 1, and it's Android 9.0. When bootloader and Android versions increment, the first build to have those changes will have its folder notated appropriately.
- HOME CSC file keeps data intact; using the other CSC will wipe data. Flashing USERDATA will also wipe data.
- Since AT&T doesn't allow their firmware to be publicly available (for any of their devices), I'll try to always upload at least one USERDATA per bootloader increment for AT&T (and Cricket, if they get this model). I'll also upload any full builds if AT&T is the only carrier to get that specific build, because you won't be able to find the files anywhere else.
- For identifying USERDATAS, and to know what region/CSC to use in SamFirm/Frija:
AIO = Cricket (not available via SamFirm/Frija)
ATT = AT&T (not available via SamFirm/Frija)
BST = Boost Mobile
CCT = Xfinity Mobile (Comcast)
CHA = Spectrum Mobile (Charter)
SPR = Sprint
TMB = T-Mobile
TMK = Metro PCS
USC = US Cellular
VZW = Verizon (available via SamFirm/Frija, but Manual Entry is required - Auto will not work)
XAA = U1 firmware
- the correct procedure for switching from one carrier's firmware to another is:
1. Flash full U1 firmware package including non HOME CSC
2. Upon boot, insert a SIM of the carrier whose firmware you want
3. Watch for the popup that says "reboot to apply new carrier settings" etc, and do it
4. After that restart completes, reboot back to Download mode and flash the full U firmware package, with the USERDATA file of the carrier whose firmware you want

Pre-release notes:
1. I do not have one of these and do not plan to acquire one, so I have no idea if anything can actually be flashed at this moment - I'm just providing the firmware. Like all other models, I'm assuming patched Odin is needed for this, but it wouldn't surprise me if a new version is needed for this specific device. There's only one way to know though, so as soon as someone gets their hands on one and can try this, please let us know.
2. I don't know if using the HOME CSC will actually save data. I don't get access to that file straight from the source - I have to decompile the regular CSC, remove the parts that initiate the factory reset, and then re-compile it. Based on the S10 and Note 10, I've done what I think will avoid a factory reset. But the S20 has some new partitions, so we won't know for sure until someone tests it. So if you're willing to be that guinea pig, you're responsible for taking proper steps to avoid an FRP lock, make sure your data is backed up, etc

So I flashed with Odin with my unlocked from Samsung U1 firmware to the T-Mobile U firmware because I wanted the advanced messaging. Only issue in the beginning was not using the patched Odin, but once I did, no problems.
Tools:
Downloaded from this previous thread, post #2, with Modified Odin and Samsung Drivers https://forum.xda-developers.com/s10-plus/how-to/sm-g975u-firmware-downloads-tmo-spr-att-t3908657
Since it's been awhile since I've done flashing or Odin, I followed this basic guide:
https://forum.xda-developers.com/s10-plus/how-to/guide-g975f-flashing-megathread-faqs-t3936704
Of note, only needed the files from the TAW folder only, did not need the T-Mobile specific U firmware as resetting the phone with a T-mobile sim automatically loaded it.
My quick rundown:
1)Extract the G981U_TAW firmware file you just downloaded. You should get 5 files:
AP (System & Recovery)
BL (Bootloader)
CP (Modem / Radio)
CSC_OXM (OXM CSC file, will wipe your phone)
HOME_CSC_OXM (OXM CSC file, will NOT wipe your phone)
2.)In Modified Odin I added each file to it's respective slot EXCEPT for HOME_CSC as I wanted to do a clean factory reset
3) Put the S20 in Download/ Odin mode. 2 different ways as outlined here https://www.youtube.com/watch?v=ZPSWEL6-gWg&t=8s
4) Once the phone was detected in the COM port number in Odin, I clicked the start button and waited til Odin said "PASS". One thing I noticed was the phone didn't reboot all the way automatically, it actually went into recovery mode and I ended up having to do a factory reset through there because at first it would bootloop and take me back into recovery mode, but after doing a factory reset in recovery mode it restarted just fine with the T-mobile firmware along with the t-mobile apps and advanced messaging working as it should be.

I want to flash my unlocked samsung s20 so I can use the ATT Volte and wifi calling but will rom eventually get released

jameslee2 said:
I want to flash my unlocked samsung s20 so I can use the ATT Volte and wifi calling but will rom eventually get released
Click to expand...
Click to collapse
If you're saying that you want AT&T apps and bloatware and features, then all the files that you need are already linked in the OP

I'm worried that I already know the answer, but i'm asking it anyways. I'm currently on a SM-G981N (South Korean version), which is a Snapdragon865 phone. I'm wondering if I can change my firmware to the SM-G981U version to get rid of the bloatware on my phone. For what I read for other phone's this wouldn't work. Perhaps I should start looking for an unbloated SM-G981N rom? Thanks!

tijsva said:
I'm worried that I already know the answer, but i'm asking it anyways. I'm currently on a SM-G981N (South Korean version), which is a Snapdragon865 phone. I'm wondering if I can change my firmware to the SM-G981U version to get rid of the bloatware on my phone. For what I read for other phone's this wouldn't work. Perhaps I should start looking for an unbloated SM-G981N rom? Thanks!
Click to expand...
Click to collapse
I'm assuming the flash would fail. But there's only one way to know for sure

I'll first try an unbloated korean firmware, until I'll find out if crossflashing between different region phones is safe and working...

tijsva said:
I'll first try an unbloated korean firmware, until I'll find out if crossflashing between different region phones is safe and working...
Click to expand...
Click to collapse
Is the a recovery for sm-g981u?
Sent from my SM-G981U using Tapatalk

Bee101 said:
Is the a recovery for sm-g981u?
Sent from my SM-G981U using Tapatalk
Click to expand...
Click to collapse
I don't understand what you're asking

Tried to flash the unbloated (my assumption at least) of the Korean rom: KOO. Followed the correct steps, flashed without problems but bloatware was not removed, also bootlogo of the original carrier doesn't disappear.
@iBowToAndroid, have you tested this method yourself with the S20 series? Flashing from unlocked to carrier firmware should always work I would say, but the other way around, have you got confirmed results for the S20 series?

SM-G981U Carrier Aggregation for Europe
I have S20 SM-G981U1 that i flashed with SM-G981U with no problems but is there any way to make CA to work in Europe?
Any help will be greatly appreciated because i have way lower mobile data speed in EU with my US unlocked phone...

tijsva said:
Tried to flash the unbloated (my assumption at least) of the Korean rom: KOO. Followed the correct steps, flashed without problems but bloatware was not removed, also bootlogo of the original carrier doesn't disappear.
@iBowToAndroid, have you tested this method yourself with the S20 series? Flashing from unlocked to carrier firmware should always work I would say, but the other way around, have you got confirmed results for the S20 series?
Click to expand...
Click to collapse
For U and U1 firmware, yes. You'll have to look elsewhere for discussions on Korean firmware

So you have tested flashing from (US) carrier firmware to unlocked carrier on the S20 succesfully? All bloatware and carrier bootscreens removed?

Any firmware (compatible with U1) that has CSC feature enabled for native call recording?

tijsva said:
So you have tested flashing from (US) carrier firmware to unlocked carrier on the S20 succesfully? All bloatware and carrier bootscreens removed?
Click to expand...
Click to collapse
@iBowToAndroid. Have you got confirmed results that bloatware is indeed removed including boot animations when changing from a US carrier branded phone to the international firmware on the Galaxy S20? I'm starting to wonder if there have been new restrictions in the S20 series that won't allow the CSC to be modified and therefor bloatware/carrier logo's won't be removed.

tijsva said:
@iBowToAndroid. Have you got confirmed results that bloatware is indeed removed including boot animations when changing from a US carrier branded phone to the international firmware on the Galaxy S20? I'm starting to wonder if there have been new restrictions in the S20 series that won't allow the CSC to be modified and therefor bloatware/carrier logo's won't be removed.
Click to expand...
Click to collapse
International firmware can't be flashed to a US model - never have been able to, never will be able to. Just because it's bloatware free doesn't make it "international". But yes, flashing the U1 firmware package removes all of the bloatware - it's been that way ever since the S7

iBowToAndroid said:
International firmware can't be flashed to a US model - never have been able to, never will be able to. Just because it's bloatware free doesn't make it "international". But yes, flashing the U1 firmware package removes all of the bloatware - it's been that way ever since the S7
Click to expand...
Click to collapse
Sorry, typo, should have been "unlocked" firmware.
You still haven't answered my question though Have you got confirmed results? Proof? I see you had good results for the S10 series, but so far I can't seem to find similar results for the S20 series.

dtothesquare said:
So I flashed with Odin with my unlocked from Samsung U1 firmware to the T-Mobile U firmware because I wanted the advanced messaging. Only issue in the beginning was not using the patched Odin, but once I did, no problems.
Tools:
Downloaded from this previous thread, post #2, with Modified Odin and Samsung Drivers https://forum.xda-developers.com/s10-plus/how-to/sm-g975u-firmware-downloads-tmo-spr-att-t3908657
Since it's been awhile since I've done flashing or Odin, I followed this basic guide:
https://forum.xda-developers.com/s10-plus/how-to/guide-g975f-flashing-megathread-faqs-t3936704
Of note, only needed the files from the TAW folder only, did not need the T-Mobile specific U firmware as resetting the phone with a T-mobile sim automatically loaded it.
My quick rundown:
1)Extract the G981U_TAW firmware file you just downloaded. You should get 5 files:
AP (System & Recovery)
BL (Bootloader)
CP (Modem / Radio)
CSC_OXM (OXM CSC file, will wipe your phone)
HOME_CSC_OXM (OXM CSC file, will NOT wipe your phone)
2.)In Modified Odin I added each file to it's respective slot EXCEPT for HOME_CSC as I wanted to do a clean factory reset
3) Put the S20 in Download/ Odin mode. 2 different ways as outlined here
&t=8s
4) Once the phone was detected in the COM port number in Odin, I clicked the start button and waited til Odin said "PASS". One thing I noticed was the phone didn't reboot all the way automatically, it actually went into recovery mode and I ended up having to do a factory reset through there because at first it would bootloop and take me back into recovery mode, but after doing a factory reset in recovery mode it restarted just fine with the T-mobile firmware along with the t-mobile apps and advanced messaging working as it should be.
Click to expand...
Click to collapse
i got advanced messaging by just inserting a T-Mobile SIM into my unlocked s20, it restarted the phone and i even have the wifi calling too

tijsva said:
Sorry, typo, should have been "unlocked" firmware.
You still haven't answered my question though Have you got confirmed results? Proof? I see you had good results for the S10 series, but so far I can't seem to find similar results for the S20 series.
Click to expand...
Click to collapse
The proof is already here in the thread. Many users have already done it

KB2007 On KB2005 Android 12

I have spent the better part of the evening trying to figure out what is wrong with the full update package for Android 12 for NA/Global. This is the one way out of the many I tried, that reliably worked for the KB2007 T-Mobile USA device to get it to running Android 12 without issues on the North American/Global firmware.
This ideally is for those of us that have a KB2007 that used the MSM Tool conversion to the EU firmware. Using Local Update does not fully convert to the NA/Global, even when using a full update package, which leaves the device with issues. For some reason, when updating to the KB2005 Android 12 using the full firmware image, you lose the second SIM slot, which just makes it worse. After plenty of flashes to figure this out. I have figured out a complicated mess of a way to do so.
I tried going to a couple of the full updates before Android 12 from the EU and still had issues after the update to Android 12 with performance. That is why I decided upon this longer method. Update using the full KB2005 image to Android 12. Easiest place to get it is from Oxygen Updater. Install it via Local Update. Download the rollback app, install it, and download the rollback package to flash through the rollback app. Rolling back to KB2005 using the downgrade image returns dual-SIM to the KB2007. That will have wiped your device so proceed through the setup until finished. Download Oxygen Updater again, download the stable KB2005 Android 12 incremental update through the System Updater, install it, and you should be as close what a KB2007 can get to a KB2005. I tried the full package update but that always disables dual-SIM after updating to Android 12, whether you do a factory reset before the flash and after or not.
Having an MSM Took to directly convert the KB2007 to KB2005 might have made this somewhat easier.

Sadly, it didn't survive a reboot. SIM 2 is still shown, but disabled. There is no way to enable it that I have found, but at least it is reading the info from the SIM 2. Does anyone know of a way to force the toggle for SIM 2?

dang i was coming here to see if anyone was able to do this and or had issues doing so. looks like if we are on an unloced tmo version phone we might be stuck with oos11 till things get figured out if they do. bummer. i really wish i had not waited when they put them on sale and got the normal 8t vs this tmo version those were sold out by the time i saw the sale though. just like i still cant figure out how to get vowifi / wifi calling working on this ive tried everything i could find online and nothing works to add those settings back
oddly im on the latest version of oos11 on the kb2007 converted and i can see sim 1 and 2 but sim 2 is greyed out. i actually was trying to get that working on oos11 and for me it does not work. did you have it working on 11?

Same problem with 12 here. We accidentally updated to 12 via the OTA update and it not only gave us the same symptom (SIM 2 visible, but disabled), but it also screwed up internet connectivity on SIM 1. Calls and text still seemed to work, but internet only via WiFi.
I spent last night and a good chunk of today troubleshooting it, and finally just went back to fully operational latest version of 11 via MSM and local update. It would be nice to be on the latest version, but browsing through the OnePlus forums, it looks like 12 is still a hot mess anyway.

bummer hopefully someone will figure it out sooner or later. i really dont want to go back to the tmobile rom in order to update

I just talked to OnePlus support center and they confirmed unlocked version will not be stock again Once they will finish selling T-Mobile version webpage will be cleaned from any 8T info. I really want to get unlocked for 399. and now only way to get this go for KB2000 CN version that sill stocked. The price for T-Mobile version is good 349 but based on conversion mess I don't want go for that. Also I am sure TM will stop on OOS11 and will not rollout OOS12 ever.

i agree ^^ any updates from anyone on this? any type of workarounds? this sucks i wish i would just went with the one off amazon instead of directly through oneplus now. we have three here we love the phone but i am not sure we will ever be able to upgrade now.

bigfry said:
Same problem with 12 here. We accidentally updated to 12 via the OTA update and it not only gave us the same symptom (SIM 2 visible, but disabled), but it also screwed up internet connectivity on SIM 1. Calls and text still seemed to work, but internet only via WiFi.
I spent last night and a good chunk of today troubleshooting it, and finally just went back to fully operational latest version of 11 via MSM and local update. It would be nice to be on the latest version, but browsing through the OnePlus forums, it looks like 12 is still a hot mess anyway.
Click to expand...
Click to collapse
Can you check the about page after upgraded to OOS12 is this sill showing wrong picture and missing some info?

bigfry said:
Same problem with 12 here. We accidentally updated to 12 via the OTA update and it not only gave us the same symptom (SIM 2 visible, but disabled), but it also screwed up internet connectivity on SIM 1. Calls and text still seemed to work, but internet only via WiFi.
I spent last night and a good chunk of today troubleshooting it, and finally just went back to fully operational latest version of 11 via MSM and local update. It would be nice to be on the latest version, but browsing through the OnePlus forums, it looks like 12 is still a hot mess anyway.
Click to expand...
Click to collapse
I have the same issue you had with the network on mobile data. I downloaded oos 11 and used magisk to install os11 to keep root , however I still have data isdue on the mobile network. Fine on wifi. Any suggestions?

you may want to try to use the msm tool to go back. or try the posted downgrade tool. i personally used the msm tool to go back to stock then re upgraded to latest 11. i hope i dont get hit with it myself. this was on my daughters phone.

Thanks for sharing this instruction!
So basically:
0) Oxygen Updater can be used to download the full/incremental OOS 11/12 kb2005 images mentioned below. (Probably also need to use MSM tool to rebrand as EU version before all these?)
1) System Update - Local Update to install OOS 12 kb2005 (full);
2) "Rollback app" to OOS 11 (rollback);
3) Regular system update to OOS 12 (incremental).
It seems pretty reasonable. Would you instruct more on what "rollback app/package" you use? This is the closest I found online: https://www.droidwin.com/downgrade-oneplus-8-pro-8t-to-oxygenos-11-android-11/ but please correct me if it is not the right one.
Does this method still work now? Do you have dual-sim dual volte/wifi calling working?

jllll said:
Thanks for sharing this instruction!
So basically:
0) Oxygen Updater can be used to download the full/incremental OOS 11/12 kb2005 images mentioned below. (Probably also need to use MSM tool to rebrand as EU version before all these?)
1) System Update - Local Update to install OOS 12 kb2005 (full);
2) "Rollback app" to OOS 11 (rollback);
3) Regular system update to OOS 12 (incremental).
It seems pretty reasonable. Would you instruct more on what "rollback app/package" you use? This is the closest I found online: https://www.droidwin.com/downgrade-oneplus-8-pro-8t-to-oxygenos-11-android-11/ but please correct me if it is not the right one.
Does this method still work now? Do you have dual-sim dual volte/wifi calling working?
Click to expand...
Click to collapse
I just tried this method and dual sim is not working.

alphahere said:
I just tried this method and dual sim is not working.
Click to expand...
Click to collapse
Thanks. I can't even get rollback app working so I gave up. Dual sim immediately after MSM again. Then I just did regular system update to the latest OOS software. Probably just switch to pixel next year.

I can fix this issue but for this i need
Unpack repack rom which is not possible
I try all kitchens but not workable if anyone can help me to unpack repack rom then i can fix it i even got the problem spot
Just need to test it now
If anyone able to do this just tell and i can fix it
But make sure don't mention payload dumper
I need extract whole rom sys ven prod etc

jllll said:
Thanks. I can't even get rollback app working so I gave up. Dual sim immediately after MSM again. Then I just did regular system update to the latest OOS software. Probably just switch to pixel next year.
Click to expand...
Click to collapse
Concur - Oneplus needs dual sim in the US. The carriers have blocked this for years but that wall in falling. Almost all the flagship and some midrange phones have e-sim and physical sim. So dual sim is here to stay. Oneplus needs to get on board the train.

I have this some issue after upgrading to Android 12. Is there any way to roll-back to Android 11, WITHOUT losing data and needing to wipe? And would it then allow the dual-sim to be working again?

Also, has anyone else tried the above method and had success with having a dual-sim Android 12 using the T-mobile KB2007?

raven911 said:
Also, has anyone else tried the above method and had success with having a dual-sim Android 12 using the T-mobile KB2007?
Click to expand...
Click to collapse
I can fix but need to unpack repack rom
If anyone can guide me tu unpack
System_ext
System
Vendor
Product odm then I'll make fix rom for this
Can build for samsung but in this I'm stuck with dynamic partitions

Mr Hassan said:
I can fix but need to unpack repack rom
If anyone can guide me tu unpack
System_ext
System
Vendor
Product odm then I'll make fix rom for this
Can build for samsung but in this I'm stuck with dynamic partitions
Click to expand...
Click to collapse
If you unpack / repack, then will we lose SafetyNet and Widevine?

raven911 said:
If you unpack / repack, then will we lose SafetyNet and Widevine?
Click to expand...
Click to collapse
Ofcourse not its not rooting process
Even i can do with rooted device but if have fully rw access