[ROM]-[11.0]-[NAIRO]-LineageOS-18.1-[OFFICIAL]

Search This thread

Emerald_N8

Senior Member
May 18, 2018
54
7
Sorry, i don't have devices to test your request.




Is this Rom still in development, or is the development in "freeze" because there is now an official lineageos rom
i tried that my self
i installed the official version of the lineage os rom and the wireless display ( aka screen mirror ) fully works ! OH THANKS GOD
also i have a front notification led that i have never seen that on stock rom :0
i just wonder if it can be disabled or not , because its so bright

Edit : yes it can be disabled and also i can change the level of brightness of the notification led
 
Last edited:
  • Love
Reactions: hteles

hteles

Senior Member
Oct 10, 2011
544
242
Sintra
Nexus 7
LG G3
Hi.
First of all, thanks for all your hard work.
My last LineageOS device was a LG H815 Device and a Nexus 7 ( tilapia ).
At that time passing safety net with magisk was easy peasy..... Now im havong a lot of trouble getting my 🏦 app to work. Ive already installed universal safety net, but no joy. 😅
Safety'snet check is giving me "CTS profile Matched"
If this conservation is not allowed here please be free to contact me privately.

regards.

P.S: What a great port ( using official LOS build ) Kudos to the developers. Great job!!!
 
May 27, 2022
5
3
Moto G 5G Plus
Hello SyberHexen,

thank you very much for the offical LineageOS build for this phone. I have the image now on my phone (after my first almost hardbrick, apparently I didn't have a bootloader on the A partition and after the flash and subsequent reboot I didn't have any more).
I have now set up and tested almost everything for daily use. So far everything is fine. The FM radio app also works but very, very quietly. Do you have an idea what that could be?
 

Sociio

New member
Feb 28, 2018
2
2
Samsung Galaxy S9
This is the most beautiful thing I've ever seen! I tried the 19.1 version but had no data and was stuck in roaming x1 so this is perfect!! Guide is lovely but oh man that was intense! Moment of terror when the guide says "important if you want gapps it MUST be installed before first boot!" but my adb stops working in the middle of it (not the errors it says is ok, like using usb 3.0 not usb 2.0 and my phone suddenly disconnecting type errors) and I boot into system like a moron.

At first i freaked and was like maaaaaaan i gotta start over from stock but it was really as simple as rebooting to recovery, wipe it all, sideload GApps, sideload magisk again and when i booted up i had GApps and no errors. Not sure if that will work across all devices but if so it would help the others who i'm sure have wondered the same but never tried it =P

thank you though frfr <3
 
  • Like
Reactions: ong14 and Tommy0000

marmistrz

Senior Member
Jun 3, 2012
61
1
Does LineageOS for nairo expose the notification light for apps? I know that it physically has a notification LED but it's not exposed by the Motorola ROM, so apps can't use it. (it's only used for battery low information afaik)
 

Emerald_N8

Senior Member
May 18, 2018
54
7
no changes in the lineage-18.1-20220608-nightly-nairo-signed.zip build ? then why its a new update ?!
 

Emerald_N8

Senior Member
May 18, 2018
54
7
hello
i had a problem from the first time i installed official LineageOS on my nairo
i have to change slot from a to b every time i want to install an update and also i was not able to install LineagOS from slot a in first time i was trying to install it so i installed it from slot b

both first install and sideloading updates from lineage recovery from slot a does not stuck at 47% (unlike installing from slot b) but immediately at 47% gives an error (Total xfer: 1.00x ) and wont get installed/updated and also when im in LineageOS updating from settings/OTA fails after pressing install and i have to reboot to bootloader and change the slot to b and apply it from recovery every time

is updating in such way ok ? does any else have same problem ?
 

hteles

Senior Member
Oct 10, 2011
544
242
Sintra
Nexus 7
LG G3
Hi.
Did you sideloaded copy partitions zip?


Note: The steps below only need to be run once per device.

In some cases, the inactive slot can be unpopulated or contain much older firmware than the active slot, leading to various issues including a potential hard-brick. We can ensure none of that will happen by copying the contents of the active slot to the inactive slot.
 

hteles

Senior Member
Oct 10, 2011
544
242
Sintra
Nexus 7
LG G3
Hi.
Did you sideloaded copy partitions zip?


Note: The steps below only need to be run once per device.

In some cases, the inactive slot can be unpopulated or contain much older firmware than the active slot, leading to various issues including a potential hard-brick. We can ensure none of that will happen by copying the contents of the active slot to the inactive slot.

Btw.
After looking the above for you, in the same page there is s another note!


Tip: Normally, adb will report Total xfer: 1.00x, but in some cases, even if the process succeeds the output will stop at 47% and report adb: failed to read command: Success. In some cases it will report adb: failed to read command: No error or adb: failed to read command: Undefined error: 0 which is also fine.
 

SyberHexen

Senior Member
Btw.
After looking the above for you, in the same page there is s another note!


Tip: Normally, adb will report Total xfer: 1.00x, but in some cases, even if the process succeeds the output will stop at 47% and report adb: failed to read command: Success. In some cases it will report adb: failed to read command: No error or adb: failed to read command: Undefined error: 0 which is also fine.
This is completely normal. I've never seen sideload progress go past 47% on any device.
Esentially the other 53% is unpacking and completing the installation process on the device side.

If you have sdcard or otg you will see the process report its a 2step
 
  • Like
Reactions: hteles

Emerald_N8

Senior Member
May 18, 2018
54
7
Btw.
After looking the above for you, in the same page there is s another note!


Tip: Normally, adb will report Total xfer: 1.00x, but in some cases, even if the process succeeds the output will stop at 47% and report adb: failed to read command: Success. In some cases it will report adb: failed to read command: No error or adb: failed to read command: Undefined error: 0 which is also fine.
i sideloaded the copy partition in the lineage recovery and i did not skipped any of the steps

i fallowed every step exactly as it said but sideloading LineagOS in the Lineag recovery with active slot_a gives xfer: 1.00x and its not fine and wont boot/update but with active slot_b it gives " xfer: 1.00x adb: failed to read command: Success " and its fine and it boots

and same thing for updating every weak :
the OTA fails and sideloading it manually from recovery with active slot_a gives xfer: 1.00x and after rebooting to the OS it did not updated and i have to change to active slot_b and then sideloading it from recovery and gives " xfer: 1.00x adb: failed to read command: Success " and now its updated to newer version

any way ,the ROM which is installed in slot_a , is fine and everything is working
 

SyberHexen

Senior Member
i sideloaded the copy partition in the lineage recovery and i did not skipped any of the steps

i fallowed every step exactly as it said but sideloading LineagOS in the Lineag recovery with active slot_a gives xfer: 1.00x and its not fine and wont boot/update but with active slot_b it gives " xfer: 1.00x adb: failed to read command: Success " and its fine and it boots

and same thing for updating every weak :
the OTA fails and sideloading it manually from recovery with active slot_a gives xfer: 1.00x and after rebooting to the OS it did not updated and i have to change to active slot_b and then sideloading it from recovery and gives " xfer: 1.00x adb: failed to read command: Success " and now its updated to newer version

any way ,the ROM which is installed in slot_a , is fine and everything is working
Well whenever you get a chance it may be good to restock with the latest factory image on slot a then flash the copy partitions zip.

Though by just switching slots and rebooting to bootloader you can see the bootloader date under mbn.
 

Emerald_N8

Senior Member
May 18, 2018
54
7
Well whenever you get a chance it may be good to restock with the latest factory image on slot a then flash the copy partitions zip.

Though by just switching slots and rebooting to bootloader you can see the bootloader date under mbn.
getvar all when active slot_b:

(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nairo_retail-614626c8108-210828
(bootloader) product: nairo
(bootloader) board: nairo
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EMLA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 128GB SAMSUNG KM8V8001JM-B813 FV=1500
(bootloader) ram: 8GB SAMSUNG LP4x DIE=16Gb M5-M8=01 07 01 50
(bootloader) cpu: SM_SAIPAN 2.0
(bootloader) serialno: ZY227WMNLL
(bootloader) cid: 0x0032
(bootloader) channelid: 0x52
(bootloader) uid: D97BA433
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805306368
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei:

i removed imei number before commenting , its shows and its fine

(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 09-26-2020
(bootloader) sku: XT2075-3
(bootloader) carrier_sku: XT2075-3
(bootloader) battid: SB18C74374
(bootloader) battery-voltage: 3877
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: retmea
(bootloader) ro.build.fingerprint[0]: motorola/nairo_retail/nairo:11/RPN
(bootloader) ro.build.fingerprint[1]: S31.Q4U-39-27-5-10/21a541:user/rel
(bootloader) ro.build.fingerprint[2]: ease-keys
(bootloader) ro.build.version.qcom: LA.UM.9.12.r1-08600-SMxx50.0
(bootloader) version-baseband[0]: M7250_HI20_78.180.02.24.04R NAIRO_EMLA
(bootloader) version-baseband[1]: DSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.19.125-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 10.0.7 for An
(bootloader) kernel.version[2]: droid NDK, GNU ld (binutils-2.27-bd24d23
(bootloader) kernel.version[3]: f) 2.27.0.20170315) #1 SMP PREEMPT Sat A
(bootloader) kernel.version[4]: ug 28 09:31:08 CDT 2021
(bootloader) git:xbl: MBM-3.0-nairo_retail-b1aecf973-210828
(bootloader) git:xbl_config: MBM-3.0-nairo_retail-b1aecf973-210828
(bootloader) git:abl: MBM-3.0-nairo_retail-614626c8108-210828
(bootloader) git:aop: MBM-3.0-nairo_retail-98367a1-210828
(bootloader) git:tz: MBM-3.0-nairo_retail-5dbf9632-210828
(bootloader) git:hyp: MBM-3.0-nairo_retail-5dbf9632-210828
(bootloader) git:devcfg: MBM-3.0-nairo_retail-5dbf9632-210828
(bootloader) git:keymaster: MBM-3.0-nairo_retail-4e35993-210828
(bootloader) git:storsec: MBM-3.0-nairo_retail-4e35993-210828
(bootloader) git:uefisecapp: MBM-3.0-nairo_retail-4e35993-210828
(bootloader) git: prov: MBM-3.0-nairo_retail-5dbf9632-210828
(bootloader) git:qupfw: MBM-3.0-nairo_retail-8c8441f-210828
(bootloader) frp-state: no protection (77)
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 2
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 7
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C90974
(bootloader) primary-display: tianma_nt36672c_1080x2520_670_dsc_vid
(bootloader) secondary-display: none
all: listed above
Finished. Total time: 0.125s

getvar all when active slot_a :

(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nairo_retail-614626c8108-210828
(bootloader) product: nairo
(bootloader) board: nairo
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EMLA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 128GB SAMSUNG KM8V8001JM-B813 FV=1500
(bootloader) ram: 8GB SAMSUNG LP4x DIE=16Gb M5-M8=01 07 01 50
(bootloader) cpu: SM_SAIPAN 2.0
(bootloader) serialno: ZY227WMNLL
(bootloader) cid: 0x0032
(bootloader) channelid: 0x52
(bootloader) uid: D97BA433
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805306368
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 09-26-2020
(bootloader) sku: XT2075-3
(bootloader) carrier_sku: XT2075-3
(bootloader) battid: SB18C74374
(bootloader) battery-voltage: 3878
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: retmea
(bootloader) ro.build.fingerprint[0]: motorola/nairo_retail/nairo:11/RPN
(bootloader) ro.build.fingerprint[1]: S31.Q4U-39-27-5-10/21a541:user/rel
(bootloader) ro.build.fingerprint[2]: ease-keys
(bootloader) ro.build.version.qcom: LA.UM.9.12.r1-08600-SMxx50.0
(bootloader) version-baseband[0]: M7250_HI20_78.180.02.24.04R NAIRO_EMLA
(bootloader) version-baseband[1]: DSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.19.125-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 10.0.7 for An
(bootloader) kernel.version[2]: droid NDK, GNU ld (binutils-2.27-bd24d23
(bootloader) kernel.version[3]: f) 2.27.0.20170315) #1 SMP PREEMPT Sat A
(bootloader) kernel.version[4]: ug 28 09:31:08 CDT 2021
(bootloader) git:xbl: MBM-3.0-nairo_retail-b1aecf973-210828
(bootloader) git:xbl_config: MBM-3.0-nairo_retail-b1aecf973-210828
(bootloader) git:abl: MBM-3.0-nairo_retail-614626c8108-210828
(bootloader) git:aop: MBM-3.0-nairo_retail-98367a1-210828
(bootloader) git:tz: MBM-3.0-nairo_retail-5dbf9632-210828
(bootloader) git:hyp: MBM-3.0-nairo_retail-5dbf9632-210828
(bootloader) git:devcfg: MBM-3.0-nairo_retail-5dbf9632-210828
(bootloader) git:keymaster: MBM-3.0-nairo_retail-4e35993-210828
(bootloader) git:storsec: MBM-3.0-nairo_retail-4e35993-210828
(bootloader) git:uefisecapp: MBM-3.0-nairo_retail-4e35993-210828
(bootloader) git: prov: MBM-3.0-nairo_retail-5dbf9632-210828
(bootloader) git:qupfw: MBM-3.0-nairo_retail-8c8441f-210828
(bootloader) frp-state: no protection (77)
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 1
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 7
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C90974
(bootloader) primary-display: tianma_nt36672c_1080x2520_670_dsc_vid
(bootloader) secondary-display: none
all: listed above
Finished. Total time: 0.172s

date under mbn ???
 
Mar 27, 2022
11
3
today i've tried to install the ota update to 20 July 2022. When i click on "install" only a error message comes for a very brief moment : "installation error" and the update has no effect. Did somebody have the same problem?
 
Mar 27, 2022
11
3
Hi.
No problem whatsoever. Maybe a bad download? Reboot and try to refresh the system updater..

18.1-20220720-NIGHTLY-nairo
Okay i've tried "export update" to sd card, and after that flash via reovery (and also sideload)
the result was every time :
error applying update : 7 (ErrorCode : kInstallDeviceOpenError)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Hi.
    No problem whatsoever. Maybe a bad download? Reboot and try to refresh the system updater..

    18.1-20220720-NIGHTLY-nairo
    1
    Hi.
    Im oit of ideas. A google search returns some results and some solved by returning back to stock.

    The last thing i can suggest is for you to download and check md5sum from https://download.lineageos.org/nairo

    Would first install the LOS official recovery ( if running twrp or old LOS recovery ).

    More help from here https://duckduckgo.com/?q=kInstallDeviceOpenError&t=fpas&ia=web

    Sorry. Can't help you further.
    1
    Hi.
    Im oit of ideas. A google search returns some results and some solved by returning back to stock.

    The last thing i can suggest is for you to download and check md5sum from https://download.lineageos.org/nairo

    Would first install the LOS official recovery ( if running twrp or old LOS recovery ).

    More help from here https://duckduckgo.com/?q=kInstallDeviceOpenError&t=fpas&ia=web

    Sorry. Can't help you further.
    Thank you for your time
    1
    Its really not about time, but knowledge.
    Keep us posted!
    Just do a backup ( JIC ) of photos and data before anything major, cause at some point it may not boot anymore.

    Im hoping that with updated recovery it will be possible to flash the update. Also it may be something about active partition.
    I'm on a linux machine.
    -My adb tools where not updated via "apt-get update" so i downloaded them from "git"
    -after that i was able to (dirty) flash my device, but there was no way of rebooting it. it was stuck in bootloop.
    -after "factory reset" the device was able to wake up again.
    1
    Los 18.1. No bugs, everything works as it should.
    The only thing I've installed was magisk and gcam from this forum.
  • 5
    2okPze5.png

    Motorola G 5G Plus/ Motorola One G 5G
    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, and if
    * you point the finger at me for messing up your device, I will laugh at you.
    */
    Introduction:
    This is the Official Lineage OS 18.1 thread for the Motorola G 5G Plus/Motorola One 5G, codename Nairo.​
    Join our Motorola G 5G Plus / Motorola One 5G Development Telegram Group!​

    LINKS:
    Magisk: Magisk
    Factory Firmware: Stock Firmware Mirror
    "Copy Partitions Zip" - courtesy of @filipepferraz
    (To setup "Slot B")

    How to Install:

    Contributors[/B]
    erfanoabdi, SyberHexen, Jleeblanch
    Source Code: https://github.com/LineageOS/

    ROM OS Version: Android 11
    ROM Kernel: Linux 4.19
    Based On: LineageOS

    Version Information
    Status:
    Stable
    2
    This is the most beautiful thing I've ever seen! I tried the 19.1 version but had no data and was stuck in roaming x1 so this is perfect!! Guide is lovely but oh man that was intense! Moment of terror when the guide says "important if you want gapps it MUST be installed before first boot!" but my adb stops working in the middle of it (not the errors it says is ok, like using usb 3.0 not usb 2.0 and my phone suddenly disconnecting type errors) and I boot into system like a moron.

    At first i freaked and was like maaaaaaan i gotta start over from stock but it was really as simple as rebooting to recovery, wipe it all, sideload GApps, sideload magisk again and when i booted up i had GApps and no errors. Not sure if that will work across all devices but if so it would help the others who i'm sure have wondered the same but never tried it =P

    thank you though frfr <3
    1
    Note to self: no, no you can't. Corrupt OS message from recovery after trying to reboot. Also storage appears encrypted still from "install Magisk" step, guess that should have been a warning. Sigh.

    Flash back to stock again, sigh. At least that seems to recover everything.
    1
    we do really need a hero who can create a nairo twrp, this version boots with android 12 on nairo but touch doesnt work :c
    wait a min or 2 for touch screen
    1
    Los 18.1. No bugs, everything works as it should.
    The only thing I've installed was magisk and gcam from this forum.