[OFFICIAL] LineageOS 20 for the Essential Phone

Search This thread
By:
Advanced…
L

lamjeff

Senior Member
Apr 2, 2008
65
6
Thanks for the custom rom ... But I am sorry that I discover the NFC is not workable... When I try to turn on the NFC in setting and it turn off itself after i left the setting screen... and the NFC is really important for me to using the Google Wallet... Can fix it in the next build... :)

Moreover, it look like the recovery (TWRP) is being overwriten by the rom ... Is it anyway can go back to the traditonal TWRP because i am not familar to using ADB sideload... And i try to flash the original TWRP thru fastboot and it cause an error as below

FAILED (remote: No such partition.)


If I really want go back to the orginal TWRP , any procedure can provide?

I really appreciate your work to make our handset still alive...

Cheers
 
Last edited:
  • Like
Reactions: yaostark
N

npjohnson

Recognized Developer
May 3, 2014
4,509
5,002
Orlando, FL
Verizon Samsung Galaxy S4
Nexus 7 (2013)
lamjeff said:
Thanks for the custom rom ... But I am sorry that I discover the NFC is not workable... When I try to turn on the NFC in setting and it turn off itself after i left the setting screen... and the NFC is really important for me to using the Google Wallet... Can fix it in the next build... :)

Moreover, it look like the recovery (TWRP) is being overwriten by the rom ... Is it anyway can go back to the traditonal TWRP because i am not familar to using ADB sideload... And i try to flash the original TWRP thru fastboot and it cause an error as below

FAILED (remote: No such partition.)


If I really want go back to the orginal TWRP , any procedure can provide?

I really appreciate your work to make our handset still alive...

Cheers
Click to expand...
Click to collapse
It sounds like you're not following the install instructions whatsoever.

We only support lineage recovery.

NFC works fine, I suspect you have older incompatible data or something - follow the wiki guide and all will work fine. I just tested an NFC tag - and it reads my wifi password just fine.
 
G

grognouf

New member
Jul 25, 2015
2
2
only positive comments here. I updated a few days ago from LOS 19.1.
Great rom, great experience. No issue for now. Thank you. I'm still amazed with this device for more than 5 years now.
 
  • Like
Reactions: swissueli and npjohnson
Z

Zargone

Senior Member
Sep 30, 2013
155
19
Scottsdale
Hello,
A little help please.
I have had Lineage 20 Android 13 installed with success since Feb of this year (I think). Last week I put a different SIM card in. Red Pocket Mobile (Verizon).
I cannot SEND SMS Text messages. I can receive them and I can send and receive RCS.

A little more history. Before I replaced the SIM card, the phone was working perfect. I originally installed the SIM card on my old number not knowing that the usage had expired several days before. I tried sending several text messages and ultimately discovered a notice that they could not be sent due to insufficient funds within the account. I paid for the next months phone service and now phone calls and data work fine. SMS Text messaging
is a different story.

I am not getting any responses so I guess that everyone thinks this is a provider issue. I reinstalled the old SIM card for my Out of US phone number and guess what. I have no SMS text messaging.
The newest update based on May 5 2023 added an additional reset option. "Reset App preferences". Perhaps it was there before and I did not notice it. In any event clicking on that brought up a notice that the Google Messages app is going to send a lot of SMS messages and Do I want to continue... I say yes but the sending is not successful.
With the prior OS version I received an Error 0 with a detailed explanation. Sort of... With this current version I only get the following: "Not sent, tap to try again"

I could really use a bit of help.


Thank you
 
Last edited:
zip.tyler.xda

zip.tyler.xda

New member
May 12, 2023
1
0
Zargone said:
Hello,
A little help please.
I have had Lineage 20 Android 13 installed with success since Feb of this year (I think). Last week I put a different SIM card in. Red Pocket Mobile (Verizon).
I cannot SEND SMS Text messages. I can receive them and I can send and receive RCS.

A little more history. Before I replaced the SIM card, the phone was working perfect. I originally installed the SIM card on my old number not knowing that the usage had expired several days before. I tried sending several text messages and ultimately discovered a notice that they could not be sent due to insufficient funds within the account. I paid for the next months phone service and now phone calls and data work fine. SMS Text messaging
is a different story.

I am not getting any responses so I guess that everyone thinks this is a provider issue. I reinstalled the old SIM card for my Out of US phone number and guess what. I have no SMS text messaging.
The newest update based on May 5 2023 added an additional reset option. "Reset App preferences". Perhaps it was there before and I did not notice it. In any event clicking on that brought up a notice that the Google Messages app is going to send a lot of SMS messages and Do I want to continue... I say yes but the sending is not successful.
With the prior OS version I received an Error 0 with a detailed explanation. Sort of... With this current version I only get the following: "Not sent, tap to try again"

I could really use a bit of help.


Thank you
Click to expand...
Click to collapse
I have the exact same problem. When updating from 19.1 (Nov 10, 2022 build) to 20.0 (April 16, 2023 build) I lost the ability to send SMS messages. I can still receive SMS, and send and receive MMS.

My phone service is through Ting (an MNVO) using the Verizon network. As a test I swapped to another Ting SIM that uses the T-Mobile towers, and I was able to send SMS messages perfectly. When I switched back to my Ting SIM on the Verizon towers I was once again unable to send SMS.

I am troubleshooting this with the Ting support staff, and imagine it will conclude with my switching to the T-Mobile towers permanently.

I also found that when upgrading from the April 16 build to the May 5 build I lost the lovely Google (Pixel?) camera app with built in QR code scanning. Now I'm a sad boy!

Despite these issues, I love using this to bring my PH-1 up to modern software! Thanks, devs!
 
W

work2077

New member
May 14, 2023
2
0
Hello. I have Divest os 19.1 firmware installed. I installed the firmware via fastboot. After installation, I flashed the kernel with magisk. After the release of Divest os 20, I decided to update also via fastboot, having previously reset to factory settings. During the firmware, an error occurred installing files (boot, system, and others). It feels like the file system is mounted read-only or the loader is locked. Also, it is not possible to return to the factory firmware, the phone is not restored. Please tell me how to solve my problem with the firmware.
 

Attachments

  • problem2.png
    problem2.png
    9.3 KB · Views: 17
  • problem.png
    problem.png
    58 KB · Views: 17
  • problem1.png
    problem1.png
    28.8 KB · Views: 17
N

npjohnson

Recognized Developer
May 3, 2014
4,509
5,002
Orlando, FL
Verizon Samsung Galaxy S4
Nexus 7 (2013)
Has nothing to do with lineageos, please go to their support venue.
work2077 said:
Hello. I have Divest os 19.1 firmware installed. I installed the firmware via fastboot. After installation, I flashed the kernel with magisk. After the release of Divest os 20, I decided to update also via fastboot, having previously reset to factory settings. During the firmware, an error occurred installing files (boot, system, and others). It feels like the file system is mounted read-only or the loader is locked. Also, it is not possible to return to the factory firmware, the phone is not restored. Please tell me how to solve my problem with the firmware.
Click to expand...
Click to collapse
 
You must log in or register to reply here.

Similar threads

invisiblek
[ROM][UNOFFICIAL] LineageOS 15.1 for the Essential PH-1 (mata)
Replies
2K
Views
265K
rophiroth
rophiroth
6
[STOCK][DUMPS][FIRMWARE] Essential stock firmware and rom dumps
Replies
1K
Views
244K
Z
Zraxonix
N
  • Locked
[CLOSED][OFFICIAL] LineageOS 18.1 for the Essential Phone
Replies
350
Views
59K
Oswald Boelcke
Oswald Boelcke
Dees_Troy
Official TWRP 3.2.3-0 for Essential PH-1
Replies
476
Views
102K
G
gk1984
xlxfoxxlx
AOSiP 9.0 [Official]
Replies
2K
Views
208K
C
chanh2018

Top Liked Posts

24 Hours 30 Days All time
  • 1
    N
    npjohnson
    Hey all, I am moving and therefore the unofficial update server/wiki will be down for a few days. Likely Wednesday, Friday at the worst.

    Don’t panic when links in the OP don’t work, and your Updater app says something like “Can’t connect to server”. It is planned outage.

    Thanks, see you on the other side!
    View
  • 1
    N
    npjohnson
    malerocks said:
    I have Magisk. Otherwise my banking app and Office email doesn't work because the Microsoft Intune app rats my phone out.
    Click to expand...
    Click to collapse
    I don't get that and I have no other reports of it so I'm betting magisk or some magisk module.
    View
    1
    M
    malerocks
    I was able to swipe it away and it only showed once after that. Tbh, I am not too worried at this point either.
    View
    1
    N
    npjohnson
    CyberCrux said:
    Hi npjohnson,

    I updated my Essential Phone from 19.1 Official Build to 20.0 Unofficial Build yesterday. Google Play Protect shows that "Device is not certified", as the same as 19.1 Official Build. I can install Netflix in 20.0 Unofficial Build, I cannot install Netflix in 19.1 Official Build previously. Does it mean that SafetyNet passed no matter the Play Protect shows "Device is not certified"?
    Click to expand...
    Click to collapse
    They are completely unrelated.
    View
    1
    C
    CyberCrux
    npjohnson said:
    They are completely unrelated.
    Click to expand...
    Click to collapse
    Many thanks to you and your excellent work.
    View
    1
    N
    npjohnson
    Hey all, I am moving and therefore the unofficial update server/wiki will be down for a few days. Likely Wednesday, Friday at the worst.

    Don’t panic when links in the OP don’t work, and your Updater app says something like “Can’t connect to server”. It is planned outage.

    Thanks, see you on the other side!
    View
  • 13
    N
    npjohnson
    lineage-os-logo.png

    Essential Phone

    Code: 
    - Your warranty is now void.
- You have been warned.
- Use at your own risk.

    Introduction:
    This is the Official Lineage OS 20 thread for the Essential Phone.

    Downloads:
    Please follow the install instructions in your device's Wiki page linked below exactly.
    • mata - Official builds
    • mata - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.
    If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.

    Known Bugs:
    • Find any? Report them according to this guide.
    Notes:
    • The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps - GApps are included in my unofficial builds
    • Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
    Kernel Source: https://github.com/LineageOS/android_kernel_essential_msm8998
    View
    9
    N
    npjohnson
    malerocks said:
    I know we are not supposed to ask, but sorry I can't resist. Any ETA of when will the official for Mata roll out?
    Click to expand...
    Click to collapse
    we're ready, just pending code-review from other maintainers.
    View
    5
    M
    malerocks
    mizzike32 said:
    I usually don't post much on XDA but I have to give thanks to Nolan, Tomtoms, and everyone else here posting about essential PH-1. Absolutely the best maintainers in my experience going back more than a decade. I have used oneplus, samsung, & google devices during that span; the majority of the time with those custom rom versions I have had less than stellar experiences with those devices. I've been stalking these threads for 2-3 years now. I've never been disappointed.

    It's truly amazing how this device is still alive and performing like its brand new.

    Now we have to pray that google doesn't force AV1 hardware encoding for android 14. Keep your fingers crossed.

    Peace.
    Click to expand...
    Click to collapse
    2nd that. I also like that they respond to queries. I have seen other threads where some maintainers don't bother or if they do, they will sometimes in a condescending tone.
    View
    5
    N
    npjohnson
    Official builds will roll Monday!
    View
    4
    N
    npjohnson
    dannysportbike said:
    same, no BT audio routing to wireless. on other phones a setting can be changed in dev options to fix it but it's greyed out on my ph1.
    Click to expand...
    Click to collapse
    Think I fixed it for the next build.
    View

New posts