[DISCONTINUED][ROM][UNOFFICIAL][OCEAN]Lineage OS 16.0

Search This thread

SyberHexen

Senior Member
https%3A%2F%2Fi.imgur.com%2F2okPze5.png

Code:
/*
 * Your warranty is now void.
 *
 * I am not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this ROM
 * before flashing it! YOU are choosing to make these modifications,
 */

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 the unofficial Lineage OS 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.


ROM:
lineage-16.0-20191001-UNOFFICIAL-ocean.zip
Stock Firmware:
Official Firmware
Recovery:
Unofficial TWRP
Copy Partitions: (To setup slot_b)
copypartitions.zip
(courtesy of @filipepferraz)
Open GApps:
http://opengapps.org

Preparation for A/B Roms:
01. Download TWRP and the Firmware for your variant from the links above.
02. Remove your google account under Settings > Accounts then factory reset your device as FRP is enforced.
03. Unlock your bootloader Instructions here.
04. 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 and flash your firmware files with these commands.
  • NOTE: This last step installs vendor.img to slot_b as well.
05. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
06. While on Slot_A Flash copypartitions.zip (This step only needs to be completed Once only after updating from stock factory firmwares.)
07. While in TWRP choose Reboot > bootloader
08. Now you're ready for ROM Steps below

ROM - Installation:
01. Download the ROM, TWRP and GApps from the links above.
02. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
03. Flash ROM.zip + TWRP_installer/boot.img ramdisk method
04. Reboot > Recovery
05. Install Gapps + Magisk (if you choose)
06. Reboot > System

Updating (AKA 'dirty flash'):
01. Download the updated ROM
02. fasboot boot twrp.img
03. Install ROM.zip + TWRP_installer/boot.img ramdisk method
04. Reboot > Recovery
05. flash gapps + Magisk (if you choose)
06. Reboot > System

Notes:
Any time your internal storage aka "Userdata" is from a stock install you must use 'fastboot -w' to erase it before using ROMS


XDA:DevDB Information
Lineage OS 16.0, ROM for the Moto G7 Power, ROM for the Moto G7 Power

Contributors
SyberHexen, erfanoabdi, LineageOS Team
Source Code:
[url]https://github.com/LineageOS[/URL]
android_kernel_motorola_msm8953
android_device_motorola_river_prebuiltvendor

ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Stock Vendor.img

Version Information
Status: Testing

Created 2019-09-18
Last Updated 2019-10-01
 
Last edited:

jhjhjhjhjhjh

Senior Member
Mar 14, 2017
386
177
Thanks for the rom. Do you know if the Moto gestures work? Like chop twice for camera....

EDiT..
Yes moto actions are included in this ROM. Awesome job. Buttery smooth so far. Nice attentive display. LTE+ I see now in the status bar. No issues to report yet.
Just to root. Flashing magisk from twrp won't boot system. I had to back up the boot.emmc.win from twrp and use the install via patch boot method. Bam rooted on Lineage OS.
I'll report if any issues should arrive. So far Great ROM.:)

Make sure you fastboot flash your stock firmware first.
 

Attachments

  • Screenshot_20190919-001248_Trebuchet.png
    Screenshot_20190919-001248_Trebuchet.png
    237.8 KB · Views: 2,464
Last edited:

ViRUS2015

Member
Dec 23, 2014
25
18
YES! I've been waiting for this since I bought the phone, and had almost given up all hope seeing the lack of activity in the forums for this device. While I'm far from an Android dev, I'll get to tinkering with the unofficial TWRP port and with this ROM during the weekend and will let you know how well it goes :)

Thank you!
 
  • Like
Reactions: ziusudra

ddougg

Member
Sep 13, 2016
12
3
Thank You , Awesome answered prayer overnight. As an inept tinkerer I typically brick phones or have days of migraines attempting this sort of upgrade but your guide may be almost idiot proof. Working for me at least, only snafu was flashing the ROM , I guess my phone wanted partitions mounted first as I got the " Not enough space in Data or System " error. Persistence a reread of guide and another prayer put me over the top. I went from soft-bricked to rooted linage in minutes. XDA rocks ! Peace
 

jhjhjhjhjhjh

Senior Member
Mar 14, 2017
386
177
Does VoLTE work? If the camera, Bluetooth, and VoLTE work I'm installing it.

Everything works on my variant. Retail...Im not going back to stock.
So smooth no bloatware. An option in settings you can turn off all animations besides the settings in developer options. This phone flies with impressive battery life. The bugs are very minimal. Like i use LG tone Bluetooth headsets and when i get a text it takes 7 seconds to read out loud. On stock it was 2 seconds before my texts would be read. I noticed on you tube vance the 720 p streaming sometimes gives a slight second blur. Other than these two bugs. The rom is near prefect.
 
  • Like
Reactions: ziusudra

arolust

Member
Feb 19, 2014
34
4
Works.

Been experimenting with it to see if the rom allows simple bypassing of the Metropcs sim lock. So far no luck. Keep in mind I dont have a working sim card for it, and am attempting to have a standard lte t-mobile sim work.

Also experiencing an issue with the screen colors going bonkers randomly, requiring restart (or two) to fix. Not sure if this is a device issue, a screw up during flashing, or a rom issue (keep in mind this was a phone only rarely messed with, not a daily driver).
 

jhjhjhjhjhjh

Senior Member
Mar 14, 2017
386
177
Works.

Been experimenting with it to see if the rom allows simple bypassing of the Metropcs sim lock. So far no luck. Keep in mind I dont have a working sim card for it, and am attempting to have a standard lte t-mobile sim work.

Also experiencing an issue with the screen colors going bonkers randomly, requiring restart (or two) to fix. Not sure if this is a device issue, a screw up during flashing, or a rom issue (keep in mind this was a phone only rarely messed with, not a daily driver).

Just fyi, there is no way at this time to bypass a sim network unlock simply by using another software.
Sim unlock is a Carrier Remote over the air network in which requires a program to unlock. (imei) Only carriers or sim unlock service's like on ebay can achieve this with a fee of course.. older phones which dont have an unlock app may have been able to sim unlock using a third party tool but that was ages ago.

Average sim unlock cost for newer devices $35 u s dollars. older phone's around $10 u s dollars.
Metro by T-Mobile unlocks for free after 180 days of service.

Hope one stops thinking sim unlock is free.

Buying a phone from a carrier will be sim locked automatically. Buying the same phone that can be bought in different regions and is not exclusive to any carrier will be sim UnLocked. Buy non- carrier branded phones in the future to avoid being stuck to one carrier. (Amazon,Ebay and BestBuy)
 
Last edited:

kry52

Member
May 18, 2019
18
1
Is it possible to bring the stock firmware back via fastboot in case I face any problems with the ROM? Is the procedure ordinary?
 

binocerino

New member
Sep 20, 2019
2
0
weird colours

Mostly it works, but the screen behaves strangely...

The colours are messed up, it looks a bit like if it was using 16 colours, and there are some horizontal lines close to the top and to the bottom of the screen.

I've tried to take a screenshot, for showing you, but on the screenshot the colours are fine :confused:

I've tried also AOSP Pie, and there the colours are ok.

My device is XT1955-4 retail EU

Anyone else is experiencing my problems?
Can I help debug somehow?
 

jhjhjhjhjhjh

Senior Member
Mar 14, 2017
386
177
The benefits of this rom I like:

No Bloatware
Fluid , fast and responsive
More data options on Metro by T-Mobile. I get HSDA+ and LTE+ always. Stock i hardly saw anything but LTE and HSDPA only.
Selinux off by default with init.d support.
Near Stock Pie experience.

---------- Post added at 05:58 PM ---------- Previous post was at 05:55 PM ----------

Mostly it works, but the screen behaves strangely...

The colours are messed up, it looks a bit like if it was using 16 colours, and there are some horizontal lines close to the top and to the bottom of the screen.

I've tried to take a screenshot, for showing you, but on the screenshot the colours are fine :confused:

I've tried also AOSP Pie, and there the colours are ok.

My device is XT1955-4 retail EU

Anyone else is experiencing my problems?
Can I help debug somehow?

Unfortunately, I dont have a color issue.
I use color changer pro for this phone because how dull the colors are. So my screen is great
I saw a color changer option in the settings you can tinker with to get your colors the way you like it.

(Under Live display)
I have mines set to sRGB
DPI set to 420. wink wink...

---------- Post added at 06:06 PM ---------- Previous post was at 05:58 PM ----------

Is it possible to bring the stock firmware back via fastboot in case I face any problems with the ROM? Is the procedure ordinary?

Of course

---------- Post added at 06:10 PM ---------- Previous post was at 06:06 PM ----------

One more thing my chop to flash is faster because I was now able to disable the vibration. Yes this phone is flying higher guys..
 

Attachments

  • Screenshot_20190920-101852_Settings.png
    Screenshot_20190920-101852_Settings.png
    89.2 KB · Views: 1,197
  • Screenshot_20190920-101953_LineageOS_Settings.png
    Screenshot_20190920-101953_LineageOS_Settings.png
    64.3 KB · Views: 1,177
  • Screenshot_20190920-102005_LineageOS_Settings.png
    Screenshot_20190920-102005_LineageOS_Settings.png
    68.2 KB · Views: 1,146
  • Screenshot_20190920-102400_Color_Changer_Pro.jpg
    Screenshot_20190920-102400_Color_Changer_Pro.jpg
    69.9 KB · Views: 1,128
Last edited:

75lick

Member
Mar 1, 2013
6
0
I can't install gapps says insufficient storage. When I check the size of the system partition it says 4mb.

Edit: I fixed this somehow so nvm
 
Last edited:

ViRUS2015

Member
Dec 23, 2014
25
18
Hey!

So, I tried installing this, and I've encountered a roadblock. I think I've got all the steps from "Preparation for A/B Roms" category right, my issue appears when actually flashing the LOS zip file. When I'm on TWRP and I go ahead and try to Install the ZIP, it simply stops after "Done processing script file" (after both steps of Checking for Digest file... are complete) but actually there's nothing on the internal memory of the phone. This means that after rebooting, I only get a bootloop on the "bootloader unlocked" warning screen.

Some things to note:
I've copied all required files to the microSD card on my phone, and I'm trying to install everything from there.
I've been doing all the TWRP stuff from the CMD prompt in Windows using ADB because for some reason the touchscreen won't work on my phone while using the unofficial port of TWRP.

I've copied a log file from my console right after step 6 of the preparation, that is, flashing copy-partitions-payton.zip up to where I get stuck, in case this is helpful to help whoever wants to lend me a hand with this :)

Code:
G:\Cosas\Android\platform-tools>adb shell
ocean:/ # twrp
TWRP openrecoveryscript command line tool, TWRP version 3.3.1-0

Allows command line usage of TWRP via openrecoveryscript commands.
Some common commands include:
  install /path/to/update.zip
  backup <SDCRBAEM> [backupname]
  restore <SDCRBAEM> [backupname]
  wipe <partition name>
  sideload
  set <variable> [value]
  decrypt <password>
  remountrw
  fixperms
  mount <path>
  unmount <path>
  print <value>
  mkdir <directory>
  reboot [recovery|poweroff|bootloader|download|edl]

See more documentation at https://twrp.me/faq/openrecoveryscript.html

ocean:/ # twrp install /external_sd/copy-partitions-payton.zip
Installing zip file '/external_sd/copy-partitions-payton.zip'
Checking for Digest file...

Partition aboot_a
3072+0 records in
3072+0 records out
1572864 bytes transferred in 0.270 secs (5825422 bytes/sec)
Partition cmnlib64_a
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.070 secs (14979657 bytes/sec)
Partition cmnlib_a
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.069 secs (15196753 bytes/sec)
Partition devcfg_a
128+0 records in
128+0 records out
65536 bytes transferred in 0.005 secs (13107200 bytes/sec)
Partition dsp_a
32768+0 records in
32768+0 records out
16777216 bytes transferred in 1.079 secs (15548856 bytes/sec)
Partition dtbo_a
16384+0 records in
16384+0 records out
8388608 bytes transferred in 0.525 secs (15978300 bytes/sec)
Partition fsg_a
24576+0 records in
24576+0 records out
12582912 bytes transferred in 0.792 secs (15887515 bytes/sec)
Partition keymaster_a
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.071 secs (14768676 bytes/sec)
Partition logo_a
32768+0 records in
32768+0 records out
16777216 bytes transferred in 1.008 secs (16644063 bytes/sec)
Partition modem_a
204800+0 records in
204800+0 records out
104857600 bytes transferred in 6.427 secs (16315170 bytes/sec)
Partition prov_a
384+0 records in
384+0 records out
196608 bytes transferred in 0.013 secs (15123692 bytes/sec)
Partition rpm_a
512+0 records in
512+0 records out
262144 bytes transferred in 0.018 secs (14563555 bytes/sec)
Partition sbl1_a
1024+0 records in
1024+0 records out
524288 bytes transferred in 0.039 secs (13443282 bytes/sec)
Partition tz_a
3584+0 records in
3584+0 records out
1835008 bytes transferred in 0.116 secs (15819034 bytes/sec)
Partition vbmeta_a
128+0 records in
128+0 records out
65536 bytes transferred in 0.004 secs (16384000 bytes/sec)

[OK]

Done processing script file

ocean:/ # twrp reboot bootloader
Done processing script file
ocean:/ #

G:\Cosas\Android\platform-tools>fastboot -w
Erasing 'userdata'                                 OKAY [  0.180s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata'                                 (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed

G:\Cosas\Android\platform-tools>fastboot boot twrp-3.3.1-0-ocean-20190904-0715.img
Sending 'boot.img' (25554 KB)                      OKAY [  0.545s]
Booting                                            OKAY [  0.730s]
Finished. Total time: 1.301s

G:\Cosas\Android\platform-tools>adb shell
ocean:/ # twrp install /external_sd/lineage-16.0-20190918-UNOFFICIAL-ocean.zip
Installing zip file '/external_sd/lineage-16.0-20190918-UNOFFICIAL-ocean.zip'
Checking for Digest file...
Step 1/2Step 2/2Done processing script file
ocean:/ #

The good thing is that I was able to recover the original system image from the lolinet file I downloaded, so my phone is fully functional and ready to give it another go hehe.

Any help will be more than welcome. I'll try giving it another go on my own during the weekend.
 

jhjhjhjhjhjh

Senior Member
Mar 14, 2017
386
177
Hey!

So, I tried installing this, and I've encountered a roadblock. I think I've got all the steps from "Preparation for A/B Roms" category right, my issue appears when actually flashing the LOS zip file. When I'm on TWRP and I go ahead and try to Install the ZIP, it simply stops after "Done processing script file" (after both steps of Checking for Digest file... are complete) but actually there's nothing on the internal memory of the phone. This means that after rebooting, I only get a bootloop on the "bootloader unlocked" warning screen.

Some things to note:
I've copied all required files to the microSD card on my phone, and I'm trying to install everything from there.
I've been doing all the TWRP stuff from the CMD prompt in Windows using ADB because for some reason the touchscreen won't work on my phone while using the unofficial port of TWRP.

I've copied a log file from my console right after step 6 of the preparation, that is, flashing copy-partitions-payton.zip up to where I get stuck, in case this is helpful to help whoever wants to lend me a hand with this :)

Code:
G:\Cosas\Android\platform-tools>adb shell
ocean:/ # twrp
TWRP openrecoveryscript command line tool, TWRP version 3.3.1-0

Allows command line usage of TWRP via openrecoveryscript commands.
Some common commands include:
  install /path/to/update.zip
  backup <SDCRBAEM> [backupname]
  restore <SDCRBAEM> [backupname]
  wipe <partition name>
  sideload
  set <variable> [value]
  decrypt <password>
  remountrw
  fixperms
  mount <path>
  unmount <path>
  print <value>
  mkdir <directory>
  reboot [recovery|poweroff|bootloader|download|edl]

See more documentation at https://twrp.me/faq/openrecoveryscript.html

ocean:/ # twrp install /external_sd/copy-partitions-payton.zip
Installing zip file '/external_sd/copy-partitions-payton.zip'
Checking for Digest file...

Partition aboot_a
3072+0 records in
3072+0 records out
1572864 bytes transferred in 0.270 secs (5825422 bytes/sec)
Partition cmnlib64_a
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.070 secs (14979657 bytes/sec)
Partition cmnlib_a
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.069 secs (15196753 bytes/sec)
Partition devcfg_a
128+0 records in
128+0 records out
65536 bytes transferred in 0.005 secs (13107200 bytes/sec)
Partition dsp_a
32768+0 records in
32768+0 records out
16777216 bytes transferred in 1.079 secs (15548856 bytes/sec)
Partition dtbo_a
16384+0 records in
16384+0 records out
8388608 bytes transferred in 0.525 secs (15978300 bytes/sec)
Partition fsg_a
24576+0 records in
24576+0 records out
12582912 bytes transferred in 0.792 secs (15887515 bytes/sec)
Partition keymaster_a
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.071 secs (14768676 bytes/sec)
Partition logo_a
32768+0 records in
32768+0 records out
16777216 bytes transferred in 1.008 secs (16644063 bytes/sec)
Partition modem_a
204800+0 records in
204800+0 records out
104857600 bytes transferred in 6.427 secs (16315170 bytes/sec)
Partition prov_a
384+0 records in
384+0 records out
196608 bytes transferred in 0.013 secs (15123692 bytes/sec)
Partition rpm_a
512+0 records in
512+0 records out
262144 bytes transferred in 0.018 secs (14563555 bytes/sec)
Partition sbl1_a
1024+0 records in
1024+0 records out
524288 bytes transferred in 0.039 secs (13443282 bytes/sec)
Partition tz_a
3584+0 records in
3584+0 records out
1835008 bytes transferred in 0.116 secs (15819034 bytes/sec)
Partition vbmeta_a
128+0 records in
128+0 records out
65536 bytes transferred in 0.004 secs (16384000 bytes/sec)

[OK]

Done processing script file

ocean:/ # twrp reboot bootloader
Done processing script file
ocean:/ #

G:\Cosas\Android\platform-tools>fastboot -w
Erasing 'userdata'                                 OKAY [  0.180s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata'                                 (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed

G:\Cosas\Android\platform-tools>fastboot boot twrp-3.3.1-0-ocean-20190904-0715.img
Sending 'boot.img' (25554 KB)                      OKAY [  0.545s]
Booting                                            OKAY [  0.730s]
Finished. Total time: 1.301s

G:\Cosas\Android\platform-tools>adb shell
ocean:/ # twrp install /external_sd/lineage-16.0-20190918-UNOFFICIAL-ocean.zip
Installing zip file '/external_sd/lineage-16.0-20190918-UNOFFICIAL-ocean.zip'
Checking for Digest file...
Step 1/2Step 2/2Done processing script file
ocean:/ #

The good thing is that I was able to recover the original system image from the lolinet file I downloaded, so my phone is fully functional and ready to give it another go hehe.

Any help will be more than welcome. I'll try giving it another go on my own during the weekend.

I had a snafu because i tried to install the rom using the TWRP already installed and I was rooted with xposed.
You must start from scratch before flashing. The OP's directions were spot on if you follow to the T.
The TWRP in the OP is important and I notice in TWRP im on slot _b.

Hope this helps ya..
 
  • Like
Reactions: amerock

ViRUS2015

Member
Dec 23, 2014
25
18
I had a snafu because i tried to install the rom using the TWRP already installed and I was rooted with xposed.
You must start from scratch before flashing. The OP's directions were spot on if you follow to the T.

Nope, in my case I had the phone fully stock before trying this. I did the whole preparation first anyway, removed my Google Account from the device and factory reset it, then flashed the downloaded factory firmware image as instructed in step 04 with the console commands in dogbin.

The TWRP in the OP is important and I notice in TWRP im on slot _b.

Hope this helps ya..

I'm using TWRP-ocean-test-1 from the thread OP linked. I can't use the exact one posted by the OP in that other thread since for some reason the touchscreen doesn't work with it.

By the way, how did you end up in slot_b on TWRP? Unless I'm missing something, in no step the OP says to change to that slot during the preparation or installation steps :/

--------------

Also, I just tried starting everything from scratch. Before going to bed last night, I reflashed the original factory image I downloaded from lolinet only to install WhatsApp and use the alarm. This morning, I re-did everything carefully and got logs at every stage, here they are:

Stage 1: These are steps 4 and 5 of the preparation. I removed my Google Account and factory reset the device, then I rebooted into fastboot and began entering the commands from the dogbin page. As far as I can tell, the console shows no errors at this stage.

Code:
Microsoft Windows [Versión 10.0.18362.356]
(c) 2019 Microsoft Corporation. Todos los derechos reservados.

C:\Windows\system32>cd G:\Cosas\Android

C:\Windows\system32>G:

G:\Cosas\Android>fastboot set_active a
Setting current slot to 'a'                        (bootloader) Slot already set active
OKAY [  0.001s]
Finished. Total time: 0.004s

G:\Cosas\Android>fastboot reboot-bootloader
Rebooting into bootloader                          OKAY [  0.000s]
Finished. Total time: 0.001s

G:\Cosas\Android>fastboot getvar max-sparse-size
max-sparse-size: 268435456
Finished. Total time: 0.000s

G:\Cosas\Android>fastboot oem fb_mode_set
                                                   OKAY [  0.003s]
Finished. Total time: 0.005s

G:\Cosas\Android>fastboot flash partition gpt.bin
(bootloader) is-logical:partition: not found
Sending 'partition' (45 KB)                        OKAY [  0.169s]
Writing 'partition'                                (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [  0.084s]
Finished. Total time: 0.260s

G:\Cosas\Android>fastboot flash bootloader bootloader.img
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (7419 KB)                     OKAY [  0.340s]
Writing 'bootloader'                               (bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib_30.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64_30.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster64.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [  0.324s]
Finished. Total time: 0.678s

G:\Cosas\Android>fastboot reboot-bootloader
Rebooting into bootloader                          OKAY [  0.001s]
Finished. Total time: 0.002s

G:\Cosas\Android>fastboot flash modem_a NON-HLOS.bin
(bootloader) is-logical:modem_a: not found
Sending 'modem_a' (65396 KB)                       OKAY [  1.585s]
Writing 'modem_a'                                  OKAY [  0.505s]
Finished. Total time: 2.125s

G:\Cosas\Android>fastboot flash fsg_a fsg.mbn
(bootloader) is-logical:fsg_a: not found
Sending 'fsg_a' (11684 KB)                         OKAY [  0.421s]
Writing 'fsg_a'                                    OKAY [  0.092s]
Finished. Total time: 0.533s

G:\Cosas\Android>fastboot flash dsp_a adspso.bin
(bootloader) is-logical:dsp_a: not found
Sending 'dsp_a' (16384 KB)                         OKAY [  0.521s]
Writing 'dsp_a'                                    OKAY [  0.105s]
Finished. Total time: 0.648s

G:\Cosas\Android>fastboot flash logo_a logo.bin
(bootloader) is-logical:logo_a: not found
Sending 'logo_a' (1285 KB)                         OKAY [  0.196s]
Writing 'logo_a'                                   OKAY [  0.045s]
Finished. Total time: 0.251s

G:\Cosas\Android>fastboot flash boot_a boot.img
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (32768 KB)                        OKAY [  0.937s]
Writing 'boot_a'                                   (bootloader) Image signed with key bad key
OKAY [  0.633s]
Finished. Total time: 1.604s

G:\Cosas\Android>fastboot flash dtbo_a dtbo.img
(bootloader) is-logical:dtbo_a: not found
Sending 'dtbo_a' (1760 KB)                         OKAY [  0.206s]
Writing 'dtbo_a'                                   OKAY [  0.043s]
Finished. Total time: 0.258s

G:\Cosas\Android>fastboot flash vendor_a vendor.img_sparsechunk.0
(bootloader) is-logical:vendor_a: not found
Sending 'vendor_a' (259120 KB)                     OKAY [  5.780s]
Writing 'vendor_a'                                 OKAY [  1.368s]
Finished. Total time: 7.261s

G:\Cosas\Android>fastboot flash vendor_a vendor.img_sparsechunk.1
(bootloader) is-logical:vendor_a: not found
Sending 'vendor_a' (147628 KB)                     OKAY [  3.359s]
Writing 'vendor_a'                                 OKAY [  0.685s]
Finished. Total time: 4.112s

G:\Cosas\Android>fastboot flash vendor_b vendor.img_sparsechunk.0
(bootloader) is-logical:vendor_b: not found
Sending 'vendor_b' (259120 KB)                     OKAY [  5.775s]
Writing 'vendor_b'                                 OKAY [  1.365s]
Finished. Total time: 7.253s

G:\Cosas\Android>fastboot flash vendor_b vendor.img_sparsechunk.1
(bootloader) is-logical:vendor_b: not found
Sending 'vendor_b' (147628 KB)                     OKAY [  3.362s]
Writing 'vendor_b'                                 OKAY [  0.689s]
Finished. Total time: 4.119s

G:\Cosas\Android>fastboot flash oem_a oem.img
(bootloader) is-logical:oem_a: not found
Sending 'oem_a' (103016 KB)                        OKAY [  2.402s]
Writing 'oem_a'                                    OKAY [  0.507s]
Finished. Total time: 2.962s

G:\Cosas\Android>fastboot flash oem_b oem.img
(bootloader) is-logical:oem_b: not found
Sending 'oem_b' (103016 KB)                        OKAY [  2.407s]
Writing 'oem_b'                                    OKAY [  0.523s]
Finished. Total time: 2.981s

G:\Cosas\Android>fastboot oem fb_mode_clear
                                                   OKAY [  0.002s]
Finished. Total time: 0.003s

G:\Cosas\Android>fastboot reboot-bootloader
Rebooting into bootloader                          OKAY [  0.001s]
Finished. Total time: 0.002s

G:\Cosas\Android>fastboot boot TWRP-ocean-test-1.img
Sending 'boot.img' (27138 KB)                      OKAY [  0.579s]
Booting                                            OKAY [  0.732s]
Finished. Total time: 1.336s

G:\Cosas\Android>

Now I'm in TWRP, instead of using the interface on my phone, I used ADB Shell to flash copypartitions to gather the logs. Here I flash copy-partitions-payton.zip while on Slot_A as instructed (I checked by going to "Reboot" in TWRP, and it says "Current Slot: A" at the bottom, so I know I'm using the correct one). Here's where the first issues appear. I check the log in TWRP and it says at the top in red:

Code:
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/data' (Invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
MTP Enabled

I proceed anyway, and install copy-partitions-payton.zip.

Code:
Microsoft Windows [Versión 10.0.18362.356]
(c) 2019 Microsoft Corporation. Todos los derechos reservados.

C:\Windows\system32>cd G:\Cosas\Android

C:\Windows\system32>G:

G:\Cosas\Android>adb shell
ocean:/ # twrp install /external_sd/copy-partitions-payton.zip
Installing zip file '/external_sd/copy-partitions-payton.zip'
Checking for Digest file...

Partition aboot_a
3072+0 records in
3072+0 records out
1572864 bytes transferred in 0.266 secs (5913022 bytes/sec)
Partition cmnlib64_a
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.071 secs (14768676 bytes/sec)
Partition cmnlib_a
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.071 secs (14768676 bytes/sec)
Partition devcfg_a
128+0 records in
128+0 records out
65536 bytes transferred in 0.006 secs (10922666 bytes/sec)
Partition dsp_a
32768+0 records in
32768+0 records out
16777216 bytes transferred in 1.135 secs (14781688 bytes/sec)
Partition dtbo_a
16384+0 records in
16384+0 records out
8388608 bytes transferred in 0.531 secs (15797755 bytes/sec)
Partition fsg_a
24576+0 records in
24576+0 records out
12582912 bytes transferred in 0.806 secs (15611553 bytes/sec)
Partition keymaster_a
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.072 secs (14563555 bytes/sec)
Partition logo_a
32768+0 records in
32768+0 records out
16777216 bytes transferred in 1.053 secs (15932778 bytes/sec)
Partition modem_a
204800+0 records in
204800+0 records out
104857600 bytes transferred in 6.565 secs (15972216 bytes/sec)
Partition prov_a
384+0 records in
384+0 records out
196608 bytes transferred in 0.015 secs (13107200 bytes/sec)
Partition rpm_a
512+0 records in
512+0 records out
262144 bytes transferred in 0.018 secs (14563555 bytes/sec)
Partition sbl1_a
1024+0 records in
1024+0 records out
524288 bytes transferred in 0.040 secs (13107200 bytes/sec)
Partition tz_a
3584+0 records in
3584+0 records out
1835008 bytes transferred in 0.119 secs (15420235 bytes/sec)
Partition vbmeta_a
128+0 records in
128+0 records out
65536 bytes transferred in 0.006 secs (10922666 bytes/sec)

[OK]

Updating partition details...
Failed to mount '/data' (Invalid argument)
Done processing script file
ocean:/ #
G:\Cosas\Android>

Then I go to Reboot > Bootloader in TWRP. I get a warning that no OS is installed, but I swipe to reboot anyway and proceed using the -w command in fastboot.

Code:
Microsoft Windows [Versión 10.0.18362.356]
(c) 2019 Microsoft Corporation. Todos los derechos reservados.

C:\Windows\system32>cd G:\Cosas\Android

C:\Windows\system32>G:

G:\Cosas\Android>fastboot -w
Erasing 'userdata'                                 OKAY [  0.149s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata'                                 (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed

G:\Cosas\Android>

Here I still get some errors about metadata and some permissions denied, maybe some of these errors are the cause of my problems?

In any case, I keep on going and reboot to TWRP again using the Windows console.

Code:
Microsoft Windows [Versión 10.0.18362.356]
(c) 2019 Microsoft Corporation. Todos los derechos reservados.

C:\Windows\system32>cd G:\Cosas\Android

C:\Windows\system32>G:

G:\Cosas\Android>fastboot boot TWRP-ocean-test-1.img
Sending 'boot.img' (27138 KB)                      OKAY [  0.578s]
Booting                                            OKAY [  0.731s]
Finished. Total time: 1.335s

G:\Cosas\Android>

Now in TWRP, I proceed to install the ROM zip + TWRP on Ramdisk as instructed in Step 3 of "ROM - Installation". Needless to say, the errors about /data are still present when TWRP boots up.

Code:
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/data' (Invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
MTP Enabled

Code:
Microsoft Windows [Versión 10.0.18362.356]
(c) 2019 Microsoft Corporation. Todos los derechos reservados.

C:\Windows\system32>cd G:\Cosas\Android

C:\Windows\system32>G:

G:\Cosas\Android>adb shell
ocean:/ # twrp install /external_sd/lineage-16.0-20190918-UNOFFICIAL-ocean.zip
Installing zip file '/external_sd/lineage-16.0-20190918-UNOFFICIAL-ocean.zip'
Checking for Digest file...
Step 1/2Step 2/2Done processing script file
ocean:/ #

Then I install TWRP to ramdisk going to Advanced > Install Recovery Ramdisk and choosing TWRP-ocean-test-1.img from my microSD card. Now I also get an error regarding /system in TWRP's log.

Code:
Unpacking Boot...
Backing up Boot...
Unpacking /external_sd/TWRP-ocean-test-1.img...
Repacking Boot...
[IMAGE FLASH STARTED]
Image to flash: '/tmp/repackorig/new-boot.img'
Calculating restore details...
[IMAGE FLASH COMPLETED]
Updating partition details...
Failed to mount '/data' (Invalid argument)
Failed to mount '/system' (Permission denied)
...done
Backing up Boot...
[IMAGE FLASH STARTED]
Image to flash: '/tmp/repackorig/new-boot.img'
Calculating restore details...
[IMAGE FLASH COMPLETED]
Updating partition details...
Failed to mount '/data' (Invalid argument)
...done

Now I go to Reboot > Recovery in TWRP. I still get a warning saying that no OS is installed, but I reboot anyway and I succesfully get into TWRP again. I try to install OpenGapps but I get an error 70 complaining that there's no enough space in System partition. If I reboot my phone to system, I get into a bootloop on the bootloader unlocked warning.

Thank you in advance to anyone willing to help me out! Surely I'm missing something trivial due to lack of experience. I've flashed many ROMS before, but this is my first time giving it a try since the A/B partition stuff was implemented :silly:
 

jhjhjhjhjhjh

Senior Member
Mar 14, 2017
386
177
Thank you in advance to anyone willing to help me out! Surely I'm missing something trivial due to lack of experience. I've flashed many ROMS before, but this is my first time giving it a try since the A/B partition stuff was implemented :silly:[/QUOTE]

Okay i do recall i had to format data so i could mount all partions. The copy partitions zip has to be flashed in the twrp of the o.p

In regards to me being on slot_b. the copy partiitions zip accomplished that part. The rom is flashed on slot_b. The O. P TWRP is needed. You keep using the wrong TWRP.
 

ddougg

Member
Sep 13, 2016
12
3
Homie as soon as TWRP installed you gotta format data where you type "yes" and reboot recovery or you end up fubared in loops or worse. Follow steps exactly...
 
  • Like
Reactions: ViRUS2015

Top Liked Posts

  • There are no posts matching your filters.
  • 21
    https%3A%2F%2Fi.imgur.com%2F2okPze5.png

    Code:
    /*
     * Your warranty is now void.
     *
     * I am not responsible for bricked devices, dead SD cards,
     * thermonuclear war, or you getting fired because the alarm app failed. Please
     * do some research if you have any concerns about features included in this ROM
     * before flashing it! YOU are choosing to make these modifications,
     */

    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 the unofficial Lineage OS 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.


    ROM:
    lineage-16.0-20191001-UNOFFICIAL-ocean.zip
    Stock Firmware:
    Official Firmware
    Recovery:
    Unofficial TWRP
    Copy Partitions: (To setup slot_b)
    copypartitions.zip
    (courtesy of @filipepferraz)
    Open GApps:
    http://opengapps.org

    Preparation for A/B Roms:
    01. Download TWRP and the Firmware for your variant from the links above.
    02. Remove your google account under Settings > Accounts then factory reset your device as FRP is enforced.
    03. Unlock your bootloader Instructions here.
    04. 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 and flash your firmware files with these commands.
    • NOTE: This last step installs vendor.img to slot_b as well.
    05. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
    06. While on Slot_A Flash copypartitions.zip (This step only needs to be completed Once only after updating from stock factory firmwares.)
    07. While in TWRP choose Reboot > bootloader
    08. Now you're ready for ROM Steps below

    ROM - Installation:
    01. Download the ROM, TWRP and GApps from the links above.
    02. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
    03. Flash ROM.zip + TWRP_installer/boot.img ramdisk method
    04. Reboot > Recovery
    05. Install Gapps + Magisk (if you choose)
    06. Reboot > System

    Updating (AKA 'dirty flash'):
    01. Download the updated ROM
    02. fasboot boot twrp.img
    03. Install ROM.zip + TWRP_installer/boot.img ramdisk method
    04. Reboot > Recovery
    05. flash gapps + Magisk (if you choose)
    06. Reboot > System

    Notes:
    Any time your internal storage aka "Userdata" is from a stock install you must use 'fastboot -w' to erase it before using ROMS


    XDA:DevDB Information
    Lineage OS 16.0, ROM for the Moto G7 Power, ROM for the Moto G7 Power

    Contributors
    SyberHexen, erfanoabdi, LineageOS Team
    Source Code:
    [url]https://github.com/LineageOS[/URL]
    android_kernel_motorola_msm8953
    android_device_motorola_river_prebuiltvendor

    ROM OS Version: 9.x Pie
    ROM Kernel: Linux 4.x
    ROM Firmware Required: Stock Vendor.img

    Version Information
    Status: Testing

    Created 2019-09-18
    Last Updated 2019-10-01
    8
    Ill be the one taking over advancing development for G7 Power :)
    6
    ##### Lineage 16.0 Unofficial Build #####

    Moto G7 Update:- 01-10-2019
    -[Ocean]-

    Maintainer:- @SyberHexen

    Device Changelog:-
    * Build CAF WLAN driver from Source
    * Fix Wifi DHCP
    * Fix Hostapd / Tethering
    * Added all known Sprint Apns from stock

    Kernel Changelog:-
    * Upstream Kernel [4.9.180] --> [4.9.194]

    Download Link:-
    * https://www.androidfilehost.com/?fid=1899786940962599045
    4
    Hey everyone!

    So I've found a few fixes for the issues in this thread.

    1. Bluetooth (you must be rooted):
    1a: delete the audiofx.apk app using the app manager of your choice (I used total commander)
    1b. Install `ViPER4Android FX Legacy` from the Magisk Manager Downloads menu. It's interactive, but I just pressed `volume up` for every setting.
    1c. I also installed `Audio Modification Library` and `Bluetooth stack audio bitrate changer for SBC + aptX & aptX-HD enabler`, but it fixed Bluetooth from step 1b, so these may be optional. The Bluetooth stack ... enabler is also interactive. Press `volume up` right away because I think the wait script is broken, and it needs to detect a volume button press.

    2. Display Issues (no root needed):
    2a. As stated, you must change the display to sRGB in Settings→Display→Adaptive Display→Color Profile
    2b. In Developer options, there is a setting called 'Picture color mode' enable it, and the display mode *should* be persistent. I have no idea how that works. While you're in there, disable the animation speed ?

    I found the first fix back a bit, please give that guy a thanks. Someone please help me enale VoLTE please I do GrubHub for a living
    4
    I went back to stock, then followed the guide separately, but with the new zip file. The original September release works. This new one doesn't. I've wiped the data partition, my SD card is portable storage (for backups), and I have XT1955-4 RETEU. I've even tried dirty flashing it. How should I get you the logs?

    After you boot device and it reboots/loops

    goto twrp

    adb pull /sys/fs/pstore/console-ramoops