{
"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
Related
{
"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.
TWRP for OnePlus 8 and 8 Pro
{
"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"
}
TWRP is an open source, community project. TWRP development is done by a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers, and zulip-chat.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom "ROM".
Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no responsibility for any damage that may occur from installing or using TWRP.
Code:
#include
/*
*
* Yea, though I walk through the valleys of c++ and java, of the shadow of death on these forums,
* I will fear no evil and i will develop and code restless: for thou art with me and my keyboard;
* thy rod and thy staff they comfort me, and my mouse..
*
*/
A13 support is still a WIP, but most things are working, A13 is all new, keep that in mind.
WORKING:
Decryption
ADB Sideload
Format Data
Flashing zips (kernels and ROM's)
Backup/Restore
MTP is working
adb is working
OTG
more...
NOT WORKING
tell me
Download
Beta 3
Flashable zips:
https://devuploads.com/h6omb3dsxg5n -> twrp_op8_ext4-3.7.0-b3.zip - 34.8 MB
https://devuploads.com/d6j8gpbyfbzf -> twrp_op8_erofs-3.7.0-b3.zip - 34.8 MB
Flashable imgs
https://devuploads.com/gxv3t5onoapm -> twrp_op8_ext4-3.7.0-b3.img - 100.0 MB
https://devuploads.com/vg662syh8j7j -> twrp_op8_erofs-3.7.0-b3.img - 100.0 MB
(Please disable any adblockers downloading from my links)
Instructions
Windows
Install oneplus usb driver, after disabling driver signature enforcement
Download and install platform tools, unzip and add the folder to Windows path,
"Settings > Advanced System Settings > Environment Variables > New"
Example -> http:///imgur.com/a/x8XOofQ
open command prompt, or powershell, and:
fastboot flash recovery_a twrpname.img
fastboot flash recovery_b twrpname.img
Linux
Download and add to path (.bashrc) platform-tools:
export PATH=$HOME"/platform-tools:$PATH"
dont forget udev rules if you're using ubuntu based distro:
https://github.com/M0Rf30/android-udev-rules
open a terminal and:
fastboot flash recovery_a twrpname.img
fastboot flash recovery_b twrpname.img
that's all.
Telegram Group:
Telegram: Contact @infected_unofficial_stuff_group
t.me
Feel free to join!
Source Code:
GitHub - infectedmushi/twrp_device_oneplus_instantnoodle
Contribute to infectedmushi/twrp_device_oneplus_instantnoodle development by creating an account on GitHub.
github.com
https://github.com/infectedmushi/android_bootable_recovery
https://github.com/bigbiff/android_device_oneplus_instantnoodle
https://github.com/TeamWin/android_bootable_recovery
https://github.com/systemad/android_device_oneplus_instantnoodle
Credits:
@bigbiff
@Lossyx
@Captain_Throwback for original tree
@mauronofrio for original tree
TWRP team
HOW TO BACKUP && RESTORE ON TWRP CORRECTLY
theincognito said:
Steps for backing up and restoring data in TWRP (Huge thanks to @BillGoss )
Remove any password/pin/pattern before doing this
Backup
In TWRP
Backup: Select only the Data partition.
Reboot System
Restore
In TWRP
If you skip this step you will not be able to successfully start the system after restoring data
Wipe>Factory Reset
Reboot System (this will rebuild the data partition)
Back in TWRP
Restore: Select the backup you want to restore
Reboot system
Note:
At this point the phone will take longer than usual to boot - that's normal
You will be presented with a blank screen or a toast message saying "com.android.phone keeps stopping."
Tap "Close app", hold the Power button down to be presented with the option to (Lockdown), Power off, or Restart. Select Restart
It may take a couple of restarts
If you want to backup and restore fingerprints too, follow the guide in the attached file
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/...ect-8t-kebab-2021-09-04.4302449/post-85292199
thanks @BillGoss && @theincognito
This is awesome! Thanks for opening a new thread!
Sweeet tnx
Thank you very much, beta 2 is working good
uploaded beta 3.
changelog:
https://gerrit.twrp.me/c/android_bootable_recovery/+/4411
* zip install: unmap any dynamic partitions before installing
https://gerrit.twrp.me/c/android_bootable_recovery/+/4401
* version: don't show as error if we cannot write the version string
https://gerrit.twrp.me/c/android_bootable_recovery/+/4386
* relink recovery modules correctly - Added ziptool as unzip deprecated in a11
regards.
Why do we need to install new drivers with no signature?
Whats the problem with normal platform tools?
Can anyone confirm if could restore a backup successfully and what is the right order to restore every partition?
xtcislove said:
Why do we need to install new drivers with no signature?
Whats the problem with normal platform tools?
Click to expand...
Click to collapse
you don't need to do anything if you already got fastboot and adb working.
Thank you to all the people involved.
Finally the hard work gave fruits!
Noce to see this become official finally
Successful restore anyone?
vibration does not work :3
Do we have to use MSM Tool to format before installing? Also, did anyone successfully restore a nandroid backup?
progress on MTP issue..
Revenant Ghost said:
Do we have to use MSM Tool to format before installing? Also, did anyone successfully restore a nandroid backup?
Click to expand...
Click to collapse
If you run MSM you'll completely wipe your phone and relock the bootloader.
anyone can test MTP on Windows, and data restore?
https://drive.google.com/open?id=1b...JmIBVr&[email protected]&usp=drive_fs
@infected_ for me mtp work on beta 2 and 3. On oneplus 8 pro with latest oos.
Noob9496 said:
@infected_ for me mtp work on beta 2 and 3. On oneplus 8 pro with latest oos.
Click to expand...
Click to collapse
nice. can you test /data restore? and see if doesn't gives error 255?
infected_ said:
nice. can you test /data restore? and see if doesn't gives error 255?
Click to expand...
Click to collapse
Unfortunately, I will not do it at the moment because I do not have time. And in case of problems with the system, I will have to reinstall everything and upload files.
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.
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
{
"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"
}
CalyxOS is an Android mobile operating system that puts privacy and security into the hands of everyday users. Plus, proactive security recommendations and automatic updates take the guesswork out of keeping your personal data personal.
Your warranty is now void, or not... I have no idea; it depends...
・ I'm not responsible for bricked devices, thermonuclear war or alarm app fails.
・ If it's your first time or you're unexperienced with flashing ROMS, please do some search before flashing!
・ YOU are choosing to make these modifications, you're the only responsible guy for messing up if you do so.
(unless i messed up something, but since it works for me, it shouldn't be an issue from the rom builder (me)
Known Bugs :
- Fingerprint
- Mobile Data & Microphone in voice calls
Notes:
Do NOT flash gapps (MicroG included, make sure to enable them when you're setting up after you just installed)
I do not work for or under the calyx institute.
This build was mainly made for myself, so i don't promise maintaining, maybe in my free time tho.
(27/04/2023) Updated the link to the new build from Yairzar (Thanks for the fixed build! My branch was kinda broken/messy as i'm a beginner.)
ROM Source : https://gitlab.com/CalyxOS
KERNEL Source : https://github.com/AOSP-for-venus/platform_device_xiaomi_venus-kernel
Device Tree / vendor & etc : https://github.com/MiRw3b/xiaomi-venus-files
Download : https://sourceforge.net/projects/yairpatch/files/calyxos/calyx_venus-ota-eng.yair.zip/download
New Clean flashing tutorial :
!YOU NEED ADB/FASTBOOT TOOLS!
1. Flash the latest TWRP/OFOX and boot on the recovery.
2. go in "Format Data/Factory Reset". (DOING THIS STEP WILL WIPE YOUR DATA) after you did,
3. on your computer, open cmd (or terminal) in the folder where the zip is located
4. push the zip file to tmp by using
Code:
adb push calyx_venus-ota-eng.yair.zip tmp/
5. go in "Install", then go up a level, then search the folder 'tmp" and find the zip file, then flash it. you don't need gapps since there's microG as a replacement HOWEVER games will NOT correctly work on it (google play services don't work)
Dirty Flashing / Updating tutorial :
1. Reboot to Recovery
2. on your computer, open CMD (or terminal) in the folder where the .zip is located
3.Flash the zip by doing "adb sideload calyx_venus-ota-eng.yair.zip"[/SPOILER]
Spoiler: Old flash tutorial
Clean Flashing / Installation tutorial :
Spoiler: Old flash tutorial
!YOU NEED ADB/FASTBOOT TOOLS!
1. Make sure you're on the latest MIUI (atleast 13.0.X)
2. Reboot to TWRP / OFOX and go to "Format Data/Factory Reset". (DOING THIS STEP WILL WIPE YOUR DATA) after you did,
3. reboot to Bootloader, and, on your computer, open CMD (or terminal) in the folder where the .zip is located
4. Flash the zip by doing "fastboot update calyx_venus-img-eng.mir.zip"
Dirty Flashing / Updating tutorial :
1. Reboot to Fastboot/Bootloader
2. on your computer, open CMD (or terminal) in the folder where the .zip is located
3.Flash the zip by doing "fastboot update calyx_venus-img-eng.mir.zip"
After you did, while flashing, it should reboot you to the legacy bootloader, the very old fastboot. it's normal, and then it should continue flashing until it's done. Enjoy!
Screenshots :
MiRw³b said:
Your Phone Should Be PrivateEveryone needs a phone. Not everyone wants to be spied on.
Reclaim your privacy with CalyxOS.
CalyxOS is an Android mobile operating system that puts privacy and security into the hands of everyday users. Plus, proactive security recommendations and automatic updates take the guesswork out of keeping your personal data personal.
Your warranty is now void, or not... I have no idea; it depends...
・ I'm not responsible for bricked devices, thermonuclear war or alarm app fails.
・ If it's your first time or you're unexperienced with flashing ROMS, please do some search before flashing!
・ YOU are choosing to make these modifications, you're the only responsible guy for messing up if you do so.
(unless i messed up something, but since it works for me, it shouldn't be an issue from the rom builder (me)
Known Bugs :
- Fingerprint? (not sure if it's my phone only)
Notes:
Do NOT flash gapps (MicroG included, make sure to enable them when you're setting up after you just installed)
I do not work for or under the calyx institute.
This build was mainly made for myself, so i don't promise maintaining, maybe in my free time tho.
ROM Source : https://gitlab.com/CalyxOS
KERNEL Source : https://github.com/AOSP-for-venus/platform_device_xiaomi_venus-kernel
Device Tree / vendor & etc : https://github.com/MiRw3b/xiaomi-venus-files
Download : https://anonfiles.com/GdF4L8O8y4/calyx_venus-img-eng.mir_zip
Flashing / Installation tutorial :
!YOU NEED ADB/FASTBOOT TOOLS!
1. Make sure you're on the latest MIUI (atleast 13.0.X)
2. Reboot to TWRP / OFOX and go to "Format Data/Factory Reset". (DOING THIS STEP WILL WIPE YOUR DATA) after you did,
3. reboot to Bootloader, and, on your computer, open CMD (or terminal) in the folder where the .zip is located
4. Flash the zip by doing fastboot update calyx_venus-img-eng.mir.zip
After you did, while flashing, it should reboot you to the legacy bootloader, the very old fastboot. it's normal, and then it should continue flashing until it's done. Enjoy!
Screenshots :
Click to expand...
Click to collapse
great job!
Just updated it, as camera and volume +/- weren't working, because some files were missing or empty in the vendor files of my tree.
Safetynet working ?
Vinc3nt.exe said:
Safetynet working ?
Click to expand...
Click to collapse
Good question, i haven't tried, and i don't think that it would work since it doesn't use officla Gapps, it instead uses MicroG, for a better privacy.
The download link doesn't work... File does not exist..
MiRw³b said:
Good question, i haven't tried, and i don't think that it would work since it doesn't use officla Gapps, it instead uses MicroG, for a better privacy.
Click to expand...
Click to collapse
Check out the guide to get safetynet working with microG
[GUIDE] How to get SafetyNet working with MicroG
This is a tutorial on how to set up your phone so that you can consistently pass SafetyNet. Note that all this is from my own experience, and if what works on one device blows up another, that's not my problem and I'm not responsible for that. I...
forum.xda-developers.com
nelvinchi said:
View attachment 5899619
The download link doesn't work... File does not exist..
Click to expand...
Click to collapse
fixed the link, sorry for the long wait time