The GPS is not starting up, tried everything. Flashing new GPS configuration, Cleaning GPS data with angry GPS, Booting, reebooting.
i9000 running CM7 7.1.0 Stable
It started after following this Post
http://forum.xda-developers.com/showthread.php?t=1182735
-GPS Antenna is on
-The gps notification used to blink while trying to fix a position, now it doesn't even show up.
Please Help
Part of a alogcat file where the same error keeps repeating itself while the antenna is on.
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
Can anyone give me a hint please?
biomanuel666 said:
The GPS is not starting up, tried everything. Flashing new GPS configuration, Cleaning GPS data with angry GPS, Booting, reebooting.
i9000 running CM7 7.1.0 Stable
It started after following this Post
http://forum.xda-developers.com/showthread.php?t=1182735
-GPS Antenna is on
-The gps notification used to blink while trying to fix a position, now it doesn't even show up.
Please Help
Part of a alogcat file where the same error keeps repeating itself while the antenna is on.
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
Click to expand...
Click to collapse
Please help me out with this!
GPS no longer working
You have a GT-I9000, yet you have sought the answer to your problem on a Vibrant thread. Did you, by any chance, install CM7 for the Vibrant onto your GT-I9000, find a problem with the GPS, and look for the answer within the Vibrant thread?
If you could supply a little more background information, then this would be helpful.
Hi all !
Here's my guide to read logcat. The post will be updated regularly when needed.
1.) How to logcat
Assuming you already have adb :
Code:
adb logcat
To logcat and save logcat to a file :
Code:
adb logcat>file_name.txt
2.) How to read it ?
Reading logcat is easy, easier than creating a flashable stock ROM. On logcat, you'll encounter following messages :
I/ : Information about what process is doing.
W/ : Warning, mostly displays something wrong, but not as fatal as E/ .
D/ : Debugging, same as I/ but can be crucial or fatal.
E/ : Error, crucial system error. Can be a cause of a problem.
V/ : Verbose-able / output. Mostly common message like I/ or D/ .
Example of the messages :
Code:
I/dalvikvm : Means dalvik-vm is showing an information
W/vold : Means on vold process, something is wrong.
D/dalvikvm : Means dalvik-vm is doing a debug-able actions.
E/dalvikvm : Means a fatal dalvik-vm or dalvik-vm crashed.
V/java : Java is doing something
While reading logcat, you must use your common sense. I/ sometimes can be a fatal error, so you must read it carefully.
3.) Fatal system errors
Another advantages of logcat if you're a ROM themer / porter is you can read where's system error is located.
The most common system errors are :
Code:
E/dalvikvm : The common cause of a bootloop
E/JNIHelp : Another common cause of bootloop
F/libc : Mostly SIGSEGV error, cause bootloop
Examples of errors :
Code:
E/dalvikvm( 908): ERROR: couldn't find native method : Means dalvikvm couldn't find correct method for following actions.
E/JNIHelp ( 908): RegisterNatives failed for 'android/net/wifi/WifiNative', aborting : Means JNIHelp can't register native method
F/libc ( 908): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 908 (zygote) : Caused by E/JNIHelp
Guide will be updated soon when I find something interesting.
Great thread bro,here so many peeps they need to understand it,thumps up.
GREEEETZ FROM TEAM-OPTIMA!!!
The other day, my phone rebooted itself, disabling/uninstalling xposed framework in the process. Reflashed, and it still didn't work. Today I clean flashed my ROM, and it still isn't working. Nexus 6 using Benzo ROM. Used the latest official SDK22 xposed. In the app, it says the framework is installed not enabled. I ticked the unlock bootloader in dev options just in case, and i tried the uninstaller as well. Root works just fine. Can't think of any other solutions. My log is below
09-05 16:52:18.586 I/Xposed ( 428): -----------------
09-05 16:52:18.587 I/Xposed ( 428): Starting Xposed version 73, compiled for SDK 22
09-05 16:52:18.587 I/Xposed ( 428): Device: Nexus 6 (motorola), Android version 5.1.1 (SDK 22)
09-05 16:52:18.587 I/Xposed ( 428): ROM: LVY48E
09-05 16:52:18.587 I/Xposed ( 428): Build fingerprint: google/shamu/shamu:5.1.1/LVY48E/2116406:user/release-keys
09-05 16:52:18.587 I/Xposed ( 428): Platform: armeabi-v7a, 32-bit binary, system server: yes
09-05 16:52:18.587 I/Xposed ( 428): SELinux enabled: yes, enforcing: no
09-05 16:52:21.756 E/Xposed ( 428): Found /data/data/de.robv.android.xposed.installer/conf/disabled, not loading Xposed
09-05 16:52:22.102 I/Xposed ( 428): Forcing image recompilation because /data/dalvik-cache/arm/[email protected]@boot.art is not compiled for the current Xposed version
09-05 16:53:27.537 F/libc ( 377): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 388 (BootAnimation)
09-05 16:53:27.588 E/DEBUG ( 414): unexpected waitpid response: n=388, status=00000000
09-05 16:53:27.588 E/DEBUG ( 414): tid exited before attach completed: tid 388
ezMesican said:
The other day, my phone rebooted itself, disabling/uninstalling xposed framework in the process. Reflashed, and it still didn't work. Today I clean flashed my ROM, and it still isn't working. Nexus 6 using Benzo ROM. Used the latest official SDK22 xposed. In the app, it says the framework is installed not enabled. I ticked the unlock bootloader in dev options just in case, and i tried the uninstaller as well. Root works just fine. Can't think of any other solutions. My log is below
09-05 16:52:18.586 I/Xposed ( 428): -----------------
09-05 16:52:18.587 I/Xposed ( 428): Starting Xposed version 73, compiled for SDK 22
09-05 16:52:18.587 I/Xposed ( 428): Device: Nexus 6 (motorola), Android version 5.1.1 (SDK 22)
09-05 16:52:18.587 I/Xposed ( 428): ROM: LVY48E
09-05 16:52:18.587 I/Xposed ( 428): Build fingerprint: google/shamu/shamu:5.1.1/LVY48E/2116406:user/release-keys
09-05 16:52:18.587 I/Xposed ( 428): Platform: armeabi-v7a, 32-bit binary, system server: yes
09-05 16:52:18.587 I/Xposed ( 428): SELinux enabled: yes, enforcing: no
09-05 16:52:21.756 E/Xposed ( 428): Found /data/data/de.robv.android.xposed.installer/conf/disabled, not loading Xposed
09-05 16:52:22.102 I/Xposed ( 428): Forcing image recompilation because /data/dalvik-cache/arm/[email protected]@boot.art is not compiled for the current Xposed version
09-05 16:53:27.537 F/libc ( 377): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 388 (BootAnimation)
09-05 16:53:27.588 E/DEBUG ( 414): unexpected waitpid response: n=388, status=00000000
09-05 16:53:27.588 E/DEBUG ( 414): tid exited before attach completed: tid 388
Click to expand...
Click to collapse
You should have a look at the unofficial Q&A in post #2 of this thread. The solution for your issue is described there. I have highlighted the corresponding line in your Xposed log.
My son's Moto X with unofficial Lineage OS 13 has been working just fine until today, when it suddenly stopped finding any network operators. The SIM card is still recognized, I may enter the pin, but then it says "No service", and when I go to network operators choice, I find that not a single operator is displayed.
I tested the SIM in another phone, it seems to be fine. I also inserted different sim, which I know to work into this phone, but that did not help.
This is what I get from adb logcat, but I can't make sense of it:
XXXXXXXXXXX simSlotIndex=0 displayName=Willkommen carrierName=No service nameSource=0 iconTint=-16746133 dataRoaming=0 [email protected] mcc 26
2 mnc 7 mUserNwMode=9}]
01-07 18:11:59.254 1572 1572 D NetworkSettings: onSubscriptionsChanged: Slot matched SimSlotIndex: 0
01-07 18:11:59.257 1833 1833 D KP2AAF : OnAccEvent
01-07 18:11:59.306 1833 1833 D KP2AAF : OnAccEvent
01-07 18:11:59.306 1572 3902 D OpenGLRenderer: endAllStagingAnimators on 0x99f02e00 (RippleDrawable) with handle 0x9d070520
01-07 18:11:59.361 1833 1833 D KP2AAF : OnAccEvent
01-07 18:11:59.361 1833 1833 D KP2AAF : event: 32, package = com.android.phone
01-07 18:11:59.361 1833 1833 D KP2AAF : event package is no launcher
01-07 18:11:59.367 1833 1833 D KP2AAF : root package is no launcher
01-07 18:11:59.367 1833 1833 D KP2AAF : URL=androidapp://com.android.phone
01-07 18:11:59.368 1833 1833 D KP2AAF : Cancel notif
01-07 18:11:59.438 1881 6159 I GeofencerStateMachine: removeGeofences: removeRequest=RemoveGeofencingRequest[REMOVE_BY_IDS Ids=[atn_geofence_request_id], packageName=
com.google.android.apps.maps]
01-07 18:11:59.458 1881 1903 I GeofencerStateMachine: removeGeofences: removeRequest=RemoveGeofencingRequest[REMOVE_BY_IDS Ids=[atn_geofence_request_id], packageName=
com.google.android.apps.maps]
01-07 18:11:59.575 1572 1572 D NetworkQuery: unregistering callback class com.android.phone.NetworkSetting$3
01-07 18:11:59.579 1572 1572 I art : Starting a blocking GC Explicit
01-07 18:11:59.634 1572 1572 I art : Explicit concurrent mark sweep GC freed 29733(3MB) AllocSpace objects, 7(156KB) LOS objects, 40% free, 10MB/17MB, paused 610u
s total 41.233ms
01-07 18:11:59.656 1572 1572 I art : Starting a blocking GC Explicit
01-07 18:11:59.676 1572 1572 I art : Explicit concurrent mark sweep GC freed 13973(846KB) AllocSpace objects, 2(80KB) LOS objects, 39% free, 9MB/15MB, paused 640u
s total 19.563ms
01-07 18:11:59.676 1572 1572 I art : Starting a blocking GC Explicit
01-07 18:11:59.691 1881 1901 I GeofencerStateMachine: removeGeofences: removeRequest=RemoveGeofencingRequest[REMOVE_BY_IDS Ids=[atn_geofence_request_id], packageName=
com.google.android.apps.maps]
01-07 18:11:59.695 1572 1572 I art : Explicit concurrent mark sweep GC freed 3(96B) AllocSpace objects, 0(0B) LOS objects, 40% free, 9MB/15MB, paused 579us total
19.136ms
01-07 18:12:00.121 21030 21030 W ps : type=1400 audit(0.0:1428831): avc: denied { getattr } for path="/proc/1" dev="proc" ino=3578 scontext=u:r:untrusted_app:s0:c5
12,c768 tcontext=u:r:init:s0 tclass=dir permissive=0
01-07 18:12:00.145 1833 1833 D KP2AAF : OnAccEvent
01-07 18:12:00.145 1833 1833 D KP2AAF : event: 2048, package = com.android.systemui
01-07 18:12:00.145 1833 1833 D KP2AAF : return.
Could it be that suddenly the hardware has become faulty? Does anybody have suggestions how to test for the cause?
Thanks very much in advance!!!
Did a factory reset, which did not solve it. Still no network operators found.
Trying to understand the problem. logcat reveals that when it scans for networks, something goes wrong:
IsDataRoamingFromRegistration=false] newSS=[1 1 voice home data home null null null null null null Unknown Unknown CSS not supported -1 -1 RoamInd=-1 DefRoamInd=-1 EmergOnly=false IsDataRoamingFromRegistration=false] oldMaxDataCalls=20 mNewMaxDataCalls=20 oldReasonDataDenied=-1
Can someone enlighten me, what CSS stands for?
Now I spotted more errors:
01-10 15:54:50.960 2132 2132 D DCT : [0]stopNetStatPoll
01-10 15:54:50.964 2132 2132 D DCT : [0]overall state is IDLE
01-10 15:59:14.763 2132 2795 D RILJ : [4000]> RIL_REQUEST_GET_CELL_INFO_LIST [SUB0]
01-10 15:59:14.770 217 7538 W use-Rlog/RLOG-RILQ: (0/217):RIL[0][cmd-109(912)] qmi_ril_qmi_req_log: req QMI NAS, msg id: 67, e len:0
01-10 15:59:14.804 217 7538 W use-Rlog/RLOG-RILQ: (0/217):RIL[0][cmd-109(912)] qmi_ril_qmi_resp_log: rsp - QMI NAS, msg id: 67, e len:7
01-10 15:59:14.804 2132 2243 D RilRequest: [4000]< RIL_REQUEST_GET_CELL_INFO_LIST error: com.android.internal.telephony.CommandException: GENERIC_FAILURE ret=
01-10 15:59:14.804 2132 2132 D GsmSST : [GsmSST] EVENT_GET_CELL_INFO_LIST: error ret null, e=com.android.internal.telephony.CommandException: GENERIC_FAILURE
01-10 15:59:14.804 2132 2795 D GsmSST : [GsmSST] SST.getAllCellInfo(): X size=0 list=null
01-10 15:59:14.805 2132 2795 D GsmSST : [GsmSST] getCellLocation(): X empty mCellLoc and CellInfo mCellLoc=[-1,-1,-1]
01-10 15:59:14.817 1929 3007 D TelephonyManager: getCellLocation returning null because CellLocation is empty
01-10 15:59:14.820 2132 20809 D GsmSST : [GsmSST] SST.getAllCellInfo(): return last, back to back calls
01-10 15:59:14.820 2132 20809 D GsmSST : [GsmSST] SST.getAllCellInfo(): X size=0 list=null
This "Generic failure" sounds spooky to me. As if something about the hardware is broken.
yahya69 said:
Did a factory reset, which did not solve it. Still no network operators found.
Click to expand...
Click to collapse
Have you tried restoring to the stock firmware? If not, try the following commands in fastboot mode first:
Code:
fastboot erase modemst1
fastboot erase modemst2
Additionally, in the Phone app, you may dial *#*#INFO#*#* (*#*#4636#*#*) to obtain more information about the device's network.
VitaTaf said:
Have you tried restoring to the stock firmware?
Click to expand...
Click to collapse
Yes, but that also did not help, so I returned to LineageOS again.
If not, try the following commands in fastboot mode first:
Code:
fastboot erase modemst1
fastboot erase modemst2
Click to expand...
Click to collapse
I am not clear what that does. Seemingly, it erases two partitions. Is their content rebuilt after? Are those two partitions shipped with the custom rom? I did several google searches and each time I found it accompanied by the instruction to flash something else in the next step. So before nuking a partition I certainly would want to know., but so far I have not found an explanation of the partition layout.
Additionally, in the Phone app, you may dial *#*#INFO#*#* (*#*#4636#*#*) to obtain more information about the device's network.
Click to expand...
Click to collapse
I know. There it says it has no cellular network. As the logs I posted indicate, something goes badly wrong while searching for cells.
Tried it now, after a backup, but it did not change the situation. The sim card is recognized, but "no service" remains.
yahya69 said:
Tried it now, after a backup, but it did not change the situation. The sim card is recognized, but "no service" remains.
Click to expand...
Click to collapse
The fastboot commands clear the modem cache, and the cache regenerates on boot up.
Unfortunately, it looks like your issue is hardware-related. Which method did you use to restore to the stock firmware?
VitaTaf said:
The fastboot commands clear the modem cache, and the cache regenerates on boot up.
Unfortunately, it looks like your issue is hardware-related.
Click to expand...
Click to collapse
Which really would be a first time for me. I never saw the GSM module of a phone suddenly fail. My son insists that nothing had happened..
Yesterday, after reflashing the stock firmware yet again, I shortly got a very weak signal, and then, after I went to manual operator selection, it immediately went away again and stubbornly remained absent since.
VitaTaf said:
Which method did you use to restore to the stock firmware?
Click to expand...
Click to collapse
TWRP (adb sideload). I am not sure whether the image is flashable via fastboot.
yahya69 said:
Which really would be a first time for me. I never saw the GSM module of a phone suddenly fail. My son insists that nothing had happened..
Yesterday, after reflashing the stock firmware yet again, I shortly got a very weak signal, and then, after I went to manual operator selection, it immediately went away again and stubbornly remained absent since.
TWRP (adb sideload). I am not sure whether the image is flashable via fastboot.
Click to expand...
Click to collapse
As a last resort, I would suggest locating the full stock firmware for your device and follow the included instructions (if any) to flash it via fastboot, or at the very least, flash the fsg.mbn and NON-HLOS.bin for your device as listed under Modem Firmware in this thread. Instructions for flashing are included in the downloaded archive.
VitaTaf said:
As a last resort, I would suggest locating the full stock firmware for your device and follow the included instructions (if any) to flash it via fastboot, or at the very least, flash the fsg.mbn and NON-HLOS.bin for your device as listed under Modem Firmware in this thread. Instructions for flashing are included in the downloaded archive.
Click to expand...
Click to collapse
I reflashed them but as a result, the sim card is no longer recognized, rebooted several times.
Update: Reflashed lineageOS and now I got my sim card back, although still not connecting to the network. Reflashed the stock firmware with twrp (not sure how this would be done via fastboot), I got my phone to re-connect to the network for a few seconds, which made me jump up and down in excitement, but then the connection dropped again, before I could even make a phonecall
Update 2 Tried a different sim card, but again, when I try to register automatically, this is what I see:
}
D/PHONE (15915): [ServiceState] setDataRegState=1
D/PHONE (15915): [ServiceState] setDataRadioTechnology=0
D/GsmSST (15915): [GsmSST] 0handlPollStateResultMessage: GsmSST setDataRegState=1 regState=0 dataRadioTechnology=0
D/PHONE (15915): [ServiceState] setVoiceRegState=1
E/PHONE (15915): [ServiceState] setState deprecated use setVoiceRegState()
D/GsmSST (15915): [GsmSST] 0handleSIB5LackIssue: no cell location change and config is 'on'
D/GsmSST (15915): [GsmSST] 0Poll ServiceState done: oldSS=[1 1 voice home data home null null null null null null Unknown Unknown CSS not supported -1 -1 RoamInd=-1 DefRoamInd=-1 EmergOnly=false] newSS=[1 1 voice home data home null null null null null null Unknown Unknown CSS not supported -1 -1 RoamInd=-1 DefRoamInd=-1 EmergOnly=false] oldMaxDataCalls=20 mNewMaxDataCalls=20 oldReasonDataDenied=-1 realOldType=Unknown realNewType=Unknown mNewReasonDataDenied=-1
D/PHONE (15915): [ServiceState] setNullState=1
Needless to say it fails.
Hello,
Has someone installed Xposed on his NX609J?
I have installed it but somehow it doesn't work. I get following Error in my log:
HTML:
ERROR: Could not access Xposed jar '/system/framework/XposedBridge.jar'
Full log:
HTML:
03-30 18:08:07.326 I/Xposed ( 1188): -----------------
03-30 18:08:07.326 I/Xposed ( 1188): Starting Xposed version 90-beta3, compiled for SDK 27
03-30 18:08:07.326 I/Xposed ( 1188): Device: NX609J (nubia), Android version 8.1.0 (SDK 27)
03-30 18:08:07.326 I/Xposed ( 1188): ROM: NX609J_ENCommon_V1.12
03-30 18:08:07.326 I/Xposed ( 1188): Build fingerprint: nubia/NX609J/NX609J:8.1.0/OPM1.171019.011/eng.nubia.20180907.173257:user/release-keys
03-30 18:08:07.326 I/Xposed ( 1188): Platform: arm64-v8a, 64-bit binary, system server: yes
03-30 18:08:07.326 I/Xposed ( 1188): SELinux enabled: yes, enforcing: yes
03-30 18:08:07.349 I/Xposed ( 1188): -----------------
03-30 18:08:07.349 E/Xposed ( 1188): ERROR: Could not access Xposed jar '/system/framework/XposedBridge.jar'
03-30 18:08:17.391 I/Xposed ( 1189): -----------------
03-30 18:08:17.391 I/Xposed ( 1189): Starting Xposed version 90-beta3, compiled for SDK 27
03-30 18:08:17.391 I/Xposed ( 1189): Device: NX609J (nubia), Android version 8.1.0 (SDK 27)
03-30 18:08:17.391 I/Xposed ( 1189): ROM: NX609J_ENCommon_V1.12
03-30 18:08:17.391 I/Xposed ( 1189): Build fingerprint: nubia/NX609J/NX609J:8.1.0/OPM1.171019.011/eng.nubia.20180907.173257:user/release-keys
03-30 18:08:17.391 I/Xposed ( 1189): Platform: arm64-v8a, 32-bit binary, system server: no
03-30 18:08:17.391 I/Xposed ( 1189): SELinux enabled: yes, enforcing: yes
03-30 18:08:17.392 I/Xposed ( 1189): -----------------
03-30 18:08:17.392 E/Xposed ( 1189): ERROR: Could not access Xposed jar '/system/framework/XposedBridge.jar'
03-30 18:08:20.550 W/Xposed ( 2133): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected]@[email protected]@xposed' : No such file or directory
03-30 18:08:20.555 W/Xposed ( 2114): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected]@[email protected]@xposed' : No such file or directory
03-30 18:08:20.558 W/Xposed ( 2105): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected]@[email protected]@xposed' : No such file or directory
03-30 18:08:20.778 W/Xposed ( 2214): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected]@[email protected]@xposed' : No such file or directory
03-30 18:08:20.784 W/Xposed ( 2231): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected]@[email protected]@xposed' : No such file or directory
03-30 18:08:20.803 W/Xposed ( 2238): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected]@[email protected]@xposed' : No such file or directory
03-30 18:08:20.833 W/Xposed ( 2282): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected]@[email protected]@xposed' : No such file or directory
03-30 18:08:20.839 W/Xposed ( 2238): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected]@[email protected]@xposed' : No such file or directory
03-30 18:08:21.065 W/Xposed ( 2383): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected]@[email protected]@xposed' : No such file or directory
03-30 18:08:21.500 W/Xposed ( 2238): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected]@[email protected]@xposed' : No such file or directory
03-30 18:08:22.234 W/Xposed ( 2674): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected]@[email protected]@xposed' : No such file or directory
03-30 18:08:21.448 W/Xposed ( 2760): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected][email protected]@[email protected]' : No such file or directory
03-30 18:08:22.880 W/Xposed ( 2949): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected]@[email protected]@xposed' : No such file or directory
03-30 18:08:22.938 W/Xposed ( 2972): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected]@[email protected]@xposed' : No such file or directory
03-30 18:08:22.967 W/Xposed ( 2997): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected]@[email protected]@xposed' : No such file or directory
03-30 18:08:23.003 W/Xposed ( 3012): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected]@[email protected]@xposed' : No such file or directory
03-30 18:08:23.146 W/Xposed ( 1785): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected]@[email protected]@xposed' : No such file or directory
03-30 18:08:23.282 W/Xposed ( 3142): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected][email protected]: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected][email protected][email protected]@xposed' : No such file or directory
03-30 18:08:23.307 W/Xposed ( 2214): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected]@[email protected]@xposed' : No such file or directory
03-30 18:08:23.543 W/Xposed ( 3209): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected]@[email protected]@xposed' : No such file or directory
03-30 18:08:23.745 W/Xposed ( 3297): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected]@[email protected]@xposed' : No such file or directory
03-30 18:08:24.048 W/Xposed ( 3362): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected]@[email protected]@xposed' : No such file or directory
03-30 18:08:24.069 W/Xposed ( 3362): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected]@[email protected]@xposed' : No such file or directory
03-30 18:08:26.616 W/Xposed ( 3862): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected]@[email protected]@xposed' : No such file or directory
03-30 18:08:26.627 W/Xposed ( 3862): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected][email protected]@[email protected]' : No such file or directory
03-30 18:08:26.732 W/Xposed ( 3933): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected]@[email protected]@xposed' : No such file or directory
03-30 18:08:27.440 W/Xposed ( 4149): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected]@[email protected]@xposed' : No such file or directory
03-30 18:08:27.527 W/Xposed ( 4172): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected]@[email protected]@xposed' : No such file or directory
03-30 18:08:27.615 W/Xposed ( 4193): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected]@[email protected]@xposed' : No such file or directory
03-30 18:08:27.984 W/Xposed ( 4259): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected]@[email protected]@xposed' : No such file or directory
03-30 18:08:28.199 W/Xposed ( 4294): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected]@[email protected]@xposed' : No such file or directory
03-30 18:08:28.635 W/Xposed ( 2238): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected]@[email protected]@xposed' : No such file or directory
03-30 18:08:28.828 W/Xposed ( 1785): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected]@[email protected]@xposed' : No such file or directory
03-30 18:08:38.708 W/Xposed ( 2238): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected]@[email protected]@xposed' : No such file or directory
03-30 18:08:38.783 W/Xposed ( 5566): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected][email protected]: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected][email protected][email protected]@xposed' : No such file or directory
03-30 18:08:38.858 W/Xposed ( 5581): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected]@[email protected]@xposed' : No such file or directory
03-30 18:08:39.027 W/Xposed ( 5618): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected]@[email protected]@xposed' : No such file or directory
03-30 18:08:40.162 W/Xposed ( 5768): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected]@[email protected]@xposed' : No such file or directory
03-30 18:08:40.346 W/Xposed ( 5768): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected]@[email protected]@xposed' : No such file or directory
03-30 18:08:40.374 W/Xposed ( 5618): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected]@[email protected]@xposed' : No such file or directory
03-30 18:09:00.930 W/Xposed ( 5989): Failed to load Xposed info for /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex: Unable to open '/data/dalvik-cache/arm64/[email protected]@[email protected]@[email protected]@[email protected]@xposed' : No such file or directory
I tried all the fixes i found on xda. But none of them worked. Can someone help me?
On the international firmware, I believe the Xposed framework is unsupported.
You might have better luck with using Magisk though, I'm sure Magisk is also unsupported on the international firmware.
Due to the international firmware locking certain partitions such as system and data, I believe you won't be able to install Xposed.
The firmware forces encryption which causes the partitions to be locked completely.
Do I understand you right: If I install the Chinese Frimware Xposed will work?
Florian Bichl said:
Do I understand you right: If I install the Chinese Frimware Xposed will work?
Click to expand...
Click to collapse
Well I guess you need root for using x-posed and that requires you to stay on Oreo.
Florian Bichl said:
Do I understand you right: If I install the Chinese Frimware Xposed will work?
Click to expand...
Click to collapse
I think now in pie already can be rooted! no need to stay on oreo again.