Development [ROM][Official][Nightly] LineageOS 18.1 for Edge S / Moto G100

Search This thread

sp6ina

Member
Mar 20, 2022
8
1
Motorola Moto G100 / Edge S
I test this rom for fer day and i have only one problem. On sms app i can't send sms because i have two sim card and always phone told me that i dont select deafault sim to sms. I do that but nothing change
 

mentao

Member
Mar 12, 2018
20
5
Vienna
I, as well as someone else in thread, had the same issue with not being able to boot this recovery, however I did have success using Electimon's modded recovery that you can find here...


That recovery worked for me, in place of the one listed in this thread.
Thanks for the link, that really helped me out :)

Also, for others who are as clueless as myself: I tried just booting without flashing via

fastboot boot LOSrecovery.img

and that lead to a boot loop. But just flashing and then rebooting into recovery works fine:

fastboot flash boot LOSrecovery.img
 
  • Like
Reactions: CCivale

Windoors

Senior Member
Jan 29, 2018
224
25
Installation getting suck at 47% and then aborting. Device getting hard bricked. Luckily was able to revive using blankflash.
 

Hazuki Amamiya

Senior Member
Jul 24, 2010
58
28
Hong Kong
I am having the same issue with edge S RETCN. What's making worse is that after few attempts of
blankflash:
Code:
D:\Edges\blankflash_nio_retca_RRTS31.Q1-84-24-3-6>.\qboot.exe blank-flash

Motorola qboot utility version 3.86

[  0.000] Opening device: \\.\COM4
[  0.014] Detecting device
[ 34.553] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.553] Check qboot_log.txt for more details
[ 34.553] Total time: 34.553s

FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error

D:\Edges\blankflash_nio_retca_RRTS31.Q1-84-24-3-6>pause

Press any key to continue . . .

The phone's QDLoader is becoming unrecognized (Device Descriptor Request failed).

Any help is appreciated.
 

Hazuki Amamiya

Senior Member
Jul 24, 2010
58
28
Hong Kong
Okay, I somehow managed to get back QDLoader by resetting the battery (yes, I have to open the lid). I was not able to recover the phone via official tools "Rescue and Smart Assistant" and luckily there is a "tinyflashscript" that allowed me to do a full firmware flash with factory reset.

This is NOT FUN. I will stay away from trying LineageOS for a while
 

HackVasant

Member
Mar 19, 2022
15
1
@dianlujitao Thanks for the ROM.

Everything works except that I cannot install any out of tree drivers that i built, even with root access.
The issue is the kernel config has (CONFIG_MODULE_SIG_FORCE=y ) which requires a signed module.
So at this point I would have to build the kernel plus all the modules a somewhat tedious exercise -:).

I am upgrading form MotoG7 (river) running Lineage OS 18.1 and the kernel config for reference has:
# CONFIG_MODULE_SIG_FORCE is not set
CONFIG_MODULE_FORCE_LOAD=y
This is a much more hacker friendly kernel -:). I hope you will consider these changes in your future build.
For now I am going to switch to the EvolutionX ROM which has the above kernel config settings.

Thanks again for your effort.
 

zsiezi

Member
Aug 31, 2015
23
2
Hey everyone, I need some feedback on how good everything works with the 19.1 official. Is it stable enough as a daily driver? Are there any (minor) flaws I should know about before flashing?

Thanks in advance!
 

CCivale

Senior Member
Apr 25, 2011
111
32
Hey everyone, I need some feedback on how good everything works with the 19.1 official. Is it stable enough as a daily driver? Are there any (minor) flaws I should know about before flashing?

Thanks in advance!
If you have any specific questions about what works and doesn't, we can move over to the 19.1 thread and I'll continue there. I've been running it since Sunday as my daily driver and I'm enjoying it.

Edit: Just saw that the thread is still marked "beta", but we can chat there.
 

sip4050sip

Member
Apr 13, 2022
16
2
I, as well as someone else in thread, had the same issue with not being able to boot this recovery, however I did have success using Electimon's modded recovery that you can find here...


That recovery worked for me, in place of the one listed in this thread.
I had the same problem, even with e/ os and that LOSrecovery.img saved me!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 10
    LineageOS is a free, community-built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.
    Code:
    #include <std_disclaimer.h>
    
    /*
    * Your warranty is now void.
    *
    * We are 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 us for messing up your device, we will laugh at you.
    *
    */
    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. You will need to provide your own Google Applications package (gapps). 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 our Gerrit Code Review. Your changelog is whatever was merged into gerrit.

    Important information:
    This thread is for LineageOS 18.1 builds for Edge S / Moto G100. The following will not be supported here:
    • Custom kernels
    • Mods
    • Xposed

    We don't support Xposed and any logcat which includes an Xposed module will be ignored. You're kindly invited to not report bugs if you:
    • Flashed a custom kernel
    • Installed or did mods from untrusted sources
    • Modified system files

    Tips:
    • I have not implemented dynamic model detection yet, so the displayed model is always "Edge S" regardless of your actual hardware, this is not a bug.

    Installation:

    Source code:

    Credits:
    • LineageOS Team & Contributors
    • Code Aurora Forum
    • Special thanks to Electimon, this work is heavily based on his prior ones.
    • ......

    Download:
    2
    Stumped on getting lineageos recovery to boot to install los.

    When I do

    fastboot boot lineage-18.1-20220226-recovery-nio.img

    Phone reboots and all I see is initial Motorola logo forever (No haptic or moto voice) Tried with and without sim/sd card installed.

    I did manage to fastboot TWRP. This at least comes up. Yet /w lineageos recovery I only see moto logo. lineageos recovery is never displayed.

    If I try to flash to boot..
    fastboot flash boot lineage-18.1-20220226-recovery-nio.img

    It's same thing Moto logo forever.. Have to flash boot.img from stock back to get the phone to boot at all after this.
    I, as well as someone else in thread, had the same issue with not being able to boot this recovery, however I did have success using Electimon's modded recovery that you can find here...


    That recovery worked for me, in place of the one listed in this thread.
    1
    Recovery didn't work if I directly flash it when I have stock ROM

    But it works after I flashed los-modded's recovery, install official los, and then reboot to recovery
    1
    I, as well as someone else in thread, had the same issue with not being able to boot this recovery, however I did have success using Electimon's modded recovery that you can find here...
    Installing losrecovery worked :D. Love the ROM - thanks all!!
    1
    hello then did you use the recovery from electomotion? Does the lineage version you used exist? dated February 26? Thanks
    Yes, I used Electimon's losrecovery.img and was able to boot into recovery and install the first official nightly (dated 19th). Since then, I updated to the 26th, but that was an ota update through the phone.