HavocOS_2.9 Fastboot ROM - Asus Zenfone Max M2 ROMs, Kernels, Recoveries, & O

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

Related

[Q] Aaaggghhhhhh!!!! androidprocess.acore stopped unexpectedly

Ok, this is beginning to drive me crazy. Yes, I have searched the forum but have found very little in the way of answers. The only time I get this error is when trying to add a contact. What bothers me most is that adding a contact will work fine for a few days after clearing and flashing and then out of nowhere I get the failure again. I've tried every solution out there to repair the issue but it always comes back. Is anyone else experiencing this on the continuum? If you have but have gotten it correct could you please share your solution? I'm running adrenalyn's EC07 clean ROM after an Odin install of the SCH-I400-EC07-FROYO-REL-PRODUCTION ROM. I'm using Touchpal dialer but it doesn't matter if I use touchpal or the stock Touchwiz dialer & contact manager to add contacts. Any help would be greatly appreciated.
Thank you,
Ray
Reborn627 said:
Ok, this is beginning to drive me crazy. Yes, I have searched the forum but have found very little in the way of answers. The only time I get this error is when trying to add a contact. What bothers me most is that adding a contact will work fine for a few days after clearing and flashing and then out of nowhere I get the failure again. I've tried every solution out there to repair the issue but it always comes back. Is anyone else experiencing this on the continuum? If you have but have gotten it correct could you please share your solution? I'm running adrenalyn's EC07 clean ROM after an Odin install of the SCH-I400-EC07-FROYO-REL-PRODUCTION ROM. I'm using Touchpal dialer but it doesn't matter if I use touchpal or the stock Touchwiz dialer & contact manager to add contacts. Any help would be greatly appreciated.
Thank you,
Ray
Click to expand...
Click to collapse
i havent had any add concact troubles but i would try this:
uninstall touchpal
reboot into cwm
clear cache and dalvik
reboot.
see if twcontacts works again... just gotta trouble shoot from there.
i had a similar episode with go sms, it was texting peole that i never texted before.
also, when u flashed ec07clean over stock did u wipe cache and dalvik?
if you want to start by reflashing, i would back up, flash ec07.tar in odin. enter stock recovery, clear cache, apply update to enter cwm, clear cache there as well as dalvik, instal ec07clean.zip, wipe cache and dalvik again (i know lol) boot, reboot, reboot into cwm, advanced restore data only. reboot
that will give you a very clean reinstall of rom, plus keep your data upto date with when you did your new backup
now like i said, this is what I would do, not making you. and if you dont think its possible for you. please dont
ciscogee said:
i havent had any add concact troubles but i would try this:
uninstall touchpal
reboot into cwm
clear cache and dalvik
reboot.
see if twcontacts works again... just gotta trouble shoot from there.
i had a similar episode with go sms, it was texting peole that i never texted before.
also, when u flashed ec07clean over stock did u wipe cache and dalvik?
if you want to start by reflashing, i would back up, flash ec07.tar in odin. enter stock recovery, clear cache, apply update to enter cwm, clear cache there as well as dalvik, instal ec07clean.zip, wipe cache and dalvik again (i know lol) boot, reboot, reboot into cwm, advanced restore data only. reboot
that will give you a very clean reinstall of rom, plus keep your data upto date with when you did your new backup
now like i said, this is what I would do, not making you. and if you dont think its possible for you. please dont
Click to expand...
Click to collapse
Thanks for the reply. I'm clearing the caches again after removing Touchpal. I suppose that can't hurt. I did do a full clear before and after both the stock ROM and the clean ROM. We'll see what happens. This is super frustrating. I don't add contacts that often but it really stinks when you can't. Thanks for the suggestion. I'll keep you posted.
Ray
Still failed after clearing caches. I really don't want to re-flash AGAIN. It's almost as if there are updates to something that occur a few days after re-flash and re-install of my apps. For now I guess I just have to log into my google contacts and add them that way. I had mentioned an issue with my bluetooth last week. I thought I had cleared up the issue but it seems to be creeping back. Quirky phones these are!
Ray
A logcat of the error would help give a idea of what's going on
Sent from my SCH-I400 using xda premium
trailblazer101 said:
A logcat of the error would help give a idea of what's going on
Sent from my SCH-I400 using xda premium
Click to expand...
Click to collapse
Well, here ya go. This is the error log. Hopefully we can figure out what the "add contact" issue is. There are 2 failures in this log. Thanks for having a look.
Code:
10-28 16:19:16.746 E/imdg81 ( 2458): IsShutDownStarted()
10-28 16:19:16.860 E/imdg81 ( 2458): IsShutDownStarted()
10-28 16:19:23.895 E/TFResourceBroker( 9748): checkModule() id 4
10-28 16:19:23.895 E/TFResourceBroker( 9748): checkModule() ATTR id 4
10-28 16:19:23.899 E/TFResourceBroker( 9748): checkModule() id 261
10-28 16:19:23.899 E/TFResourceBroker( 9748): checkModule() STYLEABLE id 261
10-28 16:19:23.899 E/TFResourceBroker( 9748): checkModule() id 31
10-28 16:19:23.899 E/TFResourceBroker( 9748): checkModule() STYLEABLE id 31
10-28 16:19:24.086 E/Sources ( 9748): exception = java.lang.IllegalStateException: Couldn't find authenticator for specific account type
10-28 16:19:25.688 E/AndroidRuntime( 9748): FATAL EXCEPTION: AsyncTask #1
10-28 16:19:25.688 E/AndroidRuntime( 9748): java.lang.RuntimeException: An error occured while executing doInBackground()
10-28 16:19:25.688 E/AndroidRuntime( 9748): at android.os.AsyncTask$3.done(AsyncTask.java:200)
10-28 16:19:25.688 E/AndroidRuntime( 9748): at java.util.concurrent.FutureTask$Sync.innerSetException(FutureTask.java:273)
10-28 16:19:25.688 E/AndroidRuntime( 9748): at java.util.concurrent.FutureTask.setException(FutureTask.java:124)
10-28 16:19:25.688 E/AndroidRuntime( 9748): at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:307)
10-28 16:19:25.688 E/AndroidRuntime( 9748): at java.util.concurrent.FutureTask.run(FutureTask.java:137)
10-28 16:19:25.688 E/AndroidRuntime( 9748): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1068)
10-28 16:19:25.688 E/AndroidRuntime( 9748): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:561)
10-28 16:19:25.688 E/AndroidRuntime( 9748): at java.lang.Thread.run(Thread.java:1096)
10-28 16:19:25.688 E/AndroidRuntime( 9748): Caused by: java.lang.IllegalStateException: Top level element must be ContactsSource
10-28 16:19:25.688 E/AndroidRuntime( 9748): at com.android.contacts.model.ExternalSource.inflate(ExternalSource.java:134)
10-28 16:19:25.688 E/AndroidRuntime( 9748): at com.android.contacts.model.ExternalSource.inflate(ExternalSource.java:104)
10-28 16:19:25.688 E/AndroidRuntime( 9748): at com.android.contacts.model.ContactsSource.ensureInflated(ContactsSource.java:99)
10-28 16:19:25.688 E/AndroidRuntime( 9748): at com.android.contacts.model.Sources.getInflatedSource(Sources.java:568)
10-28 16:19:25.688 E/AndroidRuntime( 9748): at com.android.contacts.model.Sources.getAccountsExceptSNS(Sources.java:446)
10-28 16:19:25.688 E/AndroidRuntime( 9748): at com.android.contacts.ui.EditContactActivity$AddContactTask.doInBackground(EditContactActivity.java:2633)
10-28 16:19:25.688 E/AndroidRuntime( 9748): at com.android.contacts.ui.EditContactActivity$AddContactTask.doInBackground(EditContactActivity.java:2624)
10-28 16:19:25.688 E/AndroidRuntime( 9748): at com.android.contacts.util.WeakAsyncTask.doInBackground(WeakAsyncTask.java:45)
10-28 16:19:25.688 E/AndroidRuntime( 9748): at android.os.AsyncTask$2.call(AsyncTask.java:185)
10-28 16:19:25.688 E/AndroidRuntime( 9748): at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:305)
10-28 16:19:25.688 E/AndroidRuntime( 9748): ... 4 more
10-28 16:19:31.973 E/StatusBarPolicy( 2458): Intent : android.intent.action.BATTERY_CHANGED
10-28 16:19:32.664 E/StatusBarPolicy( 2458): Intent : android.intent.action.BATTERY_CHANGED
10-28 16:19:39.633 E/TFResourceBroker( 9887): checkModule() id 4
10-28 16:19:39.633 E/TFResourceBroker( 9887): checkModule() ATTR id 4
10-28 16:19:39.637 E/TFResourceBroker( 9887): checkModule() id 261
10-28 16:19:39.637 E/TFResourceBroker( 9887): checkModule() STYLEABLE id 261
10-28 16:19:39.637 E/TFResourceBroker( 9887): checkModule() id 31
10-28 16:19:39.637 E/TFResourceBroker( 9887): checkModule() STYLEABLE id 31
10-28 16:19:40.012 E/Sources ( 9887): exception = java.lang.IllegalStateException: Couldn't find authenticator for specific account type
10-28 16:19:40.813 E/AndroidRuntime( 9887): FATAL EXCEPTION: AsyncTask #1
10-28 16:19:40.813 E/AndroidRuntime( 9887): java.lang.RuntimeException: An error occured while executing doInBackground()
10-28 16:19:40.813 E/AndroidRuntime( 9887): at android.os.AsyncTask$3.done(AsyncTask.java:200)
10-28 16:19:40.813 E/AndroidRuntime( 9887): at java.util.concurrent.FutureTask$Sync.innerSetException(FutureTask.java:273)
10-28 16:19:40.813 E/AndroidRuntime( 9887): at java.util.concurrent.FutureTask.setException(FutureTask.java:124)
10-28 16:19:40.813 E/AndroidRuntime( 9887): at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:307)
10-28 16:19:40.813 E/AndroidRuntime( 9887): at java.util.concurrent.FutureTask.run(FutureTask.java:137)
10-28 16:19:40.813 E/AndroidRuntime( 9887): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1068)
10-28 16:19:40.813 E/AndroidRuntime( 9887): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:561)
10-28 16:19:40.813 E/AndroidRuntime( 9887): at java.lang.Thread.run(Thread.java:1096)
10-28 16:19:40.813 E/AndroidRuntime( 9887): Caused by: java.lang.IllegalStateException: Top level element must be ContactsSource
10-28 16:19:40.813 E/AndroidRuntime( 9887): at com.android.contacts.model.ExternalSource.inflate(ExternalSource.java:134)
10-28 16:19:40.813 E/AndroidRuntime( 9887): at com.android.contacts.model.ExternalSource.inflate(ExternalSource.java:104)
10-28 16:19:40.813 E/AndroidRuntime( 9887): at com.android.contacts.model.ContactsSource.ensureInflated(ContactsSource.java:99)
10-28 16:19:40.813 E/AndroidRuntime( 9887): at com.android.contacts.model.Sources.getInflatedSource(Sources.java:568)
10-28 16:19:40.813 E/AndroidRuntime( 9887): at com.android.contacts.model.Sources.getAccountsExceptSNS(Sources.java:446)
10-28 16:19:40.813 E/AndroidRuntime( 9887): at com.android.contacts.ui.EditContactActivity$AddContactTask.doInBackground(EditContactActivity.java:2633)
10-28 16:19:40.813 E/AndroidRuntime( 9887): at com.android.contacts.ui.EditContactActivity$AddContactTask.doInBackground(EditContactActivity.java:2624)
10-28 16:19:40.813 E/AndroidRuntime( 9887): at com.android.contacts.util.WeakAsyncTask.doInBackground(WeakAsyncTask.java:45)
10-28 16:19:40.813 E/AndroidRuntime( 9887): at android.os.AsyncTask$2.call(AsyncTask.java:185)
10-28 16:19:40.813 E/AndroidRuntime( 9887): at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:305)
10-28 16:19:40.813 E/AndroidRuntime( 9887): ... 4 more
10-28 16:19:46.617 E/StatusBarPolicy( 2458): Intent : android.intent.action.BATTERY_CHANGED
10-28 16:19:48.192 E/JavaBinder( 2458): !!! FAILED BINDER TRANSACTION !!!
10-28 16:19:48.192 E/JavaBinder( 2458): !!! FAILED BINDER TRANSACTION !!!
10-28 16:19:57.152 E/imdg81 ( 2458): IsShutDownStarted()
10-28 16:19:57.281 E/imdg81 ( 2458): IsShutDownStarted()
10-28 16:20:00.430 E/StatusBarPolicy( 2458): Intent : android.intent.action.TIME_TICK
10-28 16:20:06.609 E/imdg81 ( 2458): IsShutDownStarted()
10-28 16:20:06.723 E/imdg81 ( 2458): IsShutDownStarted()
10-28 16:20:09.715 E/imdg81 ( 2458): IsShutDownStarted()
10-28 16:20:09.801 E/imdg81 ( 2458): IsShutDownStarted()
10-28 16:20:10.485 E/imdg81 ( 2458): IsShutDownStarted()
10-28 16:20:10.559 E/imdg81 ( 2458): IsShutDownStarted()
10-28 16:20:10.695 E/StatusBarPolicy( 2458): Intent : android.intent.action.BATTERY_CHANGED
Ray
i've had this issue on other android devices during frequent flashing.... usually corrupt data... wipe data and rebuild will fix it.
joshkoss said:
i've had this issue on other android devices during frequent flashing.... usually corrupt data... wipe data and rebuild will fix it.
Click to expand...
Click to collapse
You're right, wiping all the data and re-flashing does work...and then it happens again. The questions are, what causes the corrupt data? can it be fixed? and what can be done so that it does not get corrupted again? Without these questions answered we just run around the same circle. I've wiped and re-flashed six times now and each time it reverts to the process stop and now way to add new contacts. Editing contacts does work however.
Peace,
Ray
Reborn627 said:
You're right, wiping all the data and re-flashing does work...and then it happens again. The questions are, what causes the corrupt data? can it be fixed? and what can be done so that it does not get corrupted again? Without these questions answered we just run around the same circle. I've wiped and re-flashed six times now and each time it reverts to the process stop and now way to add new contacts. Editing contacts does work however.
Peace,
Ray
Click to expand...
Click to collapse
go start with stock rom then, odin reflash stock, then start the process flashing a custom rom. somthing happened, and i've had this before on other devices also.
joshkoss said:
go start with stock rom then, odin reflash stock, then start the process flashing a custom rom. somthing happened, and i've had this before on other devices also.
Click to expand...
Click to collapse
And don't forget to wipe before and after.
joshkoss said:
go start with stock rom then, odin reflash stock, then start the process flashing a custom rom. somthing happened, and i've had this before on other devices also.
Click to expand...
Click to collapse
Hey Josh, thanks for the suggestion. That is the process that I've used the last 2 times I started from scratch. I'll try it again this weekend. I could understand this happening if I was restoring backups but I've not restored in a couple of months.
Thanks again,
Ray
Reborn627 said:
Hey Josh, thanks for the suggestion. That is the process that I've used the last 2 times I started from scratch. I'll try it again this weekend. I could understand this happening if I was restoring backups but I've not restored in a couple of months.
Thanks again,
Ray
Click to expand...
Click to collapse
Hey, just poking my nose in the Continuum section as my wife still has hers.
With the data corruption issue (on your contacts), are you restoring them from either Verizon, or a backup? If so, more than likely there is a corrupt contact in the backup and that is probably what is hosing your contacts. Or, at least hosing the ADDING part of the contacts list.

Settings has stopped...

I'm unable to access my 'settings' menu. - Settings has stopped...
Many posts say a factory reset will not fix the issue so can someone point me in the direction on how to re-flash this phone before it gets given away or thrown in the trash...
Rooted, no new apps etc so not sure what broke it.
Pretty sure they only have images for the dev edition
fluffyofqweam said:
Pretty sure they only have images for the dev edition
Click to expand...
Click to collapse
There is an o2 image here
and some random one here which I can't ID.
At this point I don't really care what happens to this device now so if you can point me in a direction to a good guide I'll give one of those a go
Where did you find this image?
fluffyofqweam said:
Where did you find this image?
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/harpia/official/
Alright this let's try flashing the the first image you linked, do you have TWRP?
fluffyofqweam said:
Alright this let's try flashing the the first image you linked, do you have TWRP?
Click to expand...
Click to collapse
Yep that's all installed & working - I was actually going to try the newer image as the o2 one appears to be older than the image I have on the phone now... But I'm open to your wisdom.
As an aside - If I can get another identical phone could I pull the image out of that for re-installing on mine at a later date ? (I may be able to borrow a device next week for a few days) Otherwise I'm up for trying this today.
I was going to follow these instructions but only doing the;
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
part as it looks like it the OS thats broken rather than anything else. It would be nice If I didn't have to kill all my user data but I'm not that worried if I have no choice.
The phone works in fastboot and I have ADB working on my PC - I also now have mfastboot as I'd seen people hinting that Moto users should use that rather than just fastboot.
You found a newer one? I would flash the newer image as it maybe fixed the issue, not sure what you meant about the indentical phone part, if your asking if you can flash the Moto G4 play image on another device that's not a Moto G4 play the answer is no, and for the instructions you found, I have never seen it
---------- Post added at 05:45 PM ---------- Previous post was at 05:44 PM ----------
I'm actually a bit new to Android but I'm sure you can help others out to help you by posting your logcat after trying to get into the settings app
---------- Post added at 05:45 PM ---------- Previous post was at 05:45 PM ----------
And what ever you do do not throw this beast of a device away
fluffyofqweam said:
You found a newer one? I would flash the newer image as it maybe fixed the issue, not sure what you meant about the indentical phone part, if your asking if you can flash the Moto G4 play image on another device that's not a Moto G4 play the answer is no, and for the instructions you found, I have never seen it
---------- Post added at 05:45 PM ---------- Previous post was at 05:44 PM ----------
I'm actually a bit new to Android but I'm sure you can help others out to help you by posting your logcat after trying to get into the settings app
Click to expand...
Click to collapse
So the 2nd image link I posted here is slightly newer than the current phone version - I was going to try that as it appears to match in so fas as its a retail version rather than a carrier specific version (my devide was retail)
What I meant by extracting an image from another phone - I can get access to an identical non rooted stock retail image moto g4 play next week - so figured there must be a way to extract the system image then load it back onto this broken phone.
Re logcat - standby I'll edit this post in a few min once it's booted up & I've tested it. I was looking for logs but I'm even newer to this Android stuff than you are!
*** LOGCAT BELOW *** (from trying to access settings)
07-14 17:54:19.475 5162 11342 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android
.settings/.Settings (has extras)} from uid 10061 on display 0
07-14 17:54:19.480 7488 11394 D ProcSpeedReader: Failed to read freq stats from null
07-14 17:54:19.508 5162 7564 I ActivityManager: Start proc 12499:com.android.settings/1000 for activity com.android.settings/.Settings
07-14 17:54:19.553 7488 11394 D ProcSpeedReader: Failed to read freq stats from null
07-14 17:54:19.580 12499 12499 W System : ClassLoader referenced unknown path: /data/app/com.android.settings-1/lib/arm
07-14 17:54:19.583 12499 12499 D AndroidRuntime: Shutting down VM
07-14 17:54:19.589 12499 12499 E AndroidRuntime: FATAL EXCEPTION: main
07-14 17:54:19.589 12499 12499 E AndroidRuntime: Process: com.android.settings, PID: 12499
07-14 17:54:19.589 12499 12499 E AndroidRuntime: java.lang.RuntimeException: Unable to get provider android.support.v4.content.FileProvider: java.lang.ClassNotF
oundException: Didn't find class "android.support.v4.content.FileProvider" on path: DexPathList[[zip file "/system/framework/com.motorola.frameworks.core.addon.
jar", zip file "/data/app/com.android.settings-1/base.apk"],nativeLibraryDirectories=[/data/app/com.android.settings-1/lib/arm, /data/app/com.android.settings-1
/base.apk!/lib/armeabi-v7a, /vendor/lib, /system/lib]]
07-14 17:54:19.589 12499 12499 E AndroidRuntime: at android.app.ActivityThread.installProvider(ActivityThread.java:5193)
07-14 17:54:19.589 12499 12499 E AndroidRuntime: at android.app.ActivityThread.installContentProviders(ActivityThread.java:4785)
07-14 17:54:19.589 12499 12499 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4725)
07-14 17:54:19.589 12499 12499 E AndroidRuntime: at android.app.ActivityThread.-wrap1(ActivityThread.java)
07-14 17:54:19.589 12499 12499 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1418)
07-14 17:54:19.589 12499 12499 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
07-14 17:54:19.589 12499 12499 E AndroidRuntime: at android.os.Looper.loop(Looper.java:148)
07-14 17:54:19.589 12499 12499 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:5459)
07-14 17:54:19.589 12499 12499 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
07-14 17:54:19.589 12499 12499 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:728)
07-14 17:54:19.589 12499 12499 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
07-14 17:54:19.589 12499 12499 E AndroidRuntime: Caused by: java.lang.ClassNotFoundException: Didn't find class "android.support.v4.content.FileProvider" on pat
h: DexPathList[[zip file "/system/framework/com.motorola.frameworks.core.addon.jar", zip file "/data/app/com.android.settings-1/base.apk"],nativeLibraryDirector
ies=[/data/app/com.android.settings-1/lib/arm, /data/app/com.android.settings-1/base.apk!/lib/armeabi-v7a, /vendor/lib, /system/lib]]
07-14 17:54:19.589 12499 12499 E AndroidRuntime: at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:56)
07-14 17:54:19.589 12499 12499 E AndroidRuntime: at java.lang.ClassLoader.loadClass(ClassLoader.java:511)
07-14 17:54:19.589 12499 12499 E AndroidRuntime: at java.lang.ClassLoader.loadClass(ClassLoader.java:469)
07-14 17:54:19.589 12499 12499 E AndroidRuntime: at android.app.ActivityThread.installProvider(ActivityThread.java:5178)
07-14 17:54:19.589 12499 12499 E AndroidRuntime: ... 10 more
07-14 17:54:19.589 12499 12499 E AndroidRuntime: Suppressed: java.io.IOException: No original dex files found for dex location /data/app/com.android.sett
ings-1/base.apk
07-14 17:54:19.589 12499 12499 E AndroidRuntime: at dalvik.system.DexFile.openDexFileNative(Native Method)
07-14 17:54:19.589 12499 12499 E AndroidRuntime: at dalvik.system.DexFile.openDexFile(DexFile.java:295)
07-14 17:54:19.589 12499 12499 E AndroidRuntime: at dalvik.system.DexFile.<init>(DexFile.java:80)
07-14 17:54:19.589 12499 12499 E AndroidRuntime: at dalvik.system.DexFile.<init>(DexFile.java:59)
07-14 17:54:19.589 12499 12499 E AndroidRuntime: at dalvik.system.DexPathList.loadDexFile(DexPathList.java:279)
07-14 17:54:19.589 12499 12499 E AndroidRuntime: at dalvik.system.DexPathList.makePathElements(DexPathList.java:248)
07-14 17:54:19.589 12499 12499 E AndroidRuntime: at dalvik.system.DexPathList.<init>(DexPathList.java:120)
07-14 17:54:19.589 12499 12499 E AndroidRuntime: at dalvik.system.BaseDexClassLoader.<init>(BaseDexClassLoader.java:48)
07-14 17:54:19.589 12499 12499 E AndroidRuntime: at dalvik.system.PathClassLoader.<init>(PathClassLoader.java:65)
07-14 17:54:19.589 12499 12499 E AndroidRuntime: at android.app.ApplicationLoaders.getClassLoader(ApplicationLoaders.java:58)
07-14 17:54:19.589 12499 12499 E AndroidRuntime: at android.app.LoadedApk.getClassLoader(LoadedApk.java:376)
07-14 17:54:19.589 12499 12499 E AndroidRuntime: at android.app.LoadedApk.makeApplication(LoadedApk.java:568)
07-14 17:54:19.589 12499 12499 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4717)
07-14 17:54:19.589 12499 12499 E AndroidRuntime: ... 8 more
07-14 17:54:19.589 12499 12499 E AndroidRuntime: Suppressed: java.lang.ClassNotFoundException: android.support.v4.content.FileProvider
07-14 17:54:19.589 12499 12499 E AndroidRuntime: at java.lang.Class.classForName(Native Method)
07-14 17:54:19.589 12499 12499 E AndroidRuntime: at java.lang.BootClassLoader.findClass(ClassLoader.java:781)
07-14 17:54:19.589 12499 12499 E AndroidRuntime: at java.lang.BootClassLoader.loadClass(ClassLoader.java:841)
07-14 17:54:19.589 12499 12499 E AndroidRuntime: at java.lang.ClassLoader.loadClass(ClassLoader.java:504)
07-14 17:54:19.589 12499 12499 E AndroidRuntime: ... 12 more
07-14 17:54:19.589 12499 12499 E AndroidRuntime: Caused by: java.lang.NoClassDefFoundError: Class not found using the boot class loader; no stack trace a
vailable
07-14 17:54:19.591 5162 5176 W ActivityManager: Force finishing activity com.android.settings/.Settings
07-14 17:54:19.592 5162 5176 I ActivityManager: moveHomeStack, setupComplete:true
07-14 17:54:19.622 7488 11394 D ProcSpeedReader: Failed to read freq stats from null
07-14 17:54:19.682 5162 8999 I OpenGLRenderer: Initialized EGL, version 1.4
07-14 17:54:20.123 5162 5188 W ActivityManager: Activity pause timeout for ActivityRecord{103e8bb u0 com.android.settings/.Settings t9 f}
07-14 17:54:20.126 7488 11394 D ProcSpeedReader: Failed to read freq stats from null
07-14 17:54:20.170 5162 10520 I ActivityManager: Killing 12168:com.android.vending/u0a48 (adj 15): empty #7
07-14 17:54:20.209 5162 7985 D ActivityManager: cleanUpApplicationRecord -- 12168
07-14 17:54:20.761 358 717 I SFPerfTracer: triggers: (rate: 0:0) (0 sw vsyncs) (0 skipped) (26:2792 vsyncs) (28:3249)
07-14 17:54:21.333 12499 12499 I Process : Sending signal. PID: 12499 SIG: 9
07-14 17:54:21.338 5162 8999 D OpenGLRenderer: endAllActiveAnimators on 0xb94d8470 (RippleDrawable) with handle 0xb95eeb18
07-14 17:54:21.347 5162 10519 W InputMethodManagerService: Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Pr
[email protected] [email protected], token = [email protected]
07-14 17:54:21.372 5162 6956 I ActivityManager: Process com.android.settings (pid 12499) has died
07-14 17:54:21.372 5162 6956 D ActivityManager: cleanUpApplicationRecord -- 12499
Click to expand...
Click to collapse
Wait a minute, you got a Verizon version and rooted it? Werid, we yeah I would use the 2nd image if it was newer, and do you mean to get a whole other Moto G4 play just to get the image? I wouldn't really do that
---------- Post added at 05:53 PM ---------- Previous post was at 05:52 PM ----------
I would suggest the app called logcat reader, it's a simple app hold down to access a menu
---------- Post added at 05:55 PM ---------- Previous post was at 05:53 PM ----------
I know your settings is broken but please make a backup before you start flashing anything!
fluffyofqweam said:
Wait a minute, you got a Verizon version and rooted it? Werid, we yeah I would use the 2nd image if it was newer, and do you mean to get a whole other Moto G4 play just to get the image? I wouldn't really do that
---------- Post added at 05:53 PM ---------- Previous post was at 05:52 PM ----------
I would suggest the app called logcat reader, it's a simple app hold down to access a menu
---------- Post added at 05:55 PM ---------- Previous post was at 05:53 PM ----------
I know your settings is broken but please make a backup before you start flashing anything!
Click to expand...
Click to collapse
No, no - this is a UK Retail version XT1604. I have nothing to backup to be honest - and even if I end up on an old software/radio etc (o2 build) then fine - If you want me to backup from inside TWRP then I can, but I don't see much point backing up a recovery image I have, a system image which is clearly broken, cache which is empty anyway and a few user settings. I can decide that later.
Based on what you see do I just need to flash the system.image files in turn ? or do I need to flash all the other bits as well (Everything else on the phone works I should point out besides being able to access settings)
Alright, I understand it's your choice but there's a chance the situation might get even worse, luckily you have TWRP though, anyways i would think that flashing the second image you posted would already have everything, but before you do that checkout this video
It seems like he does a lot stuff not needed. But it's not going to hurt right?
---------- Post added at 06:26 PM ---------- Previous post was at 06:19 PM ----------
Copy and paste all the commands to the note pad, read the discription
---------- Post added at 06:43 PM ---------- Previous post was at 06:26 PM ----------
Any news?
Any news?
Click to expand...
Click to collapse
Only just sitting down to watch the vid - standby. It's also dinner-time
Yum! ?
Ok, so the video is the same instructions as here but rather than using mfastboot just regular fastboot.exe
I'm in the process of taking a full backup via TWRP right now.
I'll update this post shortly.
**1**
That's why I was planning on not touching the radio side of things... I'll consider a rom if none of this works - at the end of the day long as I can get into boot loader its fine.
My plan is to flash everything except the radio stuff, and the recovery image
Gotcha! Perhaps follow the article, people do say that some things like there data or wifi signal doesn't work while other people say it works perfectly, I wish the best of luck, also if this does fail, maybe consider a rom?
Before I commit to this; does anyone know the difference between the MIP and the MIPS firmwares ? Is 1 for the dual SIM version? If so which one as this is only a single SIM
Er, not sure, sorry I didn't respond, xda labs didn't send me a notification
Any news?
fluffyofqweam said:
Any news?
Click to expand...
Click to collapse
Yes! - Sorry was out. We are back in business.
I ended up doing a full re-flash using this image and these instructions as a guide. But rather than mfastboot - use just fastboot and inside the .zip you will find a file called flashfile.xml - open that file in a browser and it will show you all the steps that firmware requires and bits to do. Use the website as a guide only.
The software installed;
6.0.1
Patch 01-May-2017
Modem Version: M8916_20250106.08.05.23.01R
System Version: 24.221.18.harpia.retail.en.US
Blur Version: Blur_Version.24.221.18.harpia.retail.en.US
Version when read from CPV: harpia-user 6.0.1 MPIS24.241-2.35-2-17 18 release-keys
Kernel 3.10.49 22-May-2017
Managed to re-encrypt then root the device, I'll sort out basic apps & bits later so I can build a base config to backup through TWRP. Once I've done that I'll start stripping out some of the junk (knowing I have a working backup)
It would appear for the time being the device is safe from any nasty incidents or the bin... I'm also a bit more happy about flashing the device now as well.

(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!

Camera FC in Android 9 PIE Roms

I have been facing Camera Fc's in almost all PIE Roms randomly after a reboot.
It happens randomly after rebooting the phone. In some ROMs it happens after two or three reboots, I am attaching the link of the log file
time: 1551073148867
msg: java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
stacktrace: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.camera2/com.android.camera.CameraActivity}: java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2953)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3088)
at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:78)
at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:108)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:68)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1818)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:193)
at android.app.ActivityThread.main(ActivityThread.java:6739)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:495)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:859)
Caused by: java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
at com.android.ex.camera2.portability.AndroidCameraAgentImpl$AndroidCameraDeviceInfo.getCharacteristics(AndroidCameraAgentImpl.java:176)
at com.android.camera.app.CameraController.getCharacteristics(CameraController.java:112)
at com.android.camera.CaptureModule.getFacingFromCameraId(CaptureModule.java:1542)
at com.android.camera.CaptureModule.init(CaptureModule.java:415)
at com.android.camera.CameraActivity.onCreateTasks(CameraActivity.java:1627)
at com.android.camera.util.QuickActivity.onCreate(QuickActivity.java:114)
at android.app.Activity.performCreate(Activity.java:7145)
at android.app.Activity.performCreate(Activity.java:7136)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1272)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2933)
... 11 more
I am new and therefore could not post url here.
Kindly look into this issue
ZABCXYZ said:
I have been facing Camera Fc's in almost all PIE Roms randomly after a reboot.
It happens randomly after rebooting the phone. In some ROMs it happens after two or three reboots, I am attaching the link of the log file
time: 1551073148867
msg: java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
stacktrace: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.camera2/com.android.camera.CameraActivity}: java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2953)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3088)
at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:78)
at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:108)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:68)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1818)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:193)
at android.app.ActivityThread.main(ActivityThread.java:6739)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:495)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:859)
Caused by: java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
at com.android.ex.camera2.portability.AndroidCameraAgentImpl$AndroidCameraDeviceInfo.getCharacteristics(AndroidCameraAgentImpl.java:176)
at com.android.camera.app.CameraController.getCharacteristics(CameraController.java:112)
at com.android.camera.CaptureModule.getFacingFromCameraId(CaptureModule.java:1542)
at com.android.camera.CaptureModule.init(CaptureModule.java:415)
at com.android.camera.CameraActivity.onCreateTasks(CameraActivity.java:1627)
at com.android.camera.util.QuickActivity.onCreate(QuickActivity.java:114)
at android.app.Activity.performCreate(Activity.java:7145)
at android.app.Activity.performCreate(Activity.java:7136)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1272)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2933)
... 11 more
I am new and therefore could not post url here.
Kindly look into this issue
Click to expand...
Click to collapse
U partitions are encrypted . Do format data. Then camera will work.
Format data command decrypts and erases the data and internal sd partition.
Go to twrp
Format data
Type Yes to format.
Reboot

Mi 9T MIUI Global 10.3.7 - Stock Clock & Weather apps is not working

Hi,
Mi 9T MIUI Global 10.3.7 - Stock Clock & Weather apps is not working....
I did a hard reset, but didn't working
Code:
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.miui.weather2/com.miui.weather2.ActivityWeatherMain}: java.lang.IndexOutOfBoundsException: setSpan (-1 ... 21) starts before 0
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2984)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3119)
at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:78)
at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:108)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:68)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1839)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:201)
at android.app.ActivityThread.main(ActivityThread.java:6864)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:547)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:873)
Caused by: java.lang.IndexOutOfBoundsException: setSpan (-1 ... 21) starts before 0
at android.text.SpannableStringBuilder.checkRange(SpannableStringBuilder.java:1326)
at android.text.SpannableStringBuilder.setSpan(SpannableStringBuilder.java:682)
at android.text.SpannableStringBuilder.setSpan(SpannableStringBuilder.java:674)
at com.miui.weather2.util.UserNoticeUtil.getUserNoticeMessage(UserNoticeUtil.java:202)
at com.miui.weather2.util.UserNoticeUtil.showUserNoticeDialog(UserNoticeUtil.java:79)
at com.miui.weather2.ActivityWeatherMain.showUserNoticeDialog(ActivityWeatherMain.java:1552)
at com.miui.weather2.ActivityWeatherMain.initView(ActivityWeatherMain.java:195)
at com.miui.weather2.mvp.common.BaseMvpActivity.init(BaseMvpActivity.java:35)
at com.miui.weather2.mvp.common.BaseMvpActivity.onCreate(BaseMvpActivity.java:21)
at com.miui.weather2.ActivityWeatherMain.onCreate(ActivityWeatherMain.java:166)
at android.app.Activity.performCreate(Activity.java:7232)
at android.app.Activity.performCreate(Activity.java:7221)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1272)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2964)
... 11 more
Code:
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.deskclock/com.android.deskclock.DeskClockTabActivity}: java.lang.IndexOutOfBoundsException: setSpan (-1 ... 22) starts before 0
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2984)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3119)
at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:78)
at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:108)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:68)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1839)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:201)
at android.app.ActivityThread.main(ActivityThread.java:6864)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:547)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:873)
Caused by: java.lang.IndexOutOfBoundsException: setSpan (-1 ... 22) starts before 0
at android.text.SpannableStringBuilder.checkRange(SpannableStringBuilder.java:1326)
at android.text.SpannableStringBuilder.setSpan(SpannableStringBuilder.java:682)
at android.text.SpannableStringBuilder.setSpan(SpannableStringBuilder.java:674)
at com.android.deskclock.util.UserNoticeUtil.getUserNoticeMessage(UserNoticeUtil.java:105)
at com.android.deskclock.util.UserNoticeUtil.showUserNoticeDialog(UserNoticeUtil.java:144)
at com.android.deskclock.DeskClockTabActivity.onCreate(DeskClockTabActivity.java:166)
at android.app.Activity.performCreate(Activity.java:7232)
at android.app.Activity.performCreate(Activity.java:7221)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1272)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2964)
... 11 more
I downloaded from apkmirror the newest versions of clock and weather, and now works fine....

Categories

Resources