Database Info

Gyroscope and Proximity Sensor not working

Hi Team,
On the latest OOS 10.3.2. Have done multiple resets, downgraded using msm tool to OOS 5.1.3 and then manually updating them. Factory reset done a couple of times.
Anyone can help?
Currently running Magisk 20.4, bootloader unlocked.

Same here
I even tried using msmtool and even installing custom rom still no luck in fixing this issue . Most irritating part about this is not able to use auto rotate .

Possible Fix
Hey! I made an account today to hopefully help youins. I was also struggling with this issue, and I couldn't find anyone with a working solution. After trying resets and full msm tool restores of different android versions (I tried the standard 5.1.5, 9.0.0, and 10.3.2), I figured out my issue and fixed it.
For me, I would do an msm to android 8 (5.1.5). This is the link on the main forum for " [TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" by Fivegates. (I would link it, but I don't know if that's allowed or not.) After doing the reset, Everything worked! However, after letting the phone update to 9.0.9 by it's self with the update tool in settings, I would lose the ability to use wifi. After forcing the next update to 10.3.2, I would lose the gyro and Prox sensor again. I then tried the msm tool from a different site that went straight to 10.3.2 ... No dice. Same issue. So, I figured that the phone needed one of the updates between 5.1.5 and 9.0.9. I started trying some updates between, and here was my final process to get back up and running! (it took a while. haha)
FIX
1. MSM tool to 5.1.5 by following the MsmDownloadTool post from fivegates. (This will wipe all data and re-lock bootloader.)
2. After phone boots, run through set-up, but don't let phone update.
3. Download the full OTA for Oneplus 6, version 9.0.0. It can be found in an xda post, or elsewhere. Again, don't know if I can link anything.)
4. Put the zip on your Oneplus and use the updater in settings to preform an update from local storage. (You tap the top right corner menu and select local upgrade.)
5. Once updated to 9.0.0, let the phone do the next two updates. At the time of this guide, the first will be to 9.0.9 , and the second to 10.3.2.
6. After that, I had a working gyro and Prox sensor on 10.3.2. From there, I unlocked the bootloader, booted twrp, and carried on my rom installs like normal.
I hope this helps!

oldmanz said:
Hey! I made an account today to hopefully help youins. I was also struggling with this issue, and I couldn't find anyone with a working solution. After trying resets and full msm tool restores of different android versions (I tried the standard 5.1.5, 9.0.0, and 10.3.2), I figured out my issue and fixed it.
For me, I would do an msm to android 8 (5.1.5). This is the link on the main forum for " [TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" by Fivegates. (I would link it, but I don't know if that's allowed or not.) After doing the reset, Everything worked! However, after letting the phone update to 9.0.9 by it's self with the update tool in settings, I would lose the ability to use wifi. After forcing the next update to 10.3.2, I would lose the gyro and Prox sensor again. I then tried the msm tool from a different site that went straight to 10.3.2 ... No dice. Same issue. So, I figured that the phone needed one of the updates between 5.1.5 and 9.0.9. I started trying some updates between, and here was my final process to get back up and running! (it took a while. haha)
FIX
1. MSM tool to 5.1.5 by following the MsmDownloadTool post from fivegates. (This will wipe all data and re-lock bootloader.)
2. After phone boots, run through set-up, but don't let phone update.
3. Download the full OTA for Oneplus 6, version 9.0.0. It can be found in an xda post, or elsewhere. Again, don't know if I can link anything.)
4. Put the zip on your Oneplus and use the updater in settings to preform an update from local storage. (You tap the top right corner menu and select local upgrade.)
5. Once updated to 9.0.0, let the phone do the next two updates. At the time of this guide, the first will be to 9.0.9 , and the second to 10.3.2.
6. After that, I had a working gyro and Prox sensor on 10.3.2. From there, I unlocked the bootloader, booted twrp, and carried on my rom installs like normal.
I hope this helps!
Click to expand...
Click to collapse
your the best man i can finally use other ROMs again
my fix was to use oneplus 7 port on my 6 but it was annyoing me

oldmanz said:
Possible Fix
Hey! I made an account today to hopefully help youins. I was also struggling with this issue, and I couldn't find anyone with a working solution. After trying resets and full msm tool restores of different android versions (I tried the standard 5.1.5, 9.0.0, and 10.3.2), I figured out my issue and fixed it.
For me, I would do an msm to android 8 (5.1.5). This is the link on the main forum for " [TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" by Fivegates. (I would link it, but I don't know if that's allowed or not.) After doing the reset, Everything worked! However, after letting the phone update to 9.0.9 by it's self with the update tool in settings, I would lose the ability to use wifi. After forcing the next update to 10.3.2, I would lose the gyro and Prox sensor again. I then tried the msm tool from a different site that went straight to 10.3.2 ... No dice. Same issue. So, I figured that the phone needed one of the updates between 5.1.5 and 9.0.9. I started trying some updates between, and here was my final process to get back up and running! (it took a while. haha)
FIX
1. MSM tool to 5.1.5 by following the MsmDownloadTool post from fivegates. (This will wipe all data and re-lock bootloader.)
2. After phone boots, run through set-up, but don't let phone update.
3. Download the full OTA for Oneplus 6, version 9.0.0. It can be found in an xda post, or elsewhere. Again, don't know if I can link anything.)
4. Put the zip on your Oneplus and use the updater in settings to preform an update from local storage. (You tap the top right corner menu and select local upgrade.)
5. Once updated to 9.0.0, let the phone do the next two updates. At the time of this guide, the first will be to 9.0.9 , and the second to 10.3.2.
6. After that, I had a working gyro and Prox sensor on 10.3.2. From there, I unlocked the bootloader, booted twrp, and carried on my rom installs like normal.
I hope this helps!
Click to expand...
Click to collapse
Thank you kind person. For more than two months I tried to return the phone to normal operation and all to no avail. So I came across your post and now my phone is full again. Thank you very much.

oldmanz said:
Possible Fix
Hey! I made an account today to hopefully help youins. I was also struggling with this issue, and I couldn't find anyone with a working solution. After trying resets and full msm tool restores of different android versions (I tried the standard 5.1.5, 9.0.0, and 10.3.2), I figured out my issue and fixed it.
For me, I would do an msm to android 8 (5.1.5). This is the link on the main forum for " [TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" by Fivegates. (I would link it, but I don't know if that's allowed or not.) After doing the reset, Everything worked! However, after letting the phone update to 9.0.9 by it's self with the update tool in settings, I would lose the ability to use wifi. After forcing the next update to 10.3.2, I would lose the gyro and Prox sensor again. I then tried the msm tool from a different site that went straight to 10.3.2 ... No dice. Same issue. So, I figured that the phone needed one of the updates between 5.1.5 and 9.0.9. I started trying some updates between, and here was my final process to get back up and running! (it took a while. haha)
FIX
1. MSM tool to 5.1.5 by following the MsmDownloadTool post from fivegates. (This will wipe all data and re-lock bootloader.)
2. After phone boots, run through set-up, but don't let phone update.
3. Download the full OTA for Oneplus 6, version 9.0.0. It can be found in an xda post, or elsewhere. Again, don't know if I can link anything.)
4. Put the zip on your Oneplus and use the updater in settings to preform an update from local storage. (You tap the top right corner menu and select local upgrade.)
5. Once updated to 9.0.0, let the phone do the next two updates. At the time of this guide, the first will be to 9.0.9 , and the second to 10.3.2.
6. After that, I had a working gyro and Prox sensor on 10.3.2. From there, I unlocked the bootloader, booted twrp, and carried on my rom installs like normal.
I hope this helps!
Click to expand...
Click to collapse
Thanks a lot man !!!!

Following your steps, the automatic brightness and also the automatic screen rotation works for me again.
Thank you @oldmanz

New (to me) TMo OP7Pro and my plans - will this work?

I just bought one of those in-store display models off of eBay for ~$270 to play around with while I'm waiting for my next phone. First of all, those phones have incredibly severe screen burn-in - I don't recommend them.
The unit I bought was a T-Mobile model that is sim-unlocked (I'm also on T-Mobile, so I can eventually legitimately unlock it myself, if necessary, as I'll be running it on a spare line).
My high-level goals are:
1. Flash to Int'l
2. Flash & run xXx NoLimits
3. Flash & run Open Beta
4. Call Screening is a must! (I understand xXx NoLimits has it built-in but this is my Plan B for enabling it: Google Call Screening)
This is my more scripted-out plan for accomplishing these things:
0. Check out the device in general, make sure it works, and do a factory reset.
1. Install Drivers (Plug phone in -> install from Windows Explorer USB file share thingie)
2. Use MSM to flash stock TMo firmware
3. Fully update it via System -> Check for Updates
4. Use MSM to flash to int'l
5. Factory reset & fully update via System -> Check for Updates
6. Flash the latest Open Beta
7. Unlock bootloader, Flash TWRP, and install Magisk. (alternate guide)
8. Flash & run xXx NoLimits
9. Flash & run Open Beta
My general questions:
1. Is this a solid plan?
2. Am I missing anything important here?
3. Will these things work together?
4. What "gotchas" might I run into? Netflix support? Play Store support? Functional Call Screening? Anything else?

Jaxidian said:
I just bought one of those in-store display models off of eBay for ~$270 to play around with while I'm waiting for my next phone. First of all, those phones have incredibly severe screen burn-in - I don't recommend them.
The unit I bought was a T-Mobile model that is sim-unlocked (I'm also on T-Mobile, so I can eventually legitimately unlock it myself, if necessary, as I'll be running it on a spare line).
My high-level goals are:
1. Flash to Int'l
2. Flash & run xXx NoLimits
3. Flash & run Open Beta
4. Call Screening is a must! (I understand xXx NoLimits has it built-in but this is my Plan B for enabling it: Google Call Screening)
This is my more scripted-out plan for accomplishing these things:
0. Check out the device in general, make sure it works, and do a factory reset.
1. Install Drivers (Plug phone in -> install from Windows Explorer USB file share thingie)
2. Use MSM to flash stock TMo firmware
3. Fully update it via System -> Check for Updates
4. Use MSM to flash to int'l
5. Factory reset & fully update via System -> Check for Updates
6. Flash the latest Open Beta
7. Unlock bootloader, Flash TWRP, and install Magisk. (alternate guide)
8. Flash & run xXx NoLimits
9. Flash & run Open Beta
My general questions:
1. Is this a solid plan?
2. Am I missing anything important here?
3. Will these things work together?
4. What "gotchas" might I run into? Netflix support? Play Store support? Functional Call Screening? Anything else?
Click to expand...
Click to collapse
After reading all of that, just give up because you have no idea what you're doing. Why flash a ROM if you are flashing open beta? Open beta is the beta version of stock ROM(OOS) so it will overwrite xxx rom

jamescable said:
After reading all of that, just give up because you have no idea what you're doing. Why flash a ROM if you are flashing open beta? Open beta is the beta version of stock ROM(OOS) so it will overwrite xxx rom
Click to expand...
Click to collapse
My bad, I thought I posted in a Q&A forum where questions were encouraged. I also thought the Open Beta was an OTA update on top of stock OOS and that xxx claimed things like "Still working after OOS version upgrade" and "Support OOS Stock Rom OTA's" and "When a new OOS OTA is available, just run the OOS update, flash Magisk again and xXx NoLimits is still in place and working like before".
Not sure what your problem is but go piss in somebody else's punch bowl.

Jaxidian said:
My bad, I thought I posted in a Q&A forum where questions were encouraged. I also thought the Open Beta was an OTA update on top of stock OOS and that xxx claimed things like "Still working after OOS version upgrade" and "Support OOS Stock Rom OTA's" and "When a new OOS OTA is available, just run the OOS update, flash Magisk again and xXx NoLimits is still in place and working like before".
Not sure what your problem is but go piss in somebody else's punch bowl.
Click to expand...
Click to collapse
I am running open beta on a stock TMobile 7pro. Works great. You don't need to do all the updates. Just flash the open beta after you switch to international.

Hey if u do the call screening magisk way. Be sure to use the Google dailer 39. Apkmirror and make sure the updates is turned off for it.

Alright, so I was in the same boat as you, I bought a T-Mobile 7 Pro model earlier in the week; and nicely asked T-Mobile support through the App a few times to help me SIM-Unlock it so I could do my bootloader unlock and linked the Oneplus Support website and the Unlock page.
I ran into many issues so I'll help you out as I just finished my 6 day journey of making it functional.... Along the way, I lost cell service, I lost all my sensors.... So I'd recommend taking a TWRP backup everytime you're able to successfully boot into the device; Note: my goal was Havoc, so I ended up in a different place than where you're trying to go. I don't know what exact problems you'll run into, but I'm letting you know what I think makes sense from my previous experience over the week.
Your scripted-out plan:
0. Sure, test it, but you'll end up automatically wiping it later when you unlock the bootloader.
1. Sure, install the drivers.
2. You probably don't need to flash stock T-Mobile firmware as it's already running it.
3. You probably don't need to update it.
4. Yes, Flash it to international.
5. You probably don't need to update it. However I'd recommend to unlock the bootloader here;
5a. (The Damned T-Mobile model makes flashing TWRP a bit difficult) I'd recommend taking a note on what Slot is currently active (A or B).
Use "fastboot getvar current-slot" to find out; Then I'd recommend switching to the other slot ( If you're on Slot A, switch to Slot B, vice versa) to flash TWRP first (this overrides your boot image on your active slot, but is the only way to boot TWRP on the T-Mobile variant) and then flash the TWRP installer (this will flash TWRP to both Slots).
5b. After using the TWRP installer from your 2nd Slot, Use TWRP to swap back to the 1st Slot. Now make a complete full TWRP backup with all the boxes checked. Then, copy that backup to your computer so that it won't get wiped in the next few steps. (Do not skip this. If you did this correctly, You will have a place to come back to just in case you **** up your sensors, and cell service like I did.).
5c. Doublecheck if you can actually boot to your original Slot and if everything's functioning. Check if you can boot to your other Slot and see if everything's functioning. (This is where you super-need to make sure you have a safe place to come back to).
6. Sure, you can try flashing the latest Open Beta, but you might have to install TWRP again back in step 5b.
7. You might or might not have to unlock the bootloader, depending on what method you use to flash the Open Beta, your bootloader status might save; Sure, flash Magisk using TWRP.
8. Sure, flash xXx NoLimits using Magisk Manager.
9. Why undo your work and flash the Open Beta again? Don't do this.
With that you should be done.
If at any point you had an issue, I'd recommend using the TWRP backup you created earlier in 5b.
If you super-super have an issue, you'll have to use MSM to go back to stock International firmware.
In my case.... I had super-super issues and I had no TWRP backups.... and I had to use MSM to go back all the way back to T-Mobile stock firmware and start over because I had no service, and no sensors (proximity, gyroscope, accelorometer, etc).
But in the end, I think I have everything functioning the way I want to on HavocOS.

It's been a minute but I now have an update to my journey.
I had to take a quick pause at step 4 of my plan. The phone was SIM-unlocked but the bootloader itself was locked. So I had to do the dance with OnePlus and wait a couple weeks for that unlock code. Well, I finally got that puppy, so was able to start this project this weekend. Here's what I've done and where I'm at so far:
0. Device checked out well. Works great, aside from the screen burn-in issues (which is why I got it so dang cheap).
1. Drivers installed. ADB & Fastboot work great.
2. I used MSM to flash back to TMo firmware after my previous failings when I hit the locked bootloader wall. It worked great to get me to the point where I could generate the phone unlock code request to send to OP.
3. Not needed, although I did this while waiting 2 weeks for OP to send me a code.
4. Done. Worked perfectly. Hello, TMo-less firmware. Also, hello SIM #2 (the 2-week delay gave me time to buy a dual-sim tray).
5. Factory reset as part of the flashing and unlocking. Not bothering with system updates yet.
6. Not yet done this.
7. Bootloader is now unlocked. Magisk is installed but TWRP is not yet installed. This is where I'm at now.
Not hitting any problems. Just ran into dinnertime and my kiddo's bedtime. Thought I'd post this update before I started back up. So far, so good, other than that surprise 2-week delay waiting for an email.

New OnePlus 7Pro Owner Questions

I have purchased a OnePlus 7 Pro from a friend of mine. He has already changed it from the T-Mobile to the International version via MSM. The current build number is 9.5.3.GM21AA and model number GM1915. I have currently installed TWRP 3.3.1-0 and rooted with Magisk 20.4. As I am new to OnePlus, I am confused as to go about updating the stock firmware, if I will lose root, updating to a custom rom. I have done this with other phones, Nexus 6P, 5X, Pixel 1 and Essential PH-1, but this seems different as I have a build number that is not necessarily meant for the T-Mobile version of this phone. I have read multiple guides and instructions throughout this forum, but don't seem to find the answers for my specific phone. Any help and direction would be very helpful.

If the phone has been updated to the international version then that's a REALLY old version, the latest version for International (Global) is 10.3.5, have you checked for an update via the phone already?
Update settings are in Settings > System > System Updates
If you want to upgrade manually, you can do that via Settings > System > System Updates > (Top Right) > Local Upgrade (Make sure the zip is in the main storage folder though or it won't be listed)
However, If you want to upgrade and keep root then you need to upgrade TWRP first, the latest is 3.4.0-0 from here : https://twrp.me/oneplus/oneplus7pro.html
Flash that first.
I've uploaded both the most recent versions onto my Android File Host :
Oxygen OS - Android 10.3.5 - Global - OnePlus 7 Pro (GM21AA) : https://www.androidfilehost.com/?fid=8889791610682950702
Oxygen OS - Android 10.0.8 - EU - OnePlus 7 Pro (GM21BA) : https://www.androidfilehost.com/?fid=8889791610682950715
My Android 10 Folder : https://www.androidfilehost.com/?w=files&flid=296897
So....
Grab the international version (which is the full rom)
Download the latest TWRP and Magisk
Reboot to TWRP (3.4.0-0)
Flash the full rom build (do not reboot yet)
Flash TWRP 3.4.0-0 (before rebooting) then reboot back into recovery
Flash latest Magisk then clear cache (not data)
Reboot
Check the Magisk version with the app : https://github.com/topjohnwu/Magisk/releases
I would suggest choosing the beta release in the app as Magisk 21.0 is available and works fine (see attached)
If it shows that the phone is not rooted then just reboot back into TWRP and flash Magisk again and reboot.
-----------------
If you're going to install a custom rom then ensure you read the first posts in the thread first as the dev will usually advise pre-requisites (i.e. A specific stock rom version to have installed first, a specific version of TWRP to use, etc)
(Also, try to use paragraphs, makes your post a lot more legible)

Thank you for the information, it is very helpful!!
I am currently on 9.3.5 which is how I got it from my friend. I was thankfully for it. I will review the files and upgrade when I get home from work and then look into crDroid 6.10. It has worked great on my PH-1.
In the event I need to reflash to stock, do I just Fastboot back?

njsges said:
Thank you for the information, it is very helpful!!
I am currently on 9.3.5 which is how I got it from my friend. I was thankfully for it. I will review the files and upgrade when I get home from work and then look into crDroid 6.10. It has worked great on my PH-1.
In the event I need to reflash to stock, do I just Fastboot back?
Click to expand...
Click to collapse
No, if you change rom you should really clear data so make sure you do backups before moving from rom to rom. As long as you still have TWRP you should be able to move between them.

djsubterrain said:
No, if you change rom you should really clear data so make sure you do backups before moving from rom to rom. As long as you still have TWRP you should be able to move between them.
Click to expand...
Click to collapse
Thank you again for your help!! The more I've used the Oxygen OS, it seems to have everything the custom roms have that I might need.
I did get an update message on Oxygen Updater app to install 10.0.3, also an older version. Per what you wrote previously, I am going to bypass that to 10.3.5.

njsges said:
Thank you again for your help!! The more I've used the Oxygen OS, it seems to have everything the custom roms have that I might need.
I did get an update message on Oxygen Updater app to install 10.0.3, also an older version. Per what you wrote previously, I am going to bypass that to 10.3.5.
Click to expand...
Click to collapse
Check this thread first : https://forum.xda-developers.com/oneplus-7-pro/help/how-to-convert-tmobile-op7-to-t3935947
Especially the part labelled *Future proofing Update*, the OPS file is part of the MSM fix.
You should really check in that thread first to confirm how to update properly. The process might be different since you're changing firmware.

djsubterrain said:
Check this thread first : https://forum.xda-developers.com/oneplus-7-pro/help/how-to-convert-tmobile-op7-to-t3935947
Especially the part labelled *Future proofing Update*, the OPS file is part of the MSM fix.
You should really check in that thread first to confirm how to update properly. The process might be different since you're changing firmware.
Click to expand...
Click to collapse
Thank you. The phone has already been switched from T-Mobile to Global. I'm not sure if the OPS patcher was done yet. I will text my friend and ask him. I wonder if it is detrimental to do it again while I am still on 9.3.5?
UPDATE: My friend flashed the ops file with the MSM tool download

SUCCESS!! Thank you for all of your help!!

Question Unable to update to A13 after MSM soft brick recovery on LE2115.

I have an LE2115. I tried to update install CRdroid, and during the process the guide required an upgrade to firmware F18.
I was already on the newest (F20 I think) firmware, so I figured a small roll back would be needed. I downloaded F18 from the CRdroid firmware link, and when it was run it ended up bricking the phone. Annoying, but I didn't think it the end of the world.
To unbrick it I downloaded the MSM global 11.2.10.10 and flashed the phone with A11 (11.2.10.10). I was able to get back into the phone, and everything seemed ok at first glance.
The problem is now I can't install any updates to get it back to android 13.
If I do a system ->system update -> check for updates -> download and install. It says it downloads update LE2115_11.F.17_2170_20021123112, installs it, and reboots.
After rebooting the phone shows a successfully installed update message, but when I look at under About the system is still on Android 11 (11.2.10.10). No change at all.
If I try sticking the OTA zip LE2115_11.F.17_2170_202211231112 in root, and using that for a local update the phone gives me a update failed message after a few seconds. No useful error messages at all.
Can someone point me in the right direction? I can't figure out how to get this off A11 and back to A13 (F18).
This is making me want to rip out my hair as everything I have tried has failed to get me onto a current firmware.

wizardknight said:
I have an LE2115. I tried to update install CRdroid, and during the process the guide required an upgrade to firmware F18.
I was already on the newest (F20 I think) firmware, so I figured a small roll back would be needed. I downloaded F18 from the CRdroid firmware link, and when it was run it ended up bricking the phone. Annoying, but I didn't think it the end of the world.
To unbrick it I downloaded the MSM global 11.2.10.10 and flashed the phone with A11 (11.2.10.10). I was able to get back into the phone, and everything seemed ok at first glance.
The problem is now I can't install any updates to get it back to android 13.
If I do a system ->system update -> check for updates -> download and install. It says it downloads update LE2115_11.F.17_2170_20021123112, installs it, and reboots.
After rebooting the phone shows a successfully installed update message, but when I look at under About the system is still on Android 11 (11.2.10.10). No change at all.
If I try sticking the OTA zip LE2115_11.F.17_2170_202211231112 in root, and using that for a local update the phone gives me a update failed message after a few seconds. No useful error messages at all.
Can someone point me in the right direction? I can't figure out how to get this off A11 and back to A13 (F18).
This is making me want to rip out my hair as everything I have tried has failed to get me onto a current firmware.
Click to expand...
Click to collapse
I have the same device. After the 11.2.10.10 comes C48 first a12 build but it's marked F17 update. Then comes C-66 it's also marked F-17. Take it. Next update you guessed is labeled F-17 and it is actually F-17. Android 13. Then you will get F-18 ota as well. Then have to go into oxygen updater from playstore and update to F20. Latest with Jan sec patch. Since they dropped Android 13 all their device updates for op9 are labeled wrong. After msm you started on 11.2.4.4. I flash lineage and mess with things but mostly stay on stock as it's great and cam is good on os. Good luck. Check out pixelify by Kingsman 44. Real nice for op9 also.

mattie_49 said:
I have the same device. After the 11.2.10.10 comes C48 first a12 build but it's marked F17 update. Then comes C-66 it's also marked F-17. Take it. Next update you guessed is labeled F-17 and it is actually F-17. Android 13. Then you will get F-18 ota as well. Then have to go into oxygen updater from playstore and update to F20. Latest with Jan sec patch. Since they dropped Android 13 all their device updates for op9 are labeled wrong. After msm you started on 11.2.4.4. I flash lineage and mess with things but mostly stay on stock as it's great and cam is good on os. Good luck. Check out pixelify by Kingsman 44. Real nice for op9 also.
Click to expand...
Click to collapse
Ok. Thanks. I will run the update multiple times, and see if I can get to F18.
I can't believe the naming is all buggered up. Ok, well maybe I can believe it. Seems like OnePlus is just not doing a good job anymore, but there are not many other flagship grade phones with unlocked boot loaders and custom roms anymore (and I have been using custom android roms since the touch pro 2 days). It's making me a sad panda.
I just upgraded from a OnePlus 7t to the 9 because I got a crazy good price for an open box phone on clearance. Now I am starting to wonder if I made the wrong decision.
If I have to download 5+ updates every time something doesn't flash right I am going to burn though my 1TB internet cap in no time.
Update:
After ~10gb of updates I got to F18.
Now to go and get a custom rom on this thing, and hope I don't have to unbrick it again.

Question Flashing Androd 14

Might be a noob question but can i flash Android 14 DP2 to an inactive slot and switch back to Android 13 stable on a current slot later? Will any of these steps require a data wipe, will switching back and forth android version cause any harm to apps and settings? Using Pixel flash tool, heard about interesting stuff on A14 and want to check it out by myself.

Diofyz said:
Might be a noob question but can i flash Android 14 DP2 to an inactive slot and switch back to Android 13 stable on a current slot later? Will any of these steps require a data wipe, will switching back and forth android version cause any harm to apps and settings? Using Pixel flash tool, heard about interesting stuff on A14 and want to check it out by myself.
Click to expand...
Click to collapse
You CAN'T.

Definitely no...

Diofyz said:
Might be a noob question but can i flash Android 14 DP2 to an inactive slot and switch back to Android 13 stable on a current slot later? Will any of these steps require a data wipe, will switching back and forth android version cause any harm to apps and settings? Using Pixel flash tool, heard about interesting stuff on A14 and want to check it out by myself.
Click to expand...
Click to collapse
The quoted post below may answer the question better as to why you wouldn't be able to pull this off...
badabing2003 said:
Thanks @simplepinoi177 for finding relevant posts.
What I want to add is that, although the initial thought process was to use the alternate slot as a fallback.
Unfortunately that only works with older devices, and does not work for newer ones.
Even for older devices one needs to remove system_other.img from the update image to get it to work.
I have posted about the details, unfortunately I'm not very good at finding my own posts.
The gist of the matter is that, factory images contain system_other which is flashed to the alternate slot's system partition, they contain the optimized dex files which are copied to the active slot after booting to system to save time.
This effectively deems the alternate partition's system unusable.
Removing system_other before flashing theoretically would get around that issue, at a small performance hit at first while the dex files are optimized on first use, and that works on older devices.
I managed to setup Pixel XL with both slots bootable, and alternate between them at will, even one was rooted and the other stock.
Sadly this no longer works on newer devices due to AVB.
Click to expand...
Click to collapse

simplepinoi177 said:
The quoted post below may answer the question better as to why you wouldn't be able to pull this off...
Click to expand...
Click to collapse
And even if AVB did not prevent booting on both slots and the user took care of the system_other, it is highly likely that he would encounter random crashes or worse, mainly because of two different versions of OS using the same data partition, (remember there is only one data partition).
This is one of the reasons why a downgrade of OS version causes such issues.

Okay, i had thoughts that this would end bad, decided to ask just to make it clear. Thank you for your responses.