Database Users

[CWM] [Flashable] [Only for Aurora 4.1a] Updated init.d support

I'm sorry to have to open another thread just for this, but I was waiting for zephyr1988 to update his files for aurora 4.1a. As he didn't do it yet, here it is
I had posted these in the other thread, but the files are now outdated and there was some confusion regarding the kernel inside the zip. These files, fix this, because I updated the kernel and services.jar for Aurora 4.1a.
Please, to understand what this does, read this thread:
http://forum.xda-developers.com/showthread.php?t=1710233
Notes:
- This is only for those with Aurora 4.1 + 4.1a update. For other versions, there will be auto-reboots, especially with the gallery, so, if don't have the latest aurora version, don't install this.
To install, flash both zips in recovery. Boot takes a little longer, but believe it, it's worth it
MIRROR

Thanks, fjsferreira! You're incredibly helpful all the time.

I get this error when i try to download.
404 - Not Found

greddyrx7 said:
I get this error when i try to download.
404 - Not Found
Click to expand...
Click to collapse
Yes, I get that too, looks like a problem with xda. Here is an alternate download. Extract the two zip files first
http://www.mediafire.com/?ifhpwtzmtevv1fl

Sorry if this question was already answered.
What are the changes in the boot.img?
dzo already added support to run init.d scripts already in kernel of the versions 4.1+, correct?
Why you need to add it to your zip?
Another question, what does the OOM_Priority_Charger_Aurora_4.1a.zip?

Couldn't flash OOM_Priority_Charger_Aurora_4.1a.zip through recovery, says installation aborted..
In on update 4.1a
Sent from my U8800

sr21 said:
Sorry if this question was already answered.
What are the changes in the boot.img?
dzo already added support to run init.d scripts already in kernel of the versions 4.1+, correct?
Why you need to add it to your zip?
Another question, what does the OOM_Priority_Charger_Aurora_4.1a.zip?
Click to expand...
Click to collapse
It's the same one that's in update 4.1a, I kept it because there was a boot.img in the original script, I don't know if removing it would lead to the script not working...

demolition23 said:
Couldn't flash OOM_Priority_Charger_Aurora_4.1a.zip through recovery, says installation aborted..
In on update 4.1a
Sent from my U8800
Click to expand...
Click to collapse
It's working here, I tried it again just now... what CWM are you using? You can also just extract the services.jar that's inside the zip, and copy it to /system/framework, replace the default and set permissions like the default and reboot.

fjsferreira said:
It's working here, I tried it again just now... what CWM are you using? You can also just extract the services.jar that's inside the zip, and copy it to /system/framework, replace the default and set permissions like the default and reboot.
Click to expand...
Click to collapse
I tried with 5.5.0.4 and then with 5.8.4.5.
i will redownload and try again..
EDIT
Same again...Will try manually. Thanks anyway!

Priority charger in attached files didn't work but files from Mediafire did.

fjsferreira said:
It's the same one that's in update 4.1a, I kept it because there was a boot.img in the original script, I don't know if removing it would lead to the script not working...
Click to expand...
Click to collapse
If I already have the 4.1 or 4.1a installed I already have the boot.img in my phone and It already have the support for init.d. So I think you do not need to add it to your zip.
That is creating problems only.
This is just a comment to improve your work and correct me if I'm wrong. I'll appreciate.

sr21 said:
If I already have the 4.1 or 4.1a installed I already have the boot.img in my phone and It already have the support for init.d. So I think you do not need to add it to your zip.
That is creating problems only.
This is just a comment to improve your work and correct me if I'm wrong. I'll appreciate.
Click to expand...
Click to collapse
It doesn't create any problem at all, because I didn't modify the 4.1a kernel in any way, it's the same that it's in dzo's 4.1aupdate zip.
On the other hand, removing it could cause problems with the updater script in this flashable zip, that's why I kept it in my flashable zip. You are not forced to install this zip if you don't want, but I can guarantee the boot.img is the same that's in dzo update, there's nothing bad coming from flashing it.

fjsferreira said:
It doesn't create any problem at all, because I didn't modify the 4.1a kernel in any way, it's the same that it's in dzo's 4.1aupdate zip.
On the other hand, removing it could cause problems with the updater script in this flashable zip, that's why I kept it in my flashable zip. You are not forced to install this zip if you don't want, but I can guarantee the boot.img is the same that's in dzo update, there's nothing bad coming from flashing it.
Click to expand...
Click to collapse
Hello fjsferreira,
Thanks for updating the zip, I was away for a week with no access to a PC.
I have updated the original thread with 4.1a OOM priority charger and a init.d zip that does not mess with the boot.img now that dzo has included it in his ROM, so it should be compatible with newer versions.

I ve read the threads but still dont know what is OOM priority charger or any charger and init.d . Can someone explain it to m?
Sent from my U8800 using xda app-developers app

bassdrum01 said:
I ve read the threads but still dont know what is OOM priority charger or any charger and init.d . Can someone explain it to m?
Sent from my U8800 using xda app-developers app
Click to expand...
Click to collapse
These are scripts that run at boot time to change memory management so that you always have a good amount of memory available. The package also contains some scripts to fine tune screen sensitivity, sdcard and CPU performance, those require editing the script files to uncomment some lines. Read the instructions on the other thread to fine out how to use this.
Sent from my U8800

[Q] set_metadata_recursive: some changes failed

HI! I'm building Android 4.4 but when I try to flash the ROM via TWRP, I get the following error:
minzip: Extracted 1226 file(s)
ApplyParsedPerms: removexattr of /system/addon.d/50-hosts.sh to 0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/external_sd/box/i9305/omni-4.4-20131107-i9305-HOMEMADE.zip'
Error flashing zip '/external_sd/box/i9305/omni-4.4-20131107-i9305-HOMEMADE.zip'
Any advice on what is needed to fix this fault is appreciated!
Is the recovery.img produced during ROM build flashable? It is 2MB smaller than the TWRP recovery image.

Hey, so I went through this yesterday (see the Q & A section) and while I didn't resolve it completely, I know that it's because of selinux, and you need a newer version of TWRP. Right now in the Omni 4.4 manifest it actually has the AOSP recovery so you'll wanna change that to Omni 's TWRP on a local manifest. Beyond that it depends on your BoardConfig.mk whether your recovery is flash able, if you configured it ok then yes!
Check the links Entropy512 posted in this thread for more on TWRP configuration: http://forum.xda-developers.com/showthread.php?t=2499514
In particular make sure you have a proper fstab in v1 format (see my last post in that thread for more details as well). My recovery built after I fixed the twrp.fstab at least looks and acts like a proper recovery, but haven't done anything with it yet for lack of time.

The reason for that message can be in the kernel configuration.
If those options are not set, this will cause this message:
Code:
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
if using Ext3:
Code:
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
if using Ext4:
Code:
CONFIG_EXT4_FS=y
CONFIG_EXT4_FS_XATTR=y
CONFIG_EXT4_FS_POSIX_ACL=y
CONFIG_EXT4_FS_SECURITY=y
regards Uwe

I used for fix that ROM Manager app from Play Store and update to the latest CWM recovery. DO NOT USE TWRP!!! Just update that.

u.k-f said:
The reason for that message can be in the kernel configuration.
If those options are not set, this will cause this message:
Code:
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
if using Ext3:
Code:
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
if using Ext4:
Code:
CONFIG_EXT4_FS=y
CONFIG_EXT4_FS_XATTR=y
CONFIG_EXT4_FS_POSIX_ACL=y
CONFIG_EXT4_FS_SECURITY=y
regards Uwe
Click to expand...
Click to collapse
Thanks.. I have all those set for Ext4 (the only FS used) and still no luck ....

mcampbellsmith said:
Thanks.. I have all those set for Ext4 (the only FS used) and still no luck ....
Click to expand...
Click to collapse
Did you enable SELINUX in the kernel used for recovery?
The xattributes to be written are SELINUX Attributes...
Regards Uwe

u.k-f said:
Did you enable SELINUX in the kernel used for recovery?
The xattributes to be written are SELINUX Attributes...
Regards Uwe
Click to expand...
Click to collapse
Thanks for your help everyone.
Recompiled TWRP and it works.
CWM also works when updated.
Cheers!

It is weird. I have compiled TWRP in the omni tree. The kernel config does contain the selinux settings:
if using Ext3:
Code:
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
if using Ext4:
Code:
CONFIG_EXT4_FS=y
CONFIG_EXT4_FS_XATTR=y
CONFIG_EXT4_FS_POSIX_ACL=y
CONFIG_EXT4_FS_SECURITY=y
But i am still getting the set_metadata_recursive stuff. Do i have to include HAVE_SELINUX ? I thought that was for android versions <4.3
I did a clean / clobber before building, but i added also a kernel command to make selinux permissive
Do i have to cherrypick something to make it work?
EDIT:
Hmm somehow the new recovery image is not flashed ?

With the change from Android 4.2 to Android 4.3 I needed to enable SELINUX in the Kernel-Config.
Did you do this?
And, by the way, you do not need to install your new recovery, you can start ist from bootloader with
Code:
fastboot boot recovery.img
without installing it any time you build a new version
regards uwe

u.k-f said:
With the change from Android 4.2 to Android 4.3 I needed to enable SELINUX in the Kernel-Config.
Did you do this?
And, by the way, you do not need to install your new recovery, you can start ist from bootloader with
Code:
fastboot boot recovery.img
without installing it any time you build a new version
regards uwe
Click to expand...
Click to collapse
I fixed the problem. It was because of the fact that the image was bigger then the partition size. Using another kernel compression solved it.
Sent from my Xperia T using Tapatalk

mcampbellsmith said:
Thanks for your help everyone.
Recompiled TWRP and it works.
CWM also works when updated.
Cheers!
Click to expand...
Click to collapse
Can you explain what you changed in the CWM tree to successfully flash 4.4?

scanno said:
I fixed the problem. It was because of the fact that the image was bigger then the partition size. Using another kernel compression solved it.
Sent from my Xperia T using Tapatalk
Click to expand...
Click to collapse
hi
please explain all fix do, others dev have solution and clue...
we have to leave answer for duture and actual dev
thank you very much

lordtillt said:
Can you explain what you changed in the CWM tree to successfully flash 4.4?
Click to expand...
Click to collapse
Nothing.
The latest version of CWM that was available from the website was quite old. Recompiling it with latest sources worked fine.

desalesouche said:
hi
please explain all fix do, others dev have solution and clue...
we have to leave answer for duture and actual dev
thank you very much
Click to expand...
Click to collapse
My changes were for the TF300T. The commits are on gerrit. You can see the TWRP configuration and the changes needed in the kernel.
Sent from my Xperia T using Tapatalk

scanno said:
My changes were for the TF300T. The commits are on gerrit. You can see the TWRP configuration and the changes needed in the kernel.
Sent from my Xperia T using Tapatalk
Click to expand...
Click to collapse
can you send a link please?...thank you...

In short, if you want to flash KitKat Android 4.4, you'll have to upgrade to a version of CWM greater than v6.0.4.5. Or, use an alternate bootloader.

Try out another recovery.
I got this pb with phil touch, then I try it on TWRP and the ROM is now installed correctly : )

[Q] czechop CM10.2 com.phone app error.

I meet a problem when changing from Engle_Mars CM10.2 to czechop CM10.2, described below:
- My Install Trace Before Install czechop CM10.2:
Moto Official SBF -> Start OS and Root -> Install BootMenu 1.0.5 and reboot -> Flash BootMenu 1.1.0 with CWM 5.0.3.4 -> Flash tezet_CM10_20121228, directly reboot to recovery. -> Flash Engle_Mars_CM10.2_2013_1030.
Here, Engle_Mars_CM10.2_2013_1030 working correctly.
- Then I want to change to czechop CM10.2 to have a try, So I did following:
Reboot to recovery -> Backup Engle_Mars CM10.2 -> Dual Wipe -> Reboot to BootMenu, Format partitions to EXT4. -> Go into TeamWin Recovery, Flash czechop CM10.2, rev 2013.10.31 -> Dual Wipe again -> Reboot to normal boot.
After system starts, the application something like com.phone.*** always have error and terminated by OS. The error loops.
Could you have some suggestions?
@czechop I found that it seems in your CM10.2 package, baseband is defy's? If this cause the problem, could be fixed?
Thank you.
Ps. Could anyone point out how to generate a flashable zip file? I tried some, but failed. Thx a lot.

dr2001 said:
After system starts, the application something like com.phone.*** always have error and terminated by OS. The error loops.
Click to expand...
Click to collapse
I had something like that (phone app crashing) once when I reverted from Czechop's 10.30 version to 10.23 without wiping data. Please try to do full wipe from TRWP (cache, Dalvik, data, system - found in Advanced Wipe, you don't need to wipe sd-card), then install Czechop's latest zip, reboot. It should be fine.
---------- Post added at 05:19 AM ---------- Previous post was at 05:02 AM ----------
dr2001 said:
Could anyone point out how to generate a flashable zip file? I tried some, but failed. Thx a lot.
Click to expand...
Click to collapse
Maybe my way isn't so "professional", but I was in need of creating a flashable zip with keyboard layouts. What I did, was I took some other flashable zip, inside left my files (/system/usr/*) and some control directory, and now it can be flashed. Only thing is it displays some old info during flash, but it's ok for me, and I didn't have time to find out where in that control files this info is found.
I attach my small flashable zip - you can simply modify it, put your files inside, and it should work.

the zip won't work, if you don't change the file names and paths in the updater script (except you want to flash exactly that keylayout files)
edit: opend your attached file, and theres no updater script at all. so this file won't work as a flashable zip. you can just put the files by a root explorer into your system.

lulli1 said:
opend your attached file, and theres no updater script at all. so this file won't work as a flashable zip. you can just put the files by a root explorer into your system.
Click to expand...
Click to collapse
Funny. I understand you wanted to say "it shouldn't work because it doesn't follow standards", but luckily for me it works. I haven't read about these files structure. I just did the simpliest thing: opened zip, deleted files inside, and put what I wanted. Maybe it's some kind of lamer's luck, but my file definitely can be flashed with TRWP (I've just checked it another time).
Regards!
[EDIT]
I apologize. I was too dumb to have noticed I attached a zip file without update script, which definitely couldn't work, but instead of checking, I claimed it is OK. I feel like a moron. I attach a better version of file.

czechop's CM10.2 version
how can I find @czechop 's CM10.2 version?
in his article ：http://forum.xda-developers.com/showthread.php?t=2517735
he said "Install my CM10.2 version >= 07.11.2013 first"

help with porting validus rom

hi, i followed this guide ( https://forum.xda-developers.com/android/software-hacking/guide-port-nougat-roms-snapdragon-t3552897 ) to port validus rom from redmi note 4 (same chipset) but everytime i get error 7 in twrp:
...
patching system image unconditionally...
E1001: failed to update system image.
updater process ended with ERROR: 7
anyone can help me?
the rom is uploading to google drive. tomorrow i put link in this thread
rom link: https://drive.google.com/open?id=0ByWXQMKmKF0-NWplWlM5Z04xQzQ

Edit the updater-script by removing everything before the "ui_print" line.

wang1chung said:
Edit the updater-script by removing everything before the "ui_print" line.
Click to expand...
Click to collapse
i do it but same error, i uploaded my update scritp file below

ExperienceTesla said:
i do it but same error, i uploaded my update scritp file below
Click to expand...
Click to collapse
the script looks good to me, shouldn't be causing you issues as far as I can tell (but what do I know, lol). Are you using the latest version of TWRP?

Anyone try to flash this rom??

wang1chung said:
the script looks good to me, shouldn't be causing you issues as far as I can tell (but what do I know, lol). Are you using the latest version of TWRP?
Click to expand...
Click to collapse
yes: 3.1.0.0. i think the error is the system.new.dat. there is a way to keep system folder in rom zip instead of system.new.dat? like kitkat roms

ExperienceTesla said:
yes: 3.1.0.0. i think the error is the system.new.dat. there is a way to keep system folder in rom zip instead of system.new.dat? like kitkat roms
Click to expand...
Click to collapse
i know there is a command for the updater-script called package_extract_dir("system", "/system"); which should work if you extract system.new.dat to the /system directory of your rom zip, but there's a lot (like 100 lines) of other symlink and metadata commands that I don't understand.
Have you had any luck?
Edit.....think I found something. Try using the first 5 lines of transfer list file from the stock Rom. Maybe more, I'm not sure.
Edit 2: after looking at a breakdown of how the transfer list works, I think this is dangerous.
Edit 3: the "port rom" you uploaded is a lollipop 5.x android Rom, so I'm not sure what you're using as a "base Rom" when porting this as I thought the zf3 only came with 6.x and 7.x?

wang1chung said:
i know there is a command for the updater-script called package_extract_dir("system", "/system"); which should work if you extract system.new.dat to the /system directory of your rom zip, but there's a lot (like 100 lines) of other symlink and metadata commands that I don't understand.
Have you had any luck?
Edit.....think I found something. Try using the first 5 lines of transfer list file from the stock Rom. Maybe more, I'm not sure.
Edit 2: after looking at a breakdown of how the transfer list works, I think this is dangerous.
Edit 3: the "port rom" you uploaded is a lollipop 5.x android Rom, so I'm not sure what you're using as a "base Rom" when porting this as I thought the zf3 only came with 6.x and 7.x?
Click to expand...
Click to collapse
the port rom is Validus-mido-7.1.2.STABLE.15.1-UNOFFICIAL-20171022-2227 from xiaomi redmi note 4 and the stock rom is lineage os. i tried other tutorial with no success. tommorrow i try to port another rom :good:

@ExperiencedTesla
It's weird, because when I extracted the system.new.dat of the stock 7.1 Rom, it showed it was a android 7.1 Rom....but when I extracted your validus rom, it showed 5.0?

[Treble] Android GSI on Kenzo/Kate. [SnapDragon]

UPDATE - Pixel Experience Official is out for Kenzo. Link attached below. Ongoing support for GSI users though.
https://forum.xda-developers.com/redmi-note-3/development/rom-pixel-experience-t3835648
-------------------------------------------
Disclaimer: I'm not responsible for bricked devices, flash at your own risk. I might be able to help with restoring your device though.
This is a guide to installing Android GSI on Redmi Note 3 (Kenzo)
---------------------------------------------------
What works-
RIL
GPS
Camera
Pretty much everything
What doesn't work-
Bluetooth
Hotspot
VoLTE(I couldn't test)
(NOTE - Bugs vary GSI to GSI)
---------------------------------------------------
Required files -
Grab these files first, and keep them on your SD card
TWRP Treble - https://androidfilehost.com/?fid=5862345805528059847
Android GSI(USE ARM64 A-ONLY) - for this tutorial, I'm using Phhusson's AOSP Pie GSI found here - https://forum.xda-developers.com/pr...vice-development/aosp-9-0-phh-treble-t3831915
List of GSI's - https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Pie GApps (If using Pie GSI) - https://forum.xda-developers.com/android/development/gapps-unofficial-opengapps-builds-t3828141
Vendor Image - https://androidfilehost.com/?fid=1322778262903993757
Permissive SELinux Enabler - https://drive.google.com/file/d/1KFdPH2JGtvkXwt2emxPb-k7zdv2pLd-F/view?usp=drivesdk
Magisk 16.7 (minimum 16.7, you can use 17 as well)- https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Latest Firmware - https://forum.xda-developers.com/redmi-note-3/development/firmware-hmnote3proglobal-t3574361/page176
Optional - Digital Well-being (ONLY FOR PIE)
Digital Well-being apk (Download latest version) - https://www.apkmirror.com/apk/googl...wellbeing-0-2-207862754-android-apk-download/
Digital Well-being Magisk Module - https://drive.google.com/file/d/1AAFMWbAAK-febiP9h4iZMJONEHXopmEU/view?usp=drivesdk
--------------------------------------------
Assuming you have an unlocked bootloader, and know your way in and around Android, let's begin!
How to install -
1. First, flash the Treble enabled TWRP.
2. Reboot to recovery.
3. Mount all partitions, and wipe all partitions.
4. Flash the Vendor Image zip file and immediately flash the Permissive SELinux Enabler.
5. Clear Dalvik/Cache.
6. Mount all partitions, and wipe system.
7. Flash GSI to System partition *only*.
8. Reboot to System.
9. Reboot to recovery.
10. Perform a factory data reset, and flash GApps
11. Reboot to System, and complete setup.
12. After completing setup, reboot to recovery and flash Magisk 16.7
13. Reboot to System
14 Reboot to recovery and flash firmware.
15. Profit!
If you want Digital Well-being (ONLY FOR PIE) -
16. Install Digital Well-being apk
17. Flash Digital Well-being Magisk Module through Magisk Manager
18. Reboot
19. Profit!
-------------------------------------------------------
Tested on Snapdragon version, don't know if it works on MTK.
Screenshots are attached.

Fixes -
If you have the QS toggles moving out of the header like the screenshot attached in #1, do the following steps
1. Enable Developer Settings,
2. Find Smallest Width setting
3. Increase the value by 20. (If it's 360, make it 380)
4. Profit!
------------------------------------------
Google Camera + Face Unlock fix.
If Google Camera/Face Unlock doesn't work for you, do the following -
1. Reboot to recovery
2. Mount system
3. Flash the zip file (download link below)
4. Clear cache
5. Reboot to system
This should make Face Unlock work again, and GCam work as well.
Download patch - https://drive.google.com/file/d/17OUBxhsfeK0625_pYe8aRNr5L6doKdAK/view?usp=drivesdk
------------------------------------------
Can't find Smart Lock in settings?
1. Go to Settings < Security and Location.
2. Scroll down and click Advanced.
3. Click Trust Agents.
4. Switch on Trust Agent for Smart Lock.
You should now have Smart Lock option below Fingerprint.
-------------------++++++++++++++++-----------------------
For Changing accent colours -
Download this file - https://t.me/kenzousersglobal/1169
1. Flash it in recovery
2. Reboot to system
3. Go to Settings - Display - Advanced. Scroll down to find "Colour Theme"
4. Select colour theme and select colour of your choice.
5. Profit!
---------------------------------
Custom kernels that currently work
Radon - https://drive.google.com/file/d/1LYggpHDVph1fvWctIKY4FqQwtRb6Svh0/view
---------------------------------
Review - after extensive testing, I found this to be daily driver material, with the only exception being Bluetooth, Hotspot, and VoLTE(I couldn't test it myself)
Special thanks to - @corkiejp

Is it possible to get an Overlay Patch for Mi 8?

NielsvdS said:
Is it possible to get an Overlay Patch for Mi 8?
Click to expand...
Click to collapse
I honestly have no clue. I have only gathered all the patches and files for Kenzo and made them into one guide.

Thanks for the guide: -
Digital Well-being apk (Download latest version) <<<< Links to the overlay zip and not the apk.
Sourced the beta of apkmirror: - https://www.apkmirror.com/apk/googl...wellbeing-0-2-207862754-android-apk-download/
I used Mind the Gapps found on Telegram, when flashing.
Is it possible to dirty flash open gapps?

Work on kate devices?

Why is it there system.img.xz should I remove .xz rename it
---------- Post added at 04:24 PM ---------- Previous post was at 03:42 PM ----------
1.flashed carlosvendor.zip
2.mounted system vendor cache
3.flshed system.img as system image
After rebooting stuck at fastboot logo

sharan565 said:
Why is it there system.img.xz should I remove .xz rename it
---------- Post added at 04:24 PM ---------- Previous post was at 03:42 PM ----------
1.flashed carlosvendor.zip
2.mounted system vendor cache
3.flshed system.img as system image
After rebooting stuck at fastboot logo
Click to expand...
Click to collapse
You need to extract the image file from that compressed format, use windows are download an app that will extract it.
Suggestion RAR from play: - com.rarlab.rar or alternative app that will do the same.

corkiejp said:
You need to extract the image file from that compressed format, use windows are download an app that will extract it.
Suggestion RAR from play: - com.rarlab.rar or alternative app that will do the same.
Click to expand...
Click to collapse
Thanks man I will try

Hey @Sid127, this is really nicely written tutorial, thank you What bothers me, why we need to mount partitions once again in step 6? Partitions were mounted in step 3 and there wasn't any reboot in meanwhile.
3. Mount all partitions, and wipe all partitions.
4. Flash the Vendor Image zip file.
5. Clear Dalvik/Cache.
6. Mount all partitions, and wipe system.
7. Flash GSI to System partition *only*.
Click to expand...
Click to collapse
Second question, maybe easier... If I have existing TWRP backup for non treble ROM, is it OK to restore such backup using Treble recovery after wiping everything? Or it's recommended to flash previous recovery first?

wxtester said:
Hey @Sid127, this is really nicely written tutorial, thank you What bothers me, why we need to mount partitions once again in step 6? Partitions were mounted in step 3 and there wasn't any reboot in meanwhile.
Second question, maybe easier... If I have existing TWRP backup for non treble ROM, is it OK to restore such backup using Treble recovery after wiping everything? Or it's recommended to flash previous recovery first?
Click to expand...
Click to collapse
1. You just need to make sure that all partitions are mounted.
2. You can restore the backup through Treble TWRP.
Happy flashing!

Hexvessel1992 said:
Work on kate devices?
Click to expand...
Click to collapse
I don't know, I need someone to test it. It should work, since the Vendor for Kenzo and Kate are the same.

corkiejp said:
Thanks for the guide: -
Digital Well-being apk (Download latest version) <<<< Links to the overlay zip and not the apk.
Sourced the beta of apkmirror: - https://www.apkmirror.com/apk/googl...wellbeing-0-2-207862754-android-apk-download/
I used Mind the Gapps found on Telegram, when flashing.
Is it possible to dirty flash open gapps?
Click to expand...
Click to collapse
I'll update the thread with the right link
I think it is possible to dirty flash Open Gapps, but it might give bugs, always go for a clean flash

Everything works for me, only thing was that at the first setup it was stuck on "checking for updates". So I tried the method of tapping all sides of the screen (from top-left clockwise to bottom-left) and it skipped the setup. The flashlight is a little wonky, but that's the only thing that was getting in my way. The audio was a little too quiet, so I installed some app on the playstore to gain it. Thanks for such a comprehensive guide! Android Pie is amazing, but development for it on a 3 year old device is even more so!

srishant said:
Everything works for me, only thing was that at the first setup it was stuck on "checking for updates". So I tried the method of tapping all sides of the screen (from top-left clockwise to bottom-left) and it skipped the setup. The flashlight is a little wonky, but that's the only thing that was getting in my way. The audio was a little too quiet, so I installed some app on the playstore to gain it. Thanks for such a comprehensive guide! Android Pie is amazing, but development for it on a 3 year old device is even more so!
Click to expand...
Click to collapse
I had to forage through 4 complex guides, scourge through XDA and Telegram for all the patches, and hence could make such a simple guide. Apparently, devs on the Telegram channel are working on the Bluetooth and VoLTE fix I'll update once that happens!

Bolte
Test n let me know if it works
https://t.me/kenzoromnews/1445
Modify for treble then flash

amog787 said:
Bolte
Test n let me know if it works
https://t.me/kenzoromnews/1445
Modify for treble then flash
Click to expand...
Click to collapse
I did see that, but when I flashed it, it messed upy system and I had to reinstall the GSI. I don't know how to modify it for Treble, could you do it? I'm happy to test. I believe that fix is for Flashavle ZIPs, not for Treble GSIs.

Possible Gcam and stock working patch!
Posted this in AOSP Pie Rom thread, may also work for the GSI?
corkiejp said:
I found Gcam Pie Fix for another device in this thread.
Link to Gcam Pie Fix: - https://drive.google.com/file/d/1D5qvlA-QbQu6xoWpsLPyWquMkS3hxXi3/view
Gcam that I'm using: - https://androidfilehost.com/?fid=673956719939833577
^^^ From this thread, maybe newer versions available.
I was able to setup face unlock after flashing the above fix, you may also need to enable Smart Lock (Google) as a trusted agent.
It is buggy and the face option may not always trigger, plus you need to hold the phone far from you and swipe when the lock symbol appears (no fast unlock options xposed).
Another benefit of flashing another Camera (V 2.0.002) Started working as well. (Don't know if that is the default AOSP camera or something I restored from backup? Could be Snap Camera from LOS).
Click to expand...
Click to collapse

corkiejp said:
Posted this in AOSP Pie Rom thread, may also work for the GSI?
Click to expand...
Click to collapse
Is there also an uninstaller for this fix? I'll test only if there is an uninstaller for it. Last time I tested a fix I had to format data to revert...

Sid127 said:
Is there also an uninstaller for this fix? I'll test only if there is an uninstaller for it. Last time I tested a fix I had to format data to revert...
Click to expand...
Click to collapse
Not that I'm aware of, but this just places/replaces some Lib and Lib64 in system partition.
If your worried about it, back up your system partition, flash the this patch and wipe caches.
If you experience problems, just restore your system partition.
It was reported working by someone else here.