Question. I tried doing the rollback a couple months ago and as soon as I did and phone rebooted, it installed the latest update, asap, preventing me to going to the next step. I even diabaled installed upstairs automatically in dev options. Ty
Flash 10.5.7 TMobile version with MSMDownloadtool, then boot. ASAP, turn off automatic updates. Also, tell it that you want it to download full updates only. Put it in airplane mode if you have to or pull the SIM momentarily, haha. There is simply no way it could possibly download over 1GB in the time it takes to stop it from updating! I think it also gives you the option to delay the update.
The best thing to do is follow the instructions on this page. Use MSM to downgrade first.I am on Tmobile version 11.06.8 (A11) I have the OnePlus Global rom (15.0.40) on my phone. That one is direct from the OnePlus site. It looks as if the OnePlus 8 has been pulled from their downloads list of phones on their site. I also have the 10.5.12 global rom listed in the 1st page of the thread.
I need clarification. Do I need to revert to A10 or can I use fastboot to update to global via any of these Global rom's? I read the entire thread. Is there a consensus of anything needing to be backed up? Or are these issues on a case by case basis. I have close to a week left before I get my token.
I just wish that someone would actually make a proper modded msm tool for everyone thats on tmobile to convert to global without any issues of losing sim functionality or wait 7 days for the unlock code. Makes everyone's life easier and the fact that OP8T already has one which means that it is possible to make one and that we just need that person to help us. BE THE SAVIOUR!There are other tools able to flash this phone; I'm pretty sure qfil could do it, at the very least. There isn't anything proprietary to OnePlus; this phone speaks the Sahara protocol just like all the other devices with Qualcomm SoCs. There's a GitHub repository containing a tool someone developed that can decrypt the ops firmware files. I played around with it a while ago, and the ops file contains the firehose programmer, so there is no reason it couldn't be done by anything that speaks the Sahara protocol.
Oppo .ofp Firmware decrypter and oneplus .ops de-/encrypter - GitHub - bkerler/oppo_decrypt: Oppo .ofp Firmware decrypter and oneplus .ops de-/encryptergithub.com
Decrypt and unpack the firmware archive (ops file), and you'll see that all the files you need are there. I don't recall if contains the partition info in the right format, but that could be converted. I'm almost positive that everything you need is in that archive. I didn't really try to do anything with it because msmdownloadtool worked.
Here is a tool you can use when the phone is in edl mode to play around with it:
Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :) - GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)github.com
Here is a tool to recreate the flash image:
GitHub - NHellFire/android-qfil-unsparse: Tool to reassemble the sparse images used by Qualcomm Flash Image LoaderTool to reassemble the sparse images used by Qualcomm Flash Image Loader - GitHub - NHellFire/android-qfil-unsparse: Tool to reassemble the sparse images used by Qualcomm Flash Image Loadergithub.com
python3 backdoor.py "MsmDownloadTool V4.0.exe"'
I am on the same boat as you, waiting for my unlock code in a few days.Simple question. I have the latest Global rom from the oneplus website. Can I use the fastboot method and simply put the zip file in and load the global rom in? There is a guy on youtube that goes around all of this and renames the global rom to a zip file and uses the existing A11 to load the global OS using system update. As long as the global rom is newer than the existing OS, it works.
Right now the oneplus website is missing the OnePlus 8 for software upgrades.
On Monday I will receive my bootloader unlock token. So I have a few days to figure all of this out.
4th and Last Step: Open the Global Rom (10.5.12 OnePlus 8 Global Rom) and find flash-all.bat and double click on it, and type and enter Y when it asks to.
Can you share the global rom you downloaded? Is this actually newer than the Tmobile rom version, that's the question I guess.I got the latest global rom directly from the OnePlus website. It seems as if they pulled the OnePlus 8 from the update page in the last couple of days.
This is the guy who upgrades from Android 11 to the Android 11 global rom (OnePlus 8T) from within the existing Android 11 phone OS. His trick is to wait for an update and then redirect the update to the global Rom on the phone.
First I need to make sure the update works. The Global rom comes directly from the OnePlus website for the 8. The video I linked most likely will not work with US branded phones. With an unlocked bootloader, you cannot receive updates from Android updates. I am going the fastboot route when I get my unlocked token.
you can do OTA updates on unlocked bootloaderFirst I need to make sure the update works. The Global rom comes directly from the OnePlus website for the 8. The video I linked most likely will not work with US branded phones. With an unlocked bootloader, you cannot receive updates from Android updates. I am going the fastboot route when I get my unlocked token.
My question is can I simply flash the global rom via fastboot straight across via Android SDK platform tools without reverting to an Android 10 rom.
The Android 11 Global rom is newer than the latest T-Mobile Android 11 rom.
Thank you for sharing!!! Was pulling my hair wondering why the heck I couldn't figure this out. Finally working now.Sorry for spamming the board today, but I think I figured it out.
Thanks to @thattechguy_69 for all the work here so far. This is just to help anybody who is having issues like I did.
The "critical partitions" issue appears to be a DRIVERS issue, not a fastboot version issue or anything else with the actual phone or ROM files. I had installed all of the drivers that every guide said to install, but I stumbled upon this post by @FoxyDrew that solved my issue.
Here's how I finally got into 10.5.12.IN21AA (Global ROM) on my IN2017:
This fixed my issues with not being able to flash critical partitions (because I suspect they re-lock when fastbootd switches into bootloader if you manually do it). Now it doesn't hang at all. I am going to play around with this to make sure I didn't miss anything and see if it works with other TMo firmware versions and the newer 11.0 Global ROM.
- Just to be safe (not sure if it's necessary) boot into TEST MODE on your Windows machine. I did all of this from Test Mode.
- Download the files from the zip attached at the bottom of the first post on this thread. Install both files (OnePlus USB Drivers and QDLoader HS-USB Driver).
- At some point I THOUGHT I installed the Fastboot drivers, but maybe I messed that part up or maybe it was before I was in Test Mode. Regardless, download the Google fastboot driver zip in this post. Unzip it to your desktop.
- Open the extracted folder and then the usb_driver folder inside, then right-click on the android_winusb.inf file and select Install. Confirm the installation.
- Plug in your phone.
- Open Device Manager. Your phone should show up under "Universal Serial Bus controllers" as "IN2017" when it is in CHARGING ONLY mode, and under Portable Devices when in File Transfer mode or PNP mode. If not, you'll need to fix your USB drivers from step 2 above.
- Make sure you can get adb commands to work, then reboot to the bootloader ("adb reboot bootloader" should get you to the FastBoot Mode menu with the big green "START" banner at the top) and make sure fastboot commands also work ("fastboot devices" will show you if your phone is detected properly).
- Check Device Manager again while in bootloader mode - your phone should now show up under "Android Phone" as "Android Bootloader Interface." If it shows up as IN2017 with an exclamation mark, you need to fix the issues with the fastboot driver in step 4 above. I actually did this step while at the "waiting for device" message while flashing the Global ROM and it kick-started the installation's second phase.
- I also followed some steps from this post by @awsan - I copied the entire platform-tools folder that I downloaded from his post (r31.0.2) into the 10.5.12-GLOBAL folder, replacing all duplicate files. I don't think booting into fastboot like he says to do (language selection splash screen) worked, I had to boot into the bootloader from there to get the flash-all.bat to start.
- From here, I think I just double-clicked the flash-all.bat and everything worked properly - with the note that I was stuck at "waiting for device" after the first reboot command in the middle of the installation. The process in step 4 got me through this.
I have not tried locking the bootloader yet.
Oh, and 5G and VoLTE both appear to be working.
I couldn't help myself. I factory reset the phone. It works better after the factory reset. Android 11 didn't run all that well on the OnePlus 8. It drained the battery much faster than Android 10. I am happy to have Android 12 on it now.unless you are having issues with the phone, i dont think you need to reset it. C.16 seems to be super stable with respect to battery life and performance. I see only minor bugs like Processor name showing incorrectly (865 reported as 855), battery % not showing in status bar on swipe down etc.
In short, you should be fine without a factory reset
unless you are having issues with the phone, i dont think you need to reset it. C.16 seems to be super stable with respect to battery life and performance. I see only minor bugs like Processor name showing incorrectly (865 reported as 855), battery % not showing in status bar on swipe down etc.
I have the dual sim tray and I've tried to put 2 sims in it (visible and Verizon) while on OOS12 and it only reads sim 1, sim 2 does not connect and everything is grayed out. So unfortunately 12 still does not support dual sim.I read that same IMEIs are not an issue. I was reading this in OP7 Pro forums and that phone after unlock and international firmware update supports dual sim with same IMEI.
Again I am not an expert here but I was hoping that OOS 12 C.16 would have enabled dual sim support somehow. I do not have a dual sim tray so I cannot check this myself. So if someone has a dual sim tray and on C.16 global firmware, I would love to know if this is working or not
Sorry for spamming the board today, but I think I figured it out.I tried again, MSM to 10.5.7, unlocked bootloader, rebooted to bootloader, flash-all.bat, and I'm still getting errors on the critical partitions. And I can't figure out how to unlock the critical partitions (probably not allowed in TMo firmware).
I'm going to MSM to 10.5.22 and see if that makes any difference.
EDIT: No dice. 10.5.22 made no difference. The issue is the locked critical partitions. If anybody has any solutions please tag me.
IN2017 is Tmobile version of the phone and updates are late and you cant sideload an update because it is not available on carrier versions of the phone. Converting it to International version gives access to the latest updates, and some other features that weren't available to Tmobile version. If you do this method, you will lose Safetynet which is the ability to use bank apps and etc. So after converting you have to lock the bootloader if you wish to do anything related to banking.Thanks for the guide!! I just submitted my request to T-Mobile to unlock my boot loader so now I play the waiting game...
In the meantime, can someone please clarify what does converting from IN2017 to International achieve? Ultimately my goal is to flash a custom ROM - not sure if I can do this directly after unlocking my boot loader.
I am confused between this guide and the old one " Covert to Global ( WIP ) . Which one is best guide to convert OP8 TMO Android 11 to Global ?
Should I back up/ change modem with this guide ?
Is there diff between EU and Global ROM/modem/etc. to use 5G in USA and other oversea countries ?
I want Always On Display ( AOD ) , which ROM EU or Global will have it ?