Database Info

No Sim / Network Detected

Installed a new battery and screen, and since then sim card is not detected on Pixel. Sim works fine in other devices, just not being recognized by the pixel. IMEI number also does not show up in the system.
Any ideas on how I might have jacked something up installing the new battery and/or screen. Other than that phone seems to run fine. I've flashed a few different roms and stock back onto the device, with success, but still Sim is not recognized.
Desperate for any help with this.

MontoyaWA said:
Installed a new battery and screen, and since then sim card is not detected on Pixel. Sim works fine in other devices, just not being recognized by the pixel. IMEI number also does not show up in the system.
Any ideas on how I might have jacked something up installing the new battery and/or screen. Other than that phone seems to run fine. I've flashed a few different roms and stock back onto the device, with success, but still Sim is not recognized.
Desperate for any help with this.
Click to expand...
Click to collapse
I had this error updating to Android Pie. I found and posted an updated fix in the Pixel forums; if you are on the latest Pie, extract the Modem.img file and just reflash that file; fixed it for me. Good luck.

LBN1 said:
I had this error updating to Android Pie. I found and posted an updated fix in the Pixel forums; if you are on the latest Pie, extract the Modem.img file and just reflash that file; fixed it for me. Good luck.
Click to expand...
Click to collapse
I had this error too,what can I do?

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

Nord (India) stuck in crashdump

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 ?

Qualcomm Crashdump happening almost every day

Hi !
Some time ago, I switched to crDroid (because I don't like OOS12) and I started having some Crashdump (no error code) every day or two. If I force shutdown and restart, it works well for a time but crashes at some point.
At first I was thinking it was crDroid's fault so I went on DerpFest but the same is happening.
I've seen some posts where people's phone are bricked, which isn't my case.
Before installing the roms, I used MSMTools (MSMDownloaderTool-20210201-kebab) to reformat the phone and flash from the cleanest state possible. I have the KB2003.
Does anyone knows how I can fix it ? It happens really randomly (usually when the phone is locked, but it can happen also when using it) and I really don't want to come back to OOS...
Thanks a lot !

If this happens on all ROMs it may indicate a hardware problem e.g. with memory or smth else.
If on other Roms it works without issues. Flash stock OOS11 with another MSM (that you did before) and try installing CrDroid again.

Rootk1t said:
If this happens on all ROMs it may indicate a hardware problem e.g. with memory or smth else.
If on other Roms it works without issues. Flash stock OOS11 with another MSM (that you did before) and try installing CrDroid again.
Click to expand...
Click to collapse
I used the EU version, you mean trying something like International or just the EU from another website ?
Also, it seems to happen when I receive a notification from FB Messenger. Not on every notification but every time it happens, it seems to be this.

SamuelLeVentilateur said:
I used the EU version, you mean trying something like International or just the EU from another website ?
Click to expand...
Click to collapse
Yes, try International and India Roms.

Rootk1t said:
Yes, try International and India Roms.
Click to expand...
Click to collapse
So I tried the international one a week ago, it was fine for a few days but then the crashdumps came back.
I'll try getting back to OOS and see if it happens again, in that case I'll send it for repairs maybe.
If it doesn't crash, I'll be real sad that I'll need to use OOS...

Update after a month: OOS doesn't crash at all so maybe I'm doing something wrong when installing custom roms (don't know what as I tried 3 roms with differents methods)

OnePlus 8T installed OOS13 but failed to launch

The phone was up-to-date with OOS12 before and I downloaded the OOS13 upgrade within the system.
The installation seems to be working fine, but after the reboot, when doing the "new agreement" in the new OS, the next button is not working, and the phone goes into a reboot cycle.
Now it is just an endless cycle, which I can turn off but can not get off.
Can anyone please explain why this occurred, and is there any solution?
Another wired thing is that I have actually tried to update to OOS13 two times, the first time I updated manually, and the same problem occurred. But for some reason which I don't know, the phone just reversed itself back to the functioning OOS12 with all the data. I thought there are something wrong with the pack so the second time I just update through the system and the same issue occurred as described above.
How can I trigger that again? Just to at least make my phone back functional.

you can use the msm tool to restore the device to a working factory condition and than use oxygen updater to download the updates and install the update with system updater and use the local install option.
let me know how it goes!

JedidroidX said:
you can use the msm tool to restore the device to a working factory condition and than use oxygen updater to download the updates and install the update with system updater and use the local install option.
let me know how it goes!
Click to expand...
Click to collapse
nope, that still doesn't work, the phone is in that reboot cycle again.

T0ucHF1sh said:
nope, that still doesn't work, the phone is in that reboot cycle again.
Click to expand...
Click to collapse
You were able to boot the device after the MSM tool flash but if you update to OOS 13 the devices goes in bootloop again?

if msm tool was successful and still a boot issue than it sounds like a hardware issue. Perhaps look into to using the correct msm tool regarding you phones variant as that would be the correct firmware for the phone and hopefully would resolve the boot issue. For instance I have a tmobile variant so I would use the msm tool to restore that networks firmware. I don't know what else it could be!

JedidroidX said:
if msm tool was successful and still a boot issue than it sounds like a hardware issue. Perhaps look into to using the correct msm tool regarding you phones variant as that would be the correct firmware for the phone and hopefully would resolve the boot issue. For instance I have a tmobile variant so I would use the msm tool to restore that networks firmware. I don't know what else it could be!
Click to expand...
Click to collapse
do Chinese versions hardware have a differences with the global one and it kept me away from allowing to upgrade to oos13? Tbh I thought not so but it is probably the only explanation beside the hardware issue, maybe it is time to switch to a new phone....

T0ucHF1sh said:
do Chinese versions hardware have a differences with the global one and it kept me away from allowing to upgrade to oos13? Tbh I thought not so but it is probably the only explanation beside the hardware issue, maybe it is time to switch to a new phone....
Click to expand...
Click to collapse
It is possible that you need the correct msm tool, I speak from experience as when my fingerprint sensor and camera would not work due to heavy modification I did to the super image. After trying to restore with the global msm tool for my T-Mobile variant all was flashed correctly but still camera and fingerprint issue was not resolved. The only way was with the T-Mobile msm tool. The tool you need shouldn't be too hard to find. If its Chinese than I believe that would be HydrogenOS msm tool, after using that msm tool all should boot properly than you can convert it to OxygenOS and try to update again. If it messes up again at least you would know how to recover it to working condition.
Note: I believe the issue involves a different persist partition as I'm guessing for certain hardware to be slightly different. So the correct msm would be significant to a fully factory restored working firmware.

When I bought my 8T, it said it was a KB2000 (so, Chinese) but came with OOS 11 (KB05AA) installed, so I've used the KB05AA MSM Tool for OOS 11.0.7.9 (many times) and I've never had issues.

T0ucHF1sh said:
How can I trigger that again? Just to at least make my phone back functional.
Click to expand...
Click to collapse
It seems after unsuccesful update your phone rebooted to another slot with a working system prior to update.
You change slots using fastboot in bootloader using fastboot --set-active=other.