This is a full rom (not GSI) of lineageos 16.0.
Features:
- Custom pie based kernel with overclocking support (3GHz CPU, 800MHz GPU), merged in with upstream Linux kernel + CAF, and many other changes.
- Vendor repo based entirely on PPS 55-34 release.
Bugs:
- Dual sim devices currently broken.
- Live display high brightness mode greyed out (did once work, in progress)
- Some apps won't install from latest security patch.
- selinux permissive.
- Enabling FP gestures in gestures settings page doesn't disable navbar.
- Maybe more.
Installlation:
- If encrypted, format internal storage completely (twrp cant decrypt pie encrypted data).
- Wipe data.
- Flash Los zip.
- Flash opengapps arm (I use nano).
- Flash magisk if you would like.
- Reboot and enjoy.
Kernel source: https://github.com/RealJohnGalt/kernel-msm/tree/lineage-16.0
Thanks: HUGE thanks to karthick11 and Flash (wh0dat), along with petya230 and all testers in telegram Moto G6 group. Also big thanks to other moto devs who worked on Payton and other devices.
Download: https://www.androidfilehost.com/?w=files&flid=295813
Donate (bitcoin): 1motoP5LR6nCXy8uPEy4mtpzzMJrnpFyU
Note: I've decided device and vendor repos will stay private for a little while. Full rom builds of RR and Descendant will be happening soon using these trees. Also ARM64 work has already begun.
Wtf this is awesome!
johngalt1 said:
This is a full rom (not GSI) of lineageos 16.0.
Features:
- Custom pie based kernel with overclocking support, merged in with upstream Linux kernel + CAF, and many other changes.
- Vendor repo based entirely on PPS 55-34 release.
Bugs:
- Live display high brightness mode greyed out (did once work, in progress)
- Some apps won't install from latest security patch.
- selinux permissive.
- Enabling FP gestures in gestures settings page doesn't disable navbar.
- Maybe more.
Installlation:
- If encrypted, format internal storage completely (twrp cant decrypt pie encrypted data).
- Wipe data.
- Flash Los zip.
- Flash opengapps arm (I use nano).
- Flash magisk if you would like.
- Reboot and enjoy.
Kernel source: https://github.com/RealJohnGalt/kernel-msm/tree/lineage-16.0
Thanks: HUGE thanks to karthick11 and Flash (wh0dat), along with petya230 and all testers in telegram Moto G6 group. Also big thanks to other moto devs who worked on Payton and other devices.
Download: https://www.androidfilehost.com/?w=files&flid=295813
Donate (bitcoin): 1motoP5LR6nCXy8uPEy4mtpzzMJrnpFyU
Note: I've decided device and vendor repos will stay private for a little while. Full rom builds of RR and Descendant will be happening soon using these trees. Also ARM64 work has already begun.
Click to expand...
Click to collapse
It looks great! How about volte? is it working?
m0bileb0y said:
It looks great! How about volte? is it working?
Click to expand...
Click to collapse
Yes, it works out of the box for me as well as testers on other carriers.
Edit: also unlike GSI, nfc works for users on devices with NFC.
First off: thank you! - working great so far.
Question: does this have dual sim support?
[email protected] said:
First off: thank you! - working great so far.
Question: does this have dual sim support?
Click to expand...
Click to collapse
It should, though it may not have been tested yet. Let me know if it has dual sim issues.
For me the sim card isn't detected in any of the 2 slots, returning to descendant gsi.
rainspx said:
For me the sim card isn't detected in any of the 2 slots, returning to descendant gsi.
Click to expand...
Click to collapse
Similar problems here.. Sim is detected in Slot 1 but refuses to work with my carrier. In Slot 2 it doesnt show up at all. Everything else works fine though
New Los build just uploaded. Faster GPS, dev hw random fix, and pinner fix. Still no WFD yet. https://www.androidfilehost.com/?w=files&flid=295813
rainspx said:
For me the sim card isn't detected in any of the 2 slots, returning to descendant gsi.
Click to expand...
Click to collapse
zwackelmannnn said:
Similar problems here.. Sim is detected in Slot 1 but refuses to work with my carrier. In Slot 2 it doesnt show up at all. Everything else works fine though
Click to expand...
Click to collapse
Could I get a logcat of boot from either of you?
johngalt1 said:
New Los build just uploaded. Faster GPS, dev hw random fix, and pinner fix. Still no WFD yet. https://www.androidfilehost.com/?w=files&flid=295813
Could I get a logcat of boot from either of you?
Click to expand...
Click to collapse
Sorry, just returned to stock. Maybe in a Day or two..
(I assume I have to type "logcat" into adb while my phone is booting?)
zwackelmannnn said:
Similar problems here.. Sim is detected in Slot 1 but refuses to work with my carrier. In Slot 2 it doesnt show up at all. Everything else works fine though
Click to expand...
Click to collapse
Same here. When using one sim card, the sim is only detected in slot 1 and not in slot 2. When using two sim cards, only the sim in slot one is detected.
I've generated two logs with adb logcat, but they're massive and I have no idea how to upload them.
Nice work!
Is this 64 bit?
johngalt1 said:
New Los build just uploaded. Faster GPS, dev hw random fix, and pinner fix. Still no WFD yet. https://www.androidfilehost.com/?w=files&flid=295813
Could I get a logcat of boot from either of you?
Click to expand...
Click to collapse
I tried your newest build(lineage-16.0-20190623-UNOFFICIAL-ali), but the issue is still present.
OK so for some reason usb debugging wont stay turned on when the phone reboots. I had to use an app called logcat reader to get atleast SOME information.
Also I believe I am facing two unrelated problems:
my sim is detected but the phone wont see my carriers' network (it does find other networks though)
the sim only works in slot one
[email protected] said:
Same here. When using one sim card, the sim is only detected in slot 1 and not in slot 2. When using two sim cards, only the sim in slot one is detected.
I've generated two logs with adb logcat, but they're massive and I have no idea how to upload them.
Click to expand...
Click to collapse
Zip the logs and attach them like I did.
johngalt1 said:
New Los build just uploaded. Faster GPS, dev hw random fix, and pinner fix. Still no WFD yet. https://www.androidfilehost.com/?w=files&flid=295813
Could I get a logcat of boot from either of you?
Click to expand...
Click to collapse
Not sure if I saved it correctly.
HeavyHDx said:
Nice work!
Is this 64 bit?
Click to expand...
Click to collapse
No
zwackelmannnn said:
I tried your newest build(lineage-16.0-20190623-UNOFFICIAL-ali), but the issue is still present.
OK so for some reason usb debugging wont stay turned on when the phone reboots. I had to use an app called logcat reader to get atleast SOME information.
Also I believe I am facing two unrelated problems:
my sim is detected but the phone wont see my carriers' network (it does find other networks though)
the sim only works in slot one
Zip the logs and attach them like I did.
Click to expand...
Click to collapse
rainspx said:
Not sure if I saved it correctly.
Click to expand...
Click to collapse
Thank you both. It seems the issue is limited to dual sim devices. I'll look over the logs and hopefully find something.
zwackelmannnn said:
I tried your newest build(lineage-16.0-20190623-UNOFFICIAL-ali), but the issue is still present.
OK so for some reason usb debugging wont stay turned on when the phone reboots. I had to use an app called logcat reader to get atleast SOME information.
Also I believe I am facing two unrelated problems:
my sim is detected but the phone wont see my carriers' network (it does find other networks though)
the sim only works in slot one
Zip the logs and attach them like I did.
Click to expand...
Click to collapse
rainspx said:
Not sure if I saved it correctly.
Click to expand...
Click to collapse
What carriers are both of you on?
johngalt1 said:
What carriers are both of you on?
Click to expand...
Click to collapse
German carrier called Eplus
johngalt1 said:
What carriers are both of you on?
Click to expand...
Click to collapse
T-mobile.
Thank for your incredible work.
Getting an error upon reboot into TWRP
AP Fastboot Flash Mode (Secure)
Error: Failed to load kernel!
Fastboot Reason: Fail-through from normal boot mode
-------------EDIT
Never mind, was using the wrong kernel since my phone hadn't received the 9.0 update yet. Updated using the stock image provided on here and then reflashed it with magisk and nanodroid for microG, works fantastic. Thank you for the work, I've been waiting for a custom Rom for this phone since last October.
Related
Moto E 2015 LTE
I have to open a new thread, after everything went ok considering the camera for many hours, it again stopped working after restore.
What happened? I made a backup with TWRM and rebooted my phone, a message from SuperSu appeared that the binaries have to be updated, but this message disappeared as fast as it appeared. So I could not do anything. A hint was shown at the display to DOWNgrade! the google playstore. I installed a very early version of playstore 3.1 and rebooted. But the camera continued to stop working...is busy etc... I do not want the get rid of root access, all the rest of the apps are working without problems. Do we have to wait for another version of SU? A total unroot gives back the full functionality of the cam. But certainly I do not want to do this. It seems to be a problem with android 5.0.2 hxxps://play.google.com/store/apps/details?id=com.motorola.camera&hl=de or even motorola. But why does it work without SU?
Camera is working again after deleting cache, stopping the programm, wiping the dalvik (I did it but I am not really sure if it is necessary, have a try) and rebooting. So it is definitely not an hardware issue. So we have to wait for an update working with Android 5.0.2 as they have had several problems with their camera app before regarding other smartphones . Thanks Motorola
Greets
RioGrandeBlood said:
Moto E 2015 LTE
I have to open a new thread, after everything went ok considering the camera for many hours, it again stopped working after restore.
What happened? I made a backup with TWRM and rebooted my phone, a message from SuperSu appeared that the binaries have to be updated, but this message disappeared as fast as it appeared. So I could not do anything. A hint was shown at the display to DOWNgrade! the google playstore. I installed a very early version of playstore 3.1 and rebooted. But the camera continued to stop working...is busy etc... I do not want the get rid of root access, all the rest of the apps are working without problems. Do we have to wait for another version of SU? A total unroot gives back the full functionality of the cam. But certainly I do not want to do this. It seems to be a problem with android 5.0.2 hxxps://play.google.com/store/apps/details?id=com.motorola.camera&hl=de or even motorola. But why does it work without SU?
Camera is working again after deleting cache, stopping the programm, wiping the dalvik (I did it but I am not really sure if it is necessary, have a try) and rebooting. So it is definitely not an hardware issue. So we have to wait for an update working with Android 5.0.2 as they have had several problems with their camera app before regarding other smartphones . Thanks Motorola
Greets
Click to expand...
Click to collapse
this is already a known issue when you flash twrp and root. its kinda hit and miss for users.
fix-this! said:
this is already a known issue when you flash twrp and root. its kinda hit and miss for users.
Click to expand...
Click to collapse
I did not know this. Extracted the recovery img from stock rom and the camera is working.
Would you please give me a hint if any cwm working for moto g g2 and x should be working on our phone?
RioGrandeBlood said:
I did not know this. Extracted the recovery img from stock rom and the camera is working.
Would you please give me a hint if any cwm working for moto g g2 and x should be working on our phone?
Click to expand...
Click to collapse
No idea if there is a cm recovery yet. So maybe its twrp that messes up the cam.
There is no clockwork recovery, hopefully a dev can port it.
Is the camera breaking a stock camera thing, or all cameras? Like if the stock doesn't work would downloading the Google camera from the Play Store work?
bobbyphoenix said:
Is the camera breaking a stock camera thing, or all cameras? Like if the stock doesn't work would downloading the Google camera from the Play Store work?
Click to expand...
Click to collapse
Did you try? I have not, because now stock camera works, after update after rebooting. I wonder how long will it work and what happens next...
RioGrandeBlood said:
Did you try? I have not, because now stock camera works, after update after rebooting. I wonder how long will it work and what happens next...
Click to expand...
Click to collapse
Not yet. I haven't rooted yet because of this bug. That's why I asked if anyone has tried a Play Store camera while the stock one doesn't work.
Sent from my MotoE2(4G-LTE)
bobbyphoenix said:
Not yet. I haven't rooted yet because of this bug. That's why I asked if anyone has tried a Play Store camera while the stock one doesn't work.
Sent from my MotoE2(4G-LTE)
Click to expand...
Click to collapse
Thats broke to, any camera will be. To fix it download root explorer, go to system/app/supersu and rename the apk to .bak. Reboot, your not totally unrooted and the camera will work.
A perm fix will be when moto releases our kernel source and we can compile a kernel with selinux set to off or permissive.
Whatever I do, delete SuperSU or not, delete TWRP or not, after any reboot the camera starts working, then after the next reboot it stopps working, after the next reboot it is working again. Even with working and not renamed SuperSU
What the hell is this?
Renaming does not work better or less.
Could you post the output of running this after you try to use your camera and it doesn't work:
Code:
adb shell su -c dmesg | grep denied
This may help identify the cause of problems if SELinux is to blame. Tonight, I will build and post a kernel with SELinux disabled to see if that fixes anything.
Alright, I built a kernel with SELinux disabled. Apart from that, the source code is straight from the Motorola GitHub.
This is for Styx LTE (surnia) only! Flash at your own risk. I am not responsible for bricking your device, causing damage, bodily harm yada yada.
http://filebin.ca/1v4FfHSxMtX3/surnia_boot_noselinux.img
To install it, go into fastboot and run
Code:
fastboot flash boot surnia_boot_noselinux.img
This kernel is probably missing a bunch of stuff, and it breaks Bluetooth and WiFi. The camera should work though. Try it out and see if it changes the behaviour of the camera. Once you're done with it, you can return to the stock kernel by flashing the stock boot.img.
adb shell su -c dmesg | grep denied
Thanks, I will try, but time is the problem right now.
I was a bit too fast, camera seems to work after renaming SU.apk into bat.
squid2 said:
Could you post the output of running this after you try to use your camera and it doesn't work:
Code:
adb shell su -c dmesg | grep denied
This may help identify the cause of problems if SELinux is to blame. Tonight, I will build and post a kernel with SELinux disabled to see if that fixes anything.
Click to expand...
Click to collapse
Not sure you can modify the kernel since we have no source yet.
fix-this! said:
Not sure you can modify the kernel since we have no source yet.
Click to expand...
Click to collapse
We do have the source. It's on Motorola's GitHub. It was posted right when the phone was released. Yesterday, I built a kernel with SELinux disabled and posted it two posts above yours.
EDIT: Kernel source link
After renaming SU into bak I later renamed it into the original apk. version to see what will happen. And in fact nothing happens. . Camera is working for days now after several rebootings. TWRP is working great and has no issue on the camera. Thank you fix-this!
squid2 said:
Alright, I built a kernel with SELinux disabled. Apart from that, the source code is straight from the Motorola GitHub.
This is for Styx LTE (surnia) only! Flash at your own risk. I am not responsible for bricking your device, causing damage, bodily harm yada yada.
http://filebin.ca/1v4FfHSxMtX3/surnia_boot_noselinux.img
To install it, go into fastboot and run
Code:
fastboot flash boot surnia_boot_noselinux.img
This kernel is probably missing a bunch of stuff, and it breaks Bluetooth and WiFi. The camera should work though. Try it out and see if it changes the behaviour of the camera. Once you're done with it, you can return to the stock kernel by flashing the stock boot.img.
Click to expand...
Click to collapse
tried to flash on my lte model us based gsm. just kept booting back into fastboot until i flashed my stock boot.img. you may wanna talk to chainfire to see if it would be better to make it set to permissive instead of fully disabling selinux.
---------- Post added at 09:11 PM ---------- Previous post was at 09:11 PM ----------
squid2 said:
We do have the source. It's on Motorola's GitHub. It was posted right when the phone was released. Yesterday, I built a kernel with SELinux disabled and posted it two posts above yours.
EDIT: Kernel source link
Click to expand...
Click to collapse
i didn't know that.
---------- Post added at 09:13 PM ---------- Previous post was at 09:11 PM ----------
RioGrandeBlood said:
After renaming SU into bak I later renamed it into the original apk. version to see what will happen. And in fact nothing happens. . Camera is working for days now after several rebootings. TWRP is working great and has no issue on the camera. Thank you fix-this!
Click to expand...
Click to collapse
its hit or miss for me. sometimes the cam works sometimes it doesn't.
fix-this! said:
tried to flash on my lte model us based gsm. just kept booting back into fastboot until i flashed my stock boot.img. you may wanna talk to chainfire to see if it would be better to make it set to permissive instead of fully disabling selinux.
Click to expand...
Click to collapse
Thanks for trying it. I'm not surprised that it didn't work. The quick hack of a boot image I posted is missing the device tree, and it will also fail to load all kernel modules due to a version mismatch. I had tested it on the unit I had at hand, and was shocked that it was able to boot and function without a device tree image, but the hardware I used is a bit different than what you have. I've ordered a production device, and it will hopefully arrive this week. Then I will be able to test properly.
I've been working on setting up proper build infrastructure to build working kernels for surnia (complete with compatible driver modules, device tree images etc). I'm hoping to publish an initial release of my kernel for surnia over the next week or two. My initial release would probably be largely the same as the stock kernel, and then I'll start adding improvements from there.
I think you can make SELinux permissive from boot without recompiling the kernel by simply adding androidboot.selinux=permissive to the kernel command line arguments in boot.img. If anyone wants, I can make such an image using the stock kernel. I don't have a suitable device to test with at the moment though.
squid2 said:
Thanks for trying it. I'm not surprised that it didn't work. The quick hack of a boot image I posted is missing the device tree, and it will also fail to load all kernel modules due to a version mismatch. I had tested it on the unit I had at hand, and was shocked that it was able to boot and function without a device tree image, but the hardware I used is a bit different than what you have. I've ordered a production device, and it will hopefully arrive this week. Then I will be able to test properly.
I've been working on setting up proper build infrastructure to build working kernels for surnia (complete with compatible driver modules, device tree images etc). I'm hoping to publish an initial release of my kernel for surnia over the next week or two. My initial release would probably be largely the same as the stock kernel, and then I'll start adding improvements from there.
I think you can make SELinux permissive from boot without recompiling the kernel by simply adding androidboot.selinux=permissive to the kernel command line arguments in boot.img. If anyone wants, I can make such an image using the stock kernel. I don't have a suitable device to test with at the moment though.
Click to expand...
Click to collapse
Yes fix-this, my camera stopped from working again after using a root cleaner (fixed permissions here-is this the problem?) and rebooted the device. But as squid2 wrote/suggested, the problems (permissive) do not seem to be too severe and could be solved in the near future. It seems to be just a matter of time. At this point I strongly recommend the installation of TWRP. I got a functioning camera back and it helps while working on our handy, TWRP does not seem to be the problem so better install it and keep it working. It helped me a lot. Greets
squid2:adb shell su -c dmesg | grep denied
I did it, but got the message grep written wrong/not found
Go grab it.
You will need to be on 3.0.2 for this OTA. Size 29 MB
Download HERE
-- SOURCE
Not support voLTE, I am back to cm13
I hope that after this official oxy update, cm13 official will fix 2g problem
Can I just flash this ZIP through TWRP, and won't loose my root?
Cryer said:
Can I just flash this ZIP through TWRP, and won't loose my root?
Click to expand...
Click to collapse
If you are on OxygenOS 3.0.2, flash the OTA, then SuperSU straight after it, and you should be still rooted.
Is it possible to flash the updated modem and bootloader on a custom rom? eg delete the system folders in the zip and flash it or by fastboot
FPSUsername said:
Is it possible to flash the updated modem and bootloader on a custom rom? eg delete the system folders in the zip and flash it or by fastboot
Click to expand...
Click to collapse
No, because the zip doesn't contain the full firmware images - it just patches the stock 3.0.2 firmware.
Spannaa said:
No, because the zip doesn't contain the full firmware images - it just patches the stock 3.0.2 firmware.
Click to expand...
Click to collapse
FCK, I think I bricked my device. I flashed the files through fastboot and now nothing happens.
Edit: fixed it. Guess custom rom users can not get 3.1.0 bl and modem?
FPSUsername said:
Is it possible to flash the updated modem and bootloader on a custom rom? eg delete the system folders in the zip and flash it or by fastboot
Click to expand...
Click to collapse
Spannaa said:
No, because the zip doesn't contain the full firmware images - it just patches the stock 3.0.2 firmware.
Click to expand...
Click to collapse
I have applied the patch and made a "firmware only" update zip for OOS 3.1.0. I have flashed it running CM13 and do not see any problems (Use it at your own free will)
https://www.androidfilehost.com/?fid=24686680535467592
itskapil said:
Go grab it.
You will need to be on 3.0.2 for this OTA. Size 29 MB
Download HERE
-- SOURCE
Click to expand...
Click to collapse
Unable to flash in recovery showing error 7 ???
This "update" is junk. It doesn't fix the picture compression problem that people have been complaining about for months. It doesn't fix the battery drain. It doesn't add VOLTE. It doesn't add the OnePlus gallery app or music app that was added to the OP3 and the OPX. It is basically the August security patch and that's it. LAME. Someone also mentioned that it adds 2 icon packs. Neat.
xphyle1971 said:
This "update" is junk. It doesn't fix the picture compression problem that people have been complaining about for months. It doesn't fix the battery drain. It doesn't add VOLTE. It doesn't add the OnePlus gallery app or music app that was added to the OP3 and the OPX. It is basically the August security patch and that's it. LAME. Someone also mentioned that it adds 2 icon packs. Neat.
Click to expand...
Click to collapse
How did you judge about battery drain problem so fast! The update is by no means small. I looked at all the files in the patch and they have almost touched all aspects of the ROM. Like many have posted, if the device did not come with VoLTE, there is a very slim chance we will get it. More than a technical problem, it is a lengthy process.
hetanshu said:
Unable to flash in recovery showing error 7 ???
Click to expand...
Click to collapse
Same problem here! (TWRP 3) First got a build.prop error message, reverted build.prop back to stock, error went away but error 7 was still there.
I'm on Boeffla Kernel + Super SU + Xposed, could any of those have anything to do with it?
hackworks said:
How did you judge about battery drain problem so fast! The update is by no means small. I looked at all the files in the patch and they have almost touched all aspects of the ROM. Like many have posted, if the device did not come with VoLTE, there is a very slim chance we will get it. More than a technical problem, it is a lengthy process.
Click to expand...
Click to collapse
I personally could care less about the VoLTE. Just pointing it out. But how hard would it have been to fix the picture compression problem? That's just lazy. Especially since it's been reported for MONTHS on the OP forums. And how about adding the music and gallery apps? And at only 29MB, they sure didn't touch much...
xphyle1971 said:
I personally could care less about the VoLTE. Just pointing it out. But how hard would it have been to fix the picture compression problem? That's just lazy. Especially since it's been reported for MONTHS on the OP forums. And how about adding the music and gallery apps? And at only 29MB, they sure didn't touch much...
Click to expand...
Click to collapse
Without looking at the source code, the following changes look significant:
422 total files modified
288 non-app files
82 library files
List of patched files below
./patch/boot.img.p
./patch/firmware-update/BTFM.bin.p
./patch/firmware-update/emmc_appsboot.mbn.p
./patch/firmware-update/hyp.mbn.p
./patch/firmware-update/NON-HLOS.bin.p
./patch/firmware-update/pmic.mbn.p
./patch/firmware-update/rpm.mbn.p
./patch/firmware-update/sbl1.mbn.p
./patch/firmware-update/tz.mbn.p
./patch/system/app/AntHalService/oat/arm64/AntHalService.odex.p
./patch/system/app/BasicDreams/oat/arm64/BasicDreams.odex.p
./patch/system/app/Bluetooth/oat/arm/Bluetooth.odex.p
./patch/system/app/BluetoothExt/oat/arm/BluetoothExt.odex.p
./patch/system/app/BluetoothMidiService/oat/arm64/BluetoothMidiService.odex.p
./patch/system/app/BTtestmode/oat/arm/BTtestmode.odex.p
./patch/system/app/Bugle/oat/arm64/Bugle.odex.p
./patch/system/app/CalculatorGoogle/oat/arm64/CalculatorGoogle.odex.p
./patch/system/app/CalendarGoogle/oat/arm64/CalendarGoogle.odex.p
./patch/system/app/CaptivePortalLogin/oat/arm64/CaptivePortalLogin.odex.p
./patch/system/app/CertInstaller/oat/arm64/CertInstaller.odex.p
./patch/system/app/Chrome/oat/arm/Chrome.odex.p
./patch/system/app/colorservice/oat/arm64/colorservice.odex.p
./patch/system/app/datastatusnotification/oat/arm64/datastatusnotification.odex.p
./patch/system/app/DeskClockGoogle/oat/arm64/DeskClockGoogle.odex.p
./patch/system/app/DMAgent/oat/arm64/DMAgent.odex.p
./patch/system/app/DocumentsUI/oat/arm64/DocumentsUI.odex.p
./patch/system/app/DownloadProviderUi/oat/arm64/DownloadProviderUi.odex.p
./patch/system/app/Drive/oat/arm64/Drive.odex.p
./patch/system/app/embms/oat/arm64/embms.odex.p
./patch/system/app/EngineeringMode/oat/arm64/EngineeringMode.odex.p
./patch/system/app/EngSpecialTest/oat/arm/EngSpecialTest.odex.p
./patch/system/app/FaceLock/oat/arm64/FaceLock.odex.p
./patch/system/app/fastdormancy/oat/arm64/fastdormancy.odex.p
./patch/system/app/FingerprintServiceExtension/oat/arm64/FingerprintServiceExtension.odex.p
./patch/system/app/Galaxy4/oat/arm/Galaxy4.odex.p
./patch/system/app/Gmail2/oat/arm64/Gmail2.odex.p
./patch/system/app/GmailExchange/oat/arm64/GmailExchange.odex.p
./patch/system/app/GoogleContactsSyncAdapter/oat/arm64/GoogleContactsSyncAdapter.odex.p
./patch/system/app/GoogleTTS/oat/arm/GoogleTTS.odex.p
./patch/system/app/Hangouts/oat/arm64/Hangouts.odex.p
./patch/system/app/HoloSpiralWallpaper/oat/arm/HoloSpiralWallpaper.odex.p
./patch/system/app/HTMLViewer/oat/arm64/HTMLViewer.odex.p
./patch/system/app/KeyChain/oat/arm64/KeyChain.odex.p
./patch/system/app/LatinImeGoogle/oat/arm64/LatinImeGoogle.odex.p
./patch/system/app/Launcher3/Launcher3.apk.p
./patch/system/app/Launcher3/oat/arm64/Launcher3.odex.p
./patch/system/app/LauncherLayout/oat/arm64/LauncherLayout.odex.p
./patch/system/app/LiveWallpapers/oat/arm64/LiveWallpapers.odex.p
./patch/system/app/LiveWallpapersPicker/oat/arm64/LiveWallpapersPicker.odex.p
./patch/system/app/LogKitSdService/oat/arm64/LogKitSdService.odex.p
./patch/system/app/Maps/oat/arm64/Maps.odex.p
./patch/system/app/ModemTestMode/oat/arm64/ModemTestMode.odex.p
./patch/system/app/Music2/oat/arm64/Music2.odex.p
./patch/system/app/NetworkSetting/oat/arm64/NetworkSetting.odex.p
./patch/system/app/NoiseField/oat/arm/NoiseField.odex.p
./patch/system/app/OEMLogKit/oat/arm64/OEMLogKit.odex.p
./patch/system/app/OnePlusWallpapers/oat/arm64/OnePlusWallpapers.odex.p
./patch/system/app/OpenWnn/oat/arm64/OpenWnn.odex.p
./patch/system/app/OpSkin/oat/arm64/OpSkin.odex.p
./patch/system/app/PacProcessor/oat/arm64/PacProcessor.odex.p
./patch/system/app/PartnerBookmarksProvider/oat/arm64/PartnerBookmarksProvider.odex.p
./patch/system/app/PhaseBeam/oat/arm/PhaseBeam.odex.p
./patch/system/app/Photos/oat/arm64/Photos.odex.p
./patch/system/app/PrimaryCardController/oat/arm64/PrimaryCardController.odex.p
./patch/system/app/PrintSpooler/oat/arm64/PrintSpooler.odex.p
./patch/system/app/Protips/oat/arm64/Protips.odex.p
./patch/system/app/QtiTelephonyService/oat/arm64/QtiTelephonyService.odex.p
./patch/system/app/SampleAuthenticatorService/oat/arm64/SampleAuthenticatorService.odex.p
./patch/system/app/SdCardService/oat/arm64/SdCardService.odex.p
./patch/system/app/SensorTestTool/oat/arm64/SensorTestTool.odex.p
./patch/system/app/shutdownlistener/oat/arm64/shutdownlistener.odex.p
./patch/system/app/SimContacts/oat/arm64/SimContacts.odex.p
./patch/system/app/Stk/oat/arm64/Stk.odex.p
./patch/system/app/talkback/oat/arm64/talkback.odex.p
./patch/system/app/TimeService/oat/arm64/TimeService.odex.p
./patch/system/app/UserDictionaryProvider/oat/arm64/UserDictionaryProvider.odex.p
./patch/system/app/Videos/oat/arm/Videos.odex.p
./patch/system/app/WAPPushManager/oat/arm64/WAPPushManager.odex.p
./patch/system/app/WebViewGoogle/oat/arm/WebViewGoogle.odex.p
./patch/system/app/WebViewGoogle/oat/arm64/WebViewGoogle.odex.p
./patch/system/app/WfdService/oat/arm64/WfdService.odex.p
./patch/system/app/YouTube/oat/arm/YouTube.odex.p
./patch/system/app/YouTube/oat/arm64/YouTube.odex.p
./patch/system/bin/factory.p
./patch/system/bin/install-recovery.sh.p
./patch/system/bin/linker.p
./patch/system/bin/linker64.p
./patch/system/bin/mdnsd.p
./patch/system/bin/mediaserver.p
./patch/system/bin/mm-vidc-omx-test.p
./patch/system/bin/toolbox.p
./patch/system/build.prop.p
./patch/system/etc/NOTICE.html.gz.p
./patch/system/etc/recovery-resource.dat.p
./patch/system/etc/security/otacerts.zip.p
./patch/system/framework/am.jar.p
./patch/system/framework/android.test.runner.jar.p
./patch/system/framework/apache-xml.jar.p
./patch/system/framework/appops.jar.p
./patch/system/framework/appwidget.jar.p
./patch/system/framework/arm/boot.art.p
./patch/system/framework/arm/boot.oat.p
./patch/system/framework/arm64/boot.art.p
./patch/system/framework/arm64/boot.oat.p
./patch/system/framework/bmgr.jar.p
./patch/system/framework/bouncycastle.jar.p
./patch/system/framework/bu.jar.p
./patch/system/framework/com.android.future.usb.accessory.jar.p
./patch/system/framework/com.android.location.provider.jar.p
./patch/system/framework/com.android.media.remotedisplay.jar.p
./patch/system/framework/com.android.mediadrm.signer.jar.p
./patch/system/framework/com.google.widevine.software.drm.jar.p
./patch/system/framework/com.qti.location.sdk.jar.p
./patch/system/framework/com.qualcomm.location.vzw_library.jar.p
./patch/system/framework/conscrypt.jar.p
./patch/system/framework/content.jar.p
./patch/system/framework/core-junit.jar.p
./patch/system/framework/core-libart.jar.p
./patch/system/framework/dpm.jar.p
./patch/system/framework/ethernet-service.jar.p
./patch/system/framework/ext.jar.p
./patch/system/framework/framework-res.apk.p
./patch/system/framework/framework.jar.p
./patch/system/framework/hid.jar.p
./patch/system/framework/ime.jar.p
./patch/system/framework/ims-common.jar.p
./patch/system/framework/input.jar.p
./patch/system/framework/javax.obex.jar.p
./patch/system/framework/media_cmd.jar.p
./patch/system/framework/monkey.jar.p
./patch/system/framework/oat/arm/am.odex.p
./patch/system/framework/oat/arm/android.test.runner.odex.p
./patch/system/framework/oat/arm/appops.odex.p
./patch/system/framework/oat/arm/appwidget.odex.p
./patch/system/framework/oat/arm/bmgr.odex.p
./patch/system/framework/oat/arm/bu.odex.p
./patch/system/framework/oat/arm/com.android.future.usb.accessory.odex.p
./patch/system/framework/oat/arm/com.android.location.provider.odex.p
./patch/system/framework/oat/arm/com.android.media.remotedisplay.odex.p
./patch/system/framework/oat/arm/com.android.mediadrm.signer.odex.p
./patch/system/framework/oat/arm/com.google.widevine.software.drm.odex.p
./patch/system/framework/oat/arm/com.qualcomm.location.vzw_library.odex.p
./patch/system/framework/oat/arm/content.odex.p
./patch/system/framework/oat/arm/dpm.odex.p
./patch/system/framework/oat/arm/hid.odex.p
./patch/system/framework/oat/arm/ime.odex.p
./patch/system/framework/oat/arm/input.odex.p
./patch/system/framework/oat/arm/javax.obex.odex.p
./patch/system/framework/oat/arm/media_cmd.odex.p
./patch/system/framework/oat/arm/monkey.odex.p
./patch/system/framework/oat/arm/org.codeaurora.camera.odex.p
./patch/system/framework/oat/arm/pm.odex.p
./patch/system/framework/oat/arm/qcnvitems.odex.p
./patch/system/framework/oat/arm/qcrilhook.odex.p
./patch/system/framework/oat/arm/QPerformance.odex.p
./patch/system/framework/oat/arm/qti-telephony-common.odex.p
./patch/system/framework/oat/arm/QtiTelephonyServicelibrary.odex.p
./patch/system/framework/oat/arm/requestsync.odex.p
./patch/system/framework/oat/arm/settings.odex.p
./patch/system/framework/oat/arm/sm.odex.p
./patch/system/framework/oat/arm/svc.odex.p
./patch/system/framework/oat/arm/telecom.odex.p
./patch/system/framework/oat/arm/uiautomator.odex.p
./patch/system/framework/oat/arm/vcard.odex.p
./patch/system/framework/oat/arm/wm.odex.p
./patch/system/framework/oat/arm64/am.odex.p
./patch/system/framework/oat/arm64/android.test.runner.odex.p
./patch/system/framework/oat/arm64/appops.odex.p
./patch/system/framework/oat/arm64/appwidget.odex.p
./patch/system/framework/oat/arm64/bmgr.odex.p
./patch/system/framework/oat/arm64/bu.odex.p
./patch/system/framework/oat/arm64/com.android.future.usb.accessory.odex.p
./patch/system/framework/oat/arm64/com.android.location.provider.odex.p
./patch/system/framework/oat/arm64/com.android.media.remotedisplay.odex.p
./patch/system/framework/oat/arm64/com.android.mediadrm.signer.odex.p
./patch/system/framework/oat/arm64/com.google.widevine.software.drm.odex.p
./patch/system/framework/oat/arm64/com.qualcomm.location.vzw_library.odex.p
./patch/system/framework/oat/arm64/content.odex.p
./patch/system/framework/oat/arm64/dpm.odex.p
./patch/system/framework/oat/arm64/ethernet-service.odex.p
./patch/system/framework/oat/arm64/hid.odex.p
./patch/system/framework/oat/arm64/ime.odex.p
./patch/system/framework/oat/arm64/input.odex.p
./patch/system/framework/oat/arm64/javax.obex.odex.p
./patch/system/framework/oat/arm64/media_cmd.odex.p
./patch/system/framework/oat/arm64/monkey.odex.p
./patch/system/framework/oat/arm64/org.codeaurora.camera.odex.p
./patch/system/framework/oat/arm64/pm.odex.p
./patch/system/framework/oat/arm64/qcnvitems.odex.p
./patch/system/framework/oat/arm64/qcrilhook.odex.p
./patch/system/framework/oat/arm64/QPerformance.odex.p
./patch/system/framework/oat/arm64/qti-telephony-common.odex.p
./patch/system/framework/oat/arm64/QtiTelephonyServicelibrary.odex.p
./patch/system/framework/oat/arm64/requestsync.odex.p
./patch/system/framework/oat/arm64/services.odex.p
./patch/system/framework/oat/arm64/settings.odex.p
./patch/system/framework/oat/arm64/sm.odex.p
./patch/system/framework/oat/arm64/svc.odex.p
./patch/system/framework/oat/arm64/telecom.odex.p
./patch/system/framework/oat/arm64/uiautomator.odex.p
./patch/system/framework/oat/arm64/vcard.odex.p
./patch/system/framework/oat/arm64/wifi-service.odex.p
./patch/system/framework/oat/arm64/wm.odex.p
./patch/system/framework/okhttp.jar.p
./patch/system/framework/org.apache.http.legacy.boot.jar.p
./patch/system/framework/org.codeaurora.camera.jar.p
./patch/system/framework/oxygen-framework-res.apk.p
./patch/system/framework/pm.jar.p
./patch/system/framework/qcmediaplayer.jar.p
./patch/system/framework/qcnvitems.jar.p
./patch/system/framework/qcom.fmradio.jar.p
./patch/system/framework/qcrilhook.jar.p
./patch/system/framework/QPerformance.jar.p
./patch/system/framework/qti-telephony-common.jar.p
./patch/system/framework/QtiTelephonyServicelibrary.jar.p
./patch/system/framework/requestsync.jar.p
./patch/system/framework/services.jar.p
./patch/system/framework/settings.jar.p
./patch/system/framework/sm.jar.p
./patch/system/framework/svc.jar.p
./patch/system/framework/tcmiface.jar.p
./patch/system/framework/telecom.jar.p
./patch/system/framework/telephony-common.jar.p
./patch/system/framework/uiautomator.jar.p
./patch/system/framework/vcard.jar.p
./patch/system/framework/voip-common.jar.p
./patch/system/framework/WfdCommon.jar.p
./patch/system/framework/wifi-service.jar.p
./patch/system/framework/wm.jar.p
./patch/system/lib/egl/libGLES_android.so.p
./patch/system/lib/hw/audio.a2dp.default.so.p
./patch/system/lib/hw/audio.primary.msm8994.so.p
./patch/system/lib/hw/bluetooth.default.so.p
./patch/system/lib/hw/hwcomposer.msm8994.so.p
./patch/system/lib/libandroid_runtime.so.p
./patch/system/lib/libart-compiler.so.p
./patch/system/lib/libart.so.p
./patch/system/lib/libassert_tip_service.so.p
./patch/system/lib/libaudioflinger.so.p
./patch/system/lib/libaudiopolicymanagerdefault.so.p
./patch/system/lib/libbinder.so.p
./patch/system/lib/libbluetooth_jni.so.p
./patch/system/lib/libc.so.p
./patch/system/lib/libcamera_client.so.p
./patch/system/lib/libcameraservice.so.p
./patch/system/lib/libcompiler_rt.so.p
./patch/system/lib/libcrypto.so.p
./patch/system/lib/libcutils.so.p
./patch/system/lib/libdashplayer.so.p
./patch/system/lib/libft2.so.p
./patch/system/lib/libgui.so.p
./patch/system/lib/libhwui.so.p
./patch/system/lib/libinputservice.so.p
./patch/system/lib/libjavacrypto.so.p
./patch/system/lib/libjhead.so.p
./patch/system/lib/libjpeg.so.p
./patch/system/lib/libm.so.p
./patch/system/lib/libmedia.so.p
./patch/system/lib/libmediaplayerservice.so.p
./patch/system/lib/libOmxVdec.so.p
./patch/system/lib/libOmxVenc.so.p
./patch/system/lib/libpac.so.p
./patch/system/lib/libpixelflinger.so.p
./patch/system/lib/libpng.so.p
./patch/system/lib/libqcmediaplayer.so.p
./patch/system/lib/libskia.so.p
./patch/system/lib/libstagefright.so.p
./patch/system/lib/libstagefright_httplive.so.p
./patch/system/lib/libstagefright_omx.so.p
./patch/system/lib/libstagefright_soft_aacdec.so.p
./patch/system/lib/libstagefright_soft_avcdec.so.p
./patch/system/lib/libstagefright_soft_avcenc.so.p
./patch/system/lib/libstagefright_soft_hevcdec.so.p
./patch/system/lib/libstagefright_soft_mpeg2dec.so.p
./patch/system/lib/libstagefright_soft_vpxdec.so.p
./patch/system/lib/libstagefright_soft_vpxenc.so.p
./patch/system/lib/libsurfaceflinger.so.p
./patch/system/lib/libui.so.p
./patch/system/lib/libunwind.so.p
./patch/system/lib/libvorbisidec.so.p
./patch/system/lib/libwebrtc_audio_preprocessing.so.p
./patch/system/lib/libwifi-service.so.p
./patch/system/lib/libwilhelm.so.p
./patch/system/lib/modules/ansi_cprng.ko.p
./patch/system/lib/modules/core_ctl.ko.p
./patch/system/lib/modules/evbug.ko.p
./patch/system/lib/modules/gpio_axis.ko.p
./patch/system/lib/modules/gpio_event.ko.p
./patch/system/lib/modules/gpio_input.ko.p
./patch/system/lib/modules/gpio_matrix.ko.p
./patch/system/lib/modules/gpio_output.ko.p
./patch/system/lib/modules/gspca_main.ko.p
./patch/system/lib/modules/hcube.ko.p
./patch/system/lib/modules/mcDrvModule.ko.p
./patch/system/lib/modules/mcKernelApi.ko.p
./patch/system/lib/modules/mmc_block_test.ko.p
./patch/system/lib/modules/mmc_test.ko.p
./patch/system/lib/modules/msm-buspm-dev.ko.p
./patch/system/lib/modules/qca_cld/qca_cld_wlan.ko.p
./patch/system/lib/modules/spidev.ko.p
./patch/system/lib/modules/test-iosched.ko.p
./patch/system/lib/modules/ufs_test.ko.p
./patch/system/lib/modules/wil6210.ko.p
./patch/system/lib/soundfx/libqcompostprocbundle.so.p
./patch/system/lib/soundfx/libqcomvoiceprocessing.so.p
./patch/system/lib64/hw/audio.a2dp.default.so.p
./patch/system/lib64/hw/audio.primary.msm8994.so.p
./patch/system/lib64/hw/hwcomposer.msm8994.so.p
./patch/system/lib64/libandroid_runtime.so.p
./patch/system/lib64/libart-compiler.so.p
./patch/system/lib64/libart.so.p
./patch/system/lib64/libassert_tip_service.so.p
./patch/system/lib64/libaudiopolicymanagerdefault.so.p
./patch/system/lib64/libbinder.so.p
./patch/system/lib64/libc.so.p
./patch/system/lib64/libcamera_client.so.p
./patch/system/lib64/libcameraservice.so.p
./patch/system/lib64/libcrypto.so.p
./patch/system/lib64/libcutils.so.p
./patch/system/lib64/libdashplayer.so.p
./patch/system/lib64/libft2.so.p
./patch/system/lib64/libgui.so.p
./patch/system/lib64/libinputservice.so.p
./patch/system/lib64/libjavacrypto.so.p
./patch/system/lib64/libjhead.so.p
./patch/system/lib64/libm.so.p
./patch/system/lib64/libmedia.so.p
./patch/system/lib64/libmediaplayerservice.so.p
./patch/system/lib64/libOmxVdec.so.p
./patch/system/lib64/libOmxVenc.so.p
./patch/system/lib64/libpac.so.p
./patch/system/lib64/libpixelflinger.so.p
./patch/system/lib64/libpng.so.p
./patch/system/lib64/libqcmediaplayer.so.p
./patch/system/lib64/libskia.so.p
./patch/system/lib64/libstagefright.so.p
./patch/system/lib64/libstagefright_httplive.so.p
./patch/system/lib64/libstagefright_omx.so.p
./patch/system/lib64/libstagefright_soft_aacdec.so.p
./patch/system/lib64/libstagefright_soft_avcdec.so.p
./patch/system/lib64/libstagefright_soft_avcenc.so.p
./patch/system/lib64/libstagefright_soft_hevcdec.so.p
./patch/system/lib64/libstagefright_soft_mpeg2dec.so.p
./patch/system/lib64/libstagefright_soft_mpeg4dec.so.p
./patch/system/lib64/libsurfaceflinger.so.p
./patch/system/lib64/libui.so.p
./patch/system/lib64/libvorbisidec.so.p
./patch/system/lib64/libwifi-service.so.p
./patch/system/lib64/libwilhelm.so.p
./patch/system/lib64/soundfx/libqcompostprocbundle.so.p
./patch/system/lib64/soundfx/libqcomvoiceprocessing.so.p
./patch/system/priv-app/BackupRestoreConfirmation/oat/arm64/BackupRestoreConfirmation.odex.p
./patch/system/priv-app/CalendarProvider/oat/arm64/CalendarProvider.odex.p
./patch/system/priv-app/CallLogBackup/oat/arm64/CallLogBackup.odex.p
./patch/system/priv-app/CarrierConfig/oat/arm64/CarrierConfig.odex.p
./patch/system/priv-app/CellBroadcastReceiver/oat/arm64/CellBroadcastReceiver.odex.p
./patch/system/priv-app/CNEService/oat/arm64/CNEService.odex.p
./patch/system/priv-app/com.qualcomm.location/oat/arm64/com.qualcomm.location.odex.p
./patch/system/priv-app/ConfigUpdater/oat/arm64/ConfigUpdater.odex.p
./patch/system/priv-app/Contacts/oat/arm64/Contacts.odex.p
./patch/system/priv-app/ContactsProvider/oat/arm64/ContactsProvider.odex.p
./patch/system/priv-app/DefaultContainerService/oat/arm64/DefaultContainerService.odex.p
./patch/system/priv-app/Dialer/oat/arm64/Dialer.odex.p
./patch/system/priv-app/DownloadProvider/DownloadProvider.apk.p
./patch/system/priv-app/DownloadProvider/oat/arm64/DownloadProvider.odex.p
./patch/system/priv-app/dpmserviceapp/oat/arm64/dpmserviceapp.odex.p
./patch/system/priv-app/ExternalStorageProvider/oat/arm64/ExternalStorageProvider.odex.p
./patch/system/priv-app/FidoCryptoService/oat/arm64/FidoCryptoService.odex.p
./patch/system/priv-app/FusedLocation/oat/arm64/FusedLocation.odex.p
./patch/system/priv-app/GmsCore/oat/arm/GmsCore.odex.p
./patch/system/priv-app/GmsCore/oat/arm64/GmsCore.odex.p
./patch/system/priv-app/GoogleBackupTransport/oat/arm64/GoogleBackupTransport.odex.p
./patch/system/priv-app/GoogleFeedback/oat/arm64/GoogleFeedback.odex.p
./patch/system/priv-app/GoogleLoginService/oat/arm64/GoogleLoginService.odex.p
./patch/system/priv-app/GoogleOneTimeInitializer/oat/arm64/GoogleOneTimeInitializer.odex.p
./patch/system/priv-app/GooglePackageInstaller/oat/arm64/GooglePackageInstaller.odex.p
./patch/system/priv-app/GooglePartnerSetup/oat/arm64/GooglePartnerSetup.odex.p
./patch/system/priv-app/GoogleServicesFramework/oat/arm64/GoogleServicesFramework.odex.p
./patch/system/priv-app/InputDevices/oat/arm64/InputDevices.odex.p
./patch/system/priv-app/ManagedProvisioning/oat/arm64/ManagedProvisioning.odex.p
./patch/system/priv-app/MediaProvider/oat/arm64/MediaProvider.odex.p
./patch/system/priv-app/MmsService/oat/arm64/MmsService.odex.p
./patch/system/priv-app/OnePlusCamera/oat/arm64/OnePlusCamera.odex.p
./patch/system/priv-app/OnePlusCameraService/oat/arm64/OnePlusCameraService.odex.p
./patch/system/priv-app/OnePlusOta/OnePlusOta.apk.p
./patch/system/priv-app/OnePlusWizard/oat/arm64/OnePlusWizard.odex.p
./patch/system/priv-app/OPDeviceManager/oat/arm64/OPDeviceManager.odex.p
./patch/system/priv-app/OPDeviceManagerProvider/oat/arm64/OPDeviceManagerProvider.odex.p
./patch/system/priv-app/Phonesky/oat/arm64/Phonesky.odex.p
./patch/system/priv-app/ProxyHandler/oat/arm64/ProxyHandler.odex.p
./patch/system/priv-app/qcrilmsgtunnel/oat/arm64/qcrilmsgtunnel.odex.p
./patch/system/priv-app/QtiTetherService/oat/arm64/QtiTetherService.odex.p
./patch/system/priv-app/SecureSampleAuthService/oat/arm64/SecureSampleAuthService.odex.p
./patch/system/priv-app/Settings/oat/arm64/Settings.odex.p
./patch/system/priv-app/Settings/Settings.apk.p
./patch/system/priv-app/SettingsProvider/oat/arm64/SettingsProvider.odex.p
./patch/system/priv-app/SetupWizard/oat/arm64/SetupWizard.odex.p
./patch/system/priv-app/SharedStorageBackup/oat/arm64/SharedStorageBackup.odex.p
./patch/system/priv-app/Shell/oat/arm64/Shell.odex.p
./patch/system/priv-app/Shell/Shell.apk.p
./patch/system/priv-app/StatementService/oat/arm64/StatementService.odex.p
./patch/system/priv-app/SystemUI/oat/arm64/SystemUI.odex.p
./patch/system/priv-app/SystemUI/SystemUI.apk.p
./patch/system/priv-app/Telecom/oat/arm64/Telecom.odex.p
./patch/system/priv-app/TelephonyProvider/oat/arm64/TelephonyProvider.odex.p
./patch/system/priv-app/TeleService/oat/arm64/TeleService.odex.p
./patch/system/priv-app/Velvet/oat/arm64/Velvet.odex.p
./patch/system/priv-app/VpnDialogs/oat/arm64/VpnDialogs.odex.p
./patch/system/priv-app/WallpaperCropper/oat/arm64/WallpaperCropper.odex.p
./patch/system/vendor/app/ims/oat/arm64/ims.odex.p
./patch/system/vendor/app/imssettings/oat/arm64/imssettings.odex.p
./patch/system/vendor/lib/libavenhancements.so.p
./patch/system/vendor/lib/libextendedremotedisplay.so.p
./patch/system/vendor/lib/libmmcamera_imglib.so.p
./patch/system/vendor/lib/libmmipstreamaal.so.p
./patch/system/vendor/lib/libwfdmmsrc.so.p
./patch/system/vendor/lib/mediadrm/libwvdrmengine.so.p
./patch/system/vendor/lib64/libavenhancements.so.p
./patch/system/vendor/lib64/libextendedremotedisplay.so.p
./patch/system/vendor/lib64/libmmipstreamaal.so.p
./patch/system/vendor/lib64/libwfdmmsrc.so.p
./system/recovery-from-boot.p
We've begun rolling out OxygenOS 3.1.0 for the OnePlus 2 today. Here's what's new in this update:
Fixed some notification issues
Improved Doze Mode performance
Added media sound toggle for alert slider
Addressed alert slider/silent mode issue
Implemented August 1 security patches for Android
Implemented Quadrooter patch
General bug fixes
This rollout will be incremental. We will do our best to get everyone covered as quickly as possible. Please give us your thoughts and feedback in the comments below!
Thanks [IMG]
hackworks said:
The update is by no means small.
Click to expand...
Click to collapse
Some fixes and not fixes that I 've noticed so far on 3.1.0, comparing it to 3.0.2 ...
Fixed
* Do not Disturb can now be scheduled via a 3rd app (eg Tasker)
* NET location is now available on Tasker doesn't work, it was probably cached
* GPS icon now appears on the status bar when using Sygic, it did not on 3.0.2 yet gps was available.
Not Fixed
* Recents does not always show the last running app, sometimes it does, sometimes it doesn't
To be seen ...
* GPS drops after 20 minutes or so when using Sygic, it is consistent, I 'll find out about that tomorrow.
Clean flashed 3.0.2, flashed 3.1.0 update and factory reseted immediately.
No SuperSu/Xposed/Mods for now until I get a better picture of stock behavior.
thdervenis said:
To be seen ...
* GPS drops after 20 minutes or so when using Sygic, it is consistent, I 'll find out about that tomorrow.
Click to expand...
Click to collapse
Not only sygic I face the same problem on any GPS app (maps as example).
And not really after 20 minutesn but sometime 10 minutes and some other time 50 minutes. I have to disable and enable back GPS to fix it for few more minutes.
Riichard63 said:
Not only sygic I face the same problem on any GPS app (maps as example).
And not really after 20 minutesn but sometime 10 minutes and some other time 50 minutes. I have to disable and enable back GPS to fix it for few more minutes.
Click to expand...
Click to collapse
This is exactly the problem that I have, I got to close GPS and reopen it (or Sygic), in order to get it working again.
I haven't use GPS for over 50 mins, not at least since the release OOS 3.0.2. And yes, a couple of times GPS dropped in about 10 mins.
I 've seen it also occuring on Google Maps but I thought I shouldn't mention it because I rarely use it and don't have a solid opinion.
What I can say is it doesn't occur on OOS 2.2.1, no matter what.
Let's hope that the GPS icon that now appears on the statusbar is more than a UI fix and has some substance. More on that tomorrow when I' ll use GPS to and from work.
I 've also oppened an issue with Sygic about 3 weeks ago but I have no reply yet ...
vonotny said:
Same problem here! (TWRP 3) First got a build.prop error message, reverted build.prop back to stock, error went away but error 7 was still there.
I'm on Boeffla Kernel + Super SU + Xposed, could any of those have anything to do with it?
Click to expand...
Click to collapse
Same problem here, any ideas yet?
Anyone has had luck getting the Pixel Experience ROM working?
Site can be found here:
https://download.pixelexperience.org/j9110
I am on 8170 and would like to test it out.
Really interested in your feedbacks!
How do we flash it without a working twrp?
https://wiki.pixelexperience.org/devices/j9110/install/
Follow these instructions it should work....
chaitanya.krishna said:
Follow these instructions it should work....
Click to expand...
Click to collapse
...
TrustAugustus said:
How do we flash it without a working twrp?
Click to expand...
Click to collapse
Instructions do not Help if there is no way to follow them. Just use GSIs... There is also a Pixel Expierence One around...
joeminati said:
Anyone has had luck getting the Pixel Experience ROM working?
Site can be found here:
https://download.pixelexperience.org/j9110
I am on 8170 and would like to test it out.
Click to expand...
Click to collapse
I tried the June and July builds on my Dual SIM J9110. They are constantly improving so some things that I mention below may have changed. The SODP guys working on it are awesome.
The builds worked well for the most part, performance is not quite as good as stock, there are some stutters and frame drops, but it's still daily driver material.
Some things to keep in mind:
-There is no Dolby Audio. Volume from the speakers is slightly lower than stock.
-The display runs in always 4K mode, it looks great. Doesn't have a huge effect on battery life either.
-The notification LED only displays one colour, which is sort of a bluey-white.
-You have to use Raizen's HyperCam build for photos. A little bit of tweaking within the app and it takes fantastic photos. Supports all 3 cameras as well.
-It will not have any proprietary Sony features like Battery Care.
For flashing you have to use Payload_Dumper on the payload.bin file included within the ROM zip. It will give you dtbo.img, boot.img, system.img, vendor.img and so on.
First make sure you're on the latest Android 10 (55.1.x) firmware on both A and B slots. You can use NewFlasher to flash, and fastboot to switch between slots.
Then flash the latest Sony Open Device Binaries for Kumano (Xperia 1 / Xperia 5) which you can get from here:
https://developer.sony.com/file/dow...-aosp-android-10-0-kernel-4-14-kumano-latest/
Then flash dtbo, boot and vendor. Then boot into AOSP recovery with Power + Vol down. From there you can use adb sideload to install the ROM .zip file and your phone will reboot into PE.
If it bootloops, run fastboot format userdata or boot back into AOSP recovery and do a factory reset.
For updates, it does support OTAs since the device is officially supported by PE and hosted on their servers.
@MeltdownSpectre
Thanks for the info! I'm definitely going to try it.
Would you mind pointing me to the exact hypercam raizen file
TrustAugustus said:
@MeltdownSpectre
Thanks for the info! I'm definitely going to try it.
Would you mind pointing me to the exact hypercam raizen file
Click to expand...
Click to collapse
Here you go:
https://f.celsoazevedo.com/file/cfiles/gcm1/HyperCam-RaizenA-10.apk
MeltdownSpectre said:
Here you go:
https://f.celsoazevedo.com/file/cfiles/gcm1/HyperCam-RaizenA-10.apk
Click to expand...
Click to collapse
Thanks! It doesn't work with stock Sony. Is that normal?
I realized that the ROM is for the DSDS. I have the 802SO version. I wonder if I'll end up borking the phone.
TrustAugustus said:
Thanks! It doesn't work with stock Sony. Is that normal?
I realized that the ROM is for the DSDS. I have the 802SO version. I wonder if I'll end up borking the phone.
Click to expand...
Click to collapse
Not sure if 802SO is supported.
Yes it's normal for it to not work with stock ROM.
MeltdownSpectre said:
I tried the June and July builds on my Dual SIM J9110. They are constantly improving so some things that I mention below may have changed. The SODP guys working on it are awesome.
The builds worked well for the most part, performance is not quite as good as stock, there are some stutters and frame drops, but it's still daily driver material.
Some things to keep in mind:
-There is no Dolby Audio. Volume from the speakers is slightly lower than stock.
-The display runs in always 4K mode, it looks great. Doesn't have a huge effect on battery life either.
-The notification LED only displays one colour, which is sort of a bluey-white.
-You have to use Raizen's HyperCam build for photos. A little bit of tweaking within the app and it takes fantastic photos. Supports all 3 cameras as well.
-It will not have any proprietary Sony features like Battery Care.
For flashing you have to use Payload_Dumper on the payload.bin file included within the ROM zip. It will give you dtbo.img, boot.img, system.img, vendor.img and so on.
First make sure you're on the latest Android 10 (55.1.x) firmware on both A and B slots. You can use NewFlasher to flash, and fastboot to switch between slots.
Then flash the latest Sony Open Device Binaries for Kumano (Xperia 1 / Xperia 5) which you can get from here:
https://developer.sony.com/file/dow...-aosp-android-10-0-kernel-4-14-kumano-latest/
Then flash dtbo, boot and vendor. Then boot into AOSP recovery with Power + Vol down. From there you can use adb sideload to install the ROM .zip file and your phone will reboot into PE.
If it bootloops, run fastboot format userdata or boot back into AOSP recovery and do a factory reset.
For updates, it does support OTAs since the device is officially supported by PE and hosted on their servers.
Click to expand...
Click to collapse
Thanks for Your Post! Is there any reason for flashing the ZIP again after flashing it already via Fastboot? Sounds more Like a Option for coming Updates (I hope update.zip Files Work from the Storage too?). Great to have at least a stable Recovery Base!
Miustone said:
Thanks for Your Post! Is there any reason for flashing the ZIP again after flashing it already via Fastboot? Sounds more Like a Option for coming Updates (I hope update.zip Files Work from the Storage too?). Great to have at least a stable Recovery Base!
Click to expand...
Click to collapse
The developers had given me these flashing instructions. We only flash dtbo, boot and vendor first. Then sideloading the zip flashes them again, as well as flashing system.img which was not flashed through fastboot.
I'm using this build now, everything works fine. But the animation seems not very smooth,a little lag
Xperia 1 - J8110, J8170, J9110, 802SO, SO-03L, SOV40
what variant support by PE rom?
JOKER.SOHA said:
Xperia 1 - J8110, J8170, J9110, 802SO, SO-03L, SOV40
what variant support by PE rom?
Click to expand...
Click to collapse
PE supports J8110 (single SIM) and J9110 (dual SIM).
i have no mobile data.
no SIM detected.
i have no mobile data.
no SIM detected.
the camera is very poor, almost cannot use, even scan a qrcode is difficult
Sketch. said:
I'm using this build now, everything works fine. But the animation seems not very smooth,a little lag
Click to expand...
Click to collapse
camera is not function as better as the stock one
AOSP 13
This is a moto-common project release under the codename borneo
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
What's Moto-Common?
Moto-Common is a set of trees common to every 4.14+ QCOM Motorola device, making it easier to do bringups based on SODP.
What's AOSP?
AOSP is Android as Google publish without other modifications.
Known issues:
You tell me
IF YOU DONT HAVE SLOT B FILLED YOU CAN BRICK
Instructions :
Download the latest build
Reboot to bootloader
Code:
fastboot -w
Code:
fastboot update PACKAGE.zip
You may need to install drivers in device manager after running the last command
Downloads :
Download
Telegram Groups
My chat
Source Code:
https://github.com/moto-common
Changelog:
Jan 25th 2023: Initial release on XDA
Feb 27th 2023: Pushed Feb update
June 19th 2023: Pushed June patch update
Fix fingerprint gestures for egis
Fix color mode listings
Fix aux cameras
Improve memory management
Improve Wi-Fi 5GHz strength
Numerous other changes
Hi I recently installed this as its the only ROM currently available for my phone that I've seen, and I'm just wondering how would someone go about installing gapps?
DefinitelyDetermined said:
Hi I recently installed this as its the only ROM currently available for my phone that I've seen, and I'm just wondering how would someone go about installing gapps?
Click to expand...
Click to collapse
I have no idea , I just build to provide a base for others to work off of mostly.
DefinitelyDetermined said:
Hi I recently installed this as its the only ROM currently available for my phone that I've seen, and I'm just wondering how would someone go about installing gapps?
Click to expand...
Click to collapse
@Electimon
See the following links:
- https://stackoverflow.com/questions/71001696/how-to-include-opengapps-in-aosp-12-build
Use tau instead of sigma for aosp-13 (in the notes at bottom checked answer)\
- https://github.com/opengapps/aosp_build
- https://www.droidwin.com/how-to-download-and-install-android-13-gapps/
Note: Requires a working TWRP
Does this rom bring unlimited google photos???
sdembiske said:
@Electimon
See the following links:
- https://stackoverflow.com/questions/71001696/how-to-include-opengapps-in-aosp-12-build
Use tau instead of sigma for aosp-13 (in the notes at bottom checked answer)\
- https://github.com/opengapps/aosp_build
- https://www.droidwin.com/how-to-download-and-install-android-13-gapps/
Note: Requires a working TWRP
Click to expand...
Click to collapse
Would an outdated twrp version work? There is an unofficial one for Android 11
@Electimon Do you know anything about "range restricted" in Firehose loaders for EDL?
It prevents you from reading (and probably writing?) most partitions in EDL.
If your CID is 0xff or if you have a flag set (which I haven't traced down yet) you can bypass the restriction.
Renate said:
@Electimon Do you know anything about "range restricted" in Firehose loaders for EDL?
It prevents you from reading (and probably writing?) most partitions in EDL.
If your CID is 0xff or if you have a flag set (which I haven't traced down yet) you can bypass the restriction.
Click to expand...
Click to collapse
Yeah thats known, sadly CID partition is signed and the flag is usually burned qfuse in the SoC which is burnt on all retail devices.
Electimon said:
... the flag is usually burned qfuse ...
Click to expand...
Click to collapse
I'm using the Firehose loader size=609,484, MD5=153a904c54963cb21b901b0dd10f0641
I can see that the CID is validated by cert chains.
But I also see lots of stuff like "ssm_flash_cid", "write_cid_store".
I see a bunch of smc (Secure Monitor Calls) and a bunch of SCM (Secure Channel Monitor) calls and functions for reading/writing fuses.
I also see one small function that writes a byte into memory that can disable restrictions.
It seems like a back door, but I haven't seen what activates it.
Would it be possible to use this device tree to make a pixel experience port?
LethalGamer2121 said:
Would it be possible to use this device tree to make a pixel experience port?
Click to expand...
Click to collapse
Yes
Feb 27th 2023: Pushed Feb update
Electimon said:
Feb 27th 2023: Pushed Feb update
Click to expand...
Click to collapse
sound isnt working after update. it started working after i downgraded to the jan release
DefinitelyDetermined said:
sound isnt working after update. it started working after i downgraded to the jan release
Click to expand...
Click to collapse
Thank you for letting me know, it will be fixed soon
DefinitelyDetermined said:
sound isnt working after update. it started working after i downgraded to the jan release
Click to expand...
Click to collapse
Please redownload the same link, ive updated it with the fixed package. Thank you
having an issue where I cant flash it, its saying that it cannot flash
>fastboot update aosp_borneo-img-Feb-Week4.zip-------------------------------- - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com
if you want to reach out to me quickly, DM me on discord, Merith#5829
merith-tk said:
having an issue where I cant flash it, its saying that it cannot flash
>fastboot update aosp_borneo-img-Feb-Week4.zip-------------------------------- - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com
if you want to reach out to me quickly, DM me on discord, Merith#5829
Click to expand...
Click to collapse
Use platform-tools r32, in the latest version google broke fastboot update.
Electimon said:
Use platform-tools r32, in the latest version google broke fastboot update.
Click to expand...
Click to collapse
Small problem, phone has fastbootd, bootloader, recovery, and system (system being rom)
when you tell the phone to boot to fastboot, it goes to fastbootd which does not show up in fastboot.exe's list,
but if I send it to bootloader, it shows up
Edit, Updating drivers fixed it, IOBit Driver notified of out of date driver
Electimon said:
Use platform-tools r32, in the latest version google broke fastboot update.
Click to expand...
Click to collapse
Still broken, just differently
It flashed, rebooted, showed the AOSP android boot animation, rebooted then brought me to stock recovery (TWRP not flashed) saying the system was corrupt and could not boot
Reflashing fixed it but I dont have Cell Service (I have an carrier unlocked device on USC network)
merith-tk said:
Still broken, just differently
It flashed, rebooted, showed the AOSP android boot animation, rebooted then brought me to stock recovery (TWRP not flashed) saying the system was corrupt and could not boot
Reflashing fixed it but I dont have Cell Service (I have an carrier unlocked device on USC network)
Click to expand...
Click to collapse
Wipe data in recovery and let me know if its still an issue
I have a Lenovo Moto Z (XT1650-05, sheridan model). According to fastboot, it's in securestate: flashing_unlocked.
I tested flashing TWRP 3.3.1-0 into the recovery partition and it worked, but I can only start TWRP once it's flashed
and I haven't rebooted the phone.
Now the question I have is, can I flash griffin ROMS into it? I see many different ROMS here at XDA, but they seem
all to be for griffin.
At https://wiki.lineageos.org/devices/griffin/ the page also mentions the code for sheridan, XT1650-05
Supported models:
XT1650-03
XT1650-05
so I'm hoping if someone could tell me if it's possible or not.
Thanks,
Aki
Edit: now that I tried to download the installation package from URL https://download.lineageos.org/devices/griffin, I get this error "This device does not exist"
I updated my XT1650-05 with the files:
lineage-19.1-20230218-UNOFFICIAL-griffin.zip
MindTheGapps-12.1.0-arm64-20220605_112439.zip
and
twrp-3.3.1-0-griffin.img for the recovery and it worked! I'm a happy guy now.
Edit: also Magisk install succeeded but it was a bit complex.
me too
nice to hear people like using what I did
I couldn't make Magisk hide itself from my banking app so I reflashed the phone again without it.
SirRGB said:
me too
nice to hear people like using what I did
Click to expand...
Click to collapse
@SirRGB I have a curious problem with your ROM. If I set the preferred network type to LTE only,
I can't make or receive phone calls. But if I set it to LTE/WCDMA, the phone calls work fine.
My SIM should support VOLTE.
Is there some fix for this issue?
Best regards,
Aki
Well I personally dont use it as daily driver, so I didnt check volte. Im sorry if it doesnt work and will look into it, but no promises made. You can however check the 18.1 (A11) builds of Nolen, whose builds will soon be official. They are also a little better security wise since those builds contain enforcing sepolicy and ecnryption. Note that gapps are included.
Odd Solutions Downloads
updater.oddsolutions.us
@SirRGB Unfortunately the phone doesn't allow me to use LTE-only as the preferred network mode with that 18.1 build by Nolen either. The call hangs up immediately. I contacted my network operator if they can see if there's something wrong. Thanks for helping out
P.S. Finland is getting rid of the 3G cell towers at the end of this year
Thats odd, I didnt expect it to be dead in older versions as well. Can you send logs? (Matlog is the easiest way if you arent familiar with adb)
I've used adb shell quite often but if you have some instructions on what to run I'd be grateful.
> I contacted my network operator if they can see if there's something wrong.
The cell operator said that my SIM has VOLTE and it should work all right.