Database Develop

[RECOVERY] (Un-)tethered TWRP 2.8.7.0 for Asus ZenFone 2 (x86)

Hi folks,
finally we compiled a(n un-)tethered TWRP package for our ZenFone 2 (confirmed on ZE551ML and ZE500ML)!
!!! NOTE: If you want to apply a new OTA update, please flash stock recovery first !!!
Also, if you encounter any errors with the official recovery by TeamWin, please don't ask for support here as this is an unofficial build (done with the hard work of many people collaborating in a great manner!)​
If you don't want to unlock your Bootloader, you can use the tethered recovery.
Tethered (=after a reboot everything is back to normal)​
Features:
- Compiled with CM12 sources (although CM12 and TWRP are not liking each other very much :silly: )
- Optimized for x86 (smooth UI now)
- internal and external storages are mounted correctly
- Backup of boot, system, cache and data possible
- Full Crypto and SELINUX support
Bugs:
- Sometimes Backup and Restore hang. Fortunately it doesn't begin these operations so you don't brick your device (any hints on this are welcome!)
- USB Storage mount doesn't appear to work at all (pretty sure I took the correct path to the LUN file)
How to use:
- Download the tethered CWM package from here (method 2): http://forum.xda-developers.com/zenfone2/general/root-newbie-root-instructions-zenfone-2-t3114063
- replace the recovery.zip in "CWM_Zenfone_2_IntelFB_RecoveryLauncher" with the one you can find in the download section
- start the procedure by using cai_dat_CWM.bat
- type ACCEPT (case sensitive!) and enter
- type T4 and enter
- Set your timezone when booting the first time into the Recovery, maybe this fixes the backup and restore bug (needs to be done just once)
- Unplug your USB cable from the device, too, before flashing, backing up and/or restoring
Untethered (=permanent recovery)​
Features:
- Compiled with CM12 sources
- Optimized for x86 (smooth UI now)
- internal and external storages are mounted correctly
- Backup of boot, system, cache and data possible
- Full Crypto and SELINUX support
- kernel compiled dynamically (thanks to @crpalmer and @jrior001 and all involved for their fantastic work) with permissive Selinux
- USB-OTG support added (Beta supports NTFS file systems)
- Splashscreen can be backed up (to fiddle around and create your own)
- img files flashable now via recovery (thanks to @cangcan, @yakub234go and @vampirefo)
- F2FS support on kernel side
Drawbacks:
- MTP doesn't work
How to use:
Method 1
Get root rights
Unlock your bootloader
Download twrp.img from the download section and put on sd card (or pick the beta version for NTFS support)
Fire up adb or install a terminal emulator and type:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/by-name/recovery
reboot recovery
Method 2
Download twrp.img from the download section and put in your adb/fastboot directory
Unlock your bootloader
Boot into bootloader (turn off, keep Vol+ pressed and press the power button until it vibrates - then release ONLY the power button and keep volume up pressed until you see the fastboot GUI
Open up fastboot on your PC and type:
Code:
fastboot flash recovery twrp.img
Then press vol down 2 times until "Reboot recovery" shows up and press power 1 time to boot into recovery
Method 3 (if you have an older version of TWRP already installed)
Place img on your internal sdcard, then reboot to recovery, click install zip, then select "Images..." in bottom right, then you see the img. Tick "Recovery" afterwards and then on OK.
Download folder:
Gone
Cheers!
Credits
@social-design-concepts for the great tethering method and the brilliant support and guidance :good:
@vampirefo also his support and guidance :good:
@updateing for the link to the commit for x86 pixelflinger
@jrior001 and @crpalmer for the great work on the kernel source
etc. etc.
Special thanks:
@Drew442 Thanks for the contribution!
Amir J. - thank you too!
TeamWin for their great recovery
XDA:DevDB Information
[RECOVERY][LOLLIPOP ONLY] (Un-)tethered TWRP 2.8.7.0 for Asus ZenFone 2 (x86), Tool/Utility for the Asus ZenFone 2
Contributors
TheSSJ, social-design-concepts, vampirefo, updateing, crpalmer, jrior001, knoneNull, etc etc
Source Code: https://github.com/TheSSJ/device_asus_zenfone2
Version Information
Status: Stable
Current Stable Version: 21_f2fs
Stable Release Date: 2015-07-02
Created 2015-06-04
Last Updated 2016-09-24

Update 07-02-2015
ADB sideload works now (thanks @jrior001 & @crpalmer)! Make sure to download the latest ADB version: http://forum.xda-developers.com/showthread.php?p=42407269, credits for this to @shimp208
Update 06-30-2015
NTFS Support tested extensively and proved to be stable (not elegant, but functional)
Added recovery partition back to recovery.fstab to make it flashable via recovery itself
Update 06-28-2015
Moved to stable state
Added Beta version for NTFS support (twrp_ntfs.img)
Update 06-23-2015b
Upgraded source to TWRP 2.8.7.0
Update 06-23-2015
Functional TWRP with fast wipe/restore (-DNO_SECURE_DISCARD, thanks crpalmer)
ADB works
Just have fun in fiddleing around with the recovery
If no bugs will be reported we can declare this recovery stable
Update 06-10-2015
Boardconfig parameters changed, seems to back up, restore and flash even with USB cable attached
Update 06-04-2015b
Rolled back to 2.8.5.0 as restoring threw out the error that system was not being able to mount rw
Everything works now!
Update 06-04-2015
Built a version optimized for x86, fixes UI lags
Added Crypto Support again
Update 06-02-2015b
Removed TW_INCLUDE_CRYPTO flag as it caused backup operation to freeze
Update 06-02-2015
Moved to Beta stage
Fixed mounting of external SD
Update 06-01-2015
Completely reworked BoardConfig.mk
Removed all modules
Added @vampirefo 's adbd and adbd-recovery binaries from his TWRP builds (dunno why, but there aren't any binaries in my builds?) - thanks!
Graphics work now (still slow, need to fine tune with the correct boardconfig flags), no double backups, no flickering!
Update 05-31-2015
Included USES_ION flag into boardconfig.mk
Removed cpu temperature to reduce redraws
a little more stable now!

Nice I can't wait for the BL to be fully unlocked so we van get native TWRP.

Hello recovery or rest and it just temporary? thank you

jejemc said:
Hello recovery or rest and it just temporary? thank you
Click to expand...
Click to collapse
Hi,
yes, after rebooting no trace of TWRP is left
I have updated the zip now. It is a little stabler after I removed the CPU temperature, but still I have the feeling there are 2 GUIs sharing the same screen. Weird - I have to do more research - maybe I have to write my own UI updater...
Cheers

the gears are slowly moving! i hope BL gets unlocked by the time my ZF2 arrives..
is this for any ZF2 variant or just 551ML (4gb ram/2gb ram versions)?
thanks for taking the time with this (hopefully) awesome device!

This is awesome..thanks for your contribution! I am hoping for some custom roms..the stock ZenUI isn't the greatest :/

TheSSJ said:
Hi folks,
I managed to compile a tethered TWRP package for our ZenFone 2!
Click to expand...
Click to collapse
Do you have a link to your device repo?
Are there specific instructions for using it to build a tethered recovery (I'm familiar with building twrp, including within CM, but I haven't looked much into what the tethered exploit does to boot the recovery).

It seems I have successfully completed a Backup! As mentioned, the interface is painfully slow at times, but this is serious progress. Has anybody tried restoring a backup yet?

Could you please develop twrp or cwm for asus 450cg

NOTE:
1 backup successfully
2 Use Very lag
3 flash zip not work

crpalmer said:
Do you have a link to your device repo?
Are there specific instructions for using it to build a tethered recovery (I'm familiar with building twrp, including within CM, but I haven't looked much into what the tethered exploit does to boot the recovery).
Click to expand...
Click to collapse
Hi,
unfortunately I don't have any. Basically I wrote a BoardConfig.mk based on the data provided by the Nexus Player (Asus Fugu, which is also Intel based). Then I took 2 modules (one for the display and one for the support of exfat partitions) and compiled a normal TWRP. The output folder holds the compiled img as well as the ramdisk in a simple folder. I put the ramdisk content into a simple zip file and included an update-script to have it unpacked properly. What the recovery-trigger exactly does is not clear to me. It seems it temporarily overwrites the logcat binary with itself and then gets executed at a reboot directly. The recovery trigger just unpacks the zip and executes the recovery binary if I understood correctly.
If you want I can upload my device configuration, it's better if there are more ppl looking at this
29y6145 said:
NOTE:
1 backup successfully
2 Use Very lag
3 flash zip not work
Click to expand...
Click to collapse
Thanks for the feedback!
2. Yeah, the lags are a pain, also because it seems to execute every touch twice and I don't know how to fix this at the moment (maybe it is sufficient to increase the time to determine when a longpress is executed and when a normal touch is done, but this is strongly theoretical.
3. I tested flashing a zip and it does work, which error message do you get?
Anyways, today is a new day, so I will get to work on this (I am on vacation right now fortunately).
Cheers!

TheSSJ said:
Hi,
unfortunately I don't have any. Basically I wrote a BoardConfig.mk based on the data provided by the Nexus Player (Asus Fugu, which is also Intel based). Then I took 2 modules (one for the display and one for the support of exfat partitions) and compiled a normal TWRP. The output folder holds the compiled img as well as the ramdisk in a simple folder. I put the ramdisk content into a simple zip file and included an update-script to have it unpacked properly. What the recovery-trigger exactly does is not clear to me. It seems it temporarily overwrites the logcat binary with itself and then gets executed at a reboot directly. The recovery trigger just unpacks the zip and executes the recovery binary if I understood correctly.
If you want I can upload my device configuration, it's better if there are more ppl looking at this
Thanks for the feedback!
2. Yeah, the lags are a pain, also because it seems to execute every touch twice and I don't know how to fix this at the moment (maybe it is sufficient to increase the time to determine when a longpress is executed and when a normal touch is done, but this is strongly theoretical.
3. I tested flashing a zip and it does work, which error message do you get?
Anyways, today is a new day, so I will get to work on this (I am on vacation right now fortunately).
Cheers!
Click to expand...
Click to collapse
If you can upload the device config to github I can try to take a look tonight or tomorrow and see if I can see anything wrong that would explain your "double ui".
Either way, it is good to upload it as you'll have a history saved of when it last worked if you screw it all up!

TheSSJ said:
Hi,
unfortunately I don't have any. Basically I wrote a BoardConfig.mk based on the data provided by the Nexus Player (Asus Fugu, which is also Intel based). Then I took 2 modules (one for the display and one for the support of exfat partitions) and compiled a normal TWRP. The output folder holds the compiled img as well as the ramdisk in a simple folder. I put the ramdisk content into a simple zip file and included an update-script to have it unpacked properly. What the recovery-trigger exactly does is not clear to me. It seems it temporarily overwrites the logcat binary with itself and then gets executed at a reboot directly. The recovery trigger just unpacks the zip and executes the recovery binary if I understood correctly.
If you want I can upload my device configuration, it's better if there are more ppl looking at this
Thanks for the feedback!
2. Yeah, the lags are a pain, also because it seems to execute every touch twice and I don't know how to fix this at the moment (maybe it is sufficient to increase the time to determine when a longpress is executed and when a normal touch is done, but this is strongly theoretical.
3. I tested flashing a zip and it does work, which error message do you get?
Anyways, today is a new day, so I will get to work on this (I am on vacation right now fortunately).
Cheers!
Click to expand...
Click to collapse
Is your problems due to recovery or modules you added? My tethered twrp doesn't have the problems yours does, so I wonder if it's the modules, your packaging perhaps and not the recovery?
Sent from my T1 using Tapatalk

TheSSJ said:
- Slow graphics, according to @Dees_Troy: "The graphics are a bit laggy because pixelflinger is not very well optimized for x86"
Click to expand...
Click to collapse
Dees_Troy is lying. TWRP graphic engine isn't optimized for any architecture. Even on my SGS4 (ARM) it's slow as snail. Higher resolution - more slower. I see, they've added some code for Qualcomm overlay support. I didn't try it yet, but support only for one CPU manufacturer is nothing. Especially, there is another way to accelerate at around 1000% by SIMD instuctions. Although i've liked TWRP originally, i see developers have no intentions to improve graphics which is the key feature. So, i've decided to throw away TWRP and look at Aroma File Manager.
It has very fast graphics engine with ARM NEON optimization (and with some effort it become SSE4.2 optimized). The only feature missing is backup/restore, but i'm working on that. Actually, Backup/Restore works now. Just thinking about better backup format.

sorg said:
Dees_Troy is lying. TWRP graphic engine isn't optimized for any architecture. Even on my SGS4 (ARM) it's slow as snail. Higher resolution - more slower. I see, they've added some code for Qualcomm overlay support. I didn't try it yet, but support only for one CPU manufacturer is nothing. Especially, there is another way to accelerate at around 1000% by SIMD instuctions. Although i've liked TWRP originally, i see developers have no intentions to improve graphics which is the key feature. So, i've decided to throw away TWRP and look at Aroma File Manager.
It has very fast graphics engine with ARM NEON optimization (and with some effort it become SSE4.2 optimized). The only feature missing is backup/restore, but i'm working on that. Actually, Backup/Restore works now. Just thinking about better backup format.
Click to expand...
Click to collapse
tar is the best.
Sent from my T1 using Tapatalk

vampirefo said:
tar is the best.
Sent from my T1 using Tapatalk
Click to expand...
Click to collapse
I know. The problem is how to split the archive. Currently i split by size. In this case you cannot use parts independently. For example, if you want to extract some file, you have to concatenate whole backup first and then extract.
The better way is to split tar at header boundary but so far in many decades of years nobody created such split tool. Also, if there is a file bigger than desired part size, it won't be split and may even produce error if target disk (where backup is saving to) is FAT and file size is bigger than 4GB (extreme case).

sorg said:
Dees_Troy is lying. TWRP graphic engine isn't optimized for any architecture. Even on my SGS4 (ARM) it's slow as snail. Higher resolution - more slower. I see, they've added some code for Qualcomm overlay support. I didn't try it yet, but support only for one CPU manufacturer is nothing. Especially, there is another way to accelerate at around 1000% by SIMD instuctions. Although i've liked TWRP originally, i see developers have no intentions to improve graphics which is the key feature. So, i've decided to throw away TWRP and look at Aroma File Manager.
It has very fast graphics engine with ARM NEON optimization (and with some effort it become SSE4.2 optimized). The only feature missing is backup/restore, but i'm working on that. Actually, Backup/Restore works now. Just thinking about better backup format.
Click to expand...
Click to collapse
@Dees_Troy actually is not lying pixelflinger_static isn't optimize for x86 and Intel used to add libenc to speed up pixelflinger a little, intel later decided to use the more recent version of libminui cause it doesn't use pixelflinger_static and from what i read it a whole lot faster. i imagine @Dees_Troy and team-win are looking into moving away from pixelflinger because of it's draw backs but that is a very big task.
i plan to build against the windriver android-5.0.0_r2.0.1 source this evening cause it includes the icc tool chain when i built the new recovery.launcher against it , it was much much much much much faster hope it has the same affect on twrp

vampirefo said:
Is your problems due to recovery or modules you added? My tethered twrp doesn't have the problems yours does, so I wonder if it's the modules, your packaging perhaps and not the recovery?
Sent from my T1 using Tapatalk
Click to expand...
Click to collapse
I assume maybe I am missing some modules. There is a .ko file named fps_throttle...this led me to the conclusion that maybe the framerate is awefully high (or awefully low ), which could explain this flickering text maybe...
I will include all of the modules in my next build to see if it works better, thanks for the tip!

social-design-concepts said:
@Dees_Troy actually is not lying pixelflinger_static isn't optimize for x86
Click to expand...
Click to collapse
I think, you've missed the point. I've said current TWRP graphics isn't optimized for ALL platforms (besides very specific Qualcomm overlay which i had no chance to try). Nothing to do with x86. Even on ARM device it's very slow. In several years of TWRP existence, i didn't see any progress in GUI, so i don't hope it will be changed anytime soon.
From other side, Aroma File Manager uses NEON(which can be translated to SSE) optimization making interface very fast. Thus, you don't need any special compiler. But due to very different internal GUI engines, it's hard to port TWRP to Aroma GUI. Using 3rd party compiler give you other problems if you try to compile something requiring Android NDK.
Anyway, let me know if your approach with different compiler will make rocket from snail TWRP GUI

[RECOVERY][TREBLE] TWRP 3.2.3-0L v1.3 Labs Mod for the ZTE Axon 7

- T W R P 3.2.3-0L [Labs Mod] -
The Swiss Army Knife TWRP Mod for the Axon 7​
INTRODUCTION
This was a long term project that I have been using for a long time. I created some scripts to make it easier and faster to flash new roms and quickly restore the daily driver configuration after a testing session. For easier access I modified the TWRP interface to add direct access to the scripts. They had many problems but they were good to me since I created them and I knew how to used them well, but they were not ready for other users.
But the time has come and I have cleaned up most of the annoyances in the tools and in the UI. I have named it "Labs Mod" since it allows me to have my flashing lab on the go, making it extremely easy to switch to different configurations, or recover the daily driver configuration in a few minutes. I believe it is free of major bugs and now I can concentrate on adding new scripts, and more options to the current scripts.
FEATURES
On top of the latest improvements introduced in the official TWRP 3.2.3-0, this mod offers the following added features:
Full vendor partition support (mount, format, wipe, partition image flash, TWRP backup and restore).
Integrated Bootstack backup and restore.
Modem firmware image flash
Reboot to EDL
Button to enable device mapper verity (DM-Verity) enforcing
Button to disable the eMMC write protection (disemmcwp)
Backup/Restore internal storage to the TWRP Backup folder in the external SD. Ensure you have enough free space, free space check is not yet implemented.
EDL backup zip creation. Dual zip use since the resulting zip can be installed using TWRP from the phone or using MiFlash from the computer. It offers the following package creation options:
OS: Operating system (boot, vendor and system).
GPT: Partition table only.
CONFIG: Device config data (IMEI, SN, MAC, etc).
BOOTSTACK: Boot firmware without modem.
MINIMAL: Includes GPT+bootstack+modem+recovery.
EMERGENCY: Minimal + device config.
FULL: Minimal + OS.
FACTORY: Includes Full + config.​
Integrated Treble PARTY tool for creating and removing the vendor partition. Vendor partition is required for Treble ROMs. Removal is required for flashing old non-treble roms.
Lockscreen security removal. Removes password, pattern, fingerprint, etc... (in case you forget your password or the security descriptor gets corrupted).
Google account binding removal (in case you want to wipe from within recovery and test with different google accounts).
Bootloader unlock message removal.
New! Expand OS partitions (Vendor and System) to fit the whole partition. Useful for expanding the GSI filesystem for having space for adding GApps or moving apps to system.
New! Deep Wipe function performs a low level wipe of the partition data, erasing the remaining the portions of the eMMC that stored the partition information.
REQUIREMENTS
You need an unlocked Axon 7
INSTALLATION
WARNING, THIS SOFTWARE COULD WIPE ALL THE DATA IN YOUR DEVICE, INCLUDING THE INTERNAL STORAGE.
IT REQUIRES TWRP CUSTOM RECOVERY IN AN UNLOCKED DEVICE, OTHERWISE YOUR DEVICE COULD BE BRICKED.
!!! Whatever you do, it is at your own risk !!!​
Follow these steps:
1. Download the TWRP Labs Mod image to your External SD card.
2. Boot to TWRP and select the Install option in the main manu.
3. Tap on the install image button and select your external SD. select the image file you downloaded, select the recovery partition and confirm.
4. Reboot to recovery again to ensure the changes are applied properly.
DOWNLOAD
TWRP_3.2.3-0L_v1.3-Axon7-Labs_Mod.img Flavor of the mod using the official TWRP 3.2.3-0 Kernel binary (Quick boot even when using F2FS, full ADB support, NO B12 Oreo encryption). Use this if you do not plan on using device encryption. Please note that you won't be able to use any tool of this version if your device is encrypted.
TWRP_3.2.3-0L_v1.3.B12-Axon7-Labs_Mod.img Device encryption enabled flavor of the Labs mod. It use the 3.2.1-8 TWRP Kernel binary (Long boot when using F2FS, NO ADB support, B12 Oreo encryption). Use this one if you use device encryption. Please note that this flavor doesn't support adb interface.
NOTES
1. I do not have the time and expertise to dig into kernel hack so this is why I do not provide a unified kernel with fast F2FS boot, ADB and B12 encryption. Probably people developing kernels could help on this issue. It would be nice having a kernel with proper F2FS boot support, B12 encryption and ADB interface. Until then, there is no other way than having 2 flavors depending on the features we require.
SOURCES
C'mon, all of them are scripts!!! the sources are at glance. Use them in your projects but don't forget to give credit to the source !!!
CREDITS
@NFound for the recovery kernel binary supporting Oreo B12 encryption.
@someone755 for the keycheck binary I use in my scripts.
@Chainfire for the TWRP install script hacks.

I hope you enjoy it as much as I did creating and learning throughout the enlightenment journey.

Nice.
Any info on the scripts that are included?

voetbalremco said:
Nice.
Any info on the scripts that are included?
Click to expand...
Click to collapse
Well, all of them are Bourne shell scripts. Some of them are stupidly simple such as those in the Reboot menu, and others in the Advanced > Oki Labs menu are very elaborated, specially:
- PARTY tool: for creating and removing the vendor partition. I released it a few days ago as a separated tool that could well work in other devices.
- EDL backup: for creating EDL flashable backups of a configuration. This tool will probably require a full thread due to the concepts involved. The big feature is that the generated zip can be also flashed using any TWRP.
- Internal Storage Backup/Restore: TWRP doesn't offer a straightforward solution for backing up the internal storage, since it is excluded from the data backup, now it is possible to create a backup and restore the contents of the internal SD in case you want to mess up with the userdata partition. Now this script creates a set of files under the TWRP/backup folder. I am planning to add the possibility of having different backup folders, the same way the GUI treats the data partition.

That is looking very sweet!!!
I'm excited, nice work man!

This is just fantastic!

Well, the non b12 version can't decrypt my device, running los 15.1
also, the lab options did nothing, and when I pressed on PARTY the recovery froze on me.
Hmm.

nfsmw_gr said:
Well, the non b12 version can't decrypt my device, running los 15.1
also, the lab options did nothing, and when I pressed on PARTY the recovery froze on me.
Hmm.
Click to expand...
Click to collapse
Well, that's why in the OP I provide 2 flavors of the mod. If you require decrypt then you have to use the B12. PARTY will not work either if your device is encrypted and you are using the 3.2.3-0L. In your case, using device encryption, you have to use the 3.2.3-0L(B12). You will have all the functions except for ADB. PARTY will work fine too.

Oki said:
Well, that's why in the OP I provide 2 flavors of the mod. If you require decrypt then you have to use the B12. PARTY will not work either if your device is encrypted and you are using the 3.2.3-0L. In your case, using device encryption, you have to use the 3.2.3-0L(B12). You will have all the functions except for ADB. PARTY will work fine too.
Click to expand...
Click to collapse
Got it.
I thought the B12 version was for stock-based ROMs.
Okay I'll flash the other one once I get home, thanks.

nfsmw_gr said:
Got it.
I thought the B12 version was for stock-based ROMs.
Okay I'll flash the other one once I get home, thanks.
Click to expand...
Click to collapse
I'll clarify it a bit more to avoid any misunderstanding. Sorry about that.

Oki said:
I'll clarify it a bit more to avoid any misunderstanding. Sorry about that.
Click to expand...
Click to collapse
Thnx for this tool ! I'll test that this weekend.
It would be great if you'd make a small guide on this with a couple of situations / a possible indepth review with screens / what's possible and what's definitely not possible with this twrp tool.
Anyway seems very promising :good:

Sheesh...i have no external sd card

I have garde flashed your TWRP_3.2.3-0L (B12) -Axon7-Labs_Mod.img but this version says when starting in twrp that my password is wrong. the version 3.2.1.8 of nfound unlocks my password quite normal

Excellent Job! I can't wait to get back my Axon 7 from RMA Services. I'm just going to need sometime to get this running coming from stock MIflavor.

Found bug. Installed the ADB version (thanks Cthulu!), wanted to check the functionality.
Went into the Storage Backup and my phone froze. Rebooting from ADB worked.
EDIT: tried to reproduce the issue - same thing happened 2nd time.
EDIT2: It freezes at any option in Oki Labs

docentore said:
Found bug. Installed the ADB version (thanks Cthulu!), wanted to check the functionality.
Went into the Storage Backup and my phone froze. Rebooting from ADB worked.
EDIT: tried to reproduce the issue - same thing happened 2nd time.
EDIT2: It freezes at any option in Oki Labs
Click to expand...
Click to collapse
I can't duplicate the issue. Are you sure you downloaded it properly? Do you have an SD card? The backup requires an SD card with enough space. Checking for free space is in the todo list for this weekend.

raystef66 said:
Thnx for this tool ! I'll test that this weekend.
Anyway seems very promising :good:
Click to expand...
Click to collapse
Not good enough!

It is downloaded properly. SD card has more than 100gb free space.
As mentioned in edit it is any option that I used in Oki Labs menu that froze my phone

docentore said:
It is downloaded properly. SD card has more than 100gb free space.
As mentioned in edit it is any option that I used in Oki Labs menu that froze my phone
Click to expand...
Click to collapse
What option are you testing? the Storage Backup? What format are you using in your SDCard? Does it happen at the beginning or after a while? Is there any file under TWRP/BACKUPS/STORAGE in your Micro SD after the failure?

@Oki this is amazing. Thank you.
Is it possible to use the recently released kernel sources from los15 to solve the issue of needing two revisions?

[ROM][OFFICIAL][fajita][10.0]crDroid Android[v6.27]

{
"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"
}
​
crDroid is built on top of LineageOS, and is designed to increase performance and reliability over stock Android for your device, while also attempting to bring you many of the best features in existence today.
Features
A quick glossary and primer on slots for A/B devices (like ours):
Spoiler: Show/Hide
- "Clean flash": Removing device protection & clearing user settings before installing a bootable system install zip (usually by either wiping or formatting data, see below).
- "Dirty flash": Flashing a ROM zip (usually upgrading to new version, sometimes just re-flashing the existing one) without wiping data or anything first.
- "Wipe data": Synonymous with "factory reset", accomplished from TWRP recovery by selecting "Wipe", then performing the "Slide to factory reset". Clears user data without erasing any partitions, removing encryption, or deleting contents of internal storage.
- "Format data": Formats the data partition itself, resets all file-based encryption keys, loses all contents of internal storage, and in fact deletes all "user 0" directories (this has some implications for internal storage before & after first boot).
- "User 0" directories are a series of directories that store userdata for the primary user, "Owner", and get created in various places throughout the filesystem on first system boot if they don't exist already. Anything you copy to "internal storage" while booted in recovery after "formatting data" will actually be copied to /data/media/ instead of /data/media/0/, and will become invisible to regular file browsing after first boot once the system has created /data/media/0, since the system will prefer to use that path for internal storage from then on (so you'll need a root file browser to delete things from /data/media, or just ADB sideload things instead of copying after formatting but before booting).
- "OTA package": Originally an abbreviation for "over the air", referring to how a software update could be delivered (as opposed to having to take your phone to a carrier's store for a firmware update via serial/USB connection). The common usage in Android circles is any installation zip file that actually includes a bootable system.
- Some partitions are duplicated (system, vendor, boot, and probably a couple others, but not data) and have a "slot A" & "slot B" copy.
- "Slot A" and "slot B" are absolute designations, but most installer zip scripts use the relative designations: "active" and "inactive". Whichever slot you're booted from currently is "active", and the other one is "inactive".
- Installing a zip file that's flagged as being an OTA package will 1) install the contents to the "inactive" slot, and then 2) flag the bootloader to switch which slot is considered "active" (and booted from) and "inactive" upon next reboot.
- The OxygenOS full OTA zip files and all custom ROM installer zip files are considered "OTA packages" and will trigger a slot switch on next boot after installation.
- You can install multiple OTA zip packages one after the other without rebooting in TWRP; they will all get installed into the correct partitions in the "inactive" slot, one on top of the other, and then it will swap active & inactive upon reboot.
- We don't use what are called "delta" updates, which can patch existing partitions by block or by file; we use full filesystem images. So for us, OTA zip packages are really just a bunch of partition filesystem image files all wrapped up into a "payload.bin" with some extra instructions & metadata/checksums, so when you flash a ROM, it overwrites entire partitions at a time instead of individual files or filesystem blocks within that partition. So if you've changed something in a partition like system that gets written as part of flashing an OTA zip, all your changes are gone. The only thing in the system partition afterward will be what was in the system.img that was included in the ROM zip payload.
- The partitions that crDroid, LineageOS, and most custom ROMs for OnePlus 6 & 6T install to when flashing are boot (contains recovery & kernel), dtbo, system, and vbmeta. Some ROMs (like Syberia) build the vendor partition from source instead of just trying to work with the existing OEM vendor partition, so they flash that one too when installing. So you definitely need to flash stock vendor before switching from Syberia or another source-built vendor ROM to one like Lineage or crDroid that uses prebuilt.
- "Prebuilt vendor" vs. "source-built" vendor partitions: when first trying to get a custom ROM working on a new device now that we have separate system & vendor partitions & Google's "Project Treble" is a thing, you'll often just leave the contents of the vendor partition alone, because that's where all the proprietary or device-specific stuff lives (manufacturer specific hardware drivers & interfaces, any DRM libraries, custom frameworks & selinux policies for talking to them), and you make a compatibility map of what framework versions you're compiling against in system and what vendor version they're compatible with or supersede or you overlay updated things that should replace stuff in the vendor partition and keep it in system_ext instead. But you're also limited in that if there are some things in vendor, you CAN'T work around it from the ROM side (like, OnePlus Camera working correctly). So often, once the basics are functioning, the goal is to move to building the contents of the vendor partition from source, because you then have the freedom to fix problems with sepolicy, library/framework mismatches, etc. and make things work with the custom ROM instead of only working with the OEM's flavor of Android, and you can still copy individual pre-compiled files from the stock vendor filesystem image if needed (like if there's no open-source equivalent for some driver). Unfortunately, OnePlus SDM845 (enchilada & fajita, the OP6 & OP6T) never got a proper source-built vendor bringup by the LineageOS team (upon which crDroid is based). And while Syberia has had source built vendor in Android 11 (possibly 10?), it was only done for enchilada and NOT fajita, it's not trivial to unroll & commonize what they've done to apply to other ROMs, and some of the proprietary files they keep are imported from other similar devices/similar chipsets rather than source-built (presumably because the OnePlus ones are modified in a weird way that the open-source components can't hook into, but still not ideal). So for fixing a lot of the issues we still face with lack of things working quite right, or hardware features not available in custom ROMs (especially compared to newer OnePlus devices like the 7, 8, or 9 series), we're kinda stuck, because you can't just implement it against the stock prebuilt vendor.
- "Updating firmware" simply means we're flashing updated contents from the manufacturer into all the OTHER partitions besides the ones that the ROM OTA zip touches. There are another dozen or more of those, besides system & boot, that the full OxygenOS OTA zip would normally write to when you install it. The contents of the system partition in custom ROMs for our device are generally built against a particular version of OxygenOS (mostly the contents of the OEM vendor partition).
Prerequisites:
- Make sure your bootloader is unlocked (and don't plan on relocking it ffs).
- Make sure you have a reasonably-current, working installation of android platform tools (adb & fastboot command line binaries & necessary drivers) on your computer, with a known-good USB cable (see links in post #2).
- Make sure you've downloaded the most recent full Android 10 OxygenOS OTA installer zip (10.3.12), crDroid zip, matching crDroid boot.img, official TWRP 3.5.2_9-0 installer zip and bootable img, and whatever Magisk/GApps/microG installation packages you want to use to your computer (see links in post #2).
- Make sure you've backed up whatever data you want to keep to somewhere that's not on your phone; for a new install, we're going to format the data partition and you're going to lose everything from internal storage.
Let's get started!
Updating firmware (if already on crDroid):
- Reboot to bootloader (with no USB cable connected).
- Open a terminal on your computer, and run `fastboot flash boot path/to/boot.img`, substituting in the path & filename for the current crDroid boot.img that you downloaded as part of the prerequisites.
- Reboot to bootloader again (actually loads new bootloader that you just flashed).
- Use Vol +/- buttons to select "Recovery mode" and press Pwr button to boot into the built-in TWRP recovery. The device's internal storage should now be available for read/write on the computer via MTP.
- Copy the official OxygenOS 10.3.12 full OTA zip & latest crDroid zip into the device's internal storage, then choose "Install", select the current crDroid zip, choose "Add more zips", and crDroid installer zip, then swipe to confirm flash. No TWRP zip required, since it's built in to the boot.img that gets installed.
- Reboot recovery, then choose "Install", and select the OOS zip, then select "Add more zips" and choose the crDroid zip, and swipe to confirm flash again.
- Reboot recovery, and re-flash magisk/gapps if needed.
- Wipe dalvik.
- Reboot system.
First time installing crDroid to your OP6T, coming from stock OxygenOS or another ROM (will also update firmware while we're at it):
- Reboot to bootloader, then `fastboot boot path/to/twrp.img` to start up into TWRP recovery.
- Mount System partition read-write, use file manager to delete the /system/addons.d/ directory if it exists, unmount System.
- Choose Wipe > Format data, type "yes" and hit enter to nuke everything in the data partition and clear encryption.
- Choose Advanced > ADB sideload (don't worry about selecting cache/dalvik wipe options yet) and then on the computer, do `adb sideload path/to/OxygenOSOTA.zip` to flash the OxygenOS 10.3.12 full OTA installation zip & make sure you're on the latest Android 10 firmware.
- Go get a drink, this'll be a bit.
- When that's done, hit "back" in TWRP and start ADB sideload again, and this time send the crDroid installation zip (includes TWRP built-in, so don't need separate zip for that at this point).
- Reboot to recovery (this will switch the active slot to use the system partition you just installed those zip files into).
- Wipe data (Wipe > "Slide to factory reset" in TWRP).
- That was so much fun, let's do it again! ADB sideload OxygenOS full OTA zip.
- ADB sideload crDroid zip.
- Reboot to recovery (switches slots again, now we have latest OxygenOS firmware plus crDroid populated in both sets of partitions and won't have to do that again).
- Flash Magisk (if desired).
- Flash GApps or microG package (if desired).
- Wipe dalvik.
- If you copied anything to internal storage instead of flashing it via ADB sideload, delete it now before first boot.
- Reboot system.
- Go through setup wizard.
- Reboot system (for reasons I don't comprehend, it never shows "OnePlus Settings" in the Settings app top level menu on a fresh install until after rebooting once).
- It's gonna harass you to finish setup, go ahead and customize everything to your heart's content.
Updating crDroid from TWRP (preferred):
You don't need to remove device protection; it works fine with PIN. Be sure you have a PIN set, or have looked up whatever that arcane chart of pattern > numeric incantations in case of pattern unlock. It's awful.
- Boot into TWRP recovery.
- Choose install, then select OOS firmware OTA (if needed), then choose select additional zips, then select crDroid.zip, slide to confirm flash.
- Reboot recovery.
- Choose install, then select Magisk zip (if using), select additional zips, choose GApps/microG (if using), slide to confirm flash.
- Please keep off of the grass, shine your shoes, wipe your... dalvik.
- Reboot system.
Updating crDroid from Updater app:
Warning: I don't remember if crDroid 6 even *has* the built-in Updater app function or not, or how well it handles addon.d survival scripts. Use with caution.
- Install update in built-in Updater app (Settings > System > Updater), do NOT reboot yet.
- Go to Magisk app home, click "Install" next to Magisk, and choose the "Install to Inactive Slot (After OTA)" method.
- For GApps/microG: If you use GApps/microG that needs to be re-flashed to /system (as opposed to magisk module GApps/microG), reboot *recovery* at this point, mount the system partition in TWRP, and dig around with the File Manager in system/priv-app/ & system/product/priv-app/ to make sure that everything you expect was copied over to the now-currently-active slot, and if need be re-flash your installer zip, or else your world will be pain when you boot normally. Yes, I expect you to know what your preferred package installs & to keep the zip handy.
- NOW you can reboot to system.
Reporting bugs:
I'm a parent of three young kids whose industry disappeared in the pandemic and is now full-time house husband & parent-in-charge while my wife is teaching full-time, I'm trying to save my small live-event-turned-streaming-studio company in my spare time. I'm doing in-home caregiving for a family member overnight one day a week. This is the back-up spare-spare-time hobby. I'm not a software developer nor do I know any programming languages, I just wanted a ROM with signature spoofing support and more customization than the unofficial microg-compatible LineageOS builds. So if there are bugs or feature requests, I go over to the crDroid dev chat and ask if someone has time to hold my hand & help. Don't make me get yelled for annoying them, mmkay? That said...
- Logs/screenshots/recordings or it didn't happen. Syslog (free, open source, available on Play store and F-droid) is your friend.
- I try to keep an organized notebook of roadmap, feature reqeusts, bug reports, etc. I won't always be able to fix it, but I'll at least look and do my best to ask the actual devs.
- I don't sign into XDA much, so if I haven't said anything, check out the Telegram group. Lots of helpful folks there.
- Please keep your questions in this thread instead of PMing me with them directly, so that the entire class can benefit from the discussion and you can find out if it's just you or if this is a widespread issue.
It's your device to use the way you want of course, and I use Magisk & microG and like to tweak things myself. But don't expect much support if you:
- didn't do a clean flash.
- aren't using the built-in kernel.
- are using extensive modifications (besides Magisk) like Xposed/Riru, Dolby Atmos, Viper4A, etc.
- immediately start using "finalize.zip" or flashing migrate restore zips instead of following the actual instructions.
- are running decrypted.
Donate - Support development!
crDroid Website - Download here!
Telegram Oneplus6/6t group - Share your best cat pictures!
Source Code:
- Device tree: https://github.com/crdroidandroid/android_device_oneplus_fajita/tree/10.0
- OP6/6T Common device tree: https://github.com/crdroidandroid/android_device_oneplus_sdm845-common/tree/10.0
- OnePlus Common device tree: https://github.com/Terminator-J/crdroid_device_oneplus_common/tree/10.0-test
- Kernel: https://github.com/crdroidandroid/android_kernel_oneplus_sdm845/tree/10.0

Notes:
- Yes it supports package signature spoofing permission for microG compatibility out of the box (but will work without ANY GApps/microG implementation installed as well).
- Aux camera doesn't work correctly due to framework issues beyond my control/comprehension. So, still no portrait mode in OnePlusCamera in cr6. But 60fps video recording in OOSCam works great; huzzah!
- Doesn't pass safetynet out of the box, despite many tests with different fingerprints/props. Just use Magisk & enable the Zygisk DenyList & kdrag0n's "safetynet-fix" module and be happy. If your bank's app doesn't work, switch to a local credit union and stop feeding the bougie bankers. Smash capitalism!
- Maintainer does not use GApps, so cannot answer questions about which packages work best from firsthand experience. In general, go with the smallest package you can and then install other Google apps from the Play Store. Please note that if you replace the stock dialer with Google Dialer, you may lose access to the Phone Info menu (*#*#4636#*#*) until you install another dialer. For recommendations, see https://wiki.lineageos.org/gapps.
- Requires OOS 10.3.12 OOS firmware.
- Includes built-in TWRP, pulled from official 3.5.2_9-0 ramdisk, works well.
- Tested against latest Magisk canary (with zygisk instead of magiskhide), works well.
- No there won't be official builds with inline GApps; please don't ask.
crDroid 6.27 - February 2022 ASB release notes/known issues:
Changelog since v6.23 release:
- Merged Android Security Bulletins through February 2022 from upstream.
- Whatever changed upstream in the ROM proper (not likely much; they want to freeze it besides security updates).
- Reimplemented DeviceSettings based on crDroid 7 version (no more greyed-out things that don't actually work in Android 10).
- Backported updated display panel handling in device tree and kernel to match crDroid 7 (panel color modes are in LiveDisplay now). FOD on fajita is still kinda crap with OOS 10 firmware, but oh well.
- Little more tidying/tightening in device tree & kernel for moving to maintenance-only releases.
- Imported current wireguard VPN kernel-mode driver.
Known issues:
Fajita-specific:
- FOD seems to work kinda, um, crap compared to how it is on OOS 11 firmware. Not much I can do about that, unfortunately.
Common:
- Some screen-off gestures may not work, due to limitations beyond my control; don't use those gestures. Sorry.
- You tell me! With logs!
Other stuff:
- At this point, any little feature bugs will be considered "can't fix/won't fix"; I can't keep working on this one, I'm going to try to only do security-update-only releases of crDroid v6.
- Where do bad rainbows go? Prism. It's a light sentence.
Helpful links:
Download ROM
TWRP (use old official v3.5.2_9-0)
(TWRP is built-in to the crDroid 6 zip, but you might need the img or standalone installer zip in order to get to that point)
Magisk (use latest)
OxygenOS 10.3.12 Full OTA
MSMTool (oh now you're in trouble - use latest unless you have a good reason to intentionally downgrade)

first to test it...just flashing it...hope its better than every 10 rom that are available currently!!!!

It's early in development. They are all going to have that 'new car smell'. Lower expectations. Bare bones but stable is a milestone.

Hello everyone, firstly thanks Dev and team for your efforts developing CRDroid, question... where can I download android 10? Because the website only shows Pie downloads and 10 only says soon. Thanks guys and have a good day.

funnyquill said:
first to test it...just flashing it...hope its better than every 10 rom that are available currently!!!!
Click to expand...
Click to collapse
What's your thoughts?
Sent from my OnePlus6T using XDA Labs

oscarmaldonado said:
Hello everyone, firstly thanks Dev and team for your efforts developing CRDroid, question... where can I download android 10? Because the website only shows Pie downloads and 10 only says soon. Thanks guys and have a good day.
Click to expand...
Click to collapse
go to pie downloads, there you will find a 6.x folder to

All downloaded ready to flash when I get home
Thanks for the rom dev?

Let the game begin, I'm almost done restoring everything, clean flash including internal storage. It booted fine, no issues whatsoever, everything is running nice and smooth, wifi, wifi calling, Bluetooth, FP. Thanks Dev. and team.

So when I click on "wallpapers" on home screen, it says app isn't installed. So, is there any fix?

oscarmaldonado said:
Let the game begin, I'm almost done restoring everything, clean flash including internal storage. It booted fine, no issues whatsoever, everything is running nice and smooth, wifi, wifi calling, Bluetooth, FP. Thanks Dev. and team.
Click to expand...
Click to collapse
Looks like there's plenty of options/goodies under the crDroid settings.
Sent from my OnePlus6T using XDA Labs

L22EEW said:
Looks like there's plenty of options/goodies under the crDroid settings.
Click to expand...
Click to collapse
Yes there is, that's the reason I took that screenshot. Happy flashing bud.

Just superb work.. I am casual user.. Plays lot of games, YouTube and online streaming.. Seems pretty solid so far..

oscarmaldonado said:
Let the game begin, I'm almost done restoring everything, clean flash including internal storage. It booted fine, no issues whatsoever, everything is running nice and smooth, wifi, wifi calling, Bluetooth, FP. Thanks Dev. and team.
Click to expand...
Click to collapse
You have the weather on lockscreen option?
Sent from my OnePlus6T using XDA Labs

champagne66601 said:
You have the weather on lockscreen option?
Click to expand...
Click to collapse
No I don't, I just noticed it.

Will it work on Verizon?

L22EEW said:
Looks like there's plenty of options/goodies under the crDroid settings.
Click to expand...
Click to collapse
oscarmaldonado said:
Yes there is, that's the reason I took that screenshot. Happy flashing bud.
Click to expand...
Click to collapse
nikz106 said:
Just superb work.. I am casual user.. Plays lot of games, YouTube and online streaming.. Seems pretty solid so far..
Click to expand...
Click to collapse
Would you guys say this is the most "forwardly progressed" Android 10 ROM as of current?

Causical said:
Would you guys say this is the most "forwardly progressed" Android 10 ROM as of current?
Click to expand...
Click to collapse
With all due respect to other Devs. this is the one I like the most, lots of customizations compared to other android 10 roms, give a try I beat you won't be disappointed. This is my personal opinion. Happy flashing bud.

oscarmaldonado said:
With all due respect to other Devs. this is the one I like the most, lots of customizations compared to other android 10 roms, give a try I beat you won't be disappointed. This is my personal opinion. Happy flashing bud.
Click to expand...
Click to collapse
Yep just opinions is all I ask for, I don't care much for hierarchy, so not necessarily looking for one thing better over another, I just know 10's in the early stages and I'm not even thinking about jumping over yet, I just like to hear what people think.

Causical said:
Yep just opinions is all I ask for, I don't care much for hierarchy, so not necessarily looking for one thing better over another, I just know 10's in the early stages and I'm not even thinking about jumping over yet, I just like to hear what people think.
Click to expand...
Click to collapse
This is the first 10 rom worth staying on after testing the others I went back to pie might actually be on 10 for good now.

[OOS][Stable][OP6T Global][OP6T Tmobile] Oneplus 6T stable OOS guide thread

OOS stable for Oneplus 6T Global ​
This thread is an attempt to make things clean for OP6T users.
It will contain latest zip links for OOS stable.
It will contain a brief guide on how to root, install TWRP , how to update with or without those elements.
6T global edition is supported by thread readers and me, and T Mobile converted specific concerns will be handled by community under the supervision of @Scott, thanks to him for the help.
It will not contain basics like ADB and Fastboot connection with a computer. Experiment, read, there are many and many tutorials on the internet for that. Don’t forget there is a world outside XDA and that you can perform a search on any search engine to grab information.
It will not cover by decision the ‘patching boot.img’ method for gaining root. It’s not necessary to use it when we have a working TWRP and Fastboot. If you want to try it search on the internet about ‘extracting boot.img from payload.bin’ and then use Magisk Manager to patch it.
Please NO discussion about: Magisk itself, custom kernels, debloating (whatever method you want to use), custom ROMS… Only STOCK STABLE OOS.
If you just want to flash custom kernels, no need to have TWRP, Ex Kernel Manager and Franco Kernel Manager for example can take care of that (see Play Store to grab those apps), and backup your stock kernel.
ALWAYS USE LATEST VERSIONS of the different tools used. Don’t ask for help if you’re using 6 months old TWRP or Magisk. Update it first.
First a bit of what I have understood about our phone, and its main specificity, i.e A/B slots.
A/B slots, what else ?​
This structure is meant to enable to have two different versions of the SAME ROM, one slot will contain the previous version of the ROM, the other slot will contain the updated one. If you are on slot A and running 10.3.0, the update process will lead to have 10.3.0 on slot A and 10.3.1 on slot B. On next boot the bootloader will automatically boot updated one (i.e slot B will be flagged as the active one). In case of issues during boot process the bootloader will switch the active slot back to the ‘old’ version(here slot A) that was booting fine.
This means that IT’S NOT a dual boot feature!! If you want to run a custom ROM it’s better to have the same custom ROM on both slots and not a mix of OOS and custom ROM. But that’s already OT so let’s stay focus, each custom ROM should provide clear instructions about that.
Having a slot phone means that there is no Recovery partition. So if you ‘fastboot flash boot twrp.img’ it will overwrite your boot partition and thus the ROM kernel and can lead to issues. The .img file is only meant to be temporarly booted. Recovery (stock or TWRP) is a part of the boot ramdisk.
Some simple facts about slots and flashing in TWRP:
Flashing a whole ROM (OOS for example) will automatically flash it to the currently inactive slot and switch it to be the active one (that works also with stock recovery, when performing a ‘local update’)
Flashing a ROM overwrites completely the boot partition (in recent Android versions, flashing process is using partition RAW images and not files like it was before): that means that TWRP and Magisk (if present) will be ERASED.
Flashing TWRP installer will flash it AUTOMATICALLY ON BOTH SLOTS (and will erase Magisk if present)
Magisk (and GAPPS but it only applies to custom ROMs), when flashed with TWRP is only flashed in ACTIVE slot. That’s why you must REBOOT to recovery BEFORE flashing Magisk to have it installed on the active updated slot. And that explains why you must flash it last.
That said, if you stay on OOS, YOU DON’T care about slots, just remember those basics to understand why you have to respect some steps, and let the recovery take care of slots. Messing manually with them results often in soft bricks
Downloads​
OOS stable full signed zips: thanks to @Some_Random_Username, @Titokhan, @trollavin (their thread here)
If the above doesn’t work anymore just let me know I’ll find something else.
FYI you can still go to Oneplus website but they take time to update it to latest version… And there is no archives.
XDA:DevDB Information
OOS Stable thread support, ROM for the OnePlus 6T
Contributors
Striatum_bdr, Scott
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Created 2020-02-05
Last Updated 2020-02-06

Rooting
CHANGELOGS​
OOS 10.3.4:
System
Updated launcher version to 4.1.6
Updated Android Security Patch to 2020.05
Improved system stability and fixed general bugs
Phone
Fixed the issue with default country in assisted dialing when SIM2 is in roaming state
Newly added Work-Life Balance to help prioritize notifications and allocate time wisely (India only)
Newly added Epic Games in Game Space (India only)
OOS 10.3.3:
System
Fixed the issue with a black screen randomly appearing while playing games
Updated GMS package to 2020.02
Updated Android Security Patch to 2020.04
Improved system stability and fixed general bugs
Network updates
Integrated VoLTE & VoWifi support for Telenor – Denmark
Integrated VoWifi support for RJIO – India
Phone
Newly added OpSoprts features in the shelf
Added OnePlus Roaming feature: choose a plan without worrying about the SIM card while traveling
Cloud Sync updates [India only]
Updated the CloudService to Version 2.0
OOS 10.3.2:
Changelog 10.3.2
System
• Fixed the screen flickering issue while swiping up to unlock
• Improved system stability and fixed general bugs
• Updated Android security patch to 2020.02
OOS 10.3.1:
Changelog 10.3.1
System
Fixed the issue with a black screen appearing after unlocking the device using fingerprint
Fixed the issue with the animation logo while rebooting the device
Fixed the issue with device heating up while charging
Fixed the random disconnection issue with 5Ghz Hotspot
Improved system stability and fixed general bugs
Updated Android security patch to 2019.12
Camera
Optimized the image preview time in the Pro mode
Fixed the camera crash issue
Gallery
Fixed the issue with videos and images not displaying in Gallery
OOS 10.3.0:
Changelog 10.3.0
System
Updated system to Android 10
Brand new UI for Android 10
Fixed the automatic reboot issue
Added the notch area display option in the Settings (Settings - Display - Notch display - Hide the notch area)
Fixed the issue with lock screen appearing even after unlocking the device with the password
Fixed the issue with Navigation bar after upgrade
Fixed the Digital wellbeing option missing in the settings
Updated Android security patch to 2019.11
Fingerprint
Fingerprint unlock functionality improvement
Enhanced the fingerprint animation
Camera
Camera performance improvement
Wifi Connectivity
Fixed the issue of Wifi connection to 5Ghz networks
OOS 10.0.1:
Changelog 10.0.1
System
Updated system to Android 10
Brand new UI for Android 10
Updated Android security patch to 2019.10
Fixed the fingerprint identification issue
Fixed the animation lag for fingerprint unlock
Fixed the automatic reboot issue after upgrade
Camera
Improved the performance and fixed known issues
Wifi Connectivity
Fixed the 5Ghz WiFi connection
OOS 10.0.0:
Changelog 10.0.0
System
Upgraded to Android 10
Brand new UI design
Enhanced location permissions for privacy
New customization feature in Settings allowing you to choose icon shapes to be displayed in the Quick Settings
General bug fixes and improvements
Full Screen Gestures
Added inward swipes from the left or right edge of the screen to go back
Added a bottom navigation bar to allow switching left or right for recent apps
Game Space
New Game Space feature now joins all your favorite games in one place for easier access and better gaming experience
Contextual Display
Intelligent info based on specific times, locations and events for Ambient Display (Settings - Display - Ambient Display - Contextual Display)
Message
Now possible to block spam by keywords for Message (Messages - Spam - Settings - Blocking settings)

ROOTING (+/- TWRP)​
Magisk zip is to be found here
TWRP latest .img and installer are to be found here
Don’t use all-in-one tools, you’re a grown up person you can to it by yourself. Yes you can.
If you're not rooted and run an OOS version older than 10.3.1, update your phone normally to latest OOS stable version then do as below
If you’re not rooted and running 10.3.1 or higher, those are the simplest steps to gain root.
Unlock your bootloader (will wipe everything…): “fastboot oem unlock” from a computer (see beginning of OP to know why I don’t detail this) with phone in fastboot mode
Grab latest Magisk zip on your phone and latest TWRP .img on your computer (AND TWRP installer .zip on your phone if you want to install TWRP permanently). Boot in fastboot mode your phone.
Then :
“fastboot boot twrp_latest.img” (adapt to the name and path of your twrp file)
within TWRP, flash TWRP installer .zip if you want to keep TWRP
flash Magisk zip (always AFTER flashing TWRP)
Reboot
(you can theoretically use the TWRP feature ‘install recovery ramdisk’ to avoid flashing twrp installer but never tested)
Note: please STOP using blue_spark TWRP!!! Support for OP6T has been stopped long time ago, only OP6 twrp is still actively supported by eng.stk (errors are mandatory if you flash it on 6t). I even see people that use a 3.2.x version of blue_spark...

UPDATING WITHOUT ROOT​
If your bootloader is locked (meaning no root no TWRP, factory state), the update process is trivial, OOS (or Oxygen Updater if you use it) will grab a patch file (around 100MB max usually) and will apply it and will ask you to reboot. Everybody should be able to do this as it’s the normal way every phone on earth updates itself… If major changes are present sometimes you’ll have the whole ROM file. It doesn’t matter anyway it leads to the same destination.
If your bootloader is unlocked but without root, the only difference is that OOS (or Oxygen Updater) will download the WHOLE ROM (around 1.8GB) and will apply it then ask for rebooting
UPDATING WITH ROOT (+/- TWRP)​
Whole ROM update is mandatory. You can wait for System Update to download it or grab manually the zip file or use Oxygen updater. You then go in Settings > System > System Update > clic on the upper right cogwheel then choose ‘Local Update’ and select the zip file (If you download the OTA .zip file manually you must place it in the root of user data, like /data/media/0/ i.e the user internal storage, or eventually in the .OTA folder if there's one. If you use Oxygen Updater or System automatic donwload it will be right placed).
The following update method is the preferred one (even if you have TWRP, recommended by some TWRP devs) due to frequent changes in partitions by OnePlus
apply the ROM update via Settings > System > System Update > Local Update
DON’T REBOOT
Open Magisk Manager
[If you have TWRP, go in Modules menu, clic on ‘+’ and choose latest TWRP installer zip file on your phone. Don’t use Retention A/B Script Magisk Module I had issues with it] [then stay in Magisk Manager and do the next step]
On main screen of the app clic on ‘install’ next to Magisk paragraph
On the pop up menu confirm ’Install’
On the next pop up menu clic on the last entry: install on inactive slot (after OTA update)
Then only reboot.
The order can be changed (the most important thing to preserve is Magisk, TWRP is easy to flash back):
Update without taking care of TWRP, just Magisk part ("install to other slot after OTA thing")
Once rebooted to updated system, flash TWRP as a module with Magisk Manager
Install Magisk again using Magisk Manager ("direct install" option)
There are infinite debates about uninstalling or not Magisk Modules before updating. Most of the times nothing to touch, sometimes there could be issues, instead of uninstalling perhaps just inactivate them by precaution before updating.
Note: If you are rooted and run an OOS version older than 10.3.1, the above method should work, but you can also update your ROM to latest stable without taking care of root/TWRP and then root again as described in post #2
If you want to try TWRP way:
Reboot to TWRP
Flash OOS update
Flash TWRP installer
Reboot to Recovery
Flash Magisk
Reboot System
IF YOU ARE INTO A SOFT BRICK​
Don't forget the Vol+/Vol-/Power_button combo that can save you from a non responding phone...
If you can boot in fastboot mode, flash the stock ROM with fastboot. A little trick is to edit the flash-all-partitions**.bat and remove ‘-w’ (-w means that the partition will be wiped before flashing) from the script, it will prevent personal data wipe. Or flash manually all partitions one by one, without ‘-w’ flag evidently. Some partitions can’t be flashed with fastboot, for that once booted back to OOS, download and install by ‘local update’ method the same ROM version you’ve just restored with fastboot (see the linked thread to know why, emojis issues for example sometimes).
If you can’t go in fastboot mode, use Oneplus MSM tool. See there and there.

Thank you for the time and effort for this thread as I just came from a Sony XZ1 as I was a bit confused by the different posting on how to do what...

Thanks for a detailed post.
Can I update my rooted OP6T 9.0.17 (TWRP 3.3.1-2+ Magisk) directly to rooted 10.3.1 using the following guide :-
1. Reboot to Twrp 3.3.1-2.
2. Flash Twrp 3.3.1-31 installer.
3. Rebbot to recovery twrp 3.3.1-31.
4. Flash Magisk uninstaller
5. Flash 10.3.1 OS
6. Flash TWRP 3.3.1-31 installer
7. Reboot to recovery.
8. Flash Magisk.
9. Reboot to system.

Goormeetsingh said:
Thanks for a detailed post.
Can I update my rooted OP6T 9.0.17 (TWRP 3.3.1-2+ Magisk) directly to rooted 10.3.1 using the following guide :-
1. Reboot to Twrp 3.3.1-2.
2. Flash Twrp 3.3.1-31 installer.
3. Rebbot to recovery twrp 3.3.1-31.
4. Flash Magisk uninstaller
5. Flash 10.3.1 OS
6. Flash TWRP 3.3.1-31 installer
7. Reboot to recovery.
8. Flash Magisk.
9. Reboot to system.
Click to expand...
Click to collapse
That sounds correct

Thank you for taking the time to do this. I am now subscribed

Very nice. Subscribed. Thank you.

I've been trying to do this for the past 8 hours.
Here's what I do, please tell me where am I going wrong
- msm 9.13
- update to 9.17
- local upgrade to 10.3.1
- boot system to enable oem unlock, usb debug
- boot to fb, unlock bootloader
- boot system
- boot fb, boot twrp
- flash twrp, both slots
- reboot twrp
here I get different results:
- try to install magisk, all internal storage encrypted. sideload, but still no cigar. try to install on both slots by rebooting twrp to a and b and sideloading magisk, still no cigar
OR
- flash magisk, boot system, no magisk
OR
System boots, we have root, we have everything, but file manager shows emptyness. Can't modify any files on internal storage. Via phone and via PC.
Now tell me what am I doing wrong, please

jazzgott said:
I've been trying to do this for the past 8 hours.
Here's what I do, please tell me where am I going wrong
- msm 9.13
- update to 9.17
- local upgrade to 10.3.1
- boot system to enable oem unlock, usb debug
- boot to fb, unlock bootloader
- boot system
- boot fb, boot twrp
- flash twrp, both slots
- reboot twrp
here I get different results:
- try to install magisk, all internal storage encrypted. sideload, but still no cigar. try to install on both slots by rebooting twrp to a and b and sideloading magisk, still no cigar
OR
- flash magisk, boot system, no magisk
OR
System boots, we have root, we have everything, but file manager shows emptyness. Can't modify any files on internal storage. Via phone and via PC.
Now tell me what am I doing wrong, please
Click to expand...
Click to collapse
I think you should format data after unlock. I think it's kinda safety feature if some1 try to get into your storage by unlock bootloader. But wait by some1 to confirm

jazzgott said:
I've been trying to do this for the past 8 hours.
Here's what I do, please tell me where am I going wrong
- msm 9.13
- update to 9.17
- local upgrade to 10.3.1
- boot system to enable oem unlock, usb debug
- boot to fb, unlock bootloader
- boot system
- boot fb, boot twrp
- flash twrp, both slots
- reboot twrp
here I get different results:
- try to install magisk, all internal storage encrypted. sideload, but still no cigar. try to install on both slots by rebooting twrp to a and b and sideloading magisk, still no cigar
OR
- flash magisk, boot system, no magisk
OR
System boots, we have root, we have everything, but file manager shows emptyness. Can't modify any files on internal storage. Via phone and via PC.
Now tell me what am I doing wrong, please
Click to expand...
Click to collapse
I know you managed to sort things as you posted it in another thread. Anyway I don't understand why you had to do all those steps .... But anyway the goal is achieved

Just an FYI: I will be helping to support the T-Mobile version of the device in this thread.

Scott said:
Just an FYI: I will be helping to support the T-Mobile version of the device in this thread.
Click to expand...
Click to collapse
THANK YOU VERY MUCH. Several of us out here!

Scott said:
Just an FYI: I will be helping to support the T-Mobile version of the device in this thread.
Click to expand...
Click to collapse
Welcome back sir Scott!
---------- Post added at 03:27 AM ---------- Previous post was at 03:26 AM ----------
Thank you for this thread.

Scott said:
Just an FYI: I will be helping to support the T-Mobile version of the device in this thread.
Click to expand...
Click to collapse
hodgestl said:
THANK YOU VERY MUCH. Several of us out here!
Click to expand...
Click to collapse
I second this, thank you and also thanks to OP!!
Is there any way we could get a change log for the stable update?

hodgestl said:
THANK YOU VERY MUCH. Several of us out here!
Click to expand...
Click to collapse
r3dp0is0n2012 said:
Welcome back sir Scott!
---------- Post added at 03:27 AM ---------- Previous post was at 03:26 AM ----------
Thank you for this thread.
Click to expand...
Click to collapse
..Cory.. said:
I second this, thank you and also thanks to OP!!
Is there any way we could get a change log for the stable update?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Your all welcome!
I love this phone and like to help so lets see how this goes down :good:
...
---------- Post added at 10:48 PM ---------- Previous post was at 10:39 PM ----------
As far as the change log, that could be a challenge. I have never been able to find the full change log for the international version. The T-Mobile Version is here: https://www.t-mobile.com/support/devices/android/oneplus-6t/software-updates-oneplus-6t. Because this is something we can direct link to, I dont think it should be included in full text here on XDA. I think a link the in first or second post under "useful info" would be sufficient.
As far as the international version goes, I know every verison number by heart.. worst case scenario, I could just google each OTA version and grab the change log from the from the first Android news site that pops up. Unless someone else knows of where one might be at? We could also start at version 10.0.0 because I feel anything older than that is irrelevant.

For changelogs it could be done eventually by grabbing them on the net. There is clearly something between Oneplus and changelogs....
I'm ask for an extra reserved post to have more space and avoid too long posts.

Changelogs added in post #4

Scott said:
Just an FYI: I will be helping to support the T-Mobile version of the device in this thread.
Click to expand...
Click to collapse
Awesome. I've been running a converted TMobile phone and can't wait b for them to related A10 so I can have android pay back without root

Pixel Experience 12 For Samsung galaxy a21s

What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 12.0 (11 is available but 12 has no difference in terms of issues and is faster an the better ui and everything else of course)
Disclaimer:- This will void warranty.
You will need to unlock bootloader.
*All your data will be lost*
Read all the steps correctly
(NOTE: do not apply the fixes if a bug does not affect you)
BUGS:- bluetooth ear/headphones do not work workaround- ( go into phh treble settings misc features and enable force-disable a2dp offload (thanks to @Lil_Boudy for figuring it out!)
If bluetooth crashes your system disable media recommendations under Sound & Vibration > Media > Show media recommendations
mtp not working (mtp does work in twrp and in some custom kernels the one linked here does not fix mtp as it is not changing too many things compared to other custom kernels which brick some phones)
sim 1 incoming and outgoing does not work (you can revieve calls and call but you wonth hear anything nor will your mic go trying to fix) (workaround is to put your sim into slot 2) (i have heard that other people dont have this issue so i guess try your luck)
DO NOT let the phone die of battery you will not be able to boot you can get back by holding volume down and power (workaround- in magisk install acca https://github.com/Magisk-Modules-Repo/acc and install this apk after installing https://github.com/MatteCarra/AccA then set profile to default (this will shut down the phone at 5% hence removing the risk of your phone not booting after hitting 0%
You tell me
Links
Source (Kernel Source)
https://github.com/topjohnwu/Magisk/files/7819803/app-debug.zip (magisk)
Rom download.
1.Need TWRP 3.4.0 or higher!
2. Unpack the "xz" archive and put the .img file onto the sd card or internal (if you dont have a sd card do step 3 then transfer the img file to your phone)
3. In TWRP head to factory reset format type yes and hit enter
4. Flash the img file (as system obviously)
5 flash physwizz kernel
physwizz a21s kernel version 1.5
Based on a217f Version 2 is here https://forum.xda-developers.com/t/physwizz-a21s-kernel-version-1-5.4359957/page-3#post-86991813 For OneUI 3.1 v1.5 (May also work for GSIs) Samsung securities disabled More CPU governors Conservative...
forum.xda-developers.com
5.45 install magisk (the one linked above only) (optional but you should as a lot of modules are listed here are very important (ie the acc module and the fast charging module)
5.5.Reboot and enjoy!
Zainullah Boot fix (if you cant boot)
install oneui boot into oneui change date to 3 months from now
check for updates
boot into download mode
flash twrp 3.6.0 and vbmeta
boot into twrp
do format data
flash multidisabler
flash rom
flash kernel as boot
do factory reset
reboot
if it boots you into fastboot shutdown flash twrp only and try another factory reset and reboot (In twrp)
Install gcam go (or gcam if you get it working)
also enable extra cameras in phh treble settings - samsung settings for ultrawide
Increase performance without any battery impact or (by feravolt and gloeysik)
Step 1
- Uninstall ANY OTHER KERNEL MANAGER app including smartpack/Ktweaks to avoid conflict, since this app uses AI and machine learning to dynamically boost performance when needed
- Install FDE AI Magisk Module to make it a system app, thus it will work better and removes all kernel locks from OEMs (I'm looking at you, Samsung) https://github.com/feravolt/FDE.AI-docs/releases/download/12.4.1m/FDE.AI-as-system-app.MAGISK.zip
- Update FDE AI to the latest version by downloading the latest APK here, since the fde ai magisk module will only install fde ai 12.4.1, not the latest version: https://github.com/feravolt/FDE.AI-docs/releases
- Move to the bottom of the screen and select AI Chat, then type /advancedai (no space, no uppercase letters). This will going to make the AI more effective, without you having to do anything.
- Go to the settings tab and use the AUTO settings for FDE AI.
Optimized and adjusted Google Play services. Contribute to gloeyisk/universal-gms-doze development by creating an account on GitHub.
github.com
install cloudflaredns4magisk (install both ipv4 and ipv6 versions) (this will switch you to cloudflares faster and more secur dns
Cloudflare dns magisk download​
install adaway (optional if you want ads or not) , allow superuser for it download this https://energized.pro/bluGo/formats/filter in adaway click he button in the middle click add click file and add the file then go back to the main menu and click the reload button now https://adaway.org/
(you get better battery and performance in adaway)
also enable extra cameras in phh treble settings - samsung settings for ultrawide
install universal safteynet fix zygsik (magisk)to get safteynet working
enable denylist for apps you want to hide root from (dont enable it for google play services as it is not needed)
ALL credit goes to phusson , ponces and rest of the devs
Blog
Pixel Experience
Donate
jhenrique09
phhusson
AndyYan
eremitein
ponces

can i install this rom being in the U8 binary? SM-A217M

What about the Galaxy A21 without the S? That's what it says on my device. Would it work or is it a different model?

iLoveANDROlD said:
What about the Galaxy A21 without the S? That's what it says on my device. Would it work or is it a different model?
Click to expand...
Click to collapse
it will work
but i havent tested performance yet so it may not be fast

I'm having a problem that says I don't have available storage (even i have 50gb free), I can't download anything, any help?

I'm having a problem with the lock screen, every time I put a password and restart the phone and try to unlock it, it automatically says the password is wrong and locks the phone for more than 8000 seconds... you know how to fix it?

so our phone does not support installing firmware from tvrp? And so why does the manual describe the installation method via TWRP?

parizi57 said:
I'm having a problem with the lock screen, every time I put a password and restart the phone and try to unlock it, it automatically says the password is wrong and locks the phone for more than 8000 seconds... you know how to fix it?
Click to expand...
Click to collapse
i have this proplem too !!
on any rom and gsi and stock rom
any soulotion !?

Mouad2007 said:
i have this proplem too !!
on any rom and gsi and stock rom
any soulotion !?
Click to expand...
Click to collapse
I didn't find any way to fix it, I'm using the stock rom that I don't have this problem

parizi57 said:
I'm having a problem with the lock screen, every time I put a password and restart the phone and try to unlock it, it automatically says the password is wrong and locks the phone for more than 8000 seconds... you know how to fix it?
Click to expand...
Click to collapse
did you find any soulotion bro !! plz help me

parizi57 said:
I didn't find any way to fix it, I'm using the stock rom that I don't have this problem
Click to expand...
Click to collapse
Which binary you have !! u7 ???

Zainullahk1234 said:
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 12.0 (11 is available but 12 has no difference in terms of issues and is faster an the better ui and everything else of course)
Disclaimer:- This will void warranty.
You will need to unlock bootloader.
*All your data will be lost*
Read all the steps correctly
(NOTE: do not apply the fixes if a bug does not affect you)
BUGS:- bluetooth ear/headphones do not work workaround- ( go into phh treble settings misc features and enable force-disable a2dp offload (thanks to @Lil_Boudy for figuring it out!)
If bluetooth crashes your system disable media recommendations under Sound & Vibration > Media > Show media recommendations
mtp not working (mtp does work in twrp and in some custom kernels the one linked here does not fix mtp as it is not changing too many things compared to other custom kernels which brick some phones)
sim 1 incoming and outgoing does not work (you can revieve calls and call but you wonth hear anything nor will your mic go trying to fix) (workaround is to put your sim into slot 2) (i have heard that other people dont have this issue so i guess try your luck)
DO NOT let the phone die of battery you will not be able to boot you can get back by holding volume down and power (workaround- in magisk install acca https://github.com/Magisk-Modules-Repo/acc and install this apk after installing https://github.com/MatteCarra/AccA then set profile to default (this will shut down the phone at 5% hence removing the risk of your phone not booting after hitting 0%
You tell me
Links
Source (Kernel Source)
https://github.com/topjohnwu/Magisk/files/7819803/app-debug.zip (magisk)
Rom download.
1.Need TWRP 3.4.0 or higher!
2. Unpack the "xz" archive and put the .img file onto the sd card or internal (if you dont have a sd card do step 3 then transfer the img file to your phone)
3. In TWRP head to factory reset format type yes and hit enter
4. Flash the img file (as system obviously)
5 flash physwizz kernel
physwizz a21s kernel version 1.5
Based on a217f Version 2 is here https://forum.xda-developers.com/t/physwizz-a21s-kernel-version-1-5.4359957/page-3#post-86991813 For OneUI 3.1 v1.5 (May also work for GSIs) Samsung securities disabled More CPU governors Conservative...
forum.xda-developers.com
5.45 install magisk (the one linked above only) (optional but you should as a lot of modules are listed here are very important (ie the acc module and the fast charging module)
5.5.Reboot and enjoy!
Zainullah Boot fix (if you cant boot)
install oneui boot into oneui change date to 3 months from now
check for updates
boot into download mode
flash twrp 3.6.0 and vbmeta
boot into twrp
do format data
flash multidisabler
flash rom
flash kernel as boot
do factory reset
reboot
if it boots you into fastboot shutdown flash twrp only and try another factory reset and reboot (In twrp)
Install gcam go (or gcam if you get it working)
also enable extra cameras in phh treble settings - samsung settings for ultrawide
Increase performance without any battery impact or (by feravolt and gloeysik)
Step 1
- Uninstall ANY OTHER KERNEL MANAGER app including smartpack/Ktweaks to avoid conflict, since this app uses AI and machine learning to dynamically boost performance when needed
- Install FDE AI Magisk Module to make it a system app, thus it will work better and removes all kernel locks from OEMs (I'm looking at you, Samsung) https://github.com/feravolt/FDE.AI-docs/releases/download/12.4.1m/FDE.AI-as-system-app.MAGISK.zip
- Update FDE AI to the latest version by downloading the latest APK here, since the fde ai magisk module will only install fde ai 12.4.1, not the latest version: https://github.com/feravolt/FDE.AI-docs/releases
- Move to the bottom of the screen and select AI Chat, then type /advancedai (no space, no uppercase letters). This will going to make the AI more effective, without you having to do anything.
- Go to the settings tab and use the AUTO settings for FDE AI.
Optimized and adjusted Google Play services. Contribute to gloeyisk/universal-gms-doze development by creating an account on GitHub.
github.com
install cloudflaredns4magisk (install both ipv4 and ipv6 versions) (this will switch you to cloudflares faster and more secur dns
Cloudflare dns magisk download​
install adaway (optional if you want ads or not) , allow superuser for it download this https://energized.pro/bluGo/formats/filter in adaway click he button in the middle click add click file and add the file then go back to the main menu and click the reload button now https://adaway.org/
(you get better battery and performance in adaway)
also enable extra cameras in phh treble settings - samsung settings for ultrawide
install universal safteynet fix zygsik (magisk)to get safteynet working
enable denylist for apps you want to hide root from (dont enable it for google play services as it is not needed)
ALL credit goes to phusson , ponces and rest of the devs
Blog
Pixel Experience
Donate
jhenrique09
phhusson
AndyYan
eremitein
ponces
Click to expand...
Click to collapse
I have a problem with my samsung a21s
When I put the pin code, pattern, fingerprint or face.. then reboot.. a message says: Try again after 1440 minutes... Can you help me.. I will be very grateful

that is no one said:
I have a problem with my samsung a21s
When I put the pin code, pattern, fingerprint or face.. then reboot.. a message says: Try again after 1440 minutes... Can you help me.. I will be very grateful
Click to expand...
Click to collapse
hmm remove pin code and try again dunno why it does this

I thought we couldn't put twrp on our phones. Was a fix found?

Does it work on U8 Tho ? and A217F ?

Hello, I have a problem. It requires a screen lock with face unlock on every option, but my frontal camera is not working and it won't let me get past setup. Is it fixable?

7MODE__TN said:
Does it work on U8 Tho ? and A217F ?
Click to expand...
Click to collapse
I was able to flash it on my A217F U8. the only thing is that it won't let me go past the setup because it requires face unlock because my frontal camera doesn't work
EDIT: I was able to get over it.

I am getting random lag spikes, when this happens, I boot up ADB Shell and "top" shows 800% CPU while system_server is at the top, without using a lot of CPU... Is this supposed to be expected on this ROM? I can't seem to see it mentioned on bugs.

How do I even flash when there is no TWRP FOR it :[