[Q] Mytouch 4g camera issues - myTouch 4G Q&A, Help & Troubleshooting

I hate starting new threads and I did my research before creating this thread.
I update mytouch 4g to gingerbread stock and my camera just show black screen, i factory reset it but same result. Then I downgrade it, root it to see if that will fix the problem and it didn't. now I installed cm 7.03 rom and still give me black screen.why this happen? is the rear camera mess up or the front one?
if any one can help me I will appreciate (no im not covering the Camera LOL )
here is the log cat
when i tried to open fun camera app
10-03 04:42:54.688 1956 1962 D Finsky : [8] NotificationManager.showNotification: Showing notification: [package=com.spiceloop.camerafunfree, Title=Camera Fun Free, Message=Successfully installed.]
10-03 04:43:09.008 2218 2218 D dalvikvm: Trying to load lib /data/data/com.spiceloop.camerafunfree/lib/libfx.so 0x40515038
10-03 04:43:09.028 2218 2218 D dalvikvm: Added shared lib /data/data/com.spiceloop.camerafunfree/lib/libfx.so 0x40515038
10-03 04:43:09.028 2218 2218 D dalvikvm: No JNI_OnLoad found in /data/data/com.spiceloop.camerafunfree/lib/libfx.so 0x40515038, skipping init
10-03 04:43:09.068 1404 1404 D QualcommCameraHardware: createInstance: E
10-03 04:43:09.068 1404 1404 D QualcommCameraHardware: Storing the current target type as 2
10-03 04:43:09.068 1404 1404 D QualcommCameraHardware: constructor EX
10-03 04:43:09.068 1404 1404 D QualcommCameraHardware: startCamera E
10-03 04:43:09.138 1404 1404 D QualcommCameraHardware: loading liboemcamera at 0xb000dc88
10-03 04:43:09.138 1404 1404 I QualcommCameraHardware: Set main cam and main cam only
10-03 04:43:09.138 1404 1404 I QualcommCameraHardware: Open Device node : /dev/msm_camera/control0
10-03 04:43:09.138 1404 1404 E QualcommCameraHardware: startCamera X: /dev/msm_camera/control0 open failed: No such file or directory!
10-03 04:43:09.138 1404 1404 E QualcommCameraHardware: createInstance: startCamera failed!
10-03 04:43:09.138 1404 1404 D QualcommCameraHardware: ~QualcommCameraHardware E
10-03 04:43:50.008 1511 1548 I InputDispatcher: Application is not responding: AppWindowToken{40756308 token=HistoryRecord{406d53e0 com.spiceloop.camerafunfree/com.spiceloop.camerafun.library.MainController}}. 5003.0ms since event, 5002.9ms since wait started
this log cat is when i tried to open stock camera app
10-03 04:53:00.679 2476 2487 V CameraHolder: open camera 0
10-03 04:53:11.249 1511 1548 I InputDispatcher: Application is not responding: AppWindowToken{4073faf8 token=HistoryRecord{40773108 com.android.camera/.Camera}}. 5004.1ms since event, 5003.8ms since wait started

TechKing1987 said:
I hate starting new threads and I did my research before creating this thread.
I update mytouch 4g to gingerbread stock and my camera just show black screen, i factory reset it but same result. Then I downgrade it, root it to see if that will fix the problem and it didn't. now I installed cm 7.03 rom and still give me black screen.why this happen? is the rear camera mess up or the front one?
if any one can help me I will appreciate (no im not covering the Camera LOL )
here is the log cat
when i tried to open fun camera app
10-03 04:42:54.688 1956 1962 D Finsky : [8] NotificationManager.showNotification: Showing notification: [package=com.spiceloop.camerafunfree, Title=Camera Fun Free, Message=Successfully installed.]
10-03 04:43:09.008 2218 2218 D dalvikvm: Trying to load lib /data/data/com.spiceloop.camerafunfree/lib/libfx.so 0x40515038
10-03 04:43:09.028 2218 2218 D dalvikvm: Added shared lib /data/data/com.spiceloop.camerafunfree/lib/libfx.so 0x40515038
10-03 04:43:09.028 2218 2218 D dalvikvm: No JNI_OnLoad found in /data/data/com.spiceloop.camerafunfree/lib/libfx.so 0x40515038, skipping init
10-03 04:43:09.068 1404 1404 D QualcommCameraHardware: createInstance: E
10-03 04:43:09.068 1404 1404 D QualcommCameraHardware: Storing the current target type as 2
10-03 04:43:09.068 1404 1404 D QualcommCameraHardware: constructor EX
10-03 04:43:09.068 1404 1404 D QualcommCameraHardware: startCamera E
10-03 04:43:09.138 1404 1404 D QualcommCameraHardware: loading liboemcamera at 0xb000dc88
10-03 04:43:09.138 1404 1404 I QualcommCameraHardware: Set main cam and main cam only
10-03 04:43:09.138 1404 1404 I QualcommCameraHardware: Open Device node : /dev/msm_camera/control0
10-03 04:43:09.138 1404 1404 E QualcommCameraHardware: startCamera X: /dev/msm_camera/control0 open failed: No such file or directory!
10-03 04:43:09.138 1404 1404 E QualcommCameraHardware: createInstance: startCamera failed!
10-03 04:43:09.138 1404 1404 D QualcommCameraHardware: ~QualcommCameraHardware E
10-03 04:43:50.008 1511 1548 I InputDispatcher: Application is not responding: AppWindowToken{40756308 token=HistoryRecord{406d53e0 com.spiceloop.camerafunfree/com.spiceloop.camerafun.library.MainController}}. 5003.0ms since event, 5002.9ms since wait started
this log cat is when i tried to open stock camera app
10-03 04:53:00.679 2476 2487 V CameraHolder: open camera 0
10-03 04:53:11.249 1511 1548 I InputDispatcher: Application is not responding: AppWindowToken{4073faf8 token=HistoryRecord{40773108 com.android.camera/.Camera}}. 5004.1ms since event, 5003.8ms since wait started
Click to expand...
Click to collapse
I also updated to Stock Gingerbread,few day ago.But my Camera & everything works fine..

I am having the same issue. I have the update and now my camera is not working. It is also showing a black screen. Anyone have any ideas.

Ant ideas to the fix for this.

Related

Problem with [ROM] [4.2.1] cm10.1 unofficial [2-2-13] 3.0.59 kernel & aosp [4.2.2] [

Problem with [ROM] [4.2.1] cm10.1 unofficial [2-2-13] 3.0.59 kernel & aosp [4.2.2] [
Hi guys,
My problem with this ROM on Topic " [ROM] [4.2.1] cm10.1 unofficial [2-2-13] 3.0.59 kernel & aosp [4.2.2] [.65] 2-23-13"
is on option STORAGE in Settings Menu.
Show me a message "Unfortunately. Setting has Stopped".
Have a solution ?
Re: Problem with [ROM] [4.2.1] cm10.1 unofficial [2-2-13] 3.0.59 kernel & aosp [4.2.
Something probably within the rom. Are you trying to mount sd or something?
HTC Vivid with Sense 4+ ICS 4.0.4
Only my SD CARD
[email protected] said:
Something probably within the rom. Are you trying to mount sd or something?
HTC Vivid with Sense 4+ ICS 4.0.4
Click to expand...
Click to collapse
Rotation
Sorry for changing the topic but I have this same ROM and everything works except for landscape mode and auto rotate.
minidz said:
Sorry for changing the topic but I have this same ROM and everything works except for landscape mode and auto rotate.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=38573051&postcount=226
Works for me
New issue
When a take a pic with my camera in autoflash or static flash this pic sometimes is dark as if my phone don have a flash
Confirm OP's issue and...
I can confirm OP's issue. I followed the official downgrade and flash instructions for CM7 yesterday and after getting fed up with that backtracked and installed aosp 4.2.2.2. Storage does crash after 250 to 500 ms.
<del>I'm also having trouble getting 4g connection. I don't have the 4g anymore.</del> Though after updating my baseband to baseband version 12.58.60.25U_26.11.04.03_M I am getting notably better reception in my house. I can't be certain 4g reception isn't just a fluke since I have yet to go out driving. edit: The H icon indicates advanced HSPA+ speeds. No problem. Thank you.
The big issue is getting my camera to work but BIG thanks to Nicgrainer I learned about acatlog and got some interesting information. This problem was happening to me before so I can't rule out a hardware issue but the log is encouraging. I thought I'd done a complete wipe before updating. I did the CWM wipe and dalvik cache wipe but maybe that misses something. The most important parts of the log appear to me the following:
E/QualcommCameraHardware( 104): android::QualcommCameraHardware::QualcommCameraHardware(): build changelist:
E/QualcommCameraHardware( 104): android::QualcommCameraHardware::QualcommCameraHardware(): build date: Thu Feb 21 00:16:30 CST 2013
E/QualcommCameraHardware( 104): android::QualcommCameraHardware::QualcommCameraHardware(): build description: full_vision-eng 4.2.2 JDQ39 eng.fyodor.20130221.001544 test-keys
E/QualcommCameraHardware( 104): android::QualcommCameraHardware::QualcommCameraHardware(): sense version:
D/QualcommCameraHardware( 104): constructor EX
I/QualcommCameraHardware( 104): createInstance: created hardware=0x25cbc0
D/QualcommCameraHardware( 104): startCamera E
D/QualcommCameraHardware( 104): loading liboemcamera at 0x40085dec
D/QualcommCameraHardware( 104): Set main cam and main cam only
I/mm-camera( 104): set sensor selection :0
D/QualcommCameraHardware( 104): Open Device node : /dev/msm_camera/control0
E/QualcommCameraHardware( 104): startCamera X: /dev/msm_camera/control0 open failed: No such file or directory!
E/QualcommCameraHardware( 104): createInstance: startCamera failed!
E/CameraClient( 104): Could not open camera 0: -1
E/CameraClient( 104): initialize: Camera 0: unable to initialize device: Operation not permitted (-1)
I/CameraClient( 104): Destroying camera 0
V/StateManager( 3108): startState class com.android.gallery3d.app.PhotoPage
E/CameraHolder( 3108): fail to connect Camera
E/CameraHolder( 3108): java.lang.RuntimeException: Fail to connect to camera service
And here follows everything relevant to opening the app Camera down to opening alogcat to view the log. Any thoughts?
Code:
[snip]
V/CameraHolder( 3108): open camera 0
I/AwesomePlayer( 104): setDataSource_l(URL suppressed)
D/MediaExtractor( 104): returning default extractor
I/AwesomePlayer( 104): setDataSource_l(URL suppressed)
D/MediaExtractor( 104): returning default extractor
D/dalvikvm( 3108): GC_CONCURRENT freed 95K, 2% free 6677K/6804K, paused 20ms+10ms, total 81ms
D/dalvikvm( 3108): WAIT_FOR_CONCURRENT_GC blocked 13ms
I/CameraClient( 104): Opening camera 0
I/QualcommCameraHardware( 104): openCameraHardware: call createInstance cameraId 0
I/QualcommCameraHardware( 104): createInstance: E
D/DHDiagnostic( 104): android::DHDiagnostic::DHDiagnostic() E
D/DHDiagnostic( 104): android::DHDiagnostic::DHDiagnostic() X
D/DHDiagnostic( 104): android::DHDiagnostic::DHDiagnostic() E
D/DHDiagnostic( 104): android::DHDiagnostic::DHDiagnostic() X
D/CameraPP( 104): CameraPP::CameraPP()
D/SDO_PP ( 104): SDO_PP::SDO_PP()
I/OlaEngine( 104): [Ola_Engine_Create:79] engine build info [ name ] : htc
I/OlaEngine( 104): [Ola_Engine_Create:83] engine build info [ date ] : 2012-02-14 14:49:38
I/OlaEngine( 104): [Ola_Engine_Create:87] engine build info [ version ] : __bulid_revision_226__
D/CameraFace_OLA( 104): create OlaEngine
I/FD ( 104): [Ola_FaceDetector_Create:135] create num : 2
D/CameraFace_OLA( 104): create Ola FD
V/Olaworks( 104): [Ola_BeautyShotEngine_Create] prr(0x001dabc0)
D/CameraFace_OLA( 104): create Ola BS
D/CameraFace_OLA( 104): create Ola SD
D/CameraFace_OLA( 104): create Ola BD
D/CameraFace( 104): alloc face_t 0x2db650 num 10
D/QualcommCameraHardware( 104): Storing the current target type as 2
I/CAF_Sensor( 104): android::CAFSensorListener::CAFSensorListener() E
I/CAF_Sensor( 104): android::CAFSensorListener::CAFSensorListener() X
I/CAF_Sensor( 104): android::status_t android::CAFSensorListener::initialize() E
I/CAF_Sensor( 104): android::status_t android::CAFSensorListener::initialize() X
I/CAF_Sensor( 104): void android::CAFSensorListener::setCallbacks(void (*)(int, void*), void*) E
I/CAF_Sensor( 104): void android::CAFSensorListener::setCallbacks(void (*)(int, void*), void*) X
E/QualcommCameraHardware( 104): android::QualcommCameraHardware::QualcommCameraHardware(): build changelist:
E/QualcommCameraHardware( 104): android::QualcommCameraHardware::QualcommCameraHardware(): build date: Thu Feb 21 00:16:30 CST 2013
E/QualcommCameraHardware( 104): android::QualcommCameraHardware::QualcommCameraHardware(): build description: full_vision-eng 4.2.2 JDQ39 eng.fyodor.20130221.001544 test-keys
E/QualcommCameraHardware( 104): android::QualcommCameraHardware::QualcommCameraHardware(): sense version:
D/QualcommCameraHardware( 104): constructor EX
I/QualcommCameraHardware( 104): createInstance: created hardware=0x25cbc0
D/QualcommCameraHardware( 104): startCamera E
D/QualcommCameraHardware( 104): loading liboemcamera at 0x40085dec
D/QualcommCameraHardware( 104): Set main cam and main cam only
I/mm-camera( 104): set sensor selection :0
D/QualcommCameraHardware( 104): Open Device node : /dev/msm_camera/control0
E/QualcommCameraHardware( 104): startCamera X: /dev/msm_camera/control0 open failed: No such file or directory!
E/QualcommCameraHardware( 104): createInstance: startCamera failed!
E/CameraClient( 104): Could not open camera 0: -1
E/CameraClient( 104): initialize: Camera 0: unable to initialize device: Operation not permitted (-1)
I/CameraClient( 104): Destroying camera 0
V/StateManager( 3108): startState class com.android.gallery3d.app.PhotoPage
E/CameraHolder( 3108): fail to connect Camera
E/CameraHolder( 3108): java.lang.RuntimeException: Fail to connect to camera service
E/CameraHolder( 3108): at android.hardware.Camera.native_setup(Native Method)
E/CameraHolder( 3108): at android.hardware.Camera.<init>(Camera.java:340)
E/CameraHolder( 3108): at android.hardware.Camera.open(Camera.java:302)
E/CameraHolder( 3108): at com.android.camera.CameraManager.cameraOpen(CameraManager.java:283)
E/CameraHolder( 3108): at com.android.camera.CameraHolder.open(CameraHolder.java:210)
E/CameraHolder( 3108): at com.android.camera.Util.openCamera(Util.java:315)
E/CameraHolder( 3108): at com.android.camera.PhotoModule$CameraStartUpThread.run(PhotoModule.java:316)
W/dalvikvm( 3108): threadid=12: thread exiting with uncaught exception (group=0x40ab4930)
E/AndroidRuntime( 3108): FATAL EXCEPTION: Thread-338
E/AndroidRuntime( 3108): java.lang.RuntimeException: openCamera failed
E/AndroidRuntime( 3108): at com.android.camera.Util.openCamera(Util.java:320)
E/AndroidRuntime( 3108): at com.android.camera.PhotoModule$CameraStartUpThread.run(PhotoModule.java:316)
E/AndroidRuntime( 3108): Caused by: com.android.camera.CameraHardwareException: java.lang.RuntimeException: Fail to connect to camera service
E/AndroidRuntime( 3108): at com.android.camera.CameraHolder.open(CameraHolder.java:219)
E/AndroidRuntime( 3108): at com.android.camera.Util.openCamera(Util.java:315)
E/AndroidRuntime( 3108): ... 1 more
E/AndroidRuntime( 3108): Caused by: java.lang.RuntimeException: Fail to connect to camera service
E/AndroidRuntime( 3108): at android.hardware.Camera.native_setup(Native Method)
E/AndroidRuntime( 3108): at android.hardware.Camera.<init>(Camera.java:340)
E/AndroidRuntime( 3108): at android.hardware.Camera.open(Camera.java:302)
E/AndroidRuntime( 3108): at com.android.camera.CameraManager.cameraOpen(CameraManager.java:283)
E/AndroidRuntime( 3108): at com.android.camera.CameraHolder.open(CameraHolder.java:210)
E/AndroidRuntime( 3108): ... 2 more
W/ActivityManager( 359): Force finishing activity com.android.gallery3d/com.android.camera.CameraLauncher
D/dalvikvm( 359): GC_FOR_ALLOC freed 477K, 16% free 12609K/14908K, paused 143ms, total 144ms
V/NFC ( 3108): this device does not have NFC support
D/dalvikvm( 3108): GC_CONCURRENT freed 162K, 3% free 6937K/7128K, paused 3ms+2ms, total 54ms
D/dalvikvm( 3108): WAIT_FOR_CONCURRENT_GC blocked 9ms
W/SensorService( 359): sensor 00000000 already enabled in connection 0x5fa448 (ignoring)
W/ActivityManager( 359): Activity pause timeout for ActivityRecord{4148f470 u0 com.android.gallery3d/com.android.camera.CameraLauncher}
I/ActivityManager( 359): No longer want com.android.providers.calendar (pid 2789): empty #7
I/Process ( 3108): Sending signal. PID: 3108 SIG: 9
W/InputMethodManagerService( 359): Window already focused, ignoring focus gain of: [email protected] attribute=null, token = [email protected]
I/ActivityManager( 359): Process com.android.gallery3d (pid 3108) has died.
I/WindowState( 359): WIN DEATH: Window{416a86e8 u0 com.android.gallery3d/com.android.camera.CameraLauncher}
I/ActivityManager( 359): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=org.jtb.alogcat/.LogActivity} from pid 553
[/snip]

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

Clock app crashes on update from 4.4.2 to 4.4.4

I just updated from a personal build of OmniROM 4.4.2 (c. April) to a build off the latest sources on my Nexus 5. When I launch "Clock" it immediately crashes, without opening.
10-03 23:07:38.544 E/AndroidRuntime(12780): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.deskclock/com.android.deskclock.DeskClock}: android.database.sqlite.SQLiteException: no such column: preAlarm (code 1): , while compiling: SELECT _id, year, month, day, hour, minutes, label, vibrate, ringtone, alarm_id, alarm_state, incvol, preAlarm, alarmVol, preAlarmVol, preAlarmTime, preAlarmRingtone, painMode, randomMode, mediaStart FROM alarm_instances WHERE (alarm_state<5)
Did I miss a manual upgrade step somewhere? I can always hack the database manually (or wipe it), but if there is a "better" fix, I'd appreciate knowing about it.
More log:
10-03 23:07:38.534 E/SQLiteLog(12780): (1) no such column: preAlarm
10-03 23:07:38.534 D/AndroidRuntime(12780): Shutting down VM
10-03 23:07:38.534 W/dalvikvm(12780): threadid=1: thread exiting with uncaught exception (group=0x41570ba8)
10-03 23:07:38.544 E/AndroidRuntime(12780): FATAL EXCEPTION: main
10-03 23:07:38.544 E/AndroidRuntime(12780): Process: com.android.deskclock, PID: 12780
10-03 23:07:38.544 E/AndroidRuntime(12780): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.deskclock/com.android.deskclock.DeskClock}: android.database.sqlite.SQLiteException: no such column: preAlarm (code 1): , while compiling: SELECT _id, year, month, day, hour, minutes, label, vibrate, ringtone, alarm_id, alarm_state, incvol, preAlarm, alarmVol, preAlarmVol, preAlarmTime, preAlarmRingtone, painMode, randomMode, mediaStart FROM alarm_instances WHERE (alarm_state<5)
10-03 23:07:38.544 E/AndroidRuntime(12780): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2184)
10-03 23:07:38.544 E/AndroidRuntime(12780): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2233)
10-03 23:07:38.544 E/AndroidRuntime(12780): at android.app.ActivityThread.access$800(ActivityThread.java:135)
10-03 23:07:38.544 E/AndroidRuntime(12780): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1196)
10-03 23:07:38.544 E/AndroidRuntime(12780): at android.os.Handler.dispatchMessage(Handler.java:102)
10-03 23:07:38.544 E/AndroidRuntime(12780): at android.os.Looper.loop(Looper.java:136)
10-03 23:07:38.544 E/AndroidRuntime(12780): at android.app.ActivityThread.main(ActivityThread.java:5001)
10-03 23:07:38.544 E/AndroidRuntime(12780): at java.lang.reflect.Method.invokeNative(Native Method)
10-03 23:07:38.544 E/AndroidRuntime(12780): at java.lang.reflect.Method.invoke(Method.java:515)
10-03 23:07:38.544 E/AndroidRuntime(12780): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:785)
10-03 23:07:38.544 E/AndroidRuntime(12780): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:601)
10-03 23:07:38.544 E/AndroidRuntime(12780): at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:132)
10-03 23:07:38.544 E/AndroidRuntime(12780): at dalvik.system.NativeStart.main(Native Method)
10-03 23:07:38.544 E/AndroidRuntime(12780): Caused by: android.database.sqlite.SQLiteException: no such column: preAlarm (code 1): , while compiling: SELECT _id, year, month, day, hour, minutes, label, vibrate, ringtone, alarm_id, alarm_state, incvol, preAlarm, alarmVol, preAlarmVol, preAlarmTime, preAlarmRingtone, painMode, randomMode, mediaStart FROM alarm_instances WHERE (alarm_state<5)
10-03 23:07:38.544 E/AndroidRuntime(12780): at android.database.sqlite.SQLiteConnection.nativePrepareStatement(Native Method)
10-03 23:07:38.544 E/AndroidRuntime(12780): at android.database.sqlite.SQLiteConnection.acquirePreparedStatement(SQLiteConnection.java:889)
10-03 23:07:38.544 E/AndroidRuntime(12780): at android.database.sqlite.SQLiteConnection.prepare(SQLiteConnection.java:500)
10-03 23:07:38.544 E/AndroidRuntime(12780): at android.database.sqlite.SQLiteSession.prepare(SQLiteSession.java:588)
10-03 23:07:38.544 E/AndroidRuntime(12780): at android.database.sqlite.SQLiteProgram.<init>(SQLiteProgram.java:58)
10-03 23:07:38.544 E/AndroidRuntime(12780): at android.database.sqlite.SQLiteQuery.<init>(SQLiteQuery.java:37)
10-03 23:07:38.544 E/AndroidRuntime(12780): at android.database.sqlite.SQLiteDirectCursorDriver.query(SQLiteDirectCursorDriver.java:44)
10-03 23:07:38.544 E/AndroidRuntime(12780): at android.database.sqlite.SQLiteDatabase.rawQueryWithFactory(SQLiteDatabase.java:1314)
10-03 23:07:38.544 E/AndroidRuntime(12780): at android.database.sqlite.SQLiteQueryBuilder.query(SQLiteQueryBuilder.java:400)
10-03 23:07:38.544 E/AndroidRuntime(12780): at android.database.sqlite.SQLiteQueryBuilder.query(SQLiteQueryBuilder.java:294)
10-03 23:07:38.544 E/AndroidRuntime(12780): at com.android.deskclock.provider.ClockProvider.query(ClockProvider.java:97)
10-03 23:07:38.544 E/AndroidRuntime(12780): at android.content.ContentProvider.query(ContentProvider.java:857)
10-03 23:07:38.544 E/AndroidRuntime(12780): at android.content.ContentProvider$Transport.query(ContentProvider.java:200)
10-03 23:07:38.544 E/AndroidRuntime(12780): at android.content.ContentResolver.query(ContentResolver.java:461)
10-03 23:07:38.544 E/AndroidRuntime(12780): at android.content.ContentResolver.query(ContentResolver.java:404)
10-03 23:07:38.544 E/AndroidRuntime(12780): at com.android.deskclock.provider.AlarmInstance.getInstances(AlarmInstance.java:227)
10-03 23:07:38.544 E/AndroidRuntime(12780): at com.android.deskclock.alarms.AlarmStateManager.updateNextAlarm(AlarmStateManager.java:152)
10-03 23:07:38.544 E/AndroidRuntime(12780): at com.android.deskclock.DeskClock.onCreate(DeskClock.java:182)
10-03 23:07:38.544 E/AndroidRuntime(12780): at android.app.Activity.performCreate(Activity.java:5275)
10-03 23:07:38.544 E/AndroidRuntime(12780): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1087)
10-03 23:07:38.544 E/AndroidRuntime(12780): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2148)
10-03 23:07:38.544 E/AndroidRuntime(12780): ... 12 more
10-03 23:07:38.544 W/ActivityManager( 933): Force finishing activity com.android.deskclock/.DeskClock
10-03 23:07:38.554 W/DropBoxManagerService( 933): Dropping: system_app_crash (3491 > 0 bytes)
10-03 23:07:38.854 I/WindowManager( 933): Screenshot max retries 4 of Token{437da850 ActivityRecord{42dc2810 u0 com.android.deskclock/.DeskClock t12 f}} appWin=Window{42db7920 u0 Starting com.android.deskclock} drawState=4
10-03 23:07:38.854 W/WindowManager( 933): Screenshot failure taking screenshot for (1080x1920) to layer 21025
10-03 23:07:39.344 W/ActivityManager( 933): Activity pause timeout for ActivityRecord{42dc2810 u0 com.android.deskclock/.DeskClock t12 f}
Clear clock app data should be enough

(TB-8504x) Lenovo tab 4 8: Fix facelock ("Face Unlock") crash

Lenovo Tab 4 8 - Fix facelock crash (Related gist: https://gist.github.com/KreAch3R/734b1086c928ab8ceeafaf3e4dbd8c33)
I noticed that a Lenovo tab 4 8 (tb-8504x) on the latest stock image as of today didn't have a working face unlock ("facelock"). When it was time to add a new face, it crashed with the following log:
Code:
08-16 17:39:34.379 6600 6600 D AndroidRuntime: Shutting down VM
08-16 17:39:34.380 6600 6600 E AndroidRuntime: FATAL EXCEPTION: main
08-16 17:39:34.380 6600 6600 E AndroidRuntime: Process: com.android.facelock, PID: 6600
08-16 17:39:34.380 6600 6600 E AndroidRuntime: java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "_ZN6google8protobuf5Arena15AllocateAlignedEPKSt9type_infom" referenced by "/system/lib64/libfacenet.so"...
08-16 17:39:34.380 6600 6600 E AndroidRuntime: at java.lang.Runtime.loadLibrary0(Runtime.java:989)
08-16 17:39:34.380 6600 6600 E AndroidRuntime: at java.lang.System.loadLibrary(System.java:1530)
08-16 17:39:34.380 6600 6600 E AndroidRuntime: at com.google.android.libraries.vision.facenet.FaceNet.<clinit>(FaceNet.java:67)
08-16 17:39:34.380 6600 6600 E AndroidRuntime: at com.google.android.libraries.vision.facenet.FaceNet.createFromAssets(FaceNet.java:118)
08-16 17:39:34.380 6600 6600 E AndroidRuntime: at com.android.facelock.FaceLockUtil.initialize(FaceLockUtil.java:148)
08-16 17:39:34.380 6600 6600 E AndroidRuntime: at com.android.facelock.SetupEnrollmentScreen.onCreate(SetupEnrollmentScreen.java:517)
08-16 17:39:34.380 6600 6600 E AndroidRuntime: at android.app.Activity.performCreate(Activity.java:6720)
08-16 17:39:34.380 6600 6600 E AndroidRuntime: at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1119)
08-16 17:39:34.380 6600 6600 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2618)
08-16 17:39:34.380 6600 6600 E AndroidRuntime: at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2726)
08-16 17:39:34.380 6600 6600 E AndroidRuntime: at android.app.ActivityThread.-wrap12(ActivityThread.java)
08-16 17:39:34.380 6600 6600 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1477)
08-16 17:39:34.380 6600 6600 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
08-16 17:39:34.380 6600 6600 E AndroidRuntime: at android.os.Looper.loop(Looper.java:154)
08-16 17:39:34.380 6600 6600 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6119)
08-16 17:39:34.380 6600 6600 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
08-16 17:39:34.380 6600 6600 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886)
08-16 17:39:34.380 6600 6600 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776)
08-16 17:39:34.383 1428 2305 W ActivityManager: Force finishing activity com.android.facelock/.SetupEnrollmentScreen
The FIX
1. Download libfacenet.so from Open-GApps [Direct link to the binary I used].
2. Follow the instructions from here and download @dywersant 's magisk-remount.zip module from here.
3. Boot into Android with a RW /system using the module. You can confirm with:
Code:
su
cd /system
touch testfile.txt
If the command succeeds, you have a writable /system.
4. Go into the lib64 folder (/system/lib64)
5. Make a backup of the original libfacenet.so file:
Code:
cp /system/lib64/libfacenet.so /sdcard/libfacenet.so.orig
BE CAREFUL: Don't make the backup inside the /system partition, as it can be lost after reboot!
6. Mount the specific file as RW
I don't know how or why, but Lenovo seems to have made every lib file a different ro mount point/partition. So:
Code:
mount -o rw,remount /system/lib64/libfacenet.so
is needed, otherwise you end up with "read only file system" error (even when the whole /system is RW!)
7. Push to /sdcard and replace the file
Code:
cp /sdcard/libfacenet.so /system/lib64/libfacenet.so
Now, try to add a new face again. It should work!
--------------------------------------------------------------
Debugging
If anyone is interested to know how. You always start from the log. Let's disect this line:
Code:
java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "_ZN6google8protobuf5Arena15AllocateAlignedEPKSt9type_infom" referenced by "/system/lib64/libfacenet.so"
This tells us that the app com.android.facelock launched and called the library libfacenet.so which referenced a method/symbol/whatever named _ZN6google8protobuf5Arena15AllocateAlignedEPKSt9type_infom but that method doesn't exist inside whatever should include it, so "dlopen" failed and we got ourselves the "java.lang.UnsatisfiedLinkError" error. Let's sum up:
1. The app that crashes is com.android.facelock
2. One related .so lib is libfacenet.so
3. There is another one, unnamed, that should contain _ZN6google8protobuf5Arena15AllocateAlignedEPKSt9type_infom but it doesn't.
Googling about "_ZN6google8protobuf5Arena15AllocateAlignedEPKSt9type_infom" brings up some libprotobuf related results. This is good enough. Grepping through /system/lib64 shows up that there are two .so there:
Code:
libprotobuf-cpp-full.so
libprotobuf-cpp-lite.so
Doing the same in a working pixel image produces the same files. But obviously Facelock works on the Pixel but not on this tablet. We need a way to differentiate them (remember, pixel is on a Oreo base while this is Nougat).
Reading this StackExchange post, we find out about the "readelf -a -W elffile" command. Give this a try and you should see that a lot comes up. Next step, grepping through this file dump.
Lenovo libprotobuf-cpp-lite.so:
Code:
$ readelf -a -W libprotobuf-cpp-lite.so | grep _ZN6google8protobuf5Arena15AllocateAlignedEPKSt9type_infom
$
Pixel libprotobuf-cpp-lite.so:
Code:
$ readelf -a -W libprotobuf-cpp-lite.so | grep _ZN6google8protobuf5Arena15AllocateAlignedEPKSt9type_infom
000000000004fb10 0000005700000402 R_AARCH64_JUMP_SLOT 0000000000022254 _ZN6google8protobuf5Arena15AllocateAlignedEPKSt9type_infom + 0
87: 0000000000022254 216 FUNC GLOBAL DEFAULT 12 _ZN6google8protobuf5Arena15AllocateAlignedEPKSt9type_infom
Bingo! So we confirm that the libfacenet.so is trying to call an upstream method (probably), one that isn't bundled inside the libprotobuf-cpp-lite.so of the Lenovo stock image.
So now we know, it's a problem of version incompatibility. There are two things to try:
1. Replace libprotobuf-cpp-lite.so with a version that contains _ZN6google8protobuf5Arena15AllocateAlignedEPKSt9type_infom
2. Replaced libfacenet.so with a version that doesn't contain _ZN6google8protobuf5Arena15AllocateAlignedEPKSt9type_infom
Method No. 1 didn't work, while it got rid of the "java.lang.UnsatisfiedLinkError" error (confirming the diagnosis), it produced more .so related crashes, so I assume there were a lot more code that was incompatible. But Method No.2 worked as a charm!

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

Categories

Resources