I can turn this into a guide if we get the right info.
I have used DC-Unlocker to unlock bootloader and FRP.
I installed v20 Phh Generic System Image via fastboot flash system.
my FRP is locked now and bootloader unlocked, and oem unlock greyed out.
i am investigating a solution and maybe it can help others.
Recovery:
can flash updates if bootloader and frp is unlocked
eRecovery:
i can connect to wifi, but no firmware is found
DLOAD:
updates performed with vol down+up+power
using the update extractor i can get the UPDATE.APP from the official firmware (SHT-W09C432B151 (8.0.0.151) i think for me)
but UPDATE.APP is over fat32 4GB limit. so i cant put it on the SDCard - and im not sure if the recovery can read exFat.
i tried with both but they fail immediately.
placing the files in the internal storage with DLOAD folder seems to send update to 5% then fail.
HWOTA:
seems to be a method used on older devices - not sure if it will work to flash this device.
the sh. script seems fairly straightforward so maybe it can be modded to work with this device
Device: SHT-W09 M5 8.4 (eu)
Build Number: 8.0.0.151 (C432)
OS: Stock 151 with Phh GSI applied
ive never had a device this difficult to recover. samsung had odin to flash firmware, nexus 5/7/9 always had a way out - when i was building roms for moto xoom it wasnt this difficult.
Good luck man, it seems like when this thing bootloops, it activates some sort of defense mechanism that makes recovery particularly challenging.
I bootlooped after editing my vendor/build.prop file. DLoad method failed. Flashing partitions via fastboot failed. Stock recovery failed. TWRP became available, and I got it working...but no partitions would mount r/w. I paid to use Funky Huawei's unbrick tool, and it failed.
Funky Huawei's eRecovery method is basically all that worked for me. But I paid to use it (I still have a few weeks remaining on a pass).
These instructions, which don't involve payment to Funky Huawei, might or might not work:
https://forum.xda-developers.com/mate-9/how-to/funky-huawei-erecovery-solution-100-t3620165
Thanks for the alternative method.
I tried with hisuite using firmware finder, it uses the same funky DNS server. When I start the process the download works fine then on hisuite it says installing, does nothing then fails. After I reboot (usb in pc, all 3 buttons) it shows a usb symbol - installing but hangs at 5% for ages.
I tried with a portable router with ERecovery and it did not work unfortunately still failed to get info
I had to result to funkyhuawei who have now added SHT-W09C432 to their system.
In the 30 days I have this I'm tdetermined to find alternative solutions to fix this issue like all other devices tend to have.
I battled it out with Huawei support and there's no chance of an frp key - at least first 3 attempts. Also tried to get them tonexplqin ERecovery but said it's for insiders only just for service repairs. They have no regard for helping developers.
I was trying to figure out where the file get stored on ERecovery so if we could adb push to it and hold vol down + up + power to recover the device. I found i could pull from /dload (not internal/externalsd) which contained firmware_update_dload.zip but when uncompressed e enwbti be referenced to Qualcomm chips.
Any ideas on patching the recovery or boot image to prevent frp lock?
I also tried to see if there is a way from adb (while OS is running) to flip the OEM unlock back to on but there's nothing in system/global/settings that represents that.
It's strange because frp should not lock if you log back into the same account.
LOGMD said:
DLOAD:
updates performed with vol down+up+power
using the update extractor i can get the UPDATE.APP from the official firmware (SHT-W09C432B151 (8.0.0.151) i think for me)
but UPDATE.APP is over fat32 4GB limit. so i cant put it on the SDCard - and im not sure if the recovery can read exFat.
i tried with both but they fail immediately.
placing the files in the internal storage with DLOAD folder seems to send update to 5% then fail.
.
Click to expand...
Click to collapse
Any conclusions why this metod isnt working? On older device this works everytime if you do it right but not on this device? is it a Oreo thing or is it because the UPDATE.APP is so big?
omaga said:
Any conclusions why this metod isnt working? On older device this works everytime if you do it right but not on this device? is it a Oreo thing or is it because the UPDATE.APP is so big?
Click to expand...
Click to collapse
In my experience using the Huawei P9 the only time I was successful upgrading the firmware from the dload folder was when the firmware version ended with MF-PV (Public Version). Even though Huawei releases versions of the firmware without the MF-PV extension from what I read these versions are for testing purposes only.
In addition to my reply to you in the 8.0.0.163 firmware update thread there is a tool called HuRUpdater that has a similar upgrade procedure to the one I described when I upgraded the firmware on my SHT-AL09 from 151 to 163.
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
OK, thanks for this info, of course I thought that this device would be as easy to utdate then my much older M2-801L via dload which worked every time. And thanks for the tool tip, I'm looking into that thread as well :good:
Butch1326 said:
In my experience using the Huawei P9 the only time I was successful upgrading the firmware from the dload folder was when the firmware version ended with MF-PV (Public Version). Even though Huawei releases versions of the firmware without the MF-PV extension from what I read these versions are for testing purposes only.
In addition to my reply to you in the 8.0.0.163 firmware update thread there is a tool called HuRUpdater that has a similar upgrade procedure to the one I described when I upgraded the firmware on my SHT-AL09 from 151 to 163.
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Click to expand...
Click to collapse
Thank You for the info.
Used it to update my CMR-AL19 and worked like a charme
omaga said:
Any conclusions why this metod isnt working? On older device this works everytime if you do it right but not on this device? is it a Oreo thing or is it because the UPDATE.APP is so big?
Click to expand...
Click to collapse
Sorry for the late reply had some busy months!
So from what I remember it's because the UPDATE.APP was too big. I tried recreating the update.app without the non-essentials but I couldn't get it working.
Huawei support when I asked about how to update via recovery just kept saying it's only for technicians at Huawei so they won't help me in any way!
Before start i'd like to tell you about my adveture with my phone
I had a Huawei mate 10 ( ALP-L29 c185) installed 8.0.0.139, rooted with magisk and TWRP (By Pretoriano80) as recovery so yesterday i suddenly think that "i shuld try android 9" (i don't know why?) . I searched here and internet so finally i decided to update by "hurupdater" method. I downloaded stock firmware by "Firmware Finder for Huawei" app (9.0.0.177) and hurupdater 0.4 also twrp_bla_alp_0.7.img for twrp recovery. I put them in same folder on sdcard. Renamed recovery.img to keep recovery as twrp. Lastly i restarted recovery and installed hurupdater.zip.
DANG!!! My phone is bricked....... It gave a lot of errors during installation and when i try to reboot it was bootlooping, cant load recovery interface (twrp or stock). I could enter e-recovery but gives "getting package info failed" error. So ended up with bricked phone in my hands. I tried many ways including hisuite but nada....
Then i remembered "Funky Huawei", bought 1 credit and followed instructions. After long hellish hours (firmware downloading takes long) i have my phone back working with stock 8.0.0.140 rom, stock recovery even relocked bootloader also my whole data was intact. My curosity cost me 20 $ and hours. This morning i realised there is system update 9.0.0.159
So my questions o this point
1)What should i do now? Update to android pie (with stcock recovery of course)? Is it worth trying or just install twrp and root my current rom and go on my way for a while longer ? (till a more stable pie relase)
2) For the future, what was wrong in my update process. I'd never want to make same mistake again..
Thanks...
draqkin said:
Before start i'd like to tell you about my adveture with my phone
I had a Huawei mate 10 ( ALP-L29 c185) installed 8.0.0.139, rooted with magisk and TWRP (By Pretoriano80) as recovery so yesterday i suddenly think that "i shuld try android 9" (i don't know why?) . I searched here and internet so finally i decided to update by "hurupdater" method. I downloaded stock firmware by "Firmware Finder for Huawei" app (9.0.0.177) and hurupdater 0.4 also twrp_bla_alp_0.7.img for twrp recovery. I put them in same folder on sdcard. Renamed recovery.img to keep recovery as twrp. Lastly i restarted recovery and installed hurupdater.zip.
DANG!!! My phone is bricked....... It gave a lot of errors during installation and when i try to reboot it was bootlooping, cant load recovery interface (twrp or stock). I could enter e-recovery but gives "getting package info failed" error. So ended up with bricked phone in my hands. I tried many ways including hisuite but nada....
Then i remembered "Funky Huawei", bought 1 credit and followed instructions. After long hellish hours (firmware downloading takes long) i have my phone back working with stock 8.0.0.140 rom, stock recovery even relocked bootloader also my whole data was intact. My curosity cost me 20 $ and hours. This morning i realised there is system update 9.0.0.159
So my questions o this point
1)What should i do now? Update to android pie (with stcock recovery of course)? Is it worth trying or just install twrp and root my current rom and go on my way for a while longer ? (till a more stable pie relase)
2) For the future, what was wrong in my update process. I'd never want to make same mistake again..
Thanks...
Click to expand...
Click to collapse
I have exactly same phone (c185) never tried unlocking bootloader but I updated to emui 9 159 there are some buggy things like when you want to use third party lunchers You can't use gesture navigation and it has so many bugs so not using gesture is better
there are again some problems with third party launchers (im using nova) like sometimes when you go to "resents" its totally blank and you have to force stop "huawei home" to make it right
there are some good changes in camera like new 960 fps slow motion (but there is a huge crop in 240fps 720p and 960fps 720p I can't remember that 240fps had that crop or not) Turning off master ai and some new scene detection but it's slower than last one
there is a new performance mode that i love using it (it feels like a real flagship however it's not because of stupid SOC)
there is a new AI api that android 8 didn't have so most of apps wasn't able to use NPU
in emui 8 there is a little bit better battery
I love changes to my phone so I preferred buggy new firmware to old ones there are so many good little changes in interface (like when you take a picture you can go to gallery then scan it for QR code)
There is a way better Mira cast functionality (and new desktop mode in it)
hi touch, hi vision
These were all expensives I had with emui 9 that I can think of
How did you update @arianamirgholami ?
Meanwhile, I have the same phone but am still on Android Oreo......I have the ALP-L29 8.0.0.141(C185) model. I'm reading more and more about others with this model that have gotten the Android Pie upgrade over the last two months but the upgrade is still not available to me. Makes no sense...I have a stock rom on the phone, I am NOT rooted and my bootloader is locked. Neither hisuite, hicare, system update, nor firmware finder methods gets me anywhere. They all say that I'm on the most recent firmware.... 8.0.0.141(C185). Go figure....
curgervending said:
Meanwhile, I have the same phone but am still on Android Oreo......I have the ALP-L29 8.0.0.141(C185) model. I'm reading more and more about others with this model that have gotten the Android Pie upgrade over the last two months but the upgrade is still not available to me. Makes no sense...I have a stock rom on the phone, I am NOT rooted and my bootloader is locked. Neither hisuite, hicare, system update, nor firmware finder methods gets me anywhere. They all say that I'm on the most recent firmware.... 8.0.0.141(C185). Go figure....
Click to expand...
Click to collapse
Same here, although my brother and I have the same device (ALP-L29C185) and we're on the same career, he got the pie update like a month ago and nothing for me yet. I think it's a matter of time until our imeis turns.
MasterThiefGarrett said:
How did you update @arianamirgholami ?
Click to expand...
Click to collapse
I used Erecovery of firmware finder
curgervending said:
Meanwhile, I have the same phone but am still on Android Oreo......I have the ALP-L29 8.0.0.141(C185) model. I'm reading more and more about others with this model that have gotten the Android Pie upgrade over the last two months but the upgrade is still not available to me. Makes no sense...I have a stock rom on the phone, I am NOT rooted and my bootloader is locked. Neither hisuite, hicare, system update, nor firmware finder methods gets me anywhere. They all say that I'm on the most recent firmware.... 8.0.0.141(C185). Go figure....
Click to expand...
Click to collapse
Yes I saw many people on internet facing same issue, What I assume is that when you purchased the phone it came with 8.0.0.141, that's why its not getting the Pie. Because the phones which were using 8.0.0.140 already got the Pie instead of 8.0.0.141. So one thing you can try is to go back to 8.0.0.140 and then update the phone. I did the same, Installed 8.0.0.140 using HiSuite and then update to Pie.
Fazee99 said:
Yes I saw many people on internet facing same issue, What I assume is that when you purchased the phone it came with 8.0.0.141, that's why its not getting the Pie. Because the phones which were using 8.0.0.140 already got the Pie instead of 8.0.0.141. So one thing you can try is to go back to 8.0.0.140 and then update the phone. I did the same, Installed 8.0.0.140 using HiSuite and then update to Pie.
Click to expand...
Click to collapse
I finally got the OTA update from EMUI 8 to EMUI 9
curgervending said:
I finally got the OTA update from EMUI 8 to EMUI 9
Click to expand...
Click to collapse
Thats great. Means you got more luck. Mine is still on 9.0.0.159 and no update. Please also confirm one thing. What is android security patch in this version?
Finally grab the update today morning...
Another update today. Woww
Hy guys,
i have miui 12.5.5.0 RKIEUXM on mi11 lite 5g but when i search new versions it says there is no update for the phone. So i tried to download the V13.0.4.0.SKIEUXM from official site in order to install it manually. I go in the settings to choose the package to install the update but it can't verify the package and it can't update the phone.
I'm stucked with the 12.5.5.0!!!
What can i do?
or stay on 12.5.5..or flash with fastboot...
Not sure what official site you're referring to but I have used the following without issue. Double check the file sizes/MD5s are the same in case your original download was cut short or something.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
If still not working, it's possible it may require you to have the previous update installed before it will allow the newest. Try installing 12.5.7 first - and if it doesn't allow that then 12.5.6...
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
One issue I've personally encountered is that the update dialogue stops showing the option to install from local package. If you see this then select the updater settings from the Recents and clear data then try again.
sn0uts said:
Not sure what official site you're referring to but I have used the following without issue. Double check the file sizes/MD5s are the same in case your original download was cut short or something.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
If still not working, it's possible it may require you to have the previous update installed before it will allow the newest. Try installing 12.5.7 first - and if it doesn't allow that then 12.5.6...
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
One issue I've personally encountered is that the update dialogue stops showing the option to install from local package. If you see this then select the updater settings from the Recents and clear data then try again.
Click to expand...
Click to collapse
Thanks sn0uts, 2 days ago i did exactly as you explained: choosing that web site and starting to manually updating into 12.5.6, 12.5.7 and then 13.0.4.
Now the phone is up to date, i still don't know why i've encountered this problem but i have a solution also for future.
sn0uts said:
Not sure what official site you're referring to but I have used the following without issue. Double check the file sizes/MD5s are the same in case your original download was cut short or something.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
If still not working, it's possible it may require you to have the previous update installed before it will allow the newest. Try installing 12.5.7 first - and if it doesn't allow that then 12.5.6...
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
One issue I've personally encountered is that the update dialogue stops showing the option to install from local package. If you see this then select the updater settings from the Recents and clear data then try again.
Click to expand...
Click to collapse
Actually, with the app:
MIUI Downloader - Apps on Google Play
MIUI upgrade app for Mi users.
play.google.com
searching through Xiaomi Firmware Updater is easier. The app checks your phone model, your current firmware and points you directly to download your OTA from Xiaomi Firmware Updater.
If you don't want the offered OTA, you can search for the other suitable firmwares for your phone
Even more, it shows you Xiaomi.eu Weekly and Stable ROMs, and TWRP (if applicable)
You can also manually change the phone model and search for another Xiaomi phone
Anyway, it makes searching easier and error-free (newbie, by looking at Xiaomi Firmware Updater, may easily pick a wrong firmware, resulting by bricking his phone)
zgfg said:
Actually, with the app:
MIUI Downloader - Apps on Google Play
MIUI upgrade app for Mi users.
play.google.com
searching through Xiaomi Firmware Updater is easier. The app checks your phone model, your current firmware and points you directly to download your OTA from Xiaomi Firmware Updater.
If you don't want the offered OTA, you can search for the other suitable firmwares for your phone
Even more, it shows you Xiaomi.eu Weekly and Stable ROMs, and TWRP (if applicable)
You can also manually change the phone model and search for another Xiaomi phone
Anyway, it makes searching easier and error-free (newbie, by looking at Xiaomi Firmware Updater, may easily pick a wrong firmware, resulting by bricking his phone)
Click to expand...
Click to collapse
It does look very useful. However if I wasn't reading a recommendation on XDA and only saw it in the Play Store I might not trust an app with this from the look of it. If it's trustworthy then great.
sn0uts said:
It does look very useful. However if I wasn't reading a recommendation on XDA and only saw it in the Play Store I might not trust an app with this from the look of it. If it's trustworthy then great.
Click to expand...
Click to collapse
Actually, they have a useful TG news. Too many things, not everything for everybody but eg, useful info about roadmaps which phones will receive further updates to newer MIUI and Android versions, new phones, new ear buds, etc
If using Xiaomi.eu ROMs, you will usually see a (correct!) changelog for the upcoming weekly an hour or more earlier than posted to Xiaomi.eu forum
nikorzi said:
Hy guys,
i have miui 12.5.5.0 RKIEUXM on mi11 lite 5g but when i search new versions it says there is no update for the phone. So i tried to download the V13.0.4.0.SKIEUXM from official site in order to install it manually. I go in the settings to choose the package to install the update but it can't verify the package and it can't update the phone.
I'm stucked with the 12.5.5.0!!!
What can i do?
Click to expand...
Click to collapse
I had the same problem and FINALLY I CAME UP WITH A SOLUTION. so... I've downloaded the ROM for V12.5.7.0 and installed it through the Updater app on the phone. After that, you can download the V13.0.4.0 and install it as normal.
I made an account just to help you guys because I was really annoyed that I couldn't update and probably you feel the same way.
Good luck and enjoy your mi11 lite
P.S. my battery went ****ty on the V12.5.5.0, idk about you but I had to recharge it often...hopefully it's not a hardware problem...
SuperGeo9 said:
I had the same problem and FINALLY I CAME UP WITH A SOLUTION. so... I've downloaded the ROM for V12.5.7.0 and installed it through the Updater app on the phone. After that, you can download the V13.0.4.0 and install it as normal.
I made an account just to help you guys because I was really annoyed that I couldn't update and probably you feel the same way.
Good luck and enjoy your mi11 lite
P.S. my battery went ****ty on the V12.5.5.0, idk about you but I had to recharge it often...hopefully it's not a hardware problem...
Click to expand...
Click to collapse
What exactly do you mean by "Updater app on the phone"? I am stuck on 12.5.5.0 as well and idk what to do with it. I assume the rom you've downloaded was from MIUI Updates Tracker topic on this board? If so, which one, the Fastboot or the Recovery?
Nevermind, figured it out. Downloaded "MIUI Downloader" app from Google Play, downloaded 1 version higher than ive had. Then, I went to settings -> About phone, clicked version, clicked a few times version logo and additional settings have been enabled. Then Ive clicked the button in top right corner and selected downloaded package. The phone accepted it and installed it. Then I've proceeded with other higher versions.
hehebuhehe said:
What exactly do you mean by "Updater app on the phone"? I am stuck on 12.5.5.0 as well and idk what to do with it. I assume the rom you've downloaded was from MIUI Updates Tracker topic on this board? If so, which one, the Fastboot or the Recovery?
Nevermind, figured it out. Downloaded "MIUI Downloader" app from Google Play, downloaded 1 version higher than ive had. Then, I went to settings -> About phone, clicked version, clicked a few times version logo and additional settings have been enabled. Then Ive clicked the button in top right corner and selected downloaded package. The phone accepted it and installed it. Then I've proceeded with other higher versions.
Click to expand...
Click to collapse
Sorry for the late reply. My solution was slightly different.
I downloaded the recovery rom (so you can install it from the phone) from a website with original miui roms, placed it in the internal storage, created a folder "downloaded_rom" and then I did exactly like you (settings>about phone>clicked the 3 dots>choose update package).
After that I downloaded the latest rom from c.mi.com and that was it.
I noticed that my problem with the battery was caused by the 12.5.5 rom. Now it's good as new.
I'm glad my post helped you and hopefully will help others as well. Take care!
My phone (bought in germany, EEA-rom) was stuck at "V12.5.6.0.RKIEUXM Enhanced" since the only update I received shortly after bying in December 2021. I could resolve the issue as follows:
In the update tracker thread I verified my build version which was EEA (European) in my case. First I tried to download and install v13.0.4 directly which failed (cannot verify stable update bla bla bla). Then I tried to download and install the version that was closest to mine -> V12.5.7.0.RKIEUXM which I successfully could flash. Directly after booting into 12.5.7 I was offered another update to v13.0.4.
Did anyone have similar issues: phone would not update to latest available version? What could be the reason? Regions and Update schedules? But were now in april 2022 and my phone was still not showing any updates.
I am in Australia and have downloaded the latest firmware for the phone, Renoir, but I can't update it because the option to "choose update package" isn't available on my phone...
I downloaded the update as I am getting the problem of not being able to download the package via my phone...keep getting the error that "something went wrong. Wait a minute or two and try again". This is frustrating
I discovered the fix to my problem... If you can't see the option of selecting a package to update under the 3 dots, click on MIUI logo in the updater several times till you see a message that tells you more features have been enabled.
cheers
col
Didn't read the whole discussion but noticed fastboot and xiaomi.eu options...those are the best IMHO.
xiaomi.eu updates renoir (weekly or stable) with fastboot option / scripts.
There are also fastboot recoveries (not the same as xiaomi.eu fastboot ROMs, but in case something goes wrong this can help out of bad situation) and regular update ROMs on MIUI tracker just make sure to pick the correct phone/ROM version: https://xiaomifirmwareupdater.com/miui/
(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)
... 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 .
I have this problem with bootloader and I don't know how to solve it on ghasedak24 website.
mrwilliamm said:
I have this problem with bootloader and I don't know how to solve it on ghasedak24 website.
Click to expand...
Click to collapse
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!
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.
tdamocles said:
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
Click to expand...
Click to collapse
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
beatbreakee said:
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
Click to expand...
Click to collapse
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.
tdamocles said:
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.
Click to expand...
Click to collapse
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!
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 said:
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
Click to expand...
Click to collapse
GLO version is not NA. GLO is 2415 EU. I know this because this is the reason I'm stuck on 2415.
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?
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.
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.
beatbreakee said:
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?
Click to expand...
Click to collapse
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
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.
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!)
AkayamiShurui said:
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
Click to expand...
Click to collapse
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.
tdamocles said:
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.
Click to expand...
Click to collapse
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!
beatbreakee said:
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.
Click to expand...
Click to collapse
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.
kramnod said:
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.
Click to expand...
Click to collapse
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