I have tried everything. I'm trying to go back to Android 11 after the recent upgrade from T-mobile to Android 12. Yes, I renamed the files to .apk and .zip. Yes, I moved it into my internal storage, yet my stupid phone just doesn't find it. I've done this like 10 times. No I'm not downloading the wrong version. I even tried downloading the one for OnePlus 9 pro (NA) It won't recognize the file, and I'm not sure why. I'm not going to use this new horrible update that they forced on my phone please help me downgrade from this trash. Here is the link that shows you how to do so. I've followed the steps exactly. I've also attached screenshots. If anyone knows what I'm doing wrong please help. Thanks
Personally would just use this.
https://forum.xda-developers.com/t/global-oneplus-9-msm-tool-updated.4284779/
It takes less than 5 minutes to flash. Once done, download https://android.googleapis.com/packages/ota-api/package/580d47a7dde5862a306c07ff939cc4fe1520860f.zip and move to root of storage, use local upgrade tool in settings to get back to latest OOS 11 release.
I just did this same process to get off of a custom ROM today and it couldn't have been easier other than the fact I had to restore my backup and set my apps up again. It's good to do that every so often though, keeps the device running well cleaning out all the clutter.
Thanks, but any chance you know of a video tutorial on this? I really don't know what I'm doing and I'm already stuck
I just realized you mentioned T-Mobile up there. You actually need the T-Mobile MSM Tool if it's the T-Mobile version.
I don't know that there is a downgrade option available for the T-Mobile firmware, the MSM Tool may be your only option. This is why I don't buy phones from the carriers anymore.
It is going to put you on a pretty old firmware and I'm not sure if the zip files are available for the T-Mobile variant.
There is a detailed post on how to use this on the OnePlus forums. I just checked and the MSM Tool for the T-Mobile OnePlus 9 is on the OnePlus Community Server that's linked.
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
Related
i have looked everywhere.
i am trying to find the stock recovery for oneplus 7 pro
- t-mobile version (if required)
10.0.1 oos
Honestly this phone has been the worst experience ever.
From t-mobile not allowing me access to files to fix my device, to forums being dead, sluggish and from several developers not caring about the issues others experience. to a single phone with 7 different variations. and the one I'm stuck with has 0% help.
ive seen multiple request for these files to go look and see "nvm i just flashed international rom..."
honestly it should be illegal for companies to not provide these files.
ivoe said:
i have looked everywhere.
Click to expand...
Click to collapse
That is because you are looking for something that does not exist. This phone doesn't have a recovery partition. On A/B partition devices, the recovery resides on the boot.img partition (along with kernel and ramdisk). The A/B partition scheme is very confusing if it is new to you (as it is to a lot of folks). You can possibly fastboot flash the stock boot.img partition, depending on what exactly you are trying to accomplish.
I don't buy carrier branded phones anymore, for some of the reasons you are experiencing. Converting the T-Mob 7 Pro to be "international", seems to be a pretty popular thing.
This device is far from being "dead" the most common thing to do with the T-Mo version is to flash the international ROM. The only thing people do on the T-Mo ROM is to SIM unlock, thus allow bootloader unlocking, then go right back to the international ROM.
CosmicInsight said:
This device is far from being "dead" the most common thing to do with the T-Mo version is to flash the international ROM. The only thing people do on the T-Mo ROM is to SIM unlock, thus allow bootloader unlocking, then go right back to the international ROM.
Click to expand...
Click to collapse
i have had to many issues with international that i msm back to tmobile.
i just didnt want to lose everything over an over doing this when things go wrong
i believe i have dumped the boot.img
i just hope it works when i do need it again.
Here's what I did whenever T-Mobile update to Android 10.0.1 I downloaded the OTA Update from off the internet then extracted it on my desktop then I used the payload-dumber-win64 to get the recovery and boot.img to use Incase I needed them. I used the extracted boot.img from the payload-dumber-win64 and followed instructions on how to use magisk patcher to patch my own boot.img. search Google for the T-Mobile update then use the tools to extract the whole thing.
I am trying to rebrand my t-mobile OnePlus 7 Pro back to the t-mobile software after changing it to international a few months ago. I have to trade in my phone with t-mobile and have to flash the software. I downloaded all the necessary files, but when I run the MSM tool, I get the "Package image not exist" error. I have tried running it regular and as an admin and still get it. I do still have the OP7Pro international files and the MSM tool from that and tried launching it, but it seems that that one works.
Any ideas?
Roccothepro said:
I am trying to rebrand my t-mobile OnePlus 7 Pro back to the t-mobile software after changing it to international a few months ago. I have to trade in my phone with t-mobile and have to flash the software. I downloaded all the necessary files, but when I run the MSM tool, I get the "Package image not exist" error. I have tried running it regular and as an admin and still get it. I do still have the OP7Pro international files and the MSM tool from that and tried launching it, but it seems that that one works.
Any ideas?
Click to expand...
Click to collapse
did you fix? Same thing for me
Idk if you guys figured this out yet, but I came across this myself, messing with my old Tmobile Based OnePlus 7 Pro, with the whole "package image not exist", The Msm tool has to be in the same folder as the guacamole zip, and the L2 drivers, and using something like Winrar/7zip you gotta extract them from the .rar and .7z. then run the Msm tool again. Hope this helps.
Roccothepro said:
I am trying to rebrand my t-mobile OnePlus 7 Pro back to the t-mobile software after changing it to international a few months ago. I have to trade in my phone with t-mobile and have to flash the software. I downloaded all the necessary files, but when I run the MSM tool, I get the "Package image not exist" error. I have tried running it regular and as an admin and still get it. I do still have the OP7Pro international files and the MSM tool from that and tried launching it, but it seems that that one works.
Any ideas?
Click to expand...
Click to collapse
If you are still needing some help with this, I can try to dump my firmware and put it together for flashing in fastboot.
@EVOuser94 @phillipmckinnish @Roccothepro
This is also for all other T-Mobile users who want to convert back to TMO firmware.
I uploaded Android 11.0.1.2 firmware images to a new ROM thread. To convert back to TMO firmware without using the MSM tool you can follow the instructions in the thread.
Since you are converting from International or another non TMO ROM, you will be required to wipe your data.
T-Mobile OnePlus 7 Pro OOS 11.0.1.2 Stock Firmware (Root Optional)
I have purchased a Chinese variant (KB2000, late December 2020) of the OnePlus 8T which out of the box is running HydrogenOS 11.0.5.6KB05. I downloaded the Global ROM (OxygenOS 11.0.5.6.KB05AA) from OnePlus' website to do the local update, but cannot install as it is saying it is a previous version.
I have been scouring the internet as trying to figure out options, but it seems like I have 2 options:
1. Wait until the Global ROM version is higher than the current HydrogenOS version (11.0.5.6KB05) and do a local update. Note that the unit wants to update, but not letting it.
2. Use the BootlLoader installation method to install a fresh OxygenOS. I found what seems to be a great guides at https://www.thecustomdroid.com/oneplus-8-pro-oxygenos-restoration-guide/ or https://www.droidwin.com/restore-oneplus-8-stock-oxygenos-fastboot-commands/.
Note that I don't want to Root or install any custom mods or ROM, but just want to use the latest Global ROM on this phone.
Any insight will be greatly appreciated as I have been researching, but not finding a definitive answer. Thanks in advance!
If you are fine with wiping your phone you should be able to use the msm tools from the unbrick tools thread to convert
Qnorsten said:
If you are fine with wiping your phone you should be able to use the msm tools from the unbrick tools thread to convert
Click to expand...
Click to collapse
Ok thanks for the feedback and will search for the thread. I'm fine with wiping it as it is a new phone. I'll update how it goes.
jvg2001 said:
Ok thanks for the feedback and will search for the thread. I'm fine with wiping it as it is a new phone. I'll update how it goes.
Click to expand...
Click to collapse
I assume you found the thread by now. But this is the thread if anyone else is looking for it. Was on my phone before so couldn't link it easily
[OP8T][OOS KB05AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Hey all,
I bought a new OnePlus 8 5g T-mobile phone for my wife. She's on the RedPocket annual GMSA/ATT plan. I've stopped the auto OO11 update and I've gone into *#*#4636#*#* and selected "LTE Only" for the connection type (like I did with my old OP6) but it doesn't stick after a reboot.
My real question is:
Since 4G LTE seems to work properly with the T-Mobile stock OS, what are the reasons for converting over to the international version?
Will 4G still work after I update it to OO11.x? I don't mind it having the T-Mobile boot or bloat. I have mostly disabled/uninstalled the apps she doesn't need.
Thanks!!!
The Global version of the ROM can still get OTA updates, and gets them MUCH faster. For example always on display hit global firmware, than hit T-Mobile firmware like 7 months later. Same with Android 11, hitting T-Mobile devices a few months later than global.
T-Mobile also has bloatware that is NON-disable-able, even with adb commands. Unless your rooted, your stuck with it. And some of the package names are cleverly named so you wouldn't assume its anything bad.
You might not care about T-Mobile bloatware, but also remember it has spyware, and even if you don't really "care" about it, every time T-Mobile collects more of your data and pings it back to their servers, thats taking up recources/data on your phone, and by consequence, battery life suffers.
And T-Mobile devices collect A LOT of data, even if your not using them as your mobile provider.
Am I making it sound worse than it is? Probably. Doesn't mean everything I said isn't valid. But yes if you decide to convert to global data will work just fine.
FoxyDrew said:
The Global version of the ROM can still get OTA updates, and gets them MUCH faster. For example always on display hit global firmware, than hit T-Mobile firmware like 7 months later. Same with Android 11, hitting T-Mobile devices a few months later than global.
T-Mobile also has bloatware that is NON-disable-able, even with adb commands. Unless your rooted, your stuck with it. And some of the package names are cleverly named so you wouldn't assume its anything bad.
You might not care about T-Mobile bloatware, but also remember it has spyware. And even if you don't really "care" every time T-Mobile collects more of your data and pings it back to their servers, thats taking up recources/data on your phone, and by consequence, battery life suffers.
And T-Mobile devices collect A LOT of data, even if your not using them as your mobile provider.
Am I making it sound worse than it is? Probably. Doesn't mean everything I said isn't valid. But yes if you decide to convert to global data will work just fine.
Click to expand...
Click to collapse
@FoxyDrew Thank you for the explanation.
Just wondering about this guide: https://forum.xda-developers.com/t/...nternational-with-bootloader-re-lock.4345305/
Do you follow the 1st part, followed by the last update? Is this the best way to install the global version?
Thanks again!!
chuddler said:
@FoxyDrew Thank you for the explanation.
Just wondering about this guide: https://forum.xda-developers.com/t/...nternational-with-bootloader-re-lock.4345305/
Do you follow the 1st part, followed by the last update? Is this the best way to install the global version?
Thanks again!!
Click to expand...
Click to collapse
np man, that guide is very complicated for no reason, converting to global is rather simple, but it's a 3 step process. This all assumes you can unlock your bootloader though.
1.) MSM back to stock T-Mobile Android 10 firmware. Specifically this one. This will re-lock your BL if its unlocked.
2.) Let that boot up, go into settings to enable OEM unlocking, and then unlock the bootloader.
3.) Once the bootloader is unlocked, flash THIS global Android 10 ROM via fastboot. There's a flash-all.bat file to make it simple. Once you've finished this step your essentially done, and on global firmware, you just need to...
4.) Boot the phone up and take the OTA update in settings to Android 11. There will be 2 OTAs to take, one FULL OTA to Android 11, than an incremental one to the latest Android 11 build
Optionally afterwards you can re-lock your bootloader, or keep it unlocked and root if that's what you/she wants.
If you're not familiar with MSM tool, and the drivers it needs, check out this thread.
I attempted to convert my t-mobile oneplus 9 to international firmware by first flashing the Indian firmware.
I mistakenly downloaded the oneplus 9 PRO Indian msm.
I didn't realize this as the file has a very similar name. Lemonade_22.I.07_210412 vs Lemonadep_22_I.07_210412
I've tried everything since then, with no success. I tried to flash the correct oneplus 9 indian msm but it says incorrect device.
So I'm stuck with the oneplus 9 pro Indian firmware and can't get back to indian oneplus 9 firmware....
I have been developing and flashing android devices since the early days of Cyanogenmod... dozens of devices. And guess what? I did EXACTLY the same thing as you.
The link I downloaded from said it was Oneplus 9 firmware, and given the filenames being virtually identical, I never noticed it was the Oneplus 9 PRO firmware.
So don't feel too bad. Even experienced people can make mistakes when trying to flash phones!
I am working on a solution, but so far no luck because:
1. Msm Tool will not flash the Oneplus 9 firmware as it thinks it is the incorrect device (why did it let us flash the incorrect device firmware before???)
2. The bootloader is re-locked and the OEM Unlocking feature is greyed out in Developer options, therefore fastboot can't be used to re-flash the correct firmware.
3. The System Update "local upgrade" feature does not find ZIP files in the root folder and will not allow us to browse to the correct file.
So for now, we are stuck. I think solving #3 will be the solution. If we can make the "local upgrade" work, we should be able to flash the stock firmware ZIP.
@Derek6091 @mightysween did you fix it yet? I had my device screw up so bad today that the only MSM I could use on my global unit was the Indian 9 Pro firmware and I have gotten my device mostly working.
You can see my drama with it and how I finally got it working here.
[SOLVED] Can anyone help me unbrick? I have tried lite firehose, MSM for global, MSM for Indian 9 Pro, none work
I modded the global MSM so that it will flash to this frankenphone. https://forum.xda-developers.com/t/all-of-those-stuck-on-indian-firmware-rejoice-i-modded-the-global-msm.4442473/ EDIT: For anyone else trying this and getting unsupported...
forum.xda-developers.com
I can get it working with 11.2.10.10 but not OOS 12, in OOS 12 the touchscreen doesn't work and it shows dual SIM icons so it's still doing something that makes it think it's a foreign variant. I ended up just going back to StagOS where I was before everything got mucked up.
Unfortunately the MSMs still see it as an Indian variant so I can only flash the Indian OP9P firmware to it, tried all the other MSMs and none work. I have been reading threads here and people claim they got it back to global but I tried all of the suggestions and none of them restored the device enough to where the global MSM Tool didn't see it as an Indian model and refuse to flash so I think we are stuck with this frankendevice.
@EtherealRemnant Yes I had to do oem unlock while on the Indian firmware. If your phone has the oem unlock greyed out, there's a guide on how to fix that with a simple command line.
Then I unlocked bootloader, flashed lineage recovery then a custom ROM. Haven't tried to get back to stock rom, and I don't think we can.... But I love this rom I'm currently on which is stagos.
Feel free to message me for any questions you may have!
[ROM][OOS Cam][Android 12.1]StagOS 12.1[lemonade][FINAL][08/09/2022]
Hey another day another rom, that's what you might be thinking. but we at stag aim towards elegance. We are learners just like everyone out there, This is small project we have started which helps us learn every single day. Why Stag, you might...
forum.xda-developers.com
@Derek6091 I have modded the global firmware so that it will flash on a device recognized as the Indian variant. If you would like to give it a shot (I already tested it on my own device and am happy to say, it worked perfectly and my device is back on global firmware), here's the link
LE2115_11.2.4.4_India_fix.zip
Compressed (zipped) Folder
1drv.ms
EtherealRemnant said:
@Derek6091 I have modded the global firmware so that it will flash on a device recognized as the Indian variant. If you would like to give it a shot (I already tested it on my own device and am happy to say, it worked perfectly and my device is back on global firmware), here's the link
LE2115_11.2.4.4_India_fix.zip
Compressed (zipped) Folder
1drv.ms
Click to expand...
Click to collapse
Nice glad you figured it out.
go17lyonjon said:
Nice glad you figured it out.
Click to expand...
Click to collapse
haha yeah I was a dog with a bone, wasn't gonna drop it lol.
EtherealRemnant said:
@Derek6091 I have modded the global firmware so that it will flash on a device recognized as the Indian variant. If you would like to give it a shot (I already tested it on my own device and am happy to say, it worked perfectly and my device is back on global firmware), here's the link
LE2115_11.2.4.4_India_fix.zip
Compressed (zipped) Folder
1drv.ms
Click to expand...
Click to collapse
Excellent. How did you do it? I would like to try with the T-Mobile MSM
Derek6091 said:
@EtherealRemnant Yes I had to do oem unlock while on the Indian firmware. If your phone has the oem unlock greyed out, there's a guide on how to fix that with a simple command line.
Then I unlocked bootloader, flashed lineage recovery then a custom ROM. Haven't tried to get back to stock rom, and I don't think we can.... But I love this rom I'm currently on which is stagos.
Feel free to message me for any questions you may have!
[ROM][OOS Cam][Android 12.1]StagOS 12.1[lemonade][FINAL][08/09/2022]
Hey another day another rom, that's what you might be thinking. but we at stag aim towards elegance. We are learners just like everyone out there, This is small project we have started which helps us learn every single day. Why Stag, you might...
forum.xda-developers.com
Click to expand...
Click to collapse
I can't find a working command line fix for the greyed out OEM unlock... which one did you use?
mightysween said:
I can't find a working command line fix for the greyed out OEM unlock... which one did you use?
Click to expand...
Click to collapse
Go to your home screen on your phone and connect to computer with usb debugging and run this command in cmd,
adb shell pm disable-user com.qualcomm.qti.uim
Then go to developer options and oem unlock should be able to toggle.
mightysween said:
Excellent. How did you do it? I would like to try with the T-Mobile MSM
Click to expand...
Click to collapse
You have to use the Oppo Decrypter tools. Decrypt the OPS file and open settings.xml. At the bottom of it there's a Target area. I just edited that to IN instead of O2 and re-packed it.
Derek6091 said:
Go to your home screen on your phone and connect to computer with usb debugging and run this command in cmd,
adb shell pm disable-user com.qualcomm.qti.uim
Then go to developer options and oem unlock should be able to toggle.
Click to expand...
Click to collapse
Perfect... thanks.
EtherealRemnant said:
You have to use the Oppo Decrypter tools. Decrypt the OPS file and open settings.xml. At the bottom of it there's a Target area. I just edited that to IN instead of O2 and re-packed it.
Click to expand...
Click to collapse
Nice...
I tried it with the T-Mobile MSM but it still failed on "unsupported target". Did you only change the text value for O2 to IN, or did you need to change the numerical Target ID as well?
I am pretty content leaving this phone on StagOS anyway, but would be nice to figure out a way to return to T-Mobile stock after recovering from a brick.
mightysween said:
Nice...
I tried it with the T-Mobile MSM but it still failed on "unsupported target". Did you only change the text value for O2 to IN, or did you need to change the numerical Target ID as well?
I am pretty content leaving this phone on StagOS anyway, but would be nice to figure out a way to return to T-Mobile stock after recovering from a brick.
Click to expand...
Click to collapse
Manually flashing partitions in Fastboot does work, FYI. So it is possible to go back to stock that way once the bootoader is re-unlocked.
I wonder where the "target" data is stored on the actual device. If it is simply a numerical/text value in an accessible partition, seems like it would be pretty easy to make a TWRP flashable that can change it.
mightysween said:
Nice...
I tried it with the T-Mobile MSM but it still failed on "unsupported target". Did you only change the text value for O2 to IN, or did you need to change the numerical Target ID as well?
I am pretty content leaving this phone on StagOS anyway, but would be nice to figure out a way to return to T-Mobile stock after recovering from a brick.
Click to expand...
Click to collapse
Strange that it didn't work for you. That was indeed all I changed. Did you change it to what the unsupported target message said your device was? I was comparing the settings between India and global and besides the change of target ID, the target number on India was 3 instead of 1. No idea if that makes a difference though because I didn't try it.
You made sure to re-encrypt and replace the OPS, right?
Also yeah you can flash with fastboot, it doesn't fix that flag though and when I tried to go back to OOS 12 with the messed up flag it thought my device was a dual SIM device so there was no signal and the touchscreen didn't work. Happened twice. With the modified MSM I went back to global and am running OOS 12 right now.
EtherealRemnant said:
@Derek6091 I have modded the global firmware so that it will flash on a device recognized as the Indian variant. If you would like to give it a shot (I already tested it on my own device and am happy to say, it worked perfectly and my device is back on global firmware), here's the link
LE2115_11.2.4.4_India_fix.zip
Compressed (zipped) Folder
1drv.ms
Click to expand...
Click to collapse
Do you still have this file ? I flashed the OnePlus 9 pro indian firmware in msm since it's the only thing that worked and I want to go back to global
taintsx said:
Do you still have this file ? I flashed the OnePlus 9 pro indian firmware in msm since it's the only thing that worked and I want to go back to global
Click to expand...
Click to collapse
All you have to do to go back to global is download the full OTA for your device and flash it with the system updater.
EtherealRemnant said:
All you have to do to go back to global is download the full OTA for your device and flash it with the system updater.
Click to expand...
Click to collapse
Yea I tried that and had touchscreen not responding issues
taintsx said:
Yea I tried that and had touchscreen not responding issues
Click to expand...
Click to collapse
Then use the downgrade package. It will wipe your phone again but I will get you back to full OOS11 firmware and that issue won't happen.
EtherealRemnant said:
Then use the downgrade package. It will wipe your phone again but I will get you back to full OOS11 firmware and that issue won't happen.
Click to expand...
Click to collapse
Yea i tried that with
[OnePlus 9][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
downgrade indian version 11.2.5.5 , unfortunately it just tells me it cannot read the file when i attempt to sideload