Hi,
I was bit too quick and updated my phone to 38r level using the modified update script. This was because the original update script would fail because I had franco kernel installed and it was complaining about thermal-engine. The upgrade went fine, except now seems I am missing the whole /system/bin/thermal-engine file. Also lockscreen was not updated. So if someone could provide lockscreen apk and odex, and also the thermal-engine files, I would be grateful.
I believe the lockscreen files would be
/system/app/LockClock.odex
/system/app/LockClock.apk
Correct me if I am wrong.
Thanks
I also had the Franco kernel before updating and now I have no lock screen at all. Is this the same issue you are having?
Korov, no, I still had the default lock screen working, just not the new one.
I got the new one by going to settings/lock screen and tapping the custom lock screen to enable it.
After that the new locksreen came up.
As for the thermal-engine file, I found the 38R version of that and installed it, seems to be working fine.
Actually, the phone also worked just fine also without that file, but better safe than sorry.
Related
This is driving me crazy. I tried updating to Google Play Services 8.1.14 so I can try Android Pay. I can install the apk, and it seems to work fine. However, when I reboot I'm always back to GPS 7.8.99.
I uninstalled Android Wear, Android Pay, etc. I turned on airplane mode, reverted all GPS updates (puts it on 6.x), installed the 8.1.14 apk, and when I reboot.... still on 7.8.99!
Yes, I am using the correct built (-238). I am on stock/rooted/s-off 5.0.1 w/ root turned off in SuperSU. If anyone has any clue whats happening here, let me know!
Okay, so it looks like I solved my own problem. I reenabled root and UNINSTALLED Google Play Services via Titanium, then installed 8.1.14, and it seems to have stuck. I still have no clue why the update was reverting, but... whatever. Hopefully this helps someone in the future if they have the same issue.
Disregard my last, that was not successful. Smart Lock disappeared, and my Trust Agents page was blank with no obvious fix. I did a clean install w/ the latest stock/rooted RUU, and updated straight to services 8.1.14 apk, which worked fine (ncluding smart lock). Until...
Until an 8.1.15 auto-update. Which put me right back into the same revert on reboot loop, except now it would update to 8.1.15 a couple minutes after ever boot, and then revert to 8.1.14 every reboot.
I sorta narrowed down the problem... The 8.1.14 update I installed manually via apk resided at /data/app/com.google.android.gms-1
Every time I rebooted, it created a NEW folder and redownloaded 8.1.15 to to those folders, named com.google.android.gms-2, com.google.android.gms-3, com.google.android.gms-4, etc.
I'm assuming this is exactly what it was doing before i wiped, except 7.8.99 was installed to the com.google.android.gms-1 folder which it always reverts to.
The fix was simple: delete com.google.android.gms-1... rename com.google.android.gms-2 to com.google.android.gms-1. Delete all the extra copies.
If anyone could explain this behaviour, I would love to hear. This seems like a pretty big bug, I'm not sure if it's related to the (stock) rom or a bug with the 8.1.x google play services.
here is your fix
http://forum.xda-developers.com/ver...lipop-apps-reverts-to-version-reboot-t3076563
this was a few pages back on this section. You basically need to change the owner of '/data/app' to the system. Post 7 has the adb commands or use root explorer or some other app to change all folder and subs.
Regards
carm01 said:
http://forum.xda-developers.com/ver...lipop-apps-reverts-to-version-reboot-t3076563
this was a few pages back on this section. You basically need to change the owner of '/data/app' to the system. Post 7 has the adb commands or use root explorer or some other app to change all folder and subs.
Regards
Click to expand...
Click to collapse
:victory: Some times my searching skills aren't up to snuff. I thought my issue was specific to play services, so this didn't come up. This is good to know, and should be added to the RUU thread!
Skitals said:
:victory: Some times my searching skills aren't up to snuff. I thought my issue was specific to play services, so this didn't come up. This is good to know, and should be added to the RUU thread!
Click to expand...
Click to collapse
I would agree about adding to ruu thread, however, i cannot enforce that. I know some of the newer ROMS might support that like fluent 6.1 i believe does, and santod latest debloat i have not had any of those issues with those.
No issues here. What I did was let it download gmscore, then I cut and pasted base.apk and lib (from data/app) to system/priv-app/GmsCore (deleting preeviois GmsCore.apk and lib first) and renamed to GmsCore.apk - then reboot.
Id try this.
If you've used Android N-ify with Good Lock, you will have known that there's an annoying bug, that the Good Lock settings icon overlaps the alarm section when the Quick Settings is expanded.
This will fix that, and fix up a few things in Good Lock to match AOSP/Google Pixel visuals
Screenshots in attachments.
Should be supported on any Samsung device on a Touchwiz-based 6.0/6.0.1 Marshmallow ROM (7.0 Nougat or newer is unsupported, you can use this Substratum theme instead which makes your SystemUI more AOSP-like!)
Will update this modified Good Lock accordingly as Good Lock itself recieves updates as well.
Changelog
v2
IMPORTANT: you must go and follow this, even if you already installed the previous version, just this one time. Added proper install instructions in the OP, shouldn't have any issues with installing now (read below)
Removed charging/wireless charging water splash animations
Changed default lockscreen wallpaper to stock Google Pixel wallpaper
v1
Removed Good Lock settings icon in quick settings header, to not overlap alarm icon in Android N-ify's quick settings header (still clickable where it was to access Good Lock settings)
Changed auto brightness icon in quick settings header to AOSP style
Changed screenshot notification icon to AOSP style
Changed Good Lock app icon to AOSP Nougat's SystemUI icon
Install instructions
If you are using stock Good Lock, or if you are on the first release of the modified Good Lock, follow the instructions ahead. If you haven't installed any Good Lock, skip to Step 4. Otherwise, if you're on v2 or later of modified Good Lock, and are just updating, skip to Step 6
Disable Android N-ify and GravityBox in Xposed Installer, and reboot
Uninstall Good Lock normally from the app (optional: backup Good Lock data)
Go to /data/app/ in your favourite root file manager, and delete any "com.android.systemui-#" folders (# is substituted with a number)
Install stock Good Lock again
Flash the modified Good Lock zip in TWRP
Enable Android N-ify and GravityBox
Enjoy (optional: restore Good Lock data)
Download
Realy great, works a lot better. Thank you mate. :good:
Great work bro
It doesn't seem to get installed when I flash it, I tried with and without Good Lock installed but it had the same effect. S7 Flat on Superman Rom 1.19
DarkboyZX said:
It doesn't seem to get installed when I flash it, I tried with and without Good Lock installed but it had the same effect. S7 Flat on Superman Rom 1.19
Click to expand...
Click to collapse
Yes, the ZIP does not work if you try to flash it before installing GoodLock and N-ify. It is recommended that you wipe and reflash the system partition after uninstalling N-ify and GoodLock, and then install GoodLock and N-ify -> reboot once -> flash the ZIP through recovery.
New update!
v2
IMPORTANT: you must go and follow this, even if you already installed the previous version, just this one time. Added proper install instructions in the OP, shouldn't have any issues with installing now (read below)
Removed charging/wireless charging water splash animations
Changed default lockscreen wallpaper to stock Google Pixel wallpaper
DarkboyZX said:
It doesn't seem to get installed when I flash it, I tried with and without Good Lock installed but it had the same effect. S7 Flat on Superman Rom 1.19
Click to expand...
Click to collapse
Follow the new install instructions, it should work now.
Is it possible to for the QS panel to be bluish-greyish, like on AOSP?
Since right now, it is completely black.
moriel5 said:
Is it possible to for the QS panel to be bluish-greyish, like on AOSP?
Since right now, it is completely black.
Click to expand...
Click to collapse
Yes it is.
In Good Lock routines editor, on the section where you pick theme colours, you can try and pick the blue-greyish colour for the first hexagon to the left, then your QS panel background colour will be set accordingly.
OhayouBaka said:
Yes it is.
In Good Lock routines editor, on the section where you pick theme colours, you can try and pick the blue-greyish colour for the first hexagon to the left, then your QS panel background colour will be set accordingly.
Click to expand...
Click to collapse
Thanks, I haven't installed your modified Good Lock yet on my father's phone (I don't use TouchWiz, however I was unable for some reason to boot CM12.1 on his phone (when there will be enough time, I will try CM13, or whatever will exist then)) since I thought that the colors will be too jarring for him.
When I'll have time, I'll install your modified Good Lock on his phone.
Is there a way to get a gap between the notifications?
Done
Sent from my hero2lte using XDA Labs
..
Hello,
First of all, thanks for the mod! Developpers like you are great, and add something to the community! Thanks.
Getting to the question. I know it may sound stupid, but this is supposed to make Good Lock work with Android N-ify. But I don't know when I should instal android n-ify. Should I install Good Lock (fresh install), flash your GoodLock v2 zip, and then install Android N-ify module through Xposed? Or do I not need to install the Android N-ify module?
Thanks in advance for the clarification. Cheers!
CamilleBC said:
Hello,
First of all, thanks for the mod! Developpers like you are great, and add something to the community! Thanks.
Getting to the question. I know it may sound stupid, but this is supposed to make Good Lock work with Android N-ify. But I don't know when I should instal android n-ify. Should I install Good Lock (fresh install), flash your GoodLock v2 zip, and then install Android N-ify module through Xposed? Or do I not need to install the Android N-ify module?
Thanks in advance for the clarification. Cheers!
Click to expand...
Click to collapse
Yep, you install android n-ify and gravitybox after you flash the good lock zip.
OhayouBaka said:
Yep, you install android n-ify and gravitybox after you flash the good lock zip.
Click to expand...
Click to collapse
Well thanks for the answer.
I followed the procedure, installed Good Lock, then flashed your zip, then installed Android N-ify 0.2 and Gravity Box, but the navigation panel still looks like the original Good Lock panel (I don't see neither Android N-ify effect, nor your Good Lock).
Don't know what I did wrong, but too bad for me.
Thanks for the help anyway !
CamilleBC said:
Well thanks for the answer.
I followed the procedure, installed Good Lock, then flashed your zip, then installed Android N-ify 0.2 and Gravity Box, but the navigation panel still looks like the original Good Lock panel (I don't see neither Android N-ify effect, nor your Good Lock).
Don't know what I did wrong, but too bad for me.
Thanks for the help anyway !
Click to expand...
Click to collapse
N-ify 0.2 on the xposed repo is really old, you want the latest build from https://ci.paphonb.xyz/jenkins/job/AndroidN-ify/
Also if installing my good lock made no difference, manually copy out the base.apk from the zip into /data/app/com.android.systemui-1, give -rw-r-r permissions and reboot
OhayouBaka said:
N-ify 0.2 on the xposed repo is really old, you want the latest build from https://ci.paphonb.xyz/jenkins/job/AndroidN-ify/
Also if installing my good lock made no difference, manually copy out the base.apk from the zip into /data/app/com.android.systemui-1, give -rw-r-r permissions and reboot
Click to expand...
Click to collapse
I tried as well, but it seems I can't get Android N-ify to work on my S7 Edge. It probably isn't related to your mod.
Thanks for the help! :good:
CamilleBC said:
I tried as well, but it seems I can't get Android N-ify to work on my S7 Edge. It probably isn't related to your mod.
Thanks for the help! :good:
Click to expand...
Click to collapse
No problem
Scratch that. Think it's a bug with the version of N-ify I'm using nevermind!
CloudyxVision13 said:
Scratch that. Think it's a bug with the version of N-ify I'm using nevermind!
Click to expand...
Click to collapse
The same thing happens to me when I use the latest version of N-ify from jenkins. However it doesn't do the same with version 0.20 from xposed, but It doesn't look as good as the screenshots in the OP.
Just wanted to let you guys know that full gesture navigation ist now (December Security Update - QQ1A.191205.017) working with third party launchers! I personally tested it with Nova Launcher.
Yup
Working with CPL launcher..
Sadly, they deleted option for accent colors and font duhhh [emoji45]
Sent from my PH-1 using Tapatalk
How can I install this update without loosing riot and clean my phone ?
Sent from my PH-1 using Tapatalk
philsner said:
Just wanted to let you guys know that full gesture navigation ist now (December Security Update - QQ1A.191205.017) working with third party launchers! I personally tested it with Nova Launcher.
Click to expand...
Click to collapse
strange only seems to have been a small security patch, was hoping it might fix sensitive sensors etc also, though I did notice Google pushing an update a week or so back so maybe that fixed the gestures? Anyone know where we can find out what Google is pushing out via play store?
(edit: it took forever to optimise my apps, thought it was stuck after about 20min but no it finally installed, though maybe it was due to having some cloned apps this time)
d3adbroke said:
How can I install this update without loosing riot and clean my phone ?
Click to expand...
Click to collapse
You WILL lose root with the update; you just need to re-root it. No data loss if you do an OTA.
I've been installing all updates like this:
1. Download both OTA and full image from Essential onto PC.
2. Apply OTA via adb sideload.
3. Reboot, wait for the update to complete. The root is lost at this point.
4. Extract boot.img from the full image, copy to phone.
5. Patch boot.img with Magisk, copy patched file back to PC.
6. Flash patched boot.img via fastboot.
7. Reboot. You are now rooted again.
These steps are also described in details in other threads. I also tried once to do an OTA update directly on the phone, but somehow it took forever to finish, so I am sticking to my old method...
@kt-Froggy or anyone
I reckon this update that fixed 3rd party launcher must have come via the Play store using Googles new Project Mainline update system on Android 10. I did notice something was updating a few weeks ago in the background. Does anyone know where we can see what bits of Android has been updated via Play store?
IronRoo said:
Does anyone know where we can see what bits of Android has been updated via Play store?
Click to expand...
Click to collapse
Sorry, I have no idea... Would be interesting to know, for sure.
I also did notice a couple of times some updates in the background, even though I have auto updates disabled in Play Store. Didn't catch what was updating, though. I know some components are getting updated automatically regardless of the settings, e.g. Instant Apps, but not sure what exactly that was...
So I unfortunately have a unit with crappy wifi and bluetooth hardware that only works 10% of the time. I have sound a hopeful solution here https://forum.xda-developers.com/showpost.php?p=78204931&postcount=70
the problem is it seems to need a rooted device to run those scripts. So I have been trying to update my device to the Hal9k or malaysk ROMS. My device wont install the ModInstaller.apk no matter what I try. I click install and it just show package installer in the top bar for a sec then goes away and does nothing. I made sure the apps had access to install apks, I have tried moving it into data/apps. I jsut can get the unit to install the APKs to backup and install a new ROM. If I try to run the rom updater from sd and not with the apk backup it gives me an error: 21. not sure if either are related.
Or if someone knows a way i can run a script from the above url fix without updating a whole new rom and just whitelisting it would be so happy! I just want wifi and bluetooth
Please help
Thanks!
Still no luck,
any help?
Steelers743 said:
Still no luck,
any help?
Click to expand...
Click to collapse
How was your device determined to actually be an MTC(D/E) device?
These are the settings from my system. I have sense upgraded the firmware to the newest version i could find, I think it was 2.94 XRC.
This post is also the same issue as me. https://forum.xda-developers.com/an...e-xrc-v2-941-px5-wifi-bluetooth-wake-t3871755
No one else has had issues installing APKs before?
Is install enabled in factory options
Yup, now I feel silly, looked through all the settings and install apps was OFF in the factory settings. Thanks for the help, didn't even know to check there. I was able to update to hal9k and hopefully the script fixes the bluetooth and wireless issues.
Good morning!!
i need some quick help if possible! You can even PM me so we can troubleshoot through discord.
TL;DR: the screen instantly goes black, restarts and returns to lockscreen the moment i unlock my device with the pattern (i suspect it's SYSTEMUI but can't be 100% sure). i can't get in now and got some work related data i need to recover from a widget that contains text along with chats from Whatsapp Plus.
stupid me did not make a nandroid backup in TWRP and now i'm screwed.
I use a Oneplus one with RR-O-v6.1.0-20180613-bacon-Official Ressurection Remix ROM based on android 8.1. Kernel is default/unchanged. Magisk is newest version (i think there were no updates for months now). I got 2 modules:
- busybox.
- Magisk Hide .Props config (a small terminal utility that can make google think i use a opo6 with android 9 [that's what i chose] so i get app updates) worked fine for half a year.
Then i took a look and saw an update for both. updating Busybox crashed magisk. Updating .props config seemed ok and just required rebooting like normal.
That's it essentially. since the reboot i can't get past the unlock screen anymore.
I tried the following:
i visited this link https://magiskroot.net/uninstall-magisk-module-twrp/ to first try to boot in core-only mode. then with disabled modules, then i uninstalled Magisk entirely using magisk uninstaller flashable zip from magisk manager (dot) com
the problem persists. i wiped cache and Dalvik/ART cache too but still the same.
besides the obvious clean re-flash that will wipe my data is there anything i can do to save it?
also i tried to attach a logcat but doing it just gives me one line an then nothing when doing it in ADB while the oneplus is in recovery mode.
If device is on (on lockscreen) i get 'waiting for device'. i searched and that could be because the ADB debugging checkmark is off... any way to turn it on using adb?
could wiping JUST Boot or System in TWRP do anyting?
since i got Titanium backup, can it restore data from a TWRP backup?
please help if possible.
oneplusausage said:
(...)
TL;DR: the screen instantly goes black, restarts and returns to lockscreen the moment i unlock my device with the pattern (i suspect it's SYSTEMUI but can be 100% sure). i Can't get in now and got some work related data i need to recover from a widget that contains text along with chats from Whatsapp Plus.
(...)
Click to expand...
Click to collapse
Have you ever looked through google: Bypass Lockscreen xda?
The first link indicates the solution. Try it out.
.
ze7zez said:
Have you ever looked through google: Bypass Lockscreen xda?
The first link indicates the solution. Try it out.
.
Click to expand...
Click to collapse
Hello :good: ,
TL; DR: IT WORKED! many thanks to you, i googled a lot but your suggestion went over my head.
below info added for completion 's sake so it potentially could help future users:
meanwhile in addition to my post, i dirty flashed the original ROM (same version) without wiping anything.
i suspected that it would just bypass the PIN and lock, not the whole lockscreen.. i know both the pin and pattern, it just crashes after entering the correct pattern.
I did your google search which linked me to https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008
indeed. the pattern is successfully removed leaving me with just the 'swipe up to unlock' screen. i expected that it would crash after swiping up but it went to the homescreen thankfully!
some notes. As per guide i indeed deleted the below 3 files using the explorer in TWRP located in /data/system:
locksettings.db
locksettings.db-shm
locksettings.db-wal
however the files password.key and pattern.key were not present at all but in my case it didn't make any difference.
EDIT: added info and fixed spelling mistakes