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

[beatbreakee]

(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!

Spoiler: Credits for discovery ===>

!!! 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. !!!!

Spoiler: ***DISCLAIMER***

**" 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!

Spoiler: Only open if you acknowledge the risk!

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)

 

[beatbreakee]

... And to clarify again.. This does NOT unlock the bootloader, nor does it change our T-Mobile Devices ability to unlock via conventional methods. (still working on that)

Quick expl. In our T-Mobile models, Oppo worked directly with the carrier and enabled a feature new to Android 12 and future builds, which allows the FACTORY bootloader to be wrapped up and hidden from the FastBoot binary... And move a "copy" of the bootloader into "userspace" partitions. These partitions are called AFTER the initial secure boot has passed, and therefore disabled normal FastBoot operations. Instead in userspace, "FastbootD" is enabled, and for all who know of it, that is not much more than a glorified recovery. All OEM, and Flashing commands are rendered inoperable, because bootloader operations cannot be modified once the system is up, or in "default mode". This proves my theory of Local updater not modifying partitions. It uses the currently identified locations of the files that need to be updated to the new region on just changes them where they are already located. For "FastBoot mode" to work properly, it would need to UNWRAP the original bootloader, and disable the "Userspace Init" instructions, which cannot be done on a already running OS.

If somehow you are LUCKY and after your region change, you are able to run 'adb reboot bootloader' ... And your device starts in 'Fastboot Mode' and does not kick you out, then you should be fully able to run the Unlock commands to unlock your bootloader, without need to flash anything else. The chances of that are very minute... But I have seen stranger things with this device. Tho most likely, that command will reboot you right back into normal android immediately .

 

[mrwilliamm]

I have this problem with bootloader and I don't know how to solve it on ghasedak24 website.

 

[beatbreakee]

I have this problem with bootloader and I don't know how to solve it on ghasedak24 website.

what you mean??? i dont have any info pertaining to the real bootloader for this, the Tmobile model. Ours ships with this Oppo/Oneplus Hybrid crap what makes Fastboot Mode inaccessible. It doesnt respond to the keypress method of getting to it... and adb reboot bootloader attempts to boot into it, but the phone reboots exactly .5 seconds aftter it shows the screen. The only thing you can access is FASTBOOTD which give you literally ZERO functions that we need for the bootloader. OEM, BOOT, Flashing, Flash all fail in FASTBOOTD. Other than that man i honestly would suggest you speak with MAAMDROID because they seem to know more about the OPPO loader. MY knowledge of what is taking place came from me interrogating a Oneplus employee for about 4 straight hours when he broke and told me everything.

NOW I WILL STATE ONE DEVELOPMENT.... The GSMMAFIA user who is responsible for all the MSM firmwares that are now available for the 10T, is 100% legit. You can download the entire UPDATED Full Flash FW including the MSM TOOL... for free.... but without a login/pass authenticated, they are not much help to us. BUT... i have confirmed that the guy is a REAL Oneplus Employee, and he uses official software to remote connect and flash the MSM Unbrick firmware to your device. His charge is $45 ... but he is HIGHLY sensitive to ppl with Fiddler, or any capture programs running on your computer, so much to the point that he checks your app tray and task manager when he remote connects, and if he even sees one of these kinda programs, you lose your $45 and he disconnects. Just head to the GSM Mafia page for the 10T firmware and you can get his WhatsAPP number to contact him and setup.

Me personally, I have WAY MORE than just Fiddler, Wireshark, Proxifier, WinpCap, and many more programs that i know will spook him, and i am not gonna wipe my pc for something that is not guaranteed to do what i want. BUT if you have a bootloader error, you have nothing to lose, and flashing a full, Unbrick fw thru MSM, like he does just MIGHT format all partitions first and therefore erase the instruction init filee that locks up fastboot. Literally EVERY model except the 2419 has normal Fastboot, and an unlockable BL....

Just a thought!

 

[tdamocles]

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.

 

[beatbreakee]

I did not find any over the air or upgrade packages for the 2417 model. 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

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!

thx for reminding me.. adding to OP

 

[tdamocles]

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!

thx for reminding me.. adding to OP

the OP updater app only shows the 500mb OTA 2417 and not the 4gb full install. Will it still work? On the global version .08 I could not get the in built local install to install anything without verification failure. Also 2417 variant does not have beta 13.

 

[beatbreakee]

the OP updater app only shows the 500mb OTA 2417 and not the 4gb full install. Will it still work? On the global version .08 I could not get the in built local install to install anything without verification failure. Also 2417 variant does not have beta 13.

Links straight from 1+ community... android 13 OTA update packages for 2413, 2415, and 2417 ....
AND
Rollback packages for the same respective models... All in zip format. Must unpack and change payload_properties... Yadda yadda....

Android 13 all regions and Android 12 rollback all regions!

 

[beatbreakee]

Now you can rollback to any region you want and start from there! I must remind EVERYONE... If you have not Sim unlocked your device prior to changing regions, you will lose that ability for the near future, because there will not be a T-Mobile official upgrade/rollback packages released afaik until maybe after the new year. (Don't know why.. just relaying what T-Mobile told me!). But the Unlock apk is strictly for the 2419 model and there is not currently a way back to it.

And be aware, that if you have ANY belief that you might be considering either doing this or maybe unlocking bootloader if we find an exploit, I highly advise you flip your OEM UNLOCKING switch to ON, now! Because T-Mobile may find a way to turn that toggle grey again if your sim is still locked. Just an fyi

 

[tdamocles]

the OP updater app only shows the 500mb OTA 2417 and not the 4gb full install. Will it still work? On the global version .08 I could not get the in built local install to install anything without verification failure. Also 2417 variant does not have beta 13

GLO version is not NA. GLO is 2415 EU. I know this because this is the reason I'm stuck on 2415.

 

[beatbreakee]

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?

 

[tdamocles]

I can't move to 2417 from 2415 with built in updater. Even changed 0 to 1. Downloaded update apk and it doesn't see ota zip in root directory. I think I need full install zip for 2417. Any ideas how to go from the 2415.08 to the 2417.10? What's even better is the global package doesn't want to install either through the inbuilt updater. I have to use the updater APK to install the global package.

 

[tdamocles]

There's something in that zip that keeps it from verifying it and it's not the zero and the one. The updater APK doesn't even see that zip file it only sees the GLO zip file.

The incremental GLO a.12 did not want to flash. Failed every time I tried. The full GLO a.12 package was giving me problems flashing also. It would get to 40% complete and then fail. Third time flashing after rebooting finally took.

 

[AkayamiShurui]

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

 

[kramnod]

This is great! I have been looking to change region from India onto a Global Version.

I have the Oneplus Ace Pro which is a chinese release of the 10T, the seller I bought this from flash it to Oneplus 10T India region.

Will give it more time though, wanted to get feedback first from those that has the Ace Pro Version.

 

[beatbreakee]

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.

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!)

 

[beatbreakee]

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

as soon as i get some free time, possibly this evening or tomorrow morning, i will shoot you a dm and we will link up.

 

[beatbreakee]

There's something in that zip that keeps it from verifying it and it's not the zero and the one. The updater APK doesn't even see that zip file it only sees the GLO zip file.

The incremental GLO a.12 did not want to flash. Failed every time I tried. The full GLO a.12 package was giving me problems flashing also. It would get to 40% complete and then fail. Third time flashing after rebooting finally took.

Well i do know that the Zero - One does trigger a fail, thru simple trial and error. But you are correct in that it is much more than that. I have managed to open 2 different Payload.bin files, SWAP highly important files in each such as Boot.img ... and then pack them back, AND THEY STILL FLASHED... so it definitely doesnt have anything to do with the file signatures, because the sigs would change considering the boot.img is of different sizes. There is something possibly hidden in one of the Android Manifest files, or one of the many Build.prop files in the Payload that is what triggers a fail. If we can figure out exactly what file it is, we can find out whether we can alter them, or eliminate them completely. My focus has shifted though, now that we have a working region swap. Now i am focused on this special function of the engineering/factory mode, because if it can be found, it will mean a FULL BL unlock... THAT will negate the need for these, because we will be able to flash whatever we want !

AND YES OPPO.... I KNOW YOU ARE WATCHING MY THREAD NOW! JUST KNOW THAT IDGAF! I AM AND I WILL CONTINUE TO CHIP AT YOUR B.S. ATTEMPT TO KEEP OWNERS FROM DOING WHATEVER THEY WANT WITH THEIR DEVICES! YOU DONT OWN THE PHONES... YOU MANUFACTURE THEM! ONCE THEY LEAVE YOUR WAREHOUSES, AND WE PAY THE STORE FOR THEM, THEY BELONG TO US. IF YOU DONT WANT TO SUPPORT THEM AFTER WE CHANGE THE FW, SO BE IT.... BUT THAT DOES NOT GIVE YOU THE RIGHT TO DENY US THAT OPTION... THIS AINT CHINA! THE VAST MAJORITY OF THE WORLD WHICH PURCHASE YOUR PHONES ARE FREE REPUBLICS, SO YOU DONT DICTATE OR GOVERN THE USAGE OF OUR DEVICES! REALIZE THIS OR BECOME LIKE MOTOROLA, AND SO MANY OTHER COMPANIES WHO WENT OBSOLETE FOR A VERY LONG TIME! WHEN YOUR SALES DECLINE 50% OR MORE BECAUSE YOU ALIENATED A BIG GROUP OF YOUR CUSTOMER BASE, THEY WILL ELIMINATE THE EXECUTIVES WHO WERE RESPONSIBLE FOR THIS LOSS!

 

[AkayamiShurui]

as soon as i get some free time, possibly this evening or tomorrow morning, i will shoot you a dm and we will link up.

So I actually have a complete list pulled off of my OnePlus 10t the 2417 edition of the ussd codes otherwise the dialer codes that can and should work on the phone I can post them if you want or I can send a link to them.

 

[blasbenoit]

This is great! I have been looking to change region from India onto a Global Version.

I have the Oneplus Ace Pro which is a chinese release of the 10T, the seller I bought this from flash it to Oneplus 10T India region.

Will give it more time though, wanted to get feedback first from those that has the Ace Pro Version.

Hey man, that happened to me as well... Amazon right?.

So the only issue is the 12GB Ram... And the antennas in my case (I cant get 5G).

So why do you want to change?.....

I want to know so i can change it as well, lol