Related
Before I get into this guide I am going to start off with a disclaimer. If you break or harm your device. Or make it unbootable. This is not my fault, and you understand that you are doing this at your OWN RISK.
Now let's get into the guide!
Tip for Section Number #1: If you are having trouble using the windows file explorer or any other OS, use Sync by BitTorrent and sync files to your computer, I am not promoting the app for any self gain, just a suggestion
NOTICE: ROOTING THE N PREVIEW IS ONLY POSSIBLE USING A DECRYPTED DEVICE FROM MY KNOWLEDGE
This will be separated into sections. As listed below:
Installing Android N with working TWRP
Rooting Android N Preview
Enabling Permissive SELinux without a instant reboot
More may be added in the future!
Installing Android N with a working TWRP
Easier method :
If you have Marshmallow already installed, you can enroll your device for a OTA of Android N Developer Preview. Or you can install Marshmallow and then do the same.
Longer method :
Backup all your userdata files (I MEAN EVERYTHING!) this will erase all of your files if you want a working TWRP.
1. Download the Android N .tgz file for your device from here -=OPTIONAL=-Download the modifed boot image with decryption on boot disabled for your Preview version here
2. Decompress/extract every file. (the main file and the image directory) I would recommend having all of them in the same folder
3. Make sure you have fastboot, then open a terminal/command prompt in that folder - Shift + right click in windows then open command prompt here
4. MAKE SURE YOU HAVE YOUR DATA BACKED UP, THIS IS NECESSARY IF YOU WANT TO KEEP YOUR FILES AND HAVING A WORKING TWRP - optional
5. Boot your device into the bootloader, power down your phone (this is for nexus 6p) and hold the power button + volume down until you see a Android figure laying down
6. Do the following commands in a terminal with fastboot installed - this is inferring you have a unlocked bootloader
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash vendor vendor.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img - the modified one you downloaded, if you did.
fastboot flash recovery twrp-xxxxx-angler
fastboot format cache
fastboot flash cache cache.img
-=OPTIONAL, FOR DECRYPTION AND WORKING TWRP=-:fastboot format userdata - do not flash the userdata.img unless you have a 32gb Nexus 6P.
fastboot reboot
Now, once the device boots. Set it up and go to Settings>Security and under encryption if you want a working TWRP, it should say Decrypt phone. If not, look back and see if you did a step wrong.
Rooting Android N Preview xx
1. Download the latest BETA of SuperSU - or anything above 1.74. BETA onto your device's sdcard directory. (otherwise known as /storage/emulated/0/)
2. Reboot your device to TWRP by powering off your device, then holding the power button + volume down. Once in the bootloader, tap the volume down button until you land on Recovery. Then press the power button.
3. Go to the install section, and flash your SuperSU zip.
4. Reboot, it may reboot a few times. Let the device run it's course until it lands at the lockscreen, this is important.
Enabling a permissive SELinux without a instant reboot
Follow the guide here
In other words, download the logd file and copy and paste it to /system/bin/ then replace the other file after backing it up.
Then do
setenforce 0
in a terminal with root access on your device and then do getenforce to check if it's working.
This enables you to restore backups using Titanium backup, as it doesn't work without doing this.
Credits
Credit for SuperSU goes to @Chainfire
Credit for the modified boot.img goes to @Tigerstown
Credit for getting Permissive SELinux to work on Android N goes to @gubacsek
I do not take credit for any of the downloaded content, all of the downloaded files goes to their original creators.
PM me if anything is wrong, or edit this post!
Mods, if this post is in the wrong place. Move it to the correct place please!
Happy modding of your Nexus 6P on Android N Preview!
Isn't this the same guide as this: http://forum.xda-developers.com/showthread.php?t=3206928 ?
Sent from my Nexus 6P using XDA-Developers mobile app
johnhazelwood said:
Isn't this the same guide as this: http://forum.xda-developers.com/showthread.php?t=3206928 ?
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, in some ways. But this thread is all the information from around XDA put in one place. As I haven't found a thread with the information put together like this.
Yeah, I agree. I had to hunt through several threads to find this when I updated both my 6P's to N the other day. I knew the info was out there, but was a PITA to find. Too bad you didn't put this thread up 3 days ago when I needed it LOL.
Just a quick FYI, it is possible to run rooted N with encryption. I just wrote a guide on how to do it: http://forum.xda-developers.com/nexus-6p/general/guide-android-nougat-developer-preview-t3410906
Bump
Great guise. Might use this later to finally flash android N. I just wished that xposed worked with Android N.
TnT_ said:
This enables you to restore backups using Titanium backup, as it doesn't work without doing this.
Click to expand...
Click to collapse
If you don't like to disable SELinux, you can simply change SELinux's policy using supolicy. Execute the following commands in the terminal:
Code:
supolicy --live "allow system_app shell_data_file dir { search read write }"
supolicy --live "allow system_app dalvikcache_data_file dir { write read add_name remove_name }"
supolicy --live "allow system_app dalvikcache_data_file file { create }"
supolicy --live "allow system_app shell_data_file file { read open write }"
The following commands are needed for AdAway (busybox required):
Code:
supolicy --live "allow untrusted_app system_data_file file { read write }"
supolicy --live "allow shell dalvikcache_data_file dir { read write }"
supolicy --live "allow shell shell capability { dac_override }"
supolicy --live "allow shell dalvikcache_data_file dir { write remove_name add_name }"
supolicy --live "allow shell dalvikcache_data_file file { create write read open }"
This doesnt work for me. I tried twice. I even tried the modified boot.img. both times it says in security encrypted phone. What do I do?
XAL2 said:
This doesnt work for me. I tried twice. I even tried the modified boot.img. both times it says in security encrypted phone. What do I do?
Click to expand...
Click to collapse
@XAL2 you don't need to be decrypted - scroll up to my last post in the thread and follow the instructions there to get N and keep encryption.
asj0422 said:
@XAL2 you don't need to be decrypted - scroll up to my last post in the thread and follow the instructions there to get N and keep encryption.
Click to expand...
Click to collapse
So do I have to flash back to Marshmallow stock then try to reflash N? Or do I just go into the bootloader and reflash the M vendor image flash twrp, boot into it flash super su, and then reflash the N vendor and reboot?
Can you dirty flash (wipe cache) N over M? My device is running a stock image + root + busybox, TWRP, encrypted. Can I just flash everything over (without recovery) via fastboot, root via TWRP, and be done with it?
XAL2 said:
So do I have to flash back to Marshmallow stock then try to reflash N? Or do I just go into the bootloader and reflash the M vendor image flash twrp, boot into it flash super su, and then reflash the N vendor and reboot?
Click to expand...
Click to collapse
That sounds like it would work to me - although I don't think you have to flash the M vendor image before you flash the recovery, you just can't have the N vendor image when you try to use twrp.
---------- Post added at 08:12 PM ---------- Previous post was at 08:07 PM ----------
vostok4 said:
Can you dirty flash (wipe cache) N over M? My device is running a stock image + root + busybox, TWRP, encrypted. Can I just flash everything over (without recovery) via fastboot, root via TWRP, and be done with it?
Click to expand...
Click to collapse
Technically, yes - check out this guide I wrote, it's actually for your exact scenario. The issue is that twrp doesn't play nice with N, but if you wait on the vendor image before you use twrp, you're good to go.
http://forum.xda-developers.com/nexus-6p/general/guide-android-nougat-developer-preview-t3410906
Thank you, that worked perfectly!
PREREQUISITE
- adb enabled [developer options]
- root [Magisk/SU]
- original /vendor partition [flashed with official update/firmware]
- File/Root Explorer
- adb for Windows [Minimal ADB and Fastboot, provided]
- UKA [Unpacker Kitchen for Android] - Send me a PM
- USB cable always connected
Reserved
You can do the same steps for the other logical partitions [system & product]
At the end you do :
System
tune2fs -L / /data/local/UnpackerSystem/system.new.img
tune2fs -O ^read-only /data/local/UnpackerSystem/system.new.img
tune2fs -O ^has_journal /data/local/UnpackerSystem/system.new.img
adb shell
su
dd if=/sdcard/system.img of=/dev/block/dm-2
(just copy/past to avoid errors !)
Reboot your phone right away !
Product
must be renamed vendor because the Magisk Module still doesn't support this name yet ... just rename it vendor.img before taking any action ... and after creating your image, do :
tune2fs -L product /data/local/UnpackerSystem/vendor.new.img
tune2fs -O ^read-only /data/local/UnpackerSystem/vendor.new.img
tune2fs -O ^has_journal /data/local/UnpackerSystem/vendor.new.img
NOW you can rename it product.img
adb shell
su
dd if=/sdcard/product.img of=/dev/block/dm-0
Reboot your phone right away !
"Houston, we have problem!"
Now what? Is this only for MIUI users? I have flashed Nusantara ROM right now...
Also it is possible, that you can create "default" RW images for surya, upload them somewhere on cloud (one RW system please! medium rare, thank you ... 12.0.7 is fine for me...)
... but anyway, thanks for your hard work...
BTW @brigudav already created flashable RW vendor for Surya, can that be done also for system?
jeryll said:
"Houston, we have problem!"
View attachment 5232079
Now what? Is this only for MIUI users? I have flashed Nusantara ROM right now...
Also it is possible, that you can create "default" RW images for surya, upload them somewhere on cloud (one RW system please! medium rare, thank you ... 12.0.7 is fine for me...)
... but anyway, thanks for your hard work...
BTW @brigudav already created flashable RW vendor for Surya, can that be done also for system?
Click to expand...
Click to collapse
Check your Mount Namespace Mode in Magisk Manager
No it's not only for miui, it's for all roms ! (btw i'm on LOS 17.1 ... and i never used MIUI)
Yes, you can do that for the 3 logical partitions ... this tutorial is for all devices with dynamic paritition aka super.img (not limited to poco x3 nfc !!!)
I will put a clean vendor.img later (with RW enabled and AVB-Verity Disabled)
I will put a modded version of Magisk 20.4 too if someone would use it (like me)
janhammer504 said:
Check your Mount Namespace Mode in Magisk Manager
No it's not only for miui, it's for all roms ! (btw i'm on LOS 17.1 ... and i never used MIUI)
Click to expand...
Click to collapse
- thanks for the answer, but I must say I'm unable to continue, because I'm unable to install UKA module on A11 ROM
- regardless of Mount Namespace Mode - I checked all three - with reboot - result is the same
- I'm also unable to install magisk 20.4 on A11 ROM - and with v21.0 or higher - UKA will not install
- so Id say this guide is for now useable only for A10 users
- I will test A10 ROM in a few days
- maybe there is a problem with my phone, but I reflashed full recovery version of latest MIUI before flashing custom rom together with encryption disabler, so my super partition should be cleaned up
- so using unencrypted storage could be another problem for this to work?
jeryll said:
- thanks for the answer, but I must say I'm unable to continue, because I'm unable to install UKA module on A11 ROM
- regardless of Mount Namespace Mode - I checked all three - with reboot - result is the same
- I'm also unable to install magisk 20.4 on A11 ROM - and with v21.0 or higher - UKA will not install
- so Id say this guide is for now useable only for A10 users
- I will test A10 ROM in a few days
- maybe there is a problem with my phone, but I reflashed full recovery version of latest MIUI before flashing custom rom together with encryption disabler, so my super partition should be cleaned up
- so using unencrypted storage could be another problem for this to work?
Click to expand...
Click to collapse
Hi, flash an official MIUI for your device.
Do the dirty job and save your vendor.img
Reflash your rom !
(i have already uploaded a clean vendor.img here)
I close this thread too since a lot of features have been added to this work ... and since there are many disrespectful developers-like around who steal my work and give no credit !
Check my custom vendor thread to learn more about this work !
If you have any question, send me a PM, i will check first if you are not a troll : if you get no answer from me, then understand by yourself !
@janhammer504 Hi. For the sake of the community it's always sad to see someone taking their work from XDA.
If you've got issues with other people using your work without credit here on XDA you can always reach out to someone on the moderator team for help. Or better yet, one of us on the Developer Relations team. We can help you solve any disputes and make sure you get proper credit.
You can find a list of moderators here:
https://docs.google.com/document/d/1lK5rP103OL3StU3q9iqwX9LU_k8XABeSQIAT3EHCqgM/pub
Easy to way to install a GSI on your Samsung A21s without installing a Virtual Linux.
NFC, Screen Cast, and USB MTP unfortunately is not working with AOSP 10 and 11. Backup all your data.
If don't want to make one, download my Pre-Rooted GSIs below and flash.
*Unlock your Bootloader and wipe your data using your stock recovery and quickly boot to Download Mode and flash the super.tar on Odin (AP):
Android 10 -> Download (MediaFire)Android 11 -> Download (MediaFire)Android 11 - AOSP 11.0 v306 -> Download (MEGA) - NEWAndroid 10 Screenshots
1. Requirements:
1. Unlock your Bootloader2. Download and Install a Linux Subsystem -> Ubuntu Subsystem -> "Tutorial How to install Linux Subsystem on Windows 10 | or search how to"3. GSI Android 10 A/B Gapps -> Download only the "arm64, A/B". I recommend releases from Treble Experimentations AOSP like "system-roar-arm64-ab-gapps.img.xz". 4. Samsung.zip -> There's all needed tools and files - Odin, 7-Zip ZS etc...
- Download Samsung.zip and extract the folder "Samsung" to your desktop, and extract your chosen GSI using to this folder.
- Download your stock firmware and extract the super.img.lz4 file from AP_A217XXXXXXXXXX_XXX_XXXX_REV00_XXX.tar.md5 with 7-Zip ZS.
- Now extract super.img.lz4 using 7-Zip ZS (don't use 7-zip) to Samsung folder. Rename super.img to stock_super.img.
2. Convert stock_super.img to raw_super.img:Open CMD ad use this codes:
cd C:\Users\%USERNAME%\Desktop\Samsungsimg2img.exe stock_super.img raw_super.img
Wait...
3. Extract raw_super.img:On your Samsung folder, use SHIFT key of your keyboard + right click and click at "Open Linux Shell Here", wait a little, and use this code and wait the extraction:
./lpunpack --slot=0 raw_super.img
*If the extraction is completed, verify if there's this files odm.img, system.img, vendor.img and product.img. Delete or rename system.img and product.img, then extract your GSI to Samsung folder and rename the xxx.img file to system.img.
4. Pack all the files and Flash:No math here! Just use this code on Terminal and wait (Ignore errors like "Partition system, vendor, odm will resize..." or "Invalid sparce file format at header magic...")
./lpmake --metadata-size 65536 --super-name super --metadata-slots 2 --device super:5557452800 --group main:3819597824 --partition system:readonly:3340271616:main --image system=./system.img --partition vendor:readonly:474976256:main --image vendor=./vendor.img --partition odm:readonly:4349952:main --image odm=./odm.img --sparse --output ./super.img
Wait....
Use 7-Zip to archive the super.img to .tar (super.tar) and flash it on Odin (AP) and wait the phone to boot.
Unlock your Bootloader and wipe your data using your stock recovery and quickly boot to Download Mode and flash the super.tar on Odin (AP):
Notes:I not responsible for any damage on your phone. If anything occurs, just flash your stock regional firmware through Odin.
If this tutorial did not work, you did something wrong or your phone is not supported. Don't forget to wipe your data through Recovery, it's very important.
If you want Magisk working on your A21s I recommend you to report to an issue Topjohnwu at Github.
Dear Wer99,
I Successfully Made A Non-Rooted GSI By Following Your [Tutorial / Guide],
I'm Wondering How Could I Add SuperSU & Root Permission In It
GSI : [CherishOS, AOSP10, AOSP11]
Wer99 said:
Easy to way to install a GSI on your Samsung A21s without installing a Virtual Linux.
NFC, Screen Cast, and USB MTP unfortunately is not working with AOSP 10 and 11. Backup all your data.
If don't want to make one, download my Pre-Rooted GSIs below and flash.
*Unlock your Bootloader and wipe your data using your stock recovery and quickly boot to Download Mode and flash the super.tar on Odin (AP):
Android 10 -> Download (MediaFire)Android 11 -> Download (MediaFire)Android 11 - AOSP 11.0 v306 -> Download (MEGA) - NEWAndroid 10 Screenshots
1. Requirements:
1. Unlock your Bootloader2. Download and Install a Linux Subsystem -> Ubuntu Subsystem -> "Tutorial How to install Linux Subsystem on Windows 10 | or search how to"3. GSI Android 10 A/B Gapps -> Download only the "arm64, A/B". I recommend releases from Treble Experimentations AOSP like "system-roar-arm64-ab-gapps.img.xz". 4. Samsung.zip -> There's all needed tools and files - Odin, 7-Zip ZS etc...
- Download Samsung.zip and extract the folder "Samsung" to your desktop, and extract your chosen GSI using to this folder.
- Download your stock firmware and extract the super.img.lz4 file from AP_A217XXXXXXXXXX_XXX_XXXX_REV00_XXX.tar.md5 with 7-Zip ZS.
- Now extract super.img.lz4 using 7-Zip ZS (don't use 7-zip) to Samsung folder. Rename super.img to stock_super.img.
2. Convert stock_super.img to raw_super.img:Open CMD ad use this codes:
cd C:\Users\%USERNAME%\Desktop\Samsungsimg2img.exe stock_super.img raw_super.img
Wait...
3. Extract raw_super.img:On your Samsung folder, use SHIFT key of your keyboard + right click and click at "Open Linux Shell Here", wait a little, and use this code and wait the extraction:
./lpunpack --slot=0 raw_super.img
*If the extraction is completed, verify if there's this files odm.img, system.img, vendor.img and product.img. Delete or rename system.img and product.img, then extract your GSI to Samsung folder and rename the xxx.img file to system.img.
4. Pack all the files and Flash:No math here! Just use this code on Terminal and wait (Ignore errors like "Partition system, vendor, odm will resize..." or "Invalid sparce file format at header magic...")
./lpmake --metadata-size 65536 --super-name super --metadata-slots 2 --device super:5557452800 --group main:3819597824 --partition system:readonly:3340271616:main --image system=./system.img --partition vendor:readonly:474976256:main --image vendor=./vendor.img --partition odm:readonly:4349952:main --image odm=./odm.img --sparse --output ./super.img
Wait....
Use 7-Zip to archive the super.img to .tar (super.tar) and flash it on Odin (AP) and wait the phone to boot.
Unlock your Bootloader and wipe your data using your stock recovery and quickly boot to Download Mode and flash the super.tar on Odin (AP):
Notes:I not responsible for any damage on your phone. If anything occurs, just flash your stock regional firmware through Odin.
If this tutorial did not work, you did something wrong or your phone is not supported. Don't forget to wipe your data through Recovery, it's very important.
If you want Magisk working on your A21s I recommend you to report to an issue Topjohnwu at Github.
Click to expand...
Click to collapse
I tried all of this and I even went as far as trying to literally change the filesystem UUID and the filesystem of system.img as well, I detected some issues when booting a GSI and it's that the filesystem and the filesystem UUID's had to match (filesystem had to be EXT2 for some reason), and after I did all of that, I flashed the super.img to my phone but after a few seconds of it trying to boot (10 seconds after it's past the unlocked bootloader screen) it just reboots and kicks me to fastboot mode, a friend of mine told me that if it booted to fastboot it meant that the bootloader was able to pass instructions to the OS but failed, hence why it kicked me to fastboot, and after that I tried with different GSIs and neither of them worked sadly.
Also in the attributes I'd recommend changing "readonly" to "none" so that the partitions are Read/Write from super.img, after flashing super.img, just edit the fstab file (located in "/etc/fstab" for recovery) and replace "ro" in the mount points with "rw" so that you can read and write data to them, the point of this is to make the partitions read and write so that you can edit them and install anything you'd like, and that's exactly the reason I did it.
After some time we got a modded magisk apk that does work and doesn't have the legacy device detection issue that it had before, due to the phone using dynamic partitions and using a ramdisk, Magisk would detect the device as legacy and it would use "SAR_init", something that the device doesn't needs and because the boot process fails, it reboots.
Also, before I realized that you could make the partitions inside super.img read/write, I would usually use readonly and it wouldn't work either, I'd appreciate if you could help me with this.
Wer99 said:
Easy to way to install a GSI on your Samsung A21s without installing a Virtual Linux.
NFC, Screen Cast, and USB MTP unfortunately is not working with AOSP 10 and 11. Backup all your data.
If don't want to make one, download my Pre-Rooted GSIs below and flash.
*Unlock your Bootloader and wipe your data using your stock recovery and quickly boot to Download Mode and flash the super.tar on Odin (AP):
Android 10 -> Download (MediaFire)Android 11 -> Download (MediaFire)Android 11 - AOSP 11.0 v306 -> Download (MEGA) - NEWAndroid 10 Screenshots
1. Requirements:
1. Unlock your Bootloader2. Download and Install a Linux Subsystem -> Ubuntu Subsystem -> "Tutorial How to install Linux Subsystem on Windows 10 | or search how to"3. GSI Android 10 A/B Gapps -> Download only the "arm64, A/B". I recommend releases from Treble Experimentations AOSP like "system-roar-arm64-ab-gapps.img.xz". 4. Samsung.zip -> There's all needed tools and files - Odin, 7-Zip ZS etc...
- Download Samsung.zip and extract the folder "Samsung" to your desktop, and extract your chosen GSI using to this folder.
- Download your stock firmware and extract the super.img.lz4 file from AP_A217XXXXXXXXXX_XXX_XXXX_REV00_XXX.tar.md5 with 7-Zip ZS.
- Now extract super.img.lz4 using 7-Zip ZS (don't use 7-zip) to Samsung folder. Rename super.img to stock_super.img.
2. Convert stock_super.img to raw_super.img:Open CMD ad use this codes:
cd C:\Users\%USERNAME%\Desktop\Samsungsimg2img.exe stock_super.img raw_super.img
Wait...
3. Extract raw_super.img:On your Samsung folder, use SHIFT key of your keyboard + right click and click at "Open Linux Shell Here", wait a little, and use this code and wait the extraction:
./lpunpack --slot=0 raw_super.img
*If the extraction is completed, verify if there's this files odm.img, system.img, vendor.img and product.img. Delete or rename system.img and product.img, then extract your GSI to Samsung folder and rename the xxx.img file to system.img.
4. Pack all the files and Flash:No math here! Just use this code on Terminal and wait (Ignore errors like "Partition system, vendor, odm will resize..." or "Invalid sparce file format at header magic...")
./lpmake --metadata-size 65536 --super-name super --metadata-slots 2 --device super:5557452800 --group main:3819597824 --partition system:readonly:3340271616:main --image system=./system.img --partition vendor:readonly:474976256:main --image vendor=./vendor.img --partition odm:readonly:4349952:main --image odm=./odm.img --sparse --output ./super.img
Wait....
Use 7-Zip to archive the super.img to .tar (super.tar) and flash it on Odin (AP) and wait the phone to boot.
Unlock your Bootloader and wipe your data using your stock recovery and quickly boot to Download Mode and flash the super.tar on Odin (AP):
Notes:I not responsible for any damage on your phone. If anything occurs, just flash your stock regional firmware through Odin.
If this tutorial did not work, you did something wrong or your phone is not supported. Don't forget to wipe your data through Recovery, it's very important.
If you want Magisk working on your A21s I recommend you to report to an issue Topjohnwu at Github.
Click to expand...
Click to collapse
Also, Just so you know, the recovery that we have is OrangeFox R11 which is currently an alpha build, thanks to magisk I was able to use the tool "dd" in termux to flash the recovery.img to /dev/block/by-name/recovery (aka the recovery partition) and this helped me bypass DL mode which is even worse now that I upgraded to U5 (I regret it and I tried downgrading from recovery instead of DL mode but the linux kernel itself protects the mmcblk0boot0 partition which is supposed to be the partition where the "BL" is located, and I tried flashing the sboot.bin file to that partition and it didn't work due to it being protected
Anyways back to the original topic, I don't know how but after flashing OrangeFox R11 with dd in android (I used su with magisk of course because), OrangeFox managed to boot with stock vbmeta and this build was supposedly built with A10's firmware in mind, not A11's firmware, so I have some hopes that flashing super.img from recovery might work if given the right vendor and firmware, I even flashed a vbmeta that was made for U3 from OrangeFox and it booted without any issues, oddly enough OneUI booted with that U3 vbmeta.img
LonelyCracker said:
Dear Wer99,
I Successfully Made A Non-Rooted GSI By Following Your [Tutorial / Guide],
I'm Wondering How Could I Add SuperSU & Root Permission In It
GSI : [CherishOS, AOSP10, AOSP11]
Click to expand...
Click to collapse
You don't need SuperSU anymore, There's already a fixed magisk for it, Here's the links:
[SHARING] HOW TO ROOT A21S STOCK ROM WITH MAGISK
Hello friends I just want to share how to root A21S stock rom in case anybody needs it: 1. Unlock bootloader 2. (On PC) Extract boot.img.lz4 from AP...tar file, then copy it to phone 3. (On phone) Install ZArchiver to extract boot.img from...
forum.xda-developers.com
[ROOT] Modified Magisk for Galaxy A21S (R)
It seems that the A21S hasn't had any root since it was released (other than pre-rooted GSI ROMS) When flashing Magisk, the phone went into bootloop, and the only way to fix it was to flash stock rom via Odin. After some analysis, it seems that...
forum.xda-developers.com
David112+ said:
You don't need SuperSU anymore, There's already a fixed magisk for it, Here's the links:
[SHARING] HOW TO ROOT A21S STOCK ROM WITH MAGISK
Hello friends I just want to share how to root A21S stock rom in case anybody needs it: 1. Unlock bootloader 2. (On PC) Extract boot.img.lz4 from AP...tar file, then copy it to phone 3. (On phone) Install ZArchiver to extract boot.img from...
forum.xda-developers.com
[ROOT] Modified Magisk for Galaxy A21S (R)
It seems that the A21S hasn't had any root since it was released (other than pre-rooted GSI ROMS) When flashing Magisk, the phone went into bootloop, and the only way to fix it was to flash stock rom via Odin. After some analysis, it seems that...
forum.xda-developers.com
Click to expand...
Click to collapse
Yeah I Know But I'm Just Interested In Making A Prerooted GSI
LonelyCracker said:
Yeah I Know But I'm Just Interested In Making A Prerooted GSI
Click to expand...
Click to collapse
What's the point of making a prerooted GSI with an outdated root method?
You can't even install modules with SuperSU
To David112+ :
In My Opinion, Prerooted GSI Is Way Better.
You Could See The Comparison I Made Here.
Also Making One GSI Could Gain Me Lots Of Experience.
So I Couldn't Think Of The Reason Why Not
Magisk Patched Stock [Firmware / ROM] Also Have It Own Problem,
Which You Could Find Here.
LonelyCracker said:
To David112+ :
In My Opinion, Prerooted GSI Is Way Better.
You Could See The Comparison I Made Here.
Also Making One GSI Could Gain Me Lots Of Experience.
So I Couldn't Think Of The Reason Why Not
Magisk Patched Stock [Firmware / ROM] Also Have It Own Problem,
Which You Could Find Here.
Click to expand...
Click to collapse
I don't think you've realized or checked the group of the phone but a load of people have already rooted their ROMs with Magisk and so far they have no problems, and still, everyone agrees that installing modules somewhere from the internet is the responsibility of the end user.
And I'm pretty sure that everyone agrees that magisk is the best root method, and even if you wipe data, you can just reinstall the Magisk apk to get the root prompt and finish setting it up, or better yet. use the systemizer module to systemize the magisk apk so that it's installed in system instead of data.
Making a prerooted GSI is just a waste of time, I'd rather just make normal GSI that's flashable on the phone and just install Magisk or systemize the Magisk APK.
I do agree that making a GSI flashable for the phone makes you gain a lot of experience but you're wasting your time into something that barely anyone is going to use, due to the fact that it has SuperSU which is old and outdated and most people prefer Magisk anyways because it's updated and not only that but you can pretty much install anything you'd like with the modules.
To David112+ :
Sorry To Disagree With You, I Was Trying To Acheive A Goal There .
My Goal Was To Get ADB (Android Debug Bridge) With "adb root" Working On Magisk Patched Stock [Firmware / ROM]. After Many Research & Attempt To Acheive That, I Gave Up... I Gained Some Knowledge There Too. I Know That Stock Rom Are For Production Purpose & I Can't Gain Root Access Using ADB (Android Debug Bridge).
Hopefully I Could Get Help Somewhere.
But Fun Fact Is...
I Water-Damaged My Phone
Question :
1.) Is It Possible To Make A Non Rooted GSI & Patch It With Magisk ? How ?
LonelyCracker said:
To David112+ :
Sorry To Disagree With You, I Was Trying To Acheive A Goal There .
My Goal Was To Get ADB (Android Debug Bridge) With "adb root" Working On Magisk Patched Stock [Firmware / ROM]. After Many Research & Attempt To Acheive That, I Gave Up... I Gained Some Knowledge There Too. I Know That Stock Rom Are For Production Purpose & I Can't Gain Root Access Using ADB (Android Debug Bridge).
Hopefully I Could Get Help Somewhere.
But Fun Fact Is...
I Water-Damaged My Phone
Question :
1.) Is It Possible To Make A Non Rooted GSI & Patch It With Magisk ? How ?
Click to expand...
Click to collapse
Custom ROMs should work with ADB root normally
2. To install Magisk just use the links that I shared in this post (https://forum.xda-developers.com/t/...d-gsis-for-samsung-a21s.4269227/post-84975373)
After upgrading to U5, I can't install these GSIs anymore. It bootloop all the times
To David112+ :
But Is Not Possible To Use ADB (Android Debug Bridge) On Magisk Patched Stock [Firmware / ROM]. What I Was Saying Is To Use "adb root" On Magisk Patched Stock [Firmware / ROM]
I'm Only Able To Use The Command "adb root" In Custom GSI Built By Wer99.
Not Every Custom Build GSI Are Prerooted.
Maybe You're Right Magisk Is Better Than Old Little SuperSU. But I Need "adb root" To Work With It
thatha said:
After upgrading to U5, I can't install these GSIs anymore. It bootloop all the times
Click to expand...
Click to collapse
If you have magisk with stock ROM, good news for you, I'll be working a guide in how to get a GSI installed as a magisk module, I tested this with ShapeShiftOS and I got as far as the boot animation of ShapeShiftOS, Once I was booted I checked ADB and sdcard was encrpyted and that's why it wasn't able to start correctly, it was just stuck in the google logo with a loading bar, I'm gonna try decrypting data, formatting and then installing the module
If this does work then I'll be releasing a guide in how to get a GSI of your preference working as a magisk module
Explanation: Thanks to Magisk's Magic Mount feature, I'm able to systemlessly swap the assets of OneUI with a Custom ROM's of my choosing, such as ShapeShiftOS
Edit: This idea is discarded, Because of the userdata partition being encrypted I can't use ShapeShiftOS, and even after decrypting I can't use it because OneUI gets stuck in "Starting android" when using the boot image with patched fstab and magisk
And if I download gsi android 11 through mediafire, will I have to do all this procedure? or just flash on odin? A21S ANDROID 11.
To Oroki:
These GSI Is Ready To Be Flashed.
LonelyCracker said:
To Oroki:
These GSI Is Ready To Be Flashed.
Click to expand...
Click to collapse
but will i have to do topic 2 and 3?
To Oroki :
Please Explain What Do You Mean By Topic 2 & 3
LonelyCracker said:
To Oroki :
Please Explain What Do You Mean By Topic 2 & 3
Click to expand...
Click to collapse
2. Converta stock_super.img em raw_super.img: e3. Extrato raw_super.img:
To Oroki :
Those Step You Provide Aren't Necessary Anymore
It's Patched Which Mean You Don't Have To Do Anything To It
Sorry For Late Reply
Hi,
is there any way to set selinux permissive permanently on LiR? Everything I've found and tried only works until the next reboot.
I would like to install some audio modifications, e.g. Dolby, Viper, James, etc., and I heard they require selinux permissive.
ANE-LX1 said:
Hi,
is there any way to set selinux permissive permanently on LiR? Everything I've found and tried only works until the next reboot.
I would like to install some audio modifications, e.g. Dolby, Viper, James, etc., and I heard they require selinux permissive.
Click to expand...
Click to collapse
Try to set 'permissive' using Magisk, it works similar to init.d method
(worked for me on stock EMUI, should work on LiR too):
- First of all flash in TWRP "Phenix kernel" by @TureX and wipe Dalvik/ART cache, reboot.
- open root Explorer (e.g. Solid explorer), go to directory data/adb/post-fs-data.d , create a file , rename it as selinux
- add the line
setenforce 0
in the file 'selinux' and save it.
- change the permissions of a 'selinux' file to rwxrwxrwx (777) .
- reboot.
The phone should reboot into selinux permissive.
You can change selinux status via "Termux", without reboot, if needed.
(su <enter>
setenforce 0 <enter>
or
setenforce 1 <enter>
Status:
su <enter>
getenforce <enter> ).
Maybe this will help you.
P.S.: As for installing Viper or Dolby Atmos, it's just an academic question, imo...
-Alf- said:
Try to set 'permissive' using Magisk, it works similar to init.d method
(worked for me on stock EMUI, should work on LiR too):
- First of all flash in TWRP "Phenix kernel" by @TureX and wipe Dalvik/ART cache, reboot.
- open root Explorer (e.g. Solid explorer), go to directory data/adb/post-fs-data.d , create a file , rename it as selinux
- add the line
setenforce 0
in the file 'selinux' and save it.
- change the permissions of a 'selinux' file to rwxrwxrwx (777) .
- reboot.
The phone should reboot into selinux permissive.
You can change selinux status via "Termux", without reboot, if needed.
(su <enter>
setenforce 0 <enter>
or
setenforce 1 <enter>
Status:
su <enter>
getenforce <enter> ).
Maybe this will help you.
P.S.: As for installing Viper or Dolby Atmos, it's just an academic question, imo...
Click to expand...
Click to collapse
It's a little bit complicated for me...
Thanks for your help anyway!
P.S.: what do you mean by that?
-Alf- said:
As for installing Viper or Dolby Atmos, it's just an academic question
Click to expand...
Click to collapse
ANE-LX1 said:
P.S.: what do you mean by that?
Click to expand...
Click to collapse
I mean, neither of them will work.
-Alf- said:
I mean, neither of them will work.
Click to expand...
Click to collapse
Unfortunately, you are perhaps right and it has been a vain hope. Is there really no chance to have Volte and Dolby on a custom ROM??
ANE-LX1 said:
Unfortunately, you are perhaps right and it has been a vain hope. Is there really no chance to have Volte and Dolby on a custom ROM??
Click to expand...
Click to collapse
Oreo is your friend
Hi i have installed latest android 13 stock on t220 after i make a customAP of gsi lineage 20.0 arm64-bvs-vndklite after i make a magisk patched AP and all working but when i open magisk i have this error "su file detected that does not belong to magisk,please remove other superuser programs" but magisk work perfectly
Plz how can i solve
izimen said:
Hi i have installed latest android 13 stock on t220 after i make a customAP of gsi lineage 20.0 arm64-bvs-vndklite after i make a magisk patched AP and all working but when i open magisk i have this error "su file detected that does not belong to magisk,please remove other superuser programs" but magisk work perfectly
Plz how can i solve
Click to expand...
Click to collapse
Delete
/system/xbin/su
/system/etc/init/su.rc
/system/bin/phh-su
/system/bin/phh-securize.sh
su app in /system/app/phh.superuser
Together with
*disable toggle SuperSU in phh-treble setting
yshiv666 said:
Delete
/system/xbin/su
/system/etc/init/su.rc
/system/bin/phh-su
/system/bin/phh-securize.sh
su app in /system/app/phh.superuser
Together with
*disable toggle SuperSU in phh-treble setting
Click to expand...
Click to collapse
thanks all are good now