Hi, Im getting an "Unfortunately Settings Has Stopped" error at boot of this rom, does anyone know a fix for this ?
mdcool26 said:
Hi, Im getting an "Unfortunately Settings Has Stopped" error at boot of this rom, does anyone know a fix for this ?
Click to expand...
Click to collapse
Post a logcat.
If you don't know how, then you can run the tool in my signature and use the command lgctnp
Then post the generated text file as an attachment here.
missis roo
Lgrootnoob said:
Post a logcat.
If you don't know how, then you can run the tool in my signature and use the command lgctnp
Then post the generated text file as an attachment here.
Click to expand...
Click to collapse
I've never done a logcat before. But I have adb installed with phone connected through usb. typed in "adb logcat -v long > Settings has stopped.txt" with message saying "- waiting for device -" then nothing happens when booting phone ?
mdcool26 said:
I've never done a logcat before. But I have adb installed with phone connected through usb. typed in "adb logcat -v long > Settings has stopped.txt" with message saying "- waiting for device -" then nothing happens when booting phone ?
Click to expand...
Click to collapse
Sorry, you will need the drivers for your device and you will have to have usb debugging on.(> the reasons for the waiting for device)
If you don't have debugging on then we must find a recovery with adbd running.
Then use my tool's command lgctnp
then exit notepad.
post the text file from the Work folder here in an attachment.
Then we can move along.
Lgrootnoob said:
Sorry, you will need the drivers for your device and you will have to have usb debugging on.(> the reasons for the waiting for device)
If you don't have debugging on then we must find a recovery with adbd running.
Then use my tool's command lgctnp
then exit notepad.
post the text file from the Work folder here in an attachment.
Then we can move along.
Click to expand...
Click to collapse
Here's a logcat. I had to update adb to latest version to get working.
mdcool26 said:
Here's a logcat. I had to update adb to latest version to get working.
Click to expand...
Click to collapse
Now we got something.
Status update in 5 minutes.
---------- Post added at 03:57 PM ---------- Previous post was at 03:39 PM ----------
DISCLAIMER: I'm not a developer. So expect some hiccups.
Potential issues:
dlopen failed: library "/system/lib/libnetcmdiface.so" not found
^Missing module. (Might mean networking problems )
bool android::SecHdmi::create(int, int)::FIMC0: Insufficient memory size(0x 3c00KB) for Graphic layers
^Hdmi? Don't worry 'bout this one.
(Seems like Hdmi out on this phone won't work} Does this phone have Hdmi out?
Back to the point.
Do you have trouble with airplane mode or wifi or any other networking?
What settings have you touched in developer options?
It says something about database issues with the settings application. Have you changed the default database at all with titanium backup?
(as in: Convert dbs to WAL mode)
Go run fix permissions in recovery.
Try the settings.
Then if it doesn't work try clearing data for settings app, and rebooting into recovery and clearing dalvik cache.
Can you quote this post to the rom developer please?
Other Stuff to highlight:
Code:
[ 12-01 04:11:07.846 7678: 7718 E/Volley ]
[287] NetworkDispatcher.run: Unhandled exception java.lang.NullPointerException
java.lang.NullPointerException
at com.android.volley.toolbox.BasicNetwork.performRequest(BasicNetwork.java:100)
at com.android.volley.NetworkDispatcher.run(NetworkDispatcher.java:105)
[ 12-01 04:11:13.736 4615: 4700 D/CrashAnrDetector ]
processName: com.android.settings
[ 12-01 04:11:13.736 4615: 4700 D/CrashAnrDetector ]
broadcastEvent : com.android.settings system_app_crash
This looks like a major issue:
[ 12-01 04:11:07.776 7771: 7783 E/DatabaseUtils ]
Writing exception to parcel
java.lang.NullPointerException
at com.visionobjects.resourcemanager.util.Version.compareTo(Version.java:88)
at com.visionobjects.resourcemanager.util.Version.compareTo(Version.java:1)
at java.util.ComparableTimSort.countRunAndMakeAscending(ComparableTimSort.java:286)
at java.util.ComparableTimSort.sort(ComparableTimSort.java:153)
at java.util.ComparableTimSort.sort(ComparableTimSort.java:142)
at java.util.Arrays.sort(Arrays.java:1973)
at java.util.Collections.sort(Collections.java:1867)
at com.visionobjects.resourcemanager.core.FileSystemHelper.keepOnlyMostRecentLibVersion(FileSystemHelper.java:64)
at com.visionobjects.resourcemanager.core.FileSystemHelper.<init>(FileSystemHelper.java:52)
at com.visionobjects.resourcemanager.DataStorageProvider.buildLangCache(DataStorageProvider.java:270)
at com.visionobjects.resourcemanager.DataStorageProvider.buildLangsCursor(DataStorageProvider.java:315)
at com.visionobjects.resourcemanager.DataStorageProvider.query(DataStorageProvider.java:175)
at android.content.ContentProvider.query(ContentProvider.java:744)
at android.content.ContentProvider$Transport.query(ContentProvider.java:199)
at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:114)
at android.os.Binder.execTransact(Binder.java:388)
at dalvik.system.NativeStart.run(Native Method)
[ 12-01 04:11:07.786 7743: 7743 D/AndroidRuntime ]
Shutting down VM
[ 12-01 04:11:07.786 7743: 7743 W/dalvikvm ]
threadid=1: thread exiting with uncaught exception (group=0x41c70700)
[ 12-01 04:11:07.801 5072: 5072 W/dalvikvm ]
Refusing to reopen boot DEX '/system/framework/commonimsinterface.jar'
[ 12-01 04:11:07.806 7743: 7743 E/AndroidRuntime ]
FATAL EXCEPTION: main
java.lang.RuntimeException: Unable to start receiver com.android.settings.SettingsIntentReceiver: java.lang.NullPointerException
at android.app.ActivityThread.handleReceiver(ActivityThread.java:2541)
at android.app.ActivityThread.access$1600(ActivityThread.java:159)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1392)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:5419)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:525)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1046)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:862)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:115)
at dalvik.system.NativeStart.main(Native Method)
Caused by: java.lang.NullPointerException
at android.os.Parcel.readException(Parcel.java:1437)
at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:185)
at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:137)
at android.content.ContentProviderProxy.query(ContentProviderNative.java:385)
at android.content.ContentProviderClient.query(ContentProviderClient.java:86)
at android.content.ContentProviderClient.query(ContentProviderClient.java:67)
at com.android.settings.handwritingsearch.RMHelper.getLangList(RMHelper.java:43)
at com.android.settings.SettingsIntentReceiver.checkVOLanguage(SettingsIntentReceiver.java:1752)
at com.android.settings.SettingsIntentReceiver.onReceive(SettingsIntentReceiver.java:565)
at android.app.ActivityThread.handleReceiver(ActivityThread.java:2525)
... 11 more
[ 12-01 04:11:07.836 4615: 5202 I/ActivityManager ]
Notify an ApplicationCrash
problem in glamour s4 rom
I am also using glamour s4 rom on s3 but there are some problems which lack my device performance .!
The camera isn't working properly when I click the button to capture the image the camera is unfortunately get stopped .!
Sometimes settings also stopped !
And a window appear on which writen
Unfortunately touchwiz stopped .!
Plz help me guys .!
Although I respect the work of henery and his partners !
May I get the solutions of these all problems .!
Otherwise the best rom having features of s4 and of note 3 .!
Hey guys,
I was having trouble when disable the captive portal detection.
I got a Nexus5 with the latest original 6.0 rom MRA58N. To root the device, I also flashed a third part kernel, which is ElementalX 6.05 and SuperSU 2.46.
I used the adb shell on my computer and got a error prompt as shown below:
settings put global captive_portal_detection_enabled 0
Error while accessing settings provider
java.lang.NullPointerException: Attempt to invoke interface method 'android.app.
IActivityManager$ContentProviderHolder android.app.IActivityManager.getContentPr
oviderExternal(java.lang.String, int, android.os.IBinder)' on a null object refe
rence
at com.android.commands.settings.SettingsCmd.run(SettingsCmd.java:141)
at com.android.commands.settings.SettingsCmd.main(SettingsCmd.java:63)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:251)
Anyone here can help me?
Hello,
I downloaded an apk (yalp store) from the browser app and just cannot install it (I included screenshots). Even after redownloading it from the phone or computer then saving in the micro sd for the phone, it doesn't work.
This happens to all apks in both external (micro sd card) and internal storage.
So I fired up the logcat and found this shortly after tapping install.
Code:
6-21 20:48:51.234 1704 1718 W : Unable to open '/storage/emulated/0/Download/com.github.yeriomin.yalpstore_42.apk': Permission denied
06-21 20:48:51.234 1704 1718 W zipro : Error opening archive /storage/emulated/0/Download/com.github.yeriomin.yalpstore_42.apk: I/O Error
06-21 20:48:51.234 1704 1718 D asset : failed to open Zip archive '/storage/emulated/0/Download/com.github.yeriomin.yalpstore_42.apk'
06-21 20:48:51.236 1704 1718 W DefContainer: Failed to parse package at /storage/emulated/0/Download/com.github.yeriomin.yalpstore_42.apk: android.content.pm.PackageParser$PackageParserException: Failed to parse /storage/emulated/0/Download/com.github.yeriomin.yalpstore_42.apk
06-21 20:48:51.241 591 655 I art : Starting a blocking GC Explicit
I can install apks through the play store and
Code:
adb install
but not through a root shell with
Code:
pm install
I'm in android 6.0.1 with everything wiped out and micro sdcard is not plugged-in.
If it could help, I am currently bringing up Android Marshmallow on my device so it's possible to modify some source code and init files.
Any ideas how to install the apk from the phone?
So, the new permissions can be found on frameworks/base/data/etc/platform.xml.
Okay, it's now solved. The permission denied thingy is because of that. Since the platform.xml in the build is from the official android 4.4 kitkat build, the permission is not there yet. Manually adding the permissions made it work, well... for me I have to do a factory reset first.
One thing more, the platform.xml seems that it needs to be in unix line endings.
UPDATE: Asus has updated the servers. Older protocols for HTTPS, which are required for older Android versions, are no longer supported. Unfortunately, some additional steps are needed for the unlock now. See this post for step by step instructions.
I recently got my hands on a Asus TF700T with a locked boot loader. The official unlock app did not work, so I took a closer look. What I found is that the Asus servers are still up and running, but connection fails due to certificate pinning. And that can be dealt with
So here are the instructions:
The device must be rooted. KingoRoot (the app) worked for me.
Download the unlock bundle from the link below. I didn't find a way to directly attach files here.
Copy both apks to /system/app, change the permission to 0644
For this, a remount of the system partition may be needed:
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
DMClient.apk replaces the original DMClient.apk and DMClient.odex (i.e. you have to rename/move/delete the .odex file)
The modified unlock app cannot be installed like any other and must be installed that way
Reboot the device. On startup Android shows that one app is optimized (that's DMClient). The unlock app is now installed.
Use the unlock app. Google account does not matter.
Watch logcat to get some more information on what the unlock app does. On success the device immediately reboots, so redirect adb logcat to a file if you want to keep the log.
I only tested on a TF700T with WW SKU, V10.6.1.14.10. I assume that other firmware versions work as well.
The unlock app for TF700T also supports TF201, TF300T, TF300TG, and TF300TL, but a modified DMClient is needed.
In case something goes wrong and your device gets stuck at the boot screen, this advice may be helpful:
Bricked my Asus TF300T? Manual JB update
First, my device failed to get the OTA Update because I deleted some system apps (see my original post). Then I found this post where another user restored original APKs in /system/apps and manage...
android.stackexchange.com
(thanks @DieAbrissbirne)
Download links
Unlock app and DMClient for TF700T
https://leo.pfweb.eu/dl/OaKdx
Spoiler: Successfully used on
WW_epad-10.6.1.14.10
JOP40D.US_epad-10.6.1.14.10-20130801
DMClient for TF300T
https://leo.pfweb.eu/dl/vUHnp
DMClient for TF300TG
https://leo.pfweb.eu/dl/xphHy
DMClient for TF201
https://leo.pfweb.eu/dl/pKvEA
Spoiler: Successfully used on
WW_epad_10.4.2.17
---------------------------------------------------------------------
Unlock app and DMClient for TF701T
https://leo.pfweb.eu/dl/2AcpB
DMClient for ME301T (also seems to work for ME302KL)
https://leo.pfweb.eu/dl/uiJPN
Dealing with this same issue, but can't get your method to work... Do I need to already have the v7 unlock tool installed before this? And do I just remove the DMClient.odex file from /system/app since there is only the replacement file for DMClient.apk?
Any help is appreciated!
You don't need the original unlock app. I recommend uninstalling it. DMClient.odex is not needed, you can rename or delete it. I don't know what happens if you keep it as is.
At which point does it fail?
Is the unlock app installed after restart? If not, check the permissions of both files. It must be 644 (-rw-r--r--).
If you can start the modified unlock app: Do you get an error message? Is there anything relevant in logcat (search for "unlock")? Is the internet connection ok?
Code:
-rw-r--r-- root root 442064 2020-09-02 22:19 UnLock_App_V7_update.apk
Removed both DMClient.apk and .odex and don't have any original unlock apps installed. But I don't have the modified unlock app installed after restart.
Which firmware version do you have?
The permissions look good. Basically all apks in /system/app should have the same owner and permissions.
If I understand correctly, you have removed the original DMClient.apk and DMClient.odex and copied the modified one from the download. Is the permission correct?
If permissions are ok, it's hard to say, what is wrong. I would suggest to rename UnLock_App_V7_update.apk to something else (maybe unlock.apk) and reboot the device. This forces a reinstall. Best would be if you could watch logcat during startup. The log will tell you why the installation fails.
Edit: Are you sure, the app is not installed? Depending on the locale it may not be literally translated as "unlock app". The icon is a gear with a lock.
JOP40D.US_epad-10.6.1.14.10-20130801
Code:
W/ActivityManager( 524): No content provider found for permission revoke: file:///data/local/tmp/UnLock_App_V7_update.apk
W/ActivityManager( 524): No content provider found for permission revoke: file:///data/local/tmp/UnLock_App_V7_update.apk
I/PackageManager( 524): Copying native libraries to /data/app-lib/vmdl1192069982
W/PackageParser( 524): Exception reading classes.dex in /data/app/vmdl1192069982.tmp
W/PackageParser( 524): java.lang.SecurityException: META-INF/MANIFEST.MF has invalid digest for classes.dex in /data/app/vmdl1192069982.tmp
W/PackageParser( 524): at java.util.jar.JarVerifier.invalidDigest(JarVerifier.java:131)
W/PackageParser( 524): at java.util.jar.JarVerifier.access$100(JarVerifier.java:53)
W/PackageParser( 524): at java.util.jar.JarVerifier$VerifierEntry.verify(JarVerifier.java:123)
W/PackageParser( 524): at java.util.jar.JarFile$JarFileInputStream.read(JarFile.java:119)
W/PackageParser( 524): at java.io.BufferedInputStream.read(BufferedInputStream.java:304)
W/PackageParser( 524): at android.content.pm.PackageParser.loadCertificates(PackageParser.java:447)
W/PackageParser( 524): at android.content.pm.PackageParser.collectCertificates(PackageParser.java:634)
W/PackageParser( 524): at com.android.server.pm.PackageManagerService.installPackageLI(PackageManagerService.java:7959)
W/PackageParser( 524): at com.android.server.pm.PackageManagerService.access$1900(PackageManagerService.java:180)
W/PackageParser( 524): at com.android.server.pm.PackageManagerService$5.run(PackageManagerService.java:6108)
W/PackageParser( 524): at android.os.Handler.handleCallback(Handler.java:725)
W/PackageParser( 524): at android.os.Handler.dispatchMessage(Handler.java:92)
W/PackageParser( 524): at android.os.Looper.loop(Looper.java:137)
W/PackageParser( 524): at android.os.HandlerThread.run(HandlerThread.java:60)
E/PackageParser( 524): Package com.asus.unlock has no certificates at entry classes.dex; ignoring!
Does this SO post make sense as the issue? stackoverflow DOT com/questions/44386464/android-app-installation-failed-package-com-my-app-has-no-certificates-at-entry
That's interesting. The app isn't signed at all, that's why "normal install" does not work. But as system app things worked for me and there was no error.
Besides rooting the device I had unlocked developer options and allowed install from unknown sources. But I wouldn't expect these to make any difference.
Is there anything about DMClient in the log? The same applies here. It would be strange if it works for one and not for the other.
Got it to work. After digging a bit deeper into the logs I think it was confused because I had already installed and uninstalled the original unlock tool. It was complaining about the unlock package already existing, etc.
So, I just went all the way back to a factory reset to remove everything and then did your original steps and it worked. I was watching logcat and it didn't say anything about the unlock package for the time it worked too btw. I guess uninstalling the original and restarting wasn't enough to truly get rid of it enough without a factory reset.
Thanks for your help and effort to put this together!
Great! Do you mean, there was no output from the unlock app at all? There should have been some information starting with
Code:
/****Unlock
. However, it does not persist reboot, so you have to watch live or redirect to a file.
I was watching it live and did a find on the output for 'unlock' once it restarted and didn't see anything but I suppose I could have missed it.
It's only a couple of lines so indeed easy to miss. Thanks for the feedback :good:
d.l.i.w said:
It's only a couple of lines so indeed easy to miss. Thanks for the feedback :good:
Click to expand...
Click to collapse
Didn't work for me, unfotunatly . I still get message - "Failed to unlock your device, please try again later".
Device: TF300TG.
FW: WW_epad-10.4.3.9-20121106
Android: 4.1.1
Tried to reset to factory settings. Didn't help either.
Please, tell me - can I use V7 apk with Android 4.2 / 4.2.1 or i need patched version of Unlock_V8.apk ?
I/*** Unlock: request( 2000): h t t p s: //mdm.asus.com/DMServer/DeviceState?id=XXXXXXXXXXXX&AUTH=YYYYYYYYYYYYYYY&ACTION=get
D/dalvikvm( 2000): GC_CONCURRENT freed 269K, 5% free 6796K/7111K, paused 16ms+20ms, total 86ms
D/DMServerUnlock( 2000): index of line: 1
D/DMServerUnlock( 2000): DM Server Response: 0
W/GoogleVerify( 2000): no google account
I/UnLockActivity( 2000): no Google account and pin code
Click to expand...
Click to collapse
Of course, I changed variable values in request URL.
iserver said:
Device: TF300TG
Click to expand...
Click to collapse
Obviously DMClient is specific to each device model. So, the modified DMClient is not compatible with devices other than TF700T.
Is the original firmware for the TF300TG available somewhere? If so, I might be able to create a modified DMClient also for this model, but I can't promise anything.
So I am fairly early into this root / unlock of my new tf700t.
I rooted / unlocked my old tf300t at least 8 years ago now.
I recently dusted it off and immediately after getting 7.1.2 installed on it and having it set up just right, stepped on it by accident.
So I bought a tf700t and have been trying to root it for a whole day with out success....
I have successfully upgraded the boot loader from 10.4.4.25 to WW 10.6.1.14.8 and gotten Motochopper to root.
Can you go over the tools and method you used to put the two files from the package into the system/apps folder with he new permissions?
When I try and move the files my go-to rooted file explorer (Ghost commander) refuses to change the permissions or move the files.
Is it possible that GhostCommander and TotalCommander simply don't work with the motochopper version of rooting? or am I missing something more fundamental?
I get that given the age of the tablet I will not be able to unlock with the normal v7 unlocker and b/c Asus are bastards.
What a Deus-ex it was to find a post from only a few weeks ago on the topic.
I love XDA.
Down0038 said:
Can you go over the tools and method you used to put the two files from the package into the system/apps folder with he new permissions?
When I try and move the files my go-to rooted file explorer (Ghost commander) refuses to change the permissions or move the files.
Is it possible that GhostCommander and TotalCommander simply don't work with the motochopper version of rooting? or am I missing something more fundamental?
I get that given the age of the tablet I will not be able to unlock with the normal v7 unlocker and b/c Asus are bastards.
Click to expand...
Click to collapse
Total Commander worked for me just fine. It asked if the system partition should be mounted writable and then copied the files. The same with setting permissions.
I used KingoRoot, because Motochopper does not work on the latest firmware, but this shouldn't make any difference. You could try to copy the files via adb shell.
I was quite surprised that the Asus servers are still running and functional. The only issue is that the original unlock app does not trust the new server certificates.
"the device is unlocked"
Thanks for this work! Dusted off an old TF700T, but I'm unable to unlock, with the following logs (grepped for unlock):
Code:
I/ActivityManager( 520): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.asus.unlock/.EulaActivity} from pid 835
I/ActivityManager( 520): Start proc com.asus.unlock for activity com.asus.unlock/.EulaActivity: pid=1715 uid=1000 gids={41000, 3003, 1015, 1028, 3002, 3001, 1006, 3007}
I/ActivityManager( 520): START u0 {cmp=com.asus.unlock/.UnLockActivity} from pid 1715
D/DMServerUnlock( 1715): get DMServer Response retry count = 3
I/*** Unlock: md5 input( 1715): 50465d2a5837unknown8bf0d93b7649a513c736f4016495a5ec5b2ab8a0dm_servernEEd_query_STATe
I/*** Unlock: request( 1715): [url]https://mdm.asus.com/DMServer/DeviceState?id=50465d2a5837&AUTH=OsYXBMvoh62t24Ukl025Lw&ACTION=get[/url]
D/DMServerUnlock( 1715): index of line: 3
D/DMServerUnlock( 1715): DM Server Response: 105
I/ActivityManager( 520): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.asus.unlock/.EulaActivity} from pid 835
I/UnLockActivity( 1715): ============= UnLockActivity onStart =======================
I/UnLockActivity( 1715): ============= UnLockActivity onResume =======================
D/DMServerUnlock( 1715): get DMServer Response retry count = 3
I/*** Unlock: md5 input( 1715): 50465d2a5837unknown8bf0d93b7649a513c736f4016495a5ec5b2ab8a0dm_servernEEd_query_STATe
I/*** Unlock: request( 1715): [url]https://mdm.asus.com/DMServer/DeviceState?id=50465d2a5837&AUTH=OsYXBMvoh62t24Ukl025Lw&ACTION=get[/url]
D/DMServerUnlock( 1715): index of line: 3
D/DMServerUnlock( 1715): DM Server Response: 105
D/DMServerUnlock( 1715): get DMServer Response retry count = 3
I/*** Unlock: md5 input( 1715): 50465d2a5837unknown8bf0d93b7649a513c736f4016495a5ec5b2ab8a0dm_servernEEd_query_STATe
I/*** Unlock: request( 1715): [url]https://mdm.asus.com/DMServer/DeviceState?id=50465d2a5837&AUTH=OsYXBMvoh62t24Ukl025Lw&ACTION=get[/url]
D/DMServerUnlock( 1715): index of line: 3
D/DMServerUnlock( 1715): DM Server Response: 105
I fear I have one of those TF700's that doesn't have a valid serial number, so it can't unlock?
For me unlock worked, although the Asus website did not recognize the serial number when I tried to register my device.
I don't know what the response 105 means, but this does not necessarily mean an error. It could be that the modified DMClient was not installed correctly.
Which firmware version do you have? Did you do a factory reset before?
d.l.i.w said:
For me unlock worked, although the Asus website did not recognize the serial number when I tried to register my device.
I don't know what the response 105 means, but this does not necessarily mean an error. It could be that the modified DMClient was not installed correctly.
Which firmware version do you have? Did you do a factory reset before?
Click to expand...
Click to collapse
Yes, I factory reset before installing. I had rooted with Kingo Root / Superuser, but had to root via ADB, because I couldn't download and run the apk directly on the tablet after the factory reset. I did allow it to install all the associated root utilities/apps. I used a console/terminal app called "Material Terminal" (by Yaroslav Shevchuk) installed by the play store to su, mv the DMClient and Unlock_App_v7 apk files to /system/app and chmod 0644 them... every reboot shows it "Optimizing the app".
I have Android v 4.2.1 Kernel version 3.1.10-gb1a9af5 dated Aug 1 2013
I'll probably try doing another factory reset, root, and install again just to be sure.
Does someone have a correct version of Kingoroot apk that does work for ICS tf700t please :fingers-crossed:? I tried all i've found it doesnt work
EDIT: Found it
The tutorials works!!! Thank you very much ))
TF700T 4.2.1 - 10.6.1.14.10-20130801
I just made a LOS19 ROM. It cant seem to boot past a service. The error message is
```
[1:init]init: Control message: Could not find 'aidl/android.system.keystore2.IKeystoreService/default' for ctl.interface_start from pid: 400 (/system/bin/servicemanager)
```
I originally thought it was because I didn't do a data wipe, then I did rm -r /data/.* and rebooted I still get the boot freeze. Any Idea on what could be causing the service failure?
It is happening because I rebuilt the vendor image using proprietary blobs + vndk in system. If I don't build the vendor image selinux complains proprety context in system dosnt match property sha2 in vendor
Here is my last_kmsg log.
bretjoseph said:
I just made a LOS19 ROM. It cant seem to boot past a service. The error message is
```
[1:init]init: Control message: Could not find 'aidl/android.system.keystore2.IKeystoreService/default' for ctl.interface_start from pid: 400 (/system/bin/servicemanager)
```
I originally thought it was because I didn't do a data wipe, then I did rm -r /data/.* and rebooted I still get the boot freeze. Any Idea on what could be causing the service failure?
It is happening because I rebuilt the vendor image using proprietary blobs + vndk in system. If I don't build the vendor image selinux complains proprety context in system dosnt match property sha2 in vendor
Here is my last_kmsg log.
Click to expand...
Click to collapse
I could be wrong, but...
This part of your error tells you that the boot sequence can not find the file it is naming in the error and its location.
[1:init]init: Control message: Could not find 'aidl/android.system.keystore2.IKeystoreService/default'
This part of your error tells you which service failed to start:
ctl.interface_start from pid: 400
This part of your error tells you the location of the service that failed to start due to the missing or corrupted file.
(/system/bin/servicemanager)
This file is either missing or is incorrectly configured for the boot sequence to read/load in order to start the stated service.
You will have to either compile the ROM again from source, making sure that this file is included in the compiling process or compile this file from your device's sources or pull this file from existing ROMs or firmware for your device then place the file in the location that your error indicates:
'aidl/android.system.keystore2.IKeystoreService/default'
where do I find aidl files located? are they in some system/etc XML file?
bretjoseph said:
where do I find aidl files located? are they in some system/etc XML file?
Click to expand...
Click to collapse
It looks to be part of the source code and must be manually included in the build process.
Android Interface Definition Language (AIDL) | Android Developers
developer.android.com
AIDL for HALs | Android Open Source Project
source.android.com
Keymaster.cpp - platform/system/vold - Git at Google
From what I read I need to have a file in the following path
Code:
system/hardware/interfaces/keystore2/aidl/android/system/keystore2/IKeystoreService.aidl
and possibly
Write an AIDL HAL serverPut this in VINTF manifest,
Code:
<hal format="aidl">
<name>android.system.keystore2</name>
<version>1</version>
<fqname>IKeystoreService/default</fqname>
</hal>
Put this in the compatibility matrix,
Code:
<hal format="aidl" optional="true">
<name>android.system.keystore2</name>
<version>1</version>
<interface>
<name>IKeystoreService</name>
<instance>default</instance>
</interface>
</hal>
Yep that solved the issue
bretjoseph said:
Yep that solved the issue
Click to expand...
Click to collapse
Good, then, on to the next issue in your build, if any.
Hi, I'm trying to port lineageos to Samung Tab S7 and I had issue of
Code:
init: Control message: Could not find 'aidl/android.system.keystore2.IKeystoreService/default' for ctl.interface_start from pid: 580 (/system/bin/servicemanager)
as you did. I tried to add
Code:
<hal format="aidl">
<name>android.system.keystore2</name>
<version>1</version>
<fqname>IKeystoreService/default</fqname>
</hal>
to manifest.xml and add
Code:
<hal format="aidl" optional="true">
<name>android.system.keystore2</name>
<version>1</version>
<interface>
<name>IKeystoreService</name>
<instance>default</instance>
</interface>
</hal>
to device_framework_matrix.xml but still failed to work. May I know where exactly you put those contents to and any other actions you did you bypass this issue? Thanks