{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Moto g7
Code:
- Your warrenty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 17.1 thread for the Motorola Moto g7, codename river.
How to Install:
Please follow the instructions on our Official LineageOS Wiki page here.
If you don't follow these instructions, please don't expect support here. We also don't support 3rd party addons (Magisk/XPosed/Dolby/Viper/etc.), so please don't seek support if you use these.
Known Bugs:
None.
Notes:
Official Lineage OS builds for river ship with full Project Treble compatibility! Flash GSI's to your heart's content after flashing Lineage. Please don't report GSI bugs here, report them instead to the GSI's maker.
Technical details on our Treble implementation:
Treble is enabled with VNDK29, and VNDK runtime enforcement. VNDK runtime enforcement means that unlike most "ported treble" you'll see, ours is just as it would be from the OEM, and can run GSIs. without need for hacks or additional flashable zips. We relabeled /oem to /vendor (as /oem isn't wasn't used in custom ROMs anyway). To use a GSI, flash official Lineage, then flash your GSI, it's that simple! Flashing a factory image will likely write over /oem and remove the mock vendor image.
Download:
LineageOS Updater
npjohnson's Personal Updater -- These are experimental, likely to break/eat your cat/destroy your data, and include GApps -- you'll find no support for these.
XDA:DevDB Information
[OFFICIAL] [NIGHTLIES] LineageOS 17.1, ROM for the Moto G7
Contributors
npjohnson, erfanoabdi
Source Code: https://github.com/LineageOS
ROM OS Version: Android 10
ROM Firmware Required: Newest firmware available for your variant
Version Information
Status: Stable
Created 2020-04-01
Last Updated 2020-04-15
Awesome!
VoLTE working?
Edit 4/3: Like the unofficial releases, still no Wifi calling on Fi. Would be great if we could get that working.
Just an imporant FYI - ICYDK Community
https://www.androidpolice.com/2020/...-android-10-builds-will-probably-launch-soon/
At the time of this writing - there are some signing issues related to LineageOS 10 Roms (including river), so the link provided will take you to only version 16. Rest assured though, the team is working on it. The above link to android police, explained it all for me, hopefully for you as well. A screenshot is included in case the above link with the reference points disappear. Thank you for npjohnson for taking the time to support this. At last the river gets Android 10
LineageOS 17.1 works wonderfully however the Trebuchet Launcher does not seem to work as it crashes even upon first boot but any other launcher works perfectly.
The FM Radio does not work at all unfortunately, neither on LineageOS 16 nor 17.1, I hope that gets resolved soon.
Other than that, great work!
Very great to see this release. I have 2 questions:
- 1. Does this pass safetynet by just installing? I mean I don't want to install Magisk and Magisk hide
- 2. Does it work without any risks with the Februrary 2020 security update? I heard that if you are in that security update and then make a wrong move with formatting a partition there is no way to recover a brick / no blankflash available?
Thank you in advance!
Almost full Pixel Experience
No issues so far, running smooth and fast. I feel that this device is running faster than my Stock Pixel 3a XL. Magisk is working, so I'm using it as a daily driver from now on. Thanks a lot :good:
@npjohnson
This sounds nuts but this actually boots on the Moto G7 Play too. This tells me that 64bit builds can be ported to our device. The only thing that would need to be changed (I think) are touchscreen drivers, and gpio keys. I was able to boot into LOS recovery by changing river to channel in the default prop and flashing it. The screen is split and mostly unreadable but it is recognized by adb. Flashing the dtbo allows the boot logo to display properly with some flickering. Everything after that is still split however.
Given this info; Would you have any interest in trying to build for us too?
Also, would you have any idea how to resize a vendor partition? I think if I flash the vendor.img, it might fix the touchscreen. Right now twrp says it's bigger than my target device. (Which is a load of crap, I have 22gb free.)
Phone calls on Google Fi do not work when connected to T-Mobile, only Sprint
Is the upgrade procedure from 16.0 to 17.1 supposed to erase my data ?
Is there any specific procedure to install magisk?
So from what I've experienced so far, calling doesn't work when using Google Fi on T-Mobile and location also doesn't work either on any app. OTAs also fail via the LineageOS Updater and the FM Radio is broken too
So I and like other people that have been reporting on Reddit, my device powers down a few seconds it boots into Los 17.1 i can't be certain but I think it started powering off and rebooting into TWRP 3.3.1.2. This has been from a clear flash/install.
Formated/erased everything
Followed Los 17.1 instructions to install Os and Gapps, Magisk
Device Boots into L.o.s 17.1 Gapps updates then devices powers down and reboots back in twrp
The device now just reboots after booting into L.o.s 17.1
farscaper11 said:
So I and like other people that have been reporting on Reddit, my device powers down a few seconds it boots into Los 17.1 i can't be certain but I think it started powering off and rebooting into TWRP 3.3.1.2. This has been from a clear flash/install.
Formated/erased everything
Followed Los 17.1 instructions to install Os and Gapps, Magisk
Device Boots into L.o.s 17.1 Gapps updates then devices powers down and reboots back in twrp
The device now just reboots after booting into L.o.s 17.1
Click to expand...
Click to collapse
fastboot -w (formats data, internal SD so back them up before doing this)
AgentICS said:
So from what I've experienced so far, calling doesn't work when using Google Fi on T-Mobile and location also doesn't work either on any app. OTAs also fail via the LineageOS Updater and the FM Radio is broken too
Click to expand...
Click to collapse
I can also confirm the issues with the FM Radio and the OTA updates failing. Originally I thought it may be due flashing over 16.1, but both issues persist after a complete wipe.
Anyone have an idea what to do if LineageOS is preventing any sort of mobile data connection? I'm using a Fi phone that I've flashed the standard retail update on before to get the Android Update to Feb 1. I'm using A Sprint MNO called Tello that works fine on Stock, any ideas?
cybersecuritystudy said:
Anyone have an idea what to do if LineageOS is preventing any sort of mobile data connection? I'm using a Fi phone that I've flashed the standard retail update on before to get the Android Update to Feb 1. I'm using A Sprint MNO called Tello that works fine on Stock, any ideas?
Click to expand...
Click to collapse
Did you check for the correct apn settings?
jman315 said:
Did you check for the correct apn settings?
Click to expand...
Click to collapse
Thanks for the reply. I've researched that, and can't seem to quite find how to make a change in that. The standard procedures for doing anything with Access Point Names did not seem to show up in either Lineage 16.0 or 17.1. I found info on my carrier site (Tello), but have no idea how to change it since it doesn't show up as an option to change in the mobile network settings.
cybersecuritystudy said:
Thanks for the reply. I've researched that, and can't seem to quite find how to make a change in that. The standard procedures for doing anything with Access Point Names did not seem to show up in either Lineage 16.0 or 17.1. I found info on my carrier site (Tello), but have no idea how to change it since it doesn't show up as an option to change in the mobile network settings.
Click to expand...
Click to collapse
For me the APN settings can be found under...
Settings -> Network & Internet -> Mobile network -> Advanced -> Access Point Names
or
I can also find it by just searching for "access point names"
---------- Post added at 01:23 PM ---------- Previous post was at 01:20 PM ----------
The 4-12 nightly OTA was the first to apply successfully. One other thing I have noticed that does not work since coming from LOS 16 is night light.
AgentICS said:
Phone calls on Google Fi do not work when connected to T-Mobile, only Sprint
Click to expand...
Click to collapse
Likely the way you setup Gapps
Google Fi Requires some extra packages to function correctly
you can find my personal Gapps Fi Pico package here:
https://www.androidfilehost.com/?w=files&flid=306318
jman315 said:
For me the APN settings can be found under...
Settings -> Network & Internet -> Mobile network -> Advanced -> Access Point Names
or
I can also find it by just searching for "access point names"
---------- Post added at 01:23 PM ---------- Previous post was at 01:20 PM ----------
The 4-12 nightly OTA was the first to apply successfully. One other thing I have noticed that does not work since coming from LOS 16 is night light.
Click to expand...
Click to collapse
Thanks for the info. It's not in that location, all I have is Settings Version, Wi-Fi Calling, Carrier Video Calling, System Select, CDMA Subscription, and Carrier Settings.
The good news is, it looks like its working as of the 4-17 version I retried last night without needing to change anything. Thanks!
Also on a side note, I noticed there is no superuser download option for this version of LineageOS yet. Is this something that is coming down the line, or is there just a problem with doing this on the OS level?
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Wiki.
Important Info
To flash this rom you need TWRP 3.2.0-0 or newer. https://twrp.me/huawei/huaweinexus6p.html
Make sure you have the radio & bootloader img's installed from the stock oreo 8.1 OPM7.181205.001 Dec 2018 factory image.
They can be extracted from the factory image on google's site here. Or you can use the ones linked below that I already extracted:
radio & bootloader img's: https://androidfilehost.com/?w=files&flid=286833
Those img's can be flashed with fastboot command.
Note: There's an issue happening to some angler users on custom oreo roms. The first boot after flashing rom your sim card might not be detected. It's easy to fix. Just go to lockscreen security settings and change it to 'none' and then reboot. Then you can change it back to whatever you want. This only happens one time when you first flash oreo.
Download Links
rom: https://download.lineageos.org/angler
Note: LineageOS servers no longer make 15.1 builds for any devices. You can use my unofficial builds here. My older builds are here.
Note#2: if you want to switch from an official build to my unofficial builds, follow instructions here.
google apps (optional): https://wiki.lineageos.org/gapps.html (Use arm64 / 8.1)
root su addon (optional): https://download.lineageos.org/extras Note: Use arm64 15.1 zip. After installing the su addon, you can enable root in developer options.
Instructions
If updating from old unofficial to newer unofficial, follow the steps below:
1. if you don't already have them installed, flash the newest radio and bootloader img's linked above.
2. boot into twrp and flash the rom zip.
Reboot & enjoy.
NOTE: if you previously flashed gapps and/or the su addon, there's no need to flash them again. They will be automatically re-installed during rom zip installation.
NOTE2: if you want to switch from an official build to my unofficial builds, follow instructions here.
If coming from a different rom:
1. if you don't already have them installed, flash the newest radio & bootloader img's linked above. also make sure you have the newest twrp, linked above.
2. boot into twrp and wipe system & data & cache.
3. flash rom & gapps & su addon zips (gapps & su zips are optional).
Reboot & enjoy.
Weather Provider Addon (Optional)
For those that like the lineage cLock widget, here's the OpenWeather apk you need to get weather info.
https://download.lineageos.org/extras
Grab the one for version 16.0. It also works with 15.1.
Note: You'll need an api key from OpenWeather.
LineageOS Stats
https://stats.lineageos.org/
Credits
Many thanks to my fellow LineageOS team members and all the contributors out there in the community. :good:
LineageOS device maintainers:
sam3000, razorloves
Source Code:
Device tree: https://github.com/LineageOS/android_device_huawei_angler/tree/lineage-15.1
Kernel tree: https://github.com/LineageOS/android_kernel_huawei_angler/tree/lineage-15.1
Vendor tree: https://github.com/TheMuppets/proprietary_vendor_huawei/tree/lineage-15.1
Android version: 8.1.0 Oreo
Kernel version: Linux 3.10.73
Wooh! First!
Sent from my Nexus 6P using XDA Labs
Hey Razor. I used to be on your builds a couple of years ago in the old hammerhead and looking forward to flash your work again when 15.1 is out, this time on angler. Cheers! :fingers-crossed:
Any bugs? Is it suitable for daily driver? Just tired to wait for official build and want to flash as fast as possible. )
Thanks Razorl!!!!!
Error 7 -- make sure to flash the new twrp recovery if you face this issue!!
i42o said:
ERROR 7
Click to expand...
Click to collapse
Try reading the big bright red letters at the top, under "IMPORTANT INFO"
razorloves said:
Try reading the big bright red letters at the top, under "IMPORTANT INFO"
Click to expand...
Click to collapse
haha. Yeah my bad bro, my bad. got it tho, thanks!
Says no SIM card
Clean flash following instructions, TWRP 3.2, latest bootloader/radio/vendor, flashed vendor -> rom -> gapps. Otherwise no errors.
Any suggestions?
telefantastik said:
Says no SIM card
Click to expand...
Click to collapse
Forgot to mention in the first post. This has been happening on many custom ROMs.
An easy fix is to go to security settings and change screen lock to swipe or none, then reboot. That will remove the device protection that caused the no sim problem.
After the reboot, the problem is fixed and won't happen anymore. Then you can go back into security settings and change it back to whatever screen lock option you want.
razorloves said:
Forgot to mention in the first post. This has been happening on many custom ROMs.
An easy fix is to go to security settings and change screen lock to swipe or none, then reboot. That will remove the device protection that caused the no sim problem.
After the reboot, the problem is fixed and you can go back into security settings and change it back to whatever screen lock option you want.
Click to expand...
Click to collapse
It's weird though. I have unlock protection and got no issue when flashing this.
Can it also be related to your carrier or something?
ChemoNL said:
I have unlock protection and got no issue
Click to expand...
Click to collapse
Its not just caused by unlock protection. I posted details on the issue in my 14.1 thread about a month ago.
razorloves said:
Forgot to mention in the first post. This has been happening on many custom ROMs.
An easy fix is to go to security settings and change screen lock to swipe or none, then reboot. That will remove the device protection that caused the no sim problem.
After the reboot, the problem is fixed and won't happen anymore. Then you can go back into security settings and change it back to whatever screen lock option you want.
Click to expand...
Click to collapse
Awesome, it worked! Thanks
For those interested...
Another new version of twrp came out yesterday. 3.2.1-0
Here's the changelog for it https://twrp.me/site/update/2017/12/09/twrp-3.2.1-0-released.html
You can download it here: https://twrp.me/huawei/huaweinexus6p.html
Here's the changelog for 3.2.0-0 that came out last week, incase you missed it.
https://twrp.me/site/update/2017/12/01/twrp-3.2.0-0-released.html
Thank you for new thread and ROM.
:fingers-crossed::fingers-crossed::fingers-crossed:
Hi, looking to potentially begin using custom ROMs on my 6P to help combat some battery and performance issues I get. With future updates, do I have to keep manually flashing the radio, etc firmware or can I just OTA/DL zip of lineage and flash? Seems like a bit of a pain :/
domacikolaci said:
Hi, looking to potentially begin using custom ROMs on my 6P to help combat some battery and performance issues I get. With future updates, do I have to keep manually flashing the radio, etc firmware or can I just OTA/DL zip of lineage and flash? Seems like a bit of a pain :/
Click to expand...
Click to collapse
Hi, once a month you need to flash the new vendor for security updates
Google release them once a month (usually the first tuesday of the month)
However when you flash an update that does not require new vendor, you don't need to flash it
edit: just realised you're also from Melbourne, hi
Just have installed the last unofficial in my Angler, coming from another custom rom ( with Nougat). All good. Plan to stay here. Thanks !
Anyone having problems with the phone shutting down saying 0% battery when in reality you still have plenty of battery left? Just did a clean install and it happened after only installing chrome and whatsapp.
Apoena said:
Anyone having problems with the phone shutting down saying 0% battery when in reality you still have plenty of battery left? Just did a clean install and it happened after only installing chrome and whatsapp.
Click to expand...
Click to collapse
Have you been living under a rock for the past year? Lol jk. But see here http://www.androidpolice.com/2016/1...toff-problem-and-its-becoming-a-safety-issue/
tldr; blame Google and Huawei. And get yourself a free replacement or free upgrade.
http://www.androidpolice.com/2017/0...exus-6p-owners-pixel-xl-warranty-replacement/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About ResurrectionRemix
Resurrection Remix the ROM has been based on CM , SlimRoms, Omni and original Remix ROM builds, this creates an awesome
combination of performance, customization, power and the most new features, brought directly to your Device.
Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!
Special thanks to, the CM team, Omni team , SlimRoms and of course to all the supporters.
All the source code for Resurrection Remix is available in the RR GitHub repo: https://github.com/ResurrectionRemix
Official Resurrection Remix ROM changelog: https://github.com/ResurrectionRemix/android_vendor_resurrection/blob/oreo/CHANGELOG.mkdn
Original thread: https://forum.xda-developers.com/project-treble/trebleenabled-device-development/gsi-resurrection-remix-o-6-1-0-t3811299
Download Links
[URL="https://sourceforge.net/projects/resurrectionremix-oreo/files/armaonly/"]https://sourceforge.net/projects/resurrectionremix-oreo/files/armaonly/[/URL]
How to flash
- LineageOS 15.1 installed in order to use GSI ROMs (Optional) you can install over stock without problem. I've tested
- Download the latest build of Resurrection Remix ROM (I recommend to download without gapps and then install them later)
- Full wipe and factory reset (recommended / backup to make sure not to loose data)
- Flash the Resurrection Remix ROM GSI from the Recovery
- Reboot
- Gapps working on RR OS with the img that includes the gapps, but I'm not pretty sure If they work because of installing the image over stock ROM, and then I flash the fix given below, after flashing the image (try by yourself)
What's working
- Camera (use Opencamera o Google Camera) for gcam put into build.prop: persist.camera.HAL3.enabled=0
- Bluetooth
- Sensors
- Flashlight
- MTP
- Wifi (if it doesn't work, just wipe Dalvik/ART and cache with TWRP)
- Data
Not Working
- You tell me
- Navbar is not shown at the beginning, go to settings, RR Configurations and enable it
Lag fix for RR (Updated with new build.prop lines): https://drive.google.com/open?id=1ANWEsNgWM_OpDFoAOFUb0H3lwSnrNIdp
Device Tree: https://github.com/phhusson/device_phh_treble
Vendor/Hardware Overlays: https://github.com/phhusson/vendor_hardware_overlay
Build Scripts(upload scripts are ignored):
https://github.com/mracar07/rr_treble_scripts
Thanks to
@phhusson for all the efforts in project treble
@mracar for providing RR OS Official GSI
The LineageOS Team
The CyanogenMod Team
Everyone involved in working and testing
No go, error 255
so, you recommend only the img without the gapps then the fix... if we want to install the gapps later, where should we download them seperately without the need of the whole rom?
1juanzh0 said:
No go, error 255
Click to expand...
Click to collapse
On TWRP? which model and how did you installed?
SeerePetrova said:
so, you recommend only the img without the gapps then the fix... if we want to install the gapps later, where should we download them seperately without the need of the whole rom?
Click to expand...
Click to collapse
That's the way it worked for me, the version with Gapps are Go Apps from Android Go, sometimes you can use them without registering, but I don't know, sometimes they work and others not, you could try, but in my case I couldn't install gapps from TWRP, then I used RR with gapps
Fersho said:
On TWRP? which model and how did you installed?
Click to expand...
Click to collapse
Tried flashing thru TWRP, not fastboot, over stock OS. Hannah XT1924-7, MetroPCS variant.
1juanzh0 said:
Tried flashing thru TWRP, not fastboot, over stock OS. Hannah XT1924-7, MetroPCS variant.
Click to expand...
Click to collapse
Then try using LOS 15.1 instead, and removing encryptation, if it doesn't works maybe your variant is not compatible
Thanks, I got it to work thru fastboot. Had to fastboot - w right after flashing the .img file
how do we fix wifi issues. for example mine says that its connected with internet access but when i try to download or anything, it says that im not connected. The instructions say that we should erase dalvik cache and cache inside twrp but its encrypted and it doesnt allow me to mount those partitions to properly reset dalvik
SeerePetrova said:
how do we fix wifi issues. for example mine says that its connected with internet access but when i try to download or anything, it says that im not connected. The instructions say that we should erase dalvik cache and cache inside twrp but its encrypted and it doesnt allow me to mount those partitions to properly reset dalvik
Click to expand...
Click to collapse
because you need to decrypt the device in order to be in a custom ROM, edit fstab.qcom and flash no verity kernel for E5
XT1921-5 Boost variant
It does not work using a Verizon SIM. This phone has all the hardware capabilities of working on the Verizon network, with all CDMA and 4G LTE bands.
EDIT: It also does not work with preformated EXFAT sd cards, always reports as corrupt. This problem was fixed years ago on many phones/roms, but this rom has this problem.
EDIT2: I just tried the SIM that came with the phone and that is doing the exact same thing except instead of blank signal icon on the status bar I have a no SIM card icon.
In Hidden Settings app, it shows this
Phone Number: Unknown
IMSI: Unknown
Current Network:
Signal Strength:
Voice Service:
Data Service: Disconnected
Voice Network Type: Unknown
Data Network Type: Unknown
Voice Call Status:
Roaming:
I've tried changing "Set Preferred Network Type:" but it does nothing. I have also tried turn "Mobile Radio Power" on and off and still nothing. I just have a blank signal bar at the top, nothing mentioning Verizon.
In Settings/Network & Internet/Mobile Network/ it just shows everything greyed out with it turned off. Any ideas?
Hello, which version of Google Camera is working and what does/doesn't work? I just wan't hdr+ tbh lol
Beautiful work @Fersho. I'm very pleased to see a skilled developer such as yourself contributing these great pieces of development for these Moto E5 models.
1juanzh0 said:
Thanks, I got it to work thru fastboot. Had to fastboot - w right after flashing the .img file
Click to expand...
Click to collapse
I have MetroPCS also. Can you please give me the instruction of how you flashed the rom in fastboot. I'll be sure to hit the 'Thanks' button multiple times.
MotoJunkie01 said:
Beautiful work @Fersho. I'm very pleased to see a skilled developer such as yourself contributing these great pieces of development for these Moto E5 models.
Click to expand...
Click to collapse
Thanks, but as It is said in the thread I'm not a developer, I'm just sharing the way to install GSI, then I mentioned that the ROM is not mine, the only thing that I made by myself is the fix for lag issues, then I noticed that nobody shared here how to install GSI, and I tested all the GSI available for ARM in order to let you know which are the best or which ones where working, but as you know I love to share what I know, and I'm glad that people are able to use another ROM thanks to Treble and devs
Fersho said:
Thanks, but as It is said in the thread I'm not a developer, I'm just sharing the way to install GSI, then I mentioned that the ROM is not mine, the only thing that I made by myself is the fix for lag issues, then I noticed that nobody shared here how to install GSI, and I tested all the GSI available for ARM in order to let you know which are the best or which ones where working, but as you know I love to share what I know, and I'm glad that people are able to use another ROM thanks to Treble and devs
Click to expand...
Click to collapse
I realize you're not a "developer" in your own words, but I suppose that is a result of your humbleness. I make the same claim, and give all credit to the developers and maintainers of the GSIs. Nevertheless, I thank you all the same for your time and contributions, and I'm very glad you are a contributing part of the Moto E5 forum.
MotoJunkie01 said:
I realize you're not a "developer" in your own words, but I suppose that is a result of your humbleness. I make the same claim, and give all credit to the developers and maintainers of the GSIs. Nevertheless, I thank you all the same for your time and contributions, and I'm very glad you are a contributing part of the Moto E5 forum.
Click to expand...
Click to collapse
Well Is much appreciated what you say, and don't worry is just for helping each others
imakul8 said:
I have MetroPCS also. Can you please give me the instruction of how you flashed the rom in fastboot. I'll be sure to hit the 'Thanks' button multiple times.
Click to expand...
Click to collapse
boot the phone into fastboot and type:
fastboot flash system system-180818-arm-aonly-vanilla-nosu.img
after:
fastboot -w
lastly:
fastboot reboot
I've installed & everything seems to be running fine. Had the sd card issue & accidentally erased all my backups. Only issue now is GAPPS. Can someone explain to me how I get the ID to register?
Audio stutter/freezing when locked and on standby
Audio would stutter/freeze on standby (music and notifications), and audioFX was the issue, so thought to report and let the community know
to fix
1. reboot to twrp and mount system r/w
2. go to /system/priv-app/AudioFX and rename AudioFX.apk and delete the last letter to look like this : AudioFX.ap
reboot and audio should work properly
Hope that helps, And love the rom!
Moto E5 Play
XT1921-1 (James)
This thread hosts personal builds of LineageOS 17.x and PixelExperience 10 for Mix 2. Full credits to Arian, Wight and others doing the actual bringup, allowing us to build upon the awesome work.
Small changes in my builds:
Default stretch-to-fullscreen (force apps to render in 18:9) - LOS official solution defaults to OFF, which complicates setup
Grey-blue DeskClock color scheme (when possible)
Navbar stays on the right side of the screen under 270° rotation (optional - set the behaviour with "setprop persist.ui.seascape.disable <true|false>" in a rooted shell)
Signature spoofing support from MicroG
Revived navbar layout tuning via sysui_nav_bar tunable
...
What's working:
Everything?
Instructions:
Use firmware Stable V11.0.3.0
Use official TWRP
Download the latest build and optionally GAPPS (PE comes with GAPPS though, don't use any from external sources)
Reboot to TWRP
Flash the latest build, GAPPS and whatever other additions you need
Reboot
Extras:
Read here if you want to use unencrypted data - post is from Oreo thread, but still applies
Downloads:
SourceForge folder: https://sourceforge.net/projects/andyyan/files/ - new releases in the "10" folder
Root: use Magisk
Google Apps: http://opengapps.org/
Source Code:
https://github.com/LineageOS/
Donation:
Donate to @NeoArian
Donate to @wight554
Donate to me
XDA:DevDB Information
LineageOS 17.x, ROM for the Xiaomi Mi Mix 2
Contributors
AndyYan, NeoArian, wight554
Source Code: https://github.com/LineageOS/
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: MIUI V11.0.3.0
Based On: LineageOS
Version Information
Status: No Longer Updated
Created 2020-01-11
Last Updated 2020-02-27
Reserved
I don't know for how much longer I'll be able to keep building these, but even if I do stop, these should still serve as a good basis for installing GSIs, so you can leverage many of them out there, including my own. As far as I've tested the only major bug on that front is the proximity sensor.
Compared to the test builds of last year...
- Now using official LOS device trees - you might have to clean flash even if you come from a previous test build by me
- IMPORTANT regarding PE - if you're clean flashing, flash the package twice so that /system can be populated properly. I have no idea why this is happening...
is there any ETA on android 10 Resurrection Remix?
also thanks for your work as usual!
Mollic said:
is there any ETA on android 10 Resurrection Remix?
Click to expand...
Click to collapse
Its customization-centric role has largely been replaced by Havoc nowadays, so with my limited SSD space I'm dropping that as well.
Screen time have a bug, is look like this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
great job for years
Grick713 said:
Screen time have a bug, is look like this.
Click to expand...
Click to collapse
Have you changed your system font? Seems incompatible.
Have a problem while installing new PE.
Wiped everything (system, vendor, data). Installed zip (twice, as advised), no error messages.
TWRP warns on reboot that no OS is installed. Phone reboots to fastboot.
Tried twice with the same result. Tried re-downloading zip without success.
Ok, managed to solve the problem. As the device tree is from LOS, the solution is in the LOS thread. Need a recovery with support for SAR. Seems like official TWRP does not. So flashed recovery from the first post of LOS thread and the OS have installed just fine.
dairinin said:
Have a problem while installing new PE.
Click to expand...
Click to collapse
Thing is, I tried Wight's SAR TWRP and it's the same thing on my side - I really had to flash it twice (but not in the same queue/go).
This shouldn't have happened in the first place either, as LOS flashed just fine without this hassle.
@AndyYan
Nice to see you again being active, and thx (of course to all users who made it possible) providing LOS 17.
I know, this is probadly the wrong thread for this, but openGapps doesn't provide GAPPS for 10. The option is always greyed-out. Where do i get GAPPS then?
SanHelios said:
@AndyYan
Nice to see you again being active, and thx (of course to all users who made it possible) providing LOS 17.
I know, this is probadly the wrong thread for this, but openGapps doesn't provide GAPPS for 10. The option is always greyed-out. Where do i get GAPPS then?
Click to expand...
Click to collapse
You can find them on Sourceforge: https://sourceforge.net/projects/opengapps/files/arm64/beta/
However, not flashable on LOS: Gapps detect SDK 27 (Android 8.1). @AndyYan, can you look into it?
Update: found that PE prop.default file is fine, but for LOS it's old (says SDK=27 and some stuff more). I think you forgot to include proper props to LOS build.
SanHelios said:
@AndyYan
Nice to see you again being active, and thx (of course to all users who made it possible) providing LOS 17.
I know, this is probadly the wrong thread for this, but openGapps doesn't provide GAPPS for 10. The option is always greyed-out. Where do i get GAPPS then?
Click to expand...
Click to collapse
candiduslynx said:
You can find them on Sourceforge: https://sourceforge.net/projects/opengapps/files/arm64/beta/
However, not flashable on LOS: Gapps detect SDK 27 (Android 8.1). @AndyYan, can you look into it?
Update: found that PE prop.default file is fine, but for LOS it's old (says SDK=27 and some stuff more). I think you forgot to include proper props to LOS build.
Click to expand...
Click to collapse
Aw, I don't use GAPPS so I didn't verify that...
Does manually changing prop.default make it pass? Supposedly there's nothing in the device source dictating that.
AndyYan said:
Aw, I don't use GAPPS so I didn't verify that...
Does manually changing prop.default make it pass? Supposedly there's nothing in the device source dictating that.
Click to expand...
Click to collapse
There are several lines that need to be changed (for instance, arch is set to 'arm' instead of 'arm64'). I decided to go with PE for now and don't want to reconfigure all stuff once more.
What a treat to start 2020 to! Thanks for the new build Andy. I'll be reporting back if I find something buggy or similar =)
candiduslynx said:
You can find them on Sourceforge: https://sourceforge.net/projects/opengapps/files/arm64/beta/
However, not flashable on LOS: Gapps detect SDK 27 (Android 8.1). @AndyYan, can you look into it?
Update: found that PE prop.default file is fine, but for LOS it's old (says SDK=27 and some stuff more). I think you forgot to include proper props to LOS build.
Click to expand...
Click to collapse
Weird, I didn't had this problem yesterday. I used "open_gapps-arm64-10.0-nano-20191209-BETA.zip" on LOS.
@AndyYan Thanks for your build of LOS, it's working like a charm here.
Just gotta need a patch for my provider APN. (I'm on it)
Great news!!! Thank you Andy. Can i dirty flash from LOS16 to LOS17?
The problem is solved，thanks！
SanHelios said:
@AndyYan
Nice to see you again being active, and thx (of course to all users who made it possible) providing LOS 17.
I know, this is probadly the wrong thread for this, but openGapps doesn't provide GAPPS for 10. The option is always greyed-out. Where do i get GAPPS then?
Click to expand...
Click to collapse
I recommend flamegapps
Thanks @AndyYan for the build. I have flashed the PixelExperience version and it is working fine. Using Parrot043's GCam version and the photo quality is also fine.
The major issue I have is regarding VoLTE incoming call support on my carrier (Airtel/India). Outgoing calls are fine, but for incoming (VoLTE) calls my phone doesn't ring at all, but on the caller side it looks as if it is ringing and I am not answering calls. For the time being I have switched to WCDMA mode.
Any input to solve the VoLTE issue is highly appreciated. I have tried creating an APN named IMS with type as ims, but that didn't work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Moto G7/G7 Power
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 19.1 thread for the Moto G7/G7 Power.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
Moto G7
river - Official builds
river - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.
Moto G7 Power
ocean - Official builds
ocean - 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:
None.
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.
Kernel Source: https://github.com/LineageOS/android_kernel_motorola_sdm632
Nice work. For install going from 18.1 to 19 do we need to flash the copy partition zip like the initial install?
Just installed from 18.1 without issues. Time to play around
PMDPhD said:
Nice work. For install going from 18.1 to 19 do we need to flash the copy partition zip like the initial install?
Click to expand...
Click to collapse
Read the upgrade guide, no.
npjohnson said:
Read the upgrade guide, no.
Click to expand...
Click to collapse
I did. Just wanted to be sure because sometimes the guides leave out steps. Install was fine, looks like it is missing the FM Radio app, any reason why? Thanks.
PMDPhD said:
I did. Just wanted to be sure because sometimes the guides leave out steps. Install was fine, looks like it is missing the FM Radio app, any reason why? Thanks.
Click to expand...
Click to collapse
Fixing it.
Beautiful, solid build! Superb job, you guys!
As far as "bugs unknown" clause is concerned, my river model xt1962-4 does seem to have a location bug since los 18.1 which did NOT occur in 17.1 The bug has been reported here
If anyone with the same model on 18.1 or 19.1 would take time to check whether you also experience this issue, I would greatly appreciate it!
Only issue I have so far is a pop up telling me "Android System Intelligence keeps stopping".
xnotx2 said:
Only issue I have so far is a pop up telling me "Android System Intelligence keeps stopping".
Click to expand...
Click to collapse
My brain notification service shows the same message from time to time as well: "System Intelligence keeps stopping"
xnotx2 said:
Only issue I have so far is a pop up telling me "Android System Intelligence keeps stopping".
Click to expand...
Click to collapse
Fixed in next build.
xnotx2 said:
Only issue I have so far is a pop up telling me "Android System Intelligence keeps stopping".
Click to expand...
Click to collapse
I haven't seen this error in this build. If my memory serves me, I have seen this error it in the Pixel Experience ROM last year with a different device. It turned out that flashing a newer GAPPS package fixed this. I used the Mind The GApps 12.1 for this build and seems to be ok.
eulos said:
Beautiful, solid build! Superb job, you guys!
As far as "bugs unknown" clause is concerned, my river model xt1962-4 does seem to have a location bug since los 18.1 which did NOT occur in 17.1 The bug has been reported here
If anyone with the same model on 18.1 or 19.1 would take time to check whether you also experience this issue, I would greatly appreciate it!
Click to expand...
Click to collapse
I just checked Google Maps. Seems very accurate and not jumping around like in the report.
PMDPhD said:
I haven't seen this error in this build. If my memory serves me, I have seen this error it in the Pixel Experience ROM last year with a different device. It turned out that flashing a newer GAPPS package fixed this. I used the Mind The GApps 12.1 for this build and seems to be ok.
Click to expand...
Click to collapse
This is what I used.
lineage-19.1-20220422-UNOFFICIAL-river
MindTheGapps-12.1.0-arm64-20220416_174313
Woot. Just noticed it's being fixed in next build.
All good with the installation but when starting the cel it can't communicate with the google server and I can't log in in any way, I reinstalled 3 times with the same result... any ideas?
what version of twrp is recommended for installing the moto g7 power ocean builds. i have twrp 3.5.2.10 on my device. want to be sure that it will install with that version of twrp. i prefer twrp over the lineage recovery for installing builds. currently the moto g7 power i have is on lineage 18.1 but would like to update to lineage 19.1 when the next build is out.
mrk2815 said:
what version of twrp is recommended for installing the moto g7 power ocean builds. i have twrp 3.5.2.10 on my device. want to be sure that it will install with that version of twrp. i prefer twrp over the lineage recovery for installing builds. currently the moto g7 power i have is on lineage 18.1 but would like to update to lineage 19.1 when the next build is out.
Click to expand...
Click to collapse
use lineage recovery.
eulos said:
My brain notification service shows the same message from time to time as well: "System Intelligence keeps stopping"
Click to expand...
Click to collapse
Rule #1: No tokin' while flashing bro...
Loving the Android 12 experience on my G7. I too am experiencing some of the same issues described here. When flashing the Official ROM, and MindtheGapps, the setup program couldn't communicate with Google. It kept telling me to connect to the Internet, even though my home wifi was showing as "Connected." When I flashed the Unofficial (with Gapps included), that allows me to register, and I keep getting "System Intelligence keeps stopping" message. I tried to be sneaky and flash the official ROM through recovery/ADB after installing and setting up the unofficial ROM, but that put me in a boot loop.
Does the unofficial ROM get updates as frequently as the official (approx. every week)?
JShan said:
Loving the Android 12 experience on my G7. I too am experiencing some of the same issues described here. When flashing the Official ROM, and MindtheGapps, the setup program couldn't communicate with Google. It kept telling me to connect to the Internet, even though my home wifi was showing as "Connected." When I flashed the Unofficial (with Gapps included), that allows me to register, and I keep getting "System Intelligence keeps stopping" message. I tried to be sneaky and flash the official ROM through recovery/ADB after installing and setting up the unofficial ROM, but that put me in a boot loop.
Does the unofficial ROM get updates as frequently as the official (approx. every week)?
Click to expand...
Click to collapse
He mentioned above that his unofficial builds are roughly monthly.
JShan said:
Loving the Android 12 experience on my G7. I too am experiencing some of the same issues described here. When flashing the Official ROM, and MindtheGapps, the setup program couldn't communicate with Google. It kept telling me to connect to the Internet, even though my home wifi was showing as "Connected." When I flashed the Unofficial (with Gapps included), that allows me to register, and I keep getting "System Intelligence keeps stopping" message. I tried to be sneaky and flash the official ROM through recovery/ADB after installing and setting up the unofficial ROM, but that put me in a boot loop.
Does the unofficial ROM get updates as frequently as the official (approx. every week)?
Click to expand...
Click to collapse
Once a month.
LineageOS 20.0 for Sony Xperia XZ1 Compact
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
RELEASE
This is an alternative ROM for the Sony Xperia XZ1 Compact, offering several privacy features.
Please report any issues you observe apart from the ones listed below. Logs are needed for me to fix anything (preferably dmesg and logcat). I can't test NFC very thoroughly, to please report your findings.
FEATURES
Signed with dev keys
Up-to-date kernel
WireGuard kernel support
DOWNLOAD
ROM: https://sourceforge.net/projects/yoshino/files/lilac/lineage-20.0/
TWRP: https://sourceforge.net/projects/yoshino/files/lilac/twrp/
Suggested Gapps (MTG): http://downloads.codefi.re/jdcteam/javelinanddart/gapps (choose 13.0.0/arm64)
Check the ChangeLog below for firmware requirements!
INSTALLATION
Before first install: flash and boot into the TWRP provided in this thread, format data, reboot to recovery and wipe all internal partitions, then flash the ROM, GApps and root (if needed).
Or if you are coming from Lineage 19.x, dirty flash to 20.0 is possible too: flash the new TWRP, ROM, and GApps, su addons (if needed).
Note: There is not going to be a LOS su addon anymore. If you need root, flash a root manager of your choice. No guaranteed support from LOS for this.
When updating from previous builds, simply dirty flash the ROM is enough, decryption in new TWRP works now
Recommended GApps: MindTheGapps provided in this thread.
KNOWN ISSUES
Stock camera is not working anymore due to incompatibility of stock library (libimageprocessorjni.so) with new libgui
You tell me...
Contributors
derf elot, modpunk, Rooted_Ansh
Thanks to the yoshino testers (let me know if I forgot to add you)
coin3x, feduss, GiaSen, Gizanagi, hsheemi, kaancaliskan, sohrab1985
Source Code
https://github.com/whatawurst/android_device_sony_lilac
https://github.com/whatawurst/android_kernel_sony_msm8998
https://github.com/whatawurst/android_device_sony_yoshino-common
Rom Information
ROM OS Version: Android 13
ROM Kernel: Linux 4.4
Version Information
Status: Stable
Current Stable Version: 1.2
Stable Release Date: 2023-05-10
SECURITY ADVICE
Don't flash ROMs or Magisk modules which set SELinux to permissive or you welcome malware on your device!
How to get root?
As mentioned before, there will not be an official su addon from LOS anymore. If you need root, flash an unofficial solution.
REQUIRED FIRMWARE:
CHANGELOG
Suggested Gapps (MindTheGapps) - choose 13.0.0/arm64:
https://androidfilehost.com/?w=files&flid=322935 or http://downloads.codefi.re/jdcteam/javelinanddart/gapps
v1.2 (2023-05-10):
Updated to T QPR2 release (LineageOS upstream)
Updated to May 2023 Security updates (both ROM and kernel)
Our kernel now includes updates by CIP and is up-to-date with tag st40 - thanks also to Flamefire for help with some of these (1)
Reduced zram size to 25% (1gb) of out total RAM to have more to use freely
Updated BT stuff for QPR2 (maybe offloading is working again? needs confirmation)
Added the option to reflash the mbn via OpenCS (see Xperia Parts) - thanks also to shank03 & Flamefire (2)
Fully enabled IMS on Congstar Germany via overlay on lilac
Possibly some battery/performance optimizations here and there
Fixed Android Auto support
Added new LineageOS "Charging control hal" for battery charging care (3)
Maybe more I forgot...
(1) The CIP kernel includes fixes for issues and security vulnerabilities from 4.14 kernel (see https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git)
(2) A somehwat lengthy explanation: This option is off by default on fresh installs. When upgrading, this should be enabled because we enforced this for everybody previously. However, this option is only required for certain carrier mbns that enable IMS. Personally, I know that the O2/Telefonica Germany mbn needs this, otherwise you get a crashing modem at every boot (unless you switch to 3g before rebooting and back to LTE after boot). I generally recommend playing with this option, and if you don't need it (e.g. modem doesn't crash on boot), just keep it off - like mentioned before, this is now the default behavior of OpenCS on fresh installs anyway.
(3) This is not finalized or merged upstream is LineageOS yet, but seems like a nice feature to have and test drive already. Some bugs may be possible.
2023-01-08 | 1.1 | 47.2.A.11.228
- Updated to T QPR1 release (LineageOS upstream)- New default camera app (LineageOS upstream) - yes, we cannot change video fps currently (thanks Sony!)- Any other updates by LineageOS upstream- Kernel security updates (also thanks to Flamefire)- Dropped keyprovd service - it is useless on unlocked BL anyway- Show 4G instead of LTE icon - saves some space too- Enable IMS by default - this still only works if carrier is supported- Fix some selinux denials (also thanks to Flamefire)- Fixup ViLTE dependencies - this might in theory work again, but it's not enabled yet
2022-10-03 | 1.0 | 47.2.A.11.228
Initial release
Hello, I've flashed this ROM onto my device and it works, however Wi-Fi seems to randomly disconnect for a few seconds then reconnect, sometimes doesn't reconnect at all. Tried searching for a solution but found none. It seems to disconnect when any type of location activity happens? Currently rooted but also happens without root.
Sneexy said:
Hello, I've flashed this ROM onto my device and it works, however Wi-Fi seems to randomly disconnect for a few seconds then reconnect, sometimes doesn't reconnect at all. Tried searching for a solution but found none. It seems to disconnect when any type of location activity happens? Currently rooted but also happens without root.
Click to expand...
Click to collapse
did you format data
reboot to recovery
wipe all internal portions
reboot to recovery
then flash rom
just curious because i was gona try it
victor126 said:
did you format data
reboot to recovery
wipe all internal portions
reboot to recovery
then flash rom
just curious because i was gona try it
Click to expand...
Click to collapse
Yes, multiple times.
Dirty flash from 19.1 and all work! Thanks
I have done clean flash and I don't get any notifications or call screen on phone calls causing missed calls. No problems on wifi and mobile
susetoyix said:
I have done clean flash and I don't get any notifications or call screen on phone calls causing missed calls. No problems on wifi and mobile
Click to expand...
Click to collapse
Weird, first time hearing this. Everything works just fine for me.
sohrab1985 said:
Weird, first time hearing this. Everything works just fine for me.
Click to expand...
Click to collapse
Kinda not recurring anymore after a few more reboots. I'll keep a lookout on this.
Anyone know if lte for t-mobile works on this? I couldn't get lte on lineage 19.
azndan2 said:
Anyone know if lte for t-mobile works on this? I couldn't get lte on lineage 19.
Click to expand...
Click to collapse
t mobile and its nvmo's are the only place this phone is not white listed
rez78 said:
Dirty flash from 19.1 and all work! Thanks
Click to expand...
Click to collapse
does split screen work on 20. it didnt work for me on 19.1
victor126 said:
t mobile and its nvmo's are the only place this phone is not white listed
Click to expand...
Click to collapse
Could you be more specific? I believe it's blacklisted on AT&T. It doesn't work at all on Verizon, because it has the wrong bands.
I've seen plenty of reports of it working on T-Mobile.
How does it work compared to 19.1? Any bugs?
azndan2 said:
Anyone know if lte for t-mobile works on this? I couldn't get lte on lineage 19.
Click to expand...
Click to collapse
4G calling didn't work for me.
I used carrierconfig, the LOS version with 4G calls working.
This requires root.
The carrierconfig is located at data/user_de/0/com.android.phone/file.
carrierconfig-com.android.crrierconfig-~.xml
Replace the contents without changing the numbers in the name.
Why don't you try it?
sorry for my weird english.
norabitox said:
4G calling didn't work for me.
I used carrierconfig, the LOS version with 4G calls working.
This requires root.
The carrierconfig is located at data/user_de/0/com.android.phone/file.
carrierconfig-com.android.crrierconfig-~.xml
Replace the contents without changing the numbers in the name.
Why don't you try it?
sorry for my weird english.
Click to expand...
Click to collapse
What do I replace the contents with?
tonsofquestions said:
Could you be more specific? I believe it's blacklisted on AT&T. It doesn't work at all on Verizon, because it has the wrong bands.
I've seen plenty of reports of it working on T-Mobile.
Click to expand...
Click to collapse
correct. t mobile and mint, and others that use t mobile work.
azndan2 said:
What do I replace the contents with?
Click to expand...
Click to collapse
carrierconfig.xml for the LOS version that LTE was working on your phone
victor126 said:
correct. t mobile and mint, and others that use t mobile work.
Click to expand...
Click to collapse
Sorry, what? Can you please be more specific?
First you said it was _not_ whitelisted on T-Mobile (so presumably doesn't work) and now you say it _does_ work on T-Mobile.