[ROM][LineageOS 14.1][substratum] for Moto G [falcon]

[JuanVCS]

Apps keep getting more resource intensive, good ol' falcon can barely keep up... But it still does, thanks to MSe1969 efforts!

 

[nefescalanadam]

No. Kindly refer to the OP, where I have given an explanation.

oh i get it, my old moto g has in Lineage os 17.1 right now and only problem is SELinux is permissive.

 

[pankajandhale]

OTA Updated yesterday And now phone is fully dead ,
no Bootloader , no recovery, not charging.

if anyone have solution ,please suggest !!!!!

Thanks in advance !!!!!

 

[MSe1969]

OTA Updated yesterday And now phone is fully dead ,
no Bootloader , no recovery, not charging.

if anyone have solution ,please suggest !!!!!

Thanks in advance !!!!!

I have tested both variants f. OTA - not sure, what caused the hard-brick to your device.

Tbh, I can only recommend you to search on XDA and the search engine of your choice for methods to unbrick a hard-bricked Moto G. A quick search has delivered to me some hits, but I can't give you a recommendation for any approach. Maybe others would like to step in?

In general, the falcon is an aged (almost 10 years now) low budget device, e.g. the "internal flash memory" is only a recrafted SD card. Maybe its time simply has come...? Of course, before giving up, try to unbrick somehow...

Sorry, that I can't give you any better advice, but a true hard-brick as described by you with NO reaction at all does not belong to my experience ...

 

[pankajandhale]

I have tested both variants f. OTA - not sure, what caused the hard-brick to your device.

Tbh, I can only recommend you to search on XDA and the search engine of your choice for methods to unbrick a hard-bricked Moto G. A quick search has delivered to me some hits, but I can't give you a recommendation for any approach. Maybe others would like to step in?

In general, the falcon is an aged (almost 10 years now) low budget device, e.g. the "internal flash memory" is only a recrafted SD card. Maybe its time simply has come...? Of course, before giving up, try to unbrick somehow...

Sorry, that I can't give you any better advice, but a true hard-brick as described by you with NO reaction at all does not belong to my experience ...

Hey man thanks for reply ,

Tried all the Methods > No Luck .

then at last opened the phone and checked the battery voltage it was 2.8 V , and my fastboot oem-off-mode was set to 0 thats why phone was not charging nor booting .
Jump-charged the battery for 15 minutes and then tried to boot in fasstboot !!!!!!!!!!!!!!!!!!

My Lovely Moto rose from dead !!!!!
thank you very much for your efforts to keep this Device alive .


one last thing Whenever I try to do > fastboot oem-off-mode 1
it gives > slot-count not found .
any suggestion ?

 

[MSe1969]

Hey man thanks for reply ,

Tried all the Methods > No Luck .

then at last opened the phone and checked the battery voltage it was 2.8 V , and my fastboot oem-off-mode was set to 0 thats why phone was not charging nor booting .
Jump-charged the battery for 15 minutes and then tried to boot in fasstboot !!!!!!!!!!!!!!!!!!

Glad you reanimated your phone
Just to understand: So you put charge directly to the battery, right?

one last thing Whenever I try to do > fastboot oem-off-mode 1
it gives > slot-count not found .
any suggestion ?

Unfortunately, I am not familiar with the undocumented oem-specific fastboot commands. If I understood you right, the oem off-mode would cause the battery not being charged??? I am not sure about that - I think there is a setting to leave the screen black during charging, but not to "not load" the battery... However, as said - I am not really familiar with the hidden fastboot commands. But I would expect that the command is 'fastboot oem <special command>', hence 'fastboot oem off-mode ...' - and AFAIK, there is only a command like 'fastboot oem off-mode-charging ...' - Just my thoughts...

 

[pankajandhale]

Just to understand: So you put charge directly to the battery, right? > YES

Unfortunately, I am not familiar with the undocumented oem-specific fastboot commands. If I understood you right, the oem off-mode would cause the battery not being charged??? I am not sure about that - I think there is a setting to leave the screen black during charging, but not to "not load" the battery... However, as said - I am not really familiar with the hidden fastboot commands. But I would expect that the command is 'fastboot oem <special command>', hence 'fastboot oem off-mode ...' - and AFAIK, there is only a command like 'fastboot oem off-mode-charging ...' - Just my thoughts. >

fastboot oem off-mode-charge (takes "0" and "1" as an argument ).

if I connect charger to switched off phone , following functions can be achieved

"fastboot oem off-mode-charge 0" >>> will keep my phone switched off while charging when usb is connected
"fastboot oem off-mode-charge 1" >>> will power on phone as soon as phone is connected (as power button of my phone is little hard this trick helps me to power on my phone )

anyways thank you and please keep developing for this phone until possible

 

[MSe1969]

New builds available

Hi all,
new builds with backported July 2022 patches (July 2022 custom build release) are available for download and via the Updater app.


A. Default LineageOS 14.1 with substratum and microG patch

https://sourceforge.net/projects/lin14-mgoms/files/falcon/lineage-14.1-20220716-UNOFFICIAL-oms-falcon.zip/download

B. Hardened build with pre-installed microG and F-Droid, patched for substratum

https://sourceforge.net/projects/lin14-mgoms/files/falcon/lineage-14.1-20220716-UNOFFICIAL-mG-oms-falcon.zip/download

Happy flashing
Regards, M.

 

[amlethh]

Thank you so much for keeping the Falcon alive! I have 3 strong units and intend to use them till the dawn of time. Lately I have been facing one issue though: some apps are starting to drop support for Android 7. One example is Slack, the last versions all require Android 8+ and they are sending emails telling this for everyone who has an older version installed:

Our records indicate that you are on a version of the Slack mobile app that Slack will stop supporting on September 1, 2022.

As we all know, our beloved Falcon can't handle Android 8 or up because of hardware constraints. However, is there a way to spoof the Android version so it appears we are on Android 8 or up while still being on the current build?
That is, is there a way to spoof Android version on MSe1969's LineageOS Falcon build?

Regards.

 

[MSe1969]

As we all know, our beloved Falcon can't handle Android 8 or up because of hardware constraints. However, is there a way to spoof the Android version so it appears we are on Android 8 or up while still being on the current build?
That is, is there a way to spoof Android version on MSe1969's LineageOS Falcon build?

Unfortunately not. This is not about "spoofing". An Android app declares a "minimum SDK" level, which is the lowest Android version supported. By doing so, the developer is limited to those functionalities, which are available in that release. Any attempt of using a method or a class or simply a method parameter, which does not exist in the minimum SDK hence causes a build error, when compiling the app.
So the desire to use new cool features of a newer Android release has to be balanced against the user base. Slack has decided to "move on" it seems...
In addition, there is also the "target SDK" topic adding complexity to this, but let's talk about that another time...

 

[amlethh]

Unfortunately not. This is not about "spoofing". An Android app declares a "minimum SDK" level, which is the lowest Android version supported. By doing so, the developer is limited to those functionalities, which are available in that release. Any attempt of using a method or a class or simply a method parameter, which does not exist in the minimum SDK hence causes a build error, when compiling the app.
So the desire to use new cool features of a newer Android release has to be balanced against the user base. Slack has decided to "move on" it seems...
In addition, there is also the "target SDK" topic adding complexity to this, but let's talk about that another time...

That is a sad situation but as users we must understand developers reasons. Still, could it be that in some cases the app requiring a higher SDK is unnecessarily doing so? I found this post on another forum from some months ago:

This decision really frustrating! And yeah, I spoofed my Android version as 8 and it works perfectly fine on my Android 7, so it's not a case of technical limitations.

So far this is the only app that's limiting my Falcon experience, so it'd be really good if there were a workaround...

Thanks!

 

[phpbb3]

Sometimes, alternative apps can be an option too. The newest release of Plex crashes on my falcons, so I've moved to BubbleUPnP to read my music off my Plex server. Maybe not an option for Slack but something to keep in mind.

 

[MSe1969]

That is a sad situation but as users we must understand developers reasons. Still, could it be that in some cases the app requiring a higher SDK is unnecessarily doing so? I found this post on another forum from some months ago . . .

Technically, a developer can of course use code fully suitable for Android version Y, but declare the minimum SDK level to be Y+n - would be not really be the smartest move at all, but that is technically possible. (Further, I know that Google forces app developers to frequently increase the target SDK declaration to the defined minimum for apps in the play store - not sure however about the minimum SDK level declaration...?)

So if you find some "good stuff" helping you to spoof the Android version (like an Xposed module?) or you succeed in modifying the apk manifest to allow Android 7 in the Slack apk file via e.g. apktool and the apk does not crash, there you go. But frankly, that is nothing, I am willing to spend time with in my ROM builds. (e.g. because this is also kind of a security/stability feature to ensure, that the system does not crash and freeze)

 

[MSe1969]

New builds available

Hi all,
new builds with backported August 2022 patches (August 2022 custom build release) are available for download and via the Updater app.

A. Default LineageOS 14.1 with substratum and microG patch

https://sourceforge.net/projects/lin14-mgoms/files/falcon/lineage-14.1-20220809-UNOFFICIAL-oms-falcon.zip/download

• System Webview 103.0.5060.71

B. Hardened build with pre-installed microG and F-Droid, patched for substratum

https://sourceforge.net/projects/lin14-mgoms/files/falcon/lineage-14.1-20220809-UNOFFICIAL-mG-oms-falcon.zip/download

• Bromite Webview 103.0.5060.140

Happy flashing
Regards, M.

 

[CallMeTom1]

After updating via the updater app, I stuck in fastboot mode. I can no longer boot the system ("boot up failed"). The recovery/TWRP still works. I have already tried in TWRP to reflash the zip file but without success. Does anyone have an idea?

 

[Scranalot]

After updating via the updater app, I stuck in fastboot mode. I can no longer boot the system ("boot up failed"). The recovery/TWRP still works. I have already tried in TWRP to reflash the zip file but without success. Does anyone have an idea?

View attachment 5683775

Hello Tom
Was the phone working satisfactorily before the update?
Your phone isn't full up with data is it?
What ever you do from now though firstly I would try & extract as much data that you would want to keep from the phone as possible.
Got a few of suggestions you may want to try - please read through them all first though:

• If have you a recent Nandroid backup on your phone/OTG device/via adb you could try a backup restore
• Its possible the update was corrupted in some way so if possible download a new copy of the ROM & get it onto your phone & try re-flashing that.
• Have a look here: https://xdaforums.com/t/fastboot-reason-fall-through-from-normal-boot-mode.4052109/ - in particular the second post in that thread. If you do decide to go down the factory image restore route take a look here as I had to do it fairly recently: https://xdaforums.com/t/rom-lineageos-14-1-substratum-for-moto-g-falcon.3808428/post-86161955

Please bare in mind Tom these are only my suggestions - I am not telling you to do any of these that is entirely your own choice & responsibility - that being said I have done all the above , with the exception of the 'fall-through from normal boot mode' specific things mentioned in the first link, during my ownership of the these phones.
Someone else will hopefully chime in with a knowledgeable response.
All the best

 

[MSe1969]

After updating via the updater app, I stuck in fastboot mode. I can no longer boot the system ("boot up failed"). The recovery/TWRP still works. I have already tried in TWRP to reflash the zip file but without success. Does anyone have an idea?

I think, what @Scranalot replied to you pretty well lists your options here.

Maybe an additional thought, just to be sure - please advise:
You were using this ROM normally before without any issue, correct?
You haven't flashed anything on top recently, which has e.g. put some kind of "survival script" attempting to reflash something?
The phone wasn't already somehow "messed up" before the update (e.g. by flashing bad stuff) and you were hoping to "repair" the mess by applying an update?

 

[CallMeTom1]

@Scranalot @MSe1969
Hi! Thanks for your replies and sorry for my late reply.

The Moto G is my second phone. I use it to control my Bluetooth box and for navigation (since BT and GPS work rather poorly on my main phone). Everything worked fine before the update (it was all a bit slow, but the smartphone is old) and I only did the update/dirty flash.

Meanwhile it works again (more or less). I did a full wipe and reinstalled the ROM (without full wipe it didn't work before).
I can not install Gapps for some reason (Error Code 70), but here I will also find a solution.

 

[MSe1969]

Meanwhile it works again (more or less). I did a full wipe and reinstalled the ROM (without full wipe it didn't work before).
I can not install Gapps for some reason (Error Code 70), but here I will also find a solution.

Which flavor of Gapps did you try to install? The falcon does not have a lot of space in the system partition, so 'nano' is the largest, you should aim for (I recommend - if you really want Gapps - only the 'pico' flavor)

 

[CallMeTom1]

Which flavor of Gapps did you try to install? The falcon does not have a lot of space in the system partition, so 'nano' is the largest, you should aim for (I recommend - if you really want Gapps - only the 'pico' flavor)

I have tried nano. There the error occurred.
With pico it worked, thank you.