[Q] G900F - Boot problem: Failed to mount emulated storage - Galaxy S 5 Q&A, Help & Troubleshooting

Hi there,
I'm new here and this is my first post.
So, a couple of weeks ago, I rooted my phone (BOD3) with CF Auto Root. Everything went fine and I was happily using it until two days ago, when it would not boot up properly anymore. It goes just beyond the logo but keeps telling me "Unfortunately application <insert name> has stopped". I can use the power button to shut it down, but eventually it always restarts on itself.
I then flashed CWM revovery to dig into it, and dumpstate_app_native.txt.gz gave me lots and lots of these errors:
06-15 18:30:29.512 1303 1303 E Zygote : MountEmulatedStorage()
06-15 18:30:29.512 1303 1303 E Zygote : v2
06-15 18:30:29.512 1303 1303 E cutils : Failed to chmod(/mnt/shell/emulated/0, 0): Permission denied
06-15 18:30:29.512 1303 1303 I libpersona: KNOX_SDCARD checking this for 1000
06-15 18:30:29.512 1303 1303 I libpersona: KNOX_SDCARD not a persona
06-15 18:30:29.522 1303 1303 W Zygote : Failed to mount emulated storage: 13
06-15 18:30:29.522 1303 1303 E Zygote : Cannot continue without emulated storage
06-15 18:30:29.522 1303 1303 F art : art/runtime/jni_internal.cc:771] JNI FatalError called: RuntimeAbort
06-15 18:30:29.522 1300 1300 I dumpstate: begin
06-15 18:30:29.522 1303 1303 W libbacktrace: virtual bool BacktraceThread::Unwind(size_t, ucontext_t*): tgkill 325 failed: No such process
06-15 18:30:29.532 1032 1086 D ResourcesManager: creating new AssetManager and set to /system/priv-app/MtpApplication/MtpApplication.apk
06-15 18:30:29.532 1032 1086 I ActivityManager: Start proc com.android.settings for broadcast com.android.settings/.SettingsIntentReceiver: pid=1303 uid=1000 gids={41000, 9997, 3003, 1007, 1028, 1015, 1023, 2001, 1024, 3001, 3002, 1001} abi=armeabi-v7a
06-15 18:30:29.542 1303 1303 W libbacktrace: virtual bool BacktraceThread::Unwind(size_t, ucontext_t*): tgkill 325 failed: No such process
06-15 18:30:29.542 1303 1303 F art : art/runtime/runtime.cc:286] Runtime aborting...
06-15 18:30:29.542 1303 1303 F art : art/runtime/runtime.cc:286] Aborting thread:
06-15 18:30:29.542 1303 1303 F art : art/runtime/runtime.cc:286] "main" prio=5 tid=1 Native
06-15 18:30:29.542 1303 1303 F art : art/runtime/runtime.cc:286] | group="" sCount=0 dsCount=0 obj=0x86517ef0 self=0xb4f07800
06-15 18:30:29.542 1303 1303 F art : art/runtime/runtime.cc:286] | sysTid=325 nice=0 cgrp=default sched=0/0 handle=0xb6fddec8
06-15 18:30:29.542 1303 1303 F art : art/runtime/runtime.cc:286] | state=? schedstat=( 0 0 0 ) utm=0 stm=0 core=0 HZ=100
06-15 18:30:29.542 1303 1303 F art : art/runtime/runtime.cc:286] | stack=0xbe67e000-0xbe680000 stackSize=8MB
06-15 18:30:29.542 1303 1303 F art : art/runtime/runtime.cc:286] | held mutexes= "abort lock" "mutator lock"(shared held)
06-15 18:30:29.542 1303 1303 F art : art/runtime/runtime.cc:286] kernel: (couldn't read /proc/self/task/325/stack)
06-15 18:30:29.542 1303 1303 F art : art/runtime/runtime.cc:286] native: (backtrace::Unwind failed for thread 325)
06-15 18:30:29.542 1303 1303 F art : art/runtime/runtime.cc:286] at com.android.internal.os.Zygote.nativeForkAndSpecialize(Native method)
06-15 18:30:29.542 1303 1303 F art : art/runtime/runtime.cc:286] at com.android.internal.os.Zygote.forkAndSpecialize(Zygote.java:96)
06-15 18:30:29.542 1303 1303 F art : art/runtime/runtime.cc:286] at com.android.internal.os.ZygoteConnection.runOnce(ZygoteConnection.java:247)
06-15 18:30:29.542 1303 1303 F art : art/runtime/runtime.cc:286] at com.android.internal.os.ZygoteInit.runSelectLoop(ZygoteInit.java:1284)
06-15 18:30:29.542 1303 1303 F art : art/runtime/runtime.cc:286] at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1190)
06-15 18:30:29.542 1303 1303 F art : art/runtime/runtime.cc:286] Dumping all threads without appropriate locks held: thread list lock mutator lock
06-15 18:30:29.542 1303 1303 F art : art/runtime/runtime.cc:286] All threads:
06-15 18:30:29.542 1303 1303 F art : art/runtime/runtime.cc:286] DALVIK THREADS (1):
06-15 18:30:29.542 1303 1303 F art : art/runtime/runtime.cc:286] "main" prio=5 tid=1 Native
06-15 18:30:29.542 1303 1303 F art : art/runtime/runtime.cc:286] | group="" sCount=0 dsCount=0 obj=0x86517ef0 self=0xb4f07800
06-15 18:30:29.542 1303 1303 F art : art/runtime/runtime.cc:286] | sysTid=325 nice=0 cgrp=default sched=0/0 handle=0xb6fddec8
06-15 18:30:29.542 1303 1303 F art : art/runtime/runtime.cc:286] | state=? schedstat=( 0 0 0 ) utm=0 stm=0 core=0 HZ=100
06-15 18:30:29.542 1303 1303 F art : art/runtime/runtime.cc:286] | stack=0xbe67e000-0xbe680000 stackSize=8MB
06-15 18:30:29.542 1303 1303 F art : art/runtime/runtime.cc:286] | held mutexes= "abort lock"
06-15 18:30:29.542 1303 1303 F art : art/runtime/runtime.cc:286] kernel: (couldn't read /proc/self/task/325/stack)
06-15 18:30:29.542 1303 1303 F art : art/runtime/runtime.cc:286] native: (backtrace::Unwind failed for thread 325)
06-15 18:30:29.542 1303 1303 F art : art/runtime/runtime.cc:286] at com.android.internal.os.Zygote.nativeForkAndSpecialize(Native method)
06-15 18:30:29.542 1303 1303 F art : art/runtime/runtime.cc:286] at com.android.internal.os.Zygote.forkAndSpecialize(Zygote.java:96)
06-15 18:30:29.542 1303 1303 F art : art/runtime/runtime.cc:286] at com.android.internal.os.ZygoteConnection.runOnce(ZygoteConnection.java:247)
06-15 18:30:29.542 1303 1303 F art : art/runtime/runtime.cc:286] at com.android.internal.os.ZygoteInit.runSelectLoop(ZygoteInit.java:1284)
06-15 18:30:29.542 1303 1303 F art : art/runtime/runtime.cc:286] at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1190)
06-15 18:30:29.542 1303 1303 F art : art/runtime/runtime.cc:286]
06-15 18:30:29.542 1303 1303 F art : art/runtime/runtime.cc:286]
06-15 18:30:29.542 1303 1303 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 1303 (main)
(process 325 was zygote, btw)
What are my options here? Can I fix this permission problem from recovery? I can't adb while booting, because I can't unlock the phone.
Safe mode is not working either. I flushed cache and dalvik cache to no avail.
I did of course install Titanium, but it backed up to internal storage (/data/media/0/TitaniumBackup) So I'm worried factory-reset/wipe would eventually also delete it. Would it? (However, I did adb pull /system and /data, no nandroid yet, but then it probably wouldn't help anyways..). Also, the last titanium backup was done just hours before this problem appeared, so it could already be part of the backup.
So, what can I do at this point without loosing any of my data?

I assume you are using Philz CWM recovery and afaik there is a 'fix permissions' option somewhere, have you tried that?
Wait, your internal storage is located in /storage/emulated/legacy and that is where Titanium backup's default backup location is located at. I don't see how it could save in /data partition but you can specify the backup location from TI settings.
As far as I can tell, you don't need to wipe data, the first error (which probably is the cause of the other errors) appears as a permissions error and after you try fixing permissions from cwm the issues will probably disappear.
Sent from my SM-G900F using Tapatalk

Thanks for your reply!
Yes, its PhilZ, and I can't seem to find "Fix permission", but wasn't that used to fix permissions on apps, that were moved to sdcard before android supported it natively?
I think I didn't make clear, what I was referring to by /data. I was talking about userdata, which in recovery gets mounted to /data:
/dev/block/platform/msm_sdcc.1/by-name/userdata on /data type ext4
In this directory there is an other directory called data which contain all the app data. I thought /storage/emulated/legacy and /storage/emulated/0/ both were symbolic links to /data/media/0 (which is referred to as "internal sdcard", iirc) I have not looked at the mounts when it was running though, so I don't know where userdata would get mounted to.
Having a strong background in linux, this sure looks messy...
The permissions of the directories look sane to me:
drwxrwx--- 5 media_rw media_rw 4096 Jan 1 00:00 media
drwxrwx--- 52 media_rw media_rw 4096 Jan 1 23:24 0
Maybe it would help, if I just flash the stock rom and root again? That wouldn't wipe userdata, would it?

Rastaban said:
Thanks for your reply!
Yes, its PhilZ, and I can't seem to find "Fix permission", but wasn't that used to fix permissions on apps, that were moved to sdcard before android supported it natively?
I think I didn't make clear, what I was referring to by /data. I was talking about userdata, which in recovery gets mounted to /data:
/dev/block/platform/msm_sdcc.1/by-name/userdata on /data type ext4
In this directory there is an other directory called data which contain all the app data. I thought /storage/emulated/legacy and /storage/emulated/0/ both were symbolic links to /data/media/0 (which is referred to as "internal sdcard", iirc) I have not looked at the mounts when it was running though, so I don't know where userdata would get mounted to.
Having a strong background in linux, this sure looks messy...
The permissions of the directories look sane to me:
drwxrwx--- 5 media_rw media_rw 4096 Jan 1 00:00 media
drwxrwx--- 52 media_rw media_rw 4096 Jan 1 23:24 0
Maybe it would help, if I just flash the stock rom and root again? That wouldn't wipe userdata, would it?
Click to expand...
Click to collapse
Ah okay, now I understand.
Fix permissions when I used it worked for the whole system, so I don't think it's solely for the purpose of moved apps, however it probably also has the function you said.
Yeah that's what I would do in this situation, unless you can't think of another solution you should flash a stock rom again.
Sent from my SM-G900F using Tapatalk

Akalsemann said:
Ah okay, now I understand.
Yeah that's what I would do in this situation, unless you can't think of another solution you should flash a stock rom again.
Click to expand...
Click to collapse
Did that and it worked. Not funny, but once I enter recovery (no matter if stock or PhilZ) it messes up my phone again. I flashed several times to confirm this. Any idea, what I am missing here?

Related

Verification failed on class ART / Dalvik

I'm getting a weird error using the Aviary SDK for some users who are using ART. I'm confused on why this happening (only on 4.4.x obviously) as the app works perfectly when calling this SDK on Dalvik. Any one have any have any ideas to solve this? Aviary claims it's PhoneGap/Cordova issue (our base), but I don't think that's the issue here as it only fires when the activity is launched.
HTML:
06-06 09:45:36.037: D/Aviary(27701): Pictures folder: /storage/emulated/0/Pictures
06-06 09:45:36.037: D/Aviary(27701): show
06-06 09:45:36.037: D/Aviary(27701): VERSION => 3.0.4
06-06 09:45:36.037: D/Aviary(27701): VERSION => 157
06-06 09:45:36.041: I/ActivityManager(741): START u0 {dat=file:///storage/emulated/0/DCIM/Camera/1402062335694.jpg cmp=com.XXXX.app/com.aviary.android.feather.FeatherActivity (has extras)} from pid 27701
06-06 09:45:36.054: W/CursorWrapperInner(27701): Cursor finalized without prior close()
06-06 09:45:36.058: I/CordovaLog(27701): Changing log level to ERROR(6)
06-06 09:45:36.087: I/ActivityManager(741): Start proc com.XXXX.app:standalone for activity com.XXXX.app/com.aviary.android.feather.FeatherActivity: pid=28285 uid=10060 gids={50060, 3003, 1028, 1015}
06-06 16:20:12.473 W/art (188): Could not get current activity
......
06-06 09:45:36.320: E/art(28285): Verification failed on class com.aviary.android.feather.library.external.tracking.LocalyticsSession$UploadHandler in /data/app/com.XXXXXXX.apk because: Verifier rejected class com.aviary.android.feather.library.external.tracking.LocalyticsSession$UploadHandler due to bad method void com.aviary.android.feather.library.external.tracking.LocalyticsSession$UploadHandler.deleteBlobsAndSessions(com.aviary.android.feather.library.external.tracking.LocalyticsProvider)
06-06 09:45:36.320: E/AndroidRuntime(28285): FATAL EXCEPTION: SessionHandler
06-06 09:45:36.320: E/AndroidRuntime(28285): Process: com.XXXXX.app:standalone, PID: 28285
06-06 09:45:36.320: E/AndroidRuntime(28285): java.lang.VerifyError: Verifier rejected class com.aviary.android.feather.library.external.tracking.LocalyticsSession$UploadHandler due to bad method void com.aviary.android.feather.library.external.tracking.LocalyticsSession$UploadHandler.deleteBlobsAndSessions(com.aviary.android.feather.library.external.tracking.LocalyticsProvider) (declaration of 'com.aviary.android.feather.library.external.tracking.LocalyticsSession$UploadHandler' appears in /data/app/com.XXXXXXX.apk)
06-06 09:45:36.320: E/AndroidRuntime(28285): at com.aviary.android.feather.library.external.tracking.LocalyticsSession$SessionHandler.init(LocalyticsSession.java:1427)
06-06 09:45:36.320: E/AndroidRuntime(28285): at com.aviary.android.feather.library.external.tracking.LocalyticsSession$SessionHandler.handleMessage(LocalyticsSession.java:1124)
06-06 09:45:36.320: E/AndroidRuntime(28285): at android.os.Handler.dispatchMessage(Handler.java:102)
06-06 09:45:36.320: E/AndroidRuntime(28285): at android.os.Looper.loop(Looper.java:136)
06-06 09:45:36.320: E/AndroidRuntime(28285): at android.os.HandlerThread.run(HandlerThread.java:61)
06-06 09:45:36.320: W/ActivityManager(741): Force finishing activity com.XXXXXX.app/com.aviary.android.feather.FeatherActivity

HavocOS_2.9 Fastboot ROM

This file is exclusively prepared by BN_P
for
Asus Zenfone Max M2 (X01AD). It is havoc Pie 2.9 on pie vendor, Firmware-JP-16.2018.1910.52.
How to ::
1. Confirm your device model as above.
2. No need to be worried on which build your device is presently. This Rom can be flashed on any build. Also seperate unlock bootloader not required... It will b done by flash process automatically.
3. Only for windows users, flashing can be done in windows only.
Before start flashing,
Unzip the downloaded file. Put it in a folder in desktop.
There is a file named "system+vendor.zip" or something like that, unzip that, refer readme guide for details.
Put those above unzipped .img files in the main folder i.e same location of flash_all.cmd.
4. Put your device in fastboot mode, connect to PC and run the flash_all.cmd, just double click on it.
5. Follow the pop up screen.
6. Data erase will be required after flashing before boot.
Detailed process available in readme file inside.
Best of luck
This ROM is included
TWRP+Magisk
opengapps pico
Gcam
Ampere app
Viper sound mod
Google Phone Dialer
Safetynet Fixed
Bugs::
You tell me.
Thanks to::
@vincent for HavocOS GSI image.
[MENTION=268073]topjhonwu for magisk
Link for file...
https://www.androidfilehost.com/?w=files&flid=293310
NB Drop a line in comment section mentioning your feedback / bugs / experience
Updated version V2
Changelog
Magisk19.3 (magisk20 creating problem)
Updated gapps
Fastboot flashscript errors removed
added viper sound mod
updated twrp3.3.1-0
(NB:: Need to unzip system.zip, vendor.zip,recovery.zip,boot.zip to get corrsponding img files before flash)
what are the differences from havoc 2.9 gsi? (besides TWRP + Magisk20.1 opengapps pico Gcam Ampere app Google Phone Dialer Safetynet Fixed)
Gcam version? all work fine?
KLozhev said:
what are the differences from havoc 2.9 gsi? (besides TWRP + Magisk20.1 opengapps pico Gcam Ampere app Google Phone Dialer Safetynet Fixed)
Gcam version? all work fine?
Click to expand...
Click to collapse
It is a fastboot rom.... Can b flashed thru fastboot mode without twrp/custom recovery. No need to unlock bootloader seperately.
Everything will b done thru flashing script... U can say
Its a one click install rom.
[email protected] said:
It is a fastboot rom.... Can b flashed thru fastboot mode without twrp/custom recovery. No need to unlock bootloader seperately.
Everything will b done thru flashing script... U can say
Its a one click install rom.
Click to expand...
Click to collapse
thx
[email protected] said:
TWRP+Magisk20.1
Gcam
Click to expand...
Click to collapse
Gcam not work
without root
in TWRP 3.2.3(!) not work, mtp, adb, microsb
in archive missing generate_image.exe
Code:
934 I ActivityManager: START u0 {act=android.content.pm.action.REQUEST_PERMISSIONS pkg=com.google.android.packageinstaller cmp=com.google.android.packageinstaller/com.android.packageinstaller.permission.ui.GrantPermissionsActivity (has extras)} from uid 10230
10-28 16:42:04.510 1532 3811 D StorageManagerService: UID 10230 is actively using camera; letting them defy reserved cached data
--------- beginning of crash
10-28 16:42:04.570 8619 8665 E AndroidRuntime: FATAL EXCEPTION: GoogleApiHandler
10-28 16:42:04.570 8619 8665 E AndroidRuntime: Process: com.google.android.GoogleCamera, PID: 8619
10-28 16:42:04.570 8619 8665 E AndroidRuntime: java.lang.SecurityException: GoogleCertificatesRslt: not whitelisted: pkg=com.google.android.GoogleCamera, sha1=61ed377e85d386a8dfee6b864bd85b0bfaa5af81, atk=false, ver=14848037.true
10-28 16:42:04.570 8619 8665 E AndroidRuntime: at android.os.Parcel.createException(Parcel.java:1950)
10-28 16:42:04.570 8619 8665 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:1918)
10-28 16:42:04.570 8619 8665 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:1868)
10-28 16:42:04.570 8619 8665 E AndroidRuntime: at ksy.a(Unknown Source:35)
10-28 16:42:04.570 8619 8665 E AndroidRuntime: at krq.a(Unknown Source:98)
10-28 16:42:04.570 8619 8665 E AndroidRuntime: at lar.run(Unknown Source:54)
10-28 16:42:04.570 8619 8665 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:873)
10-28 16:42:04.570 8619 8665 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
10-28 16:42:04.570 8619 8665 E AndroidRuntime: at android.os.Looper.loop(Looper.java:193)
10-28 16:42:04.570 8619 8665 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:65)
10-28 16:42:04.620 1532 8279 W ActivityManager: Force finishing activity com.google.android.GoogleCamera/com.android.camera.CameraLauncher
10-28 16:42:04.639 1532 8279 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1005 com.android.server.am.AppErrors.crashApplicationInner:469 com.android.server.am.AppErrors.crashApplication:392 com.android.server.am.ActivityManagerService.handleApplicationCrashInner:15805 com.android.server.am.ActivityManagerService.handleApplicationCrash:15771
10-28 16:42:04.644 1532 1585 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
10-28 16:42:04.644 1532 1585 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
--------- beginning of main
10-28 16:42:04.693 949 8767 I chatty : uid=1047(cameraserver) /system/bin/cameraserver expire 3 lines
10-28 16:42:04.708 1532 5145 I WindowManager: WIN DEATH: Window{a97e4c3 u0 com.google.android.GoogleCamera/com.android.camera.CameraLauncher}
10-28 16:42:04.708 1532 8108 I ActivityManager: Process com.google.android.GoogleCamera (pid 8619) has died: vis +99TOP
10-28 16:42:04.710 1532 1588 I chatty : uid=1000(system) ActivityManager expire 8 lines
10-28 16:42:04.710 795 8752 I chatty : uid=1047(cameraserver) [email protected] expire 4 lines
10-28 16:42:04.713 1532 3227 I WindowManager: WIN DEATH: Window{263b47e u0 Toast}
10-28 16:42:04.713 1532 3227 I chatty : uid=1000(system) Binder:1532_3 expire 1 line
10-28 16:42:04.732 831 1286 W SurfaceFlinger: Attempting to set client state on removed layer: com.google.android.GoogleCamera/com.android.camera.CameraLauncher#0
10-28 16:42:04.732 831 1286 W SurfaceFlinger: Attempting to destroy on removed layer: com.google.android.GoogleCamera/com.android.camera.CameraLauncher#0
10-28 16:42:04.736 795 8785 I chatty : uid=1047(cameraserver) [email protected] expire 2 lines
10-28 16:42:04.739 831 906 E BufferQueueProducer: [SurfaceView - com.google.android.GoogleCamera/com.android.camera.CameraLauncher#0] queueBuffer: BufferQueue has been abandoned
10-28 16:42:04.743 815 840 E ANDR-PERF-MPCTL: Invalid profile no. 0, total profiles 0 only
10-28 16:42:04.743 815 840 E ANDR-PERF-OPTSHANDLER: Perflock resource /sys/devices/system/cpu/cpu0/cpufreq/schedutil/hispeed_load not supported
10-28 16:42:04.743 815 840 E ANDR-PERF-OPTSHANDLER: Perflock resource /sys/devices/system/cpu/cpu0/cpufreq/schedutil/hispeed_freq not supported
10-28 16:42:04.749 1532 1587 W ActivityManager: Slow operation: 142ms so far, now at startProcess: returned from zygote!
10-28 16:42:04.752 746 746 I Zygote : Process 8619 exited due to signal (9)
10-28 16:42:04.763 8821 8821 I chatty : uid=10230(u0_a230) expire 4 lines
10-28 16:42:04.763 1532 1587 W ActivityManager: Slow operation: 156ms so far, now at startProcess: done updating battery stats
10-28 16:42:04.763 1532 1587 W ActivityManager: Slow operation: 156ms so far, now at startProcess: building log message
10-28 16:42:04.763 1532 1587 I ActivityManager: Start proc 8821:com.google.android.GoogleCamera:crash_report/u0a230 for service com.google.android.GoogleCamera/com.google.android.apps.camera.app.silentfeedback.SilentFeedbackService
10-28 16:42:04.763 1532 1587 W ActivityManager: Slow operation: 156ms so far, now at startProcess: starting to update pids map
10-28 16:42:04.763 1532 1587 W ActivityManager: Slow operation: 156ms so far, now at startProcess: done updating pids map
10-28 16:42:04.768 831 1286 E BufferQueueProducer: [SurfaceView - com.google.android.GoogleCamera/com.android.camera.CameraLauncher#0] queueBuffer: BufferQueue has been abandoned
10-28 16:42:04.769 949 1913 I chatty : uid=1047(cameraserver) HwBinder:949_3 expire 12 lines
10-28 16:42:04.771 4271 4271 D Launcher.Utilities: onLauncherStart: 0
10-28 16:42:04.773 1532 3811 W ActivityManager: Unable to start service Intent { act=com.android.launcher3.WINDOW_OVERLAY dat=app://ch.deletescape.lawnchair.ci:10038?v=7&cv=9 pkg=com.google.android.googlequicksearchbox } U=0: not found
10-28 16:42:04.803 831 3852 E BufferQueueProducer: [SurfaceView - com.google.android.GoogleCamera/com.android.camera.CameraLauncher#0] queueBuffer: BufferQueue has been abandoned
10-28 16:42:04.815 795 1794 I chatty : uid=1047(cameraserver) HwBinder:795_1 expire 122 lines
10-28 16:42:04.818 815 840 E ANDR-PERF-MPCTL: Invalid profile no. 0, total profiles 0 only
10-28 16:42:04.853 795 8804 I chatty : uid=1047(cameraserver) [email protected] expire 1 line
10-28 16:42:04.893 795 8841 I chatty : uid=1047(cameraserver) [email protected] expire 2 lines
10-28 16:42:04.894 795 8842 I chatty : uid=1047(cameraserver) [email protected] expire 2 lines
10-28 16:42:04.895 795 8843 I chatty : uid=1047(cameraserver) [email protected] expire 3 lines
10-28 16:42:04.896 795 8844 I chatty : uid=1047(cameraserver) [email protected] expire 2 lines
10-28 16:42:04.903 8821 8821 E AndroidRuntime: FATAL EXCEPTION: main
10-28 16:42:04.903 8821 8821 E AndroidRuntime: Process: com.google.android.GoogleCamera:crash_report, PID: 8821
10-28 16:42:04.903 8821 8821 E AndroidRuntime: java.lang.SecurityException: GoogleCertificatesRslt: not whitelisted: pkg=com.google.android.GoogleCamera, sha1=61ed377e85d386a8dfee6b864bd85b0bfaa5af81, atk=false, ver=14848037.true
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at android.os.Parcel.createException(Parcel.java:1950)
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:1918)
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:1868)
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at ksy.a(Unknown Source:35)
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at krq.a(Unknown Source:98)
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at kzw.a(Unknown Source:98)
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at laa.run(Unknown Source:21)
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:458)
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at java.util.concurrent.FutureTask.run(FutureTask.java:266)
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at kwm.run(Unknown Source:7)
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at java.lang.Thread.run(Thread.java:764)
10-28 16:42:04.908 1532 8820 W ActivityManager: Process com.google.android.GoogleCamera has crashed too many times: killing!
10-28 16:42:04.910 1532 8820 I ActivityManager: Killing 8821:com.google.android.GoogleCamera:crash_report/u0a230 (adj 500): crash
10-28 16:42:04.914 795 8846 I chatty : uid=1047(cameraserver) [email protected] expire 5 lines
10-28 16:42:04.918 795 8848 I chatty : uid=1047(cameraserver) [email protected] expire 2 lines
10-28 16:42:04.932 1532 1585 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
10-28 16:42:04.933 1532 1585 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
10-28 16:42:04.937 802 843 I SDM : ResourceImpl::SetMaxBandwidthMode: new bandwidth mode=0
10-28 16:42:04.947 439 439 E SELinux : avc: denied { find } for interface=vendor.lineage.camera.motor::ICameraMotor sid=u:r:cameraserver:s0 pid=949 scontext=u:r:cameraserver:s0 tcontext=u:object_r:default_android_hwservice:s0 tclass=hwservice_manager permissive=0
THANK YOU!!!!!!
[email protected] said:
This file is exclusively prepared by BN_P
for
Asus Zenfone Max M2 (X01AD). It is havoc Pie 2.9 on pie vendor, Firmware-JP-16.2018.1910.52.
How to ::
1. Confirm your device model as above.
2. No need to be worried on which build your device is presently. This Rom can be flashed on any build.
3. Only for windows users, flashing can be done in windows only.
Before start flashing,
There is a file named "system+vendor.zip", unzip that, it will generate two file i.e. system.img and vendor.img
Put the above two .img files in the main folder i.e same location of flash_all.cmd.
4. Put your device in fastboot mode, connect to PC and run the flash_all.cmd, just double click on it.
5. Follow the pop up screen.
6. Data erase will be required after flashing before boot.
Best of luck
This ROM is included
TWRP+Magisk20.1
opengapps pico
Gcam
Ampere app
Google Phone Dialer
Safetynet Fixed
Bugs::
You tell me.
Thanks to::
@vincent for HavocOS GSI image.
[MENTION=268073]topjhonwu for magisk
Link for file
https://www.androidfilehost.com/?fid=4349826312261607460
Click to expand...
Click to collapse
Bootloader unlocking required or not ???
Techgaming432 said:
Bootloader unlocking required or not ???
Click to expand...
Click to collapse
Not required... Unlock will b done automatically by flash script
[email protected] said:
This file is exclusively prepared by BN_P
for
Asus Zenfone Max M2 (X01AD). It is havoc Pie 2.9 on pie vendor, Firmware-JP-16.2018.1910.52.
How to ::
1. Confirm your device model as above.
2. No need to be worried on which build your device is presently. This Rom can be flashed on any build.
3. Only for windows users, flashing can be done in windows only.
Before start flashing,
There is a file named "system+vendor.zip", unzip that, it will generate two file i.e. system.img and vendor.img
Put the above two .img files in the main folder i.e same location of flash_all.cmd.
4. Put your device in fastboot mode, connect to PC and run the flash_all.cmd, just double click on it.
5. Follow the pop up screen.
6. Data erase will be required after flashing before boot.
Best of luck
This ROM is included
TWRP+Magisk20.1
opengapps pico
Gcam
Ampere app
Google Phone Dialer
Safetynet Fixed
Bugs::
You tell me.
Thanks to::
@vincent for HavocOS GSI image.
[MENTION=268073]topjhonwu for magisk
Link for file
https://www.androidfilehost.com/?fid=4349826312261607460
Click to expand...
Click to collapse
Any other ROM like MIUI or Oxygen OS have for X01AD ??
Techgaming432 said:
Any other ROM like MIUI or Oxygen OS have for X01AD ??
Click to expand...
Click to collapse
Search.... I hv not made yet
[email protected] said:
Search.... I hv not made yet
Click to expand...
Click to collapse
Please made a MIUI 10 stable ROM i will give what you want but please made a MIUI 10 stable ROM
Techgaming432 said:
Please made a MIUI 10 stable ROM i will give what you want but please made a MIUI 10 stable ROM
Click to expand...
Click to collapse
May b in future
please tell me full process step by step
nixsting said:
please tell me full process step by step
Click to expand...
Click to collapse
Follow readme file inside
An error occurred when flashing the system image it says invalid sparse system in command prompt window and skips the system image from flashing
Please tell me the solve of the problem
Techgaming432 said:
An error occurred when flashing the system image it says invalid sparse system in command prompt window and skips the system image from flashing
Please tell me the solve of the problem
Click to expand...
Click to collapse
Did u unzipped system.zip and kept the system.img file at flashing folder....?
Plz follow readme file inside.
Before flashing ensure all img files are present
Sydtem.img
Vendor
Boot
Recovery
Other firmwire images
[email protected] said:
Did u unzipped system.zip and kept the system.img file at flashing folder....?
Plz follow readme file inside.
Click to expand...
Click to collapse
Yes i extracted the system+vendor zip file and moved the system.img and vendor.img file into the same location on flashall.cmd and exactly follow the guide but the error occurres
Techgaming432 said:
Yes i extracted the system+vendor zip file and moved the system.img and vendor.img file into the same location on flashall.cmd and exactly follow the guide but the error occurres
Click to expand...
Click to collapse
Post a screenshot
[email protected] said:
Post a screenshot
Click to expand...
Click to collapse
Ok I will try another time to flash if the erro occure then i will take a screenshot of the command prompt window and send it to you by today evening

Android 11 / LineageOS 18.0

When is an unofficial 18.0 build arriving? Unofficial LineageOS 17.1 (afaneh92, Couchy) hasn't had a build in months.
Newer devices than S5 are too limited (bootloaders locked or limited cell coverage with no bootloader locking, fixed battery, sound jack missing/occupies USB charging, $$$$$, curved screen, missing notification LED, obtrusive cameras). No ROM's for bootloader unlocked Galaxy S10 5G Sprint either. So S5 is all there is.
My crystal ball is broken. But probably A11 will arrive when (and if) it is ready...
guest4711 said:
My crystal ball is broken. But probably A11 will arrive when (and if) it is ready...
Click to expand...
Click to collapse
Ok. 6 more months or so. Thanks.
LineageOS 18.0 is already
Khalvat created an alpha version for klte:
lineage-18.0-20200926-UNOFFICIAL-klte.zip
edit.
It does not boot.
edit 2
When you insert the RSA key from your PC after authorization in another ROM,
Code:
adb push adb_keys /data/misc/adb/
then you can watch the logcat.
Code:
adb logcat -b all > klte_logcat.txt
.
ttesty said:
When is an unofficial 18.0 build arriving? Unofficial LineageOS 17.1 (afaneh92, Couchy) hasn't had a build in months.
Newer devices than S5 are too limited (bootloaders locked or limited cell coverage with no bootloader locking, fixed battery, sound jack missing/occupies USB charging, $$$$$, curved screen, missing notification LED, obtrusive cameras). No ROM's for bootloader unlocked Galaxy S10 5G Sprint either. So S5 is all there is.
Click to expand...
Click to collapse
Im going to build some lineage os builds probably starting tonight
¯\_(ツ)_/¯
haggertk said:
¯\_(ツ)_/¯
Click to expand...
Click to collapse
Clean installed ROM only to my g900i device.
Install was smooth, no problems.
There appears to be no mobile data available, otherwise a beautiful build. Testing continues...
Thanks for your work :good:
pmduper said:
Clean installed ROM only to my g900i device.
Install was smooth, no problems.
There appears to be no mobile data available, otherwise a beautiful build. Testing continues...
Thanks for your work :good:
Click to expand...
Click to collapse
Yeah, you should need a dv build for the g900i to have data... I may get to that tomorrow. I did just put a SIM in my g900w8 and have solid mobile data.
Purposely not advertising these since they are permissive, but most people know where to find them.
lineageos 18.0 ready for klte
haggertk said:
Yeah, you should need a dv build for the g900i to have data... I may get to that tomorrow. I did just put a SIM in my g900w8 and have solid mobile data.
Purposely not advertising these since they are permissive, but most people know where to find them.
Click to expand...
Click to collapse
Today I put in my SM-G900F and it works without any noticeable lag.
Thank a lot Mr Haggertk
haggertk said:
Yeah, you should need a dv build for the g900i to have data... I may get to that tomorrow. I did just put a SIM in my g900w8 and have solid mobile data.
Purposely not advertising these since they are permissive, but most people know where to find them.
Click to expand...
Click to collapse
Hi mate,
Thanks for your kltedv build.
Unfortunately I still have no mobile data with LOS18 20201130 build.
Formatted and advanced cleaned, flashed rom only. Setup was smooth. No other fault found after testing the usual.
Appreciate your work
6 months is a good original estimate (in Sept) for a stable 18.1 build for S5, though it may take some more time by the looks of it.
@haggertk posted a few Android 11.0/LineageOS 18.0 builds here (not sure about their state - think it's alpha, but good work!): https://androidfilehost.com/?w=files&flid=320376
OpenGApps only has links to 11.0 test builds for ARM64 (not ARM) - haven't used alternatives yet: https://sourceforge.net/projects/opengapps/files/arm64/test/
So BitGApps:
https://drive.google.com/u/0/uc?id=1w3EK5DpDjJWNN27LFLg-_x41fnT4GopC&export=download
Then there's TWRP 3.4:
https://dl.twrp.me/klte/twrp-3.4.0-0-klte.img.html
Magisk:
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
It would help to setup a thread on the S5 Unified Development forum for all the Android 11.0 build/setup items for @haggertk's release. There's also CRDroid 11.0, but no idea about long-term builds.
Might need to move to ARM64 for future Android releases - S5 is about 7 years old, though still better than many newer devices (full root, unlocked bootloader, buttons, headphone jack, no curved screen, notification LED, $80-$100 - like the raw cost to make the new $1000 devices, etc). The S10 5G G977P would be a great ARM64 Snapdragon option (bootloader unlocked), but no ROM's yet, silly cost (about $450). Exynos is cheap, but 4G/5G reception is a guess in the US.
For now, just using latest official 17.1 - it's been pretty rock solid: https://download.lineageos.org/klte
No rush to buy a Galaxy S21 Ultra for $2000 - get more for less
Mobile data internet is not
ttesty said:
6 months is a good original estimate (in Sept) for a stable 18.1 build for S5, though it may take some more time by the looks of it.
@haggertk posted a few Android 11.0/LineageOS 18.0 builds here (not sure about their state - think it's alpha, but good work!): https://androidfilehost.com/?w=files&flid=320376
OpenGApps only has links to 11.0 test builds for ARM64 (not ARM) - haven't used alternatives yet: https://sourceforge.net/projects/opengapps/files/arm64/test/
So BitGApps:
https://drive.google.com/u/0/uc?id=1w3EK5DpDjJWNN27LFLg-_x41fnT4GopC&export=download
Then there's TWRP 3.4:
https://dl.twrp.me/klte/twrp-3.4.0-0-klte.img.html
Magisk:
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
It would help to setup a thread on the S5 Unified Development forum for all the Android 11.0 build/setup items for @haggertk's release. There's also CRDroid 11.0, but no idea about long-term builds.
Might need to move to ARM64 for future Android releases - S5 is about 7 years old, though still better than many newer devices (full root, unlocked bootloader, buttons, headphone jack, no curved screen, notification LED, $80-$100 - like the raw cost to make the new $1000 devices, etc). The S10 5G G977P would be a great ARM64 Snapdragon option (bootloader unlocked), but no ROM's yet, silly cost (about $450). Exynos is cheap, but 4G/5G reception is a guess in the US.
For now, just using latest official 17.1 - it's been pretty rock solid: https://download.lineageos.org/klte
No rush to buy a Galaxy S21 Ultra for $2000 - get more for less
Click to expand...
Click to collapse
Mobile data internet is not working (((...it shows "H" and internet is not working (((((
This Android 11 release kind of works on a G900T, but it's unstable. Just change your APN and Network Type and reboot.
You can run "ping -I rmnet1 8.8.8.8" and it will ping. I get a lot of Google Maps crashes, and there's no default network route that works. It lists LTE and allows me to make calls, but there's an X. Some kind of iptables issue with not finding an interface.
For the Network problems:
12-21 16:38:57.059 909 1083 D DataUsageController: setMobileDataEnabled: enabled=true
12-21 16:38:57.059 909 1083 D TelephonyManager: setDataEnabled: enabled=true
12-21 16:38:57.205 479 744 E RIL-QMI : qmuxd: TX message on fd=21, to qmux_client_id=0x1, len=283
12-21 16:38:57.205 591 860 E RIL-QMI : qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=c1
12-21 16:38:57.205 591 860 E RIL-QMI : qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=c0
12-21 16:38:57.205 591 860 E RIL-QMI : qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=bf
12-21 16:38:57.205 591 860 E RIL-QMI : qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=be
12-21 16:38:57.205 591 860 E RIL-QMI : qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=bd
12-21 16:38:57.205 591 860 E RIL-QMI : qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=b0
12-21 16:38:57.205 591 860 E RIL-QMI : qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=ab
12-21 16:38:57.205 591 860 E RIL-QMI : qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=aa
12-21 16:38:57.205 591 860 E RIL-QMI : qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=a9
12-21 16:38:57.205 479 479 E RIL-QMI : qmuxd: RX 52 bytes on fd=21 from qmux_client_id=0x1
12-21 16:38:57.212 479 744 E RIL-QMI : qmuxd: TX message on fd=21, to qmux_client_id=0x1, len=283
12-21 16:38:57.306 765 790 I EthernetTracker: interfaceLinkStateChanged, iface: rmnet1, up: true
12-21 16:38:57.348 765 780 D ConnectivityService: registerNetworkAgent NetworkAgentInfo{ ni{[type: MOBILE[], state: UNKNOWN/IDLE, reason: (unspecified), extra: pta, failover: false, available: true, roaming: false]} network{102} nethandle{441492361229} lp{{InterfaceName: rmnet1 LinkAddresses: [ HIDDEN/32 ] DnsAddresses: [ /PRIVATE ] Domains: null MTU: 1410 TcpBufferSizes: 2097152,4194304,8388608,262144,524288,1048576 Routes: [ 0.0.0.0/0 -> HIDDEN rmnet1 mtu 0,HIDDEN/32 -> 0.0.0.0 rmnet1 mtu 0 ]}} nc{[ Transports: CELLULAR Capabilities: MMS&SUPL&INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN&NOT_ROAMING&FOREGROUND&NOT_CONGESTED&NOT_SUSPENDED LinkUpBandwidth>=15000Kbps LinkDnBandwidth>=30000Kbps Specifier: <TelephonyNetworkSpecifier [mSubId = 1]> AdministratorUids: [] RequestorUid: -1 RequestorPackageName: null]} Score{10} everValidated{false} lastValidated{false} created{false} lingering{false} explicitlySelected{false} acceptUnvalidated{false} everCaptivePortalDetected{false} lastCaptivePortalDetected{false} partialConnectivity{false} acceptPartialConnectivity{false} clat{mBaseIface: null, mIface: null, mState: IDLE} }
12-21 16:38:57.374 765 866 D ConnectivityService: [102 CELLULAR] EVENT_NETWORK_INFO_CHANGED, going from UNKNOWN to UNKNOWN
12-21 16:38:57.375 765 866 D ConnectivityService: [102 CELLULAR] EVENT_NETWORK_INFO_CHANGED, going from UNKNOWN to CONNECTED
12-21 16:38:57.378 765 866 W DnsManager: updatePrivateDns(102, PrivateDnsConfig{false:/[]})
12-21 16:38:57.378 765 866 D ConnectivityService: Setting DNS servers for network 102 to [/HIDDEN]
12-21 16:38:57.378 765 866 D DnsManager: sendDnsConfigurationForNetwork(102, [HIDDEN], [], 1800, 25, 8, 64, 0, 0, , [])
12-21 16:38:57.379 765 866 D ConnectivityService: Adding iface rmnet1 to network 102
12-21 16:38:57.308 765 790 I EthernetTracker: interfaceLinkStateChanged, iface: rmnet1, up: true
12-21 16:38:57.389 765 790 I EthernetTracker: interfaceLinkStateChanged, iface: rmnet1, up: true
12-21 16:38:57.389 435 465 E Netd : Error adding route 0.0.0.0/0 -> HIDDEN rmnet1 to table 1004: Network is unreachable
12-21 16:27:01.131 8034 8198 E AndroidRuntime: FATAL EXCEPTION: grpc-default-executor-0
12-21 16:27:01.131 8034 8198 E AndroidRuntime: Process: com.google.android.apps.maps, PID: 8034
12-21 16:27:01.131 8034 8198 E AndroidRuntime: java.lang.UnsupportedOperationException: The bidirectional stream API is not supported by the Java implementation of Cronet Engine
12-21 16:27:01.148 765 8217 I DropBoxManagerService: add tag=data_app_crash isTagEnabled=true flags=0x2
12-21 16:27:01.149 765 1696 W ActivityTaskManager: Force finishing activity com.google.android.apps.maps/com.google.android.maps.MapsActivity
[/data/user_de/0/com.google.android.gms/app_chimera/m/0000000b/CronetDynamite.apk!/lib/armeabi-v7a, /data/user_de/0/com.google.android.gms/app_chimera/m/0000000b/CronetDynamite.apk!/lib/armeabi, /system/lib, /system/system_ext/lib, /system/product/lib, /system/vendor/lib]]
12-21 16:26:56.051 8034 8087 E ChimeraModuleLdr: Failed to load code for module FileApk(/data/user_de/0/com.google.android.gms/app_chimera/m/0000000b/CronetDynamite.apk)
12-21 16:26:56.051 8034 8087 E ChimeraModuleLdr: czi: Can't load code for CronetDynamite.apk
12-21 16:26:59.145 8034 8164 W ChimeraFileApk: Failed to validate PathClassLoader for /data/user_de/0/com.google.android.gms/app_chimera/m/00000011/MeasurementDynamite.apk: java.lang.ClassNotFoundException: Didn't find class "com.google.android.gms.chimera.DynamiteModuleInitializer" on path: DexPathList[[],nativeLibraryDirectories=[/data/user_de/0/com.google.android.gms/app_chimera/m/00000011/MeasurementDynamite.apk!/lib/armeabi-v7a, /data/user_de/0/com.google.android.gms/app_chimera/m/00000011/MeasurementDynamite.apk!/lib/armeabi, /system/lib, /system/system_ext/lib, /system/product/lib, /system/vendor/lib]]
12-21 16:26:59.149 8034 8164 E ChimeraModuleLdr: Failed to load code for module FileApk(/data/user_de/0/com.google.android.gms/app_chimera/m/00000011/MeasurementDynamite.apk)
12-21 16:26:45.752 1979 7875 W aolp : setProperties failed with SecurityException [CONTEXT service_id=204 ]
12-21 16:26:45.752 1979 7875 W aolp : java.lang.SecurityException: Permission denial: writing to settings requires:android.permission.WRITE_DEVICE_CONFIG
12-21 16:26:45.752 1979 7875 W aolp : at android.os.Parcel.createExceptionOrNull(Parcel.java:2373)
12-21 16:26:45.752 1979 7875 W aolp : at android.os.Parcel.createException(Parcel.java:2357)
12-21 16:26:45.752 1979 7875 W aolp : at android.os.Parcel.readException(Parcel.java:2340)
ttesty said:
This Android 11 release kind of works on a G900T, but it's unstable. Just change your APN and Network Type and reboot.
You can run "ping -I rmnet1 8.8.8.8" and it will ping. I get a lot of Google Maps crashes, and there's no default network route that works. It lists LTE and allows me to make calls, but there's an X. Some kind of iptables issue with not finding an interface.
For the Network problems:
12-21 16:38:57.059 909 1083 D DataUsageController: setMobileDataEnabled: enabled=true
12-21 16:38:57.059 909 1083 D TelephonyManager: setDataEnabled: enabled=true
12-21 16:38:57.205 479 744 E RIL-QMI : qmuxd: TX message on fd=21, to qmux_client_id=0x1, len=283
12-21 16:38:57.205 591 860 E RIL-QMI : qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=c1
12-21 16:38:57.205 591 860 E RIL-QMI : qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=c0
12-21 16:38:57.205 591 860 E RIL-QMI : qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=bf
12-21 16:38:57.205 591 860 E RIL-QMI : qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=be
12-21 16:38:57.205 591 860 E RIL-QMI : qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=bd
12-21 16:38:57.205 591 860 E RIL-QMI : qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=b0
12-21 16:38:57.205 591 860 E RIL-QMI : qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=ab
12-21 16:38:57.205 591 860 E RIL-QMI : qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=aa
12-21 16:38:57.205 591 860 E RIL-QMI : qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=a9
12-21 16:38:57.205 479 479 E RIL-QMI : qmuxd: RX 52 bytes on fd=21 from qmux_client_id=0x1
12-21 16:38:57.212 479 744 E RIL-QMI : qmuxd: TX message on fd=21, to qmux_client_id=0x1, len=283
12-21 16:38:57.306 765 790 I EthernetTracker: interfaceLinkStateChanged, iface: rmnet1, up: true
12-21 16:38:57.348 765 780 D ConnectivityService: registerNetworkAgent NetworkAgentInfo{ ni{[type: MOBILE[], state: UNKNOWN/IDLE, reason: (unspecified), extra: pta, failover: false, available: true, roaming: false]} network{102} nethandle{441492361229} lp{{InterfaceName: rmnet1 LinkAddresses: [ HIDDEN/32 ] DnsAddresses: [ /PRIVATE ] Domains: null MTU: 1410 TcpBufferSizes: 2097152,4194304,8388608,262144,524288,1048576 Routes: [ 0.0.0.0/0 -> HIDDEN rmnet1 mtu 0,HIDDEN/32 -> 0.0.0.0 rmnet1 mtu 0 ]}} nc{[ Transports: CELLULAR Capabilities: MMS&SUPL&INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN&NOT_ROAMING&FOREGROUND&NOT_CONGESTED&NOT_SUSPENDED LinkUpBandwidth>=15000Kbps LinkDnBandwidth>=30000Kbps Specifier: <TelephonyNetworkSpecifier [mSubId = 1]> AdministratorUids: [] RequestorUid: -1 RequestorPackageName: null]} Score{10} everValidated{false} lastValidated{false} created{false} lingering{false} explicitlySelected{false} acceptUnvalidated{false} everCaptivePortalDetected{false} lastCaptivePortalDetected{false} partialConnectivity{false} acceptPartialConnectivity{false} clat{mBaseIface: null, mIface: null, mState: IDLE} }
12-21 16:38:57.374 765 866 D ConnectivityService: [102 CELLULAR] EVENT_NETWORK_INFO_CHANGED, going from UNKNOWN to UNKNOWN
12-21 16:38:57.375 765 866 D ConnectivityService: [102 CELLULAR] EVENT_NETWORK_INFO_CHANGED, going from UNKNOWN to CONNECTED
12-21 16:38:57.378 765 866 W DnsManager: updatePrivateDns(102, PrivateDnsConfig{false:/[]})
12-21 16:38:57.378 765 866 D ConnectivityService: Setting DNS servers for network 102 to [/HIDDEN]
12-21 16:38:57.378 765 866 D DnsManager: sendDnsConfigurationForNetwork(102, [HIDDEN], [], 1800, 25, 8, 64, 0, 0, , [])
12-21 16:38:57.379 765 866 D ConnectivityService: Adding iface rmnet1 to network 102
12-21 16:38:57.308 765 790 I EthernetTracker: interfaceLinkStateChanged, iface: rmnet1, up: true
12-21 16:38:57.389 765 790 I EthernetTracker: interfaceLinkStateChanged, iface: rmnet1, up: true
12-21 16:38:57.389 435 465 E Netd : Error adding route 0.0.0.0/0 -> HIDDEN rmnet1 to table 1004: Network is unreachable
12-21 16:27:01.131 8034 8198 E AndroidRuntime: FATAL EXCEPTION: grpc-default-executor-0
12-21 16:27:01.131 8034 8198 E AndroidRuntime: Process: com.google.android.apps.maps, PID: 8034
12-21 16:27:01.131 8034 8198 E AndroidRuntime: java.lang.UnsupportedOperationException: The bidirectional stream API is not supported by the Java implementation of Cronet Engine
12-21 16:27:01.148 765 8217 I DropBoxManagerService: add tag=data_app_crash isTagEnabled=true flags=0x2
12-21 16:27:01.149 765 1696 W ActivityTaskManager: Force finishing activity com.google.android.apps.maps/com.google.android.maps.MapsActivity
[/data/user_de/0/com.google.android.gms/app_chimera/m/0000000b/CronetDynamite.apk!/lib/armeabi-v7a, /data/user_de/0/com.google.android.gms/app_chimera/m/0000000b/CronetDynamite.apk!/lib/armeabi, /system/lib, /system/system_ext/lib, /system/product/lib, /system/vendor/lib]]
12-21 16:26:56.051 8034 8087 E ChimeraModuleLdr: Failed to load code for module FileApk(/data/user_de/0/com.google.android.gms/app_chimera/m/0000000b/CronetDynamite.apk)
12-21 16:26:56.051 8034 8087 E ChimeraModuleLdr: czi: Can't load code for CronetDynamite.apk
12-21 16:26:59.145 8034 8164 W ChimeraFileApk: Failed to validate PathClassLoader for /data/user_de/0/com.google.android.gms/app_chimera/m/00000011/MeasurementDynamite.apk: java.lang.ClassNotFoundException: Didn't find class "com.google.android.gms.chimera.DynamiteModuleInitializer" on path: DexPathList[[],nativeLibraryDirectories=[/data/user_de/0/com.google.android.gms/app_chimera/m/00000011/MeasurementDynamite.apk!/lib/armeabi-v7a, /data/user_de/0/com.google.android.gms/app_chimera/m/00000011/MeasurementDynamite.apk!/lib/armeabi, /system/lib, /system/system_ext/lib, /system/product/lib, /system/vendor/lib]]
12-21 16:26:59.149 8034 8164 E ChimeraModuleLdr: Failed to load code for module FileApk(/data/user_de/0/com.google.android.gms/app_chimera/m/00000011/MeasurementDynamite.apk)
12-21 16:26:45.752 1979 7875 W aolp : setProperties failed with SecurityException [CONTEXT service_id=204 ]
12-21 16:26:45.752 1979 7875 W aolp : java.lang.SecurityException: Permission denial: writing to settings requires:android.permission.WRITE_DEVICE_CONFIG
12-21 16:26:45.752 1979 7875 W aolp : at android.os.Parcel.createExceptionOrNull(Parcel.java:2373)
12-21 16:26:45.752 1979 7875 W aolp : at android.os.Parcel.createException(Parcel.java:2357)
12-21 16:26:45.752 1979 7875 W aolp : at android.os.Parcel.readException(Parcel.java:2340)
Click to expand...
Click to collapse
i dont understand anything what you wrote here
Skerleton said:
i dont understand anything what you wrote here
Click to expand...
Click to collapse
Ok.
pmduper said:
Hi mate,
Thanks for your kltedv build.
Unfortunately I still have no mobile data with LOS18 20201130 build.
Formatted and advanced cleaned, flashed rom only. Setup was smooth. No other fault found after testing the usual.
Appreciate your work
Click to expand...
Click to collapse
@haggertk. Merry Christmas to you. Thanks for the 20201225 update.
kltedv build installed works flawlessly!
ROM only, no gapps and no custom kernel.
Mobile data, calls, SMS, Bluetooth, fingerprint, WiFi etc all working smoothly.
Taking it on a road trip tomorrow so I'll have the opportunity to have a good play.
pmduper said:
...Thanks for the 20201225 update.
kltedv build installed works flawlessly!...
Click to expand...
Click to collapse
Thanks for the report.
Could you tell me please if in > Settings > Privacy > Trust > SELinux is set to Permissive or Enforcing?
That's the path in 17.1 & it may have changed in 18.1.
FYI the LineageOS S5 klte family maintainer created a new thread here:
[ROM][UNOFFICIAL][11] LineageOS 18.1 for Samsung Galaxy S5 (klte*)
***
curiousrom said:
Thanks for the report.
Could you tell me please if in > Settings > Privacy > Trust > SELinux is set to Permissive or Enforcing?
That's the path in 17.1 & it may have changed in 18.1.
FYI the LineageOS S5 klte family maintainer created a new thread here:
[ROM][UNOFFICIAL][11] LineageOS 18.1 for Samsung Galaxy S5 (klte*)
***
Click to expand...
Click to collapse
Hi mate
Its set to Enforcing...
curiousrom said:
Thanks for the report.
Could you tell me please if in > Settings > Privacy > Trust > SELinux is set to Permissive or Enforcing?
That's the path in 17.1 & it may have changed in 18.1.
FYI the LineageOS S5 klte family maintainer created a new thread here:
[ROM][UNOFFICIAL][11] LineageOS 18.1 for Samsung Galaxy S5 (klte*)
***
Click to expand...
Click to collapse
Enforcing.. getenforce too.

Trouble compiling 8.2.0 kernel from source for ShieldTV 2017

I am trying to compile the 8.2.0 Kernel for my Shield TV 2017. I am hoping to adding the Wireguard kernel module.
I downloaded the source linked from https://developer.nvidia.com/shield-open-source following the instructions links here https://nv-tegra.nvidia.com/gitweb/...7;hb=1a508fa42d6ae55ee0fe62a3e07559a484794108
The source code checks out fine. I set up my cross compiler by setting these environment variables
Code:
ARCH=arm64
SUBARCH=arm64
CROSS_COMPILE=/absolute/path/shield-open-source/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-
I removed the CONFIG_SYSTEM_TRUSTED_KEYS="signing_key.x509" from the tegra_android_defconfig file
I then went to ~/shield-open-source/kernel/kernel-4.9 and ran
Code:
make mrproper
make tegra_android_defconfig
make -j4
There were a few warnings that got flagged as errors and caused the build to failed. I modified the make files so the warnings wouldn't be flagged as errors (ex: ccflags-y += -Wno-error=maybe-uninitialized)
There is one more error with ~/shield-open-source/hardware/nvidia/platform/t210b01/ers/kernel-dts/ers-platforms/tegra210b01-ers-common.dtsi in that it can't find <tegra210b01-cpufreq.dtsi>. I changed this to include "darcy-platforms/tegra210b01-darcy-cpufreq.dtsi"
I also added Wireguard by following the kernel instructions from https://forum.xda-developers.com/android/development/wireguard-rom-integration-t3711635
At this point I am able build the Image.gz file. I took the boot.img from the recovery images that NVidia provides and used AndroidImageKitchen (https://forum.xda-developers.com/showthread.php?t=2073775) to unpack the boot.img, swap out boot.img-Image.gz with the one Image.gz that I compiled and re-packed the boot.img I flashed this boot.img to my device using fastboot, and the device never boots.
I have some logs from the bootloop - here is the snipit that seems most relevant but I don't really know what I am looking for or how to determine what needs to change
Code:
09-12 22:00:42.120 3384 3384 I ConfigStore: android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasWideColorDisplay retrieved: 1
09-12 22:00:42.120 3384 3384 I ConfigStore: android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasHDRDisplay retrieved: 1
09-12 22:00:42.120 3383 3383 E Netd : cannot find interface dummy0
09-12 22:00:42.120 3383 3383 I Netd : Initializing RouteController: 1.3ms
09-12 22:00:42.120 3384 3384 F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 in tid 3384 (surfaceflinger), pid 3384 (surfaceflinger)
09-12 22:00:42.120 3383 3383 D XfrmController: Sending Netlink XFRM Message: XFRM_MSG_FLUSHSA
09-12 22:00:42.120 3383 3383 D XfrmController: Sending Netlink XFRM Message: XFRM_MSG_FLUSHPOLICY
09-12 22:00:42.120 3383 3383 I Netd : Initializing XfrmController: 0.2ms
09-12 22:00:42.121 3383 3383 I Netd : Registering NetdNativeService: 0.5ms
09-12 22:00:42.122 3383 3383 I Netd : Starting CommandListener: 0.1ms
09-12 22:00:42.123 3383 3383 I Netd : Registering NetdHwService: 1.0ms
09-12 22:00:42.123 3383 3383 I Netd : Netd started in 219ms
09-12 22:00:42.132 3378 3378 D Zygote : begin preload
09-12 22:00:42.132 3378 3378 I Zygote : Installing ICU cache reference pinning...
09-12 22:00:42.132 3378 3378 I Zygote : Preloading ICU data...
09-12 22:00:42.135 3379 3379 I Zygote : Accepting command socket connections
09-12 22:00:42.138 3378 3378 I Zygote : Preloading classes...
09-12 22:00:42.140 3436 3436 I crash_dump64: obtaining output fd from tombstoned, type: kDebuggerdTombstone
09-12 22:00:42.140 3184 3184 I /system/bin/tombstoned: received crash request for pid 3384
09-12 22:00:42.141 3436 3436 I crash_dump64: performing dump of process 3384 (target tid = 3384)
09-12 22:00:42.143 3436 3436 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
09-12 22:00:42.143 3436 3436 F DEBUG : Build fingerprint: 'NVIDIA/darcy/darcy:9/PPR1.180610.011/4079208_2235.1395:user/release-keys'
09-12 22:00:42.143 3436 3436 F DEBUG : Revision: '0'
09-12 22:00:42.143 3436 3436 F DEBUG : ABI: 'arm64'
09-12 22:00:42.143 3436 3436 F DEBUG : pid: 3384, tid: 3384, name: surfaceflinger >>> /system/bin/surfaceflinger <<<
09-12 22:00:42.143 3436 3436 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
09-12 22:00:42.143 3436 3436 F DEBUG : Cause: null pointer dereference
09-12 22:00:42.143 3436 3436 F DEBUG : x0 0000000000000000 x1 0000000000000000 x2 0000000000000000 x3 00000025b1c537d0
09-12 22:00:42.143 3436 3436 F DEBUG : x4 0000000000000000 x5 0000007fe38db898 x6 0000000000000000 x7 0000000000000030
09-12 22:00:42.143 3436 3436 F DEBUG : x8 0101010101010101 x9 b72fc0062f2280b8 x10 000000005f647079 x11 0000000000000000
09-12 22:00:42.143 3436 3436 F DEBUG : x12 0000000000000001 x13 0000000000000000 x14 0000000000000001 x15 00000025b1c81a88
09-12 22:00:42.143 3436 3436 F DEBUG : x16 000000252f3b9e58 x17 00000025307de610 x18 0000000000000001 x19 00000025b1c537d0
09-12 22:00:42.143 3436 3436 F DEBUG : x20 0000000000000000 x21 0000000000000000 x22 000000252ed0c5e0 x23 0000000000000000
09-12 22:00:42.143 3436 3436 F DEBUG : x24 0000000000000001 x25 0000007fe38dbb00 x26 00000000000f4240 x27 0000007fe38dbb00
09-12 22:00:42.143 3436 3436 F DEBUG : x28 0000007fe38dba90 x29 0000007fe38db900
09-12 22:00:42.143 3436 3436 F DEBUG : sp 0000007fe38db8e0 lr 000000252f396f78 pc 00000025307de620
09-12 22:00:42.146 3378 3378 I PackageBackwardCompatibility: Loaded android.content.pm.OrgApacheHttpLegacyUpdater
Any pointers to what I am doing wrong, or how to further debug would be appreciated.
Also if there is already a kernel built with Wireguard support, a reference to that would be :good:
Hi, I've compiled kernel for Shield 2017 following your steps and I'm probably facing same issue. My boot hangs on Nvidia logo. I have a question - how you've obtained boot logs? ADB don't work from fastboot menu for me.
Hi, did you finally succeed in compiling a kernel for shield 2017 ?

Cannot use internal storage

Hello,
since today I cannot use/see my internal storage. But in TWRP it is usable. I get all the time this error:
Code:
ndroid.database.sqlite.SQLiteCantOpenDatabaseException: Cannot open database '/data/user/0/com.android.providers.media.module/databases/external.db': File /data/user/0/com.android.providers.media.module/databases/external.db doesn't exist
at android.database.sqlite.SQLiteConnection.open(Unknown Source:283)
at android.database.sqlite.SQLiteConnection.open(Unknown Source:5)
at android.database.sqlite.SQLiteConnectionPool.openConnectionLocked(Unknown Source:6)
at android.database.sqlite.SQLiteConnectionPool.open(Unknown Source:3)
at android.database.sqlite.SQLiteConnectionPool.open(Unknown Source:7)
at android.database.sqlite.SQLiteDatabase.openInner(Unknown Source:6)
at android.database.sqlite.SQLiteDatabase.open(Unknown Source:2)
at android.database.sqlite.SQLiteDatabase.openDatabase(Unknown Source:49)
at android.database.sqlite.SQLiteDatabase.openDatabase(Unknown Source:4)
at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(Unknown Source:81)
at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(Unknown Source:2)
at com.android.providers.media.DatabaseHelper.setFilterVolumeNames(DatabaseHelper.java:226)
at com.android.providers.media.MediaProvider.lambda$updateVolumes$0(MediaProvider.java:386)
at com.android.providers.media.MediaProvider.lambda$updateVolumes$0$MediaProvider(Unknown Source:0)
at com.android.providers.media.-$$Lambda$MediaProvider$xkbvwfxDRx2gMdY_Cje8WjPqJTM.run(Unknown Source:2)
at android.os.Handler.handleCallback(Unknown Source:2)
at android.os.Handler.dispatchMessage(Unknown Source:4)
at android.os.Looper.loop(Unknown Source:249)
at android.os.HandlerThread.run(Unknown Source:28)
Caused by: android.database.sqlite.SQLiteCantOpenDatabaseException: unknown error (code 14 SQLITE_CANTOPEN): Could not open database
at android.database.sqlite.SQLiteConnection.nativeOpen(Native Method)
at android.database.sqlite.SQLiteConnection.open(Unknown Source:36)
... 18 more

Categories

Resources