[ NO LONGER ACTIVELY BEING DEVELOPED - SORRY, READ THE POSTS FOR INFORMATION ]
Yes, you read that right. What we have here is a semi-functional CM11 (Kit Kat 4.4.4) for those with the locked boot loader using Safe Strap. I have been working on this for about a month, and this is what has come of that work. However, I need some help. I am not Android savvy enough to fix all of these problems to make this a fully functioning phone.
That being said, the phone does boot up and appears to mostly work. At this time, it is not a stable daily driver.
I did search all the threads, and I believe that this is not covered in another thread, so please forgive me if there is another CM11 thread that is for SS users on AT&T's locked boot loader phones. I don't see any.
How I got here:
Well, I wanted Cyanogenmod on my AT&T locked boot loader Safe Strapped phone. Every thread says we can't do that, and I just don't like hearing people tell me we can't do something and not provide any reasons. So I decided to try for myself. For the most part, they are right, but with enough perseverance, anything could happen.
I wanted to still use my phone as my daily driver, so I needed SafeStrap to work without having to bounce between kernels.
I was currently using Safe Strap with the NB1/NC1 kernels, and running Joe-Tech's GPE 4.4.4, so I decided that I should start with a 4.4.4 variant of CM, which lead me to CM11. I tried all of them, the nightlies, the home builds, the official builds, and I stumbled across one particular CM11 nightly (20151115) that would boot and then crash as soon as it booted. So I decided to use that as a base.
Reviewing the situation/logs/errors after each crash, I slowly removed, edited, or replaced something until it would not receive that error and would move on to the next error. By the grace of God it was slowly coming together! Hence why the built in camera app is gone and replaced with open camera, etc.
If we get this working, we may be able to use these hacks or tricks to get higher versions such as CM12 or perhaps (fingers crossed) CM13. I know this is kind of lofty, but perhaps we could get something going here. Once we identify the key problems, perhaps we can also apply these tricks to other AOSP variants, such as Slim Roms.
However, let's stick to putting one foot in front of the other right now and focus on CM11.
The Setup:
AT&T boot loader locked phone with NB1/NC1 kernel and modules flashed.
Safe Strap 3.75, currently using Rom Slot 1 for this, as my daily driver is on the stock slot, however I have done it both ways, and it works either way.
Download the below CM11 zip and put it on your phone.
In Safe Strap, choose stock or rom slot, then wipe and flash the CM11 zip.
After flashing the zip, flash the wifi modules for your kernel.
Once it boots:
Go to the settings->about phone->tap on build to enable developer mode.
Then, in developer menu, choose "Disable HW overlays" to always use GPU for screen compositing. (To improve graphics performance, you may find playing with the other graphics options help also.)
Then disable the lock screen by changing "slide" to "none" (To prevent sleep of death until we fix it.) Thanks @Sterben Pistole
Temporary Root:
Simply open the KingoRoot app and click on the padlock. This will take roughly 3-5 minutes, but it will successfully give you root permissions. After reboot, root permission will be lost, but you can simply open KingoRoot and give yourself root permissions again.
Download link:
http://www.mediafire.com/download/at7iw100uawi74k/CM11-20160322-SS.zip
OR This version, which includes the qcom scripts (testing):
http://www.mediafire.com/download/nb98rtkk2j0vjpa/CM11-20160326-SS.zip
Screenshots:
Boot animationhttp://www.mediafire.com/view/wgn5m57mjk5irvm/IMG_20160310_165320.jpg
Boot animationhttp://www.mediafire.com/view/7k8y591adrwsscw/IMG_20160310_162451.jpg
Settings http://www.mediafire.com/view/lrni6kpw04oi43d/IMG_20160310_165713.jpg
About phone1http://www.mediafire.com/view/8hb8slcwxgqxycl/IMG_20160310_165603.jpg
About phone2http://www.mediafire.com/view/ugra6jdeiz6wro5/IMG_20160310_165610.jpg
Dev. optionshttp://www.mediafire.com/view/qvd2q9uwd2vv8pn/IMG_20160310_165652.jpg
Home screen2http://www.mediafire.com/view/5h9vg4wxaacfpio/IMG_20160310_165742.jpg
Menu screenhttp://www.mediafire.com/view/55bvds7k08b2nkk/IMG_20160310_165548.jpg
Home screen1http://www.mediafire.com/view/qkod20qyyv3fska/IMG_20160310_165449.jpg
Check the following posts for issues and known working items. If you have an idea of how to solve the item, the best thing to do would be to download this CM11 and try it out. If you can't do that, or if you did and found a solution, just post your thoughts/trials/2 cents here in the forum and we can hopefully integrate it into the final product!
Team Members and Contributors: (People who have contributed to the project.)
@Sterben Pistole
@Evant28
Beta testers: @DeadlySin9
Huge special thanks to @jmsq and @Joe-Tech for permission to use things we need from their GPE roms!
Known problems
Here is a list of the Known issues:
SYSTEM:
-USB - MTP, UMS, and PTP are not currently working properly. The PTP may be working, but my Linux computer cannot connect to it. The UMS will not mount. The MTP says the connection is taking too long and resets (on my computer).
-Sleep of Death - Lock screen causes sleep of death and reboot errors. Must disable the lock screen to prevent this. Thanks @Sterben Pistole !
-Mounting external SD card - Currently the extSdCard is mounted, however it requires root privileges to use it.
-SU - Currently, @Sterben Pistole has found a SU temporary work around, however, it is lost on reboot.
-GPS - Not currently functioning.
-APN settings - Since that portion of the settings crashes, I thought we could edit the xml file directly and set a default option for the carrier of choice. Not ideal, but perhaps a good work around?
-TeleService.apk has been removed, it causes too many crashes, this apk is really important for phone calls/radio control, so this would really need to be replaced.
APPS:
-GPS Status - The app works, but GPS does not appear to be functioning.
-Messaging - Crashes when you open it. I think due to settings issue with connectivity to network.
-Settings - Mostly works, a few settings options cause it to crash, most importantly, the mobile network settings for APN's etc. crashes.
-Torch - Torch apk does not function at this time. Found that during CM kernel init, changes are made to facilitate the torch.apk, which are not done by the stock kernel init. However, it is possible that these could be written in as a init.d script.
Known Working
Here is a list of the known working:
SYSTEM:
-ADB - Fully functional.
-Audio - Makes sounds when you tap on buttons, appears to work fine.
-Bluetooth - Fully functional, used it to tether internet to use the browser, worked great.
-Bootlogo - Fully functional.
-Bootup - Boots all the way up the first time.
-Camera - Fully functional.
-External SD Card - Currently mounts, but requires super user privileges to use it.
-Internal Storage - Fully functional.
-Themes - @Sterben Pistole has verrified that different themes work.
-Wifi - Remember to flash your modules in SS! Thanks @Sterben Pistole
APPS:
-Apollo - Works great.
-Browser - Works great when you have an active network connection.
-Calculator - Works great.
-Calendar - Works great.
-Camera - Works great. Thanks @Sterben Pistole
-Clock - Works great.
-CM File Manager - Now working!
-DSP Manager - Appears to work.
-Email - Appears to work.
-Gallery - Works great!
-Movie Studio - Appears to work.
-People - Appears to work.
-Phone - Appears to work, but due to a settings issue with setting the carrier, I could not connect to make a phone call.
-Terminal Emulator - Works great.
-Voice Dialer - App opens, don't know if it works as I did not add my contacts.
Change log
Code:
3/26/16
-New QCOM script testing download link CM11-20160326-SS.zip
-Removed two of the scripts, the BT, and the BTDUN scripts. Those two scripts cause the Bluetooth to fail. Now the bluetooth works just as it did before the scripts were added.
3/24/16
-Alternate CM11-20160324-QCOMSCRIPTS-SS.zip download link
-Our NB1/NC1 kernel will need certain settings, services, and scripts run to be fully functional in regards to the hardware. Our kernel, through init, was calling for several qcom shells that did not exist. They have been added into this zip. Although it does not immediately solve any issues, it may be worth trying some of the things in these scripts, thus the original 20160322 zip is still available for download.
3/22/16
-New CM11-20160322-SS.zip download link
-Removed /recovery, boot.img, and file_context from zip as well as from updater-script. This makes it smaller and quicker to flash to your phone.
-Removed Loki script from installation script, as we do not need it on SS.
3/16/16
-New CM11-20160316-SS.zip download link
-External SD card now is auto mounted to /storage/extSdCard, however, it requires super user permission to use it.
-Dropped UltraExplorer and added ES File Manager for maintenance tools. Not intended for final product.
3/15/16
-New CM11-20160315-SS.zip download link
-Added Kingoroot for simpler one click rooting, root is still temporary.
(We had already achieved temporary root, but it was more complicated to activate than this. Kingoroot can re-root after restarting your phone.)
3/14/16
-New CM11-20160314-SS.zip download link
-Subtle changes in build.prop, fixed model # in about phone.
-Added TowelRoot, UltraExplorer, and Pushbullet for maintenance tools. Not intended for final product.
3/13/16
-New CM11-20160313-SS.zip download link.
-Camera2.apk fixed, open camera removed. Thanks [user=6053184]@Sterben Pistole[/user]
-CM File Manager fixed, removed ES File explorer.
3/12/16
-New CM11-20160312-SS.zip download link.
-WiFi Fixed, be sure to flash the appropriate modules in SS! Thanks [user=6053184]@Sterben Pistole[/user] !
3/11/16
-New CM11-20160311-AKLU-SS.zip download link with fix for internal phone memory "sdcard" mounting with SS.
-Sleep of death and reboot error workaround - Thanks [user=6053184]@Sterben Pistole[/user]
- Disable the lock screen to prevent sleep of death and to allow future reboots. We will want to disable or fix the lock screen function, but the workaround allows us to continue working at this time!
3/10/16
-Uploaded to XDA for assistance from other members and to share what has been done so far.
2/26/16
-Created new boot animation reflecting SS and CM.
2/24/16
-Removed Torch.apk, camera.apk, camera2.apk due to issues.
-Added OpenCamera - works great, and you can choose where to save pics.
-Added /system/lib/modules, but still cannot insmod them, due to no root permission.
-Tried Kingroot, will not root without internet connection, used bluetooth tether, but it did not recognize internet connection, even though browser worked online.
-Tried SuperSU, but it cannot update the binary.
2/23/16
-Removed teleservices.apk from /system/priv-app due to issues.
-Edited build.prop
-Now the crrashing has stopped, however we cannot use data or make phone calls without teleservices.apk. Perhaps we can steal it from another rom?
-Camera app crashes when accessing the camera.
-Settings sometimes crash.
-File manager could not find any storage devices, internal or external. Replacd with ES File Manager and now can see all files in mounted partitions.
-sdcard and extSdCard are not mounted at boot. Write script to do that?
-GPU needed set to no HW overlays in dev. options to prevent graphics errors/tearing.
-Bluetooth tests sat! :)
2/22/16
-Installed CM11 nightly through SS, but it constantly crashes.
I'm going to be experimenting with your build as I've started working on the same type of project as of last week. I'm going to see what I can do to fix a couple of the crashes and report back to you.
EDIT: TO ALL, IF YOU DON'T KNOW WHAT YOU'RE DOING DO NOT INSTALL THIS. IT IS NOT A DAILY DRIVER AT ALL.
EDIT 2: As I suspected, if you go into the settings and disable the lockscreen it won't go into the sleep of death.
Wow, this looks great! I'd love to help with this if I can.
Rebooting works flawlessly if you turn off the lock screen. As for the internal and external storage not mounting properly, you need a wrapper script for that. I think @jmsq made one a while ago, but he's not active anymore.
Sterben Pistole said:
I'm going to be experimenting with your build as I've started working on the same type of project as of last week. I'm going to see what I can do to fix a couple of the crashes and report back to you.
EDIT: TO ALL, IF YOU DON'T KNOW WHAT YOU'RE DOING DO NOT INSTALL THIS. IT IS NOT A DAILY DRIVER AT ALL.
EDIT 2: As I suspected, if you go into the settings and disable the lockscreen it won't go into the sleep of death.
Click to expand...
Click to collapse
Tested, works great! Updated thread! Great work!
Now we should replace or fix the lock screen. At least now we know what the problem was. Great insight!
Evant28 said:
Wow, this looks great! I'd love to help with this if I can.
Click to expand...
Click to collapse
Evant28,
You bet, if you can, download the files and play around with it. Let us know if you find any way to fix anything and we'll put it to work.
Sterben Pistole said:
Rebooting works flawlessly if you turn off the lock screen. As for the internal and external storage not mounting properly, you need a wrapper script for that. I think @jmsq made one a while ago, but he's not active anymore.
Click to expand...
Click to collapse
Great find on the disabled lock screen allowing reboots! I've added it to the instructions after booting up the first time. I am breaking down @jmsq GPE 4.4.3 rom to look at the script. I've also pm'd to ask their permission.
To be fair, some of those people saying it wasn't possible did specify that it would require plenty of work that most people don't want to/can't do. Kitkat probably is the best option since we did get those GPE's working though, and I certainly applaud your efforts. I'm no developer myself or I'd help out, but I think a good way to get some things working since we can't change the kernel is to try and build and load modules for it using bypasslkm. I don't know the viability of that, but I know at least for the storage issue I've seen a case where a module was loaded in order to allow mounting.
*deleted*
DeadlySin9 said:
To be fair, some of those people saying it wasn't possible did specify that it would require plenty of work that most people don't want to/can't do. Kitkat probably is the best option since we did get those GPE's working though, and I certainly applaud your efforts. I'm no developer myself or I'd help out, but I think a good way to get some things working since we can't change the kernel is to try and build and load modules for it using bypasslkm. I don't know the viability of that, but I know at least for the storage issue I've seen a case where a module was loaded in order to allow mounting.
Click to expand...
Click to collapse
Does BypassLKM work on 4.4.2? I know it works on 4.3, because that's what it was built for, but if it does it would definitely help a good bit.
Mounting of sdcard fixed.
DeadlySin9 said:
To be fair, some of those people saying it wasn't possible did specify that it would require plenty of work that most people don't want to/can't do. Kitkat probably is the best option since we did get those GPE's working though, and I certainly applaud your efforts. I'm no developer myself or I'd help out, but I think a good way to get some things working since we can't change the kernel is to try and build and load modules for it using bypasslkm. I don't know the viability of that, but I know at least for the storage issue I've seen a case where a module was loaded in order to allow mounting.
Click to expand...
Click to collapse
Internal phone storage "sdcard" mounting is fixed, new download link in OP. Turns out SS roms use a special sdcard mounting script. Thanks for the suggestions though, we need all the help we can get!
Wow great progress! I'll be installing as soon as I get home. Now that internal storage is fixed does WiFi work?
Evant28 said:
Wow great progress! I'll be installing as soon as I get home. Now that internal storage is fixed does WiFi work?
Click to expand...
Click to collapse
Not at the moment. Even if Wi-Fi was working this would still be far off from being a stable daily driver. I'll post an update if I figure something out.
EDIT: WIFI IS NOW UP AND RUNNING! Modules are needed as always.
EDIT 2: Uploading build with working Wi-Fi as I am typing this. I have slow Wi-Fi so it'll be a while ;-;
EDIT 3: Got root working, but it's not out of the box. You need to flash SU in Safestrap right after modules, download towelroot, make it rain, and then install SU binary's from SU app.
EDIT 4: Root is only temporary. After a reboot it disappears. Also, theme's work great
Sterben Pistole said:
Not at the moment. Even if Wi-Fi was working this would still be far off from being a stable daily driver. I'll post an update if I figure something out.
EDIT: WIFI IS NOW UP AND RUNNING! Modules are needed as always.
EDIT 2: Uploading build with working Wi-Fi as I am typing this. I have slow Wi-Fi so it'll be a while ;-;
EDIT 3: Got root working, but it's not out of the box. You need to flash SU in Safestrap right after modules, download towelroot, make it rain, and then install SU binary's from SU app.
EDIT 4: Root is only temporary. After a reboot it disappears. Also, theme's work great
Click to expand...
Click to collapse
Just about to flash, did you by chance get the build uploaded? Awesome work!
Evant28 said:
Just about to flash, did you by chance get the build uploaded? Awesome work!
Click to expand...
Click to collapse
uploaded wrong file lol There you go btw, there's still no service.
EDIT: Reuploading... Uploaded the original one by accident :/
Sterben Pistole said:
Does BypassLKM work on 4.4.2? I know it works on 4.3, because that's what it was built for, but if it does it would definitely help a good bit.
Click to expand...
Click to collapse
I'm pretty sure someone got it working while everyone was looking into getting a working kexec module. I'll see if I can't find a link somewhere.
EDIT: Still searching, but there are also directions on how to point it to the right address and compile it in the bypasslkm thread. Surge1223 built one for 4.4.2, but it's for verizon NC5 and I haven't found the link yet just found it here.
DeadlySin9 said:
I'm pretty sure someone got it working while everyone was looking into getting a working kexec module. I'll see if I can't find a link somewhere.
EDIT: Still searching, but there are also directions on how to point it to the right address and compile it in the bypasslkm thread. Surge1223 built one for 4.4.2, but it's for verizon NC5 and I haven't found the link yet just found it here.
Click to expand...
Click to collapse
http://ubunmobile.blogspot.com/2015/03/moddev-enable-unsigned-kernel-modules.html Here's a link to what seems like it's what we're looking for.
So today some process called zygote64 tried to access root and SuperSU prompted to allow or deny the request. This is the first time I've seen this process ever in my life.
Anyone have clue as to if it's safe or what it represents?
Google search showed some vanuralibilities regarding zygote64 but it really didn't have alot of coverage.
I got this today on my OnePlus 3 don't know what it is
---------- Post added at 02:46 PM ---------- Previous post was at 02:14 PM ----------
Accidentally granted it permission after it appeared on the initial reboot after a TWRP backup. Went back and re-restored the same backup but it didn't appear this time. Would love to find out what the heck it is.
reiichiroh said:
I got this today on my OnePlus 3 don't know what it is
Accidentally granted it permission after it appeared on the initial reboot after a TWRP backup. Went back and re-restored the same backup but it didn't appear this time. Would love to find out what the heck it is.
Click to expand...
Click to collapse
I think it must be one of the ROOT apps that we are using. See if you have any apps in common with mine.
Nova Launcher
Automate
FKUpdater ( franco kernel updater)
Tried restoring it 5 plus times and didn't see it again. I even reviewed the SuperSU logs.
Here are my root apps:
YouTube adaway
System app mover
Greenify
Amplify
Better battery stats
Ex kernel manager
Busy box pro
SuperSU pro
Flux
TWRP manager
Adaway
Root cloak
Xposed installer 3.1
Paragon NTFS HFS
Notification Slider
Sent from my ONEPLUS A3000 using Tapatalk
Did you guys manage to find out what it is?
I got this on my OP3 today.
Zygote is the display server of android. (Think X11/Xorg on Linux)
No idea why it would require root rights. (It should have the required rights by default because its a system component).
Malware infected it maybe?
tauio111 said:
Zygote is the display server of android. (Think X11/Xorg on Linux)
No idea why it would require root rights. (It should have the required rights by default because its a system component).
Malware infected it maybe?
Click to expand...
Click to collapse
Zygote is the Init process on Android, it doesnt need root to do anything... it sounds like some malware is called like that.
Update: Android 7.1.1 stock rooted. I was still asked for zygote for root permission. this time instead of it being zygote64 it was zygote. Still haven't found a solution to this. if anyone can shine a light into this.
in doubt i say Malware !!!
Yeah, I just got it today on CM14 for Find 7a December 18th build. I wasn't sure what it was so I just denied it permissions. After a quick Google search, it seems sketchy that a component of the system wouldn't already have root permission.
I also just checked SuperSU and didn't see any app that had root access denied to it, so I wonder what's actually going on here.
I ended up purging my phone and reinstalling everything.
Haven't been asked for that in 14.1. Wiped everything and flashed everything again.
one things i figured out is zygote is coming with whatsapp as since i refused whatsapp su permission by than zygote is asking for su permission .. zygote is a project is being used by whatsapp for stopping the mod or to retrive the logs to block them
I got this request on my Nexus 5x for zygote64 once the day before yesterday when I tried to switch from wifi to mobile data with a self-designed toogle from "Power Toogles", which needs root rights to do that. I did nothing and let the SuperSU message dissappear. Wifi were successfully disabled but mobile data didn't get enabled, even not after several tries. I use this buttons every day and it was never a problem to enable/disable mobile data with it.
There was no entry regarding this root request in the SuperSU logs! So I checked what happens when the root request is ignored like I did it with the zygote64 request. I removed "PowerToogles" from the allowed-list in SuperSU and tried to enable mobile data via the toogle. The SuperSU request came up (now for "PowerToolges" not for "zygote64"), I ignored it and after that I checked the SuperSU logs. There was a "Deny" entry for this request. Why is there no deny entry for the zygote64 request?
The phone is nearly new (Christmas present), and were updated to the newest Stock Android 7.1.1 one and a half week ago. I use only the Google Store to download and install apps, and the phone contains nearly the same apps which I used on my previous phone, where I never had this problem.
I'm a bit confused where this request comes from, but I don't think that it is from a adware app or something like this. I could imagine that it has to do with SuperSU and it's harmless. But I'm not an Android expert.
Yeah,
I literally just got this right now through an su prompt while listening to Spotify. At first I granted permission for it, but later went to the Su app I disabled it and found this post. Regarding its connections to WhatsApp, I recently opened up the app after a long period of time, if that has an effect, even though it's a non root app. Keep in mind I just restored yesterday's nandroid backup coming from the Nexus 5X Lineage OS 14.1 nightly build. I don't know if that has anything to do with it as well as me changing my ElementalX kernel profile to Ghost pepper. That's all lol I'm not trying to get hacked.
I have this one too on xiaomi's miui 7.1.19 and no WhatsApp at all.
C:\Windows\System32>adb shell
adb server is out of date. killing...
* daemon started successfully *
[email protected]:/ $ ps | grep zygote
root 453 1 6528 1288 __skb_recv 0000000000 S zygote
root 665 1 2143808 60040 poll_sched 0000000000 S zygote64
root 672 1 1579612 32724 poll_sched 0000000000 S zygote
root 2872 672 36072 2364 futex_wait 0000000000 S xposed_zygote_service
[email protected]:/ $
Click to expand...
Click to collapse
Does dirty flash of the ROM replaces the zygote files (and I remove xposed beforehand, then reinstall expose later on)
---------- Post added at 12:30 PM ---------- Previous post was at 12:10 PM ----------
I restarted the phone and zygote64 no longer appears in supersu's log...
I've been seeing this over the last couple days, and never approving it. It seems "spontaneous" in that it's not related to UI-driven activity.
(I'm running OmniROM 7.1.1 with very heavily trimmed GApps, no XPosed framework in place)
I only see "zygote64" in the SuperSU apps, and nothing in the SuperSU logs.
The hints I have so far are:
Code:
bullhead:/ # ps | fgrep 64
[...]
root 491 1 2140052 26968 poll_sched 786e1c9cc8 S zygote64
[...]
u0_a64 1364 491 1578476 38536 SyS_epoll_ 786e1c9ba8 S com.teslacoilsw.notifier
[...]
Given the number of process with ppid of 491, and that pid 492 is "zygote", I've got to think that "zygote64" is the 64-bit parent process for apps.
Just got this too (zygote64). Running 6.0.1 cause I love xposed. So this shouldn't be related to the OS.
Recently started getting same requests from com.android.settings which is my settings app. Been on the sand Rom without updates or dirty flashes since November (Running buttery-smooth with N-ify and other modules.) And this is the first time I get this request.
Thus, I can safely make the assumption that we got a potential virus...
Edit: I'm on a 6P and when I denied access to both settings and zegote64, I had no differences in phone operation. No "failed to switch from Wi-Fi to Data" like oth3rd are claiming. So I'm just going to keep rejecting until we get a firm details on what that thing is
---------- Post added at 07:08 PM ---------- Previous post was at 06:58 PM ----------
Gonna run a log cat until I get home, where I'll look more into it...
jeffsf said:
I've been seeing this over the last couple days, and never approving it. It seems "spontaneous" in that it's not related to UI-driven activity.
(I'm running OmniROM 7.1.1 with very heavily trimmed GApps, no XPosed framework in place)
I only see "zygote64" in the SuperSU apps, and nothing in the SuperSU logs.
The hints I have so far are:
Code:
bullhead:/ # ps | fgrep 64
[...]
root 491 1 2140052 26968 poll_sched 786e1c9cc8 S zygote64
[...]
u0_a64 1364 491 1578476 38536 SyS_epoll_ 786e1c9ba8 S com.teslacoilsw.notifier
[...]
Given the number of process with ppid of 491, and that pid 492 is "zygote", I've got to think that "zygote64" is the 64-bit parent process for apps.
Click to expand...
Click to collapse
It's highly unlikely that you will see whatever is asking for in the process list as it may quit once it gets access denied.
Extending the prompt time may give you a chance to connect the device to your PC and use adb shell to look for it, but seeing as it occurs spontaneously I doubt you will catch it on time.
The only thing you may look for elsewhere is a app_process32 or app_process64 file, which is the actual name of the zygote binary (zygote is the service's name)
Also, per init.zygote64_32.rc, both versions of the service should already run as root, and unless this is a bug; which could be possible if somehow app_process32 or app_process64 do not recognize their parent (the one started by init) and tries to restart as the new parent.
I just saw this popping up on my phone and started scouring the net which brought me here. Anyone yet know exactly what this is?
---------- Post added at 08:46 AM ---------- Previous post was at 08:14 AM ----------
I denied it super user permissions though, and nothing seems to be broken. I just remembered I updated whatsapp and gbwhatsapp few hours ago.
Hi, I have the same thing going on on my phone. And I can tell so far that it has absolutely nothing to do with WhatsApp as I never ever had WhatsApp or any Facebook related app installed on my phone. I even hadn't installed any app for a longer time before the first appearance. Maybe there is another way of infection (if it is a malware).