[11][R][GSI][A51] HAVOC OS 4.1 GSI FOR SAMSUNG GALAXY A51[A51] - Samsung Galaxy A51 ROMs, Kernels, Recoveries, & Ot

UPDATED GUIDE FOR ANDROID 11[R]
Hey Guys,
Before you dive in, irrespective of your reading speed read this carefully and slowly for better understanding but if you cannot focus and read it slowly then you better give up music for a few weeks.
About the Device
Before you jump in and get your hands dirty.. you should know that what you will be installing is Generic System Image, It is not specifically made for your device so if you are going to install some other GSI other than this, you might face some issues.
If you are a beginner, you should Go Through Project Treble, just for the sake of knowledge.
Also Galaxy A51 has A/B partition and Supports Project Treble though remember that Treble Devices are not same as A/B devices and Vice Versa.
Things You’ll Need
A Computer (not an iPad)
Internet [requirement around 6 gigs (4.8 gigs optional, for downloading stock Firmware, Highly Recommended)]
Samsung Galaxy A51 (will not work on A50)
Patience and a madcap attitude.
Resources
Download Odin from the link given below and extract it in a folder.
https://odindownload.com/download/Odin3_v3.13.3.zip
Adb and Fastboot Drivers
https://gsmusbdrivers.com/download/adb-fastboot-drivers/#
Samsung Drivers
https://developer.samsung.com/mobile/file/68b2dc40-3833-4a8b-b58e-32f7aca25c00
Havoc OS GSI [ANDROID 11]
[11][OFFICIAL] Havoc-OS 4.1 [ARM64/ARM/A64][A/AB/AB-VNDKLITE][GApps/Vanilla] | XDA Developers Forums (xda-developers.com)
Don’t forget to check that there is “arm64” and “ab” written on the name of the file
Other option is with Gapps (it means the rom will come with Google Play services built in, otherwise it is Vanilla Android.
CHONDOE FLASHER
ChonDoe_Flasher.zip | by androidhowto for Utilities (androidfilehost.com)
Twerp Recovery [ANDROID 11]
Twrp+vbmeta_A11.tar | by androidhowto for Utilities (androidfilehost.com)
Encryption Disabler
Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip | by androidhowto for Utilities (androidfilehost.com)
EDIT
BEFORE YOU PROCEED
1. IT IS MANDATORY TO FOR THE DEVICE TO BE IN ONE UI 3.0, ANDROID 11. IF NOT DOWNLOAD ONE UI 3 FROM Model : SM-A515F - Galaxy A51 — Samfrew.com THEN PROCEED.
2. NOT ALL GSIs WILL WORK TO KEEP A LIGHT HEART ABOUT A GSI NOT WORKING.
Its Show time
1. Go to settings and go to about phone, tap build number 7 times and a dialog will appear, you are now a developer. [IF IT WAZ THAT EASY]
2. Go to additional setting or search developer options in the settings search bar
3. Once in the developer settings find OEM unlock and turn in on, scroll down and also turn on USB debugging, your phone will ask the permission for accessing the data by your computer.
4. Turn off your device. Get a usb cable and connect it to your computer.
5. While phone is off first press Volume UP and Volume Down together, and then then insert the usb cable into the phone while holding the buttons wait for two seconds. a blue screen will come up telling you about consequences and life choices.
6. Long press the Volume Up Button and a new blue screen will show up asking you for unlocking the bootloader. Press Volume Up to confirm. You device will erase everything and reset itself ( Don’t forget to take backup of your Data).
7. After the setup screen appears skip everything in the setup and enable developers option and enable USB debugging in the developer options.
8. Turn off your device again and Repeat step 5.
9. Press Volume up for entering the download mode
10. Now in your computer, Install Odin and open Odin.exe you’ll find your device as comm: xx. Go to options and disable auto reboot.
11. Now click on the AP button and select the twerp you downloaded. do not remove the usb cable and after it is installed press vol down and power, as the screen goes black hold with cable connected press and hold vol up and power until twerp boots up.
12. If you miss it repeat the process again but don’t let it boot to One Ui.
13. twerp press wipe => format data =>type yes. Press home button and again go to wipe advanced select Data, Cache and Dalvik and swipe to clear.
14. Press home again. Go to reboot and select recovery, twerp wil reboot. Once it reboots transfer the encryption disabler to your phone and in twerp press install select the storage, sdcard or internal storage, where you have stored the file, select it and swipe to install.
15. Now in your computer extract the Havoc os image and rename it as “system.img”.
16. Place the chondoe flasher zip and system.img in internal storage and then flash chondoe flasher zip
17. Reboot and KABLAMO You have installed Havoc OS.
Bugs
A small random issue in Auto Brightness
If you root with magisk and install modules, after you reboot your phone will get into a bootloop. Use Phh_Magisk but I aint sure if it’ll work or not Your call madcap.
NONE OF THE FILES IN THIS TUTORIAL HAVE ANYTHING TO DO WITH ME. If SOMETIHING HAPPENS I AM NOT RESPONSIBLE. ONLY DO IT AT YOUR OWN RISK.
Troubleshooting.
If you find errors in twerp, such as unable to mount vendor or system_root, or data. Then you got to install the stock One Ui Back again, therefore it is highly recommended to keep with yourself the stock firmware. You will need It. And it is 4.78 gigs. You can download it from
Model : SM-A515F - Galaxy A51 — Samfrew.com
To reinstall the stock firmware first extract it and the open odin and repeat steps 8 and 9, once your device is detected in Odin press the respective buttons and select the respective files such as for BL button select the file With BL in the name. Do it for buttons, BL, AP(once you select the file it will take long for it load into odin so do not panic and let it load, it might become unresponsive but use patience and wait.)CP , CSC. Click on start and you’ll have ONE Ui back on your device.
To Lock the bootloader repeat steps 5 and 6.
If you still want more stability and Control You can install a different Kernel NDataX from (@Hendamanu) https://forum.xda-developers.com/m/hendramanu.11224917/

Does fingerprint works?

adrgmez said:
Does fingerprint works?
Click to expand...
Click to collapse
nah fingerprint is not supported in this one.

GrandmaGotGuns said:
nah fingerprint is not supported in this one.
Click to expand...
Click to collapse
The fingerprint will work when it works in the phh gsi, they are all based basically there, it is best to test directly in phh aosp or send logs to the dev

I have a problem with brightness. It's lower than on stock. Extended brightness range doesn't help that much

AlexHHHx said:
I have a problem with brightness. It's lower than on stock. Extended brightness range doesn't help that much
Click to expand...
Click to collapse
You can try another gsi such as aosp11
[email protected] - Browse Files at SourceForge.net
aosp with gapps also works great.

I currently have havoc Android 10 installed, I would like to update to Android 11, I am very happy with the battery life, as I read this version it has the same small bugs, but the battery lasts the same as the previous version?

darkshinigami said:
I currently have havoc Android 10 installed, I would like to update to Android 11, I am very happy with the battery life, as I read this version it has the same small bugs, but the battery lasts the same as the previous version?
Click to expand...
Click to collapse
Yeah havoc 10 is very good for battery life..
There is really not much difference between battery life as vendor for Android 11 Is optimized but u might see a small drop in battery. Make sure you install one up 3.0 first... you may test battery life with the stock one ui 3 11.0.. what really matters is the vendor, system image rarely makes difference ( unless its loaded with bloat).
So in conclusion vendor for Android 11 is pretty much optimized as that of Android 10 with minor difference and should offer almost same performance for different GSIs..

Thanks for answering bro, the truth with ui 3.0 the battery drained very quickly and the performance was terrible, but it was sure because it was updated via ota and it was not a clean installation, I will give it the opportunity, I am tempted by the one that goes better even if it loses a bit of battery life, thanks
GrandmaGotGuns said:
Yeah havoc 10 is very good for battery life..
There is really not much difference between battery life as vendor for Android 11 Is optimized but u might see a small drop in battery. Make sure you install one up 3.0 first... you may test battery life with the stock one ui 3 11.0.. what really matters is the vendor, system image rarely makes difference ( unless its loaded with bloat).
So in conclusion vendor for Android 11 is pretty much optimized as that of Android 10 with minor difference and should offer almost same performance for different GSIs..
Click to expand...
Click to collapse

darkshinigami said:
Thanks for answering bro, the truth with ui 3.0 the battery drained very quickly and the performance was terrible, but it was sure because it was updated via ota and it was not a clean installation, I will give it the opportunity, I am tempted by the one that goes better even if it loses a bit of battery life, thanks
Click to expand...
Click to collapse
I don't think clean install will really help.. didn't help me and I did mention unless , one ui is bloat city
But it's worth a shot...

darkshinigami said:
Atualmente tenho o havoc Android 10 instalado, gostaria de atualizar para o Android 11, estou muito feliz com a duração da bateria, pois li esta versão ela tem os mesmos pequenos bugs, mas a bateria dura o mesmo que a versão anterior?
Click to expand...
Click to collapse
The fingerprint run perfectly?
Thanks

hacker812c said:
The fingerprint run perfectly?
Thanks
Click to expand...
Click to collapse
Sorry dude.. it doesn't.

GrandmaGotGuns said:
Sorry dude.. it doesn't.
Click to expand...
Click to collapse
Great job i m using havoc in j7
Stsrting use a51 today

bro I already managed to install havoc 4.1 and I love the smoothness, and the battery is on the right track, it does not seem to be better than havoc 3, but better than the stock for sure, but I have a big problem and it is that the option of two taps to wake does not work, do you know if it is a matter of havoc or it is not yet implemented in the gsi code of android 11

darkshinigami said:
bro I already managed to install havoc 4.1 and I love the smoothness, and the battery is on the right track, it does not seem to be better than havoc 3, butbetter than the stock for sure, but I have a big problem and it is that the option of two taps to wake does not work, do you know if it is a matter of havoc or it is not yet implemented in the gsi code of android 11
Click to expand...
Click to collapse
Dude first of all if it has Android 11 in its name then it definitely has the Android 11 code. As far as these roms go.. they start from a very stock Android 11 from Google and they modify up to their requirements.. mostly they just cut and paste the code which they already have from previous versions to the same libraries as the new version without making any changes as Android is not drastically updating its small improvements and more polish.. more over the features like lock screen visualizer or double tap are installed as apk inside the rom. So there can be a lot of reasons something might not work when changing the Android version without optimization. Definitely it's a problem from their side or it can be incompatibility with the vendor of the device.. not all features will work as you expect them to unless it is specifically optimized for the particular device. And since we are dealing with GSIs here.. they are generic so the above scenario of optimization is really over the top as it is made for each and every device. They mostly focus on important features and leave the rest on the vendors.. if it works then yay if not then eh...

GrandmaGotGuns said:
Dude first of all if it has Android 11 in its name then it definitely has the Android 11 code. As far as these roms go.. they start from a very stock Android 11 from Google and they modify up to their requirements.. mostly they just cut and paste the code which they already have from previous versions to the same libraries as the new version without making any changes as Android is not drastically updating its small improvements and more polish.. more over the features like lock screen visualizer or double tap are installed as apk inside the rom. So there can be a lot of reasons something might not work when changing the Android version without optimization. Definitely it's a problem from their side or it can be incompatibility with the vendor of the device.. not all features will work as you expect them to unless it is specifically optimized for the particular device. And since we are dealing with GSIs here.. they are generic so the above scenario of optimization is really over the top as it is made for each and every device. They mostly focus on important features and leave the rest on the vendors.. if it works then yay if not then eh...
Click to expand...
Click to collapse
Ah then my guess was not bad, but thanks for clarifying it, for now I will play it with the option to activate the ambient screen when lifting, and sometimes I forget that I am trying a generic rom, rather it surprises me that it is not have so many things broken, rather it is to be appreciated that there are people who take their time to compile and share these roms, it will be to wait maybe later they will implement it

GrandmaGotGuns said:
Sorry dude.. it doesn't.
Click to expand...
Click to collapse
The problem is aosp phh or only havoc?
Goodnight from brazil

I send new thread for phh developer for correction fingerprint a51 natively

Eu send new thread for phh developer for correction fingerprint a51 natively
GrandmaGotGuns said:
nah fingerprint is not supported in this one.
Click to expand...
Click to collapse
What is the reason for using chondoe and not twrp to flash the rom directly?

Thanks 30+

Related

[G800F/M/Y][ROM][7.1][NDE63P] CyanogenMod 14.1 for G800F/M/Y [Test 07/11/2016][eol]

CyanogenMod is discontinued.
This ROM is continued as a LineageOS ROM.
Check the G800F LineageOS ROM for more info.
This is a CyanogenMod 14.1 ROM for the Exynos3470 based Samsung Galaxy S5 mini (G800F/G800M/G800Y).
DO NOT USE IT FOR G800H OR YOU WILL BRICK YOUR DEVICE
Although G800F and G800H share the same name they are not related in terms of hardware due to the different SoCs used (Exynos vs. Snapdragon).
Hence please do not ask for support or ROMs for the G800H.
Important note: It is possible that flashing this ROM can cause efs partition issues. Therefore it is strongly recommended to make a backup of your efs partition before flashing this ROM. This can be done via TWRP.
Working features
HW accelerated GUI
Camera (pictures+video: Back+Front) (switching between camera and video-recording might crash the camera-app)
MTP storage
Flash Light
Bluetooth (A2DP, HFP, HID)
IR
Sound
SMS
Initiate and receive calls (the first ingoing call seems to have no sound)
Wifi
Mobile Data
USB-OTG (Keyboard, Mouse, USB-Audio, Mass-Storage)
NFC
Hardware sensors (Orientation, Compass, Proximity, Acceleration, Hall sensor, Step counter)
Light sensor (needed for auto-brightness)
Pulse sensor (preliminary and very inaccurate. Works with Apps like Kardiograph)
SD-Card as internal storage (new Android M feature)
GPS
Fingerprint scanner
Non-working features:
SELinux
Known issues:
See the Bug Report section of this thread
Disclaimer:
You flash this image at your own responsibility. I am not responsible for any damage that might be caused by flashing this image (bricked device, lost data, ...)
Flashing this kernel image will trigger the KNOX counter, so your warranty will be void.
Applications that use KNOX (e.g. "Private Mode") might not work anymore when returning to the stock ROM, as the device is regarded as compromised. Do not flash this ROM if you need those applications.
The image is only for Exynos3470 based S5 Mini variants SM-G800F/M/Y.
It might be instable, crash your device, drain your battery, or even might damage your smartphone (e.g. if an USB-OTG device drains too much power)
Some users reported that their touch-screen stopped working permanently after some weeks of usage. For some user's (two at the moment including me) NFC stopped working permanently. Probably this issues are not related to this ROM as also many stock user's complain about hardware issues (random reboots, black screens, unresponsive touchscreen) but you have been warned.
Backup your data before flashing and check if the original firmware is present (e.g. at SamMobile)
Click to expand...
Click to collapse
Before you start:
Backup your data, like call history, contacts, sms, WhatsApp messages, favourite app settings that are on internal and external sd (by using Titanium Backup or other apps available on PlayStore). At least all internal data will be lost in any case. If you have bad luck you might also loose data from your external sd card.
Download:
Odin3-v3.07 (it is contained in CF-Auto-Root)
TWRP 3.0.0 recovery image [25/03/2016] (AndroidFileHost Mirror)
CM 14.1 ROM for G800F/M/Y (Android File Host)
Google Apps (contains Google Play, ...) for Android 7.1. The following is recommended:
Open GApps Project, Platform:ARM, Android:7.1, Variant: whatever you prefer (e.g. "mini" or "nano")
Install recovery:
Reboot your device into Odin mode: turn off your device, then press Volume-Down + Home + Power button at the same time and release them.
Confirm the following warning message with the Volume-Up button.
Connect your device to your PC via USB
Make sure the device driver's are installed on your PC
Start Odin
In Odin select PDA and select the recovery image (recovery.tar.md5)
Check that only "Auto Reboot" and "F. Reset Time" is set
Click on "Start": the kernel image should be flashed now and the device should reboot afterwards. By flashing the recovery, your warranty will be void.
After the recovery flashing process was successful, power of your device. If not restart into Download mode and flash again or flash the stock rom.
Before you flash:
You need the latest TWRP recovery (see above). Otherwise TWRP might not be able to flash the ROM. This is because TWRP checks now if the device is "supported".
Wipe the device to avoid problems with remaining files from the old installation (see instructions below). This also applies if you already installed an older version of CM 14.1.
Flash CyanogenMod:
Reboot into recovery mode (Press Volume-Up + Home + Power button)
If you come from a stock ROM, this is your opportunity to make a Backup of your phone(Backup, then select Boot, System, Data, then swipe to backup). Note that the recovery might fail to restore the backup when you want to go back to the stock ROM (for me it got stuck after a restore during boot. But the backup was made with a different version of TWRP, so it might work in general) - simply do not expect too much of it at the moment.
If you haven't copied the installation files yet, you can now copy the GApps and CyanogenMod zip to your internal sd or external sd (be careful not to put the files into the data directory of the internal sd card as this will be deleted in the next step). Be sure that MTP is enabled (inside Mounts, click on Enable MTP), then, from your pc, copy the files. If MTP does not work from recovery, try it directly from Android or remove the external sd card from the phone and put it into your PC.
Wipe Dalvik Cache, Cache, System and Data (inside Wipe -> Advanced Wipe). Do not report problems if you did not wipe those partitions as the problems are most probably related to this!
Install the CM ROM zip-package
Install the GApps zip-package
How to root:
No SuperSu is needed as CyanogenMod already comes with integrated root support. Root access is disabled by default.
You normally do not need root access. If you want to activate root access for apps, do the following:
Open the Settings menu, select "About Phone"
Tap on the "Build number" entry seven times. You should be notified, that the developer settings are now active.
Open the Settings menu, select "Developer options". Enable root access by selecting "Apps" in the "Root-Access" setting.
In case you want to go back to the stock ROM:
lf you do not have the latest ROM for the G800F you can download it from SamMobile
Reboot your phone into Odin mode
Open Odin on your PC and connect your smartphone with your PC via USB
If you have a zip-file unzip it so that you have a .tar.md5 file
In Odin click on the PDA button and select the .tar.md5 file. Then press "Start".
Normally the stock rom fails to boot as the data from CM is still on the data partition. So after flashing the stock rom, reboot into recovery mode (it looks a bit different now). First wipe the data partition, then wipe the cache.
Reboot
Changelog
Code:
07/11/2016:
* Initial test build
This section is for developers:
A README file with build instructions can be found here:
Code:
https://github.com/cm-3470/android_device_samsung_kminilte
Sources:
Code:
https://github.com/cm-3470/android_device_samsung_kminilte
https://github.com/cm-3470/android_vendor_samsung_kminilte
https://github.com/cm-3470/android_kernel_samsung_kminilte
https://github.com/cm-3470/android_device_samsung_smdk3470-common
Developers welcome
At the moment the G800F/M/Y specific port of this ROM is only done by two persons (CTXz and hennymcc). Although Unjustified Dev also works on this ROM he does not own an Galaxy S5 Mini but a Galaxy Light which has a similar base but is different when it comes to camera, nfc and other components (maybe even slightly when it comes to audio and radio).
Help from other developers is always welcome. See the bug/feature section and this thread to see what is missing. Just give some short info (here in this thread or PM) that you want to work on some issue or feature so that work can be synchronized. Maybe there are also other devs that want to work with you on the same issue.
Knowledge in how the kernel works and good programming skills in C, C++ and Java would be nice but not necessary for all problems. At least you should be able to build the ROM and test your changes yourself but you do not need experience in porting ROMs.
Thanks to CTXz, Psyafter, spookcity138 and ayke for working on this ROM.
XDA:DevDB Information
[G800F/M/Y][ROM][7.1][NDE63P] CyanogenMod 14.1 for G800F/M/Y [Test 07/11/2016][eol], ROM for the Samsung Galaxy S5 Mini
Contributors
hennymcc, CTXz, spookcity138, psyafter, ayke
Source Code: https://github.com/cm-3470
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP Recovery [version >= 15/08/2015]
Based On: CyanogenMod
Version Information
Status: Testing
Created 2016-11-07
Last Updated 2017-02-01
Reserved
This is just a test build. CM 14.1 is not released yet and still instable. There are lots of known issues.
Here a short list of known problems:
First incoming call has no sound
Camera app crashes when you try to switch between camera and video recording mode (in this case: restart the app and recording will work)
Messages with "Browser crashed" will occur from time to time
The default browser does not always display all the text that was typed into a text field.
This was an awesome ROM but now I propose LineageOS 14.1
It works perfect (at least until now) for me ? great job
I hope @ayke brings OTA updates here to make everything easier
Enviado desde mi SM-G800F mediante Tapatalk
This rom is really great! Smooth and without big issues. Everything works as you said and here are some screenshots of Antutu if someone need them. Thanks devs!
What's the problem with first income call? The first one is the only one with no sound?
Great job Henny
@hennymcc
Robotic voice again ��
Everything else works fine
===========================
Guys I've been testing the Rom for a few hours, and it's preety awesome.
The only bad thing is the robotic voice. @spookcity138
As i remember you fixed this last time
Do your stuff mate
CostasGr said:
@hennymcc
Robotic voice again ��
Everything else works fine
===========================
Guys I've been testing the Rom for a few hours, and it's preety awesome.
The only bad thing is the robotic voice. @spookcity138
As i remember you fixed this last time
Do your stuff mate
Click to expand...
Click to collapse
what about battery drain?
sgilyin said:
what about battery drain?
Click to expand...
Click to collapse
seems normal so far
is this normal?
CostasGr said:
seems normal so far
Click to expand...
Click to collapse
With my usage yes.
The only problem is robotic voice
Hey !
Thanks for your amazing job (all of you), I don't have any browser crashes since I use chrome and I remove the stock browser, I also don't have any crash with my camera. I use Google Camera for that. Here is a list of bugs I've noticed:
- Chrome (stable) has crashed the first time I've opened it (only one time, that's why I did say that I don't have any browser crashes)
- Sometimes, something like "MTP Host" crashes..
- In Allo, while sending a message, there's a little sound, that's not a bug since it's in the app... But that sound is garbled (I don't know if that word is correct, I've used Google Translate for it)
I guess that's all..
Also, I don't have robotic voice... Good bye ! And thanks again
EDIT: About the "MTP Host" app.. it's the download app :/
Bugs
Hi there, thanks for your work on the rom really enjoying it and love Android 7.
Throughout my use I have discovered a bug with YouTube (not sure if it's the app or rom, but reporting anyway as did not happen on Mm) where changing into 720p causes the app to zoom into the upper left corner of the video. It can be remedied buy only using 360p but is rather annoying.
Again thanks for the work on the rom and all the best in the future. ?
Anyone have the link for xposed framework of this version?
Thomzey said:
Hi there, thanks for your work on the rom really enjoying it and love Android 7.
Throughout my use I have discovered a bug with YouTube (not sure if it's the app or rom, but reporting anyway as did not happen on Mm) where changing into 720p causes the app to zoom into the upper left corner of the video. It can be remedied buy only using 360p but is rather annoying.
Again thanks for the work on the rom and all the best in the future. ?
Click to expand...
Click to collapse
I also experienced that with some internet players when watching HD content..
Enviado desde mi SM-G800F mediante Tapatalk
CostasGr said:
@hennymcc
Robotic voice again ��
Everything else works fine
===========================
Guys I've been testing the Rom for a few hours, and it's preety awesome.
The only bad thing is the robotic voice. @spookcity138
As i remember you fixed this last time
Do your stuff mate
Click to expand...
Click to collapse
Well,as of now my sim card is not detected on CM14 for some strange reason. I seem to be alone in that. The robotic voice,if I remember correctly is linked to using the LP libs. Maybe someday we'll see official MM for the g800f. [emoji3]
Sent from my SM-G800F using Tapatalk
spookcity138 said:
Well,as of now my sim card is not detected on CM14 for some strange reason. I seem to be alone in that. The robotic voice,if I remember correctly is linked to using the LP libs. Maybe someday we'll see official MM for the g800f. [emoji3]
Sent from my SM-G800F using Tapatalk
Click to expand...
Click to collapse
You had changed the device tree as I remember and you fixed it last time ( I might be wrong I have no idea about developing) anyhow any help would be awesome because I need my phone for my work so I cant have that robotic voice... Thank you
Great job guys :good:
What are the chances like to get a first update soon? Or better said, moving to beta status?
I think the user respondings are quit positiv so far.
Greetings
Sunn76
Sunn76 said:
Great job guys :good:
What are the chances like to get a first update soon? Or better said, moving to beta status?
I think the user respondings are quit positiv so far.
Greetings
Sunn76
Click to expand...
Click to collapse
Most oft the current issues are Cm related so the CM-Team needs to update their sources time by time
Sent from my SM-G800F using XDA-Developers mobile app

DELETE

DELETE
DELETE
Reserved
For Indian Users +8.1 AOSP Users
If Jio 4g voice is offline Turn on Location and it will work
P.s Turn on location in Battery saver mode it will not consume more battery then.
Regards~
Great, I'll check this in few days Before this i have questions
Magisk works on this rom?
Can i return to nougat roms?
bohdankrulik said:
Great, I'll check this in few days Before this i have questions
Magisk works on this rom?
Can i return to nougat roms?
Click to expand...
Click to collapse
magisk is not working ? for now
---------- Post added at 01:49 AM ---------- Previous post was at 01:07 AM ----------
Treble Support Included
You can now flash any GSI Image on This TWRP
detailed Instructions on it will be added later ?
Regards~
Proximity sensor does not work
Earpiece volume is too low. Having trouble listening to calls.
And yes safetynet passes. I am able to use Google Tez and Snapchat.
mthepa said:
Proximity sensor does not work
Click to expand...
Click to collapse
it works just need to be calibrated
After installing this TWRP oreo, the screen does not work
I know you understand how important is to upload a source code of your rom. Because all your work based on a source code from other contributors of MTK community that they provided for everyone. Your rom can even has my code (just because one of the people you mentioned used it). So I think it is important to share the code with the community. It will helps to fix bugs and create new roms in the future. And it will be fair for all people have been making roms before you. Also some people (like me) want to make enchancements to original code from Android vendors but it will be impossible without source. I hope you understand my position and will make needed acions once you will be ready to show it for the public.
stanislavskiy said:
I know you understand how important is to upload a source code of your rom. Because all your work based on a source code from other contributors of MTK community that they provided for everyone. Your rom can even has my code (just because one of the people you mentioned used it). So I think it is important to share the code with the community. It will helps to fix bugs and create new roms in the future. And it will be fair for all people have been making roms before you. Also some people (like me) want to make enchancements to original code from Android vendors but it will be impossible without source. I hope you understand my position and will make needed acions once you will be ready to show it for the public.
Click to expand...
Click to collapse
there are some personal reasons for not opening device tree and vendors please understand also treble support is there so
any GSI image will bootup without issue so ahead from this I don't think no more roms needed also kernel sources are already there.
Regards~
murtaza1326 said:
there are some personal reasons for not opening device tree and vendors please understand also treble support is there so
any GSI image will bootup without issue so ahead from this I don't think no more roms needed also kernel sources are already there.
Regards~
Click to expand...
Click to collapse
My message was for Dinolek
And Treble support is good but not enough if you want to build a rom for yourself because Dinolek made changes for core system libraries/frameworks. And kernel is not a problem at all. The problem was to make everything working on system-level and Dinolek did it. That's awesome.
stanislavskiy said:
My message was for Dinolek
And Treble support is good but not enough if you want to build a rom for yourself because Dinolek made changes for core system libraries/frameworks. And kernel is not a problem at all. The problem was to make everything working on system-level and Dinolek did it. That's awesome.
Click to expand...
Click to collapse
i replied on his behalf only he have exams i was also there when he was bringing up this project now i openly say why sources are hidden you know lunik he charges money for developing roms also he didn't provided credits to patches owner dinolek did it for us i know other developers also want this but if all sources goes out i am damn sure lunik will copy his work and earn money from it so sources are not open tho kernel sources with modifications are out you can bringup with that kernel
stanislavskiy said:
I know you understand how important is to upload a source code of your rom. Because all your work based on a source code from other contributors of MTK community that they provided for everyone. Your rom can even has my code (just because one of the people you mentioned used it). So I think it is important to share the code with the community. It will helps to fix bugs and create new roms in the future. And it will be fair for all people have been making roms before you. Also some people (like me) want to make enchancements to original code from Android vendors but it will be impossible without source. I hope you understand my position and will make needed acions once you will be ready to show it for the public.
Click to expand...
Click to collapse
Source will be uploaded when rom get to beta stage.
I'm not using clear aosp sources, I based on Mediatek alps 8.1 source code, that's why it's hard to share it in proper way.
Nothing is based on work from other contributors, except maintained ones.
Stuck at boot animation
Test results
So i have tested this rom in my phone fr 2 days & i gt a result ...
What doesn't work
_________________
1)No navigation bar(no option to switch)
2)It doesn't restart (only power offs if u click on restart)
3)Power button doesn't work when u want to switch on the device
4)Proximity sensor error
5)gyroscope sensor error
6)Apps booting time is very slow
7)low ear-peace & speaker vol
8)Magisk error(if u flash magisk it stucks in boot-loop)
9)Physical home & back button doesn't work
10)Headphone sound output is bad
11)It takes more time to install an app
12)Camera is avg
13)2nd time if ur flashing this os it just says No OS INSTALLED while booting the device.
14)Call quality is not that much gud (avg)
What works fine
______________
1)OS booting & installing time is very fast
2)Battery management is very good
3)Ram management is very good
4)Wifi, hotspot, celular data, bluetooth tethering, USB tethering works fluently
5)location is very accurate
6)some of the basic sensors works
7)Touch works very well
8)very less heating issues
This are the results i gt in the testing of this rom in my device thanks to the developer nd all the persons who are been works on this
Cheers SAM.J
SAM.J said:
So i have tested this rom in my phone fr 2 days & i gt a result ...
What doesn't work
_________________
1)No navigation bar(no option to switch)
2)It doesn't restart (only power offs if u click on restart)
3)Power button doesn't work when u want to switch on the device
4)Proximity sensor error
5)gyroscope sensor error
6)Apps booting time is very slow
7)low ear-peace & speaker vol
8)Magisk error(if u flash magisk it stucks in boot-loop)
9)Physical home & back button doesn't work
10)Headphone sound output is bad
11)It takes more time to install an app
12)Camera is avg
13)2nd time if ur flashing this os it just says No OS INSTALLED while booting the device.
14)Call quality is not that much gud (avg)
What works fine
______________
1)OS booting & installing time is very fast
2)Battery management is very good
3)Ram management is very good
4)Wifi, hotspot, celular data, bluetooth tethering, USB tethering works fluently
5)location is very accurate
6)some of the basic sensors works
7)Touch works very well
8)very less heating issues
This are the results i gt in the testing of this rom in my device thanks to the developer nd all the persons who are been works on this
Cheers SAM.J
Click to expand...
Click to collapse
Thanks for feedback.
About 2 and 3, install latest 6.2.0.0G from flyme site, not twrp one.
For 4 flash the fix from rom download link fix_alsps_mblu2_oreo.zip, it will be included in next update.
About 5, we don't have gyroscope, on other firmwares it is emulated from magnetometer.
What do you mean in 9?
To disable hardware keys and enable software flash zip from faq.
SAM.J said:
So i have tested this rom in my phone fr 2 days & i gt a result ...
What doesn't work
_________________
1)No navigation bar(no option to switch)
2)It doesn't restart (only power offs if u click on restart)
3)Power button doesn't work when u want to switch on the device
4)Proximity sensor error
5)gyroscope sensor error
6)Apps booting time is very slow
7)low ear-peace & speaker vol
8)Magisk error(if u flash magisk it stucks in boot-loop)
9)Physical home & back button doesn't work
10)Headphone sound output is bad
11)It takes more time to install an app
12)Camera is avg
13)2nd time if ur flashing this os it just says No OS INSTALLED while booting the device.
14)Call quality is not that much gud (avg)
What works fine
______________
1)OS booting & installing time is very fast
2)Battery management is very good
3)Ram management is very good
4)Wifi, hotspot, celular data, bluetooth tethering, USB tethering works fluently
5)location is very accurate
6)some of the basic sensors works
7)Touch works very well
8)very less heating issues
This are the results i gt in the testing of this rom in my device thanks to the developer nd all the persons who are been works on this
Cheers SAM.J
Click to expand...
Click to collapse
2nd,3rd and 9th option from not working are working fine on my device.
Thank you very much for the firmware!

[GUIDE] Having a decent Android P GSI experience while Markus works.

So, this is how I PERSONALLY got a pretty decent experience on phhussons P GSI.
I am not responsible if something doesn't work or doesn't work the way you want.
Update: The PixelExperience build over on the Treble section works pretty well and eliminates the need for Overlays_Pr1.zip as well as Bitgapps. It's also including gapps (with SetupWizard as well as the pixel launcher). Same bugs as listed below.
Step 1: Trebleizing your phone
Download the latest trebleized Lineage OS ROM by SGCMarkus here and install it.
Make sure to read his guide to repartition your device carefully, otherwise this won't work.
Step 2: Prerequesites to have a nice time with Android P.
Before we wegin with the GSI stuff, you will have to copy the build.prop [or if you have the device fingerprint for your phone, just copy that] to a safe location.
Step 3: Installing the GSI
Download phhusson's latest Pie GSI from here
Unzip it and load it onto your phone's storage.
Proceed with wiping your /system, /data, /cache and Dalvik. Do not wipe /vendor (duh.)
Then install the image by tapping "Install image" button in the selection screen.
Step 4: Installing GAPPS
Download BitGapps from here. (I do **not** recommend using unofficial OpenGapps, as I run into several issues with them.)
[This version of GApps does not include any SetupWizard, which means you will have to download all your apps manually!]
Step 5: Fixing Device not Certified
While the notification doesn't pop up, it is indeed not certified and is (one of) the reason(s) why the phone gets so hot sometimes.
So what you need to do is download Magisk 16.7 (or later) as well as MagiskPropsHideConfig from here
as well as get any terminal app from the Play Store you like. [I personally like Material Terminal, as you can copy/paste in it]
After doing that, open a terminal window and type "props" (without quotation marks). Then select 1 and enter your device fingerprint (either from the build.prop we saved earlier or the fingerprint you saved somewhere)
Step 6: Makin' it nice.
So most of this besides maybe the Vibrator are purely optional, so you can go and enjoy some Pie if you wish.
Vibration:
- reboot to TWRP
- mount /vendor
- Install SGC's sGSI fix from here
- Install temp_vib_fix_joan_v2.zip from the attached files. Doesn't fix the dullness that occurs after some time.
DT2W:
- reboot to TWRP
- mount /system
- Install dt2w_on_gsi_joan.zip
Proper rounded corners and that new navbar[not required on PE P GSI]:
- Reboot to TWRP
- mount /vendor
- Install Overlays_PR1.zip from the attached files. (not mine, it's from erfanoabdi's Telegram group, will add proper credits if i manage to find the creator)
- Navigate to Settings -> System -> Gestures -> Swipe up to home
Additional System Accents (Yay! Colors!)
- Reboot to TWRP
- Install System_Accents_P.zip from the attached files. (not mine, it's from erfanoabdi's Telegram group, will add proper credits if i manage to find the creator)
Always-on Display (DT2W still works!)[Not required on PE P GSI]
According to phhusson, this does more than just enable AOD apparently, and it does something with the vibration, so installing this is on **your own risk** (not like it wasn't anyways)
-Reboot to TWRP
- Install P_AOD_FIX_-_by_ElHechicero.zip (not mine, credit goes to ElHechicero)
Getting Wellbeing [Not requried on PE GSI]:
-Download the Wellbeing.apk from ApkMirror
-Rename it to WellBeing.apk
-Move it into /system/priv-app/WellBeing/ (create the folder WellBeing)
-Reboot
Getting a nicer launcher with the appdrawer[PE P GSI uses the Pixel Launcher]:
-Download Nokias (HMDs) Launcher from ApkMirror
-Rename it to Quickstep.apk
-Replace /system/priv-app/Quickstep/Quickstep.apk with the Nokia launcher (which you renamed to Quickstep)
-Reboot
Issues:
- A lag when tapping on the "Default Apps" or the Bluetooth/NFC area in Settings
- Can get warmer when in playstore
- Vibration: Gets dull and sounds like static after a while. Hopefully SGCMarkus will be able to fix this or we'll be stuck with the dullness on P gsi's for now.
Not working:
-Hotspot
-NFC (?) [Seemed to work just fine on my device]
- Let me (or others, rather.) know.
Credits go to:
SGCMarkus
the LG V30 telegram group for the pointers
erfanoabdi's telegram group
ElHechicero
phhusson​
FAQs:
Is Launcher <Insert Launcher Name here> compatible?
- Any launcher is but don't expect the new Recents-Appdrawer to work.
Does the DAC work?
- Only in certain apps, as for all AOSP roms.
Screenies in attachments
You did a good job! I'm happy to have android pie on v30 but does its dac still not work?
thanks for the tutorial,
depending on your experience, do you think it suitable as a daily driver (I don't mind with the quad DAC) ?
Panokiaran said:
You did a good job! I'm happy to have android pie on v30 but does its dac still not work?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=77389334&postcount=15
Onkyo HF Player
USB Audio Player PRO
both are able to utilize the quad dac,
with the 2nd you can even use it with streaming
dr.guru said:
thanks for the tutorial,
depending on your experience, do you think it suitable as a daily driver (I don't mind with the quad DAC) ?
Click to expand...
Click to collapse
If you don't depend on Hotspot (and maybe NFC) and don't mind the occasional dullness, then yes. It is very daily driver capable. I'm using it.
Saxithon said:
If you don't depend on Hotspot (and maybe NFC) and don't mind the occasional dullness, then yes. It is very daily driver capable. I'm using it.
Click to expand...
Click to collapse
Any comments on battery life ?
Saxithon said:
Update: The PixelExperience build over on the Treble section works pretty well and eliminates the need for Overlays_Pr1.zip as well as Bitgapps. It's also including gapps (with SetupWizard as well as the pixel launcher). Same bugs as listed below.
Click to expand...
Click to collapse
is this the proper image: click ?
So this will eliminatre the need to install bitggaps, but I still need to go through points 5 and 6, right?
Is Nova compatible with this setup?
zacharias.maladroit said:
https://forum.xda-developers.com/showpost.php?p=77389334&postcount=15
Onkyo HF Player
USB Audio Player PRO
both are able to utilize the quad dac,
with the 2nd you can even use it with streaming
Click to expand...
Click to collapse
Thanks your
rdeets said:
Is Nova compatible with this setup?
Click to expand...
Click to collapse
Any launcher is. Just the new Recents Appdrawer will only work with certain devices. As of now those are working: AOSP Quickstep, Nokia Quickstep(Also called Android One launcher), The Pixel launcher (but doesn't work by installing?? [works on the PE P GSI tho]) and sometime in the future Lawnchair V2.
pizmak said:
is this the proper image: click ?
So this will eliminatre the need to install bitggaps, but I still need to go through points 5 and 6, right?
Click to expand...
Click to collapse
Yup and yup.
zacharias.maladroit said:
https://forum.xda-developers.com/showpost.php?p=77389334&postcount=15
Onkyo HF Player
USB Audio Player PRO
both are able to utilize the quad dac,
with the 2nd you can even use it with streaming
Click to expand...
Click to collapse
if the dac not work with jetaudio and spotify than why treble !!! ?
Sent from my LGM-V300S using XDA Labs
seloka180 said:
if the dac not work with jetaudio and spotify than why treble !!!
Sent from my LGM-V300S using XDA Labs
Click to expand...
Click to collapse
Has nothing to do with treble... its aosp in general.
me2151 said:
Has nothing to do with treble... its aosp in general.
Click to expand...
Click to collapse
thank you
Sent from my LGM-V300S using XDA Labs
why can't you just backup your rom and make a zip file?
everything working good and smooth, but i only can not instal MagiskPropsHideConfig from magisk or TWRP,
and camera always force close, but then open camera doing well in PE room.
ahhh so great to taste the sweetest pie
thanks to you and others dev
much love
Arif Ferdian said:
everything working good and smooth, but i only can not instal MagiskPropsHideConfig from magisk or TWRP,
and camera always force close, but then open camera doing well in PE room.
ahhh so great to taste the sweetest pie
thanks to you and others dev
much love
Click to expand...
Click to collapse
Have the same issue. Fixed by going to TWRP, wipe cache & Dalvik and then reflash the Magisk 16.7 zip, then boot to OS and install MagiskPropsHideConfig.
@Saxithon your thread name suggests that @SGCMarkus is working on sth.
Will he make a flashable zip of the Pie ROM that we can flash without treblezing?
FcBayernMinga said:
@Saxithon your thread name suggests that @SGCMarkus is working on sth.
Will he make a flashable zip of the Pie ROM that we can flash without treblezing?
Click to expand...
Click to collapse
Im working on Pie, kinda, but atm im stuck somewhere...
Have to figure out wtf is going on there
Followed the treble parttioning guide, flashed EnesSastim pixel expirience rom, and im happy to report its working fine so far. Left my Ext sdcard in exfat fromat working well so far too. Did not need to recertify my device. And no error after the setup wizard. I will change the apn settign to see if i can get lte, so far i am 4g.
Edit: cant seem to be able to use camera, even with open camera app.

[DISCONTINUED][ROM][9.0][SM-G930F] Lightheart OS [30/10/2020]

Lightheart 1.0 - The key to speed.​
Hi everyone. My name is Skulldron and for those of you who do recognise me, know me as the creator of Project Pixel, another one of the greatest ways to emulate the Pixel Experience, whilst keeping all the benefits of using OneUI and its stock optimized drivers as its base. Today I'm going to introduce something, different. Over the years of working on Touchwiz based ROMs, I've learnt the description of every little apk, every little permission, what it accepts and what it rejects, its pros and its cons. As a result of this experience, I have one of the best debloat lists out there, with each item on the debloat list, being tested, through extensive testing, and it goes over every file and every partition known in the OneUI OS. This exact same debloat script was used in Project Pixel, which has received positive review after positive review for how efficient and how lightweight OneUI became after the debloat. Today however, I present to you Lightheart OS, a new project that I will be building myself and updating monthly. Today I showcase Lionheart, the Lineage OS to my Cyanogenmod.
Key Features:
1. Heavily Debloated System: The debloat script that was made by me, has over 250+ debloated permissions, apks and other files.
2. Better Battery Performance due to Efficiency - With the removal of an incredible amount of bloat, along with better performance and lesser services, you should be looking at better SOTs and better standby times.
3. Kernel Power Control: With MTweaks and Magisk, you will be able to control your device’s clock speed and be able to force higher GPU and CPU Clock, when doing more intensive tasks such as gaming.
4. Better Kernel Performance - Due to the deepness of the debloat, the kernel now has more RAM and more space to be more efficient and allow it to focus on less threads at once.
5. Latest available patch with the promise of updates every month - Every month an update is released, the ROM will be updated along with it, with a time frame of 1-2 weeks.
6. Restored some stock Google Permissions - Some stock google framework was restored, such as the default setup wizard.
7. All Essential Samsung Features have been kept - All essential OneUI features have been kept alive, for the sole purpose of necessity.
8. Completely Deknoxed -The ROM has been Deknoxed and FRP lock measures have been disabled
9. VoLTE Supported
Individual Features:
1. AdAway
2. Eleven Music
3. Files GO
4. GBoard
5. Android Pie AOSP Emojis
6. Lightheart X Boot Animation
7. AOSP System Sounds
8. Samsung Gallery (Stripped Down and lightened to improve performance)
9. Samsung's Stock Camera with HDR parameter changes, debloated and additional video modes
10. SystemUI Tuner (Provides battery stats along with other useful customizations - Check QS icons and add it to QS Panel to view)
11. YouTube Vanced (Ad-free Youtube)
12. Mtweaks (Has Hardware Control - Similar to Kernel Adiutor but more tailored to Exynos)
INSTALL INSTRUCTIONS: (Backup everything,contacts, photos etc.)
1. Download the zip and download the latest Magisk (ROM will not boot if Magisk is not flashed due to encryption procedures)
2. Wipe System, Data, Dalvik Cache and Cache
3. Flash the zip and flash Magisk.
Notes:
- To view Battery Stats and Storage, pull down the Quick Settings Panel and on the top right click the three bubbles button and then Button Order. Then move the new Battery and Storage icon to the Quick Settings.
- Set Trebuchet as default launcher, for better battery savings. OneUI Home was only included for its app switcher.
Changelog:
1.0 - Initial Release
If changes are made, they will be highlighted in the next post.
Download Links:
1. Lightheart 1.0:
https://drive.google.com/file/d/1cqQXrQecOmmXEhXnUx6GL8aV7_Xsarwk/view?usp=sharing
2. Magisk Manager:
https://github.com/topjohnwu/Magisk/releases
3. Magisk:
https://github.com/topjohnwu/Magisk/releases/tag/v20.4
Credits and kernel source:
Cronos Kernel Source: https://github.com/ananjaser1211/Cronos_8890/releases/tag/V4.0-Pie
@arcatarc for permission to use his base
Check the screenshots tab to see screenshots of the ROM in action.
XDA:DevDB Information
Lightheart 1.0, ROM for the Samsung Galaxy S7
Contributors
Skulldron
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest Bootloader Available
Based On: OneUI
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2020-10-30
Created 2020-10-30
Last Updated 2020-10-31
Samsung note fe base???
Hi, thanks for the ROM. Will try it. Could you please provide md5?
Can't use GPay
mie_ayam said:
Samsung note fe base???
Click to expand...
Click to collapse
Yes it is running the base from a Note FE. In particular the SuperLegerra ROM
wow, ... and echo cancellation works perfect ... but two things that I miss so far
the option "kill app back button" in the settings -> developer options ... please don't forget to build-in
the possibility to mount the SD card in the file system
Both options are default in LOS ... and yes, I know it was an initial release.
Thx for your work. we are hopefully waiting for the improvements!
:good::good::good:
Download and trying to install tonight
Info regarding phone stuck on boot pic
Hi there,
I have little experience with custom roms etc. I had installed LineageOS some moths ago as my phone was working poorly on stock rom and now with LOS 17.1 was starting to have problems again. Like an hour ago decided after some research to install this rom. However, after flasing the rom and magisk (I couldnt flash Gapps as error 20 appeared), my phone got completely stuck on boot picture (SAMSUNG GALAXY S7; POWERED BY ANDROID). I have both tried to get into twrp (previously installed) and download mode. No luck in any of the cases. I have tried to do the same from odin, to flash again twrp. However, as I cannot access download mode, I didnt work.
Now, I´m trying my best to figure out how to install some OS and continue from there, or at least be able to flash twrp and install another ROM.
I would much appreciate any advice in the matter.
Thanks in advance.
EDIT: NEW SITUATION. No need of help anymore (by now)
iggamez said:
Hi there,
I have little experience with custom roms etc. I had installed LineageOS some moths ago as my phone was working poorly on stock rom and now with LOS 17.1 was starting to have problems again. Like an hour ago decided after some research to install this rom. However, after flasing the rom and magisk (I couldnt flash Gapps as error 20 appeared), my phone got completely stuck on boot picture (SAMSUNG GALAXY S7; POWERED BY ANDROID). I have both tried to get into twrp (previously installed) and download mode. No luck in any of the cases. I have tried to do the same from odin, to flash again twrp. However, as I cannot access download mode, I didnt work.
Now, I´m trying my best to figure out how to install some OS and continue from there, or at least be able to flash twrp and install another ROM.
I would much appreciate any advice in the matter.
Thanks in advance.
EDIT: NEW SITUATION. No need of help anymore (by now)
Click to expand...
Click to collapse
Could you write down here how you can solved the proble, it might be helpfull for other.
Hi All, has anyone got EdXposed working?
I've installed magisk 21.1, riru core 21.3 , and riru YAHFA 0.4.6.4 EdXposed manager shows framework not active :/
Does mobile hotspot work?
I've been looking for a ROM that has kept the Samsung gallery and camera so I want to try this ROM. but I need to be able to use mobile hotspot so please let me know if it works fine. Thx
Hello, the ROM works great. There are some minor things. Like always on display does not work with option to tap the screen to show for 10 seconds. Also for some reason I can't instal Revolut from the play store. And lastly Titanium backup does not restore all the apps. I could not figure out a way how to make that work.
The hotspot works fine on mine.
I had the same issue with Titanium backup.
In the end I used split screen and installed each app from the play store, then restored data only.
Has anyone got xposed working?
Gapps
Do I need to flash gapps or is it included?
I'm currently using lineage is 16 with gapps. Do I need to flash gapps again if flashing a ROM again? Sorry I'm a newbie.
Wara35 said:
Do I need to flash gapps or is it included?
I'm currently using lineage is 16 with gapps. Do I need to flash gapps again if flashing a ROM again? Sorry I'm a newbie.
Click to expand...
Click to collapse
No gapps needed.
---------- Post added at 03:59 PM ---------- Previous post was at 03:52 PM ----------
@Skulldron, thanks for the ROM, works great and it's stable. Just few things. Could you please update the Adaway app? There is a newer stable version on xda available. I tried to update it myself but it was not possible. Also could you please fix the Always on display function? The tap on screen option does not work.
Blato said:
Hello, the ROM works great. There are some minor things. Like always on display does not work with option to tap the screen to show for 10 seconds. Also for some reason I can't instal Revolut from the play store. And lastly Titanium backup does not restore all the apps. I could not figure out a way how to make that work.
Click to expand...
Click to collapse
As I experienced from other ROM that based on Note FE base, the Galaxy S7 cant show AOD with tap to show mode due to hardware problem, so please choose always show option on the setting
Flashing a different rom, I do like this rom but need xposed and it's annoying that YouTube and adaway are system apps.
6sicSIX said:
Flashing a different rom, I do like this rom but need xposed and it's annoying that YouTube and adaway are system apps.
Click to expand...
Click to collapse
Youtube and Adaway can be removed with System App remover or Link2sd from Play Store. Then you restart the S7 and install Adaway from github and Vanced.app
I do like this rom, espicially the first boot right after install, which was really fast, made an impression. Probably the most battery friendly and lite-weight One UI-Rom one can find. One usability problem for me was the *missing feature that increased touch sensitivity*. With my screenprotector on, I have to push harder and several times before successfully pulling down the notification bar or when writing or selecting.
Is it just me or is SmartSwitch taking a long time/not restoring messages? I get to the part when it would start restoring messages but then it just never loads.. other then that, the ROM is great!
6sicSIX said:
Hi All, has anyone got EdXposed working?
I've installed magisk 21.1, riru core 21.3 , and riru YAHFA 0.4.6.4 EdXposed manager shows framework not active :/
Click to expand...
Click to collapse
I tried many versions of modules ,but no luck .Is possible to work exposed framework?

How To Guide A Complete Guide to Unlocking and Flashing for the A52s 5G.

Disclaimer​
Your warranty will be void
Some carriers' Terms of Service prohibit device modifications
Modifying will trip Samsung Knox and SafetyNet, so be aware that some apps will cease to work
I AM NOT RESPONSIBLE FOR BRICKED DEVICES, FAILED ATTEMPTS AND OTHER CAUSES OF IMPROPER USAGE OF THIS GUIDE!​Now that we got that out of the way, we can continue.
Unlocking the Bootloader​UNLOCKING THE BOOTLOADER WILL ERASE ALL OF YOUR DATA!​
Go into Settings > About Phone > Software Information
Find Build Number and quickly tap it 7 times. This will enable Developer Options
Find OEM Unlocking and USB Debugging options and enable them
Turn off the phone
Hold Volume Up and Volume Down while connecting your phone to a PC to boot into Download Mode
Read the Warning carefully to understand it and then if you want to continue press Volume Up
On the Unlock Bootloader screen, press and hold the Volume Up button one more time (This is the step that erases all of your data, if you don't want to do it, now is the time to turn back!)
After the automatic reboot, repeat steps 1. - 3. and make sure that OEM Unlocking is greyed out and enabled
Congratulations! You bootloader is now unlocked.
Flashing a Custom Recovery​Credit to @BlackMesa123 for this guide.
Rooting your Phone​
Download the latest version of Magisk on your Computer
Follow the Official Installation Guide from Magisk developers
Flashing a GSI (Generic System Image)​
Choose a GSI from this List
Power Off your phone and connect it to your Computer
Hold Volume Up and Power buttons, after the logo appears, release only the Power button, this will boot you into TWRP
Do a Wipe and transfer the GSI file from you Computer to your Phone
Click Install >Image Flashing, find your transferred GSI file and tap on it.
Toggle the System Image option and flash the file.
After flashing Format Data to be able to boot into your new System.
I know your Camera doesn't work, don't worry check out this Post to get it to work again.
Useful Resources​
A52s bootloader/modem collection repository
OrangeFox Recovery
SafetyNet Fix for Magisk (Zygisk)
Custom ROMs: RayOS (One UI 4.1), NcX (One UI 5.0)
Mesa's Custom Kernel
Credit to @BlackMesa123 @Ryzen5950XT @ShaDisNX255 for the additional resources.
That's it! Thank you for following the guide and enjoy your unlocked Samsung.
This is very helpful thanks
Thank you for the guide. Here's some additional resources/changes that can be added in the post:
- A52s bootloader/modem collection repository
- OrangeFox Custom Recovery, same as TWRP but with a different UI
- SafetyNet and (some) Knox features can still work with the correct adjustments. See the SafetyNet fix for Magisk (Zygisk) or custom ROM's such as RayOS (One UI 4.1), NcX (One UI 5.0)
- Mesa's Custom Kernel, greatly improves device's performance
Hoping to see the list enhanced soon.
BlackMesa123 said:
Thank you for the guide. Here's some additional resources/changes that can be added in the post:
- A52s bootloader/modem collection repository
- OrangeFox Custom Recovery, same as TWRP but with a different UI
- SafetyNet and (some) Knox features can still work with the correct adjustments. See the SafetyNet fix for Magisk (Zygisk) or custom ROM's such as RayOS (One UI 4.1), NcX (One UI 5.0)
- Mesa's Custom Kernel, greatly improves device's performance
Hoping to see the list enhanced soon.
Click to expand...
Click to collapse
Thank you for the links, thread is now updated.
Quick question, with MCK, should I wipe everything before/after flashing and will it work with PE+ GSI?
kzyx said:
Thank you for the links, thread is now updated.
Quick question, with MCK, should I wipe everything before/after flashing and will it work with PE+ GSI?
Click to expand...
Click to collapse
You shouldn’t wipe anything when flashing the kernel. If the stock kernel works fine, I don’t see why mine shouldn’t
Everything is working perfectly, thanks for the guide. I installed the PixelExperience GSI but for some reason Fingerprint sensor is not working. The process is stuck on "Touch the sensor" and the sensor is not lighting up. Yes, I set the color of fingerprint sensor to White (and even tried all other colors).
I even have the following options checked
- Enable Extra Sensor
- Enable workaround for broken fingerprint sensor
- Enable workaround for white-ish screen
Any help will be appreciated, thanks.
Mian-786 said:
Everything is working perfectly, thanks for the guide. I installed the PixelExperience GSI but for some reason Fingerprint sensor is not working. The process is stuck on "Touch the sensor" and the sensor is not lighting up. Yes, I set the color of fingerprint sensor to White (and even tried all other colors).
I even have the following options checked
- Enable Extra Sensor
- Enable workaround for broken fingerprint sensor
- Enable workaround for white-ish screen
Any help will be appreciated, thanks.
Click to expand...
Click to collapse
I don't know what could be the issue, maybe try to google or try disabling and enabling the fingerprint lock again.
I have tried few GSI Roms. Here is my summary:
Android 13
- AOSP, Android 13, No image with GAPPs pre-installed and cannot seem to install it. Tried NikGAPPs, and LiteGAPPs, both didn't work
- Google GSI, Android 13, same issue
- Pixel Experience, Android 13, GAPPs pre-installed but Fingerprint sensor won't get detected.
Android 12
- AOSP, Android 12, GAPPs pre-installed, Fingerprint sensor detected (changing color to white). Will stick to it unless there is an issue detected.
Mian-786 said:
I have tried few GSI Roms. Here is my summary:
Android 13
- AOSP, Android 13, No image with GAPPs pre-installed and cannot seem to install it. Tried NikGAPPs, and LiteGAPPs, both didn't work
- Google GSI, Android 13, same issue
- Pixel Experience, Android 13, GAPPs pre-installed but Fingerprint sensor won't get detected.
Android 12
- AOSP, Android 12, GAPPs pre-installed, Fingerprint sensor detected (changing color to white). Will stick to it unless there is an issue detected.
Click to expand...
Click to collapse
Thanks for the feedback, have you tried any ROMs instead of GSIs?
You have links for them in this thread.
kzyx said:
Thanks for the feedback, have you tried any ROMs instead of GSIs?
You have links for them in this thread.
Click to expand...
Click to collapse
Nope, I tried to find a good custom rom for A52s but couldn't find any.
What about volte and hotspot on GSI pixel experience 13?
Mian-786 said:
I have tried few GSI Roms. Here is my summary:
Android 13
- AOSP, Android 13, No image with GAPPs pre-installed and cannot seem to install it. Tried NikGAPPs, and LiteGAPPs, both didn't work
- Google GSI, Android 13, same issue
- Pixel Experience, Android 13, GAPPs pre-installed but Fingerprint sensor won't get detected.
Android 12
- AOSP, Android 12, GAPPs pre-installed, Fingerprint sensor detected (changing color to white). Will stick to it unless there is an issue detected.
Click to expand...
Click to collapse
Thanks for your summary,
Is there any experience with MicroG on this device with AOSP 13?
7slaper said:
Thanks for your summary,
I'm on AOSP 13 now, but perhabs it's better to go back to 12. I'm very interested in the AOSP with the GAPPs pre-installed. Could you share a link to the file?
Click to expand...
Click to collapse
I got the image from AOSP under the official Android 12/12L section. You can find release here. The exact image I got is the system-squeak-arm64-ab-vndklite-gapps-secure.img.xz one since the standard gapps one came with an app called "superuser" which I couldn't seem to uninstall (I tried the scripts to remove supersu). This caused my banking apps to not run. That is why I installed the "secure" one and then installed Magisk and added my banking apps to the defylist.
Zhazhael said:
What about volte and hotspot on GSI pixel experience 13?
Click to expand...
Click to collapse
I think VoLTE was available as an option in one of the ROM I tested but I don't remember exactly. Currently AOSP 12 doesn't support it. Hotspot worked on every ROM just fine.
Mian-786 said:
I got the image from AOSP under the official Android 12/12L section. You can find release here. The exact image I got is the system-squeak-arm64-ab-vndklite-gapps-secure.img.xz one since the standard gapps one came with an app called "superuser" which I couldn't seem to uninstall (I tried the scripts to remove supersu). This caused my banking apps to not run. That is why I installed the "secure" one and then installed Magisk and added my banking apps to the defylist.
Click to expand...
Click to collapse
Hi Mian,
Thanks for your response. When I typed my question I realized that in the end I want to have and de-googled phone. So I changed my question in the direction of MicroG. I didn't expect you to be so quick with answering.
7slaper said:
Hi Mian,
Thanks for your response. When I typed my question I realized that in the end I want to have and de-googled phone. So I changed my question in the direction of MicroG. I didn't expect you to be so quick with answering.
Click to expand...
Click to collapse
I haven't tried MicroG in any of the ROM. I just to have as little Google apps as possible but if you do find a good guide, let me know, I will try to use a de-googled phone.
Thx, all worked.
Mian-786 said:
I haven't tried MicroG in any of the ROM. I just to have as little Google apps as possible but if you do find a good guide, let me know, I will try to use a de-googled phone.
Click to expand...
Click to collapse
I've installed MicroG. But it seems AOSP doen't allaw support system spoofs signature. Play services (GmsCore) is installed but without the spoofed signature it can't do much I guess...
I have been using AOSP Android 12 for the past week or so. Most of the things just plain works but somethings don't. Here is the list of things that are not working so you can decide if the hassle of installing GSI is worth it or not.
- Proximity Sensor is worse than it was in OneUI. Yes, it is a virtual sensor but on OneUI, it worked better. Now, it is worse. More often than not, it turns on the screen during the call. It would have been better if it simply didn't work.
- The viewport of default camera App in the AOSP displays picture in 4:3 but the camera hardware is giving out 16:9, so the viewport was squeezed. After installing GCam everything is good.
- Fingerprint Sensor simply doesn't work in-app like those in banking apps. It works on the lock screen but nowhere else.
- USB Audio Devices don't work. I have a USB-C to A OTG where I used to insert my headphones. On OneUI they used to work but here they don't. Storage devices work.
- 120 Hz felt smoother on OneUI.
Hello everyone
I managed to install LineageOS with working GApps and camera using this guide, so a big thanks to everyone who worked on flashing this phone
If anyone wants to install it, you need to:
Chose a bgN package (I installed this one : https://sourceforge.net/projects/an...UNOFFICIAL-arm64_bgN-vndklite.img.xz/download). It includes the GApps. You won't be able to install GApps after installing a vanilla (bvS / bvN) package. For some reasons, the /system partition is too small.
For unlocking camera and install magisk, just flash this kernel : https://forum.xda-developers.com/t/kernel-12-13-a528b-n-mesas-custom-kernel-r4.4490653/
I also installed magiskhide prop conf module, but I'm not sure it changed anything and the camera fix was probably already in the MCK. You can find it here anyway : https://forum.xda-developers.com/t/...safetynet-prop-edits-and-more-v6-1-2.3789228/

Categories

Resources