• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][OFFICIAL][fajita][11] LineageOS 18.1

Search This thread

AluminumTank

Member
Jan 19, 2016
31
13
Moto G5 Plus
Google Pixel 3
Okay so I tried to edit the file in the built in TWRP editor but calls still go to RTT. Both of the carrier config files are both set to false. I don't know why this is happening and it is very strange.

As always, when messing around with stuff in root/recovery, make sure you're backed up.

One thing that I've had to do is completely remove the config file (or files in your case); make sure you save them on your computer or somewhere where you can put them back if needed. Also, make sure you just remove the carrierconfig files and nothing else in that directory.

After that, boot up into Android and make sure that all SIMs are working as expected (reception, data, text, etc.) and that they have the correct APN set in settings. Then try going back and modifying the files; Android should re-create them.
 

tobusygaming

New member
Nov 2, 2020
4
0
First, you need to make sure that you're phone has data decrypted. Currently the only ways I know how to do this and edit the file is with the phone booted up and root access, or using TWRP and putting your PIN/password in to decrypt. You can't acess this folder with LineageOS recovery because it doesn't decrypt data.

If you are using TWRP, did you get the prompt to decrypt your data when TWRP booted up?
I'm using the phone with root access and booted up, through MiXplorer.
 

AluminumTank

Member
Jan 19, 2016
31
13
Moto G5 Plus
Google Pixel 3

tobusygaming

New member
Nov 2, 2020
4
0
Just reread your original question. Are you looking in /data/user_de/0/? Your post makes it sound like you're looking only in /data/user_de/ (without the 0 directory)...
To clarify I'm currently in the /data/user_de/0/ directory and there is no com.android.phone, only com.google.android.gms and com.mixplorer.beta
Hmm. To be honest I've only done this in TWRP but assumed it would work with root access as well (I cannot test on my end since mine isn't rooted). Maybe try with TWRP?
Seems like I'm able to find and edit the file using solid explorer, but MiXplorer doesn't see the file, very strange. Thank you for working with me through it! :)
 

AluminumTank

Member
Jan 19, 2016
31
13
Moto G5 Plus
Google Pixel 3
"These instructions are NOT for carrier branded variants."
If I do this update on a Tmob 6T, I'll be effed?

I converted my tmob to international.... I am assuming that it won't be an issue? (Looking for confirmation 😁)

I'm in the same boat with a tmob converted to international. I ran the last OTA (10.3.11) without any issue, but haven't done this one yet. Assuming it should be fine, but I'm going to have some backups at the ready :/

Just wanted to confirm that I flashed the latest FW (10.3.12) on my Tmob today and booted up with no issues. Actually, it may have fixed a camera focus issue I was experiencing.
 

jhedfors

Senior Member
Oct 16, 2009
1,451
729
St Paul, AZ
Moto G6
OnePlus 6T

dwardo

Senior Member
Jan 15, 2011
488
357
France
  • Like
Reactions: thomasnsr

retry0001-coffee

Senior Member
Oct 21, 2019
56
11
I'm confused about something. If I'm already using LOS on my 6T (Tmo edition), and I can't update the firmware because it's not for my device (unless I convert to international? But I actually use Tmo in the USA), and then the latest LOS ROM will require it at some point? Am I screwed?
 

jabashque

Senior Member
Feb 17, 2017
140
75
I'm confused about something. If I'm already using LOS on my 6T (Tmo edition), and I can't update the firmware because it's not for my device (unless I convert to international? But I actually use Tmo in the USA), and then the latest LOS ROM will require it at some point? Am I screwed?
No, not entirely. The changes to the device tree and kernel still keep compatibility with Q vendor+fw, but you'll lose ANT+ and DASH charging support. However, once lineage-19.x comes about, support for Q vendor+fw will be dropped.

EDIT: that being said, I converted my fajita to intl from tmo long ago. Benefits like roaming onto U.S. Cellular are still present because that's based on an IMEI whitelist, I think,.so it doesn't matter what you run on your phone.
 
  • Like
Reactions: Eric_Lev

Eric_Lev

Senior Member
Jan 27, 2019
1,199
2,344
Angers
androidfilehost.com
No, not entirely. The changes to the device tree and kernel still keep compatibility with Q vendor+fw, but you'll lose ANT+ and DASH charging support. However, once lineage-19.x comes about, support for Q vendor+fw will be dropped.
Thank you!

Indeed, the dash charge support is lost with the latest build.

If I am not wrong:
1- From build 20210902, LOS 18.1 for fajita is compatible with firmwares 10 and 11.
2- It is recommended to update the firmware from 10 to 11 via the official procedure (see this commit, just merged) to keep ANT+ and dash charging support.

EDIT: Successfull update from fw 10 to fw 11 (see screenshot) .... fw 11 is here (if needed ... unzip and follow the official instructions ... use LOS recovery in fastbootD mode).

Thanks @LuK1337 !
 

Attachments

  • Screenshot_20210902-144135_Paramètres.png
    Screenshot_20210902-144135_Paramètres.png
    170.6 KB · Views: 56
Last edited:
  • Like
Reactions: thomasnsr

jabashque

Senior Member
Feb 17, 2017
140
75
As @Eric_Lev mentioned, update to the newest build first before updating to Android 11 vendor + fw. Without the kernel changes from the newest build, your phone will end up booting into crashdump mode on Android 11 fw, whether you try booting android or recovery.

I'd suppose if you already did this and your phone enters crashdump upon trying to boot android or recovery, you could still download and boot the latest lineage recovery using the wiki instructions?
 

Top Liked Posts

  • 2
    FYI ... firmware 11.1.1.1:

    About updating firmware on fajita:
    If needed, you can download the required files for updating your firmware here (unzip and follow the official instructions ... use LOS recovery in fastbootD mode)
    Thanx @Eric_Lev for the files and instructions. I've updated the firmware yesterday evening + installed the latest LOS+MicroG built and so far so good, everything works perfectly !
    And finaly, the color rendition is fine !!!!! Champagne !! Thanks @LuK1337 ;-)
  • 4
    FYI ... firmware 11.1.1.1:

    About updating firmware on fajita:
    If needed, you can download the required files for updating your firmware here (unzip and follow the official instructions ... use LOS recovery in fastbootD mode)
    3
    Hello,

    Thx for the files but when is it needed ?
    Optional if you have already updated your firmware from 10 to 11.
    See the screenshot of my previous post (i.e. vendor security patch level and baseband version).
    2
    FYI ... firmware 11.1.1.1:

    About updating firmware on fajita:
    If needed, you can download the required files for updating your firmware here (unzip and follow the official instructions ... use LOS recovery in fastbootD mode)
    Thanx @Eric_Lev for the files and instructions. I've updated the firmware yesterday evening + installed the latest LOS+MicroG built and so far so good, everything works perfectly !
    And finaly, the color rendition is fine !!!!! Champagne !! Thanks @LuK1337 ;-)
    2
    Dumb question : how do I get into fastbootD mode ?
    1- Boot up LineageOS recovery
    2- Go to “Advanced” -> “Enter fastboot”
    2
    Its still available on official website as well as ota is working..
    It is back now after being removed for several hours.
  • 12
    2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

    Instructions :
    Downloads :
    Reporting Bugs
    • DO NOT Report bugs if you're running a custom kernel or you installed Xposed
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    • If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
    Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.

    Code:
    What is your--
    LineageOS version:
    LineageOS Download url:
    Gapps version:
    
    Did you--
    wipe:
    restore with titanium backup:
    reboot after having the issue:
    
    Are you using--
    a task killer:
    a non-stock kernel:
    other modifications:
    
    Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
    9
    @LuK1337 Tahnks for all your hard work.
    Will our beloved 6T also get official 18.1 support?
    Eventually.
    5
    So I went and read through the RTT docs. One way to make sure RTT is disabled is to remove it from the carrier configuration, lol. So I went and did just that:

    UPDATE: So, I found a better way to do this that doesn't break everything else. You can go to /data/user_de/0/com.android.phone/files and edit the carrierconfig file there. It should be something like carrierconfig-com.android.carrierconfig-89148000001882338238-1839.xml. Note that the first number is the SIM ID, so it will be different for each phone. Change the following line:

    <boolean name="rtt_supported_bool" value="true"/>
    becomes
    <boolean name="rtt_supported_bool" value="false"/>

    And reboot! After that, RTT shouldn't be a bother anymore. This is a bit of a hack, but it works! XD
    5
    Why do the builds say nightly and not stable on the download page? I thought the ROM was "official" and stable now?
    lmao.
    4
    Thanks for your reply! I have a noob question, I can find several guides and instructions on how to install Magisk using TWRP recovery. However, I cannot seem to find any guides on how to install Magisk using Lineage OS recovery.

    Probably because most people on this device are using TWRP, myself included.

    You should be able to use the steps for installing Magisk from 8T Guide. (Should be the key word, as I'm using TWRP, this is untested on this device personally. It is how I would do it though if I needed to try it.)

    It's basically just

    In LOS recovery choose:

    - Apply update
    - Apply from ADB

    Now in the terminal on the PC:
    - sudo adb sideload Magisk-v22.1.zip. (remove sudo if you aren't using Linux)

    If you get a warning about them not being signed, choose flash anyways. We should be ready to reboot to the system now.

    The section there about passing safety net will work as well. Just remember the safety net test in Magisk doesn't currently work.