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.

[Discussion] OP8Pro - magisk notification lead to unresponsive manager

Anyone else ever have it happen where you get a magisk update prompt, thought you swiped it away only to have accidentally tapped it? It installed something. But my magisk manager stopped responding. After trying to open it a few times, my 8pro rebooted. I had to install magiskv23.apk because my manager wasn't loading and it was renamed through the magisk app (I had to rename it because I had a couple apps that saw Magisk and wouldn't load). Now I'm stuck without root, and without a stock boot image for open beta 12. Pain in the rear situation. BUT TiBu still recognizes root access. So does terminal emulator when I type su. I get a pop up that MagixMgr isn't responding. Not even sure how to get out of this situation, since I don't have twrp..

If your talking about OB1 ColorOS12, you can download the OTA.zip for it, and extract the payload.bin file from the zip using 7zip (or similar). Run the payload.bin through the payload dumper tool to get the boot.img. Than patch that and flash it.

No, I'm on open beta 12. Still oxygen OS. I extracted my boot images through terminal emulator since I still have root. Patched those with magisk 23 apk. Just have to try flashing them. But I don't think that's my issue since I still have root. The magisk manager is broken, and if I install a different magisk apk, it doesn't recognize that I have magisk installed, or root.

mattgyver said:
No, I'm on open beta 12. Still oxygen OS. I extracted my boot images through terminal emulator since I still have root. Patched those with magisk 23 apk. Just have to try flashing them. But I don't think that's my issue since I still have root. The magisk manager is broken, and if I install a different magisk apk, it doesn't recognize that I have magisk installed, or root.
Click to expand...
Click to collapse
Where is open beta for oxygen os 12 on 8 pro? There were no news or release of an oos 12 ob...

@gsser It's not OOS 12. Open beta 12 is OOS 11. And it's been available since end of July.
{
"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"
}

I thought maybe reinstalling a patched boot image would help. Extracted my boot image, patched it in Magisk 23 apk. Flashed it in fastboot. Nada. Magisk 23 doesn't recognize magisk installed. my magisk app that was renamed through it's own UI still is failing to respond. Titanium Backup, Terminal Emulator, and Solid Explorer still all have retained root access.
I guess technically I'm fine, but I can't make changes to my modules, magiskHide apps, and I'm not sure if trying to upgrade to Magisk 24.1 apk will cause issues when upgrading my Magisk install.
What's interesting is that the magisk apk that my manager tried downloading was saved as Magisk-(-1).apk instead of any version numbering. it was only 280KB in size, compared to a few MB. and if I try manually installing it, it fails to parse the package.
Update1: so I flashed the official twrp beta. Downloaded the twrp app, and it never prompts about root permission, so it can't find my recovery. I don't get a prompt about MagixMgr not responding this time. So I can't grant any new apps root access.
Update2: apparently this has killed my wifi, too. I can't get the oneplus 8 pro to start wifi. it acts like it's starting, but if I swipe away the notification shade, and bring it back down, wifi is off again. i don't want to factory reset my phone, but I have this funny feeling that it's going to be my only option....
Update3: Uninstalled my magisk proxy app. pulled the full OTA OOS11 OB12 zip file and extracted payload.bin on my linux box. patched with magisk 24.1. flashed stock boot, and stock recovery to both a/b slots. then flashed magisk patched stock boot image instead of the one that I had pulled from my phone. success. Magisk 24.1 shows as installed, and I have full superuser access again. and a few more gray hairs. but all is well, even if I wasn't too sure about upgrading to the new magisk and losing magiskHide. but I'll look into the new modules being developed...

[Discussion] OP8Pro - magisk notification lead to unresponsive manager

Anyone else ever have it happen where you get a magisk update prompt, thought you swiped it away only to have accidentally tapped it? It installed something. But my magisk manager stopped responding. After trying to open it a few times, my 8pro rebooted. I had to install magiskv23.apk because my manager wasn't loading and it was renamed through the magisk app (I had to rename it because I had a couple apps that saw Magisk and wouldn't load). Now I'm stuck without root, and without a stock boot image for open beta 12. Pain in the rear situation. BUT TiBu still recognizes root access. So does terminal emulator when I type su. I get a pop up that MagixMgr isn't responding. Not even sure how to get out of this situation, since I don't have twrp..

If your talking about OB1 ColorOS12, you can download the OTA.zip for it, and extract the payload.bin file from the zip using 7zip (or similar). Run the payload.bin through the payload dumper tool to get the boot.img. Than patch that and flash it.

No, I'm on open beta 12. Still oxygen OS. I extracted my boot images through terminal emulator since I still have root. Patched those with magisk 23 apk. Just have to try flashing them. But I don't think that's my issue since I still have root. The magisk manager is broken, and if I install a different magisk apk, it doesn't recognize that I have magisk installed, or root.

mattgyver said:
No, I'm on open beta 12. Still oxygen OS. I extracted my boot images through terminal emulator since I still have root. Patched those with magisk 23 apk. Just have to try flashing them. But I don't think that's my issue since I still have root. The magisk manager is broken, and if I install a different magisk apk, it doesn't recognize that I have magisk installed, or root.
Click to expand...
Click to collapse
Where is open beta for oxygen os 12 on 8 pro? There were no news or release of an oos 12 ob...

@gsser It's not OOS 12. Open beta 12 is OOS 11. And it's been available since end of July.
{
"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"
}

I thought maybe reinstalling a patched boot image would help. Extracted my boot image, patched it in Magisk 23 apk. Flashed it in fastboot. Nada. Magisk 23 doesn't recognize magisk installed. my magisk app that was renamed through it's own UI still is failing to respond. Titanium Backup, Terminal Emulator, and Solid Explorer still all have retained root access.
I guess technically I'm fine, but I can't make changes to my modules, magiskHide apps, and I'm not sure if trying to upgrade to Magisk 24.1 apk will cause issues when upgrading my Magisk install.
What's interesting is that the magisk apk that my manager tried downloading was saved as Magisk-(-1).apk instead of any version numbering. it was only 280KB in size, compared to a few MB. and if I try manually installing it, it fails to parse the package.
Update1: so I flashed the official twrp beta. Downloaded the twrp app, and it never prompts about root permission, so it can't find my recovery. I don't get a prompt about MagixMgr not responding this time. So I can't grant any new apps root access.
Update2: apparently this has killed my wifi, too. I can't get the oneplus 8 pro to start wifi. it acts like it's starting, but if I swipe away the notification shade, and bring it back down, wifi is off again. i don't want to factory reset my phone, but I have this funny feeling that it's going to be my only option....
Update3: Uninstalled my magisk proxy app. pulled the full OTA OOS11 OB12 zip file and extracted payload.bin on my linux box. patched with magisk 24.1. flashed stock boot, and stock recovery to both a/b slots. then flashed magisk patched stock boot image instead of the one that I had pulled from my phone. success. Magisk 24.1 shows as installed, and I have full superuser access again. and a few more gray hairs. but all is well, even if I wasn't too sure about upgrading to the new magisk and losing magiskHide. but I'll look into the new modules being developed...

General [NE2213] OxygenOS 13 C.20

[NE2213] OxygenOS 13 C.20
{
"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"
}

Full OTA Link:
[NE2213] OxygenOS 13 C.20

Update instruction for Root users:
1- Uninstall all magisk modules => Manual reboot
2- Uninstall magisk (Complete uninstall) => Auto reboot
3- You can only install Full OTA with Local update option (I don't recommend incremental update)
4- [Optional] After update if you need root access extract stock boot.img from Full OTA and patch it with magisk

S /\ E E D said:
Full OTA Link:
[NE2213] OxygenOS 13 C.20
Click to expand...
Click to collapse
Hi mate if I update to this stable version using oxygen updater app from beta 2, will I loose my data? Thanks

ugendersingh said:
Hi mate if I update to this stable version using oxygen updater app from beta 2, will I loose my data? Thanks
Click to expand...
Click to collapse
I don't think, BTW have a backup from your data before install

S /\ E E D said:
I don't think, BTW have a backup from your data before install
Click to expand...
Click to collapse
Hi Mate I have tried backup using oneplus clone phone app but it doesn't backup photos and videos. Any other way of backing up data?

S /\ E E D said:
Update instruction for Root users:
1- Uninstall all magisk modules => Manual reboot
2- Uninstall magisk (Complete uninstall) => Auto reboot
3- You can only install Full OTA with Local update option (I don't recommend incremental update)
4- [Optional] After update if you need root access extract stock boot.img from Full OTA and patch it with magisk
Click to expand...
Click to collapse
Did someone try alread this method here from android 12 updates?
Magisk OTA Update reboot directly
Hey Guys, I don't found any similar thread about this topic, so I will create a new. I have magisk installed and used OxygenOS 12.1 A.10. Today I got the first update to A.12. I did it the same way as I did on Android 11. Recover Image ->...
forum.xda-developers.com

NE2215 here; no C.20 yet for us.

2- Uninstall magisk (Complete uninstall) => Auto reboot <---- do i have to do this? or is that optional?

beterman said:
2- Uninstall magisk (Complete uninstall) => Auto reboot <---- do i have to do this? or is that optional?
Click to expand...
Click to collapse
If you ask from me, I answer it with yes, you should do it
However someone else maybe say you skip that
You can also ask from @Prant about this

Prant said:
NE2215 here; no C.20 yet for us.
Click to expand...
Click to collapse
Wait 2 or 3 more days for the NE2215 we're the bastard child of the 10 pro LOL

foamerman said:
Wait 2 or 3 more days for the NE2215 we're the bastard child of the 10 pro LOL
Click to expand...
Click to collapse
Hahaha, "Global" version.

I'm having trouble extracting the boot.img from payload.bin with payload_dumper in Python. See the error below. Anyone any tips or care to upload the boot.img?
Traceback (most recent call last):
File "payload_dumper.py", line 92, in <module>
dump_part(part)
File "payload_dumper.py", line 55, in dump_part
data = data_for_op(op)
File "payload_dumper.py", line 41, in data_for_op
data = dec.decompress(data)
_lzma.LZMAError: Input format not supported by decoder
NEVER MIND:
used Fastboot enhance instead and that worked well

Hi i have a question somebody can check Viper4android working on oxygen os 13? And how to install

S /\ E E D said:
Update instruction for Root users:
1- Uninstall all magisk modules => Manual reboot
2- Uninstall magisk (Complete uninstall) => Auto reboot
3- You can only install Full OTA with Local update option (I don't recommend incremental update)
4- [Optional] After update if you need root access extract stock boot.img from Full OTA and patch it with magisk
Click to expand...
Click to collapse
Local update option disabled in update menu?

Hello, anyone can help me please ?
after the update, I patch the boot.img with magisk i have magisk_patched.img file and I flash it with the commands:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
after that the phone reboots in bootloader loop mode forced to reflash the original boot.img
what mistake am I making?
EDIT : sorry i find a tutorial to root :
2. Reboot your phone to fastboot
and connect to your computer.
3. Boot the magisk patched img
fastboot boot magisk_patched (or name of your patched boot img)
Your phone should now boot automatically, you should now be rooted but we need to make this permanent, if you were to reboot you would lose root.
4. Open magisk manager and click install/update, if you are missing the install/ update buttons, change magisk version to beta in magisk settings and install the update, the buttons should then show.
5. Select Direct install (recommended) then click ok.
6. Allow magisk to permanently root your device then click reboot.
it's ok with this ...

Hi guys !
Is NFC payment with google wallet working on this build ?
And battery life semme better/worst/similar to android 12 ?
I'm still with android 12 and wonder if it is worth to go for A13 now
Thanks !

Yes / better

Prant said:
Hahaha, "Global" version.
Click to expand...
Click to collapse
I notice you keep calling 2215 the global version when its not. That may have been what most people thought in the beginning but its simply not the case. Even if you browse the one plus community pages where they release the information about these updates they are also labeling 2213 as the global version. 2215 is for North America.

biglo said:
I notice you keep calling 2215 the global version when its not. That may have been what most people thought in the beginning but its simply not the case. Even if you browse the one plus community pages where they release the information about these updates they are also labeling 2213 as the global version. 2215 is for North America.
View attachment 5725283
Click to expand...
Click to collapse
Exactly

How do I install gapp's on A11 and with Chinese firmware version V5.17?

Hello friends!
I bought the Red Magic 3S. It has firmware from the Chinese version V5.17 and Android 11. I don't have Google play or Google Services. It also did not receive notification in most apps. I would like to know where to start, sorry for the bad english
As per "courtesy" a Senior Moderator translated your post, I encourage you to use a translator to use the English language in your later posts

Im in the same situation, installed the chinese version through system update. Updated chinese version to Android 11 V5.17. Installed TWRP with adb with bootloader and then also installed magisk through TWRP Recovery adb sideload but cannot install gapps pico it says error 70, when I googled that it means that theres not enough system storage to install gapps. I've deleted some of the original bloatware with magisk debloater and still has no space. I'm beginning to think that it is due to system being encrypted and twrp thinks theres no space to installed. Have tried removing screen lock still didn't work. Under settings security we can find were phone says encrypted I just have to figure out how yo decrypt. Maybe something nubia did to prevent us from rooting?

Try installing Google packages through the app called "HiGoPlay". You will find this app in the app center store
{
"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"
}
juan_carlos__007 said:
Im in the same situation, installed the chinese version through system update. Updated chinese version to Android 11 V5.17. Installed TWRP with adb with bootloader and then also installed magisk through TWRP Recovery adb sideload but cannot install gapps pico it says error 70, when I googled that it means that theres not enough system storage to install gapps. I've deleted some of the original bloatware with magisk debloater and still has no space. I'm beginning to think that it is due to system being encrypted and twrp thinks theres no space to installed. Have tried removing screen lock still didn't work. Under settings security we can find were phone says encrypted I just have to figure out how yo decrypt. Maybe something nubia did to prevent us from rooting?
Click to expand...
Click to collapse
In my case, I still haven't done any procedure, like unlocking the bootload, twrp, root, etc. But with you it can work!

if u still need help dm me

To install Оpen GApps pico on 11 android v5.17, you need to delete the folder nubia_Browser, it is in the folder app, this browser still needs to be removed so that it does not redirect to the Chinese store, you will have 100 mb of free space and twrp will not give an error that there is not enough free space.
https://sourceforge.net/projects/opengapps/files/arm64/20220503/open_gapps-arm64-11.0-pico-20220503.zip/download
Before installing google services, you need to remove all types of locks on your phone and put one pin code lock, then when you load it into the system, Google will ask for a pin code, then fingerprints: write your own pin code, fingerprints must be skipped!
Installing gapps pico:
1. You must be root!
2. reboot into twrp-3.3.1-4-NX629J-mauronofrio
3. click: settings
4. click: reset settings
5. go: extra
6. push: explorer
7. choose: system_root
8. choose: system
9. choose: app
10. find: nubia_Browser and other programs I threw off screenshots
11. in the lower right corner, click on the folder with a checkmark
12. click on: delete button
13. flash open gapps pico from phone memory or flash drive
14. reboot into the system.
15. optional: download Browser V7.3.5.2022091518a.zip, unzip and install browser apk.
SDCARD TRANSCRIPT:
The phone must be rooted with twrp-3.3.1-4-NX629J-mauronofrio installed!
1. In TWRP clear: Dalvik/ART Cache, Cache, Data, Device Memory
2. Reboot your phone in twrp
3. With flash drive install magisk Magisk-25.2(25200).zip
4. Reboot into the system.
5. Install Magisk 25.2.apk