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.
Hi,
I've got a RN3, snapdragon version, 3GB of RAM. Unlocked bootloader. TWRP 3.0.2-2
I've been using CM for a while, android 6.0.1 and I've been trying now for a few days to move to Nougat.
I've tried different roms: NitrogenOS, lineage OS, resurrectionRemix.
I've also tried flashing different versions os miui firmware: 7.3.16, 7.3.23, 7.3.30
So, after all that, the result is always the same. The flashing seems successful, the phone boots but then I cannot go through the initial setup screen.
I choose the wifi network but when I try to enter the password, the screen resets every 5 seconds or so. I know it's resetting/reloading because the password I've typed so far goes away and I have to start again. It happens every few seconds and I cannot setup wifi properly.
I tried changing the password to aaaaaaaaaa to make it easy and quick to setup. Once I go through that, it stays for ever in the next screen "checking information" (or something like that). Again, it seems to be reloading this screen every few seconds.
is there something am I missing? Maybe I'm flashing firmware/rom in the wrong order?
I'm back with android 6.0.1 now and the phone works fine.
thanks in advance for your help.
Flash Kenzo Firmware , Rom & Nougat Gapps not MM , next reboot system
Sent from my Redmi Note 3 using Tapatalk
VaibhavKumar07 said:
Flash Kenzo Firmware , Rom & Nougat Gapps not MM , next reboot system
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
thanks @VaibhavKumar07
so, this is exactly what I've tried a few times.
what about wipes and all that stuff?
I don't mind doing a clean install and reinstalling/reconfiguring everything.
I've tried different things, but for example what is mentioned in the thread "CM13/14/14.1/AOSP N firmware for KENZO/KATE [VoLTE][12.1.2017]"
-Reboot to TWRP recovery
-Flash firmware
-Factory reset (data, cache and dalvik-cache)
-Flash your favorite Marshmallow or Nougat ROM
-Reboot your phone
is that still valid for the nightly builds from April 2017?
On Cm firmwares I was unable to get VoLTE working so recommend you to flash Miui beta firmware search in SD Rom or guide section you'll find em if not message me again .
Regarding procedure :
- First flash Twrp 3.1.1.0 from official site cuz that's latest
- Next go & wipe check everything except SD card & OTG
- Flash Firmware
- Flash Rom
- Flash Gapps Arm *64 Android N from Open apps
- Flash Any Add-ons if required like kernel or Sound enhancement mods ( optional )
- Clean cache/dalvik cache
- Reboot
Mention the Rom you're flashing!
Sent from my Redmi Note 3 using Tapatalk
So, I did all that several times, except for flashing the latest twrp version. I'm on 3.0.2-2 because it flashes ok but when rebooting it's back to 3.0.2-2. I'm doing this from fastboot. I'm not only loading, but flushing. It seems to be ok but then it's gone after reboot.
Anyway, I've tried this procedure with 3 different roms:
ResurrectionRemix
LineageOS
Nitrogen OS
flashing latest versions for each rom.
Could the twrp not updating properly have something to do with this issue? does the latest version fix some flashing issues with Nougat?
the thing is that if flashed and boots, but it doesn't run properly as mentioned.
I will try to get latest twrp version working and report back if that makes any difference.
VaibhavKumar07 said:
On Cm firmwares I was unable to get VoLTE working so recommend you to flash Miui beta firmware search in SD Rom or guide section you'll find em if not message me again .
Regarding procedure :
- First flash Twrp 3.1.1.0 from official site cuz that's latest
- Next go & wipe check everything except SD card & OTG
- Flash Firmware
- Flash Rom
- Flash Gapps Arm *64 Android N from Open apps
- Flash Any Add-ons if required like kernel or Sound enhancement mods ( optional )
- Clean cache/dalvik cache
- Reboot
Mention the Rom you're flashing!
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
so, still fighting with this.
i managed to upgrade to twrp 3.1.0-1, all good.
however, i still have the same problem with the initial screen, it keeps reloading every few seconds and can't finish the setup or even skip it.
i've tried different versions of firmware. I've also tried flashing the latest miui rom (dev and global) and then a custom rom.
i've tried different builds (different dates) of the following roms:
nitrogenOS
lineageOS
aospextended
mokee
resurrectionremix
exact same behaviour with all these roms.
what am I doing wrong? i'm on marshmallow and everything works fine, but stuck moving to nougat. do I have to flash something not mentioned already to move from custom MM to custom Nougat?
txutxe said:
so, still fighting with this.
i managed to upgrade to twrp 3.1.0-1, all good.
however, i still have the same problem with the initial screen, it keeps reloading every few seconds and can't finish the setup or even skip it.
i've tried different versions of firmware. I've also tried flashing the latest miui rom (dev and global) and then a custom rom.
i've tried different builds (different dates) of the following roms:
nitrogenOS
lineageOS
aospextended
mokee
resurrectionremix
exact same behaviour with all these roms.
what am I doing wrong? i'm on marshmallow and everything works fine, but stuck moving to nougat. do I have to flash something not mentioned already to move from custom MM to custom Nougat?
Click to expand...
Click to collapse
Try this once (Clean) :
Flash Nitrogen
Reboot
Flash gapps and firmware.
Hope it may work for you.
So I just did a perfectly good install of Lineage 14.1(the latest vs985 nightly from the lineage website) and GApps but it doesn't seem to detect my SIM? I tested the SIM on a friend's phone and it works perfectly fine. I attempted to clean the contacts for both the card and reader. It was tough because of the G3's metal cover SIM card reader design but I did the best I could nonetheless. What gives? The SIM worked before on the stock rom. Just to be clear I have a gsm unlocked LG G3 VS985.
--update--
Just flashed stock vs985 rom and the sim card works on there, which means its not a physical issue
--update2--
SIM works on old resurrection remix roms, but not the recent nougat one, is this a nougat issue??
maybe you could change to other baseband (exp: 30b..)
I've heard you can try this.
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 bootstacks
6. Flash 35b modem
7. Wipe cache /davilk then reboot and it should fix it.
Nougat roms seem to have this problem. I followed these steps and my Sim is now recognized.
Kickin' it on my vs985
Please see this thread too, maybe useful : LINK
Just installed Slimrom d2att 6.0.1 build 2.1 on Samsung S3 SGHI747 with ARM 6.0 Nano from Open Gapps.
Previous to flashing Rom above I had Slim 4.4.4 build 7.0 Official 5979. Recently had a new sim card installed at a local AT&T store and phone was working fine before flashing Rom. I followed procedures from Slimrom "coming from another ROM or Android version Clean Flash but did a factory reset, wipe cache, and then using TWRP wiped dalvik, cache, system and data, then flashed ROM and Gapps.
Problem: "No SIM card" message. Would factory reset mess up the IMEI? Does this sound like a problem with IMEI?
Pointers and possible fixes are appreciated.
Ended up going back to Slimrom 4.4.4 where Sim Card is identified and Cellular Networks are available. Not sure the new Slimroms 6.0's work on Samsung S3 i747 unless you manually configure.