Upgraded to Android 12. It shows IN2015 instead of IN2017. No big deal. I have the Tmobile version on the global OS. Should I do a factory reset of the phone since I upgraded from Android 11 to Android 12?
[GUIDE] Complete Step-by-Step Convert T-Mobile to Global (or other) firmware
- Thread starter thattechguy_69
- Start date
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
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
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.
D
Deleted member 8880810
Guest
Did you factory reset in the settings of android 12 or did you use recovery to do it?
it dont matter either way. if you factory reset on ur phone it will go to recovery immediately and factory resets there
D
Deleted member 8880810
Guest
The reason I ask is because on Android 11 I factory reset using the settings and it rebooted into recovery and ran a script but I still had all my photos and text messages.
Just an update on the OOS 12... I ended up rolling back using the rollback app and OOS 11 zip provided by Oneplus...
forums.oneplus.com
OOS 12 lost the ability to output from USBC to HDMI/DVI and I was unable to use it with a monitor at work. Probably not a feature that many uses, but for me it was a big deal. The only issue was what I mentioned earlier with using it with visible as a carrier. Looks like even if you got it connected, restarting the phone will lose the carrier again and you had to switch sim card in order to get the signal back which is a pain if your phone restarted unexpectedly while you're out.
Hope this is useful for others...
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
OOS 12 lost the ability to output from USBC to HDMI/DVI and I was unable to use it with a monitor at work. Probably not a feature that many uses, but for me it was a big deal. The only issue was what I mentioned earlier with using it with visible as a carrier. Looks like even if you got it connected, restarting the phone will lose the carrier again and you had to switch sim card in order to get the signal back which is a pain if your phone restarted unexpectedly while you're out.
Hope this is useful for others...
Normally I do it using the buttons. This time I did it within the system settings. I am still testing out this phone.
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.
Yes. OOS 11 at least can recognize the second sim, but OOS 12 completely block the second one. No doable way so far.
yeah downgrade to oos 10, do fastboot method, then update and after update then lock bootloader
The battery life on Android 12 is much better for me than Android 11. I think it's equal to the battery life on Android 10.
since it seems a11 is a dumpster fire on the oneplus8 tmobile can going to global keep it on a10?
you can keep it on global a10, there are tutorials on yt but you are gonna lose L1 and will be on L3 until you update.
the phone seems stable on its original a10 but tmobile keeps forcing a11 on it. o gotta do something as its not very usable. or is there another stable option that anybody is aware of?
Last edited:
Sorry boss. Can I install a custom rom on oneplus 8 T-Mobile version? If so, could you explain how? I tried to do it and it gave me error QUALCOMM CrashDump Mode
Similar threads
Top Liked Posts
-
1
You can try this
(Need Root)
I quote
""
For OnePlus 8t kb2007 T-Mobile users who can't get their dual sims to work on nameless
Type this in termux
su
setprop persist.vendor.radio.multisim_switch_support true
setprop persist.radio.multisim.config dsds
Then reboot , dual sims works perfectly
tested on my device OnePlus 8t kb2007 using nameless 13""1 -
1
No, unfortunately I have the Verizon variant and can't flash OxygenOS 12 or 13.1
I had something similar and I came across this thread -
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
You sir are saint...I've been trying to get...
forum.xda-developers.com
what worked for me was this post in the above thread -
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
You sir are saint...I've been trying to get...
forum.xda-developers.com
111 -
23*** Use this at your very own risk.
*** You will lose all data
*** Backup your working modem and persist, just in case.
*** USE USB 2.0 Port and Windows Machine
Part 1: Return to T-Mobile Stock Firmware via MSM TOOL
Turn on Test Mode, Disable Device Driver Signing via Powershell and set Time Date to 2017, then restart PC
Code:bcdedit.exe /set nointegritychecks off bcdedit.exe /set testsigning off
1. Launch MsmDownloadTool V4.0.exe.
2. On the login prompt select "Other" in the dropdown menu and click on Next.
3. Click on Target button and select TMO.
4. Press Start button so that it waits for your device to be connected
5. Power off your device
6. Put your phone in EDL mode
- by completely turning off your device, hold vol up + vol down and plug in the cable
- via ADB command
7. Once phone is in EDL Mode, immediately Click ENUM button and then START buttonCode:adb reboot edl
Wait approximately ~250-300 seconds.
Device will reboot afterwards.
Part 2: Unlock Bootloader with no code and apply Dual SIM
After reboot, Turn on OEM Unlock in Developer Options before proceeding with the steps
1. Rename and move “instantnoodlet_15_O.16_201001.ops” from MSM Tool directory to somewhere else (e.g., Documents Folder)
2. Download "unlock.ops" and rename it to instantnoodlet_15_O.16_201001.ops
3. Move the "renamed unlock.ops" to MSM Tool directory
4. Launch MSM Tool and proceed using the steps from Part 1
MSM Tool will finish flashing in under 15 seconds and the device will reboot with the message, "<!> The device is corrupt.."
5. Unplug phone from PC and Force Shutdown device by simultaneously press and holding Power and Vol buttons till the device reboots
6. Let go of all buttons once you see device reboot with the logo FASTBOOT MODE, the big START logo will appear afterwards
7. Open SDK Platform Tools folder and launch Powershell/CMD from there
8. Copy and paste this command to check if device is recognized in FASTBOOT
9. Once device isrecognized by terminal, copy and paste this other commandCode:fastboot devices
10. A confirm bootloader prompt will appear, use Vol buttons to hover on UNLOCK THE BOOTLOADER and to confirm, simply press Power buttonCode:fastboot flashing unlock
Once confirmed, device will reboot back to T-Mobile Firmware but now with Dual SIM and an unlocked bootloader. To use the MSM Tool again without the "unlock.ops", move the unlock.ops to a different place and put back the original ops.
Part 3: Converting to other regions (e.g., Global, EU, Indian) and lock Bootloader
*** Cannot lock bootloader after flashing Fastboot ROM. Will corrupt device
*** As of right now, Dual SIM doesn't work on OOS12/13 Indian Firmware
1. Download this Fastboot ROM
2. Open Fastboot ROM Folder, click flash-all.bat and type and enter "y" to the terminal
Code:Do you want to wipe all the data ( Reccomended )[Y/N]?y < waiting for any device >
3. Reboot phone to FASTBOOT MODE and plug the phone back to the PC
4. Once the process is done, find an OTA ZIP from this thread to update to and download it
(You can use ota.zips from any region whether it be EU/India/Global, e.g., OxygenOS 11 Global 11.0.11.11)
5. put the OTA ZIP in the phone, update it and reboot
After rebooting, you can either lock bootloader or stay unlocked to root
6. To lock bootloader, reboot to FASTBOOT and plug phone in to PC
7. Open platforms-tool and open a terminal from the folder
8. Copy, paste and enter this command:Code:fastboot flashing lock
9. Confirm the prompt LOCK THE BOOTLOADER and the phone will perform a factory reset and reboot.
There you go! What you can do at this point is stay and daily drive OxygenOS 11 or update to OxygenOS 12/13 or even ColorOS. Dual SIM will work on any Firmware Region. The phone's model will also permanently change to IN2015=OnePlus 8 Global Version Model unless you go back and use MSM Tool again with the original ops.11
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:
- 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.4I managed to successfully convert my OP8 to the global version this morning.
Here are a few things I can confirm:
- 5G and VoLTE are working on my device (Rogers network in Canada)
- Banking apps work as expected
- Widevine certification is exactly as it was prior (L1), meaning I can stream in full HD/HDR with Netflix
- I was able to OTA update to the latest 11.0.10.10 without any issues at all
My first attempt trying this was a month ago. I was lazy and didn't roll the phone all the way back to Android 10 using the MSM tool. So I tried using "flash-all" with a newer global package and it did not work (crashdump error). Figured it was worth a shot... for whatever reason it just doesn't work. Ended up restoring with the MSM tool.
This time, I did this:
- Reverted back to official T-Mobile Android 10 using the MSM tool
- Unlocked my bootloader using the all-in-one tool + my unlock token
- Used the all-in-one tool to flash the global fastboot ROM (Android 10) linked in the original post
- Manually flashed the EU update from the device (also linked in original post)
- Locked the bootloader using the all-in-one tool
- Used the Oxygen Updater app to download the latest global full release (11.0.9.9) and installed it from my device
- Performed an OTA update, bringing me to 11.0.10.10
3
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.3
Yeah, it's not entirely clear to me, either.
This is what you should do:
(1) Put your phone back on Android 10 TMobile firmware using one of the packages with msmdownloadtool. I used 10.5.7
(2) Unlock bootloader.
(2*) Get TWRP boot image. Put phone in fastboot mode, type:
fastboot boot twrpimage.img
After TWRP boots, take a backup of your persist and modem partitions (I recommend using dd to do it, here's an example: dd if=/dev/block/boot device/by-name/persist of=/sdcard/persist.img.ext4). You could probably use TWRP to do the backup, but that's on you. Transfer them off of the phone and safeguard them.
Now reboot from TWRP to fastboot mode. Unlock the bootloader, reboot to fastboot mode, and flash a 10.x euro or global ROM with fastboot. The guide says Euro, but I suspect you could use global, also. The goal is to have it running 10.x firmware (that's not for a carrier variant). After that boots, download the latest global OTA zip onto your internal sdcard. Open the updater in Settings, then select the file. After it updates, reboot to see if everything is OK. If it is, boot to fastboot and relock the bootloader.
The
New posts
-
-
-
-
[ROM][OFFICIAL][ginkgo][13] crDroidAndroid v9.x- Latest: NotowanyWieslaw