Hi,
I am currently on LineageOS 14.1 on my OP3, I am on the March 9th build, and to do so I had to flash the Open Beta 12 Firmware + Modem. But now I am trying to go to either VertexOS or FreedomOS, but after flashing either rom, my phone is unable to connect to WiFi. It says that it is an Authentication Error and a message saying "Password may be incorrect" pops up on the bottom, even though it isnt. I have tried flashing 4.1.0 firmware before flashing VertexOS but that does not help either. But when i restore my TWRP backup to LineageOS, the wifi works normally. Is there anyway to fix this?
Related
Coming from stock rooted / unlocked Touchwiz KitKat
Cm12.1 installed just fine but when I rebooted and went to flash gapps I get a non-stop error saying "there's an internal problem with your device, and it may be unstable until you factory data reset."
So I factory reset the device and even installed CM 12.1 without gapps and it still gives me this error.
Factory reset again, try my recovery and I get an error mentoning UID's being messed up (I did this and it did not help http://forum.xda-developers.com/and...on-finally-t3151579/post61729442#post61729442 ) . So I factory reset again and flashed CM 12.1 without gapps and everything is fine.
Boot into recovery and flash gapps and boom the error again. Seems like the only way to get rid of the error (After many trials and errors) is to Restore recovery -> factory reset -> flash rom. The only problem is when I also flash gapps the error comes back.
Now here is the part where I can use YOUR help, in TWRP I keep saying red text that says
"E:error opening '/data/data/com/google.android.gms/files/images/games/de7f5650'
E:error: Not a directory"
on everything I do, from formating the system to flashing a rom. I think this is where my problem lies.
Other notes: No sd card,
when CM is working, I am getting no reception (Looks like a full but has ! next to it)
When CM is working, the messaging app does not even open and just instantly closes
OK I'll break into parts I see 1: gapps 2 signal 3:msg app.
1: GAPPS
cm 12.1 is android 5.1.* so you need to verify you have correct gapps. Use gapps for 5.1 hopefully that will fix problem. Factory reset, flash cm 12.1, flash gapps 5.1, wipe dev/cache, and reboot. Should be working fine after.
2: Signal is due to rom bugs but usually due to bad/wrong apn settings or bad efs/modem pretty much all the time from my experience. So I'll break that down from easiest to the latter and hopefully we'll fix it.
a: check you apn settings and see the attachments. I'm on lte tmo so if you aren't the Google apn setting for your carrier.
b: flash back up of moden/efs
3: msg app might be fixed since gapps was installed but if not only thing I can think of is clear data/cache for msg app.
Hope I could help
these days I'd use LineageOS for the Note 3/SM-N900T (I use nightlies and my note 3 used on wifi only) I can't test the normal 2g 3g 4g or lte cuz I dont have a compatible sim card (I have a nano sim in my j7 prime so it won't fit) it takes a bigger sim so yeah......I have gapps installed for my android version and they work fine for me
BsB5068 said:
N900TUVUCNB4
Click to expand...
Click to collapse
Rolatnor said:
these days I'd use LineageOS for the Note 3/SM-N900T (I use nightlies and my note 3 used on wifi only) I can't test the normal 2g 3g 4g or lte cuz I dont have a compatible sim card (I have a nano sim in my j7 prime so it won't fit) it takes a bigger sim so yeah......I have gapps installed for my android version and they work fine for me
Click to expand...
Click to collapse
lineageos 16.0 is what I've been running on it, i needed a newer os cuz stock 5.0 was the last official version, and pokemon go was dropping support for the note 3 with stock roms, now switching to LineageOS 17.1 on my note 3 i'll update whether gapps works so you know
LineageOS Downloads
download.lineageos.org
LineageOS 17.1 is android 10
btw I have sd cards in all my spare phones 8gb normally, so I am recommending a small sd card 4gb-16gb because it makes it easier to flash roms with twrp
google play works, gmail works, yt works, sound works, flashlight works, and camera works on LineageOS 17.1
note 3 sm-n900t
i used the nano gapps from opengapps
the newest file version of lineageos 17.1 on their site
Dirty flashed lineage-14.1-20170116-UNOFFICIAL-oneplus3 over cm-14.1-20161225-NIGHTLY-oneplus3 with recommended Unofficial TWRP 3.0.3-0 touch recovery for OnePlus 3. So far no problems.
I assume the UNOFFICIAL in the zip name is uncorrect for the thread is named OFFICIAL. [ROM][Official] LineageOS 14.1 for OnePlus 3
*edit* It's unofficial because the builds are dianlujitao's personal builds and not yet the official weeklies.
Is this build has SU/root enabled? I saw the latest changelog that SU is now disabled by default.
After dirty flashing another nightly build I lost root totally. Trying to flash SuperSU doesn't help (failed at "Extracting ramdisk")
sunng87 said:
Is this build has SU/root enabled? I saw the latest changelog that SU is now disabled by default.
After dirty flashing another nightly build I lost root totally. Trying to flash SuperSU doesn't help (failed at "Extracting ramdisk")
Click to expand...
Click to collapse
There's still the "Root access" option in Developer options and I can do "su -" in a terminal. So yes, root is still enabled but I never flashed SuperSU, I'm using the built in root manager.
Will any ROM, other than stock, ever offer VoWiFi and VoLTE? Stock has these features.
magic242 said:
There's still the "Root access" option in Developer options and I can do "su -" in a terminal. So yes, root is still enabled but I never flashed SuperSU, I'm using the built in root manager.
Click to expand...
Click to collapse
Maybe the change will comes to jianlujitao's build tomorrow (or never, because su can be enabled at build time)
Update: I updated my twrp to dianlujitao's 3.0.3 and I can successfully flash SuperSU. Now root is back! YAY!
No LTE after second boot
All,
I have a really weird problem with lineageOS lately. I clean flashed jianlujitao's (20170120) and flo017's (20170116) built, both show the same issue: after the first boot and doing the initial setup, the phone connects to LTE without problems. If I reboot directly after the initial setup, I don't touch any settings or do anything else, just reboot directly, the phone doesn't connect to LTE anymore. It only connects to H+.
Nothing else flashed but clean lineage, no gapps, no SuperSU or anything.
Tried to force LTE in the settings by choosing LTE only, but then it doesn't connect to cellular network at all. Deleted the APN, no change.
With Experience ROM by jamal2367 (OOS based) everything works fine!
What could be wrong here? I hope someone has an idea. I want to go back to lineage! :crying:
Cheers
I figured a workaround today. Changed Sim Card Slots to have the one for Data in Slot 1. Doesn't solve the root cause, but works now. :good:
I'm currently running my OP3 on Resurrection Remix 5.7.4 (MM 6.01), the phone has the latest version of TWRP and I've flashed other ROMs in the past without any issue
RR has proven to be quite unstable for me, the system UI keeps crashing, which renders the phone unusable until after a reboot so I wanted to flash Freedom OS as that worked quite well for me previously. When I tried to flash the ROM in TWRP the ROM seemed to flash successfully but when I rebooted, only the boot logo showed and then the screen went black and the phone refused to respond at all for about two hours, after that exactly the same thing happened. I managed to boot into recovery and tried flashing a different ROM but the result was the same every time, the only way to get the phone to work normally was to flash RR again/restore from a Nandroid backup, either way, the result is the same, I'm stuck on an unstable ROM and I don't know why, the last time I flashed these ROMs they worked fine, I followed all of the instructions for flashing said ROMs to the letter, I have the latest version of TWRP, etc, does anyone know what the problem could be?
Have you flashed the latest firmware? If not, I think this is why due to you being on a very old version (6.0.1) and as you are not flashing official OxygenOS you are not getting the newest firmware.
Download and flash the latest firmware here:
https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
Pick the right one for the ROM you are flashing (For Freedom OS installing firmware Open Beta 14 - Firmware + Modem under 7.1.1 should be good.)
Note: After you have flashed the firmware the next time you reboot the phone it will appear to not turn on for a few seconds, this is normal while it updates, don't worry
Let me know if you have any questions
Currently my OP3 has LineageOS 15.1 with installed firmware and modem from Oxygen Open Beta 32. Is it really safe to upgrade firmware to the latest open beta (for now it's version 37), as it is suggested at official LOS 15.1 for OP3 thread? Won't be there a problems with, for example, device encryption, which might be changed in firmware packages?
Always updating my MODEM and Firmware and never had problems.
I did try to flash latest LOS 15.1 today with latest OB37 and had an Encryption Unsuccessful error and could not boot, asking me to Format. I actually do not know what was causing the error as I did not try to troubleshoot, but it was the first time I was trying to flash any rom with the latest OB37. Don't know if that means anything.
I always flash OB31, it has better battery drain than latter ones.
I recently upgraded the Motorola One Action LOS4M to the latest 4-7-2022 build and, after the typical LineageOS loading screen (which lingered an abnormal amount of time), it shut off on its own and was sent to the LineageOS Recovery saying the ROM was "corrupt," and to do a factory reset to possibly fix it. After trying that a few times (including a TWRP advanced wipe), I get the same result of being sent back to the recovery with the same message installing the Official ROM from LOS4M official site. Anyone else having this problem with this build, and any of the recent Official LineageOS builds (not the 'for MicroG' builds) so we can tell where the issue is? The previous build (3-21-2022) still works fine so had to downgrade to get the phone to work.
You should try the new 19.1 build and see if it works.
From reading the wiki, you should use "MindTheGapps".
If you're not looking to do that, isn't a way to use MicroG "rootless" (without flashing it)?
This could be a bug, as none of the builds are stable (nightly).