FORUMS
Remove All Ads from XDA

Segmentation Fault in all customs ROMs

250 posts
Thanks Meter: 89
 
By andyro2008, Senior Member on 2nd October 2017, 07:59 PM
Post Reply Email Thread
The Segmentation Fault error is fixed on LineageOS. It will be fixed progressively in any other ROM in the upcoming updates.

Infinite thanks to @wzedlare, and the other persons and devs that helped us. Im gonna request to mods to close this thread


And over again thanks to all! I'm so happy now!

Quote:

On certain devices a series of binaries, shell/ADB commands are not working correctly.
Most of the time when one of these binaries I invoked the crash with a "Segmentation fault" error (SIGEGV 11). If the command/binarie is executed multiple times, at some point it works without the error. (1 of 30 times approximately).

These commands/binaries are very important for Root applications, but are not limited to them.
As a result many applications that need ROOT work very sporadically, and some not root apps are affected too.

If you are suffering the same problem, please share your logcats, the app or the command affected, and your device model, in order to get more information about the problem to help the devs and other users.

Affected ROMs and Devices

So far all customs ROMs for Cedric are affected. It appears to be related to a Cedric variant with Dual SIM, removable battery and 3GB of RAM. Mostly sold in Europe trough Amazon.

Known affected apps and Workarrounds:
  • SuperSu and MagikSU(all versions): Devices rooted with Magisk or SuperSu, suffer from the error almost every time that SU binarir is invoked. The visible symptom is that although according the info provided by the application (Magisk manager says that the device is correctly rooted), the requests to get root permission will not popup because the binarie is crash almost 29 to 30 times. As a result these options for root are almost useless.
  • LineageOS SU By itself works correctly, the binarie will not crash, but the other commands still will be affected. Is the most funtional root option for affected devices!!
  • Secure Settings, BetterBattery stats, AutoTools ADB commands to Grant permissions can be executed multiple times. Once authorized, they work correctly.
  • Super Doze To change doze settings you need to press apply button multiple times. There is no way to know when the change was actually applied except using ADB.
  • Nap Time it's useless to change doze settings, but force doze is working.
  • Greenify, Servicely The will pop out an error every time that trying to stop every single app. In short they are useles.
  • Titanium BackUp and Link2SD To freeze or unfreeze an app you must tap multiples times until it work.
  • Disable Services Tap multiple times until it work.
  • LiveBoot After installed it will work only 1/30 reboots (Useless)

Known affected binaries
  • pm
  • am
  • settings
  • adb backup
  • Magisk Su, and Super Su

Disclaimer
:

I'm not a developer. I created this topic to help other users, to find a workarounds to the error. I'm not a developer. I created this topic to help other users, to find a way to dodge the error.
In addition I hope to raise awareness about this problem and help the devs with the information that is recopiled.

Screenshots Examples and Logcats of the error

Logcat: http://cloud.tapatalk.com/s/59...279...5-12-12-33.txt
Series of post in LineageOS Thread talking about the issue: https://forum.xda-developers.com/g5/...3611973/page48
Tipical Crash message after invoking a command:
[CODE]
08-23 19:04:28.670 12408 12408 I chatty : uid=0(root) app_process expire 847 lines
08-23 19:04:28.694 11748 11748 W Atfwd_Sendcmd: AtCmdFwd service not published, waiting... retryCnt : 4
08-23 19:04:28.715 12408 12408 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x9c in tid 12408 (app_process)
08-23 19:04:28.716 402 402 I chatty : uid=0(root) /system/bin/debuggerd expire 2 lines
08-23 19:04:28.777 12410 12410 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
08-23 19:04:28.778 12410 12410 F DEBUG : LineageOS Version: '14.1-20170811-UNOFFICIAL-cedric'
08-23 19:04:28.778 12410 12410 F DEBUG : Build fingerprint: 'motorola/lineage_cedric/cedric:7.1.2/NJH47F/43d07c81c5:userdebug/test-keys'
08-23 19:04:28.778 12410 12410 F DEBUG : Revision: '0'
08-23 19:04:28.778 12410 12410 F DEBUG : ABI: 'arm'
08-23 19:04:28.778 12410 12410 F DEBUG : pid: 12408, tid: 12408, name: app_process >>> app_process

The Following 3 Users Say Thank You to andyro2008 For This Useful Post: [ View ] Gift andyro2008 Ad-Free
 
 
2nd October 2017, 09:01 PM |#2  
Senior Member
Thanks Meter: 83
 
More
Great thread! My device is also affected and matches the mentioned specs.
2nd October 2017, 09:19 PM |#3  
ektus's Avatar
Senior Member
Flag Bayern
Thanks Meter: 46
 
More
I've got the recommended LineageSU method installed but normally don't use ADB. The only application I did try to use is Liveboot, where the test mode fails to start quite often. Transferring files via USB won't work on the first try, but I don't know how to tell if that is related. My device also is the European G5 with triple slot, 16GB and removable battery, type XT1676 or M2675. Currently running the unofficial LineageOS 14.1 build by @wzedlare from August, 2017.
3rd October 2017, 12:09 AM |#4  
andyro2008's Avatar
OP Senior Member
Flag Rosario
Thanks Meter: 89
 
More
Quote:
Originally Posted by ektus

I've got the recommended LineageSU method installed but normally don't use ADB. The only application I did try to use is Liveboot, where the test mode fails to start quite often. Transferring files via USB won't work on the first try, but I don't know how to tell if that is related. My device also is the European G5 with triple slot, 16GB and removable battery, type XT1676 or M2675. Currently running the unofficial LineageOS 14.1 build by @wzedlare from August, 2017.

The easiest way to check if a problem is caused by the segmentation fault is open a terminal emulator session (you can install any terminal emulator from the Playstore), and write:

su
logcat | grep "signal 11 (SIGSEGV)"


It will filter the logcat showing the Segmentation Fault errors. If you get new errors when performing an certain action, or opening certain app, it's affected by the error.

Enviado desde mi Moto G5 mediante Tapatalk
3rd October 2017, 06:10 AM |#5  
ektus's Avatar
Senior Member
Flag Bayern
Thanks Meter: 46
 
More
Quote:

The easiest way to check if a problem is caused by the segmentation fault is open a terminal emulator session (you can install any terminal emulator from the Playstore), and write:

su
logcat | grep "signal 11 (SIGSEGV)"

That one shows quite a number of results, at a first glance most with
Code:
signal 11 (SIGSEGV), code 1 (SEGV_MAPPER), fault addr 0x9c in tid xxxxx (zygote)
and one of each with
Code:
(app_process)
and
Code:
(Downloadmanager)
The fault addr is always the same except for the Downloadmanager where it's
Code:
code 2 (SEGV_ACCERR), fault addr 0x200006464
.

Regards
Ektus.
5th October 2017, 04:08 PM |#6  
Member
Flag Ulm
Thanks Meter: 12
 
More
Just for reference and to add to the discussion started in the Moto G5 TWRP thread, I never had any such issuess. My model is the 3GB dual sim version, bought at Amazon Germany. LineageOS with root addon.
The Following User Says Thank You to floydburgermcdahm For This Useful Post: [ View ] Gift floydburgermcdahm Ad-Free
6th October 2017, 10:56 AM |#7  
Senior Member
Thanks Meter: 83
 
More
Don't know if it is of importance but it never got to boot a clean system with changed filesystem. Tried to change /data to ext4, also tried it with /system as f2fs but nothing worked. This also happened with the new TWRP 3.1.1.
I also tried to flash phh supersu with noverity. But could only boot to bootloader which gave me an error.

Just wanted to share my attempts. I have limited knowledge of the fundamentals of segmentation so I just tried whatever I could find.
6th October 2017, 03:14 PM |#8  
andyro2008's Avatar
OP Senior Member
Flag Rosario
Thanks Meter: 89
 
More
Quote:
Originally Posted by floydburgermcdahm

Just for reference and to add to the discussion started in the Moto G5 TWRP thread, I never had any such issuess. My model is the 3GB dual sim version, bought at Amazon Germany. LineageOS with root addon.

F***! what will be the difference between your device and mine?

Did you ever use the rooted stock ROM?
Can you please, share these numbers from the sticker behind your battery, to know your exact device variant:


Thanks for your help!

Enviado desde mi Moto G5 mediante Tapatalk
6th October 2017, 03:45 PM |#9  
andyro2008's Avatar
OP Senior Member
Flag Rosario
Thanks Meter: 89
 
More
Anyone affected with segmentation fault error, o with a device with Dual SIM, please share these numbers.

A picture is not necessary, just the numbers. It's behind the battery

Enviado desde mi Moto G5 mediante Tapatalk
6th October 2017, 03:57 PM |#10  
Senior Member
Thanks Meter: 83
 
More
Here is mine.

Edit: if picture is too small, it is the same phone as yours...
Attached Thumbnails
Click image for larger version

Name:	IMG_20171006_165031.jpg
Views:	132
Size:	121.5 KB
ID:	4294233  
6th October 2017, 05:02 PM |#11  
TheFixItMan's Avatar
Senior Member
Flag London
Thanks Meter: 3,779
 
More
Just for reference my phone doesn't have any issues with root function

XT1675
2+16gb

All other numbers are the same

The FCC ID is the registration code for the United States
Federal Communications Commission
First three letters are grantee code - the rest is product code

I think the type relates to the battery size
The Following User Says Thank You to TheFixItMan For This Useful Post: [ View ] Gift TheFixItMan Ad-Free
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes