[GSI][PHH][Q][R][S] GSI flashing for Realme C12 - Realme C12 Guides, News, & Discussion

Before doing anything to device, keep a copy of Stock ROM from here in your PC or SD Card.
Installing GSI ROMs
Tutorial:
If you don't know what a GSI is or want to know more about it, see this, this and this
Don't try to flash GSI in custom recovery.​
Note:- We can only flash GSIs having android version higher than or equal to stock rom android version. That is if your StockROM Android version is 10, then you can only flash GSIs of Android 10 or higher.
If you are flashing GSI with custom ROM installed, then flash stock ROM before flashing GSI. Since boot and vendor(may), get modified with custom ROM.
Step 1 - Pick your poison in the Treble Forums or from here!
Check below of this thread if you want to see my recommendations with links to them.
Step 2 - Download the chosen ROM, A/B ARM64 version (usually nicknamed (b), with (g) or without GApps (v), rooted (S) or not (N), that's entirely up to you.
It should be an .img.xz file, extract it and you'll get an .img file.​
For example, I am downloading this​
You're ready to flash. Make sure to backup your phone's data before continuing on with this tutorial, as wiping it is required for installation!
Step 3 - Put your phone into fastboot mode (Power + Volume Down) and link it to your PC.
Step 4 - Move the .img file and vbmeta.img you downloaded to your ADB & Fastboot (Platform Tools) folder, and rename it to system.img.
Step 5 - Shift + Right click in an empty space inside the folder, and click Open Command window here.
Inside the Command window, input the following commands line by line, in order.​
Code:
fastboot reboot fastboot // Recovery will appear with fastbootd mode
fastboot flash system system.img
fastboot reboot bootloader
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot -w // Skip this if you are updating GSI
fastboot reboot
Your phone will now reboot on its own, using the new ROM you picked earlier, set it all up and enjoy!
GSI bugs without having any possible fixes
These bugs are there in my device and I can't able to fix them
DoubleTapToWake with Q vendor
Lift to wake with R vendor
Fingerpirnt(egis) with R vendor
GSI bugs and possible fixes
VoLTE is fixed in Android 11(R) GSIs which are based on AOSP v300j for Q vendor and AOSP v312 for R vendor
we can get VoLTE working by following below
- Goto Settings => Phh Treble Settings => IMS features
- Now Select both Request IMS network && Force the presence of 4G Calling
- Now click Install IMS APK for Mediatek Q vendor.
- Let it complete download (check your notification panel).
It will show IMS installed You may now reboot! as a toast message
- Now click Create IMS APN (Nothing will happen)
- Reboot and Enjoy!
Play Protect not certified can be fixed by following below
- Download https://f-droid.org/en/packages/makeinfo.com.getid/
- Copy Google Service Framework Key
- Go to https://www.google.com/android/uncertified/
- Sign In and paste copied Value to it and register
- Reboot
Fix Low Brightness
- Go to Settings => Phh Treble Settings => Misc features
- Check Force alternative backlight scale
- Adjust brightness
Fix et512/egis fingerprint
- See https://forum.xda-developers.com/t/gsi-phh-q-r-gsi-flashing-for-realme-c12.4244979/post-85451661
Fix wired ear phones not working
- Go to Settings => Phh Treble Settings => Misc features
- Check Use alternative way to detect headsets
- Reboot
Fix Bluetooth speakers/earphones not working (not tested because I don't have these)
- Go to Settings => Phh Treble Settings => Misc features
- Check Force-disable A2DP offload
- Reboot
Enable USB OTG
- Go to Settings => Phh Treble Settings => Oppo features
- Check Enable USB OTG
If there is no Oppo features in settings then simply run below command in Termux
Code:
su -c "setprop persist.sys.phh.oppo.usbotg 1"
/system partition is read-only
this is the default behaviour of non-vndklite GSIs from v300.j onwards, to get R/W access for /system use vndklite variant.
Click to expand...
Click to collapse
If you have any other issues, tell the developer with logs. See this to know about taking logs.
FAQ
I can't able to use Magisk because of inbuilt phh SuperUser
- To use Magisk, we have to remove inbuilt phh SuperUser first, to do so boot to TWRP and run below commands in PC
Code:
adb shell
mount /system_root
mount -o rw,remount /system_root
rm -rf /system_root/system/app/me.phh.superuser
rm -f /system_root/system/bin/phh-su
rm -f /system_root/system/etc/init/su.rc
rm -f /system_root/system/xbin/su
exit
Now you can able to use Magisk
I can't able to install GApps in vanilla variant
- Simple thing we have to do is to use GApps variant of GSI. If you don't want to use GApps variant for some reason or there is no such thing at all, we need to resize system to increase free space in /system partition. For this we need to use fastbootd mode
Code:
adb reboot fastboot // or fastboot reboot fastboot if your are in fastboot mode
fastboot resize-logical-partition system 4294967296 // 4 GiB
fastboot reboot recovery
Now you can flash GApps package
If your are using UI 2.0 (means R vendor), then you may can't resize system 4 GiB as shown above, to do so we have to remove some unnecessary partitions first, run these commands in PC
Code:
adb reboot fastboot // or fastboot reboot fastboot if your are in fastboot mode
fastboot erase my_heytap
fastboot resize-logical-partition my_heytap 4096
fastboot erase my_stock
fastboot resize-logical-partition my_stock 4096
fastboot erase my_preload
fastboot resize-logical-partition my_preload 4096
Note that instead of deleting those partitions I erased and resized to 4KiB because deleting will cause longer booting time.
Click to expand...
Click to collapse
Spoiler: GSI Recommendations
All my recommendation's latest releases contain fixes for our device.
Ordered by personal preference:
LOS mod (LineageOS GSI)
crDroid
CAOS

Flashing StockROM in TWRP
Note:- If you want to flash older version of stock rom than the one that is installed, then you need to be on GSI or custom ROM to do it.
- Search Software update - realme in Google and go to your region specific site
- Download and place stock .ozip in External storage
- Download and install TWRP from https://androidfilehost.com/?fid=7161016148664786711 (Don't use other TWRP)
- Boot to TWRP
- Go to Settings and check Skip Treble Compatibility error
- Choose Wipe and then Format Data and type yes
- Now choose Install and select Micro SDCard in Select Storage that is located in bottom left
- Select Stock ROM .ozip and Swipe for Installation
- After 7 - 15 minutes flash will complete. Choose Wipe Dalvik/Cache
- Reboot
- Enjoy!
Downgrading StockROM using TWRP
- Download .ozip of specific version of Stock ROM that you need to downgrade
- Flash TWRP from https://androidfilehost.com/?fid=7161016148664786711 (Don't use other TWRP)
- Boot to TWRP
- Enable 'Skip Treble Compatibility error' in settings
- Flash ozip
- Format Data and wipe cache
- Reboot
Flashing StockROM in Stock Recovery
Note:- If you want to flash older version of stock rom than the one that is installed, then you need to be on GSI or custom ROM to do it.
If you don't have a backup of stock recovery, then you can get one from A.83 which will work on all other versions of UI 1.0 ONLY from here
- Search Software update - realme in Google and go to your region specific site
- Download and place stock .ozip in External storage
- Boot to stock recovery
- Select Install from storage and select storage where .ozip is located
- Click on .ozip and click OK when prompted to Installation package
- After 7 - 15 minutes flash will complete. Click OK in Installation successful. Prompt
- Go back and select Wipe data, enter verification code and select Format data and click on Format
- Click OK in Wiped successfully prompt and it will automatically boot to stock rom
- Enjoy!
Thanks:-
To this

egis/et512 Fingerprint fix
* First check if you have egis/et512 fingerprint by using Device Info HW app and see 'General' => 'Fingerprint'. If you have egis/et512 then follow below
* This needs to have rooted with Magisk
* Flash below attached module in Magisk app to fix fingerprint
This module is only for Realme UI 1.0 Android 10 vendor with Android 11/12 custom ROM/GSI
Credits
- titidlancip
- dodyirawan85

I am just testing AOSP v313 vndklite vanilla to create an overlay for fixing battery stats, status bar height and to set notch cutout.
Overlay made so far is attached below.
To make the overlay work, just place it in /system/product/overlay/and reboot. See if status bar height is increased or not and after some usage battery stats will appear (Setting -> Battery -> 3-dot -> Battery usage). We can check if overlay is applied or not using below commands in Termux su -c "lsof | grep treble-overlay-realme-c12" it will output some lines if successfully applied.

HemanthJabalpuri said:
I am just testing AOSP v313 vndklite vanilla to create an overlay for fixing battery stats, status bar height and to set notch cutout.
Overlay made so far is attached below.
To make the overlay work, just place it in /system/product/overlay/and reboot. See if status bar height is increased or not and after some usage battery stats will appear (Setting -> Battery -> 3-dot -> Battery usage). We can check if overlay is applied or not using below commands in Termux su -c "lsof | grep treble-overlay-realme-c12" it will output some lines if successfully applied.
Click to expand...
Click to collapse
Wow was searching for this for like past 2-3 days, Thanks, man.
Can I use it on RMX2185?
and How to do it.

RoyTheBoy83 said:
Wow was searching for this for like past 2-3 days, Thanks, man.
Can I use it on RMX2185?
and How to do it.
Click to expand...
Click to collapse
for now the overlay that I made will only work on C12 RMX2189. I will check once there is some time

HemanthJabalpuri said:
egis/et512 Fingerprint fix
* First check if you have egis/et512 fingerprint by using Device Info HW app and see 'General' => 'Fingerprint'. If you have egis/et512 then follow below
* This needs to have rooted with Magisk
* Flash below attached module in Magisk app to fix fingerprint
This module is only for Realme UI 1.0 Android 10 vendor with Android 11/12 custom ROM/GSI
Credits
- titidlancip
- dodyirawan85
Click to expand...
Click to collapse
FIx for both relame ui 1 and 2

Related

[ HOW TO FLASH AOSP 8.1 - Phh-Treble ] _ [ ON TECLAST TAB M20_4G (M3K1) ] _MT6797D_

*[Requirements: Your device MUST be Project Treble compatible (M20 supports Treble Project,A only x64)
Your device MUST have an unlockable bootloader
Your device LAUNCHED with Android 8.0 +(was made Project Treble compatible by the manufacturer)
Your device is free of any heavy modifications such as the Xposed Framework, SuperSU, or Magisk(You can re-install after)]
__First than all,we need the right drivers on pc... Turn OFF any antivirus...
1) disable Driver Signature enforcement on Windows 10- https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
2)MTK_USB_All : https://mega.nz/#!JvY2SB5K!h8l34d1n3QxRxaLZ36pZMMCP4gE56vcCN6Etg6VGF8I
*Universal MTK CPU Drivers: https://mega.nz/#!R6xnzYJb!R9POyi7nBAxA7dpXlqCLw7aXvtFWbNFNyGzdwOTET2o (7z)
3)Windows10 VCOM drivers : https://mega.nz/#!9z5lWQpb!YheGLaes0mFACq8pwjWVjZV-JEMTuXDu-LB8MrQ2cAo
_[how to use VCOM drivers: https://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033 ]
4) Google USB Drivers: https://mega.nz/#!1uYDACob!RszDuYFxGUIrPjayhExK2KgzmnsBUQjSZDK2sRZSxF4
*[for fastboot you will need: https://forum.xda-developers.com/showthread.php?t=2588979
_minimal adb & fastboot : https://forum.xda-developers.com/showthread.php?t=2317790
_How to Use ADB or Fastboot From Any Directory: https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/ ]
*Οptionally: [Or you can use this great tool for all..This is for xiaomi but can Install all MTK+VCOM drivers + driver signature disable etc..Just,follow the instructions]
https://mega.nz/file/5rphEShJ#-VGvFPM0hZICZC28VQ6zqwHXLA9EEfv_8thiTXla1dY
*Source: https://xiaomi-miui.gr/community/index.php/Thread/23910-Αυτοματοποιημένη-εγκατάσταση-drivers-για-κινητά-Xiaomi-σε-όλα-τα-Windows-x64-x86/?pageNo=1
_[Unlock Bootloader]_
_Now you must unlock bootloader : Turn ON "oem unlock" on the developer options - usb debugging On...
Connect your tablet to your PC via USB, and launch an ADB terminal - cmd ...
_type: "adb devices" > "adb reboot bootloader" > "fastboot devices " - Once your device is in Fastboot Mode, type into ADB terminal : "fastboot oem unlock" ..
Press the Volume Up key to confirm & your bootloader will be unlocked (this will also perform a factory reset on your device)
_Also,turn your device in fastboot mode again & type : "fastboot erase system" (all data etc, will delete)
Now, turn your device OFF...Install SPFT on pc: https://spflashtool.com/ (this only needs for twrp method)
[ * Via TWRP ]
Install this version TWRP : https://forum.xda-developers.com/showpost.php?p=77079814&postcount=332 [*this is for chuwi hi9 air but works in M20_4G{same hardware} and flash TWRP 3.2.2-0 via SPFT....(anyone who wants can flash it and through fastboot,just follow the instructions there) BUT! don't reboot device on System ! .Just turn off your device temporarily)
__*all thanks there to @Alberto96 for TWRP 3.2.2-0 !
_*("It’s possible that dm-verity is preventing your device from booting with the GSI. In that case, please go ahead and flash Magisk and then see if it boots.
that is required for various devices sometimes) - Read here In "Troubleshooting Tips" : https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
_Magisk: https://github.com/topjohnwu/Magisk
*(better leave the device encrypted...Device can be decrypted, but maybe not start in some cases ! but whoever wants can be try)
_Installation Rom via twrp_ [the recommended way is through fastboot!]
_Reboot on Recovery > From TWRP > type cancel > swipe to allow modifications > wipe > swipe to factory reset / advanced wipe > system - cache - data - dalvik / Reboot Recovery !....
_Now Install rom on pc : system.img for A-only ARM64 devices with GApps and SU : (newer releases there!)
https://github.com/phhusson/treble_...wnload/v25/system-arm64-aonly-gapps-su.img.xz
_Or: system.img for A-only ARM64 devices vanilla :
https://github.com/phhusson/treble_...ad/v25/system-arm64-aonly-vanilla-nosu.img.xz
*Source: https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
_Or Aosp 9 treble phh : https://forum.xda-developers.com/pr...vice-development/aosp-9-0-phh-treble-t3831915
Decompress it with 7z ,connect device-pc & send .img on device and flash it on "System Image" Partition ...When Installation finish,wipe ONLY cache + dalvik & reboot system...The device takes several minutes to start,needs patience(If it is enough minutes on a black screen you can use the start button)
__ 7z: https://www.7-zip.org/download.html
* For decryption:
(any one who wants to decrypt his device,can in this way:
https://mega.nz/#!snwgXQZL!2mdUdmsZMWX2XpQkMbJKn9jETsMReHpoDLhOe1rxG8g
*Source: https://www.cyanogenmods.org/downloads/disable-force-encryption-twrp-flashable-zip-treble/
_Or: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389 ): Recommended: BUT! you must read in OP there how to...
(you have to flashing one of these and magisk at the end)
_*[You can't decrypt your existing data "PERMANENTLY" If flashing only this...The Flashing "DM-Verity-ForceEncrypt" can only be done when you format data.
(Just, flash the zip in twrp before flashing Magisk-mandatory requirement or else the zip won't work)
....Format Data will format your internal Storage! This step is needed to use encryption on your internal storage]
_*[Some devices may fail due to dm-verity check. To fix, you can install Magisk to disable dm-verity / read for Universal DM-Verity from link above]
Magisk Installation:General "Info-Quide"-Magisk in Recovery etc: https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery
https://topjohnwu.github.io/Magisk/install.html
_ΗOW TO FLASH AOSP Phh Treble 8.1 or 9 VIA FASTBOOT_ [Recommended]
1) Unlock bootloader : enable "oem unlock" in developer option & usb debugging on...
_Reboot on bootloader : from cmd type : "fastboot oem unlock" > Press the Volume Up key to confirm & your bootloader will be unlocked
_Reboot on bootloader again and type : "fastboot erase system"
2) Flash gsi rom : open a command and type : "fastboot -u flash system name_of_system.img"
_Once it has completed, reboot your device either manually via power key or by entering > "fastboot reboot".
_*(with these commant : "fastboot erase system" - "fastboot -w"
everything on the device is deleted!)
__*[General Information GSI__ It's good to read: Flashing GSIs Requirements_]
https://source.android.com/setup/build/gsi
__ https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
[ Ready-made files Stock Rom M20_4G (M3K1) that will help users to Restore or Root ]
_Stock Rom -Android8.0-V1.04_google_play_(M20_4G M3K1) : https://mega.nz/#!InwhkKSY!X2nLf2t1Ai7RDr6pnmYg9m01-sESMRGDrvqbndlYhog (playstore Included)
* https://naijarom.com/teclast-m20-4g-m3k1 (stock rom + tutorial)
_vendor .img : https://mega.nz/#!F2YQAY7b!-xacb26Ll2To3m4LIPy9anzzBWG5YTxOLL93HNatyqY [M20_4G M3K1- V1.04_20180814]
_boot.img : https://mega.nz/#!EywBiCxQ!Im2pGWyj6mhFl1ABtqQiTV8Qvwc_Xvax7Vhnuya_1w0
_patched_boot.img : For rooted your STOCK device in very easy way with magisk : https://mega.nz/#!5zhCyKqY!EkVDajKy-p4EpJOYfR4nE-4tGuOUVWzRMbNshHMA2kk
(M20_4G M3K1- V1.04_20180814)
_IMPORTANT: you can use "patched_boot" OR "boot.img" only for this build !
__(M20_4G M3K1- V1.04_20180814)__
__Required : unlocked bootloader !
__Latest Magisk Manager (from link above)
Simply,In stock device M20_4G M3K1 boot your Android device into fastboot mode ,connect your phone to the PC,open a command line & type : "fastboot flash boot patched_boot.img" / "fastboot reboot"
after your device boots, open magisk manager and confirm that the installation was done!
*[optionally]:_ device certification after boot: Install device ID app from playstore : https://play.google.com/store/apps/details?id=com.evozi.deviceid
_wipe playstore cache
_open Device ID app & copy GSF (Google service framework)
_ Go to : https://www.google.com/android/uncertified/ > paste GSF ....Reboot your device
__READ & THIS for more Info about playstore certificate & how to fix: https://www.xda-developers.com/how-to-fix-device-not-certified-by-google-error/
*[maybe the device cannot pass safetynet,regardless of whether it is hidden in magisk and whether it is certified or not,one doesn't exclude the other]
Info - SafetyPatcher module : https://forum.xda-developers.com/apps/magisk/module-safetypatcher-t3809879
MagiskHide troubleshooting quide: https://www.didgeridoohan.com/magisk/HomePage
[ __* M20 4G(M3K7) - M20 4G(M3K7)_Android 8.0_V1.01_SZ.rar Stock Rom (Global firmware v1.01 with Google Play)
AFH : https://androidfilehost.com/?fid=6006931924117939713
__* Teclast M20 4G (M3K7) TWRP 3.3.1.7z : AFH : https://androidfilehost.com/?fid=6006931924117938571
__* Firmware for Chinese Area v1.01 (without Google Play) AFH : https://androidfilehost.com/?fid=6006931924117939717 ]
[_Info for android9 Phh-Treble : https://forum.xda-developers.com/pr...vice-development/aosp-9-0-phh-treble-t3831915
_Info for android10 Quack Phh-Treble : https://forum.xda-developers.com/pr...aosp-10-0-quack-phh-treble-t3992559?nocache=1
_ Very Ιmportant: Before installation "GSI phhusson 9 or 10",read carefully for "Bugs/Issues" in GitHub & "treble_experimentations_issues" thread,with users feedback,Logs & informations for our devices & generally for MTK devices with same hardware ,cpu/gpu etc here : https://github.com/phhusson/treble_experimentations/issues?page=1&q=is:issue+ispen
**I want to thank ! :
@ georgekaggelaris for xiaomi driver tool _ xdi 1.0.3
@ Alberto96 for TWRP 3.2.2-0
@ phhusson for great work in AOSP 8.1 & 9 treble rom
@ topjohnwu for magisk
@ skeleton1911 for VCOM drivers tutorial
@ Snoop05 for 15 seconds adb Installer
AND OF COURSE TO ALL USERS
_ please be kind with everyone _
**_IMPORTANT : If someone user does not know how to restore his device in factory condition,better to stay away!! All this contain great risk for the device!
I have no responsibility for what each one does on his device ! Please use with extreme caution!
sry for english
:good:¨
_Screenshots : https://postimg.cc/gallery/176fg6i4e/
https://postimg.cc/gallery/3dnir72ke/
_Screenshots Teclast M20_4G treble AOSP 9 Phh : https://postimg.cc/gallery/dxx0ck3i/
_ https://postimg.cc/gallery/e1yplflq/
(For M3K4 model and AOSP 9.0 you can see post #22 : https://forum.xda-developers.com/showpost.php?p=80068658&postcount=22 )
new release v28 sec patch 5-2-2019
Today I got the new release v28 / update aosp 8.1 treble phh with sec patch 5-2-2019
For more Info etc : https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
https://github.com/phhusson/treble_experimentations/releases/tag/v28
AOSP treble 9 phh - M20_4G
Today I tried and AOSP Treble 9 phh..Device works well,but there still some bugs!
decrypted device on AOSP treble phh 9 : https://postimg.cc/gallery/2aw12ydoe/
_Source: https://forum.xda-developers.com/pr...vice-development/aosp-9-0-phh-treble-t3831915
https://postimg.cc/gallery/dxx0ck3i/
device with decryption on aosp treble 8.1 phh
Device can be decrypted even with this recovery as you can see on screenshots : https://postimg.cc/gallery/e1yplflq/
Just, > format data > Reboot on Recovery > flash: https://mega.nz/#!snwgXQZL!2mdUdmsZMWX2XpQkMbJKn9jETsMReHpoDLhOe1rxG8g > flash magisk 18.1 : https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 > wipe cache + dalvik & reboot ...
M20_4G aosp treble phh 8.1 SIM cards +4G etc...
Yes 4G ,SIM cards etc works normally without problem
(wifi ,Bluetooth, data ,camera ,videos, SD, adb-mtp all working)
https://postimg.cc/gallery/yerr9oji/
New release v29 (aosp 8.1) 6-3-2019
https://github.com/phhusson/treble_experimentations/releases/v29/
source: https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
(Launcher in 8.1 : https://github.com/amirzaidi/launcher3/releases
+ https://mega.nz/#!9nZUHCrJ!BqOy0Y0tYZ6mF2FpR7mkfEO151_8H8oib1b160X30UM
Or : https://forum.xda-developers.com/android/apps-games/app-lineageos-15-trebuchet-laucher-rom-t3667436 )
AOSP 8.1 v30 released : https://github.com/phhusson/treble_experimentations/releases/tag/v30
source : https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
AOSP 9.0 v112 released : https://github.com/phhusson/treble_experimentations/releases/tag/v112
source: https://forum.xda-developers.com/pr...vice-development/aosp-9-0-phh-treble-t3831915
both works for M20_4G
daitalos said:
AOSP 8.1 v30 released : https://github.com/phhusson/treble_experimentations/releases/tag/v30
source : https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
AOSP 9.0 v112 released : https://github.com/phhusson/treble_experimentations/releases/tag/v112
source: https://forum.xda-developers.com/pr...vice-development/aosp-9-0-phh-treble-t3831915
both works for M20_4G
Click to expand...
Click to collapse
Just wondering does this toturial also works on M20-4g(M3K4)? It's the 4gb memory version
jefferyli said:
Just wondering does this toturial also works on M20-4g(M3K4)? It's the 4gb memory version
Click to expand...
Click to collapse
I'm not very sure but normally yes...
I have try only in M3K1 but Is the same device generally (MT6797D 64 gb Internal 4gb ram android 8 + playstore)
better try via fastboot
the decision is yours
daitalos said:
I'm not very sure but normally yes...
I have try only in M3K1 but Is the same device generally (MT6797D 64 gb Internal 4gb ram android 8 + playstore)
better try via fastboot
the decision is yours
Click to expand...
Click to collapse
@jefferyli:
Did you try to install it on the M3K4 device? Was it successfull?
@daitalos:
In terms of stability do you recommend AOSP 8.1 over AOSP 9.0?
flotux said:
@jefferyli:
Did you try to install it on the M3K4 device? Was it successfull?
@daitalos:
In terms of stability do you recommend AOSP 8.1 over AOSP 9.0?
Click to expand...
Click to collapse
aosp 8.1 was more stable,but after the latest update (build v112) aosp 9 works very well
we are expecting and new update of aosp 9 these days....So,if you want to install it is better to wait for the newest build I think ...
LOL... There is new build aosp 9 V113 : https://github.com/phhusson/treble_experimentations/releases/tag/v113
aosp 8.1 build V31 : https://github.com/phhusson/treble_experimentations/releases/tag/v31
daitalos said:
aosp 8.1 was more stable,but after the latest update (build v112) aosp 9 works very well
we are expecting and new update of aosp 9 these days....So,if you want to install it is better to wait for the newest build I think ...
Click to expand...
Click to collapse
@daitalos: Thanks for your answer. That fits well as my Teclast M20 4G is still somewhere between China and Europe.
flotux said:
@jefferyli:
Did you try to install it on the M3K4 device? Was it successfull?
Click to expand...
Click to collapse
No, sorry, didn't have time recently... Causing I'm using Mac, and I have to install windows first. But I will try it in two weeks
What is better about this ROM than the Stock ROM?
Held der Arbeit said:
What is better about this ROM than the Stock ROM?
Click to expand...
Click to collapse
....this depends on what custom rom you are talking about & your device model - stock rom
some advantages of aosp phh 8.1 (or 9) from teclast M20_4G stock rom
stock rom on M20_4G is android oreo 8 - without updates & support anymore
this aosp phh is oreo 8.1 (or newer-latest android pie9)
security : stock firmware has sec patch 2018 - this 8.1 (or pie9) gets monthly updates (bug fixes + sec patch 2019)
features : this aosp phh is pure stock android
& more like as : root access,better performance,battery management etc...
https://dazeinfo.com/2017/04/10/android-stock-rom-custom-rom/
https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
sry for english
I flashed AOSP 9.0 v113 and Magisk 19.1, but titanium Backup does not get root access.
Edit: It worked with Magisk 18.1
Held der Arbeit said:
I flashed AOSP 9.0 v113 and Magisk 19.1, but titanium Backup does not get root access.
Edit: It worked with Magisk 18.1
Click to expand...
Click to collapse
If you want you can add the device here,so that other users with M20_4G can see that the device is compatible.You can be the first one to test it and report
https://github.com/phhusson/treble_experimentations/wiki
(Unfortunately, I no longer have the device)
Latest release - AOSP 9.0 v114 : https://github.com/phhusson/treble_experimentations/releases/tag/v114
https://forum.xda-developers.com/pr...vice-development/aosp-9-0-phh-treble-t3831915
I flashed the system-arm64-aonly-gapps-su.img but now the tablet only boots in TWRP.
Held der Arbeit said:
I flashed the system-arm64-aonly-gapps-su.img but now the tablet only boots in TWRP.
Click to expand...
Click to collapse
Try to flash vendor .img or flashing from the beginning via fastboot (recommended way)

[ROM][11.0][Official][hotdogb] StatiXOS 4.0

{
"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"
}
StatiXOS for OnePlus 7T (hotdogb)
About us
StatiXOS is a custom ROM based on the Android Open Source Project aiming to be minimal while providing quality of life improvements and up to date security patches.
Source code
Spoiler
GitHub
Gerrit
Features
Spoiler
Feature List
Screenshots
Download StatiXOS here
Spoiler
Download StatiXOS
Mirror
GApps are included!
Stay in touch
Our Telegram channel​
ROM OS Version: 11.0
ROM Firmware Required: OOS 10.0.16 (Global Version)
You're free to flash StatiXOS with Lineage Recovery, TWRP or fastbootd
Clean Flash
Spoiler
The last OOS you flashed to your phone (doesn't necessarily need to be the flashed right before StatiX) needs to be the latest stable global variant, you can get it here.
Spoiler: Easiest way: fastbootimages
Download the ROM from here (or our mirror server)
Reboot to bootloader
Flash StatiX by executing
Code:
fastboot update <statix_hotodgb-...-.zip>
(Replace the text between the "<>" with the actual zip name and remove the "<>")
Spoiler: Through LOS Recovery
Download the recovery from here (or our mirror server)
Flash LOS recovery by executing
Code:
fastboot flash recovery <recovery-hotdogb-...-.img>
(Replace the text between the <> with the actual zip name)
Reboot into recovery mode
Format your data to f2fs
Go back to the main menu and tap Apply Update
Tap Apply from ADB
Sideload the ROM by executing
Code:
adb sideload <statix_hotodgb-...-OFFICIAL.zip>
(Replace the text between the <> with the actual zip name)
Reboot
You'll find more info in this section of LineageOS Wiki
Spoiler: NOT ADVISED: Through TWRP
Reboot to bootloader (!= fastbootd)
Connect your device to a computer and execute:
Code:
fastboot -w
Note: This will format your data, which means that a backup is advised
Reboot to recovery
Flash the ROM zipfile
Reboot to bootloader once again and execute
Code:
fastboot -w
Reboot to system
Spoiler: Through fastbootd
Dump the ROM zipfile through payload_dumper
Reboot to bootloader (!= fastbootd)
Connect your device to a computer and execute:
Code:
fastboot -w
Note: This will format your data, which means that a backup is advised
Now reboot to fastbootd executing:
Code:
fastboot reboot fastboot
Flash each partition (be sure to open the terminal window in the folder you extracted the payload):
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash odm odm.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor vendor.img
Reboot to system
Spoiler: Magisk
You can install Magisk by patching the boot image (which can be found here, download the one with the same date as the build you've flashed) or flashing its zip (Version 21.0+) once you've booted for the first time.
Update
Spoiler
Spoiler: Easiest way: Builtin OTA Updater
Go into Settings > System > Updater
Check for Update
Once it's finished updating press "REBOOT"
Note: Remember to flash whatever add-on you need (eg. Magisk) before rebooting to the other slot
Spoiler: Through TWRP
Disable thedevice PIN/Passcode
Reboot to recovery
Flash the ROM zipfile
If you want to flash further zips (e.g. Magisk) reboot to recovery to switch slots
Reboot to system
Add back your PIN/Passcode
Spoiler: Through fastboot
Dump the ROM zipfile through payload_dumper
Reboot to bootloader (!= fastbootd)
Now reboot to fastbootd executing:
Code:
fastboot reboot fastboot
Flash each partition (be sure to open the terminal window in the folder you extracted the payload):
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash odm odm.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor vendor.img
Reboot to system
F.A.Q. / Various Info
At the moment I'm shipping LOS kernel, for a simple reason: it's the only one that doesn't have issues with MTP, I'll switch to a custom solution as soon as OnePlus releases OOS11 kernel sources. In the meantime you're free to use a custom kernel (I highly suggest neutrino) if you don't care about MTP and rather prefer a better battery life.
SELinux is Enforcing and builds are user.
This ROM has been tested with Verizon and everything works as expected.
If you end up in a bootloop after a clean flash reboot to recovery and format your data partition to either ext4 or f2fs.
If you encounter issues with the fingerprint sensor be sure to flash the latest stable version of OOS (be sure to flash ALL the partitions, if you can use the unbrick tool/msmtool is even better, remember to select the "global" variant from the dropdown menu before starting the process) and then flash StatiX on top of that.
TWRP can't decrypt so you must disable your PIN/Passcode prior to rebooting to TWRP.
Follow these steps to format your filesystem to f2fs using Built-in/LOS recovery
Spoiler: Switch to f2fs
Clean flash the ROM using your preferred method
Boot into the system
Reboot to recovery
Tap on "Factory reset"
Tap on "Format data/factory reset"
Select "f2fs"
Tap on "Format data"
Reboot
[*][*][*][*][*]
You can fully pass SafetyNet by following these steps:
Spoiler: How to pass SafetyNet
Right after the first boot flash Magisk through your favorite method
Boot back into system
Open the Magisk app and enable MagiskHide
Install the MagiskHide Props Config module through the Magisk app
Reboot
Install and open a terminal app (e.g. Termiux) -or use adb shell-
Give it root permissions by entering
Code:
su
Enter
Code:
props
Enter
Code:
1
(aka "Edit device fingerprint")
Enter
Code:
f
(aka "Pick a certified fingerprint")
Enter
Code:
21
(aka "OnePlus")
Enter the number corresponding to your OnePlus 7T model
Confirm by entering
Code:
y
Reboot
Open the Magisk app and check SafetyNet status, you should now pass both basicintegrity and ctsProfile
Clear storage of both Google Play Store and Google Play Services
Enjoy
[*][*][*][*]
GPay fully works! How? Here it is:
Spoiler: How to setup GPay
Be sure to fully pass SafetyNet
Install GPay
Enable MagiskHide for GPay
Clear storage of both Google Play Store and Google Play Services
Install GPay
Enable MagiskHide for GPay
Enjoy
[*][*][*][*]
Known Issues:
Setting the USB preference to "File transfer" to trasfer files between the phone and PC leads to crashdump mode.
Workaround: keep the device connected to your pc and force reboot to bootloader by holding vol up + vol down + power, reboot to system: file transfer should now work fine. FIXED!
Nice
Another rom! Awsome!! Can't wait to try this out
Is there a three-finger screenshot?
Is there face unlock and how reliable is the fingerprint compared to stock?
swt95237 said:
Is there a three-finger screenshot?
Click to expand...
Click to collapse
Not yet, will be implemented very soon.
Nicholas6706 said:
Is there face unlock and how reliable is the fingerprint compared to stock?
Click to expand...
Click to collapse
No face unlock. Fingerprint is just as fast and reliable as on OOS, with no flickers whatsoever.
Any chance for micro G support?
NisseGurra said:
Any chance for micro G support?
Click to expand...
Click to collapse
MicroG hasn't been tested, but keep in mind that we (currently) prebuild our custom gapps package, which means that you'd need to remove any trace of it if you want to install MicroG.
zzkW35 said:
MicroG hasn't been tested, but keep in mind that we (currently) prebuild our custom gapps package, which means that you'd need to remove any trace of it if you want to install MicroG.
Click to expand...
Click to collapse
Yes, but to have microg support the services.jar need to have spoofing support.
As now there is no way to add it afterwards until smali has been updated to support android 11
NisseGurra said:
Yes, but to have microg support the services.jar need to have spoofing support.
As now there is no way to add it afterwards until smali has been updated to support android 11
Click to expand...
Click to collapse
At the moment I don't see a reason to support signature spoofing on the source side of things, since our builds contain gapps. Nonetheless if we added said support, would you really go through the hassle of first removing the built-in gapps and then installing microG?
Everything is working fine and smooth until now. I think this is the best implementation of adaptive brightness I've seen on custom ROMs on the Oneplus 7T. I'm having a little worse signal on wifi and on mobile but I think all custom ROMs are the same, I have a router that changes 2.4ghz and 5ghz wifi depending on the reliability and it doesn't seem to keep 5ghz for long, on OOS it did but I think it's the same on all custom ROMs I've tried until now. A+ for this first build.
Edit: Also a little things I've noticed (not major): Lockscreen colors are somewhat different before you unlock the phone, also when lockscreen (or always on screen) the fingerprint logo is full brightness even if you're not touching it.
Edit 2: Sorry, it was a known issue.
hectorviov said:
Everything is working fine and smooth until now. I think this is the best implementation of adaptive brightness I've seen on custom ROMs on the Oneplus 7T. I'm having a little worse signal on wifi and on mobile but I think all custom ROMs are the same, I have a router that changes 2.4ghz and 5ghz wifi depending on the reliability and it doesn't seem to keep 5ghz for long, on OOS it did but I think it's the same on all custom ROMs I've tried until now. A+ for this first build.
Edit: Also a little things I've noticed (not major): Lockscreen colors are somewhat different before you unlock the phone, also when lockscreen (or always on screen) the fingerprint logo is full brightness even if you're not touching it.
Edit 2: Found a bug, when connecting with USB to computer, if you change to file transfer mode, instead of only charging, system crashes. I once got a qualcomm dump screen and the second time that I tried it soft rebooted.
Click to expand...
Click to collapse
Its stated on the op.
hectorviov said:
Everything is working fine and smooth until now. I think this is the best implementation of adaptive brightness I've seen on custom ROMs on the Oneplus 7T. I'm having a little worse signal on wifi and on mobile but I think all custom ROMs are the same, I have a router that changes 2.4ghz and 5ghz wifi depending on the reliability and it doesn't seem to keep 5ghz for long, on OOS it did but I think it's the same on all custom ROMs I've tried until now. A+ for this first build.
Click to expand...
Click to collapse
I'll look into this asap.
hectorviov said:
Edit: Also a little things I've noticed (not major): Lockscreen colors are somewhat different before you unlock the phone, also when lockscreen (or always on screen) the fingerprint logo is full brightness even if you're not touching it.
Click to expand...
Click to collapse
I'm aware, it's a way to avoid weird screen flickers when FOD is pressed. Will be very likely fixed in the next release.
hectorviov said:
Edit 2: Found a bug, when connecting with USB to computer, if you change to file transfer mode, instead of only charging, system crashes. I once got a qualcomm dump screen and the second time that I tried it soft rebooted.
Click to expand...
Click to collapse
This is a known issue, check the 3rd post of this thread.
Awsome!! thanks
@zzkW35 phil da hero
zzkW35 said:
I'll look into this asap.
I'm aware, it's a way to avoid weird screen flickers when FOD is pressed. Will be very likely fixed in the next release.
This is a known issue, check the 3rd post of this thread.
Click to expand...
Click to collapse
for the icon dim one, we forward ported it on yaap (also there on aosip gerrit under https://review.aosip.dev/q/topic:"eleven-fod-dim"+(status:open OR status:merged) for quick repopicks) configurable by overlay so shouldnt mess with other devices either
Fingerprint entry and fingerprint unlocking are too slow Fingerprint entry is almost unavailable
OmkarTheAndroid said:
for the icon dim one, we forward ported it on yaap (also there on aosip gerrit under https://review.aosip.dev/q/topic:"eleven-fod-dim"+(status:open OR status:merged) for quick repopicks) configurable by overlay so shouldnt mess with other devices either
Click to expand...
Click to collapse
Thanks
谷歌原生 said:
Fingerprint entry and fingerprint unlocking are too slow Fingerprint entry is almost unavailable
Click to expand...
Click to collapse
As I already wrote in a previous reply: with stock kernel and no janky Magisk mods FOD is just as fast as on OOS. Have you changed kernel and/or flashed Magisk mods?

Teclast T30 [T1Px] -> suitable GSI ROMs

Project Treble - https://forum.xda-developers.com/c/project-treble.7259/
The Android 8.0 release includes Project Treble, a major re-architect of the Android OS framework designed to make it easier, faster, and less costly for manufacturers to update devices to a new version of Android. Treble is for all new devices launching with Android 8.0 and beyond.
Project Treble results in GSI ROMs.
There are quite a few GSI ROMs available, but not all of them are suitable for T30 tablet.
I started this thread to summarize my experience with using different GSI ROMs.
The prerequisite for installing GSI ROM is an unlocked Bootloader.
Description of GSI ROM versions installation file names:
<ARCH>_xyZ
<ARCH> can either be arm, a64 (arm32_binder64) or arm64
x can either be a or b
y can either be v, o, g or f
Z can be N or S
b = a/b
a = a-only
g = gapps
o = gapps-go
v = vanilla (no gapps included)
f = floss (free & open source apps instead gapps)
N = no superuser
S = superuser included
The most suitable GSI ROM for T30:
T30 requires A/B ROM instalation file type and Android 10.
Suitable are files with key "arm64-bgN" or "arm64-bgS" in filename. "g" if you want use GAPPS.
b = a/b
g = gapps
N = no superuser
S = superuser included
HavocOS
-> Installation video guide + download all necessary files
-> tested file: Havoc-OS-v3.8-20200821-Official-GApps-arm64-ab.img.xz
-> in TWRP install "RebootFix.zip" to aviid random restarts from attachment.
LeOS - https://forum.xda-developers.com/t/aosp-11-0-2020-11-27-leos-ungoogled-gsi.4195571/
-> installation, see bellow
-> Download tested file: 20201218-RW-bvN.img.xz
Family of TrebleGSI ROMs:
CAOS - Custom AOSP OS
-> installation, see bellow
-> Download, tested file: caos-v300j-201213-arm64-bgN.img.xz
LOSQ - LineageOS 17
-> installation, see bellow
-> Download, tested file: losq-v224-201017-arm64-bgN.img.xz
cRDrom - crDroid 6.11
-> installation, see bellow
-> Download, tested file: crdrom-v224-201019-arm64-bgN.img.xz
qiDroid - BootleggersROM 5.2
-> installation, see bellow
-> Download, tested file: qidroid-v224-201021-arm64-bgN.img.xz
Bless - BlissROM 12.12
-> installation, see bellow
-> Download, tested file: bless-v224-201015-arm64-bgN.img.xz
Nusantara 2.6 - Nusantara ROM
-> installation, see bellow
-> Download1, Download2 , tested file: Nusantara_v2.6-11-arm64-ab-GApps.img.xz
This is Android 11 ROM which fits to our System partition (file size is 2.7GB ONLY)
----------------------------------------------------------------------------------------------------------------------
How to install GSI ROMs on Teclast T30:
a) use this HavocOS Installation video guide, but use specific GSI ROM System file
b) use instructions from 2nd post
GSI ROMs are not perfect, they have bugs, and on the T30 tablet I noticed the following two:
- The battery charging animation does not work (charging works OK) when the tablet is switched off
- watching youtube videos in Chrome browser sometimes ends with a system restart (youtube application and embeded internet browser usually works OK)
I have tried all the above GSI ROMs and I was most satisfied with HavocOS and LOSQ.
I continue to use LOSQ, because it has the fewest errors and supports the NTFS filesystem on the inserted SD card.
If you want to try GSI ROM on your Teclast T30, choose LOSQ / HavocOS as the first choice.
I would be happy if here will start a discussion about GSI ROMs suitable for Teslast T30.
in any problems with PC and tablet communication (with platform tools or Flashtool), install the drivers "MTK_USB_All_v1.0.8.zip" or "platform-tools_r30.0.5-windows.zip" from attachment in the 2nd post
Alternative way to install GSI ROM:
(Prerequisite for installing GSI ROM is an unlocked Bootloader)
a) Unlock Bootloader
- To make the item "For developers" available on the tablet, in Settings / System / Advanced / Tablet information you need to click on the Build number 8 times
- A new "Developer menu" item will now appear in Settings / System / Advanced, turn on the "unblock OEM" item here
- In the task manager on the PC, check that there is an ADB device
- Turn off the tablet
- Hold down the Vol+ and Power buttons together, until the tablet starts
- Then use the Vol+ key to select the second Fastboot item and press the Vol- key to select it
- Connect the tablet to the PC via USB, in the PC to hear the sound of the connection
- Unzip platform-tools_r30.0.4-windows.zip to drive "C:\platform-tools" on your PC
- On your computer, click Start / Run, enter command "cmd", click OK, will appears black command window
- In the command window go to Platform-tools folder by command:
cd c:\platform-tools
- In the command window, enter:
C: platform-tools> fastboot devices
0123456789ABCDEF fastboot
- numbers may vary.
- If all is well, enter the unlock command:
fastboot flashing unlock
- You will be asked on the tablet whether or not you want to unlock the Bootloader by pressing Vol+ confirm it
- As soon as you confirm the action, what you see on the tablet, it will be unlocked
Next, enter the command:
fastboot reboot
- The tablet will restart (ALL your data will be deleted) and the tablet will return to its original state
- tablet will start initially setup
b) Install Hybrid ROM 1.2a
- in TWRP install GSI ROM image file to System partition
- in TWRP install Boot 1.05 image file to Boot partition (unpack ZIP from attachment, will get IMG file)
- restart System
- done
in any problems with PC and tablet communication (with platform tools or Flashtool), install the drivers "MTK_USB_All_v1.0.8.zip" or "platform-tools_r30.0.5-windows.zip" from attachment.
-> New version of HAvocOS from December 31, 2020
Lineage os is not booting and my tab is stuck on teclast logo.Any fix ??
Lightning Killer said:
Lineage os is not booting and my tab is stuck on teclast logo.Any fix ??
Click to expand...
Click to collapse
I assume you didn't follow the installation instructions exactly.
Maybe you forgot to install the Boot image from ROM 1.05 to Boot patition or you didn't unlock Bootloader.
You need to do install Boot 1.05 image in the end of installation process, after installing Lineage GSI on the System partition. Also, Bootloader must be unlocked (it is mentioned in that installation video)
I added necessary img file to attachment. Install it in TWRP to Boot partition. Then Lineage GSI ROM will boot (Bootloader must be unlocked!!!).
(unpack ZIP from attachment, you will get IMG file)
For everyone, I added a new alternative installation guide to the second post.
I have been using it for a long time HavocOS from December 31, 2020
(Havoc-OS-v3.12-20201230-Official-GApps-arm64-ab.img.xz)
It works well. Of course, it has minor flaws like all GSIs.
This is latest version HavocOS on Android 10.
Newer versions of HavocOS 4.1 are based on Android 11.
Unfortunately, the System image with GAPPS is too large to fit in the system partition of our tablet.
The System IMG size limit is 3GB.
GSI HavocOS 4.12 based on Android 11 available
I used this files:
Havoc-OS-v4.1-20210208-arm64-ab-vndklite-Official.img.xz
NikGapps-basic-arm64-11-20210130-signed.zip
It is necessary to incerase System partition size before install, do tgis steps:
- go to TWRP
- Wipe->Advanced Wipe->Select System->Repair or Change File System->Resize File System
- if errors will apperas, restart to TWRP a repeat the previous step again
It may not work first time for whatever reason, you may also try Repair FIle System there in this case, or just try a reboot
rbt07 said:
GSI HavocOS 4.12 based on Android 11 available
I used this files:
Havoc-OS-v4.1-20210208-arm64-ab-vndklite-Official.img.xz
NikGapps-basic-arm64-11-20210130-signed.zip
It is necessary to incerase System partition size before install, do tgis steps:
- go to TWRP
- Wipe->Advanced Wipe->Select System->Repair or Change File System->Resize File System
- if errors will apperas, restart to TWRP a repeat the previous step again
It may not work first time for whatever reason, you may also try Repair FIle System there in this case, or just try a reboot
Click to expand...
Click to collapse
Hi after installing this, I`m in a boot-loop, What can I do?
H1S8V87 said:
Hi after installing this, I`m in a boot-loop, What can I do?
Click to expand...
Click to collapse
Hi, you have to install Boot.img from ROM 1.05 to Boot partition through TWRP.
File is here in 2nd post.
Unpack ZIP anf install IMG file to Boot partition.
rbt07 said:
Hi, you have to install Boot.img from ROM 1.05 to Boot partition through TWP.
File is here in 2nd post.
Unpack ZIP anf install IMG file to Boot partition.
Click to expand...
Click to collapse
Hi, yeah I`ve done this several times. Nothing helps, I`m back to your Hybrid Rom
It worked for me, but I still preferred to go back to the older Havoc.
H1S8V87 said:
Hi after installing this, I`m in a boot-loop, What can I do?
Click to expand...
Click to collapse
For me it works...
I've found a fix for random reboots !!! Just flash this zip file in twrp
GSI HavocOS 4.5 based on Android 11 available
I used this files (click to download):
HavocOS-4.5-official-arm64-ab-vanilla.img
open_gapps-arm64-11.0-pico-20210713.zip
Links:
Havoc 4.5
arm64-ab-vndklite • Havoc-OS
Havoc-OS Downloads
download.havoc-os.com
OpenGAPPS
The Open GApps Project
OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.
opengapps.org
How to install:
- as a base system is my Hybrid ROM 1.2a
- Install GSI System image Havoc4. 5
- then increase System partition, do this steps:
a) go to TWRP
b) Wipe->Advanced Wipe->Select System->Repair or Change File System->Resize File System
c) if errors will apperas, restart to TWRP a repeat the previous step again
If incerasing fails, reboot to TWRP recovery and try again, now it will works now
- install GAPPS.
- reboot System
Add nusantra project gsi to the list !!! It is much more smoother than havoc and lineage os Here's the link for 2.5 (based on android 11 )
[email protected] - Browse /Nusantara-11 at SourceForge.net
sourceforge.net
+ It comes with gapps and can easily be flashed without having to resize the system partition
deleted
Lightning Killer said:
I've found a fix for random reboots !!! Just flash this zip file in twrp
Click to expand...
Click to collapse
Hi, thanks, it reallly work for HavocOS 3.8 GSI ROM.
rbt07 said:
Added to 1st post, thanks for info.
Do you use it? Write somthing about this ROM please.
Click to expand...
Click to collapse
It's the best gsi rom for teclast t30 I have used till date !!! It is very smooth and responsive. There are some customisation settings which crash when using in landscape mode but they work just fine in potrait mode.else this rom works like a charm for me.
Another gsi for teclast t30 that I would recommend is cr droid gsi based on android 11 . Here's the link -
TrebleGSI - Browse /crDRom11/2021.05.21 at SourceForge.net
sourceforge.net
Lightning Killer said:
It's the best gsi rom for teclast t30 I have used till date !!! It is very smooth and responsive. There are some customisation settings which crash when using in landscape mode but they work just fine in potrait mode.else this rom works like a charm for me.
Click to expand...
Click to collapse
I will try soon, thanks.

How To Guide List of Working GSI's for Realme GT Neo 2 | GSI of Custom Rom

WARNING
Author of this guide won't be responsible for damages that occur to your device
Proceed at your own risk
​
Overview-
After reading excellent guide by @SirCDA - Guide Link ,
I have tried several GSI's for our phone GT NEO 2 and in
this post I am sharing which GSI worked for me .
Requirements-
1) Backup All data , Internal storage will be wiped !
2) Use latest adb and fastboot binaries - Link
3) Enable USB Debugging
4) Bootloader should be unlocked - Link
5) TWRP installed (by @SathamHussainM - Link )
first connect phone to pc by usb cable
6) Empty vbmeta files by @SirCDA - Link )
Instructions-
Follow Guide from here ,
Basically you have to reboot to fastboot mode using adb or by going to TWRP and in reboot section selecting fastboot mode
after that flash vbmeta files
Then erase system partition by using command fastboot erase system
Then flash the downloaded GSI using fastboot flash system gsileos.img
It will take some time after that
Wipe all data using command fastboot -w
Then reboot to sysem using fastboot reboot command
List of Working GSI
​1) LeOS Arm64 A/B Android 11 - reported by me
Boots =Yes​Working = Calling(on 2g and 3g),Camera,GPS,Bluetooth,Wifi&Hotspot,FaceUnlock(with third party app)​Bugs= Volte,Fingerprint ,Fast Charging , and some minor bugs​
2) Havoc Os Arm64 A/B Android 11 - reported by me
Boots =No​Working=NA​Bugs= NA​
3) Ancient OS Arm64 A/B Android 11 - reported by @SirCDA
Boots =Yes​Working=Camera,GPS,Bluetooth,Wifi&Hotspot,​Bugs=Not Reported​
4)Ancient OS Arm64 A/B Android 12 - reported by me
Boots = No​Working=NA​Bugs= NA​
5) crDRom11 Arm64 A/B Android 11 - reported by me
Boots = Yes​Working=Calling(on 2g and 3g),Camera,GPS,Bluetooth,Wifi&Hotspot,FaceUnlock,Fingerprint(enrollment takes time to detect finger press slightly harder)​Bugs= VOLTE and Fast Charging​
LeOs Tips
​Use Signal as SMS app for working Messaging ,​Dont try to enroll fingerprint , it make system UI crash ,
Only use this Magisk if you want to root it else other magisk will cause system to hang at bootanimation .​Follow this guide to get supefast face unlock Click Here​Use LeOS laucher instead of Trebutchet Launcher since it has many customistaions .​Enable Devloper mode and inside that setup Smallest Width as 392 and Display Cutout as Punch Hole Cutout .​Customise your OS from these settings - Settings> Display>Styles and Wallpapers and Setting>System>Buttons , Status Bar and Gestures​​​crDRom11 Tips
Use Signal as SMS app for working Messaging ,​Be patient while enrolling fingerprint , use thumbs and make whole area of thumb connect with screen at the light green spot​Only use this Magisk if you want to root it else other magisk will cause system to hang at bootanimation ​FaceUnlock is included by default and it works​Enable Devloper mode and inside that setup Smallest Width as 392 and Display Cutout as Punch Hole Cutout Many customisations available in crDroid settings.​Screenshots attached in this post ​
Thanks to @SirCDA for his guide from which I understood that you need to flash empty vbmeta files else phone will directly boot to fastboot mode only.
Thanks to @phhusson for making tools that allow GSI to work properly
Thanks to @harvey186 for making LeOS .
I also tried
Havoc OS Android 10 Arm64 A/B but that did not boot .
Ancient OS Android 11 Arm64 A/B but that did not boot .
RMX3370 said:
I also tried
Havoc OS Android 10 Arm64 A/B but that did not boot .
Ancient OS Android 11 Arm64 A/B but that did not boot .
Click to expand...
Click to collapse
Ancient OS Android 11 on mine it started normal
SrCDA said:
Ancient OS Android 11 on mine it started normal
Click to expand...
Click to collapse
Please also mention the bugs and exact ROM name
RMX3370 said:
Please also mention the bugs and exact ROM name
Click to expand...
Click to collapse
AncientOS-R-Society-v5.4_arm64_AB_bvN-IRON
Updated OP , currently the least buggy working GSI is crDrom11 with only two recognised bugs VOLTE and Fast Charging
I've tried the following roms:
https://sourceforge.net/projects/ancientrom/files/gsi/V6.2/AncientOS-S-Shield-v6.2-arm64_bgN-Steel-20220417.img.xz/download
https://builds.haridhayal.workers.dev/ProtonAOSP/2022_03_24/proton-12.3.0-2022_03_24-vndklite-arm64_bgN.img.xz
Haven't tried phone functions cause don't have a second sim card.
AncientOS have no fingerprint and face unlock. For face unlock there is the option but cannot detect the face. With magisk v24.3 there is no way to pass safetynet. On this one I've also copied my apps and settings from my previous phone and haven't found any malfunctions.
Proton also have no fingerprint and face unlock options into settings. After installing magisk v24.3 the system broke. It boots but the launcher sometimes works sometimes no. Settings app not opening and some other apps crashes (com.android.phone, etc). I've tried this for just a fews minutes so probably there is a solution for magisk but I don't like the rom and lack of personalization so no more testing for me..
For both roms the recovery is partially broken. /data and /cache partitions are inaccessible. Even if I format them, after a normal boot the partitions are broken again.
Also if the brightness is reduced to zero it completely disables the screen but the touch continues to work.
I think I'll try corvus as the next rom.
@maxysoft @RMX3370 crDroid Android 11, works fingerprint reader and face unlock
SrCDA said:
@maxysoft @RMX3370 crDroid Android 11, works fingerprint reader and face unlock
Click to expand...
Click to collapse
I had already added it to working list (I tried them on 20 but was not having enough free time to update OP)
maxysoft said:
I've tried the following roms:
https://sourceforge.net/projects/ancientrom/files/gsi/V6.2/AncientOS-S-Shield-v6.2-arm64_bgN-Steel-20220417.img.xz/download
https://builds.haridhayal.workers.dev/ProtonAOSP/2022_03_24/proton-12.3.0-2022_03_24-vndklite-arm64_bgN.img.xz
Haven't tried phone functions cause don't have a second sim card.
AncientOS have no fingerprint and face unlock. For face unlock there is the option but cannot detect the face. With magisk v24.3 there is no way to pass safetynet.
Proton also have no fingerprint and face unlock options into settings. After installing magisk v24.3 the system broke.
I think I'll try corvus as the next rom.
Click to expand...
Click to collapse
Please also comment if VOLTE works oon these ROMs by trying to open any webpage while on a call
RMX3370 said:
WARNING
Author of this guide won't be responsible for damages that occur to your device
Proceed at your own risk
​
Overview-
After reading excellent guide by @SirCDA - Guide Link ,
I have tried several GSI's for our phone GT NEO 2 and in
this post I am sharing which GSI worked for me .
Requirements-
1) Backup All data , Internal storage will be wiped !
2) Use latest adb and fastboot binaries - Link
3) Enable USB Debugging
4) Bootloader should be unlocked - Link
5) TWRP installed (by @SathamHussainM - Link )
first connect phone to pc by usb cable
6) Empty vbmeta files by @SirCDA - Link )
Instructions-
Follow Guide from here ,
Basically you have to reboot to fastboot mode using adb or by going to TWRP and in reboot section selecting fastboot mode
after that flash vbmeta files
Then erase system partition by using command fastboot erase system
Then flash the downloaded GSI using fastboot flash system gsileos.img
It will take some time after that
Wipe all data using command fastboot -w
Then reboot to sysem using fastboot reboot command
List of Working GSI
​1) LeOS Arm64 A/B Android 11 - reported by me
Boots =Yes​Working = Calling(on 2g and 3g),Camera,GPS,Bluetooth,Wifi&Hotspot,FaceUnlock(with third party app)​Bugs= Volte,Fingerprint ,Fast Charging , and some minor bugs​
2) Havoc Os Arm64 A/B Android 11 - reported by me
Boots =No​Working=NA​Bugs= NA​
3) Ancient OS Arm64 A/B Android 11 - reported by @SirCDA
Boots =Yes​Working=Camera,GPS,Bluetooth,Wifi&Hotspot,​Bugs=Not Reported​
4)Ancient OS Arm64 A/B Android 12 - reported by me
Boots = No​Working=NA​Bugs= NA​
5) crDRom11 Arm64 A/B Android 11 - reported by me
Boots = Yes​Working=Calling(on 2g and 3g),Camera,GPS,Bluetooth,Wifi&Hotspot,FaceUnlock,Fingerprint(enrollment takes time to detect finger press slightly harder)​Bugs= VOLTE and Fast Charging​
Click to expand...
Click to collapse
Hey, crdroid a11 gsi volte isnt working???
akgosai96 said:
Hey, crdroid a11 gsi volte isnt working???
Click to expand...
Click to collapse
Nope, not working on any GSI

[A/B][A-ONLY][SCRIPT][READ-ONLY][EROFS][ANDROID 10+] Universal Disable Force Encryption for RO and RW "NEO STABLE"

Disable Force Encryption NEO​Do you all know what DFE is? no?
Anyway. Basically, your device has an encrypted data section "/data" by default. Let's look at the advantages of google's solution that we will lose after disabling encryption:
- Confidence in data retention. Even if your device has TWRP/OFOX or other custom Recvoery, before accessing your data, you will need to enter the password from the lockscreen, otherwise it will be impossible to read the data.
What disadvantages follow from this?
- As an enthusiast who wants to flash different ROMs, you may have noticed that every time that you flash a new ROM, you have to format the "/data" section. Which can be a pain.
Why is it necessary to do this?
- The fact that every ROM is assembled/compiled on a different database and may have different approaches (encryption keys) for data encryption. In order for this to work you need to format the data partition so that when the new ROM boots it can encrypt the system with its own unique encryption keys, so that the integrity of the data partition is maintained and it is accessible to the user.
So what does the DFE do?
- Removes the keys that are used to encrypt the data section from the fstab file
Read more about fstab here source.android.com
What are the advantages of using DFE?
- You don't need to FORMAT the data in the following cases:
*If you change the android database (From 11 to 12 and vice versa)
*If you change vendor database, miui/aosp/OOS/LOS and so on
*** !!!! You will still need to make wipe data for the ROM to work correctly
-There are also disadvantages:
*Since the data is not encrypted in any way, then access to them is free. Anyone who gets access to your device will be able to access ALL the data
*You need to carefully monitor the sequence of actions when installing or changing the ROM, so that the DFE is active, otherwise you may lose data because the data will try to be encrypted again, you will get a bootloop, and all data will be lost
What is DFE-NEO?
*Many people know DFE from this thread XDA, it has stopped working for A/B devices with dynamic partitions, there is also a problem that in some ROMs the system has the RO(Read-Only) status of the system partition. Starting with A13 Google will promote EROFS(Enhanced Read-Only File System) which will not be possible to manipulate without first converting to EXT4, in order to change the status to RW(Read-Write). Because of this, it is not possible to modify fstab directly in 100% of cases. This is where DFE-NEO comes in.
*The NEO method works by utilizing Magiskinit and Overlay.d GitHub
How does it work without Magisk?
*In fact, in no way. If my script does not detect magisk in the boot_a/Boot_b section, magisk will be installed, after which the main bianrys files will be deleted, so there will be no root access but magiskinit itself will continue to work. In this regard, the system boot time will be longer by 40-50 seconds ( from the brand logo )
And so what can this script do:
-Hides Encryption - Forces the system to think that the data is encrypted.
-Reflash recovery after OTA - only for devices with recovery in boot_a/_b
-Flash current recovery - only for devices with recovery in boot_a/_b
-Flash DFE
-Flash magisk
Spoiler: Arguments.txt
{
"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"
}
If you want to change the parameters , then you need to change the file argumetns.txt inside the archive , or put the modified arguments.txt to the archive, or to rebuild the archive with the changed argumetns.txt
Code:
# legacy or neo
DFE method=neo
# both | in-current | un-current
Flash SLOT=both
# none|system|bootloader|recovery
Reboot after installing=none
# You can add your own language, to do this, just drop
a file into the language folder by analogy with the topic
that is already there
# indo|russian|english
Language=english
Code:
# ================================================== #
Force reading arguments.txt=false
# ================================================== #
Flash DFE= true
Disable AVB= true
Disable QUOTA= true
Hide not encrypted= true
# ================================================== #
Flash Magisk= false
# ================================================== #
Reflash Recovery for OTA= false
Reflash current Recovery for Recovery= false
# ================================================== #
Wipe DATA= false
Remove PIN= false
# ================================================== #
Skip warning= false
Modes of operation of these parameters
These parameters have two modes:
• true (yes, true),
• false(no, not true)
Exceptions for specific parameters
• DFE method(DFE method)= neo(new method)
Another argument for DFE method
legacy(old method)
• Flash slot= both (patching boot_a and boot_b sections, also applies to magisk firmware, twrp)
More arguments for Flash slot
• in-current (patching of the boot_x section, where x is the current slot, also applies to magisk firmware, twrp)
• un-current (patching the boot_x partition, where x is the opposite slot)
• Reboot after installing(Reboot after installation)= none (no, that is, there will be no reboot)
More arguments for Reboot after installing
• system(restart into the system, simple reboot)
• bootloader (reboot to fastboot mode)
• recovery (reboot into recovery mode)
• Language(installer language)=english(English)
More arguments for Language
• indo(Indonesian)
• russian (Russian language)
So we have sorted out the modes of operation of all parameters. Now, what does each of them mean.
The values of these parameters
Here the functions of the parameters are described in true mode, for exceptions depending on the mode of operation of the parameter
• DFE method - DFE patching method
• Flash slot - patching the boot partition
• Reboot after installing - reboot after installation
• DISABLE DINAMIC REFRESHRATE - disable dynamic screen formatting, ONLY FOR MIUI
• Language - the language of the installer
• Force reading arguments.txt - dfe-neo will immediately address the arguments in arguments.txt without the possibility of creating a temporary arguments.txt
• Flash DFE - DFE firmware
• Hide not encrypted - The ROM will think that encryption is enabled
• Skip warning - at the end, a guide will be shown on the correct use of dfe after firmware
• Reflash recovery for ota - reinstalling recovery after ota updates, according to the Flash slot parameter mode=
• Reflash current Recovery for Recovery - flash the current recovery, according to the Flash slot parameter mode=
• Wipe DATA - deleting the contents of the /data section without formatting the internal memory (where the Android, Downloads, Music, etc. folders are located) If you sew DFE for the first time, then we still do format data
• Remove PIN - remove password
• Disable AVB - system integrity check is disabled (or whatever you call it, you can set false if you flash magisk)
• Disable QUOTA - (to be honest, I didn't understand what it was, but you can leave it true)
• Flash Magisk - Installing Magisk, according to the Flash slot parameter mode=
And you can also set up your own temporary arguments.txt during installation:
In DFE-NEO, in addition to using arguments.txt in .zip archive, you can still set up your temporary one.
Launch the dfe-neo archive and select Configure Arguments now ( volume + >> volume - )
And we are offered to configure the parameters.
Volume + indicates change
Volume - indicates select
What should I choose DFE method= neo or legacy?
• Neo method - patches the boot partition, we leave neo if the system partitions are read-only, also suitable if the system partitions are editable
• Legacy method - patches fstab.qcom in the /vendor/etc/ section, this method cannot be used if the system partitions are read-only.
Also be careful and read what the script writes at the end of the installation
If you data is encrypted, then after flashing DFE you need to format data
If DFE was installed with Magisk you can upgrade or downgrade the Magisk version later without flashing DFE again
If you uninstall Magisk via uninstall or Magisk app Then the DFE will stop its work! In this case, you will need to flash the DFE again
If DFE was WITHOUT Magisk, it WILL work, but you can also install Magisk later. And also follow the warning 1 and 2
If you install TWRP or another custom recovery, then DFE by analogy with Magisk, will stop working
If you update/Install a new ROM, then DFE will need to be flashed again, by analogy with Magisk
You can install DFE as a magisk module. BUT THIS IS NOT A MODULE, BUT JUST AN INTERFACE FOR INSTALLATION
Demo vido: https://t.me/mfpupdate/22
And also you can flash as a regular zip archive via TWRP, while you do not have to reboot TWRP.
The work consists of the same mechanism as Magisk. If your recovery is located in boot, then after updating / flashing twrp, just like magisk, dfe will be overwritten
After updating/changing ROM you need to reflash dfe again
You can flash dfe without rebooting twrp
No needed for system to be RW for DFE to work
Support erofs
Support flashing from magisk app ( like module magisk )
Later from the computer I will supplement the post. I will add screenshots, etc.
Download link - SourceForge
TG group : @PocoF3DFE
Donate only TG link https://t.me/mfpupdate/47
Great job Alexey. Very useful mod
LeeGarChat said:
Hello everyone, I am writing a script to disable encryption on A/B devices. if you help me with testing on other devices, I will be glad, at the moment it works fine for Poco f3 ( Alioth/Aliothin ). I'm sure it will work just as well on other devices.
And so what can this script:
Hide no encrypted - Forces the system to think that the data is encrypted.
Reflash recovery after OTA - only for devices with recovery into boot_a/_b
Flash current recovery - only for devices with recovery into boot_a/_b
Flash DFE
Flash magisk
The work consists of the same mechanism as Magisk. If u recovery if your recovery is located in boot, then after updating / flashing twrp, just like magisk, dfe will turn off
After update/change ROM u need reflash dfe
You can flashing dfe without reboot twrp
No needed RW system
Support erofs
Support flashing from magisk app ( like module magisk )
Later from the computer I will supplement the post. I will add screenshots, etc.
TG group : @PocoF3DFE
Click to expand...
Click to collapse
Great job bro its perfectly work on my Redmi Note 11 Spes, thanks buddy
sorry for my noob question:does it solove the read-only attribute for erofs partion，my phone is civi （code mona）
wsdyleon said:
sorry for my noob question:does it solove the read-only attribute for erofs partion，my phone is civi （code mona）
Click to expand...
Click to collapse
Yes, if I understand u. Anyway it's working on RW system and RO system. But anyway waiting 0.8.0 beta, because in > 0.7.0 patching only boot partitions, I think need patching recovery partition for device with recovery
LeeGarChat said:
Yes, if I understand u. Anyway it's working on RW system and RO system. But anyway waiting 0.8.0 beta, because in > 0.7.0 patching only boot partitions, I think need patching recovery partition for device with recovery
Click to expand...
Click to collapse
thank u for your answer，but i donnt konw how to flash it.i flash"dfe+magisk+reflash"on my phone in twrp，but bootloop for me
LeeGarChat said:
Yes, if I understand u. Anyway it's working on RW system and RO system. But anyway waiting 0.8.0 beta, because in > 0.7.0 patching only boot partitions, I think need patching recovery partition for device with recovery
Click to expand...
Click to collapse
my english still sucks,after flashing the zip ，the ro system would still ro，just dfe。am i right?
LeeGarChat said:
Download link - SourceForge
Click to expand...
Click to collapse
Great and Congrats!
Can you explain about each zip file made?
Is there a situation for each file?
What does each file do exactly?
Which file should I choose?
----------------------------------------
UPD.
Okay OP. Good work but have consequencies........
Here what I made:
installed magisk;
installed DFE-NEO-0.7.0-BETA+HNE.zip via magisk - modules;
Rebooted device.
Problem: Red message in the screen (look attached SS).
Solved with:
USB Debugging enable;​Permission adb Okay;​cmd command:​
Code:
D:\Program Android\platform-tools>adb shell
Mydevice:/ $ pm list packages
package:com.google.android.networkstack.tethering
package:com.android.fmradio
package:com.android.temperature
[...]
package:com.android.theme.icon_pack.filled.settings
package:com.android.watermark
package:com.android.dreams.basic
[...]
Mydevice:/ $ pm uninstall --user 0 com.android.watermark
Success
127|Mydevice:/ $ exit
D:\Program Android\platform-tools>adb reboot
D:\Program Android\platform-tools>
Reboot device and Red message good bye.
My device fir reference: MTK arm64 -- armv8-a - A11 - TWRP AB - ro.virtual_ab.enabled=true
lopestom said:
Great and Congrats!
Can you explain about each zip file made?
Is there a situation for each file?
What does each file do exactly?
Which file should I choose?
----------------------------------------
UPD.
Okay OP. Good work but have consequencies........
Here what I made:
installed magisk;
installed DFE-NEO-0.7.0-BETA+HNE.zip via magisk - modules;
Rebooted device.
Problem: Red message in the screen (look attached SS).
Solved with:
USB Debugging enable;​Permission adb Okay;​cmd command:​
Code:
D:\Program Android\platform-tools>adb shell
Mydevice:/ $ pm list packages
package:com.google.android.networkstack.tethering
package:com.android.fmradio
package:com.android.temperature
[...]
package:com.android.theme.icon_pack.filled.settings
package:com.android.watermark
package:com.android.dreams.basic
[...]
Mydevice:/ $ pm uninstall --user 0 com.android.watermark
Success
127|Mydevice:/ $ exit
D:\Program Android\platform-tools>adb reboot
D:\Program Android\platform-tools>
Reboot device and Red message good bye.
My device fir reference: MTK arm64 -- armv8-a - A11 - TWRP AB - ro.virtual_ab.enabled=true
Click to expand...
Click to collapse
Thanks for feedback. I'll try fix it. After installing DFE noe, is your device no longer encrypted?
LeeGarChat said:
Thanks for feedback. I'll try fix it. After installing DFE noe, is your device no longer encrypted?
Click to expand...
Click to collapse
I can make backup of Data now with TWRP.
But..........
I need to do more testing regarding the ROM.
I fixed a reset - FORMAT DATA with TWRP to see/test if everything would work fine after that.
Knowing that there would be a possibility it might not work, re-install your zip file and reboot to test again.
So there's a big problem: - WiFi connection doesn't work
- going to settings - Security - Encryption&credentials =====>>> Black Screen .......... stop ............ go back setting automatically
- others??
Do not worry about me. I have experience in getting the device running normally. The device is also not for my daily use.
So I will need time for more testing or you should write for users not to do a factory reset.
lopestom said:
I can make backup of Data now with TWRP.
But..........
I need to do more testing regarding the ROM.
I fixed a reset - FORMAT DATA with TWRP to see/test if everything would work fine after that.
Knowing that there would be a possibility it might not work, re-install your zip file and reboot to test again.
So there's a big problem: - WiFi connection doesn't work
- going to settings - Security - Encryption&credentials =====>>> Black Screen .......... stop ............ go back setting automatically
- others??
Do not worry about me. I have experience in getting the device running normally. The device is also not for my daily use.
So I will need time for more testing or you should write for users not to do a factory reset.
Click to expand...
Click to collapse
Send me download link on you ROM. I'll check structure
LeeGarChat said:
Send me download link on you ROM. I'll check structure
Click to expand...
Click to collapse
UMIDIGI Power 5 4GB_N_V1.0_20220315 - SPFT release
UMIDIGI_POWER5_4GB_N_V1-0_20220315.rar
Great.
lopestom said:
I can make backup of Data now with TWRP.
But..........
I need to do more testing regarding the ROM.
I fixed a reset - FORMAT DATA with TWRP to see/test if everything would work fine after that.
Knowing that there would be a possibility it might not work, re-install your zip file and reboot to test again.
So there's a big problem: - WiFi connection doesn't work
- going to settings - Security - Encryption&credentials =====>>> Black Screen .......... stop ............ go back setting automatically
- others??
Do not worry about me. I have experience in getting the device running normally. The device is also not for my daily use.
So I will need time for more testing or you should write for users not to do a factory reset.
Click to expand...
Click to collapse
Test 0.9.0 version please
LeeGarChat said:
Test 0.9.0 version please
Click to expand...
Click to collapse
Thanks man. I appreciate what you're doing.
I already tried with this and newer version DFE-NEO-0.10.1-BETA.zip having the same situation as before.
Unfortunately there is something that blocks the wifi working after installing DFE-NEO-x.xx.x-BETA.zip. Regarding this, I tested restoring the NVRAM, NVCFG and NVDATA files and the wifi started to work, however the part that DFE-NEO does is lost.
Is there something that DFE-NEO does with NvRam, NvCfg and NvData partitions?? Is it something that is a prerequisite for the ROM to work encrypted and consequently to work or not work the wifi?
I couldn't try all possibilities to investigate and test as I have been sick for a few days.
lopestom said:
Thanks man. I appreciate what you're doing.
I already tried with this and newer version DFE-NEO-0.10.1-BETA.zip having the same situation as before.
Unfortunately there is something that blocks the wifi working after installing DFE-NEO-x.xx.x-BETA.zip. Regarding this, I tested restoring the NVRAM, NVCFG and NVDATA files and the wifi started to work, however the part that DFE-NEO does is lost.
Is there something that DFE-NEO does with NvRam, NvCfg and NvData partitions?? Is it something that is a prerequisite for the ROM to work encrypted and consequently to work or not work the wifi?
I couldn't try all possibilities to investigate and test as I have been sick for a few days.
Click to expand...
Click to collapse
Some ROMs may not work correctly with DFE, due to the fact that the ROMs are designed to work with an encrypted data partition, or there are any protections. also, on some ROMs, the data split must be formatted according to the associated with certain keys -C and -O -g. DFE-NEO does not modify any partitions except boot, just like magisk. DFE-NEO works thanks to magisk-init, which allows you to run custom scripts during ROM startup. the script that is executed during system startup, makes a copy of fstab, deletes the encryption keys and mounts it in place of the original fstab, there is no full-fledged verification of the system. all work is based on magisk logic
Awesome job LeeGarChat, much appreciated by all users I have quoted your post link in other threads too so all can see the magic .
My device is Shamshung Galeksi M21 2021 (SM-M215G) But when I flashed from TWRP it showed some red error : 577 something like that, then when I flashed from Majisk it showed error code 3 : DFE-NEO only for virtual_ab devices
Treble Check shows my device is treble compliant having AB partition and TWRP displays following partitions: System, Vendor, Product, Odm, Cache, Data, EFS, Metadata, Sec EFS, Micro SD Card, USB OTG.
In my Shaomi Readmi Note 10 (mohito) TWRP displays Slot A & Slot B under Advanced Tab and ROMs get directly flashed to Inactive Slot B, also everytime I try flash new custom ROM I have to first flash MyUi Factory ROM and also System partition doesnt show in TWRP Mount section.
My question is what is the difference between Shamshung Galeksi M21 Android 11 out-of-box & Shaomi Readmi Note 10 Mohito ? why TWRP shows System partition mount in Shamshung and not in shaomi though both are A/B devices?
Pls help.
LeeGarChat said:
Some ROMs may not work correctly with DFE, due to the fact that the ROMs are designed to work with an encrypted data partition, or there are any protections. also, on some ROMs, the data split must be formatted according to the associated with certain keys -C and -O -g. DFE-NEO does not modify any partitions except boot, just like magisk. DFE-NEO works thanks to magisk-init, which allows you to run custom scripts during ROM startup. the script that is executed during system startup, makes a copy of fstab, deletes the encryption keys and mounts it in place of the original fstab, there is no full-fledged verification of the system. all work is based on magisk logic
Click to expand...
Click to collapse
Great News!
@2mkl and me solved the Wi-Fi issue......... But I not write here about.
Thanks again
lopestom said:
Great News!
@2mkl and me solved the Wi-Fi issue......... But I not write here about.
Thanks again
Click to expand...
Click to collapse
can you tell us in PM how you fixed the problems you wrote about earlier
History of updates and news
June 16
Update DFE-NEO 0.10.0 beta
- Added Feature, choose wether you want to flash DFE legacy / neo ( for legacy need RW system and not working with erofs)
july 14
Update dfe-neo beta 0.11.0
- Add magisk 25.1
- Add volume key selector
- Add remove lockscreen-pin select for key selector
july 20
Update dfe-neo beta 0.12.0
- Add new arguments:
- Wipe data
- Reboot after
july 22
DFE-NEO-0.12.4-BETA update
- Add additional settings (optional) like wipe data, reboot after
- Add disable dynamic refrash rate display ( only miui and works with dfe-neo method )
july 23
DFE-NEO-0.13.0-BETA update
- Add new arguments into arguments.txt, now u can change it without volume key
- Add new options "remove avb" " remove quota" ( default removed )
- The code has been slightly rewritten
- Update somthing patches for safety net fix based on later version 2.3.1 https://github.com/kdrag0n/safetynet-fix/releases/tag/v2.3.1
july 24
DFE-NEO-0.13.3-BETA update
- Minor fix
- Cleaning ui print
- Added calculation of script running time
july 25
I show by my example how to install a ROM in conjunction with DFE-NEO, as well as additional zips
Download DFE-NEO LINK ( Alway later version )
Thread XDA LINK
Please subscribe to the updates and news channel LINK
Thanks
july 28
DFE-NEO-0.14.0-BETA update
- Add language select ( it is currently configured only in the file arguments.txt )
Languages:
• Russian
• English
• Indo
• you can add your own language
- Fix ro.dfe.neo.state
- Add force reading arguments.txt
july 30
DFE-NEO-0.14.1-BETA update
- Reworked my_print function to work correctly in other languages. previously, it worked fine only with English
- Updated the Russian language. fixed typos
july 30
DFE-NEO-0.15.0-BETA update
- Add support A-Only devices
Languages v003:
- There was a bug with a large number of characters ****

Categories

Resources