Related
Anybody tried phoenix os in flounder..? They have released a beta image..
If you want to check it out: http://files.phoenixos.com/os/PhoenixOS_Nexus9_V1.0_Beta.tgz or
http://www.phoenixos.com/download
If anybody tried, tell your experience. I have tried remix os 1.5 in flounder.
can't get it to boot. installed and it just sits at google
aeppacher said:
can't get it to boot. installed and it just sits at google
Click to expand...
Click to collapse
I haven't tried to install it. But if it's anything like Remix OS 1.5, it might be based on 5.0? So you would need the 5.0 Vendor and Bootloader for this to boot properly.
EDIT: Correction, I read from another source that it's based on 5.1.1. Try going back to the latest 5.1.1 Vendor and Bootloader.
Booting up for me. You have to flash the boot loader and vendor from 5.1.1. So far I'm at the PhoenixOS boot screen. Can't tell if it's loading or frozen lol.
Edit: Ended up having to format data to remove encryption (was previously decrypted) and sore dalvik and cache. Boots, but needs work. Better suited for a desktop, as there are no back or home buttons. Flashed gapps, but play store won't open
Got it to boot by flashing over 5.0. Flashed gapps as well but play store doesn't open. Remix is way more polished and much better for tablets. Also some things aren't translated, still getting Chinese on certain ui elements
Meh, I haven't tried Phoenix OS but I have tried Remix. It's okay. I was hoping for a version that looked more like windows and mac versions. No app drawer, no options to remove apps from homescreen, the phone orientation isn't supported in most apps. Overall, the OS has potential, but right now it feels like IOS with a bit of Samsung's multiwindow. I switched back to Pure Nexus rom because apps like glovebox and launchers don't work on the OS. I'll come back to it once some of those issues are addressed.
Hi all,
I have been trying to port TWRP for my device (a somewhat dated tablet, the Toshiba AT100 Thrive) but am running into problems with the kernel. It seems that no matter what I try, I am unable to get a kernel that actually boots.
I have the full OmniROM 4.4 source (with the end intention of building OmniROM for the tablet) as well as the kernel source from Toshiba (it is their patched version of 2.6.39.4). I also have a known working recovery (built around CWM with a 2.6.39 kernel) and stock boot.img and ICS ROM for the tablet.
I have extracted the kernel config from the ICS ROM as well as the kernel command line parameters.
Additionally, I also have access to two other ports (CyanogenMod) with kernel sources for this tablet and have found the AOSP source for the 2.6.39 and 3.10 kernels.
I am using CentOS 6.7 64-bit as my build OS, as that is what I have running on my Linux machine. I have OpenJDK 1.6 installed as opposed to the Oracle version (this might affect building OmniROM, but certainly shouldn't affect the kernel build).
I can successfully compile the kernel from the Toshiba sources using the tablet's config, as well as the CM-based port kernel sources and the 3.10 kernel (2.6.39 has some bugs straight out of the Google repository, which I can only get around if I disable yaffs2 in that kernel config or replace the yaffs2 source for it with the equivalent from the Toshiba sources).
I have the Android emulator set up on my Windows machine with both a ICS and KitKat AVD. After being unable to get the Toshiba-based kernel to start on my tablet, I thought I'd try building a kernel from the sources to run in the emulator.
At this stage, not a single one of my kernels has successfully booted either the tablet or the emulator. I have tried using the kernel config from the ICS AVD to build both the Toshiba 2.6.39 and AOSP 3.10 sources. The compile completes with no errors and a zImage is produced. However, it fails to boot the emulator.
Out of desperation, I have tried downloading the toolchains for Gingerbread and ICS and using those to build the kernels instead of the toolchain provided with OmniROM 4.4. That hasn't made a difference, either.
On the tablet, I have tried extracting the known working recovery kernel from the CWM recovery and using it as a prebuilt kernel. TWRP fails to load and the tablet always reboots after a few seconds, regardless of whether I set the kernel commandline parameters or not.
I am puzzled by this. Clearly there is something wrong but I am at a loss as to how to debug it, especially as do not appear to be able to produce a working kernel either for the tablet or emulator, despite having the sources and the kernel configs.
If anyone has any suggestions, they would be much appreciated.
Still have the same problem.
I've now tried building an Ubuntu 12.04 VM and compiling the kernels within that, but still get the same results.
Does anyone have any ideas or has anyone else ever run into this problem?
Did it ever work? I am experiencing this with SM-G950F. Very keen.
Unfortunately I was not able to resolve the issue. After spending a fair bit of time on it, I gave up and moved onto other projects. I've still got everything I need to try again, so at some point I may do so (especially as a use case for my tablet is possible again in the near future).
This is a port of OMNIRom 7.1.1 for the Samsung Galaxy Tab A 7.0 (2016) LTE SM-T285. OMNIRom aims to be a community based project and is a lot "lighter" than CyanogenMod/LineageOS.
5.1.1 is the best that you can get from samsung right now and it is not known if they plan to do any upgrades. I have absolutely no idea why samsung chose to stay with the outdated 5.1.1 mid 2016 when we already got 7.1 coming out. This custom rom is probably the best you can get if you want an upgrade from Lollipop. Performance on the latest build is also better, you be the judge.
Though this is stable enough that I use it currently as my daily driver, make sure you read the pending issues below and decide if this is acceptable to you before you flash this rom. This rom probably won't get much use out of some people until bluetooth is fixed.
Based off on OMNIRom 7.1.1 N4F260 sources which is based on Marshmallow.
For more information on OMNIRom and its features see their site here.
Device Tree:
=========
https://github.com/jedld/device_samsung_gtexslte.git
https://github.com/jedld/vendor_samsung_gtexslte.git
https://github.com/jedld/kernel_samsung_gtexslte.git
Omnirom Notes:
=============
- omnirom doesn't have ffmpeg libraries unlike the CM based roms, but no worries since I ported over CMs libraries here.
Works:
- Wifi/LTE/SMS (Some users report data intermittently not connecting, though toggling airplane mode on/off can fix it)
- Audio
- Graphics
- Bluetooth
- Wifi Hotspot
- MTP
Does not work:
- Calls (needs testing)
- Camera
- GPS (no fix)
- probably more (need testers)
Download
========
Remember flashing an unofficial ROM on your samsung device will probably void your warranty. Don't expect samsung to support you if you have any issues.
As always flash this at your own risk. Make sure you have a copy of the stock ROM so that you have something to fall back to, which is highly the case when using an experimental rom.
See DevDB download section for older releases. Or click below for the latest release:
https://forum.xda-developers.com/devdb/project/dl/?id=23245
Note that this rom is pure stock and does not come with the Play Store or any Gapps, I suggest you download a micro gapps package separately and install it via recovery.
There have been reports that recent versions of open gapps don't work properly, it is advised to use older versions instead (e.g. open_gapps-arm-6.0-nano-20161109.zip)
Installation Instructions
==================
Perform a backup of all of your important files. This ROM is experimental and I will not be responsible for your loss of data.
Download the zip file and extract the tar.
Use Odin/Heimdall to flash the tar file to your device. If you are coming from stock oranother rom make sure you wipe first using TWRP. Coming from a previous version of OMNIRom for SM-T285 may not require a wipe, however please perform a wipe if you encounter problems.
Root and customization
===================
This ROM is a purely based on source and is not rooted out of the box. However you can easily root it by using TWRP to install the latest version of SuperSU.
If you want to customize this ROM and repackage it you may use this guide as a reference.
XDA:DevDB Information
Omnirom 7.1.1 Galaxy Tab A 7 LTE SM-T285, ROM for the Samsung Galaxy Tab A series
Contributors
jedld
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: Omnirom
Version Information
Status: Testing
Created 2017-02-18
Last Updated 2017-02-20
Possible Hope?
Im Not A Developper But I'm The Closest Thing There Is To It. Il Be Running Some Tests To See If It Might Be Compatable With The Sm-t280 Model. Any Boot.Img I Should Install First?
thanks Jedid-did you have a link here for the ROM as I cannot see it (says status is testing so perhaps a placeholder?) as always great work!
mac231us said:
thanks Jedid-did you have a link here for the ROM as I cannot see it (says status is testing so perhaps a placeholder?) as always great work!
Click to expand...
Click to collapse
should be available now
Tinker101 said:
Im Not A Developper But I'm The Closest Thing There Is To It. Il Be Running Some Tests To See If It Might Be Compatable With The Sm-t280 Model. Any Boot.Img I Should Install First?
Click to expand...
Click to collapse
It will be a long shot, there are hardware differences, but nothing stopping you from trying it. Do note that the T280 has a padded boot.img see here, which means you need to get the boot.img from this rom and add an additional header in front of it before you flash it with heimdall or odin.
jedld said:
should be available now
Click to expand...
Click to collapse
thanks Jedid
will look in a couple of days when I the Tab back (gave it to a friend)
EDIT
tried the ROM today...calling is a problem (for me) tried multiple times of reboot and allowed rom to settle before making calls (4g and data in out activity was showing-could go to internet)
The call does not connect and sits in dialing mode forever...if you try to hang up it then sits in hanging up mode and will not terminate
(shows a call in progress as if it is still on)...sms works
With all credit to you and all due respect...I stopped there-
think your very FIRST Lineage 14.1 was the best in all the Nougat ROMs
(the next one had issues with the drives seen but not accessible even though the MTP thing was purported to have been solved in that one)-i.e no real files just drives with overall sizes shown and then the lockscreen issue made it unusable (the PIN and notification method was risky as swiping the notification accidentally would lead to an inaccessible phone or maybe demand a reboot)
Works for me
I don't use the Sim functionality at all, so can't comment on that. I had to try a few variations of GApps to get a working Google Play service, and finally managed with the Dynamic GApps 20170215 Minimal build. Once I got that going, everything worked well. I'm using this as my daily ROM on the tablet now, so will report any further issues I have. Just wanted to say a big thank you! This ROM is very fast and smooth.
home button to wake up device
hi, i just use this rom and its really fast..
just want to ask how to make home physical button to wake up device beside the power button ?
Original Link worked but the file i got
"omni-6.0-20161209-UNOFFICIAL-SMT285-BETA-3.tar"
did not flash, rejected by Odin.
The new one you have linked works
"omni-7.0-20170219-UNOFFICIAL-SMT285.tar"
Quick scan results:
Mem use 462mb of 1.4gb
Space use 2.71 of 7.28gb
Apps installed 17
Very Similar to Lineage "LINEAGE-OMS-14.1-20171209-UNOFFICIAL-SMT285.tar".
In fact almost exact other than a couple of megabytes and an app.
This is BEFORE SU And APP Remover has gone in to shred some files
Stock rom: Terrible
Mem use 5 TB of 1.4gb
Space use Smoke coming out of 7.28gb
Apps installed Still counting I was sure it would finish last week.
Stock rom: Terrible
Mem use 874mb of 1.4gb
Space use 3.7gb of 7.28gb
Apps installed 64
Vol Down Button
Home
Power
[DOWNLOAD SCREEN]
Vol Up to confirm
{Go to PC Odin}
Load AP Custom Rom (TWRP Required)
Press Start...
file explorer cannot read files in internal and external sd card, is it just me, or anyone else?
Download
thank
Can anyone send me other link this ones showing not found.
Link not found
thatha said:
Link not found
Click to expand...
Click to collapse
index - powered by h5ai v0.30.0 (https://larsjung.de/h5ai/)
index - powered by h5ai v0.30.0 (https://larsjung.de/h5ai/)
aol.zanoza.lv
Here is the link.
Reload 4 times if not loading.
Hi everyone,
My phone has this restarting loop issue after flashing either Candy7 or CM13 ROM. Not sure if this is bootloop error because It got pass the Huawei booting logo, but as soon as it finish loading the Google App and go to the OS home screen it restart again and again. Worth noting that the phone restart from ROM loading logo (the blue face for CM13 or the Google Dot for Candy7), not all the way back from Huawei booting logo.
First I use TWRP to factory reset wipe, then advance wipe /system, /data, /cache / Dalvik, then install new ROM + Gapp, and got the sucess message, then reboot to system.
I also tried with out Gapp to save loading time, and it restart again when get to OS home screen.
Please advise what may cause this.
No issue when i restore back to B322 EMUI 3.1
I have US version unlocked MT2-L03, B322 version, unlocked bootloader, rooted, TWRP 3.1.1.0 installed.
I made a video clip of the looping: https://www.youtube.com/watch?v=Y7kRpdGN2qA
I'm going through the EXACT same thing. I tried CM13, CM14 and even CandyRom, and the same thing happened more or less. Even if I got the ROMs running for a while, eventually that LOD (Loop of Death) would hit and I'd have to again reflash. I'm now back to B322 (Lollipop) for stability.
Given that the SAME thing is happening on all those ROMs, it's leading me to think that perhaps there is a software issue with my phone. Not sure if this helps, but I do think it could be the way I updated to Lollipop (B322) from the original Jelly Bean (B148). I've done a LOT of digging, and it looks like the way I did it was not quite right, even though my phone has worked fine all this time.
Here is the XDA post that seems to detail the correct upgrade path to B322:
https://forum.xda-developers.com/ascend-mate2/help/how-to-update-unlocked-mt2-l03-to-t3422775
Basically, it looks like the correct path should be B148 (Jelly Bean) --> B309 (Lollipop) --> B322 (Lollipop)
Being rather new, I just flashed to B322 right off of B148. I am now wondering if this could be the source of my problems. Especially since I keep getting the "Error 7" for "unknown bootloader" whenever I use TWRP 3.1.1 to flash LineageOS or CandyRom.
But, if you successfully used TWRP 3.1.1 to flash, that means your bootloader was recognized (I got the Error 7). If that's the case, then we're both having the same issue and something else is indeed the culprit.
I strongly suspect that "something else" could be GAPPS. I've experimented with several GAPPS packages, and noticed that right before crashing and the dreaded infinite loop, something glitched involving Google apps.
Desperately want to leave Lollipop since Oreo is about to drop meaning we Android L users are in for a world of hurt if we can't migrate soon. :-\
I upgrade my phone B148-B309-B322. I also get error 7 whenever I flashed the ROM, so I have to manually delete '"assert" command line from ROM script to flash successfully.
Error screen shot: http://imgur.com/zzTbjRJ
hondaman82 said:
I upgrade my phone B148-B309-B322. I also get error 7 whenever I flashed the ROM, so I have to manually delete '"assert" command line from ROM script to flash successfully.
Error screen shot: http://imgur.com/zzTbjRJ
Click to expand...
Click to collapse
My phone has been rooted for over a year now, I've had many roms on it doing that time. This loop started with a app I updated from the play store. Not sure it may be substratum will look into it when I have more time..
These problems is because of the room. Try to install lineageOs.
Thanks Kevinoriej,
Same looping issue on LineageOS, after loading to OS homescreen , phone restart.
Also get error 7, and manually remove "assert" lines in the ROM script in order to flash.
hondaman82 said:
I upgrade my phone B148-B309-B322. I also get error 7 whenever I flashed the ROM, so I have to manually delete '"assert" command line from ROM script to flash successfully.
Error screen shot: http://imgur.com/zzTbjRJ
Click to expand...
Click to collapse
I believe the Error 7 message is because your bootloader is showing as "unknown". I downloaded an app from the Playstore that gave me my device's technical info, and sure enough, my bootloader is listed as "unknown". I forwarded a question to Huawei's EMUI team asking them if that happened due to unlocking it (using Huawei's official unlocking request). Still waiting for a replay. In order to get any of the ROMs to install, I had to downgrade TWRP to 2.8.7.0. Any version above that would trigger Error 7.
Out of curiosity, I then downgraded and flashed CandySix (with a corresponding GAPPS package) - and sure enough, the same looping happened. And again when I flashed CM13 AND LineageOS. The phone would successfully boot, get to the actual Start screen, and then boot again. I could NEVER predict exactly what triggered this. Also, I tried installing ROMs without GAPPS, and that didn't go well for me (couldn't get any of them to load properly without flashing a GAPPS package for some reason).
Something goofy seems to be happening between Google services and the custom ROMs on this phone. I'm not sure what's triggering it, but given the sheer number of different ROMs I've tried - ALL of which have the EXACT SAME ISSUE - I strongly suspect there is indeed a GAPPS problem lurking somewhere.
As a side note - I reflahsed B322 (restoring from backup) and the phone is again as stable as it has always been.
Is there an EMUI GAPPS package for Marshmallow and/or Nougat (i.e., pulled from Mate 7, 8 or 9) available for download? I'm game for testing.
RE: MT2 boot loop
(*** SEE POST #25 FOR UPDATED FIX!***)
I just noticed this thread, wish I found it earlier. I recently posted my discussion of the boot loop (and fix) here:
https://forum.xda-developers.com/ascend-mate2/orig-development/cm-nougat-mt2-t3478345/page14
Bratzilla was right when he said in his post, "I strongly suspect there is indeed a GAPPS problem lurking somewhere".
Thanks EndlessFall,
please help to check this link: github(dot)com/opengapps/arm/releases/download/20170811/open_gapps-arm-7.1-pico-20170811.zip
no files listed.
RE: dead link for Open GApps previous versions & boot loop fix
Strange, it seems that in the past day Open GApps has purged their GitHub archive. The "Older Releases" button at their website still redirects to the GitHub repo, but it no longer displays any version other than the current one.
As long as it does not violate any policy, I can always post a copy of the Open GApps 08/11/17 ARM 7.1 Pico package.
Although I have not tried other GApps distributions (Delta, Beans, etc), in theory there is no reason why they shouldn't work, as long as Google Play Services is not newer than v11.3.02. I recommend the minimal GApps available. Installing "pico" was an important part of isolating, and simplifying the search for, the culprit.
As I mentioned in my original post, I tested all versions of Google Play Services on apkmirror newer than v11.3.02 (build format 436 for MT2L03), up until 08/26. All newer builds induced an immediate boot loop. A future version may resolve the boot loop issue and work fine on the MT2L03, but it does not seem to be available as of today.
Have been running custom ROMs on my MT2L03 for years. Boot looping problem began for me two weeks ago when I completely wiped/formatted my CandyROMs v7.1.2 06/15 install and flashed MDMower's 08/19 LineageOS. Began digging deep into the cause (knowing MDMower would not release garbage) and discovered the connection to Play Services. Have been running MDMower's LineageOS & CandyROMs v7.1.2 ever since without any issues.
Remember to use MDMower's TWRP v3.1N0-0, it is much more stable on the MT2L03.
Thanks again Endless,
I follow your instruction to flash Candie ROM and the matching GAPP from 6/15, all went well, no more bootloop. I will check the phone from time to time to see if the Loop of death come back, maybe once GAPP get updated it may come back. LOL... hopefully not though.
RE: MT2 boot loop fix (workaround)
Great, hondaman82 - so glad it worked for you. Funny, the exact same environment that you are using (06/15 CandyROMs with the matching 06/15 Open GApps) is what served as my "proof of concept" that current Open GApps with updated Play Services was likely the problem.
Although the proper GApps package resolves the boot loop issue, it is important to point out that it's more of a workaround than a fix. The root cause might be a bug in the AOSP/LineageOS source code itself, preventing MT2L03 compatibility with the latest versions of Play Services.
MDMower has just released a new build of LineageOS dated 08/29/17. I'll continue to test the latest ROMs with the latest GApps & Play Services to see if new commits/updates fix the problem...
hondaman82 said:
Thanks again Endless,
I follow your instruction to flash Candie ROM and the matching GAPP from 6/15, all went well, no more bootloop. I will check the phone from time to time to see if the Loop of death come back, maybe once GAPP get updated it may come back. LOL... hopefully not though.
Click to expand...
Click to collapse
EndlessFall said:
Great, hondaman82 - so glad it worked for you. Funny, the exact same environment that you are using (06/15 CandyROMs with the matching 06/15 Open GApps) is what served as my "proof of concept" that current Open GApps with updated Play Services was likely the problem.
Although the proper GApps package resolves the boot loop issue, it is important to point out that it's more of a workaround than a fix. The root cause might be a bug in the AOSP/LineageOS source code itself, preventing MT2L03 compatibility with the latest versions of Play Services.
MDMower has just released a new build of LineageOS dated 08/29/17. I'll continue to test the latest ROMs with the latest GApps & Play Services to see if new commits/updates fix the problem...
Click to expand...
Click to collapse
Have you had the chance to try 0829 Build of Lineage OS with newer GApps? TIA.
Oh nooo.. the LOD (loop of death) come back, after 3 days of working OK... sigh.... back to EMUI stock
RE: new ROM builds, GApps, & boot loop issue
Yes, I tested MDMower's LineageOS 08/29 last night using the 08/29 Open GApps package. Unfortunately, the boot loop bug persists. However, the 08/29 LineageOS runs great with Open GApps 08/11 and is worth installing (at least for me). Hopefully MDMower will keep up the good work and release a build in the next week or two with the Sept security patch.
I'll continue to test and report back if there is any progress...
MT2-User said:
Have you had the chance to try 0829 Build of Lineage OS with newer GApps? TIA.
Click to expand...
Click to collapse
EndlessFall said:
Yes, I tested MDMower's LineageOS 08/29 last night using the 08/29 Open GApps package. Unfortunately, the boot loop bug persists. However, the 08/29 LineageOS runs great with Open GApps 08/11 and is worth installing. Hopefully MDMower will keep up the good work and release a build in the next week or two with the Sept security patch.
I'll continue to test and report back if there is any progress...
Click to expand...
Click to collapse
Thanks!
RE: return of boot loop
Sorry to hear that Hondaman82.
I can only speak from my own experience, which is that my MT2L03 has been stable for the past 2 weeks using Open GApps pico dated no later than 08/11. It is possible that your Google Play Services was auto-updated to a version newer than v11.3.02 (inducing the loop), but you won't be able to tell because you can't boot the corrupted OS to read the version number in app settings. If my boot loop returns, I'll do an ADB pull from TWRP to examine the Play Services package version (curious to see if there is an update correlation).
Goes to show what I mentioned yesterday, which is that the root cause is likely some incompatibility between the ROMs customized for MT2L03 and Play Services that can only be fixed by a commit to the ROM source code, a script, patch, or change to Play Services.
Let's see what happens, perhaps MDMower would be willing to offer his expertise? I visited Matt's website, GitHub and XDA profile, but it seems difficult to contact him directly....
hondaman82 said:
Oh nooo.. the LOD (loop of death) come back, after 3 days of working OK... sigh.... back to EMUI stock
Click to expand...
Click to collapse
RE: preventing Google Play Services auto-update
(***SEE UPDATED FIX IN POST #25!***)
For those of you willing to experiment further, there is a method that supposedly disables Google Play Services from updating. This might allow you to "lock in" v11.3.02 until there is a proper fix for the boot loop:
https://forum.xda-developers.com/android/help/delete-disable-downgrade-prevent-update-t3091832
Basically, this involves using a root file manager to create two empty folders entitled "com.google.android.gms-1.apk" and "com.google.android.gms-2.apk" in the "\data\app" directory, causing auto-update to fail.
I haven't used this hack, try at your own risk!
Of course, this works off of the assumption that updating Google Play Services beyond v11.3.02 is the only factor involved in the boot loop. I just haven't dug deep enough...
Mine (Candy 0725 build) went into LOD by itself a moment ago
Does anyone have a B322 TWRP backup ZIP? I as of this morning have 2 MT2 phones dead. One went into LOD about 3am and the other about 4am.
About:
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), 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.
Introduction:
This is an unofficial WIP LineageOS thread for the Motorola G7 Power, codename ocean.
We support all the T-Mobile, International, and Project Fi variants, as their bootloaders are unlockable, while we can't support the Verizon and AT&T variants, as their bootloaders are permanently locked.
Changelog:
20200516 (download from Drive) (download from AFH):
Using audio configuration from @Grim truth , which is confirmed to be working
20200514 (build pulled)[/URL]:
Using @Rondeau79's audio stack, which is currently incompatible
20200511 (download):
Builds are now signed. Please wipe data if you're coming from the previous build.
The May security patch has been merged in.
Audio issues have now been eliminated.
Hotspot now works.
Issues:
VoLTE not working prior to May 6 build
[*]Hotspot issues
[*]Garbled call audio on some devices
Headset issues and no audio from local files on May 11 build
ROM:
My Google Drive folder
Android File Host
Make sure to only download the latest build.
Stock Firmware:
Official Firmware
Recovery:
Use whatever recovery you want, but I'm linking OrangeFox (courtesy of @electimon) here
Copy Partitions (To setup slot_b):
copypartitions.zip
(courtesy of @filipepferraz)
GApps:
https://opengapps.org
Pixel GApps (optimized for ocean, Open GApps can have issues)
Preparation for A/B Roms:
Download a custom recovery and the stock firmware for your variant from the links above.
Remove your Google account under Settings > Accounts then factory reset your device, as FRP is enforced.
Unlock your bootloader on Motorola's official site.
Flash your factory firmware image on slot_a.
Hold power + Volume down untill you reach bootloader (fastboot mode).
In your extracted firmware folder, open a terminal or command prompt and flash your firmware files with these commands.
NOTE: This last step installs vendor.img to slot_b as well.
ROM - Installation:
LineageOS 17.1 requires some extra steps to install properly. These instructions are brought to you by @Bernie_nix.
Boot phone into bootloader
From a PC, use one of these command to boot custom recovery (TWRP/oFox). In Linux, use the following command:
Code:
sudo fastboot boot recovery.img
In Windows or macOS, use the following:
Code:
fastboot boot recovery.img
Replace 'recovery.img' with the filename for your recovery image.
If you are coming from stock, install the copy partitions zip after your phone boots into recovery.
In TWRP/oFox go to Wipe - Dalvik/Art Cache, Data, Internal Storage and System.
In TWRP go to the Reboot menu > Switch slots OR in oFox go to the Reboot menu > Switch Slots (press the grey one)
Wipe - Dalvik/Art Cache, Data, Internal Storage and System again.
Reboot into bootloader.
Boot TWRP/oFox with the fastboot command in step 2 above.
Install LineageOS.
Reboot.
It will bootloop 2x, then take you to factory data reset screen. Select Yes. It will reboot into LineageOS. At this point, if you don't want to install anything else, you're done.
Once Lineage boots, if you want to set up GApps, Magisk or another recovery, reboot into recovery mode, install TWRP/oFox, GApps, and/or Magisk.
Reboot into the bootloader and input this.
Code:
fastboot -w
Reboot. You're done.
Updating (AKA 'dirty flash') {do not follow these steps when going from unsigned to signed builds}:
Download the updated ROM.
Reboot to recovery
Install ROM.zip + the recovery, if you're using something other than Lineage Recovery.
Reboot into recovery
Flash gapps + Magisk (if you want)
Reboot into system.
Notes:
Any time your internal storage aka "userdata" is from a stock install you must use 'fastboot -w' to erase it before using any ROM, otherwise it won't boot.
Contributing:
If you have any patches you want to make to the device-specific code, do it at my GitHub, which will be linked at the bottom. I've conveniently pinned all the repositories.
If you want to contribute to LineageOS itself, go to the LineageOS GitHub at https://github.com/LineageOS .
XDA:DevDB Information
LineageOS 17.1, ROM for the Moto G7 Power
Contributors
yagyaxt1068, electimon, erfanoabdi, The people who contributed to LineageOS and the device sources
Source Code: https://github.com/yagyaxt1068
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: LineageOS
Version Information
Status: No Longer Updated
Current Beta Version: 20200516
Beta Release Date: 2020-05-16
Created 2020-05-09
Last Updated 2020-07-05
Nice! I'm looking through the git repos now. What's all this with switching between LineageOS and RevengeOS? Never heard of RevengeOS before.
Edit: Is it possible to keep the stock software installed in slot A, and install this in slot B?
Greek2me said:
Nice! I'm looking through the git repos now. What's all this with switching between LineageOS and RevengeOS? Never heard of RevengeOS before.
Edit: Is it possible to keep the stock software installed in slot A, and install this in slot B?
Click to expand...
Click to collapse
I based my device tree off of @Electimon's Revenge OS device tree.
And, it is possible to keep stock installed in slot A, but slot A would be useless without a data wipe in fastboot.
I'll give it a try sometime soon. Is there anything you need help with? I'm new to Android work, but I can take a stab at it.
edit: Installed, and it's working well for the most part! I'm going to record issues here as I come across them:
moto gestures missing Actually, they are included. There are two menus: one called "Gestures" and one called "Moto Gestures". They're both under the "System" category in settings.
notification LED constantly on battery was fully charged...
Android Setup crashes after agreeing to TOS
Bug Confirmation
Greek2me said:
I'll give it a try sometime soon. Is there anything you need help with? I'm new to Android work, but I can take a stab at it.
edit: Installed, and it's working well for the most part! I'm going to record issues here as I come across them:
moto gestures missing
notification LED constantly on battery was fully charged...
Android Setup crashes after agreeing to TOS
Click to expand...
Click to collapse
I can confirm that Android Setup is crashing. This occurs with both Pico/Nano Gapps. Also, I'm not sure if this is just the nature of Lineage, but after adding a google account, the only sync toggle option is listed as "People details." I am attempting to sync my contacts from my google account but this doesn't seem to be available. This would be under settings > accounts > google > contacts. There are also some frame rate issues, particularly when switching between applications or home screens. There does not seem to be any frame rate issues within the apps themselves, however.
I just want to add that everything I need seems to be working well. I've placed several calls and the quality was as expected. This will probably be my daily driver - nice work!
Bug report....
Installed nicely in Xfinity (Comcast) Phone.
Bug report - Local music files do not play from speaker or plugin headphones. Doesn't matter if stock player or other. (But works with Bluetooth device).
However speaker and plugin headphones work from browser and apps like Spotify.
nomadman1 said:
Installed nicely in Xfinity (Comcast) Phone.
Bug report - Local music files do not play from speaker or plugin headphones. Doesn't matter if stock player or other. (But works with Bluetooth device).
However speaker and plugin headphones work from browser and apps like Spotify.
Click to expand...
Click to collapse
Try updating to the latest build. If the problem persists, let me know.
Hello all! Considering upgrading to the G7 Power and replacing my aging LG V20 and throwing LOS on it. One single question: Does your LOS support WiFi Calling, and do other ROMs? This is the single factor forcing me off my beloved old tank, I moved to the middle of nowhere and I don't have any signal, and my only option is VoLTE and WiFI Calling, neither of which is supported in LOS on the V20.
Thanks so much for your work!
vectorvitale said:
Hello all! Considering upgrading to the G7 Power and replacing my aging LG V20 and throwing LOS on it. One single question: Does your LOS support WiFi Calling, and do other ROMs? This is the single factor forcing me off my beloved old tank, I moved to the middle of nowhere and I don't have any signal, and my only option is VoLTE and WiFI Calling, neither of which is supported in LOS on the V20.
Thanks so much for your work!
Click to expand...
Click to collapse
Most ROMs (including this one) support WiFi calling. I've tested it myself.
Sent from my moto g(7) power using Tapatalk
I'm not sure if this is just me, but wired headphones/mic don't seem to work while on a call. The audio still comes through the phone speakers.
Please note that I'm still on the May 6th build.
Greek2me said:
I'm not sure if this is just me, but wired headphones/mic don't seem to work while on a call. The audio still comes through the phone speakers.
Please note that I'm still on the May 6th build.
Click to expand...
Click to collapse
It's an issue on the May 11 build as well.
Sent from my moto g(7) power using Tapatalk
Glad you can confirm. Location services also seem to be nonfunctional at the moment.
I installed the latest build (May 14th) on my device and all audio output is now broken (including calls). I have a XT1955-2.
edit: I flashed the May 11th build over the top and audio is working again.
My Moto_G7_XT1955-5_ ocean is mute completely with May 14th build.
bluetooth speakers work.
fastness said:
My Moto_G7_XT1955-5_ ocean is mute completely with May 14th build.
bluetooth speakers work.
Click to expand...
Click to collapse
That was part of a test to see if there were audio issues. It will be reverted eventually.
Greek2me said:
Glad you can confirm. Location services also seem to be nonfunctional at the moment.
Click to expand...
Click to collapse
I'm on the May 11 build and my GPS locks faster than it ever has and it's very accurate on my device. I'd even go so far as to say its faster than stock. I haven't used maps ever on my 1955-5 except on rare occasions when testing a rom but when I saw your location is off post I flipped on location tile opened Google maps and probably 2 seconds after that the dot showed just outside my bedroom window at my house. Going to run a few tests now and see what the outcome is just for kicks but seems good on my end on the May 11th build.
Yes, location is working now on the May 11th build.
I'm not sure if this is the fault of the OS, but my SMS messages are being received late and in batches. It seems that I sometimes don't receive SMS messages until I unlock the phone and open the Messages app. Is anyone else experiencing that?
Greek2me said:
Yes, location is working now on the May 11th build.
I'm not sure if this is the fault of the OS, but my SMS messages are being received late and in batches. It seems that I sometimes don't receive SMS messages until I unlock the phone and open the Messages app. Is anyone else experiencing that?
Click to expand...
Click to collapse
I get that now and I'm not rooted yet
The night light / blue light filter doesn't seem to work in the May 11th build.