after android 12 update screen keeps flashing - OnePlus 7 Pro Questions & Answers

Hi, I'm hoping that someone can help me.
after installing oos12 on my oneplus 7 pro my screen started to randomly flash.
i cant find anyone else that has this issue anywhere else on google.
Attached video's are from the CrDroid rom but the same thing happens when I was with the OTA oos12update
so far I tried to:
oos12 firmware via the crDroid page here on xda.
when I download the OTA update from oneplus themself (after the msm reflash) the blinking returns.
oos12 and oos13 rom from crDroid (including their recovery firmware)
evolution Rom (including their recovery firmware)
back to oos11 via the msm tool. this fixes the flashing issue, but i prefer not to stay on oos11 when I can run new roms).
does anyone have an idea what could fix it, I'm willing to try just about anything.

i think go back to OOS11 might help

Related

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

OOS 9.0.9 needed before updating to Android 10 (FYI)

I was having a bunch of issues updating my phone. I kept receiving a System Update Installation Failed error. I tried local using the zip downloaded directly from OnePlus support and it wouldn't work. It said that there was no update available when trying to use the update setting. Long story short...it just wasn't working. I then proceeded to use the MSM Tool to completely erase and reset the phone. STILL wouldn't work. I randomly came across someone saying you needed OxygenOS 9.0.9 before 10..tried it and it worked perfectly. Sigh.
I wanted to save someone else the hassle and document it here with the error I was receiving. Good luck! I got OOS 9.0.9 HERE if anyone needs it and I'm allowed to link.
@bam099
Thanks for sharing the link for 9.0.9
Out of interest which version were you upgrading from and which version MSM tool were you trying?
My OP6 is still on 9.0.8 as I've not had the inclination to go through the hassle of a full reset to restore to factory (BL is unlocked, TWRP is installed, was rooted but got rid of that due to constant hassle with banking apps detecting root and magisk hide not working for all my bank apps)
Now that 11 is released as stable I'm probs going to to the full return to factory stock and then upgrade straight to 11 (once the early adopters have found the first bugs and OP patch them ) but if 9.0.9 was needed to update to 10.x.x I guess the same will be needed for 11.
Surprisingly I took a little bit of notes so I could go back if I wanted to (and I wouldn't waste time searching for issues like this weird 9.0.9 thing I found). I was on 9.0.6 (Build Number A6003_22_190528).
I would imagine that 9.0.9 is going to be needed to get to 11 (I'm on 11 now but I went from 10 so I'm not positive about what is required).
If you download the stock ROM for 9.0.9 can't you upgrade it? I THINK TWRP can flash the update but I'm sure there's some kind of an issue with an unlocked BL and upgrading via the stock app.
I don't recall what version of the MSM tool I used...I was frustrated at that point and not taking notes haha. I keep remembering 4.0.4 so if that sounds right for MSM then that's what I used. But I think any of the ones you see on a guide would work. Good luck with it!

Question [HELP]Fat fingered OOS12 OTA update on rooted stock OOS11 and now I have no touch input.

Hello all,
I ****ed up, what I feel is big time?
I accidentally fat fingered the "install and restart" button for an OTA update for OOS12 on my rooted stock OOS11. From what I learned during my research phase of rooting my OP9, that's a big no no and can cause a lot of problems. When the phone booted back up I have no touch input at all. I have a mouse plugged into my phone and can use the phone that way and I am currently backing up as much as I can in the event I have to wipe my phone.
My question is, can I just dirty flash the previous OOS11 image I was running to go back to before the OOS12 OTA got applied? Just wanted to get the general consensus before I ruin my **** further.
I'm running stock recovery, stock OOS11.2.4.4 with Magisk, MagiskHide and not much else.
Much appreciated!
To my what i know you have to downgrade from 12 to 11 ect. I managed to get to global.
I messed up, and updated mine to 12. and from what i learned. my touch screen did not work due to the fact my update was for a global 9 pro, Not my oneplus 9-tmobile version. In the end I had to use the india msm tool to get back to working
warglock said:
Hello all,
I ****ed up, what I feel is big time?
I accidentally fat fingered the "install and restart" button for an OTA update for OOS12 on my rooted stock OOS11. From what I learned during my research phase of rooting my OP9, that's a big no no and can cause a lot of problems. When the phone booted back up I have no touch input at all. I have a mouse plugged into my phone and can use the phone that way and I am currently backing up as much as I can in the event I have to wipe my phone.
My question is, can I just dirty flash the previous OOS11 image I was running to go back to before the OOS12 OTA got applied? Just wanted to get the general consensus before I ruin my **** further.
I'm running stock recovery, stock OOS11.2.4.4 with Magisk, MagiskHide and not much else.
Much appreciated!
Click to expand...
Click to collapse
I would def recommend just MSM back to stock 11.2.4.4, I was in your same situation before and I always had the touchscreen issues if I was rooted when I upgraded to OOS12. I think I tried flashing back to 11 and just ended up soft bricking my device and having to MSM anyway. Also like the commenter said above I had to use the Indian MSM but Ive been able to use the Global MSM now with no issues so if thats what your're on Id recommend trying that one first and only using the Indian MSM if that one gives you errors.
So I'm running into this same problem and absolutely can not upgrade to OOS12. Each time, by display will not respond to touch. I went back to 11 via MSM (HAD TO USE OP9 Pro INDIA) because OP screwed something up with these phones.
I have tried multiple ways, went back to OOS 11, installed latest OOS 11 without root. Locked bootloader, Installed latest OOS 11 twice via system update to make sure everything was clean. Installed OOS 12 update and same problem.
Same problem here.....
I have installed the msm india and then the official android 11 for OP 9. After that the OP9 runs on Android 11. After that i have closed the bootloader and try the msm with the eu rom and i gets the "device not match image" error. Maybe i have the new rom for op9 installed and the productnumber is still on op9p ? Now i am going back to a custom rom. is there an option to get the fully working camera on a custom rom?
DerBaLu841 said:
Same problem here.....
I have installed the msm india and then the official android 11 for OP 9. After that the OP9 runs on Android 11. After that i have closed the bootloader and try the msm with the eu rom and i gets the "device not match image" error. Maybe i have the new rom for op9 installed and the productnumber is still on op9p ? Now i am going back to a custom rom. is there an option to get the fully working camera on a custom rom?
Click to expand...
Click to collapse
To get back to the correct ROM, boot to TWRP and flash the signed full zip to each slot.

Reverted from COS12 fingerprint/ face unlock bug

Recently reverted from ColorOs12 build to original Oxygenos 10. Had the auto rotate bug, fixed it. Now fingerprint, face unlock, and ambient gestures are broken. Anyone have suggestions on getting back to fully stock? Already tried MSM tool with no luck.
Edited. The file and advice I was giving was a last resort before sending back to OnePlus. Follow advice below and if you need persist.img as a last resort I can give you the link later.
Never use someone else's persist file. I went back to oxygenOS 9 by MSM tool then upgraded via ota to 11 then i download my persist file by MSM tool and edit it in Hex-master. You have tutorial on techibee channel on YT.
After that rotation works good but i dont have fingerprint too. I download this version of oxygen os11 what i actualy have by oxygen updater and flash it by localupdate in settings after that all works like before flash colorOS 12

After using msm-tools I can no longer install custom roms. Qualcomm CrashDump occurs after every install.

I recently installed lineageOS 18.1 on my Oneplus 8 (t-mobile) and everything worked just fine. Only problem I had was a slightly reduced signal strength and noticed I was often roaming with LOS while at work so I ended up using msm-tools to go back to stock and check a few things with the stock firmware near my work and noticed I was just always roaming out there so lineage was working just fine after all (OOS just didn't have the R above my signal like LOS). But when I tried reinstalling any other custom rom it now fails to write the modem or something. I get no errors until it boots up lineage and then suddenly CrashDumps after a minute or so. I have no sim detection or wifi. The msm tool will always bring me back to a fully functional stock image that works just fine but I cant get any custom rom working now. Has anybody else seen this issue before? I get no error reports other than modem failed to load on CrashDump. Followed the same instructions on lineageOS site and ran same exact files as before. I have tried running older versions of msm tools and still the same result. Same with crDroid. I tried installing through both TWRP and LineageRecovery.
Ok I think I figured it out. In case anyone else stumbles on this issue.. using the manual firmware upgrade on lineage site.. https://wiki.lineageos.org/devices/instantnoodle/fw_update fixed the problem. Just need to extract a payload from an official update from T-Mobile and flash every driver again.

Categories

Resources