Database Info

[ROM][RJames] Stock Android 8.0.0 ROM for XT1921-1 Moto E5 Play

Moto E5 Play (RJames) Single SIM Retail
Android Version: 8.0.0 Oreo
Build No. OPP27.98
Kernel Version: 3.18.71-perf
Radio Version: M8917_03.04.05.38R
System Version: 27.1.50.rjames.retail.en.US
Security Patch Level: February 1, 2018
SPECIFICATIONS:
This is an unmodified stock Android Oreo ROM for the XT1921-1 retail variant of the Moto E5 Play. This ROM was structured from factory firmware and encompasses no modifications such as root, BusyBox, etc. Force encryption and dm-verity are fully intact. As such, so long as the /userdata partition is properly formatted, this ROM should install on an encrypted device. It is also noteworthy that this ROM appears to be compatible with some other variants of the Moto E5 Play. I can confirm full compatibility with the XT1921-5 variant. This ROM installer flashes only your /boot and /system partitions and does not install the radio firmware (baseband). See my Moto E5 firmware thread for the full firmware package for the XT1921-1. https://forum.xda-developers.com/moto-e5/how-to/firmware-moto-e5-xt1944-4-dual-sim-t3820901/page6
KERNEL SOURCE CODE:
Moto E5 Play (James, RJames)
MSM8920 Kernel Source Code: https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-OCP27.91-23
DISCLAIMER & WARNING:
By proceeding further, you are taking sole responsibility for the functionality and integrity of your device. Although I have fully tested this ROM on my own device, I will not be held liable or otherwise responsible in the event you brick your device or render your device otherwise inoperable. Follow the simple instructions and things should go smoothly.
REQUIREMENTS:
First and foremost, your device bootloader must be unlocked and TWRP custom recovery is required. If you have not yet performed these prerequisites, see @CodyF86's comprehensive guide on rooting and installing TWRP on the XT1921-5 variant. His tutorial is confirmed to work on the XT1921-1 as well. https://forum.xda-developers.com/mo...very-twrp-moto-e-5-play-james-t3796323/page25 Be sure you hit the Thanks button if you use CodyF86's tutorial.
INSTRUCTIONS:
• 1. Download the ROM zip from the below link and save it to your device's external storage (because the /userdata partition needs to be formatted for best results, it would be futile to save the ROM to internal storage);
• 2. Boot your device into TWRP recovery mode;
• 3. Select Wipe and choose System, Cache & Dalvik. Swipe the action bar to initiate the wipe. Now select Wipe again and choose the Format Data option in the lower right of the screen. Swipe to commence formatting;
• 4. Reboot Recovery (often necessary for proper mounting of /userdata after formatting);
• 5. Select Install and navigate to the location you saved the ROM zip, select the file and swipe the action bar to begin installation. The process takes just over a minute;
• 6. Reboot System. Finished...
If you want to root the stock ROM, simply flash Magisk v16.7 beta -- after Step 5 -- from the following link: https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589, and be sure and thank @topjohnwu if you use his Magisk Universal Systemless Interface.
Download Link: https://drive.google.com/file/d/1Ra-uOsMnaZBRc8g31bRH6W4Wtb9XPdoi/view?usp=drivesdk

MotoJunkie01 said:
Moto E5 Play (RJames) Single SIM Retail
Android Version: 8.0.0 Oreo
Build No. OPP27.98
Kernel Version: 3.18.71-perf
Radio Version: M8917_03.04.05.38R
System Version: 27.1.50.rjames.retail.en.US
Security Patch Level: February 1, 2018
SPECIFICATIONS:
This is an unmodified stock Android Oreo ROM for the XT1921-1 retail variant of the Moto E5 Play. This ROM was structured from factory firmware and encompasses no modifications such as root, BusyBox, etc. Force encryption and dm-verity are fully intact. As such, so long as the /userdata partition is properly formatted, this ROM should install on an encrypted device. It is also noteworthy that this ROM appears to be compatible with some other variants of the Moto E5 Play. I can confirm full compatibility with the XT1921-5 variant. This ROM installer flashes only your /boot and /system partitions and does not install the radio firmware (baseband). See my Moto E5 firmware thread for the full firmware package for the XT1921-1. https://forum.xda-developers.com/moto-e5/how-to/firmware-moto-e5-xt1944-4-dual-sim-t3820901/page6
DISCLAIMER & WARNING:
By proceeding further, you are taking sole responsibility for the functionality and integrity of your device. Although I have fully tested this ROM on my own device, I will not be held liable or otherwise responsible in the event you brick your device or render your device otherwise inoperable. Follow the simple instructions and things should go smoothly.
REQUIREMENTS:
First and foremost, your device bootloader must be unlocked and TWRP custom recovery is required. If you have not yet performed these prerequisites, see @CodyF86's comprehensive guide on rooting and installing TWRP on the XT1921-5 variant. His tutorial is confirmed to work on the XT1921-1 as well. https://forum.xda-developers.com/mo...very-twrp-moto-e-5-play-james-t3796323/page25 Be sure you hit the Thanks button if you use CodyF86's tutorial.
INSTRUCTIONS:
• 1. Download the ROM zip from the below link and save it to your device's external storage (because the /userdata partition needs to be formatted for best results, it would be futile to save the ROM to internal storage);
• 2. Boot your device into TWRP recovery mode.
• 3. Select Wipe and choose System, Cache & Dalvik. Swipe the action bar to initiate the wipe. Now select Wipe again and choose the Format Data option in the lower right of the screen. Swipe to commence formatting;
• 4. Reboot Recovery (often necessary for proper mounting of /userdata after formatting);
• 5. Select Install and navigate to the location you saved the ROM zip, select the file and swipe the action bar to begin installation. The process takes just over a minute;
• 6. Reboot System. Finished...
Download Link: https://drive.google.com/file/d/1Ra-uOsMnaZBRc8g31bRH6W4Wtb9XPdoi/view?usp=drivesdk
Click to expand...
Click to collapse
Glad to see this thread created!

Will there be a new build since the source code has been released?
MotoJunkie01 said:
Moto E5 Play (RJames) Single SIM Retail
Android Version: 8.0.0 Oreo
Build No. OPP27.98
Kernel Version: 3.18.71-perf
Radio Version: M8917_03.04.05.38R
System Version: 27.1.50.rjames.retail.en.US
Security Patch Level: February 1, 2018
SPECIFICATIONS:
This is an unmodified stock Android Oreo ROM for the XT1921-1 retail variant of the Moto E5 Play. This ROM was structured from factory firmware and encompasses no modifications such as root, BusyBox, etc. Force encryption and dm-verity are fully intact. As such, so long as the /userdata partition is properly formatted, this ROM should install on an encrypted device. It is also noteworthy that this ROM appears to be compatible with some other variants of the Moto E5 Play. I can confirm full compatibility with the XT1921-5 variant. This ROM installer flashes only your /boot and /system partitions and does not install the radio firmware (baseband). See my Moto E5 firmware thread for the full firmware package for the XT1921-1. https://forum.xda-developers.com/moto-e5/how-to/firmware-moto-e5-xt1944-4-dual-sim-t3820901/page6
KERNEL SOURCE CODE:
Moto E5 Play (James, RJames)
MSM8920 Kernel Source Code: https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-OCP27.91-23
DISCLAIMER & WARNING:
By proceeding further, you are taking sole responsibility for the functionality and integrity of your device. Although I have fully tested this ROM on my own device, I will not be held liable or otherwise responsible in the event you brick your device or render your device otherwise inoperable. Follow the simple instructions and things should go smoothly.
REQUIREMENTS:
First and foremost, your device bootloader must be unlocked and TWRP custom recovery is required. If you have not yet performed these prerequisites, see @CodyF86's comprehensive guide on rooting and installing TWRP on the XT1921-5 variant. His tutorial is confirmed to work on the XT1921-1 as well. https://forum.xda-developers.com/mo...very-twrp-moto-e-5-play-james-t3796323/page25 Be sure you hit the Thanks button if you use CodyF86's tutorial.
INSTRUCTIONS:
• 1. Download the ROM zip from the below link and save it to your device's external storage (because the /userdata partition needs to be formatted for best results, it would be futile to save the ROM to internal storage);
• 2. Boot your device into TWRP recovery mode;
• 3. Select Wipe and choose System, Cache & Dalvik. Swipe the action bar to initiate the wipe. Now select Wipe again and choose the Format Data option in the lower right of the screen. Swipe to commence formatting;
• 4. Reboot Recovery (often necessary for proper mounting of /userdata after formatting);
• 5. Select Install and navigate to the location you saved the ROM zip, select the file and swipe the action bar to begin installation. The process takes just over a minute;
• 6. Reboot System. Finished...
If you want to root the stock ROM, simply flash Magisk v16.7 beta -- after Step 5 -- from the following link: https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589, and be sure and thank @topjohnwu if you use his Magisk Universal Systemless Interface.
Download Link: https://drive.google.com/file/d/1Ra-uOsMnaZBRc8g31bRH6W4Wtb9XPdoi/view?usp=drivesdk
Click to expand...
Click to collapse

smeogle said:
Will there be a new build since the source code has been released?
Click to expand...
Click to collapse
I don't own this variant @smeogle, but, if you want to send me a system.img and boot.img (both unmodified preferably) from the latest build, I'll cook you up an updated ROM.

hey it says i need permission to download from your google drive. can you grant me access?

hello, I have sent you a request for permission to download the ROM. can you grant me access? Thanks.

MotoJunkie01 said:
Moto E5 Play (RJames) Single SIM Retail
Android Version: 8.0.0 Oreo
Build No. OPP27.98
Kernel Version: 3.18.71-perf
Radio Version: M8917_03.04.05.38R
System Version: 27.1.50.rjames.retail.en.US
Security Patch Level: February 1, 2018
SPECIFICATIONS:
This is an unmodified stock Android Oreo ROM for the XT1921-1 retail variant of the Moto E5 Play. This ROM was structured from factory firmware and encompasses no modifications such as root, BusyBox, etc. Force encryption and dm-verity are fully intact. As such, so long as the /userdata partition is properly formatted, this ROM should install on an encrypted device. It is also noteworthy that this ROM appears to be compatible with some other variants of the Moto E5 Play. I can confirm full compatibility with the XT1921-5 variant. This ROM installer flashes only your /boot and /system partitions and does not install the radio firmware (baseband). See my Moto E5 firmware thread for the full firmware package for the XT1921-1. https://forum.xda-developers.com/moto-e5/how-to/firmware-moto-e5-xt1944-4-dual-sim-t3820901/page6
KERNEL SOURCE CODE:
Moto E5 Play (James, RJames)
MSM8920 Kernel Source Code: https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-OCP27.91-23
DISCLAIMER & WARNING:
By proceeding further, you are taking sole responsibility for the functionality and integrity of your device. Although I have fully tested this ROM on my own device, I will not be held liable or otherwise responsible in the event you brick your device or render your device otherwise inoperable. Follow the simple instructions and things should go smoothly.
REQUIREMENTS:
First and foremost, your device bootloader must be unlocked and TWRP custom recovery is required. If you have not yet performed these prerequisites, see @CodyF86's comprehensive guide on rooting and installing TWRP on the XT1921-5 variant. His tutorial is confirmed to work on the XT1921-1 as well. https://forum.xda-developers.com/mo...very-twrp-moto-e-5-play-james-t3796323/page25 Be sure you hit the Thanks button if you use CodyF86's tutorial.
INSTRUCTIONS:
• 1. Download the ROM zip from the below link and save it to your device's external storage (because the /userdata partition needs to be formatted for best results, it would be futile to save the ROM to internal storage);
• 2. Boot your device into TWRP recovery mode;
• 3. Select Wipe and choose System, Cache & Dalvik. Swipe the action bar to initiate the wipe. Now select Wipe again and choose the Format Data option in the lower right of the screen. Swipe to commence formatting;
• 4. Reboot Recovery (often necessary for proper mounting of /userdata after formatting);
• 5. Select Install and navigate to the location you saved the ROM zip, select the file and swipe the action bar to begin installation. The process takes just over a minute;
• 6. Reboot System. Finished...
If you want to root the stock ROM, simply flash Magisk v16.7 beta -- after Step 5 -- from the following link: https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589, and be sure and thank @topjohnwu if you use his Magisk Universal Systemless Interface.
Download Link: https://drive.google.com/file/d/1Ra-uOsMnaZBRc8g31bRH6W4Wtb9XPdoi/view?usp=drivesdk
Click to expand...
Click to collapse
can i have access to this link please...i installed xposed thru magisk and now my baseband and imei are unknown... i can get it back to stock but if i flash anything it boot loops and if i get it to load i have no phone service...4g..lte.. data..etc......

MotoJunkie01 said:
Moto E5 Play (RJames) Single SIM Retail
Android Version: 8.0.0 Oreo
Build No. OPP27.98
Kernel Version: 3.18.71-perf
Radio Version: M8917_03.04.05.38R
System Version: 27.1.50.rjames.retail.en.US
Security Patch Level: February 1, 2018
SPECIFICATIONS:
This is an unmodified stock Android Oreo ROM for the XT1921-1 retail variant of the Moto E5 Play. This ROM was structured from factory firmware and encompasses no modifications such as root, BusyBox, etc. Force encryption and dm-verity are fully intact. As such, so long as the /userdata partition is properly formatted, this ROM should install on an encrypted device. It is also noteworthy that this ROM appears to be compatible with some other variants of the Moto E5 Play. I can confirm full compatibility with the XT1921-5 variant. This ROM installer flashes only your /boot and /system partitions and does not install the radio firmware (baseband). See my Moto E5 firmware thread for the full firmware package for the XT1921-1. https://forum.xda-developers.com/moto-e5/how-to/firmware-moto-e5-xt1944-4-dual-sim-t3820901/page6
KERNEL SOURCE CODE:
Moto E5 Play (James, RJames)
MSM8920 Kernel Source Code: https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-OCP27.91-23
DISCLAIMER & WARNING:
By proceeding further, you are taking sole responsibility for the functionality and integrity of your device. Although I have fully tested this ROM on my own device, I will not be held liable or otherwise responsible in the event you brick your device or render your device otherwise inoperable. Follow the simple instructions and things should go smoothly.
REQUIREMENTS:
First and foremost, your device bootloader must be unlocked and TWRP custom recovery is required. If you have not yet performed these prerequisites, see @CodyF86's comprehensive guide on rooting and installing TWRP on the XT1921-5 variant. His tutorial is confirmed to work on the XT1921-1 as well. https://forum.xda-developers.com/mo...very-twrp-moto-e-5-play-james-t3796323/page25 Be sure you hit the Thanks button if you use CodyF86's tutorial.
INSTRUCTIONS:
• 1. Download the ROM zip from the below link and save it to your device's external storage (because the /userdata partition needs to be formatted for best results, it would be futile to save the ROM to internal storage);
• 2. Boot your device into TWRP recovery mode;
• 3. Select Wipe and choose System, Cache & Dalvik. Swipe the action bar to initiate the wipe. Now select Wipe again and choose the Format Data option in the lower right of the screen. Swipe to commence formatting;
• 4. Reboot Recovery (often necessary for proper mounting of /userdata after formatting);
• 5. Select Install and navigate to the location you saved the ROM zip, select the file and swipe the action bar to begin installation. The process takes just over a minute;
• 6. Reboot System. Finished...
If you want to root the stock ROM, simply flash Magisk v16.7 beta -- after Step 5 -- from the following link: https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589, and be sure and thank @topjohnwu if you use his Magisk Universal Systemless Interface.
Download Link: https://drive.google.com/file/d/1Ra-uOsMnaZBRc8g31bRH6W4Wtb9XPdoi/view?usp=drivesdk
Click to expand...
Click to collapse
just requested permision to download the link. thankyou.

[ROM][A530W/A530F/A730F] SaboorROM

[A530x][A730F]
SaboorROM
PLEASE READ ALL THIS BEFORE DOING ANYTHING
________________________________________________
NOTICE:
I am not responsible for any happy endings, a nuclear war with your device, your alarm clock electrically shocking you, or your device literally freezing, so dont blame me for my mistakes or yours, or else i will laugh at you
Please backup your device (System, Data, EFS, and Cache, Especially EFS) because you might regret flashing this
________________________________________________
CREDITS:
@prashantp01 for Quantum Kernel
SuperR kitchen to build rom
________________________________________________
FEATURES:
Canada A530WVLU4CSCA base
Debloated
Deknoxed
Rooted
S10 Sounds and ringtones
Screen Recording (check section 2 on post #3 for more details)
build.prop tweaks
Status bar size options (check section 1 on post #3 for more details)
G975F/G975W ODM
ODM mods that add mobile data quick settings tiles etc
Applock
Call recording
Mobile data toggle in power menu
________________________________________________
BUGS:
Freezes on bootanimation and when playing video (sometimes) (i dont think there is with 4/23 build, someone test and tell me ASAP)
Digital wellbeing not showing stats (check section 3 on post #3 for workaround) (DIGITAL WELLBEING NOT AVAILABLE ON 4/23 BUILD I WILL ADD IT ON FUTURE BUILDS LOL I JUST FORGOT ABOUT DIGITAL WELLBEING)
Everything else works
________________________________________________
INSTRUCTIONS:
1. Download the ROM zip, and zip #2 for your model under this section
2. Boot into TWRP
3. Wipe system, cache, and data
4. Flash ROM zip
5. Flash zip #2
6. Boot and setup
7. done! (PLEASE READ THE BUGS BEFORE YOU GO TO THE COMMENTS AND SAY "sar why my phone freeze so much ur rom is stupid")
________________________________________________
DOWNLOAD
DOWNLOAD ROM AND ZIP #2
DOWNLOAD UNTESTED NEWER 4/23 BUILD AND ZIP #2
________________________________________________
How to update from existing version of rom
1. Dont forget to download the zip #2 update too, that zip updates too!
2. Flash ROM zip
3. Flash zip #2
4. Wipe cache/dalvik
5. Wait for device to finish optimizing and updating before reporting any bugs
________________________________________________​
XDA:DevDB Information
SaboorROM, ROM for the Samsung Galaxy A8+ (2018)
Contributors
587.saboor
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Current Stable Version: 420-11:11AM
Stable Release Date: 2019-04-20
Current Beta Version: 4-23-6:50PM
Beta Release Date: 2019-04-23
Created 2019-04-13
Last Updated 2019-04-23

/////////////////////////////////////////////////////////////////
Click here to join us in the one and only A8/A8+ Telegram group
/////////////////////////////////////////////////////////////////​

_____________________________________________
STATUS BAR SIZE
If you see the screenshot below, you'll see the status bar is a bit big (pls don't mind the blank settings page lol)
https://photos.app.goo.gl/wiYKVbJed52t9SiN6
DON'T PANIC BIG STATUS BAR HATERS! THIS IS ONLY OPTIONAL AND THIS EVEN HAS OPTION FOR SMALLER STATUS BAR
How do you get it, you ask?
just follow these steps after installing the rom
1. go to settings
2. developer options (u already know how to turn dev options on)
3. scroll down to "Simulate display with a cutout" and tap it
4. select a size of status bar (this wont add any notch on your phone, this only makes the status bar a bit bigger like on the screenshot)
5. done!
_____________________________________________
SCREEN RECORDER
You can record your screen with sound too
How do you get it, you ask?
just add it to the quick settings menu
_____________________________________________
DIGITAL WELLBEING FIX
Digital wellbeing doesn't show stats but you can make it show
How?
just follow these steps:
1. go to settings
2. search "Special Access"
3. press Special Access
4. scroll down to Usage data access and press it
5. press the 3 dot menu on the top right
6. press Show system apps
7. press Digital wellbeing and enable allow usage tracking
8. done!
_____________________________________________
SCREENSHOTS
https://photos.app.goo.gl/4USaY78w3cm8DG5p9
_____________________________________________​

yeet

587.saboor said:
yeet
Click to expand...
Click to collapse
Why do you think Samsung released a updated that has bugs?

mchlbenner said:
Why do you think Samsung released a updated that has bugs?
Click to expand...
Click to collapse
idk cuz they're high? ????

A8 2018 - SM-A530F
Upgrade from Nougat (Android 7.x):
-installed newest TWRP via TWRP
-backed up the old Nougat via TWRP
-wiped and installed DOWNLOAD ROM AND ZIP #2 (non-beta) via TWRP
-reboot
-it took about 15 minutes and several reboots --> be patient
-message "KERNEL IS NOT SEANDROID ENFORCING" at every boot now (top left of screen, small red font)
Root problem:
if you grant apps root, magisk manager is constantly crashing (if an app uses root) (e.g Titanium Backup, Total Commander)
-reduce to core functions in magisk manager did not help
-upgrading magisk manager to 7.1.1 did not help
-downgrading magisk to 18.1 helped (I removed magisk 19.0 with Magisk-uninstaller-20190328.zip in TWRP first)
EdXposed is working (I had to flash it _twice_ via TWRP)
-flash magisk-riru-core-v18.zip
-flash magisk-EdXposed-v0.3.1.7_beta-release.zip
-install EdXposedInstaller_v2.2.4-release.apk
Important apps that work: AFWall+ 2.99, XPrivacyLua 1.24, Titanium Backup, FM-radio
Looks like, I can't go back to Nougat (just want to do this because I missed to save settings in XPrivacy and wifi passwords before the upgrade).
Downgrading to Nougat (Restore in TWRP) didn't work:
-backed up the new Pie and wiped data, system, cache
-restoring Nougat went well but gave one error at the end:
-Failed to mount '/system' (Invalid argument)
-I got bootloops.
So I restored Pie in TWRP:
-wiped data, system, cache
-wiping went well but gave one error at the end:
Failed to mount '/system' (Invalid argument)
-restore went well, no bootloops

phocriab said:
A8 2018 - SM-A530F
Upgrade from Nougat (Android 7.x):
-installed newest TWRP via TWRP
-backed up the old Nougat via TWRP
-wiped and installed DOWNLOAD ROM AND ZIP #2 (non-beta) via TWRP
-reboot
-it took about 15 minutes and several reboots --> be patient
-message "KERNEL IS NOT SEANDROID ENFORCING" at every boot now (top left of screen, small red font)
Root problem:
if you grant apps root, magisk manager is constantly crashing (if an app uses root) (e.g Titanium Backup, Total Commander)
-reduce to core functions in magisk manager did not help
-upgrading magisk manager to 7.1.1 did not help
-downgrading magisk to 18.1 helped (I removed magisk 19.0 with Magisk-uninstaller-20190328.zip in TWRP first)
EdXposed is working (I had to flash it _twice_ via TWRP)
-flash magisk-riru-core-v18.zip
-flash magisk-EdXposed-v0.3.1.7_beta-release.zip
-install EdXposedInstaller_v2.2.4-release.apk
Important apps that work: AFWall+ 2.99, XPrivacyLua 1.24, Titanium Backup, FM-radio
Looks like, I can't go back to Nougat (just want to do this because I missed to save settings in XPrivacy and wifi passwords before the upgrade).
Downgrading to Nougat (Restore in TWRP) didn't work:
-backed up the new Pie and wiped data, system, cache
-restoring Nougat went well but gave one error at the end:
-Failed to mount '/system' (Invalid argument)
-I got bootloops.
So I restored Pie in TWRP:
-wiped data, system, cache
-wiping went well but gave one error at the end:
Failed to mount '/system' (Invalid argument)
-restore went well, no bootloops
Click to expand...
Click to collapse
lol
first of all, why are you downloading this rom from nougat? it's gonna obviously cause problems if you're coming from nougat so i recommend going to pie first from odin, then flash this rom, or oreo if you really dont want pie.
second of all, you shouldnt use xposed with samsung firmware, or else you would encounter issues but it's fine if you want to use stuff like greenify or something
third of all, the KERNEL IS NOT SEANDROID ENFORCING is normal but shouldn't show up anyways, it's showing up because you have old nougat bootloader so thats another reason to flash official pie from odin before flashing this rom

587.saboor said:
first of all, why are you downloading this rom from nougat? it's gonna obviously cause problems if you're coming from nougat so i recommend going to pie first from odin, then flash this rom, or oreo if you really dont want pie.
Click to expand...
Click to collapse
that's the lazy man's approach, just give it a try
587.saboor said:
second of all, you shouldnt use xposed with samsung firmware, or else you would encounter issues but it's fine if you want to use stuff like greenify or something
Click to expand...
Click to collapse
okay, i switchted from XPrivacyLua to AppOps
587.saboor said:
third of all, the KERNEL IS NOT SEANDROID ENFORCING is normal but shouldn't show up anyways, it's showing up because you have old nougat bootloader so thats another reason to flash official pie from odin before flashing this rom
Click to expand...
Click to collapse
imho it is not obvious: you can still boot windows 10 with a windows 7 bootloader, same for linux
probably you should add that hint to you first post

phocriab said:
imho it is not obvious: you can still boot windows 10 with a windows 7 bootloader, same for linux
probably you should add that hint to you first post
Click to expand...
Click to collapse
nah i dont really need to add the hint cuz ur literally the only one here who's flashing on nougat bootloader lol

587.saboor said:
nah i dont really need to add the hint cuz ur literally the only one here who's flashing on nougat bootloader lol
Click to expand...
Click to collapse
I recently upgraded to the latest bootloader to see if it would help pie boot better.
Which it did not these roms issues freezing on boot up and video freezing is Samsung fault.
I have contacted them and I ask why they would released a buggy update their been giving me excuses instead of answers.
Back to Oreo for a couple months until I sell this phone no more Samsung!

mchlbenner said:
I recently upgraded to the latest bootloader to see if it would help pie boot better.
Which it did not these roms issues freezing on boot up and video freezing is Samsung fault.
I have contacted them and I ask why they would released a buggy update their been giving me excuses instead of answers.
Back to Oreo for a couple months until I sell this phone no more Samsung!
Click to expand...
Click to collapse
ye its complete bs that they give excuses and s*** like that smh

new 4/20 build is out
Changelog:
Call recording
Mobile data toggle in power menu

My phone broke, so development will be temporarily suspended till I get a replacement.
For now, as an "update" flash quantum kernel v2 and then magisk after flashing the latest version
For now, I'll see y'all later when I get a new replacement a8

Pls donate to me
paypal.me/youhavebeenyoted
This is just so I can fully pay for my replacement A8 which is $229 or make it more affordable for me
I'd be very thankful if you donate

lol i did say development was suspended till i get a replacement a8 but i just dont know what to do in my free time other than this
anyways new build 4/23 blah blah blah heres the changelog:
separated zip 2 for people with limited internet data i guess
updated base to a530w base
someone pls try this build and tell me if there are any freezes or not ASAP thanks
enjoy

587.saboor said:
lol i did say development was suspended till i get a replacement a8 but i just dont know what to do in my free time other than this
anyways new build 4/23 blah blah blah heres the changelog:
separated zip 2 for people with limited internet data i guess
updated base to a530w base
someone pls try this build and tell me if there are any freezes or not ASAP thanks
enjoy
Click to expand...
Click to collapse
What are the two zips

mchlbenner said:
What are the two zips
Click to expand...
Click to collapse
What two zips?
Theres 2 zips to flash for the rom
First one is the rom zip
Then the zip 2, ignore the ones that arent your model number

587.saboor said:
What two zips?
Theres 2 zips to flash for the rom
First one is the rom zip
Then the zip 2, ignore the ones that arent your model number
Click to expand...
Click to collapse
I have discovered that on the latest pie you have use custom kernel or you will get locked but reflashed stock then I was able to flash twrp.

mchlbenner said:
I have discovered that on the latest pie you have use custom kernel or you will get locked but reflashed stock then I was able to flash twrp.
Click to expand...
Click to collapse
Lol the zip 2 contains the custom kernel

[UNOFFICIAL][ENCRYPTION][wrappedkey] TWRP 3.3.1-6: proper system_as_root & decryption

[UNOFFICIAL][ENCRYPTION][wrappedkey] TWRP 3.3.1-6: proper system_as_root & decryption
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
Introduction
This is an unofficial build of TWRP for Redmi Note 7 Pro (violet). Differences with the official one include:
- Supports CAF-based wrappedkey encryption (decryption) properly (tested with MIUI 10.3.5.0)
- Supports decrypting devices that have screen lock set up after Android 9 May update, which introduced a new key derivation function.
- Mounts the system partition at /system_root as per AOSP standards. This makes the auto-backup scripts (e.g. GApps / Magisk survival script) work properly during updates, and you no longer need any 'patch' to flash GApps / Magisk properly. However, this may break some existing ROMs. See below FAQ section for details.
- Appended DTBO to the recovery image so it doesn't depend on the dtbo partition. No standalone DTBO image required.
Flashing instructions
- Download and extract the img file
- Reboot to fastboot mode
- fastboot flash recovery whatever_img_file_you_extracted.img
- Reboot and press Volume + to enter recovery
- DO NOT try to run 'fastboot boot recovery.img', it won't work.
- DO NOT flash the fcrypt disabler if you use my recovery. There is no need to do so, and it is possible to mess stuff up if you don't know what you are doing.
- You have to format the data partition if and ONLY IF:
1) You were not encrypted, now going to an encrypted state, or vice-versa OR
2) You were on a ROM other than MIUI that does not support "wrappedkey" (ROMs would often state it supports wrappedkey if it does), now going to a ROM that supports it
Limitations
DO NOT boot this recovery with empty system and vendor partitions. It will fail to decrypt any data partition with empty /system and /vendor. DO NOT wipe system and vendor partitions without installing a new one before rebooting. I am working to remove this limitation.
Now works even with empty system and vendor partitions after 3.3.1-5. No need to worry about formatting system and vendor breaking TWRP any more.
The restore zip created by the Migrate app is NOT compatible with this recovery. It's a problem of the Migrate app, not this recovery. Please DO NOT try to flash the restore zip created by Migrate.
FAQ
- Q: Do I need any specific DTBO image to make this recovery working?
- A: Nope. It is appended to the recovery image so it will work with any DTBO.
- Q: What is wrappedkey?
- A: It's a different mode of FBE implemented in CAF, the Qualcomm branch of AOSP.
- Q: This cannot install ROM X, why?
- A: Because it mounts the system partition at /system_root, which is AOSP standard behavior for A-only system_as_root devices, but is broken in some custom ROMs currently (MIUI should work though). To make any ROM work again, they will need to include this commit from LineageOS Gerrit https://review.lineageos.org/c/LineageOS/android_build/+/247066
- Q: Decryption doesn't work with ROM X, why?
- A: Decryption should work for most ROMs based on the CAF branch (not AOSP). CAF ROMs (including official MIUI) use a different scheme for key storage, which is why TWRP hasn't supported it till now. I have ported the CAF encryption changes (wrappedkey) to TWRP, but unfortunately this will break ROMs that do not support the CAF wrappedkey mode of encryption. Here is a list of patches non-CAF ROMs need to support CAF-encrypted /data partitions https://mokeedev.review/q/topic:%22fbe-wrapped-key%22+(statuspen%20OR%20status:merged). If you confirm your ROM is CAF-based but the decryption still does not work, please open an issue on my GitHub repository which you could find below. (XDA threads are no good for issue tracking, sorry)
- Q: Why not contribute to the official TWRP?
- A: All the patches to the TWRP code base have been submitted to the official gerrit code review, though not merged yet, which you can see below.
Downloads
3.3.1-6: https://mega.nz/#!3QIRQYhK!Jq5QrGfJw5VCYZ8sq_BO1qNZecrFqlM9IB1IdSwogvI
changes: updated kernel to support pstore instead of /proc/last_kmsg. If you don't know what this is, it's probably not relevant to you.
Here you can find an unofficial LOS build with wrappedkey encryption and also proper system_as_root support for those survival scripts https://forum.xda-developers.com/redmi-note-7-pro/development/unofficial-lineageos-16-caf-encryption-t3933532. In addition, all official MIUI builds should flash just fine.
History versions:
3.3.1-5: https://mega.nz/#!nMowHKiL!zRvoTM0iIZKArmUDnZzaEFtXQv0_q7hIHUCmTHTOmOM
changes: 1) Now works even with empty /system and /vendor partition 2) Fixed brightness problem; 3) Enabled EDL Reboot
3.3.1-3: https://mega.nz/#!yAYXxAzZ!FNMYLzLphnSmJ-DbBx-OZUgxxYiftgn8e4Jn3kxiQik
Patches and sources
Patches for TWRP are available here:
https://gerrit.omnirom.org/#/c/34091/
https://gerrit.omnirom.org/#/c/34093/
https://gerrit.omnirom.org/#/c/34092/
https://gerrit.omnirom.org/#/c/android_bootable_recovery/+/34096/
Patches for ROMs to support wrapped key have been given in the above sections.
Source of the current device tree for TWRP: https://github.com/PeterCxy/android_device_xiaomi_violet-twrp
Kernel source: https://github.com/PeterCxy/android_kernel_xiaomi_sm6150, note that the device tree uses a prebuilt kernel image.
Contributors
PeterCxy, Dyneteve, merothh
Source Code: https://github.com/PeterCxy/android_device_xiaomi_violet-twrp

Now fixed and tested with MIUI.

PeterCxy said:
Now fixed and tested with MIUI.
Click to expand...
Click to collapse
Could you please tell us what is fixed and what is wrong with the previous one? Just out of curiosity.

I’m not new to installing custom recoveries and installing ROM, but I am new to Xiaomi devices.
In the simplest form possible,
With this I should be able to just run the ‘fastboot install recovery twrp.img’ and not have to run “fastboot erase userdata’?
also
Do I still need to flash the zip I have that disables forced encryption?

Could you provide instructions to flash this ?
Or is it just the same as the 'official one'?

Can confirm this successfully decrypts storage, running xiaomi.eu on my phone. Thanks for your work.

Dwughjsd said:
Could you please tell us what is fixed and what is wrong with the previous one? Just out of curiosity.
Click to expand...
Click to collapse
It did not decrypt MIUI 10.3.5.0 successfully due to magic (I missed some commits from qcom). It was fixed by pulling more commits in.

Jpwner said:
I’m not new to installing custom recoveries and installing ROM, but I am new to Xiaomi devices.
In the simplest form possible,
With this I should be able to just run the ‘fastboot install recovery twrp.img’ and not have to run “fastboot erase userdata’?
also
Do I still need to flash the zip I have that disables forced encryption?
Click to expand...
Click to collapse
You won't need to erase userdata or flash fcrypt disabler anymore, if all the ROMs will update to support the wrappedkey encryption

Naveenthemi said:
Could you provide instructions to flash this ?
Or is it just the same as the 'official one'?
Click to expand...
Click to collapse
just fastboot flash recovery whatever_you_downloaded_and_extracted.img

PeterCxy said:
just fastboot flash recovery whatever_you_downloaded_and_extracted.img
Click to expand...
Click to collapse
So it's possible for me to flash OTA Updates without encountering a bootloop and such?

Can someone please provide an alternate download link? The Mega link doesn't seem to work for me.
EDIT: Worked on a different device. Thanks.

Naveenthemi said:
So it's possible for me to flash OTA Updates without encountering a bootloop and such?
Click to expand...
Click to collapse
+1
Please answer

Good job! ?
I want you to know that your patch has been merged with the official one. I was away for a while so I hope you understand the little unfortunate delay.

In latest update can we flash any custom roms without any issue?

Yogendra Kher said:
In latest update can we flash any custom roms without any issue?
Click to expand...
Click to collapse
You have to wait until custom ROMs pull in necessary system_as_root changes. Currently it seems only my LOS build pulled that in

PeterCxy said:
You have to wait until custom ROMs pull in necessary system_as_root changes. Currently it seems only my LOS build pulled that in
Click to expand...
Click to collapse
Is it possible to flash OTA updates without encountering bootloops and such? (MIUI)

Naveenthemi said:
Is it possible to flash OTA updates without encountering bootloops and such? (MIUI)
Click to expand...
Click to collapse
Should work fine with MIUI. At least from what I have tested.

kushal.purkar said:
+1
Please answer
Click to expand...
Click to collapse
PeterCxy said it would as far as his testing had been done.

Gapps aroma not installing in this one as well. error 255

Can I flash Magisk and root my phone with this build.?
Do you have any Magisk zip file that will work.?
Thank you for your work

[UNOFFICIAL][wrappedkey] LineageOS 16 with CAF encryption support

Introduction
This is an unofficial build of LineageOS 16 for Redmi Note 7 Pro. Differences from the one provided by Dyneteve include:
- Ported the CAF wrappedkey encryption stuff, which is what MIUI uses, over using patches from https://mokeedev.review/q/topic:%22fbe-wrapped-key%22+(statuspen%20OR%20status:merged), This requires an recovery with wrappedkey decryption support, e.g. this one
- Applied unmerged patch https://review.lineageos.org/c/LineageOS/android_build/+/247066 to mount system as /system_root properly on install. This makes addon.d scripts (e.g. Magisk / GApps survival script) work again on our device. This requires an recovery with proper system_as_root support, e.g. this one
- ROM includes its own vendor image instead of relying on one provided by MIUI. I intend to try to build as much of vendor image as possible from CAF source in the future.
Flash instructions
- Make sure you have the latest firmware images. If not, update them before flashing.
- Flash a TWRP recovery that supports mounting system as /system_root and supports wrappedkey encryption (the one provided above)
- Wipe data partition (without wiping /data/media). If you came from another non-CAF ROM (ROM that do not support wrappedkey mode) and had encryption enabled, you will need to format your data partition (including /data/media).
Note: If you decide to format your data partition, always format with 'advanced wipe' in TWRP recovery. DO NOT use fastboot -w or fastboot erase, even if you do, please format again in recovery, otherwise the system might not work.
- Install the zip in TWRP.
- Install whatever you want e.g. Magisk, OpenGapps
- DO NOT install the fcrypt disabler.
- Reboot and enjoy
Known issues
DO NOT remove screen lock passwords if you set one. You can change the password just fine, but DO NOT REMOVE IT. YOU WILL LOSE ACCESS TO ALL DATA IF YOU DO THIS AND REBOOT.
Removing screen lock passwords work after 20190528-1.
Downloads
20190609-1: https://mega.nz/#!PdRnxIia!Boh-a8e5JHt8YEBwbXKt8rWYj3PC56mdpEIXwDEY2ng
changelog: 1) Merged upstream LineageOS (June security patch) 2) Updated kernel to 4.14.123 3) Updated MIUI binary blobs 4) Some clean-up
NOTE: /proc/last_kmsg support is removed due to incompatibility. This feature is replaced by pstore, which you could find more information on through some Google-fu.
History versions:
20190528-1: https://mega.nz/#!nZRTQCbS!qf-RdT-ijayg8UBxyyz3Hoi2O_8ZtpWewgNv-eVDcqA
changelog: 1) merged upstream LineageOS; 2) fixed the bug of removing screen lock passwords, now it won't swallow all your data (this commit: https://github.com/PeterCxy/android...mmit/d2fe3434cddb98eeb414906e71a817559ade1b26; 3) merged LTS kernel 4.14.122, thanks to YaroST and aviraxp; 4) fixed potential charging problem; 5) some other kernel improvements
20190526-1: https://mega.nz/#!rRgwmY5T!2fQyDjukLoGmk7KRtas5n2Y_it9QS_s2noAItzNvFfY
Sources
Device: https://github.com/PeterCxy/android_device_xiaomi_violet
Kernel: https://github.com/PeterCxy/android_kernel_xiaomi_sm6150
Other changes and patches: see what is available on my GitHub https://github.com/PeterCxy/, everything is open-source for this ROM.
Contributors
PeterCxy, GuaiYiHu, aviraxp
Source Code: https://github.com/PeterCxy/android_device_xiaomi_violet

Thanks ?

Thank you for the ROM!

There's a Typo in the ROM os version description.

cant boot. installed as mentioned in instruction. its automatically rebooting to recovery (twrp, the given one). now whenever i try to flash other rrecovery its not booting into. stuck. please help.

jyoti.id said:
cant boot. installed as mentioned in instruction. its automatically rebooting to recovery (twrp, the given one). now whenever i try to flash other rrecovery its not booting into. stuck. please help.
Click to expand...
Click to collapse
If you can't boot to recovery at all you may need to flash a fastboot ROM of MIUI (of course in fastboot mode) and try to install twrp again.

jyoti.id said:
cant boot. installed as mentioned in instruction. its automatically rebooting to recovery (twrp, the given one). now whenever i try to flash other rrecovery its not booting into. stuck. please help.
Click to expand...
Click to collapse
Sorry I have no idea here.. What ROM you were on before flashing this?

Dwughjsd said:
If you can't boot to recovery at all you may need to flash a fastboot ROM of MIUI (of course in fastboot mode) and try to install twrp again.
Click to expand...
Click to collapse
iv flashed the stock rom, but now the internal storage is showing only 16GB of storage.
Edit: fixed everything. Thank you. I was curious about the battery backup of this ROM badly, so I just rushed in things so maybe I made some mistakes.

jyoti.id said:
iv flashed the stock rom, but now the internal storage is showing only 16GB of storage.
Edit: fixed everything. Thank you. I was curious about the battery backup of this ROM badly, so I just rushed in things so maybe I made some mistakes.
Click to expand...
Click to collapse
Just keep in mind that safety first

Download link not working
Edit: UC browser was the culprit

dwughjsd said:
just keep in mind that safety first
Click to expand...
Click to collapse
how u fixed storage issue

gsunil said:
how u fixed storage issue
Click to expand...
Click to collapse
It was @jyoti.id that faced and solved the issue, so let's call him for an answer

rom keeps rebooting into twrp , i did every step

gsunil said:
how u fixed storage issue
Click to expand...
Click to collapse
I just flashed the whole fastboot rom again & it fixed everything.
---------- Post added at 04:34 AM ---------- Previous post was at 04:33 AM ----------
King_Dinoco10 said:
rom keeps rebooting into twrp , i did every step
Click to expand...
Click to collapse
Same thing happened with me too

Device not charging above 86%. Anyone else facing this bug ?

PeterCxy said:
Sorry I have no idea here.. What ROM you were on before flashing this?
Click to expand...
Click to collapse
The phone does not charge more than 91%!

lapo_chel said:
The phone does not charge more than 91%!
Click to expand...
Click to collapse
now should be fixed, try today's new build

PeterCxy said:
now should be fixed, try today's new build
Click to expand...
Click to collapse
Safetynet does not pass.

lapo_chel said:
Safetynet does not pass.
Click to expand...
Click to collapse
It's because I used vendor files from MIUI beta. You can bypass it with a magisk module to reset the build fingerprint

Many thanks for your build! I like it much.
IMHO, SELinux should be enabled.

[WIP][EXYNOS][ROM][UNOFFICIAL][12]LineageOS 19.1 for Galaxy S20 FE

LineageOS is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
Unlock bootloader
Boot into download mode
Flash recovery using heimdall or odin
Boot into recovery right as it finishes flashing
Flash ROM using adb sideload path_to_ROM.zip command
Optionally flash GAPPS the same way you flashed ROM
Format data in recovery
Reboot to system.
Downloads:
RECOVERY
ROM
GAPPS
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
DO NOT Report bugs if you're using TWRP
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Support
Telegram group
Credits
Doomer231
A2L5E0X1
DeHuMaNiZeD
Linux4
Device tree and kernel source code:
R8S-OSS

Issues:
voLTE[wont fix, unless any samsung gets voLTE fixed]
fingerprint scanner might not work
overlays might need some tweaking
no encryption
permissive SELinux

Steps I followed from @Gully.Moy that worked perfectly:
Unlocked bootloader as per guides no problem
Downloaded latest stock firmware from Frija and extract
Copy the AP_xxxxxxxxxxx.tar.md5 file to phone storage
Copy Magisk manager on your phone https://github.com/topjohnwu/Magisk/releases/tag/v25.2
Open Magisk manager, select 'install' next to Magisk, select the .tar.md5 file and patch it
Copy newly created magisk.tar file from phone download folder to computer
Flash via Odin 3.13.3 with standard BL CP and CSC from Frija download, but the magisk .tar file in AP slot.
Boot into android and reenable USB debugging (not sure if necessary).
(Recovery mode combination is volume up + side button with USB plugged in)
I am now in the first boot of the ROM that I copied to the internal storage and flashed with TWRP (as my device is not recogised in fastboot and doesn´t let me sideload via adb it closes) but seems to be in an endless startup loop and it failed to install the gapps also when I tried to, the provided recovery cannot be flashed with Odin @Doomvrr thank you.

BraskOviedo said:
Steps I followed from @Gully.Moy that worked perfectly:
Unlocked bootloader as per guides no problem
Downloaded latest stock firmware from Frija and extract
Copy the AP_xxxxxxxxxxx.tar.md5 file to phone storage
Copy Magisk manager on your phone https://github.com/topjohnwu/Magisk/releases/tag/v25.2
Open Magisk manager, select 'install' next to Magisk, select the .tar.md5 file and patch it
Copy newly created magisk.tar file from phone download folder to computer
Flash via Odin 3.13.3 with standard BL CP and CSC from Frija download, but the magisk .tar file in AP slot.
Boot into android and reenable USB debugging (not sure if necessary).
(Recovery mode combination is volume up + side button with USB plugged in)
I am now in the first boot of the ROM that I copied to the internal storage and flashed with TWRP (as my device is not recogised in fastboot and doesn´t let me sideload via adb it closes) but seems to be in an endless startup loop and it failed to install the gapps also when I tried to, the provided recovery cannot be flashed with Odin @Doomvrr thank you.
Click to expand...
Click to collapse
I need to update the ROM to boot on latest firmware, because samsung updated bootloader. So for now it won't boot unless you're on august firmware, don't try to downgrade firmware. Just wait.

Doomvrr said:
I need to update the ROM to boot on latest firmware, because samsung updated bootloader. So for now it won't boot unless you're on august firmware, don't try to downgrade firmware. Just wait.
Click to expand...
Click to collapse
Thank you for the ROM and the quick answer, if I can help out with something please let me know, thank you.

Doomvrr said:
I need to update the ROM to boot on latest firmware, because samsung updated bootloader. So for now it won't boot unless you're on august firmware, don't try to downgrade firmware. Just wait.
Click to expand...
Click to collapse
Forgot to ask, is there an ETA? Is it LineageOS 20? Thank you

Doomvrr said:
I need to update the ROM to boot on latest firmware, because samsung updated bootloader. So for now it won't boot unless you're on august firmware, don't try to downgrade firmware. Just wait.
Click to expand...
Click to collapse
It´s the October 2022 patch

Doomvrr said:
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
DO NOT Report bugs if you're using TWRP
Click to expand...
Click to collapse
What is the context of the above statments, I ask because -
One of the primary reason for running a custom ROM is for rooting, and the primary reason for rooting for a LOT of users is the ability to run Magisk and EdXposed/Riru.
This one is exspecially confusing, the vast majority of users flash custom ROMs with TWRP. Does the recovery that needs to be flashed with this ROM as comprehensive as TWRP..?

b1k3rdude said:
What is the context of the above statments, I ask because -
One of the primary reason for running a custom ROM is for rooting, and the primary reason for rooting for a LOT of users is the ability to run Magisk and EdXposed/Riru.
This one is exspecially confusing, the vast majority of users flash custom ROMs with TWRP. Does the recovery that needs to be flashed with this ROM as comprehensive as TWRP..?
Click to expand...
Click to collapse
Agreed.

b1k3rdude said:
What is the context of the above statments, I ask because -
One of the primary reason for running a custom ROM is for rooting, and the primary reason for rooting for a LOT of users is the ability to run Magisk and EdXposed/Riru.
This one is exspecially confusing, the vast majority of users flash custom ROMs with TWRP. Does the recovery that needs to be flashed with this ROM as comprehensive as TWRP..?
Click to expand...
Click to collapse
Xposed modules may cause stability issues on the system due to their nature. Debugging the issue becomes a hard task because there can be a ton of reasons as to why it happens, and you'll be most certainly reaching out to the ROM maintainer to help you fix something not even related to his work.
I can't say for sure but I guess it's because TWRP has had some problems to keep up with the changes made to Android on recent years due to the maintainers' private life and the fact that some changes were groundbreaking, like moving the recovery to the boot partition instead of having its dedicated partition, as it used to be until a couple of Android versions.
TL;DR: maintainers post these statements so users can discard possible known causes of issues beforehand, and to avoid complaints about pieces of work that aren't their responsibility at all.

All-In-One said:
Xposed modules may cause stability issues on the system due to their nature. Debugging the issue becomes a hard task because there can be a ton of reasons as to why it happens, and you'll be most certainly reaching out to the ROM maintainer to help you fix something not even related to his work.
I can't say for sure but I guess it's because TWRP has had some problems to keep up with the changes made to Android on recent years due to the maintainers' private life and the fact that some changes were groundbreaking, like moving the recovery to the boot partition instead of having its dedicated partition, as it used to be until a couple of Android versions.
TL;DR: maintainers post these statements so users can discard possible known causes of issues beforehand, and to avoid complaints about pieces of work that aren't their responsibility at all.
Click to expand...
Click to collapse
Imho and experience this nearly always down to the Xposed modules not xposed itself. I have been using xposed since my Galaxy S and its been reliable and solid enough that after 10 Samsung devices later (S, S2, S4, S5, Note5, S6, S7, S7edge, Note9, S20FE) I will always install it. And the Xposed modules I run ar XpirvacyLua, Firefds kit [Q], GravityBox [Q] which are then Managed by EdXposed. I tend not to update the modules unless there is a specific issue that an update will fix.
Nope, check the twrp thread i the section we are upto 3.7.x which supports Android 12 (and should support 13 due to it being an incrmental update on 12).
Thats a fair comment.

Hello, is there a possibility to release this also for snapdragon?