Database Info

Magisk Root: XZ

Hi, Does anyone know if Magisk root is supported on the Xperia XZ (F8331)?
The reason I ask is I want to be able to hide root from some apps that will not work with root otherwise i'd use SuperSU.

rasseru16 said:
Hi, Does anyone know if Magisk root is supported on the Xperia XZ (F8331)?
The reason I ask is I want to be able to hide root from some apps that will not work with root otherwise i'd use SuperSU.
Click to expand...
Click to collapse
Yes V12 works great so far

dillalade said:
Yes V12 works great so far
Click to expand...
Click to collapse
Perfect thanks. Now rooted with Magisk

rasseru16 said:
Perfect thanks. Now rooted with Magisk
Click to expand...
Click to collapse
I have had boot loops twice now.
First time I had to do a reinstall.
2nd time I ran the magisk uninstall from TWRP.
Booted up after that
Just a heads up.
I'm researching how to resolve this. Not to sure

rasseru16 said:
Perfect thanks. Now rooted with Magisk
Click to expand...
Click to collapse
I'm rooted with magisk too but unable to hide root from apps like 8ball pool and other apps. Hide root functionality don't work at all.

Have no problems with Magisk V12 so far had it running for several days now. Hiding root from Snapchat, My EE and some other apps without issue. I dont have TWRP installed though.

rasseru16 said:
Perfect thanks. Now rooted with Magisk
Click to expand...
Click to collapse
How do you hide root? With me it just doesn't work. I enable hide root and select app.

Has anyone faced any bootloops with magisk.
Some research has shown it's perhaps when using viper4android together with magisk that can cause a bootloop. But that was on a Nexus 6p from my research.
Has anyone set up magisk and also viper4android, that can let me know if they have faced this bootloop?

I have found that I can use Magisk Root with 'AndroPlus Kernel' but not 'Sony Stock Patcher for Xperia XZ by AdrianDC'. Installing MAGISK under the Sony Stock Patcher Kernel caused TWRP to create an error "Unable to repack boot image!"

latest update working without any hiccups

pw1nce said:
I'm rooted with magisk too but unable to hide root from apps like 8ball pool and other apps. Hide root functionality don't work at all.
Click to expand...
Click to collapse
yes it works, u need to enable magisk core only to make safetynet work and magisk hide too

fastbooking said:
yes it works, u need to enable magisk core only to make safetynet work and magisk hide too
Click to expand...
Click to collapse
Can you prove that or do you mind writing a little guide how to get past safetynet?
I literally tried everything I could find to get Magisk Hide working with unlocked bootloader yesterday after the change to pass Safetynet for Pokemon Go. No chance. Before I could at least remove Magisk to run Go but now that's over. What I tried was latest A.35 with Stock + Patcher or AndroPlus with twrp and then Magisk 13.2 (plus fixes). But I always failed CTS and Basic Integegrity.
Even with Magisk Hide turned on and Core Modules only activated. No chance.

Delvius said:
Can you prove that or do you mind writing a little guide how to get past safetynet?
I literally tried everything I could find to get Magisk Hide working with unlocked bootloader yesterday after the change to pass Safetynet for Pokemon Go. No chance. Before I could at least remove Magisk to run Go but now that's over. What I tried was latest A.35 with Stock + Patcher or AndroPlus with twrp and then Magisk 13.2 (plus fixes). But I always failed CTS and Basic Integegrity.
Even with Magisk Hide turned on and Core Modules only activated. No chance.
Click to expand...
Click to collapse
How to fix this:
1. This fix is only a temporary fix. You will have to apply it after every reboot.
2. Use a Terminal emulator app or adb to enter these commands.
3. Use resetprop to delete the properties - again: I have no idea how this interferes with magisk behavior!!!! Do this at your own risk:
Code:
su
resetprop --delete init.svc.magisk_pfs
resetprop --delete init.svc.magisk_pfsd
resetprop --delete init.svc.magisk_service
resetprop --delete persist.magisk.hide
Using Magisk Core mode? also execute this command:
Code:
resetprop --delete ro.magisk.disable

smellz said:
How to fix this:
1. This fix is only a temporary fix. You will have to apply it after every reboot.
2. Use a Terminal emulator app or adb to enter these commands.
3. Use resetprop to delete the properties - again: I have no idea how this interferes with magisk behavior!!!! Do this at your own risk:
Code:
su
resetprop --delete init.svc.magisk_pfs
resetprop --delete init.svc.magisk_pfsd
resetprop --delete init.svc.magisk_service
resetprop --delete persist.magisk.hide
Using Magisk Core mode? also execute this command:
Code:
resetprop --delete ro.magisk.disable
Click to expand...
Click to collapse
Does it work for you? It doesn't for me. As I worte I did exactly this - no chance.
If it works for you, which firmware, kernel and twrp do you use?

Delvius said:
Does it work for you? It doesn't for me. As I worte I did exactly this - no chance.
If it works for you, which firmware, kernel and twrp do you use?
Click to expand...
Click to collapse
Yes it works with me.
Fw: 41.2.A.7.8
Kernel: AndroPlus kernel v27
Twrp: twrp-3.1.1-20170523-boot-kagura (DL: https://mega.nz/#F!bg9QhDzC!TTkhy2Fi6cNTZ1ojlmobRQ )
Magisk: v13.2 and 5.0.6 Manager

Delvius said:
Can you prove that or do you mind writing a little guide how to get past safetynet?
I literally tried everything I could find to get Magisk Hide working with unlocked bootloader yesterday after the change to pass Safetynet for Pokemon Go. No chance. Before I could at least remove Magisk to run Go but now that's over. What I tried was latest A.35 with Stock + Patcher or AndroPlus with twrp and then Magisk 13.2 (plus fixes). But I always failed CTS and Basic Integegrity.
Even with Magisk Hide turned on and Core Modules only activated. No chance.
Click to expand...
Click to collapse
You need to know that Google updated safetynet for magisk 13.2 so for the moment it's pretty random to get it working, the team is aware of that and they're making the necessary to fix this

smellz said:
Yes it works with me.
Fw: 41.2.A.7.8
Kernel: AndroPlus kernel v27
Twrp: twrp-3.1.1-20170523-boot-kagura (DL: https://mega.nz/#F!bg9QhDzC!TTkhy2Fi6cNTZ1ojlmobRQ )
Magisk: v13.2 and 5.0.6 Manager
Click to expand...
Click to collapse
Thanks a lot! You give me hope.

Delvius said:
Thanks a lot! You give me hope.
Click to expand...
Click to collapse
V13.3 fix safetynet
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Code:
v13.3
- [MagiskHide] Update to bypass Google CTS (2017.7.17)
- [resetprop] Properly support removing persist props
- [uninstaller] Remove Magisk Manager and persist props

Still not working for me even with latest version. I'm still waiting silently for any help here.

boydzethuong said:
Still not working for me even with latest version. I'm still waiting silently for any help here.
Click to expand...
Click to collapse
What kernel are you using?
Here is a small guide which definitely works:
1.Flash firmware 4.2.A.7.8
2. Uses tobias.waldvogel tool for fido_keys
Code:
-.ftf with WinRAR open,
-Kernel.in unpack,
-Open Flashtool,
-Select Top Tools,
-Sin Editor and in the next window
-Extract data.
-Now the extracted kernel.elf in the folder of the waldvogel its tool,
-There open the WinKonsole,
-Enter this command:
-Rootkernel kernel.elf boot.img,
-Disable sony_ric => YES
-Disable ... verity => YES
-DRM-Fix => YES
-TWRP => NO
-BusyBox => NO
-
NOW THE KERNEL FLASH
3. Flash TWRP: twrp-3.1.1-20170523-boot-kagura (DL: https://mega.nz/#F!bg9QhDzC!TTkhy2Fi6cNTZ1ojlmobRQ )
4. Flash Kernel via TWRP - AndroPlus kernel v27 and Reboot
5. Flash Magisk v13.3 via TWRP
Finished and safetynet should work

[GUIDE][PORT] How to install the Android Pie sGSI on your Xiaomi Mi A1

Code:
Disclaimer:
I am not responsible for anything that may happen to your phone as a result of installing this GSI and/or kernels. You do so at your own risk and take the responsibility upon yourself.
MOD EDIT: Remember to be prepared for an experimental or unstable ROM. If do you not know what you are doing or not experienced with flashing and recovering your data then it's not recommended.
REMEMBER TO BACKUP EVERYTHING AS THIS WILL REPARTITION YOUR USERDATA AND WILL WIPE YOUR INTERNAL STORAGE. ALSO, REMEMBER TO READ EVERYTHING AS ALL FIXES ARE POSTED BELOW. DON'T JUST FLASH THEN JOIN TELEGRAM TO ASK WHY THIS DOESN'T WORK FOR YOU.
READ THE IMPORTANT NOTES POSTED HERE​
TO REVERT TO NON-TREBLE/STOCK ROM, WATCH THIS VIDEO BY @GizmoFreak OR FOLLOW THIS POST
Here's everything I can provide to the normal user willing to try this out on their Mi A1.
PLEASE VISIT THIS NOTE TO SEE ALL THE REMAINING BUGS
OR JUST READ THEM HERE
SELinux is permissive
Hw key lights don't light up
Everything else works fine. Just need to update your Google Play services app and you can restore apps via Google Backup (if you didn't already do it with Titanium Backup). Yes, rooting with Magisk works and some modules work as well such as Blobmojis among others.
Here are the steps to install it in your Mi A1 if you're coming from stock ROM
Or watch a video made by @GizmoFreak
Enable Developer options in Settings app
Check Enable OEM Unlocking
Reboot to fastboot mode
Unlock your bootloader
Install TWRP-fastboot only through fastboot boot command (Extract the .img file from the zip)
Flash CosmicDan's TWRP Installer through your current TWRP. Credits to @CosmicDan for his TWRP and @mohancm for official TWRP sources.
Reboot to TWRP recovery
Go to WIPE then ADVANCED then click FORMAT data. This will remove Encryption on your device and allows you to set new passwords when installing the GSI. Note that this will format your internal storage.
Treblelize through TWRP Tissot Manager (Go to advanced, click Tissot Manager and choose the repartition userdata option. Select singleboot option then click repartition)
Flash latest Vendor.img as VENDOR IMAGE
Flash A/B system Pie PR2 img as SYSTEM IMAGE (Extract the .img file from the zip) (special thanks to @dgadelha for the sGSI)
Flash POST-sGSI 1 tissot zip.
Flash POST-sGSI 2 tissot zip.
Flash a treble-compatible kernel (Moun, ProjectK,Velocity)(credits to @mountaser halak, @khusika, @kdragon)
Reboot to system.
Once booted, install the latest Play services linked above either via the Files app or via adb. This will fix the Pixel Setup and Google Backup issues as well as allows you access to the Play Store without problems.
You can now flash Magisk 17.3. This is the version that works properly with treble. Credits to @topjohnwu for Magisk.
Install the Data transfer tool APK update as well.
Special thanks to @erfanoabdi for porting the Pie A/B GSI.
Some features may seem to be broken but can actually be fixed with a few tweaks
USB MTP FIX
To enable USB MTP, enable Developer options in the About phone section of the Settings app by tapping the Build Number 4 times. Then look for the File Transfer option in the Dev options.
ENABLE NAV BAR GESTURES
To enable Nav Bar, I installed this nav bar enabler by @Hugwalk via Magisk.
After rebooting, go to Settings > System > Gesture and enable Swipe Up on Home Button to enable the Nav Bar Gestures.
SUBSTRATUM
Substratum is now much better for Pie.
Install the latest APK from this telegram channel and now all themes with Pie support can be installed.. Just reboot after building the themes and go into managers to enable the overlays you built.
Ethereal - https://play.google.com/store/apps/d...ethereal&hl=en
Outline - https://play.google.com/store/apps/d....outline&hl=en
Compound - https://play.google.com/store/apps/d...compound&hl=en
Sai's theme - https://t.me/tissotpsemigsi/33526
Click to expand...
Click to collapse
You should have the Android Pie booting on your Mi A1 now with less issues.
To update from PR1 to PR2, you can do so without wiping data
Wipe system ONLY
Flash PIE PR2 AB GSI
Reboot to system
Click to expand...
Click to collapse
To update your post post GSI zips, follow this
Wipe vendor ONLY
Flash vendor
Flash POST-sGSI 1 tissot zip.
Flash POST-sGSI 2 tissot zip.
Reboot to system
Click to expand...
Click to collapse

Awesome work @joeyhuab bro ?

Edit:- Chrome sucks! Posted same thing twice.

Youtube not working for me(

Great job!!!i will wait to change to beta

Tornado95 said:
Youtube not working for me(
Click to expand...
Click to collapse
I also encounter YouTube issues. :/

Don't work the camera and black for me

ErickCartman17 said:
Don't work the camera and black for me
Click to expand...
Click to collapse
Try Footej Camera from Play Store please, it can be usefull if Footej or Open Camera works

waiting camera fix

cant mount system(invalid argument)
Failed to mount system after i try to flash GSI

I will wait for the stable...but is a good work... Thanks for try this.

andrexp31 said:
I will wait for the stable...but is a good work... Thanks for try this.
Click to expand...
Click to collapse
lol, then just wait for the official release. This is as close as we can get, for now since google hasn't uploaded the source code for P yet

I'm already looking into a fix for Camera. I'll post it once it's available.

What if I want to come back from Android Phone to another Custom ROM? Do I have to "un-treble" the device?

When I Flash A/B system GSI img i have a 255 error: Updater process ended with ERROR: 255 Error installing xip file `tissot_manager/flash_proxy.zip`. How i can fix it? What is the problem?

danilguy said:
When I Flash A/B system GSI img i have a 255 error: Updater process ended with ERROR: 255 Error installing xip file `tissot_manager/flash_proxy.zip`. How i can fix it? What is the problem?
Click to expand...
Click to collapse
Remove the spaces from the folder name and try... Works for me...

Camera has been fixed. Just adding some more fixes and we'll probably get fingerprint working too. I'll update the links later when done.

joeyhuab said:
Camera has been fixed. Just adding some more fixes and we'll probably get fingerprint working too. I'll update the links later when done.
Click to expand...
Click to collapse
U have don great work
Really well done
Waiting for camera, fingerprint and flash bugs fixed and i will surely test the rom

What about Bluetooth?

Chris_Cheekyz said:
What about Bluetooth?
Click to expand...
Click to collapse
Fixed as well together with Camera fix. Credits to Rupansh and @kdragon for using Whyred's blobs. Credits also to @ghpranav for BT fix.
Download

[Q] Have you successfully rooted your Samsung Galaxy A8 (2018) Oreo?

It seems there are some conflicting reports on the issue. Some people say that rooting Oreo can't be done because there is an issue with Magisk/SuperSU preventing it, while others says they've managed to root their Oreo A8.
I would just like to get an idea of anyone who has tried to root Oreo. Please share your experience to date.
Did it fail or was it successful?
Is everything running smoothly?
What method and steps did you use?
I'm sure I'm not the only one who would appreciate the feedback.

it failed
no natter what i did
on modifying the /system through twrl, on reboot, the os locks the sim, uninstalls the Samsung apps like pay/health etc and then re encrypts the phone

shunsai said:
It seems there are some conflicting reports on the issue. Some people say that rooting Oreo can't be done because there is an issue with Magisk/SuperSU preventing it, while others says they've managed to root their Oreo A8.
I would just like to get an idea of anyone who has tried to root Oreo. Please share your experience to date.
Did it fail or was it successful?
Is everything running smoothly?
What method and steps did you use?
I'm sure I'm not the only one who would appreciate the feedback.
Click to expand...
Click to collapse
Yep
https://forum.xda-developers.com/ga...--other-development/root-magisk-oreo-t3825096

Used Ashyx TWRP and no-verity-opt-encrypt_ashyx, from corsicanu's thread. I've used Magisk v16.0 stable as well as beta v16.7.
Root is working for ADB, Termux and Xposed (installed as Magisk module). Root is not working for Titanium (says it can't detect root; used Magisk busybox) and for Stericson's Busybox (says unverified binary and won't install). Another thing I've noticed is that microG's UnifiedNlp "self check" says NO to "UnifiedNlp is registered in system".
Magisk was showing as "not installed" in Magisk Manager for a while, but switched to green (installed) after a few reboots. Not sure what I've done to change it. I suspect it's a certain combination of TWRP and no-verity-opt-encrypt that does the trick, because I've been alternating between Mesa's and Ashyx's versions. Magisk root was working even when Manager was saying "not installed".
I will retry with a clean reinstall of Oreo 8.0.0, Mesa's TWRP and no-verity-opt-encrypt-6.0.zip from his TWRP thread. I'm on official ROM A530FXXU2BRG1.
I haven't tested SuperSU much, I will try it more thoroughly. (Personally I don't care about systemless and hiding from SafetyNet or *Pay stuff, so whatever root method works is fine with me.)
Whatever you do, a piece of advice: follow whatever guide you're using carefully, because not doing all the steps properly can end up in a mess (eg. bootloops, or you get a screen asking for password to decrypt phone that won't go away). Also, it seems that mixing flashable stuff from different sources is a bad idea unless you know what you're doing.

Same as above. Best working combination I've found is Mesa's TWRP and no-verity, with Magisk 16.7 and Manager 5.8.3.
Root works with mostly everything I've thrown at it, with the following notable exceptions:
* Titanium Backup triggers the popup to ask for root, but says "Sorry, I could not acquire root privileges."
* UnifiedNlp's self check says "can't integrate with system".
* As soon as you flash Magisk, MTP and ADB stop working. When you connect to the PC there's no popup for either "allow connection" or ADB fingerprint.
Mesa's kernel fixes the MTP issue, and PC connection "allow" popup starts working again.
On the flip side, attempting to enter developer settings while running Mesa's kernel crashes the settings app. I've used a terminal app (Termux) to enable ADB manually (or you can enable it before you flash the kernel):
Code:
settings put global development_settings_enabled 1
settings put global adb_enabled 1
Here's everything I've gathered about the process (or as I like to call it, "how to get root on A8 2018 in 20 easy steps"):
* Start the phone, enable OEM lock from developer settings. Never disable it again, it prevents the phone from booting if any of the partitions are unofficial.
* Use Odin 3.13 or later, earlier versions can't deal with the new LZ4 compression Samsung applies to the partition images. Heimdall is very old and will not work. If you're on Linux, use a virtual machine to run Odin under Windows. VirtualBox is excellent (remember to connect the phone from VB's USB menu when in download mode).
* Power+VolDn+VolUp from any situation will force reboot. Power+VolDn+VolUp immediately after start enters download mode.
* Flash BL, AP, CP and CSC from an official ROM to bring the device to factory status.
* At this point you phone is functional, if you don't want root and just want to use it, stop here.
* If you intend to continue, I recommend that you don't boot to system.
* Reboot and re-enter download mode, flash Mesa's TWRP.
* Reboot and immediately press Power+VolUp to enter TWRP. Do NOT boot to system just yet, you can trip the anti-theft protection.
* [Always] swipe to allow modifications when entering TWRP.
* You may want to grab a TWRP backup of various partitions at this moment. Recovery is obviously not official anymore, but you can grab boot, system, efs, baseband, modem etc. Very good idea. If your SD card is not large enough for system (has 3.5 GB) at least grab the others.
* From Wipe menu, choose format data. Boot to RECOVERY. Do not install TWRP app.
* From Mount menu, verify that Data is mounted.
* Flash in this order: RMM fix and no-verity.
* Reboot to system, let it work (Samsung logo and blue led flashing). Yes, it may take a lot of time, let it work.
* At this point you have a clean system with custom recovery but no root. Check that stuff is still working fine.
* During phone setup, do NOT check "send diagnostic data".
* Reboot to TWRP, flash Magisk.
* Again, the first boot may take a long time, let it work.

wirespot said:
Same as above. Best working combination I've found is Mesa's TWRP and no-verity, with Magisk 16.7 and Manager 5.8.3.
Root works with mostly everything I've thrown at it, with the following notable exceptions:
* Titanium Backup triggers the popup to ask for root, but says "Sorry, I could not acquire root privileges."
* UnifiedNlp's self check says "can't integrate with system".
* As soon as you flash Magisk, MTP and ADB stop working. When you connect to the PC there's no popup for either "allow connection" or ADB fingerprint.
Mesa's kernel fixes the MTP issue, and PC connection "allow" popup starts working again.
On the flip side, attempting to enter developer settings while running Mesa's kernel crashes the settings app. I've used a terminal app (Termux) to enable ADB manually (or you can enable it before you flash the kernel):
Here's everything I've gathered about the process (or as I like to call it, "how to get root on A8 2018 in 20 easy steps"):
* Start the phone, enable OEM lock from developer settings. Never disable it again, it prevents the phone from booting if any of the partitions are unofficial.
* Use Odin 3.13 or later, earlier versions can't deal with the new LZ4 compression Samsung applies to the partition images. Heimdall is very old and will not work. If you're on Linux, use a virtual machine to run Odin under Windows. VirtualBox is excellent (remember to connect the phone from VB's USB menu when in download mode).
* Power+VolDn+VolUp from any situation will force reboot. Power+VolDn+VolUp immediately after start enters download mode.
* Flash BL, AP, CP and CSC from an official ROM to bring the device to factory status.
* At this point you phone is functional, if you don't want root and just want to use it, stop here.
* If you intend to continue, I recommend that you don't boot to system.
* Reboot and re-enter download mode, flash Mesa's TWRP.
* Reboot and immediately press Power+VolUp to enter TWRP. Do NOT boot to system just yet, you can trip the anti-theft protection.
* [Always] swipe to allow modifications when entering TWRP.
* You may want to grab a TWRP backup of various partitions at this moment. Recovery is obviously not official anymore, but you can grab boot, system, efs, baseband, modem etc. Very good idea. If your SD card is not large enough for system (has 3.5 GB) at least grab the others.
* From Wipe menu, choose format data. Boot to RECOVERY. Do not install TWRP app.
* From Mount menu, verify that Data is mounted.
* Flash in this order: RMM fix and no-verity.
* Reboot to system, let it work (Samsung logo and blue led flashing). Yes, it may take a lot of time, let it work.
* At this point you have a clean system with custom recovery but no root. Check that stuff is still working fine.
* During phone setup, do NOT check "send diagnostic data".
* Reboot to TWRP, flash Magisk.
* Again, the first boot may take a long time, let it work.
Click to expand...
Click to collapse
Were you able to test from a non-tripped Knox and if so was it tripped by your process?

I don't have another phone with the e-fuse not tripped so I can't test, but USB works perfectly fine until you flash root and also after you flash Mesa's kernel.

Pipsname said:
Were you able to test from a non-tripped Knox and if so was it tripped by your process?
Click to expand...
Click to collapse
Un-tripped Warranty Bit and Root are two thing that can't stay together lol
---------- Post added at 06:01 PM ---------- Previous post was at 06:00 PM ----------
wirespot said:
On the flip side, attempting to enter developer settings while running Mesa's kernel crashes the settings app.
Click to expand...
Click to collapse
Never heard about this issue; Could you please share a log of the error to look at it to fix it? A new version of the kernel is under-the-hood so would be nice to fix all the possible issues

BlackMesa123 said:
Un-tripped Warranty Bit and Root are two thing that can't stay together lol
Click to expand...
Click to collapse
I am currently rooted on 7.1.1 with no tripped Knox so I was wondering if it was possible with Oreo.

Pipsname said:
I am currently rooted on 7.1.1 with no tripped Knox so I was wondering if it was possible with Oreo.
Click to expand...
Click to collapse
Rooted without tripping Warranty Bit? And how since bootloader checks binary signatures at each boot lol

BlackMesa123 said:
Never heard about this issue; Could you please share a log of the error to look at it to fix it? A new version of the kernel is under-the-hood so would be nice to fix all the possible issues
Click to expand...
Click to collapse
Kernel log? Would an export from logcat do?

wirespot said:
Kernel log? Would an export from logcat do?
Click to expand...
Click to collapse
Nah a simple logcat is what I need lol. Use Logcat Extreme if you don't wanna use adb

BlackMesa123 said:
Nah a simple logcat is what I need lol. Use Logcat Extreme if you don't wanna use adb
Click to expand...
Click to collapse
Lel I use matlog

In some hour (or maybe less lol) the new version of my custom kernel will be released, with a good present for you all... ?

BlackMesa123 said:
In some hour (or maybe less lol) the new version of my custom kernel will be released, with a good present for you all... ?
Click to expand...
Click to collapse
I can't open the therd image.

BlackMesa123 said:
Rooted without tripping Warranty Bit? And how since bootloader checks binary signatures at each boot lol
Click to expand...
Click to collapse
I used your guide.
https://forum.xda-developers.com/ga...recovery-twrp-3-2-2-0-galaxy-a8-2018-t3818201

Pipsname said:
I used your guide.
https://forum.xda-developers.com/ga...recovery-twrp-3-2-2-0-galaxy-a8-2018-t3818201
Click to expand...
Click to collapse
Lol that's faked userspace warranty bit prop. Go in Download Mode and you see Warranty Bit is actually blown

BlackMesa123 said:
Lol that's faked userspace warranty bit prop. Go in Download Mode and you see Warranty Bit is actually blown
Click to expand...
Click to collapse
Well would you look at that! Thank you.

Is Magisk 16.7 Beta?

Samsung Galaxy (SM-A530F/DS) A8 (2018), Android 8.0.0.
After 129 hours I got OEM Unlock. I installed TWRP 3.2.3-0. In TWRP > Wipe>Format Data and follow the instructions in screen. After I flashed latest no-verity-opt-encrypt zip and RMM Bypass zip. Reboot System.
In TWRP I flashed MCK-Oreo_A8_BRG1_v1-fix.zip. Reboot System.
In TWRP I flashed Magisk 16.7 Beta. Reboot System.
I installed Magisk Manager 5.8.3. and I got this:

[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?