Hello,
i installed the unofficial CM12.1 for the N7100 device from here (cm-12.1-20150530-UNOFFICIAL-n7100.zip):
http://forum.xda-developers.com/galaxy-note-2/orig-development/cyanogenmod-12-alpha-1-n7100-t2949644
two months ago.
Everything works fine until i decided to update the system because OTA was recognizing a new update...worst idea
After the update my sim card was not recognized anymore. After i wiped cache and dalvik via TWRP 2.8.7.0 and installed the cm-12.1 version from scratch the problem still exists. If i try to get my IMEI-number via the dialer (*#06#) the dialer software just crashes.
I installed gapps from here: https://github.com/cgapps/vendor_google/tree/builds/arm (gapps-5.1-arm-2015-07-17-13-29.zip)
Any ideas how i could get my sim card to work again?
SW_Tech said:
Hello,
i installed the unofficial CM12.1 for the N7100 device from here (cm-12.1-20150530-UNOFFICIAL-n7100.zip):
http://forum.xda-developers.com/galaxy-note-2/orig-development/cyanogenmod-12-alpha-1-n7100-t2949644
two months ago.
Everything works fine until i decided to update the system because OTA was recognizing a new update...worst idea
After the update my sim card was not recognized anymore. After i wiped cache and dalvik via TWRP 2.8.7.0 and installed the cm-12.1 version from scratch the problem still exists. If i try to get my IMEI-number via the dialer (*#06#) the dialer software just crashes.
I installed gapps from here: https://github.com/cgapps/vendor_google/tree/builds/arm (gapps-5.1-arm-2015-07-17-13-29.zip)
Any ideas how i could get my sim card to work again?
Click to expand...
Click to collapse
Have you tried asking in your specific device help forum?
http://forum.xda-developers.com/galaxy-note-2/help
You might have better results asking the experts for your device.
Hi! I flashed the OxygenOS 3.1.0 (Marshmallow) Community Build in my OnePlus X (link), everything okay but my SIM card slots have stoped working. I've tried the following:
Factory reset
Wipe cache
Flash OOS 2 stock
Reflash OOS3
Remove the SIM
Change SIM from slots
Try another WORKING SIM (still not detected)
Reboot tons of times between any steps
Went back to a (working) TWPR backup I had of OOS2
Flash XOSP
Flash CM13
But still no luck...
Can't get a way to fix this and it is obviously a software problem as this never happened before the OOS 3 install.
Any ideas?
Dial *#06# and confirm if it displays Valid IMEI number.
This is just stock LineageOS for the vs985 with no modifications (except baked in root in one edition) built daily from their source code. It's not terribly useful to anyone but people who want to be on the bleeding edge of development for whatever reason (like me), but I figured I'd share. I'll be doing these daily builds for the foreseeable future as long as I own the device or don't change OSes personally.
To install, do one of the following:
If you want to start fresh (or are coming from a non-Lineage based rom):
1.) In TWRP, wipe system, cache, dalvik, and data. Install the standard build (or the standard build with root). Do not install a migration build. Now Install open-gapps if desired. Reboot.
If you want to keep your data (and are coming from a Lineage based rom, official most likely)
1.) In TWRP, wipe system, cache, and dalvik. Install the migration build first, and then an open gapps build if desired. Reboot (it may take a bit). Once you are at your homescreen, reboot back to TWRP, and AGAIN wipe system, cache, and dalvik. Now flash a NORMAL build (with or without root) of your choosing. Again, flash open-gapps. Reboot. All done.
To upgrade, you simply wipe system/cache/dalvik and flash a non-migration build and appropriate gapps.
A warning about migration builds
Migration builds only need to be used once, but they appear to be a one way street. Once you are on my build, you can't "migration-build" your way back to official builds (or at least, I was not able to). You will need to data wipe to go back there. So, caveat emptor. Be sure this is what you want.
Find my dailies (along with build dates) here:
https://www.androidfilehost.com/?w=files&flid=164143
Open-gapps can be downloaded here: http://opengapps.org/
LineageOS Source can be found from the LineageOS github. It was compiled unmodified from this repo:
https://github.com/lineageos
Please, although these are stock code based, they are UNOFFICIAL BUILDS. Please do not bother the LineageOS project for support of these unless you can confirm the issue in an official build.
Thanks for looking! I'll most likely have a new build up tomorrow.
EDIT: Please make sure you are on the 35B bootstack prior to install:
Just flash this via TWRP if you are not sure: https://www.androidfilehost.com/?fid=24052804347843993
Has anyone installed this yet and can confirm compatibility?
I use them daily so they are compatible (if you can trust my word that is).
That said, they are not exactly bug free, but no LineageOS build bleeding edge ever can be.
The build server was thrashing it's disk space for a few days due to a build script failing to clean up after itself... this means a few days of builds were missed. This has been fixed, and we should have daily builds again.
Not sure if anyone uses this, but hey, just an update.
Hands down best ROM I've used on the G3. Everything works, very little FC if ever and I've even gotten Dolby Atmos to work with it. Never going back to anything else.
Glad to hear it. My build server had issues again yesterday, but it appears to be related to a bad stick of ram. I hope to have daily builds moving again tonight.
I wiped system, cache, dalvik and data, on my rooted, VS985 with TWRP 3.0.2-0.and got an "error 7: error installing zip file" when I tried to install the lineage-14.1-20170402-UNOFFICIAL_WROOT-vs985.zip. "Checking for baseband 35B. Error: It appears you are running an unsupported baseband. assert failed: g3.verify_baseband(35B:2.0.1C1.13.4-00005) =="1""
Android Version; 5.0.1
Baseband; VS985-MPSS.DI.2.0.1.c1.13.00073-M8974AAAANPZM-1
Kernel; 3.4.0-perf-g2d182d3
Build number; LRX21Y
Software Version; VS98524B
Any hints would help. I would really like to see this work on my phone.
dweezle said:
I wiped system, cache, dalvik and data, on my rooted, VS985 with TWRP 3.0.2-0.and got an "error 7: error installing zip file" when I tried to install the lineage-14.1-20170402-UNOFFICIAL_WROOT-vs985.zip. "Checking for baseband 35B. Error: It appears you are running an unsupported baseband. assert failed: g3.verify_baseband(35B:2.0.1C1.13.4-00005) =="1""
Android Version; 5.0.1
Baseband; VS985-MPSS.DI.2.0.1.c1.13.00073-M8974AAAANPZM-1
Kernel; 3.4.0-perf-g2d182d3
Build number; LRX21Y
Software Version; VS98524B
Any hints would help. I would really like to see this work on my phone.
Click to expand...
Click to collapse
You'll need to flash the bump-friendly 35B bootstack first. You can get it here:
https://www.androidfilehost.com/?fid=24052804347843993
Forgot to mention that, will edit it in.
R-T-B said:
You'll need to flash the bump-friendly 35B bootstack first. You can get it here:
https://www.androidfilehost.com/?fid=24052804347843993
Forgot to mention that, will edit it in.
Click to expand...
Click to collapse
Do you know if the "updater-script" fix would also work in this case?
If I do choose to flash the 35B bootstack, will I be able to get back to the backup of my current configuration simply by restoring it in TWRP or would I need to flash back the existing 24B then restore?
Lastly, how is your build different from the official LineageOS version for the VS985?
Thanks for your work with this. I think my VS985 still has lots of life in it, your ROM should give it even more.
Question please.
What's different about this "unofficial" stock Lineage from the "official" Lineage that is avail for VS985?
Why would one want this one vs that one?
It is just built more frequently from source to get more daily changes. Otherwise it is identical. It's mainly for those who like to track bleeding edge changes.
dweezle said:
Do you know if the "updater-script" fix would also work in this case?
If I do choose to flash the 35B bootstack, will I be able to get back to the backup of my current configuration simply by restoring it in TWRP or would I need to flash back the existing 24B then restore?
Lastly, how is your build different from the official LineageOS version for the VS985?
Thanks for your work with this. I think my VS985 still has lots of life in it, your ROM should give it even more.
Click to expand...
Click to collapse
A twrp restore should work regardless of the bootstack flash.
I just Flashed lineage-14.1-20170623-nightly-vs985-signed and open_gapps-arm-7.1-mini-20170707 it all went ok but it don't find my SIM card on boot, so how am I gonna get my sim card active. plz otherewise I would have to withdraw my choice of this Namely Custom ROM.
Please helpp!! I was using Lineage OS on my LG G3 VS985 it doesn't come with prebuilt root so I was rooting through SuperSU. I reboot my phone into twrp recovery and installed SuperSU.zip and then reboot my phone but now it is showing Secure Boot Error, boot certification failed. Please tell me how to fix this issue
and how is the camera quality of this rom as compared to stock and other aosp/cm based rom?
I flash the 35B bootstack before all and my phone goes wrong.. It is on power off, there's just 2 flicking red and blue led. When I go to the recovery mode, I can choose any proposition, my phone come back to this condition.. Can someone help me please ?^^ I was on Fulmics Rom
This rom hasn't been updated in some time as I no longer have the phone, so I am unsure how to help.
I rooted my phone then flashed TWRP installed Lineage OS but the sim is not working now. Imei is there, I tried RR, Lineage, Cloudy but still it's not working. The is currently on RR android 7.1.2 rooted and twrp is installed. Kindly help!!
What is your carrier? I recently switched to T-mobile (GSM) from Verizon (CDMA) on my vs985 with rr 5.8.3 35B bootstack. I should have full 2G, 3G, 4G, and LTE support, but I get a "no sim card" in quick settings:
https://frequencycheck.com/carrier-compatibility/B3jDu9/lg-g3-vs985-lte-a-lg-b2/t-mobile-united-states
Others have also confirmed support, but they might be on untouched stock firmware and roms.
My SIM isn't recognized, so I heard the following (which I'm about to try):
https://forum.xda-developers.com/verizon-lg-g3/development/xdabbeb-s-vs980-2-0-0-t3231279
1. Flash xdabbed 3.1.1
2. Do a full wipe
3. Flash lineage or whatever ROM you want
4. Flash gapps
5. Flash 35b bootstack (modem includes)
6. Wipe cache /davilk then reboot and it should fix it.
Now that I remember, I never flashed xdabbed 3.1.1 firmware because I assumed it was a custom ROM, but anyways I still have everything working without it, except for this recent switch of mine to T-mobile from Verizon.
So I figure out what I've done wrong.
I had to update the FW to move from 16.1 to 17.1
This is what I have done by mistake
1) format
2) factory reset
3) wipe everything
4) Flash the Poco fone ROM-GLOBAL-RECOVERY-V10 version coming from xiaomifirmwareupdater (Big Mistake cause I wanted the FIRWARE update only 2Gb FILE)
5) Flash LineageOS 17.1 OFFICIAL nightly 0829
6) Flash gapps pico
After that Wi-fi works but Mobile Network won't work anymore
So I try:
1) to change the SIM card slot
2) to select LTE only
3) to reset network configurations
4) to factory reset
nothing seems to work
Now what I'm trying to do is to
1) format
2) factory reset
3) wipe everything
4) Flash FW-GLOBAL-10 version coming from xiaomifirmwareupdater (AROUND 90Mb FILE)
5) Flash LineageOS 17.1 OFFICIAL nightly 0829
6) Flash gapps pico
But still....Mobile Network is not working at all....
Any hints or ideas on how to fix this issue?
More info about the issue!
So I made a few more tests.
If I have a SIM Card from another Carrier the Mobile Network starts to work
If I try this SIM Card which is not working on my Poco Fone on another phone the Mobile Network works on that second phone
If I try a SIM Card from the SAME Carrier as the first it does not work
So I assume there are some files to delete manually cause any kind of wipe, format or restore to factory/reset fails.
Anyone? ....
Did you solve the problem? I am facing same kind of problem after flashing Magisk.