How To Guide How to change regions on Oneplus 10T 5g via Update/Downgrade Packages:

Search This thread

tungninh

Member
Jul 23, 2015
28
9
there is a much easier way. For example I am in IN and want to move to EU. I just need to download ROLLEDBACK A12 IN and downgrade to 10T, then download A13 EU and update locally. DONE
 
so after doing some research i have found 2 things... 1. Oppo has ppl watching this thread and has made some alterations to the files that come from their server... these are the only 3 i had original copies of but of those 3 ALL of them had a minor difference and all were modified right after I revealed that i had success in converting my 2419 to a 2415. Once i stated that i was able to move to ANY region using my method, SOMETHING very small was changed in the files, and that is the reason the 2417 OTA fails to load in Local Updater... look at the attached pic. View attachment 5766339
So this is obvious that they are onto us and this is a concern to them. You should still be able to Downgrade with any region that has an Android 13 Beta. The technique works perfectly as long as you have a full version of Android in between.... AKA 12 to 13, and 13 back down to 12. And because of the new links in the OP, you can use local update to roll back to 2413 or 2415 ... I do believe that a 2417 beta is imminent and as such there will have to be a 2417 rollback released with it. There is still no danger with using this method, as you see because if the file is incompatible. local updater will fail to populate it!

Now for the second thing. OPPO used to have a special function in the Engineering Mode, which when activated would re-enable Fastboot Mode on the devices temporarily. This function is still alive in these devices today, only it has been hidden away deeper. This was confirmed to me after another grueling 3 hr chat with OnePlus technicians. I was told, "Sir we do not have access to the program you are asking about. The MSM Tool is completely maintained and controlled by OPPO division, and while yes we are under their ownership, there remains 2 different divisions in our company" ... 1st tech ..... "Sir you would need to enable fastboot mode so that you can flash the original firmware to your device, if it is failing to boot. You need to enter "Factory Mode" and input the locking code which is calculated from your device Imei. Once you have entered the code, you will be instantly rebooted into fastboot mode, and there you will be able to flash the signed firmware to it. Do not attempt to flash unsigned firmware as it will fail if your device comes with a locked bootloader." ..... 2nd tech......

This is not FastbootD he is talking about, because in FastbootD you do not need "Factory Mode" to enter it, and a little bit further research found this post which almost exactly matches what the tech told me!

Factory Mode Unlock

Of course the same way that Oppo decided to interfere with me, they also interfered with this method. They went and simply unlocked engineering mode completely in our devices, which made the screen where you enter the code, vanish. But i guarantee you, that based on some digging into the system files that our devices have running, i found several processes mentioning privileged processes that have simple flags that are called when "pre-boot" functions are initiated. Now in YEARS of time that OPPO has had to deal with the programming these devices they have never managed to actually eliminate "Fastboot Mode". They just become sneakier in hiding it behind user accessible operations. I am fully confident that the same thing applies here. While i dont have all the answers, i implore you all to apply the knowledge i have given and help find just where it is hidden in ours.

To call Engineering Mode on our phones, the code was changed to:
*#899*

Maybe the unlock screen has been hidden in here under a different label... maybe they created a new dialer code, but make no mistake, OPPO must have a need for this mode for repairing our phones otherwise they would eliminate it completely. Oppo is a 2-bit chinese company who is too cheap to design a new OS, and therefore somewhere, there is going to be a method to gain what were looking for. That is all i have for now.... but i am still digging. ( i have managed to get an additional 2 weeks to hold onto the 10t before i have to drop it into the return box and hand it over. So any ideas that you come up with, you DO NOT have to risk your personal devices! I can try ANYTHING on mine with absolutely ZERO ****s to give, as to it getting bricked! BRAINSTORM PPL! let me know what you come up with and i will try it!)
I just used the one+ tool and I see that there are probably 100-150 engineering codes identified using the tool. Incase you don't have the tool here's a link to the one I have. check it out maybe you might be able to find something https://1drv.ms/u/s!AqDQuxOzB8wghvoaD02pqZRbUL4eXw
 

jld2k6

Senior Member
Jan 21, 2011
58
12
Local updated doesn't detect the rollback package on TMobile, no idea where to go from here
 

jld2k6

Senior Member
Jan 21, 2011
58
12
just got this from another OnePlus thread here. says it has almost 100% success with all OnePlus devices https://optool.daxiaamu.com/wiki_pctool
Says it works on all except operator versions, I don't know if that applies to the T-Mobile OnePlus 10 pro or just the 10t since only the 10t is carrier exclusive. Also, it only roots the phone and unlocks the bootloader, it won't help you to switch regions, which is the problem everyone is trying to solve :(
 
Says it works on all except operator versions, I don't know if that applies to the T-Mobile OnePlus 10 pro or just the 10t since only the 10t is carrier exclusive. Also, it only roots the phone and unlocks the bootloader, it won't help you to switch regions, which is the problem everyone is trying to solve :(
root won't make it easier to accomplish? I believe there is a downgrade flasher and firmware flash in version 13
 

jld2k6

Senior Member
Jan 21, 2011
58
12
root won't make it easier to accomplish? I believe there is a downgrade flasher and firmware flash in version 13
It would make it easier but the method to change regions no longer works because OnePlus patched it, I don't know why they are so hellbent on stopping people from unbricking their phones or allowing them to flash like they have for years
 
I have a TMobile OP10T that I tried to convert to NA, after following the instructions, when the phone rebooted, I kept getting a "(app) has been disabled due to security strategy" with any app that I try to open. I did format the device and am able to navigate through the phone on wifi, but if I insert my SIM card I get the error again and can't do anything but reboot the phone. I do have a sim locked OP10T. Wondering what I did wrong....?
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    (Moderators, please make this post a sticky, and i will keep it updated of any changes or issues that might come up in future builds, thanks)

    To clarify things.... I am the dude who figured out how to side-step from model to model... I have went from 2419 (android 12 .11), to 2413 (android 13), Down to 2415 (android 12 .08), then 2417 (android 12.10), back up to 2415 (android 13), down to 2415 (android 12 .05), 2417 (android 12 .08) and finally a FULL sidestep 2417 (12 .08) to 2415 (12.08) which the latter is supposed to be impossible, with downgrade package, yet i am sitting here and i have done it!

    !!! Credit for discovering the Downgrade Packages, and Information about OPPO/Oneplus Bootloader restrictions goes to, Maamdroid , and EtherealRemnant !... Without their most important input, i would not have had the courage, and knowledge of exactly what i was going up against, in attempting a region change on a BL/Carrier locked device. They were the geniuses who helped me derive this method, i was just the guinea pig willing to go Dr. Frankenstein on my T-Mobile locked, handicapped device. !!!!

    **" I TAKE NO RESPONSIBILITY FOR BRICKS, BOOTLOOPS, SYSTEM CRASHES, INSTABILITY.... WORLD FAMINE, 6G MUTANT INVASION, NANO BOTS ENTERING YOUR FANNY, TRUMP RE-ELECTION, CIVIL WAR, YOU FORGETTING TO DO THAT THING YOU WERE SUPPOSED TO DO EARLIER.... 72 HOUR KARDASHIAN MARATHONS, GLOBAL WARMING, YO MAMA SLAPPING YOU, OR ANY OTHER SIDE EFFECT FROM ATTEMPTING THESE IMAGINARY WORDS THAT YOU THINK YOU ARE READING, YET YOU ARENT BECAUSE READING HASNT BEEN INVENTED YET IN YOUR TIMELINE B.C.5182 , AND THE FACT THAT YOU ARE A MEAT POPSICLE... PROCEED ONLY IF YOU FEEL FULLY CONFIDENT IN THE ANALYSIS YOU ARE ABOUT TO IMAGINE READING , AND THEN REPEAT AFTER ME: ***

    " I AM FULLY AWARE OF THE RISKS INVOLVED WITH MAKING MODIFICATIONS OR EXPLOITING FUNCTIONS THAT WERE NOT INTENDED TO BE USED IN THE METHOD I AM ABOUT TO USE THEM FOR. AND IF A ZOMBIE APOCALYPSE ERUPTS DUE TO ANY MISTAKE I MADE FLASHING THE FILES LISTED HERE, I WILL NOT EVER ... EVER... EVEN CONSIDER ANY WORDS READ FROM HERE, AS HAVING ANY THING BUT A TRULY POSITIVE EFFECT UPON MY LIFE! " .... PROCEED!

    The ONLY requirements of the downgrade packages on the 10T, is that you CANNOT downgrade to a build version that is lower than your current one IF you are attempting to region hop while staying on the same version of android.... (ie. you cannot go from A12 .10, to A12 .08... but you can go from 2415 A12 .05 to 2413 A12 .08) Got that?

    One other important thing is that in the zip file that contains the payload.bin, there is an additional file named payload_properties.txt. You need to open that file in a text editor, and look for the line about the "Update_Engine_Check_Disable".... by default it is set to 0 which makes Local Updater check to see if the models match in some files. A mismatch will just cancel your update. Local updater is KEY to doing any Region Swaps, especially with a locked bootloader. This is because Local Updater does NOT perform any of the flashing itself... that whole progress bar is your phone verifying the contents of the payload.bin to make sure that all files in the manifests are present, and compatible with your device... it actually KEEPS YOU FROM BRICKING your phone because of a mismatched file/ or bad flash. If Local Updater detects ANYTHING that is not interchangeable, it will crash during the verification, your phone will reboot, and start normally as if you never attempted an update.

    Local updater is also not capable (afaik) of applying ANY changes to the Bootloader, or boot partition. As well it seems limited in its ability to even fully access some userdata files. All of my developer options were in exactly the same state that they were prior to each flash. The only deviation of that , was in DOWNGRADING from A13 to A12... but every upgrade, no matter which model fw used seemed to have done the 'Data, system, bin, etc, var, lib, and kernel, plus a few others' , but the truly secure partitions such as 'aboot, xbl, and system-priv' + deep memory blocks werent touched i believe.

    The END result of each region swap will be your device FULLY IDENTIFYING as the model for that region.. (ex. 2419 will now show as 2415 if Global, 2413 if India, or 2417 if North America)
    This will change EVERY TIME you flash a different region, and Local Updater will block you from flashing if it detects a lower build, EXCEPT for the 2415 Downgrade Package. So ALWAYS use that as a base if you want to go to another region. <ie. to go from 2413 to 2417, i recommend first flashing the 2415 downgrade, which will put you on A.08 build, then you can update to any region you want, even the Android 13 builds.... but if you want to go to a different region and back to 12, you must use that 2415 Downgrade or Local updater will stop you. The 2415 is a signed official rollback package direct from oneplus, so it allows you to downgrade from pretty much any version.

    ***** KEY FACT ***** This ONLY applies to OTA upgrade and downgrade packages that come in a single zip file that contains 3 items. Payload.bin Payload_properties.txt and Meta_Inf folder ... If you unzip the fw that you dl, and it contains anything other than those 3 that i just named, you either have a Fastboot package, a Full system package, or a MODIFIED package which you should NOT interact with unless you completely trust the source it was dl from. I have seen some NAAAAASTY scripts, coded in Russian, Vietnamese, Chinese, and Wingdings (yes that weird windows font!) ... and they are becoming VERY GOOD at moving to an app directory, changing a files name and replacing that file with WHATEVER IT IS, but renamed to a something common to the location! So by doing that, those files evade most onboard detection, if they have modified code, because that file name was whitelisted . Stick with the signed rollback package, and OTA either direct from the Oneplus community websire, or from the "gsmmafia" site, as both are packages sourced direct from the manufacturer and contain no modified code!

    ***How to get the OTA files for the region you want to switch to... follow instructions EXACTLY and you wont have an error.***

    You have to use the "OXYGEN UPDATER" app from the google play store... When you first open it , it will tell you that your device is on the current version... ignore that, and you have to open the settings menu for it, and go enable ADVANCED MODE.... This will allow you to go back and CHOOSE what device you are supposedly using. (kinda a cheap override command)... doing this will let you choose the 2417 (NA) model. **Now once again HIGHLY IMPORTANT that you are doing this ONLY after flashing the Downgrade/Rollback so that you will be on 2415 A.08 build... cuz then when you select the 2417 model, it will show an update available for 2417 A.12 build. and also the Android 13 Beta. Pick whichever you want, and click download... NOW once downloaded DO NOT HIT THE REBOOT BUTTON.... this will attempt to flash it via normal methods... instead jump into ADB , go to Shell, and head to /sdcard/ and start looking for the folder where it just downloaded the update. It places it sometimes in the main /Sdcard/ folder, and other times in the /Sdcard/Android/Data/<app name>/ folder.... you will know it when u see it. Find it and copy it to your computer and then you have the official OTA saved. After that, make sure it is moved to the /Sdcard/ folder and use "local updater". Will ask you to confirm, click Ok, and it should start the verification and flash process.

    Be advised it will APPEAR like its frozen or no progress for like 4 minutes, then it will slowly start moving. Once it gets to 99, it will appear stuck again... just be patient and about 5 min later it will complete. Total flash time is arouund 20-25 min.

    DO NOT FORGET TO UNPACK THE ZIP FILE
    EDIT THE PAYLOAD_PROPERTIES.TXT
    CHANGE THE "0" TO A "1" ON THE ENGINE_UPDATE_CHECK_DISABLE =
    SAVE THE CHANGES, AND RE - ZIP THE CONTENTS
    THEN COPY THIS ZIP FILE TO YOUR /SDCARD/ FOLDER!

    if you dont it will fail!


    Links to Downgrader Packages used can be found HERE

    👇👆EDIT: I went ahead and linked the main files necessary for this whole process here for ease, and my peace of mind. Now I know that you have all re required tools. Enjoy!

    2015 Rollback Package, courtesy of EtherealRemnant

    Oxygen Updater (for current OTA of region)

    Local Update apk (official)
    1
    I did not find any over the air or upgrade packages for the 2417 model from the above link. How did you get back to the 2417 model? And what APK did you use because some of them did not work on my device. It would just say verification failed. I thought I tried to go from a global.08 to the over the air .10 2417 model but it didn't work for me it just said verification failed. I did try to go sideways from the global .10 to the North American .10 but it also did a verification failed. maybe I'll try again. I got the over-the-air 2417 model update from the OnePlus updater app.
    1
    yes you are correct... and i can honestly say i have NO idea where i got a 2417 beta 1 android 13 firmware from, but I DO have it downloaded to my computer ... I am looking at it. I know for a fact that i got it from some chinese site, or vietnamese ... something like that... but because of that i wont upload or link it, as i stated in my OP, i had 2 of my Laptops, one macbook pro running parallels 18 from bootcamp, AND my Dell laptop, BOTH infected with a VERY FIERCE malware/virus that took me almost 12hrs to find everything altered, and i STILL dont feel 100% about that! I get some random cpu spikes while doing nothing, but cannot find the process doing it. So it was definitely a modified package of android 13 ... C.11 .... (which gives me ideas because if they modded a payload and it still flashed, then maybe i can do the same to crash that dumbass init script somehow.... anyways... different thread)

    if i find the link i will post it with caution.... but YES that 573 mb file will work to move you to 2417. Personally i would consider looking more towards using a GSMMAFIA Full Flash FW, for 2417 , but thats just me, and i trust them. but again, Yes this file will work.

    (its very funny how the official oneplus site shows 3 different files for 3 Android 13 updates, as well as 3 files for 3 rollback packages

    NONE OF WHICH are the 2419.... why create 3 files for 2 versions?
    Hey you seem like a very competent programmer you should shoot me a private message and add me and discord I have the OnePlus 10t and I've been trying to figure out how to restore it if we run into a problem again I did restore them at once but it doesn't seem like I can do it the same way again I would like to get more details but I want to keep it to a private chat cuz I don't want to get people's hopes up a way to fix a phone that isn't real
    1
    first of all, thanks beatbreakee for this thread.
    I had an updated version of android 12 - India, and wanted to switch it to global.
    here is what I did, in case someone wants to do the same:

    1- Rolledback to an older version of android 12 - India, using local install
    file used: 4190_sign_CPH2413_11_A_OTA_0080_all_e63867_00011011.zip

    2- Installed the android 13 version of android - GLO, using Local Update apk (official)
    file used: CPH2415_11_C_OTA_1100_all_WcQAfm_10100111.zip

    *Both files I downloaded from Android 13 all regions and Android 12 rollback all regions!
    *I did not edit the oplus_update_engine_verify_disable property, I just let it be 0.
    *I renamed the files from .zip.jar to .zip

    I did lose all my data when rolling back, but did not lose anything when upgrading to Android 13 and changing region. I immediately installed the newest A13 beta using the built-in updater, formated my phone right after it, and then rooted with magisk.

    Now I have an up-to-date rooted global version of One Plus 10T (Ace Pro)
    1
    How is the working so far? Good for daily driver? Thanks!
    perfect, bro. the phone is a little smoother, actually, I can link the phone to a brazilian phone number and I dont get indian language websites sometimes, like when I open facebook using the browser.