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?
Related
I followed instructions to flash my one m using roms here, through trial and error i found a couple that worked but i ended up just going with cyanogenmod because it was familiar. when i booted it up i had an issue with my camera and micro sd, it said i didn't have storage/sd and the camera would fc, the gallery as well. the file manager seemed to access everything just fine though. i tried second party cameras/galleries to the same effect. so w/e my phone worked it didn't bug me too much at first...
then i noticed there were updates for the rom so i flashed the latest one and suddenly i needed to unlock my sim. that had been referenced in a thread here so based on that thread i entered 12345678 and wham it locked. i tried flashing a kitkat rom and the the stock blu one m rom here and neither helped. i took it to my metro store and they said i needed a new sim so i bought one and no dice. it won't even let me access the sim settings. it also doesn't show my imei anywhere in the phone info anymore.
i'm not really sure what to do at this point. i made a few backups at one point but i think i accidentally deleted them because i am super smart....
Hello,
I'll try to give all the details while keeping the long story short.
My moto C (xt1757) stopped working and I was forced to install again the stock rom. I never created a backup of the working phone before because I had no intention of flashing anything. But, when the problem occurred, the only thing I backed up, before starting, was the contents of /system/vendor/firmware.
Attempt 1. Custom ROM with TWRP.
Outcome: No flash was working using TWRP, all I got was a boot-loop.
Attempt 2. Custom ROM with SP Flash Tools.
Outcome: Again, boot-loops.
Attempt 3. Stock ROM with SP Flash Tools.
Outcome: Yet again, more boot-loops.
So, in the end, I decided to go the full monty with the phone and instead of just downloading the flash from the Stock ROM with SP Flash Tool, I used Format and Download instead. It worked :victory:, the phone was flashed and it booted.
I installed TWRP and rooted the phone again. All was happiness .
Until I noticed I was getting no signal from one SIM card :crying:. So I restored the backed up firmware (which was just the same thing from the stock ROM). Then I realized nvram stuff was deleted. At that point I didn't even knew what it was. So I did some research and was capable of creating the IMEI file MP0B_001 using two different tools, one was imei.386 from luckasfb's Fly_IQ255_Firmware_Build (here) and the other was the app GhostPhone (here).
I then noticed two more files in the same directory (/nvdata/md/NVRAM/NVD_IMEI/). These are...
MT00A001
MT00B001
at the beginning I just ignored them, however IMEI (IMEIs, actually, my phone is dual SIM) never changed from 000000000000000 to anything.
So at some point I decided to get rid of them, so I backed them up and delete them. Then voilà!, IMEI was being read correctly by Ghost Phone. However, android's IMEI information passed from 000000000000000 to empty. Also IMEI SV passed from 04 to empty.
So I tried to first set MP0B_001 and then upload MT00A001 and MT00B001. By doing that IMEI was again 000000000000000 and IMEI SV returned to 04.
Both files are identical, except for the file name, and both are binary. Nonetheless, some text is readble
Code:
LR9.W1444.MD.LWTG.MP WT6737M_65_Nn LWG_DSDS_COTSX
I suspect these two files act as a protection measure which prevents people from changing the IMEI. However, to the best of my knowledge, nobody has posted anything about them on the Net.
When I don't use those files, IMEI turns to "empty" according to android, even when Ghost Phone can read it properly (probably because it is just designed to decode MP0B_001) and WiFi MAC Address gets deleted (set as 00:00:00:00:00:00) every time the phone boots (/nvdata/APCFG/APRDEB/WIFI is rewritten by something). On the other hand, when I do use them, WiFi's MAC Address is OK but now IMEI becomes 000000000000000.
So I am kind of stuck here.
Any help will be appreciated.
I am a linux user, so I would thank you more if you don't rely on Windows apps; but I am open to suggestions.
My best regards.
This solved the issue for me. In a way, though.
Solution link
What is it? Well it is a working nvdata/nvram image that can be flashed using SP Flash Tools.
The important information here is the memory address where to flash nvdata.bin into my device (Moto C xt1557):
Code:
NVDATA=0x6b80000
The solution is posted for XT1756, but worked with my model too.
After flashing, both SIM cards were detected and WIFI MAC address was fixed. It was no longer 00:08:22:XX:XX:XX, but d0:04:01:XX:XX:XX. (Which is a valid vendor for the device: Motorola Mobility LLC, a Lenovo Company)
IMEI is obviously not my IMEI, but phone is working. So I will eventually find a way to change it.
After flashing I lost root, but TWRP image was intact, so I recovered ir fast.
Hope this helps somebody or myself in the future.
Sorry if the question sounds weird, it's probably because I don't fully understand this. I know that the OnePlus 6 has two software slots, an A slot and a B slot, and I also have a vague idea about what those slots are doing during an update.
Looking around, I found a thread that recommends flashing software on both slots, saying that it could fix some issues. I'm currently on Oreo, and I'm planning to get back to 9.0.4., but I remember that during 9.0.2. I think, when I was upgrading from Oreo again, I locally installed the same update file twice. I installed it once, everything went well, I went back to the local upgrade menu after the restart, and installed it again. And the phone seemed to be faster for some reason, that's what I'm trying to achieve again.
The thread that I found mentioned how to flash the software on both slots while on TWRP, would locally installing it twice achieve the same effect? Or is there something else that I can do?
Thank you very much in advance
TheMadKing said:
Sorry if the question sounds weird, it's probably because I don't fully understand this. I know that the OnePlus 6 has two software slots, an A slot and a B slot, and I also have a vague idea about what those slots are doing during an update.
Looking around, I found a thread that recommends flashing software on both slots, saying that it could fix some issues. I'm currently on Oreo, and I'm planning to get back to 9.0.4., but I remember that during 9.0.2. I think, when I was upgrading from Oreo again, I locally installed the same update file twice. I installed it once, everything went well, I went back to the local upgrade menu after the restart, and installed it again. And the phone seemed to be faster for some reason, that's what I'm trying to achieve again.
The thread that I found mentioned how to flash the software on both slots while on TWRP, would locally installing it twice achieve the same effect? Or is there something else that I can do?
Thank you very much in advance
Click to expand...
Click to collapse
Yupp. Same effect ??
whizeguy said:
Yupp. Same effect ??
Click to expand...
Click to collapse
Thank you!
Hi and thanks in advance for any help anyone can provide, I think my phone is dead :crying:
Anyway, story time...
I woke up to the door knocking and the postman was there with a package I had to sign for. My heart jumped as I knew it was my new OP6 from ebay (refurbed and from a highly regarded refurbed phone seller).
I inserted my SIM and the symbol for signal came on so the sim slot was working. I then connected to my wifi so the wifi is working. I like to customize my phones so I immediately come to XDA to find a ROM I'd like to install and to find the instructions for unlocking the bootloader, installing TWRP and Majisk. I looked and settled on AOSiP seeing that the required OOS firmware is 10.3.0 I upgrade through the system update feature.
Having updated I go on to unlock the bootloader, install TWRP and magisk. Upon unlocking the bootloader when the system rebooted it stopped reading sim cards and picking up wifi signals. Using adb I installed TWRP (using the proper method of temporarily booting into the TWRP and the installing the ZIP. Like an idiot I didn't read the instructions properly and flashed the AOSiP zip which failed.
I thought the best thing to do was start over so I flashed the official recovery boot image using adb. I ended up only able to access the bootloader/fastboot. Every option apart from turn off just caused the phone to boot into the bootloader. I fixed this using the instructions on https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 using the 10.0-OnePlus6Oxygen_22_OTA_040_all_1910270546_42a63-FASTBOOT.zip and I can now access the system but the setup keeps stopping and it still won't pick up sim cards or wifi and keeps rebooting.
I have tried to restore to stock using the system update feature and manually downgrade but the phone reboots before the downgrade gets chance to finish. I think this is eveything I did although maybe I pressed something i shouldn't have in TWRP.
I've heard two different things about this issue one is that android 10 is not fully working yet and that's causing the reboots and connectivity issues but I have had an OP6 before (I had to sell it ) another thing I heard was it was a hardware issue and the motherboard needs replacing. Please help, if it is a software issue then I'm screwed, I relocked the bootloader but I'm sure the seller will be able to tell and not replace of refund the item. If it's a hardware issue I can at least get my money back. If anyone can help me fix this it would be much appreciated.
Hello
I was originally on the LineageOS ROM, and used the MSM tool to go back to stock firmware/rom. I updated all the way up to the newest A12 update... and tried to use the msm tool again to go back and now my phone will not recognize the sim card and freezes and crashed randomly every few minutes. I've tried clearing the cache and whatnot in the recovery menu and nothing helps.
Edit:
So I finally got this issue to stop. The MSM tool I was using was pretty outdated and something about it wasn't sitting right with the phone. I downloaded a more updated version of the MSM tool and the issue is fixed entirely I believe.
During this issue I was experiencing
-Random freezes and restarts
-Sim card not reading
-OEM Unlock being greyed out where it never has been before
If anyone is experiencing this issue feel free to reply on here or DM me and I can upload and post the exact MSM tool that I used to fix this issue.
duzzqqqq said:
Hello
I was originally on the LineageOS ROM, and used the MSM tool to go back to stock firmware/rom. I updated all the way up to the newest A12 update... and tried to use the msm tool again to go back and now my phone will not recognize the sim card and freezes and crashed randomly every few minutes. I've tried clearing the cache and whatnot in the recovery menu and nothing helps.
Edit:
So I finally got this issue to stop. The MSM tool I was using was pretty outdated and something about it wasn't sitting right with the phone. I downloaded a more updated version of the MSM tool and the issue is fixed entirely I believe.
During this issue I was experiencing
-Random freezes and restarts
-Sim card not reading
-OEM Unlock being greyed out where it never has been before
If anyone is experiencing this issue feel free to reply on here or DM me and I can upload and post the exact MSM tool that I used to fix this issue.
Click to expand...
Click to collapse
Would be great if you can post a link to the msmtool. I'm going through the same issue right now
gingerboy92 said:
Would be great if you can post a link to the msmtool. I'm going through the same issue right now
Click to expand...
Click to collapse
You still need it? I don't have a direct link to the specific one I have, could only upload the one I currently possess. And this is for the TMobile variant.. You could also try different USB ports, different cable, oem cable that came with the phone, etc.
duzzqqqq said:
You still need it? I don't have a direct link to the specific one I have, could only upload the one I currently possess. And this is for the TMobile variant.. You could also try different USB ports, different cable, oem cable that came with the phone, etc.
Click to expand...
Click to collapse
I tried extracting newer version from op9 file. Works great for a couple of days until the phone upgraded to android 12 by its own and the problem started again.
My global one plus 8 also randomly reboots (every ±5 minutes). The firmware with the MSM tool does not change the situation in any way, but only exacerbates (The phone stopped seeing imei and lost the function of calling) I need help
Westy089 said:
My global one plus 8 also randomly reboots (every ±5 minutes). The firmware with the MSM tool does not change the situation in any way, but only exacerbates (The phone stopped seeing imei and lost the function of calling) I need help
Click to expand...
Click to collapse
In the event that you cannot bring your device from the dead via the MSM Tool, you might be a candidate for a replacement device.
Can you send the link to MSM tool because i have the same problem. Thank you.
Moaz Adel said:
Can you send the link to MSM tool because i have the same problem. Thank you.
Click to expand...
Click to collapse
MSM Tool.