Database Develop

[Guide] PROJECT TREBLE for ZOOM

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So, we have a fully functional TWRP. Now we can install custom firmware. I've been trying to get a working system on the Project Treble firmware for a long time, and found the right a working GSI images!
The firmware was taken as an example for installation Havoc-OS 3.5
Prerequisites - bootloader must be unlocked, clean Stock firmware must be installed.
Installation Instruction
1. Download the Project Treble system image archive without included GAPPs (Vanilla, ARM64-AB). Otherwise the system will not start. Unpack the archive and copy the ROM image to an external SDCard.
Download and copy to external SD Card GAPPs archive (ARM64, Android 10), Magisk Installer https://github.com/topjohnwu/Magisk (latest version for today Magisk v20.4) and Disable_Dm-Verity_ForceEncrypt https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389 (latest version for today Disable_Dm-Verity_ForceEncrypt_03.04.2020 https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip ), Permissiver_v4 (look at the attached files);
2. Install TWRP according to the Instruction, doing everything up to the 6th step.
3. Reboot in TWRP and go to the "Wipe" tab, "Advanced Wipe" and select Dalvik, System, Data, and then go back two steps back and do a "Swipe Factory reset".
4. Install the Project Treble system image. In the "Install" tab in the lower right corner click "Install image" and select ROM Image. A window will open in which you should select partition "System Image" in which the image where to be installed. Swipe for confirm flash.
5. Installing GAPPs. If you try to install the GAPPs archive immediately, the installation will be aborted with an error: 70 (Error 70). This will be eliminated as follows:
- Go to the "Wipe" tab;
- Then select "Advanced Wipe";
- In the menu that opens, select the System partition and click "Repair or change file system";
- A few buttons will appear and click "Resize File System". If the process failed the first time with Error 1, then repeat this action again.
Now you can install the GAPPs archive without any errors.
6. When the installation is complete, go to Wipe and perform a "Swipe Factory reset".
7. Install the Magisk.zip, Disable_Dm-V_ForceEncrypt.zip and Permissiver_v4.zip. Reboot into the system and make the settings, use the Project Treble working system.
The first launch will be a bit long, do not worry.
Important additions
Adaptive brightness - Copy framework-res__auto_generated_rro.apk to /vendor/overlay. Give this application permission 644. Remove the "FrameworkResVendor" folder from /vendor/overlay. Reboot the phone. In "Phone Settings" you will have a new item "Adaptive brightness" and this feature will work in "Quick Settings".
Noticed problems on Havoc-OS 3.5:
- Does not pass SafetyNet check (ctsProfile: false; basicIntegrity: true). On Google Play, your device is not certified, but applications are installed and updated.
- Wired headphones are plugged in. When connected, the Bluetooth headset in the Dialer application works, but when listening to audio, video, YouTube is not.
- Unlocking by fingerprint is implemented for scanners on the back of the phone.
Automatic brightness setting does not work - Fixed!

Found working Project Treble firmware:
Havoc-OS-v3.5 https://sourceforge.net/projects/ha...fficial-arm64-ab-vanilla-nosu.img.xz/download
AOSP 10.0 v216 https://github.com/phhusson/treble_...oad/v216/system-quack-arm64-ab-vanilla.img.xz
Firmware installation instructions will be available later.

It's truely impressive what you are doing!

Wooooooow! Finally!

Awesome work!!!
Can you confirm if the fingerprint scanner works with any of the roms?
Or if there is something missing?
Also whichone would you recommend over stock?
Thanks!!!

One zoom
Can we install this project in our one zoom?

spcarlos2 said:
Can we install this project in our one zoom?
Click to expand...
Click to collapse
I don't understand the question

ilia3367 said:
I don't understand the question
Click to expand...
Click to collapse
can i install this rom on my one zoom cell phone?

spcarlos2 said:
can i install this rom on my one zoom cell phone?
Click to expand...
Click to collapse
Buddy! And for which phone is this theme created? Isn't it for Moto One Zoom? :laugh:

After the flashes I get this:
Failed to mount '/system's (Invalid argument)
After I unpack the image zip, I rename to .img, maybe that's why, help me please...

After a successful installation, I reboot the phone and don't starts, just go to TWRP over and over, what should I do?...

thirdphotographer said:
After a successful installation, I reboot the phone and don't starts, just go to TWRP over and over, what should I do?...
Click to expand...
Click to collapse
Install again Magisk.zip, Disable_Dm-V_ForceEncrypt.zip and Permissiver_v4.zip.

I'm assuming there would be no way to get Google pay to work with this if it doesn't pass safetynet?

Afifus said:
I'm assuming there would be no way to get Google pay to work with this if it doesn't pass safetynet?
Click to expand...
Click to collapse
https://4pda.ru/forum/index.php?showtopic=968480&view=findpost&p=96932663
Try to read with a translator.

Samsung Tab A7 SM T500 Update to Android 11

First, an editorial comment:
For the money this is a great device. Compare it to the Flagship Tab S7 ($650 Fall 2021 - 128GB) versus the Tab A7 at $180 (32GB with a few $ more for a MicroSD). It is quick, plenty of storage with the MicroSD, and about the right size.
But my Rooted Tab A7 (via Magisk) kept bugging me about updating. It even started restarting in an effort to update itself.
I spent way too long yesterday reading instructions for updating to Android 11. It seems that everyone wanted to make it harder than it needed to be.
It isn't that difficult:
No loss of Data, apps, etc.
The details below have numerous steps, mostly for the unfamiliar. But there really are just three steps
Download the update
Use your existing Magisk installation to create a magisk-patched AP_T500
Flash it using Odin
DEVICE
Galaxy Tab A7 SM-T500, previously rooted with Magisk
Download Oden, the latest version. I used Odin3 v3.13.1_3B_PatcheD. https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
Download the Android 11 update. There are several ways to do this (Google it.) I found that the old standby, SamMobile lacked the latest update. I used https://samfrew.com/download/Galaxy__Tab__A7__-Wi-Fi-__/wte0/XAR/T500XXU3BUF3/T500OXM3BUF3/
Inside the ZIP file you'll find AP_T500XXU3BUF3_CL21871393_QB40910992_REV00_user_low_ship_MULTI_CERT_meta_RKEY_OS11.tar.md5
Move that to the Tablet. I put it in the root of the MicroSD card.
Open Magisk. Top Right, tap Install. Radial Button (put little black dot in circle) "Select and Patch a File"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tab LET'S GO
Magisk puts the patched file in your Download Folder of your internal memory (the internal directory called "sdcard"
Move patched file magisk_patched-XXXXX_XXXX.tar to your computer (for convivence, the same folder as your unzipped SM-T500_1_20210617XXXXXX
Open Magisk and Turn off all your Magisk modules. (If your modules are all compatible with the version you're going to this is ok but mine were not which sent my tablet into a bootloop after the update)
Now unzip Oden, from step #1, into that same SM-T500_1_20210617XXXXXX folder (for convivence.)
Turn your Tablet OFF
Launch Odin
Boot to Download Mode - hold BOTH the VolumeUP and VolumeDOWN buttons down ans simultaniously plug in your Samsung USB-C , THAT IS ALREADY CONNECTED to the PC
Put the BL_T500XXU3BUF3_XXXXX???.md5 in the Odin BL, the HOME_CSC_OMC_OXM_T500OXM3BUF3_XXXXX???.md5 in the CSC and the magisk_patched-XXXXX_XXXX.tar in the AP
Tap the Tab Start
That should do it.
16. Open Magisk and uninstall the module and reinstall compatible modules
If you forget to turn off the Magisk modules and end up in a bootloop, hold the volume up button. The the tablet should go into Safe Mode which will cause magisk to disable all the modules. Manually reboot from Safe Mode
CREDITS
https://www.thecustomdroid.com/install-ota-update-rooted-android-device-guide/
https://forum.xda-developers.com/t/...-t860-without-wiping-data-using-odin.4250457/

I would have stayed with Q. Even Q is too restrictive with trusted apps, R went Apple wild.
There are reasons I don't want an Apple, Android is moving in the same lame direction trying to make a "safer" OS. Predictable and unacceptable.
Security was never an big issue for me when using Android... you just need to take out the trash.
My conclusion, you lose more than you gain with Android 11 and above.
Go ahead Gookill, prove me wrong...
if you can big sister☠

if i get this right, by flashing the new ota updatet firmware version with home_csc i will not get a fatory reset ?

Gianni_10 said:
if i get this right, by flashing the new ota updatet firmware version with home_csc i will not get a fatory reset ?
Click to expand...
Click to collapse
yes

Mister Monday said:
yes
Click to expand...
Click to collapse
but both firmware needed to be either non rooted or rooted right?

Gianni_10 said:
but both firmware needed to be either non rooted or rooted right?
Click to expand...
Click to collapse
No.

How To Guide [Guide] - = Installing Project Treble ROM = -

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- = Installing Project Treble ROM = -
ARM64-A/B​
Preliminary requirements:
The bootloader should be unlocked on the phone, adb+fastboot drivers should be installed on PC.
Recommendations:
1. Install Project Treble firmware with already integrated GAPPs, because there is no fully-functional TWRP for this phone yet.
2. Or after installing firmware without GAPPs use this MAGISK GAPPs installer.
From personal experience. Of all the Project Treble ROM I've tried, on the interface, settings, functionality, I liked the Octavi-OS
Instruction from installing:
1. Archive Project_Treble_Install unzip to the folder with the same name at your convenience place.
2. Download your choice of Project Treble system image archive for the ARM64-AB architecture. Unzip it into the Project_Treble_Install folder and rename it to system.img.
3. Boot the phone into bootloader mode and connect it to the PC.
4. If this is your first time installing a Project Treble system image, you need to do the following:
a) Run the executive file 0_slot_pre-check.bat to determine the active slot where the device system is located.
- 1_flash_treble_slot-a - use this executable file if the slot was detected as current-slot: a (if the system was not updated via OTA or was installed using MotoFlashPro or other similar software)
- 2_flash_treble_slot-b.bat - use this executable file if the slot was detected as current-slot: b (if the system was updated via OTA);
5. 3_flash_treble_new.bat - use this executable file if you previously installed Project Treble image and want to flash some other one.
6. The device will be rebooted to fastbootd mode during installation.
7. When the installation is finished the device will automatically boot into the system. Make all necessary settings.
8. Warning! After the initial setup, perform the necessary steps with MAGISK as described HERE
Project Treble firmware topic: XDA

Say, with real GAPPS (not microG), did you get this "Uncertified Device" error (that prevents you from logging in to GMS)?
I recall seeing that error on another device after flashing GApps on top of phh-AOSP v304, and I think the issue started to happen at that point on since I never encountered the message before. Maybe because I was not using Magisk at that time... so not sure if Magisk (pre MagiskHide drop) might be taking care of it...
I tried the guide to register my device before, but it didn't really work at that time, either because it doesn't always work, or just it does not immediately take effect, so I gave up and used NanoDroid instead (which uses microG and never had that issue, and it has working IAP).

On the ROM with integrated GAPPs all is well - device is certified.

Just checked your script. I noticed the following:
1. Looks like you provided your own vendor.img. As I'm using Edge S Pro I'm not sure if this vendor.img is applicable. Also, does VoLTE work for you? My device with the stock (unmodified) Edge S Pro vendor can't get VoLTE working correctly at the moment (you can force it active but calls will hang).
2. According to the scripts, looks like you simply cleared the previous dynamic partitions and installed your vendor as well as the user provided GSI to slot A and set it to active (with different sets of commands depending on the user's currently active slot). While there's no problem in this, I'm curious about whether there is any underlying difference between the two "slots" in the context of dynamic partitions.

LSS4181 said:
1. Looks like you provided your own vendor.img. As I'm using Edge S Pro I'm not sure if this vendor.img is applicable.
Click to expand...
Click to collapse
Yes. Everything works great!
LSS4181 said:
2. According to the scripts, looks like you simply cleared the previous dynamic partitions and installed your vendor as well as the user provided GSI to slot A and set it to active (with different sets of commands depending on the user's currently active slot). While there's no problem in this, I'm curious about whether there is any underlying difference between the two "slots" in the context of dynamic partitions.
Click to expand...
Click to collapse
I don't like it when the system wastes a lot of extra disk space on the device. If you check the dynamic partition sizes of both slots in fastbootd mode, you will understand. In essence there is no difference, but why should this unnecessary garbage eat up the disk space of a device which has no SD Card support?
LSS4181 said:
Also, does VoLTE work for you?
Click to expand...
Click to collapse
I don't use this function.

Hi I have a question, How can I port the default camera ?

hello greetings, I have a big problem I followed this guide to install rom gsi and my moto edge 20 pro is dead, the device manager recognizes it in edl mode and tried with the blank flash of version 19.50 and it gives me an error, help please

[CLOSED](ROM)(A5)(Stock)(8.0) N'CreamOS (Tweaked, Deodexed, DeKnoxed, Decrypted and Rooted)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer
I am NOT responsible for bricked devices, dead SD cards or any
damage to you device. You are doing this at YOUR OWN RISKS. It's
reccomended to do a full SYSTEM BACKUP in case something went wrong.
Features
Tweaked with Build.prop for better experience
Deodexed for easy system apps modifications
DeKnoxed to remove annoying settings
Decrypted for keeping data when performing system changes trough TWRP of CWM recovery
Pre Rooted with Magisk to get superuser access and for some interesting advantages
Minecraft PE 1.19 & Geometry Dash 2.111 preinstalled (removable with root) so no need to pay for them
Many others features coming from stock Oreo ROM​
How to install
First of all, make sure you have downloaded the ROM flashable zip (Download link in bottom of this post)
Put the zip file in your phone storage or SD card if not already in
Reboot in custom recovery such as TWRP or CWM with hardware buttons (if not installed, this is a Tutorial)
Go to WIPE section and select advanced wipe
wipe Data, System, Preload, Cache-Dalvik, Cache and Internal Storage (I highly recommend to do a full backup of your ROM BEFORE WIPING)
Now, go back to home and to INSTALL section
Select storage where the ROM zip is stored and choose it
Start the operation with -zip signature check- unchecked or it will fail
If everything goes well, reboot to system and after booted, complete the setup wizard
That's it
Devices supported
Samsung Galaxy A5 2017 (SM-A520W)
Maybe F, K, L and S variants
Not for DS (dual sim) versions and Snapdragon
Requirements
A computer (for custom recovery flash)
Latest Oreo bootloader unlocked (developpers options from settings)
SD card (at least 4Gb)
Internet connection
A minimum of knowledge in Samsung phones
TWRP/CWM/OrangeFox recovery installed
Downloads
flashable rom zip file---------- - Mod Edit : Link Removed -
Thanks to
AndroDef------ For his helpfull Classy Kitchen
Topjohnwu------ For his irreplacable Magisk Root
sfirmware.com------ For the stock TAR.MD5 file
If you see some bugs, please inform me[/CODE]

I would appreciate if someone gives me comments and reports errors and bugs

Duplicate thread, see this one :
(ROM)(A5)(Stock)(8.0) N'CreamOSv2 (Tweaked, Deodexed, Busybox, DeKnoxed, Decrypted and Rooted)
Disclaimer I am NOT responsible for bricked devices, dead SD cards or any damage to you device. You are doing this at YOUR OWN RISKS. It's reccomended to do a full SYSTEM BACKUP in case something went wrong. Features Tweaked with Build.prop...
forum.xda-developers.com

(ROM)(A5)(Stock)(8.0) N'CreamOSv2 (Tweaked, Deodexed, Busybox, DeKnoxed, Decrypted and Rooted)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer
I am NOT responsible for bricked devices, dead SD cards or any
damage to you device. You are doing this at YOUR OWN RISKS. It's
reccomended to do a full SYSTEM BACKUP in case something went wrong.
Features
Tweaked with Build.prop for better experience
Deodexed for easy system apps modifications
DeKnoxed to remove annoying settings
Decrypted for keeping data when performing system changes trough TWRP of CWM recovery
Pre Rooted with Magisk to get superuser access and for some interesting advantages
Many others features coming from stock Oreo ROM
Busybox added to xbin
How to install
First of all, make sure you have downloaded the ROM flashable zip (Download link in bottom of this post)
Put the zip file in your phone storage or SD card if not already in
Reboot in custom recovery such as TWRP or CWM with hardware buttons (if not installed, this is a Tutorial)
Go to WIPE section and select advanced wipe
wipe Data, System, Preload, Cache-Dalvik, Cache and Internal Storage (I highly recommend to do a full backup of your ROM BEFORE WIPING)
Now, go back to home and to INSTALL section
Select storage where the ROM zip is stored and choose it
Start the operation with -zip signature check- unchecked or it will fail
If everything goes well, reboot to system and after booted, complete the setup wizard
That's it
Devices supported
Samsung Galaxy A5 2017 (SM-A520W) the one which i have tested (works fine)
Maybe F, K, L and S variants (Tell me if it works please)
Not for DS (dual sim) versions and Snapdragon
Requirements
A computer (for custom recovery flash)
Latest Oreo bootloader unlocked (developpers options from settings)
SD card (at least 4Gb)
Internet connection
A minimum of knowledge in Samsung phones
TWRP/CWM/OrangeFox recovery installed
Downloads
flashable rom zip file---------- N'CreamOS_8.0_v2_a5y17lte
Thanks to
AndroDef------ For his helpfull Classy Kitchen XDA Link
Topjohnwu------ For his irreplacable Magisk Root Magisk Github
sfirmware.com------ For the stock TAR.MD5 file SM-A520W(XAC)
If you see some bugs, please inform me

its just like samsung experience, i relly like it )

It is working fine on my Galaxy A520F Exynos Model, so you can check that out from the compat. checklist. For some reason the os thinks this is a A520W, but this is a F Model. I had a problem where TWRP said that flashing failed with error 7, but then I restarted it and I flashed it and it worked. Also you actually don't need a SD Card for the flasheble zip, you can actually just turn MTP on and Mount the DATA partition and copy the zip from your computer to your phone. This ROM is pretty good!

Oops, wrong post.