I have a two year old V50, that was bought new in the box. Has been working great except for the fast few weeks - post Android 12 update.
1. Phone lags like it has an app that is frozen.
2. Sluggish to open apps like the camera.
3. Safe mode does not work
4. AOD display get shifted on the screen.
These are all intermeittent problems and Verizon has offered to replace the phone under a warranty. Curious to hear thoughts if you think this really is a phone issue or something else. I did a factory reset after the Android 12 update, didn't seem to make a difference.
Thx.
why not just flash back A11 with LGup? before u do that though, could you do me a hugh favor? go into EDL mode and backup modem_a and modem_b partitions for me please. Reason being A12 Kdz doesn't exist, only way to get A12 on Verizon is OTA, as I have a 450vm but with EU 40b A12 (which works great BTW) but I don't have the lastest A12 modem for it...
LG rom has now Verizon A12 KDZ uploaded, so I don't need the dumps for the modem partitions anymore! thx anyway
u can still however use LGup to downgrade to A11 in PM as I've suggested.
dman535 said:
I have a two year old V50, that was bought new in the box. Has been working great except for the fast few weeks - post Android 12 update.
1. Phone lags like it has an app that is frozen.
2. Sluggish to open apps like the camera.
3. Safe mode does not work
4. AOD display get shifted on the screen.
These are all intermeittent problems and Verizon has offered to replace the phone under a warranty. Curious to hear thoughts if you think this really is a phone issue or something else. I did a factory reset after the Android 12 update, didn't seem to make a difference.
Thx.
Click to expand...
Click to collapse
Related
Gentlemens, I ask for your help because it's 30 hours that i'm fighting for this
Last morning I woke up and I looked at my Nord, and I saw it sluggishly slow, a bit like it has been in recent times and I was really tired of it, so I decided to clean the Nord by restoring everything in the most pristine way possible to try to make it more like it's Out-Of-The-Box, so i chose to downgrade with msm and luckily i had the wit to back up the persist.img
Making a summary, after I reset everything I reviewed how many bloatware there were in the Nord Indian version (I have that) and I wondered if you could put the global or eu rom on top of the ac2001
Reading on xda, reddit and oneplus I saw that many have done it and everything is semi all right, at most the 5g, the footprint or similar gave them a bit of problems, then I said to myself FINALLY I can get out of this Indian hell as an european (I have not a damn way to use amazon on the nord, because it does not accept that I am in Italy, so it refuses to connect, I breathed fire to make it work by removing the bloatware version, fighting with the router, adb, and the list goes on) and then I immediately threw myself into it
The global / eu version worked, but they crashdumped as soon as I updated them
I thought "Oh well" and I go back to edl and try to put the Indian back
Everything is fine with oos10, but as soon as I ******* go back to updating to oos11 it crashdumps, and i and go back to msm with edl to flash
I feel idiotic, oh well
fact that says something with sensor_process rc
device_restart_work_hdlr
and various other little things
Anyone have any idea how I could upgrade to oos11, global/eu (maybe god) or india?
Thank you in advance and forgive me for the papyrus: /
PS: relatively relevant detail, at more or less the second hour and a half at 12 o'clock in hell the pc while flashing went to bsod for unreleated issues (how lucky am i) and there it gave the first crashdump, but as soon as I reflashed in edl it it booted and then the continuous is over
I've flashed various combinations various versions and several times with edm today, so I don't really know what I can do anymore
crashdump is
err_qdi.c:1045:EF:sensor process:0x1:SNS_REG_INIT:0x9e:sns_registry
_sensor.c:94:SNS_RC_SUCCESS == rc
subsys_err_fatal_intr_handlersubsys-restart: Resetting the SoC - ad
sp crashed.
device_restart_work_hdlr
GiuseppeT03 said:
crashdump is
err_qdi.c:1045:EF:sensor process:0x1:SNS_REG_INIT:0x9e:sns_registry
_sensor.c:94:SNS_RC_SUCCESS == rc
subsys_err_fatal_intr_handlersubsys-restart: Resetting the SoC - ad
sp crashed.
device_restart_work_hdlr
Click to expand...
Click to collapse
The same issue for me bro. Did you solve it?
GiuseppeT03 said:
Gentlemens, I ask for your help because it's 30 hours that i'm fighting for this
Last morning I woke up and I looked at my Nord, and I saw it sluggishly slow, a bit like it has been in recent times and I was really tired of it, so I decided to clean the Nord by restoring everything in the most pristine way possible to try to make it more like it's Out-Of-The-Box, so i chose to downgrade with msm and luckily i had the wit to back up the persist.img
Making a summary, after I reset everything I reviewed how many bloatware there were in the Nord Indian version (I have that) and I wondered if you could put the global or eu rom on top of the ac2001
Reading on xda, reddit and oneplus I saw that many have done it and everything is semi all right, at most the 5g, the footprint or similar gave them a bit of problems, then I said to myself FINALLY I can get out of this Indian hell as an european (I have not a damn way to use amazon on the nord, because it does not accept that I am in Italy, so it refuses to connect, I breathed fire to make it work by removing the bloatware version, fighting with the router, adb, and the list goes on) and then I immediately threw myself into it
The global / eu version worked, but they crashdumped as soon as I updated them
I thought "Oh well" and I go back to edl and try to put the Indian back
Everything is fine with oos10, but as soon as I ******* go back to updating to oos11 it crashdumps, and i and go back to msm with edl to flash
I feel idiotic, oh well
fact that says something with sensor_process rc
device_restart_work_hdlr
and various other little things
Anyone have any idea how I could upgrade to oos11, global/eu (maybe god) or india?
Thank you in advance and forgive me for the papyrus: /
PS: relatively relevant detail, at more or less the second hour and a half at 12 o'clock in hell the pc while flashing went to bsod for unreleated issues (how lucky am i) and there it gave the first crashdump, but as soon as I reflashed in edl it it booted and then the continuous is over
I've flashed various combinations various versions and several times with edm today, so I don't really know what I can do anymore
Click to expand...
Click to collapse
Bro, please help me. How did you solve the issue?
ajaygrylls said:
Bro, please help me. How did you solve the issue?
Click to expand...
Click to collapse
Hello, I was wondering, do you have the solution to the problem ?
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.
As the title says OnePlus open beta 2 has been released. However on ob1 the Verizon users lost data/internet. My question is. Is anyone out here on an Na op9 using a Verizon sim and getting data. Last ob1 build was righteous and am excited for oxygen 13 they call it. But requires a data wipe if not, the rollback package that is. I hate starting over.
https://community.oneplus.com/thread?id=1184353608213725185 [OxygenOS 13 Open Beta 2 for the OnePlus 9/9 Pro]
I m using ob2 still data not working without magisk fix
Maybe you should back up and factory reset. I have everything working on Ob2. 5g ,Volte,almost all apps fine now. Only play store update broken still. I don't care about that. I love new OOs so much better than what they handed us for A12
mattie_49 said:
Maybe you should back up and factory reset. I have everything working on Ob2. 5g ,Volte,almost all apps fine now. Only play store update broken still. I don't care about that. I love new OOs so much better than what they handed us for A12
Click to expand...
Click to collapse
Yes my data is working too but at start i lost all signals but working good right now will keep testing if there is any issue with mobile data or signals then i will finalize
My attempt to install the OOS Cam bricked my phone.... so my question is Why did my phone got bricked exactly? I want to know what I did wrong since I really want to use the OOS Camera.So I was trying to get the original stock camera app to work on my device because the other ones looks horrible. I mean I have a kind of flagship device and the photo quality looks like my old cheap Huawei phone.
First I tried with an 3.x.x version of the app installed as an normal application. It works but the quality is still bad.
This is where I got that apk: https://forum.xda-developers.com/t/apk-oneplus-camera-for-any-a11-custom-rom.4350205/
On Reddit there is a post that said if you replace the Camera.apk on /system/app/Camera with the OnePlus Camera it should work.
The result? It worked and the quality seems better!....but some functions of the app like video or changing the size of the picture crash the app. Now the phone got really hot for some reason. No idea why but anyways I decided to go "creative" and I analyzed the official OxygenOS Rom(This is where I got the OOS Camera apk) to see what files where related to the OnePlus Camera app and then I pushed it through ADB to the respective directories of my phone.
These are the directories that I added with their specific files:/system/priv-app/OnePlusCameraService/
/system/system_ext/priv-app/OnePlusCamera/
/system/system-ext/priv-app/OnePlusGallery/
Then I rebooted the phone expecting to see the OnePlus Camera working in all it's glory!...The phone got stuck in the boot logo.
The phone stays on the boot logo for some seconds, then reboots again but this time in Recovery mode and says this:
Can't load Android System. Your data may be corrupt. If you continue to get this message, you might need to perform a factory data reset and erase all user data store in this device.
Click to expand...
Click to collapse
I did the factory data reset but it did not work.
Now this might seem relatively easy to fix by using adb right? Well it is the worst moment to have the usb port damaged so until I fix that I have this beautiful OnePlus Paperweight.
The last detail is I actually deleted a folder which contained the .xml config files of the OOS Cam I installed on the second try because I thought it might cause some issues with the last try. Those files were on /system/data/
The phone have the bootloader open because I use a custom ROM and this one is called "/e/" which is based on Lineage OS. I used the wireless ADB function since my usb port is damaged, it jsut works as a charge port.
Again my main motive to this post is to understand "what did I do wrong?". I don't get why Android thinks the data is corrupted. The files are the official ones and as far I know I didn't deleted any important files. I even want to try with a more modern version of the app since I use the 6.4.45. This is the one that came on my phone the moment I opened the box. I want to see if the quality of the pictures got better with a newer one.
If you read this massive dump of text...thank you!
hello people, I have a small Problem, i have a redmi Note 11 Pro 5g global bought over Amazon in Germany, before i got it i checked for sure that it will get a12 now in my news app they are talking about the Note 11 Pro 5g will get a12, the last Update was only November Security Patch.
and cuz' i read a Bit more about it there are custom Roms, but without twrp so If it gets updatet i need to Reset my Phone again.
sooo is there a way currently to get me a12 or a newer Version with OTA Updates?
since in the MIUI Downloader App there is a global MIUI 13 a12 Rom, with Recovery i read so much about those Things now i dont have a clue anymore i'll attach some Screenshots downbelow.
If there is a Option with only one time resetting the Phone i would do it, with a safe Guide thanks for Reading.
Fendonacci said:
hello people, I have a small Problem, i have a redmi Note 11 Pro 5g global bought over Amazon in Germany, before i got it i checked for sure that it will get a12 now in my news app they are talking about the Note 11 Pro 5g will get a12, the last Update was only November Security Patch.
and cuz' i read a Bit more about it there are custom Roms, but without twrp so If it gets updatet i need to Reset my Phone again.
sooo is there a way currently to get me a12 or a newer Version with OTA Updates?
since in the MIUI Downloader App there is a global MIUI 13 a12 Rom, with Recovery i read so much about those Things now i dont have a clue anymore i'll attach some Screenshots downbelow.
If there is a Option with only one time resetting the Phone i would do it, with a safe Guide thanks for Reading.
Click to expand...
Click to collapse
If you checked that the update is for your device, then you can take it, and flash it through your stock recovery.
By taking the other route, i.e. flashing a custom recovery, and so on, you always can return totally to stock, to take the update you want, if it is available. Also, when some TWRP appears (based on your words), then you can flash any stock ROM, that is prepared to be flashed through recovery.
SubwayChamp said:
If you checked that the update is for your device, then you can take it, and flash it through your stock recovery.
By taking the other route, i.e. flashing a custom recovery, and so on, you always can return totally to stock, to take the update you want, if it is available. Also, when some TWRP appears (based on your words), then you can flash any stock ROM, that is prepared to be flashed through recovery.
Click to expand...
Click to collapse
i would need a Guide dir this why is it so hard
Fendonacci said:
i would need a Guide dir this why is it so hard
Click to expand...
Click to collapse
Sorry for delay, I will show you with images.
Go to Settings/about phone:
Then open it, and tap on 13
Then tap 7 times on 13 Miui 13, to have more options
Then go to the three dots, up to the right, then you'll see the options to flash the package to your device, download the latest ROM package, and navigate to it, then your device will make the rest. Be sure to enable USB debugging previously, and set all the drivers correctly, to have more options, just in case.