Does anyone knows how to root lava x81?
I searched google bout it didn't help?
Phone Specs:
Mediatek MT6735
OS: Star OS based on Android 6
Kernel:3.18.19
[HELP] Please anyone help to build/port TWRP for Lava X81 MT6735 Marshmallow Arm64
:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
Any body please help us. Lava X81 16GB 3GB MT6735 SoC is a June 2016 Model. Today is 27 May 2019. Till now we don't find any custom recovery for Lava X81.
Device Vendor : Lava
Model/Version : X81
SoC Vendor : MediaTek
Soc CPU : MT6735 1.30 Ghz
CPU Cores : Quad-Core (4)
CPU Architecture : 4x ARM Cortex-a53 @ 1.30 GHz
CPU Family: Cortex-A53
CPU Clock Speed : 299 MHz - 1300 MHz (i.e., 1.3 GHz)
Machine : aarch64
ABI : arm64-v8a
Bit Version : 64-bit (Arm)
GPU Vendor : ARM
GPU Renderer : Mali-T720
GPU Clock Speed : 279 MHz - 448 MHz
RAM : 3 GB (2934 MB) LPDDR3_16GB
ROM : 16 GB
Screen Density : 320 DPI (xhdpi)
Resolution : 1280x720
Kernal Version : Linux 3.18.19 (1470576607)
Kernal Architecture : armv8l
[HELP] to build/port [TWRP] [RECOVERY] for Lava X81 MT6735 Marshmallow Arm64 ?
Android Version : 6.0
Android Version Codename : Marshmallow
Please anyone built/port TWRP for us (We are around lacks of users would got benifitted).
:good::good::good::good::good::good::good::good::good::good::good:
You don't need TWRP for rooting. Install MediaTek MT65xx USB VCOM Preloader USB Drivers. Install SP Flash Tool. Find a scatter file for your device. If you can not find it, you can create it. Load the scatter file. Read back boot.img from phone. Install the Magisk Manager app. Patch the boot.img from Magisk. On the Download Tab, flash the patched_boot.img from SP Flash Tool (IMPORTANT: uncheck all checkboxes except BOOT) You are rooted as soon as you boot from this patched_boot.img and can check it from Magisk Manager app
aIecxs said:
You don't need TWRP for rooting. Install MediaTek MT65xx USB VCOM Preloader USB Drivers. Install SP Flash Tool. Find a scatter file for your device. If you can not find it, you can create it. Load the scatter file. Read back boot.img from phone. Install the Magisk Manager app. Patch the boot.img from Magisk. On the Download Tab, flash the patched_boot.img from SP Flash Tool (IMPORTANT: uncheck all checkboxes except BOOT) You are rooted as soon as you boot from this patched_boot.img and can check it from Magisk Manager app
Click to expand...
Click to collapse
How to patch boot image with Magisk ? Anyone know
https: // www. t h e c u s t o m d r o i d .com/install-magisk-root-android-devices
aIecxs said:
https: // www. t h e c u s t o m d r o i d .com/install-magisk-root-android-devices
Click to expand...
Click to collapse
We are discussing here to root lava x81.
WIthout rooting, how to install Magisk & then how to patch boot.
Currently it is impossible without introducing A CUSTOM TWRP RECOVERY for LAVA X81
please READ my first post! then LOOK at the screen shot (second post)
https: // www. t h e c u s t o m d r o i d .com/install-magisk-root-android-devices/#Method-2-Patch-Stock-Boot-Image
aIecxs said:
https: // www. t h e c u s t o m d r o i d .com/install-magisk-root-android-devices
Click to expand...
Click to collapse
Thanks it works!
[ROOTED] Lava X81 using Magisk Manager by patching stock boot image (No TWRP)
---------------------------------------------------------
Who said this method to us ?
aIecxs, XDA Senior Member from Germany
https://forum.xda-developers.com/member.php?u=7285913
Thread Link :
https://forum.xda-developers.com/android/help/helproot-lava-x81-t3620166
Thanks alecks!!!!
------------------------------------------------------------
Youtube Video Assistance:
Video Name: How to root Android using Magisk Manager & stock boot.img
Channel : Hovatek
------------------------------------------------------------
REQUIREMENTS :
(0) Unlocked Bootloader
To unlock bootloader in Lava X81 by Fastboot mode use the command
fastboot oem unlock #unlock bootloader via fastboot mode
{{{{{ NOTE: Unlocking bootloader in Lava X81 will erase all the user data. So please take a backup before unlocking bootloader. }}}}}
(1) Stock boot.img for your phone model (its best its for your Build Number / Variant ) . You can extract from the stock rom / firmware of your device (you may check our collection at https://forum.hovatek.com/forum-89.html ) OR backup from your device using a hardware box e.g Miracle Box, CM2, Nck Box Pro etc
(2) Download Latest Magisk Manager {Currently 7.3.0 (220)}
(3) Active internet connection on your Android device
(4) A windows 10 Laptop
---------------------------------------------------------
INSTRUCTIONS :
Step 1: Patching the stock boot.img
1. Install Magisk Manager 7.3.0 (220) APK on your android device.
2. Copy the stock boot.img of Lava X81 to your phone's internal storage or SD card whereever you want (Internal Storege\Dowloads is the better option)
3. Launch Magisk Manager app and check for latest updates. After the updates you will see that Magisk Manager is up to date.
4. Then, Select (Magisk is not installed. Latest 19.3 (19300)) Install > (Install Magisk) Install > Select and Patch a File >
5. Navigate to the location of the stock boot.img you copied earlier on (select Dowloads option or in my case, I used ES File Explorer File Manager), then Select it
6. Magisk Manager should begin downloading the magisk zip file for our arm64-v8a Device platform.
7. Once download is complete, MagiskManager will automatically patch the boot file and store it under
/storage/emulated/0/Download/magisk_patched.img
(Then I renamed it as "patched_boot.img" for our convenience)
Step 2: Flashing the patched boot.img
Among a variety of options to flash, I preferred Fastboot method
(0) Connect your Lava X81 one or two times to the PC (for preinstalling drivers)
(1) Boot your Lava X81 into fastboot mode.
(2) Open platform-tools_r28.0.1-windows.zip file
(3) Simultaneously press Keyboard's Shift key and Right click on the mouse, to open PowerShell window
(4) On the PowerShell use the following codes to flash:
Starting from phone's normal usb debugging mode,
adb devices #Ensures your phone connectivity in ADB (Android Debug Interface) mode via USB Debugging
adb reboot-bootloader #Reboot your phone to Fastboot Mode from ADB
fastboot devices #Ensures your phone connectivity in Fastboot mode
fastboot getvar unlocked #To check whether the bootloader is unlocked or not. It should be unlocked to proceed further
fastboot flash boot patched_boot.img #Flash the Magisk Patched Boot image file in Fastboot Mode
fastboot reboot #Reboot to the system from exiting Fastboot Mode
(5) Congrats and check with a Root checker app for root status. While checking for root status itself pop out for root permission.
--------------------------------------------------------
Proofs and All the necessary files as a zip file - MediaFire Link
Root Lava X81 using Magisk Manager by patching stock boot image (No TWRP)
http://www.mediafire.com/file/zjb78878i52865c/Root_Lava_X81_using_Magisk_Manager_by_patching_stock_boot_image_%2528No_TWRP%2529.zip/file
---------- Post added at 05:23 PM ---------- Previous post was at 05:19 PM ----------
aIecxs said:
please READ my first post! then LOOK at the screen shot (second post)
https: // www. t h e c u s t o m d r o i d .com/install-magisk-root-android-devices/#Method-2-Patch-Stock-Boot-Image
Click to expand...
Click to collapse
[ROOTED] Lava X81 using Magisk Manager by patching stock boot image (No TWRP)
---------------------------------------------------------
Who said this method to us ?
aIecxs, XDA Senior Member from Germany
https://forum.xda-developers.com/member.php?u=7285913
Thread Link :
https://forum.xda-developers.com/android/help/helproot-lava-x81-t3620166
Thanks alecks!!!!
------------------------------------------------------------
Youtube Video Assistance:
Video Name: How to root Android using Magisk Manager & stock boot.img
Channel : Hovatek
------------------------------------------------------------
REQUIREMENTS :
(0) Unlocked Bootloader
To unlock bootloader in Lava X81 by Fastboot mode use the command
fastboot oem unlock #unlock bootloader via fastboot mode
{{{{{ NOTE: Unlocking bootloader in Lava X81 will erase all the user data. So please take a backup before unlocking bootloader. }}}}}
(1) Stock boot.img for your phone model (its best its for your Build Number / Variant ) . You can extract from the stock rom / firmware of your device (you may check our collection at https://forum.hovatek.com/forum-89.html ) OR backup from your device using a hardware box e.g Miracle Box, CM2, Nck Box Pro etc
(2) Download Latest Magisk Manager {Currently 7.3.0 (220)}
(3) Active internet connection on your Android device
(4) A windows 10 Laptop
---------------------------------------------------------
INSTRUCTIONS :
Step 1: Patching the stock boot.img
1. Install Magisk Manager 7.3.0 (220) APK on your android device.
2. Copy the stock boot.img of Lava X81 to your phone's internal storage or SD card whereever you want (Internal Storege\Dowloads is the better option)
3. Launch Magisk Manager app and check for latest updates. After the updates you will see that Magisk Manager is up to date.
4. Then, Select (Magisk is not installed. Latest 19.3 (19300)) Install > (Install Magisk) Install > Select and Patch a File >
5. Navigate to the location of the stock boot.img you copied earlier on (select Dowloads option or in my case, I used ES File Explorer File Manager), then Select it
6. Magisk Manager should begin downloading the magisk zip file for our arm64-v8a Device platform.
7. Once download is complete, MagiskManager will automatically patch the boot file and store it under
/storage/emulated/0/Download/magisk_patched.img
(Then I renamed it as "patched_boot.img" for our convenience)
Step 2: Flashing the patched boot.img
Among a variety of options to flash, I preferred Fastboot method
(0) Connect your Lava X81 one or two times to the PC (for preinstalling drivers)
(1) Boot your Lava X81 into fastboot mode.
(2) Open platform-tools_r28.0.1-windows.zip file
(3) Simultaneously press Keyboard's Shift key and Right click on the mouse, to open PowerShell window
(4) On the PowerShell use the following codes to flash:
Starting from phone's normal usb debugging mode,
adb devices #Ensures your phone connectivity in ADB (Android Debug Interface) mode via USB Debugging
adb reboot-bootloader #Reboot your phone to Fastboot Mode from ADB
fastboot devices #Ensures your phone connectivity in Fastboot mode
fastboot getvar unlocked #To check whether the bootloader is unlocked or not. It should be unlocked to proceed further
fastboot flash boot patched_boot.img #Flash the Magisk Patched Boot image file in Fastboot Mode
fastboot reboot #Reboot to the system from exiting Fastboot Mode
(5) Congrats and check with a Root checker app for root status. While checking for root status itself pop out for root permission.
--------------------------------------------------------
Proofs and All the necessary files as a zip file - MediaFire Link
Root Lava X81 using Magisk Manager by patching stock boot image (No TWRP)
http://www.mediafire.com/file/zjb78878i52865c/Root_Lava_X81_using_Magisk_Manager_by_patching_stock_boot_image_%2528No_TWRP%2529.zip/file
i have nothing todo with Magisk - all credits go to the author @topjohnwu
(and you don't need to unlock bootloader, just flash with SP Flash Tool)
Returning to oreo GUIDE
We are going to speak about Returning to oreo for Samsung J4 PLUS .
Requirements
- Any archive decompress tool .
WINDOWS : Winrar & 7zip .
LINUX : U can use shell or any archive decompress tool .
ANDROID : Zarchiver .
- Custom recovery .
- LZ4 Tool .
WINDOWS : Here .
LINUX : Package name is liblz4-tool .
ANDROID : Use termux app , pkg update ; pkg install lz4 .
- Oreo stock rom .
Code:
U CAN'T FIND IT FREE ON MOST SITES OR IT WAS DELETED FROM OTHER SITES .
BUT I FOUND THIS SITE PROVIDES STOCK ROM FOR FREE AND WITHOUT SIGN IN , BUT DOWNLOADING SPEED IS SLOW :
[URL="https://samfrew.com/"][COLOR="Red"]SITE LINK[/COLOR][/URL] .
- Patience .
Lets start steps
A - Preparing . . .
Download oreo stock rom .
Unzip stock rom zip .
Rename AP ( tar.md5 to tar ) .
Decompress AP ( system - boot - vendor) & CSC ( odm only ) tar files in a dir (eg work) . ( WINDOWS : 7ZIP )
Decompress lz4.zip in previous dir ( WINDOWS ONLY)
Open cmd ( WINDOWS ) or console ( LINUX ) or termux ( ANDROID , but if u face issue try to move files to termux home dir using com.android.documentsui app , it is in any android system ) in previous dir .
Open as root or administrator write this :
Code:
- lz4 -d system.img.ext4.lz4 --no-sparse . ( [COLOR="red"]WINDOWS : lz4.exe [/COLOR])
Then delete system lz4 compressed file .
- lz4 -d -m *.lz4
Then delete all lz4 compressed file .
Rename all img.ext4 to img .
Copy all ( system - vendor - boot - odm ) img to your phone .
B - Installing . . .
- Reboot recovery
- Wipe data , system , vendor .
- From custom recovery teriminal or adb shell , go to img saved location ( using cd command ) :
Code:
- simg2img odm.img odm.raw
- dd if=odm.raw of=/dev/block/bootdevice/by-name/odm
- Install system .
Notice : With twrp , Better to reboot recovery .
- Install boot , vendor .
- Install custom kernel . (if u want)
- Install security disable stuff :
J6+ J4+ disable encryption : here .
Disable all pie security : here .
- Install magisk .
C - Waiting until it boot . . .
- Done phone booted . :good:
Thanks
• @ashyx for Twrp & J6+ J4+ disable encryption .
• @SebaUbuntu for custom recoveries .
• me for writing this thread .
• @topjohnwu for magisk .
Indonesia region try this mirror https://drive.google.com/file/d/1lGxg2R5HJiBRWvNy1uMBKd-RJ56u49Gt/view
Credit nanda.id
Can I lock the bootloader after this?
btw thanks so much for this guide, I've always wanted to downgrade...
this phone has been flashed with unauthorized software, meh.
If you're running Pie, stay there and be happy.
blackhawk said:
If you're running Pie, stay there and be happy.
Click to expand...
Click to collapse
my touchscreen didn't work after updating to the latest one
How to fix this phone has been flashed with unauthorized software
i have not working face and fingerprint unlock..
nick D1256 said:
i have not working face and fingerprint unlock..
Click to expand...
Click to collapse
i cant register it
zawarud0 said:
this phone has been flashed with unauthorized software, meh.
Click to expand...
Click to collapse
Install medusa Kernel
Hello. I have J6+ and followed all the steps carefully but I have the problem of
"your device has been flashed with unauthorized firmware and is locked"
what can I do? I really want an Android 8 or 8.1 custom ROM
NOT PORTED BY ME
SElinux is DISABLED
DOWNLOAD : download1
TWRP : download
Changelog:
• Initial build
Bug:
VOLTE (Matikan Aplikasi Ims)
1 Flash unofficial TWRP in fastboot (fastboot flash twrp <twrp image file name>.img)
2 Not sure, but you might also have to disable dm verity,
fastboot --disable-verity --disable-verification flash vbmeta <VB META FILE>
(replace <VB META FILE> with the actual file name of vbmeta)
Remark : Download magisk from the github, after doing so download the .zip for flashing later... NEEDED, DONT SKIP
3 Boot to TWRP, (turn your phone off, after it turns off keep holding the power button and volume up button, when the phone vibrates and the boot logo shows up, stop holding the power button and hold only volume up
4 In TWRP tap on Wipe and click on format data, type yes and continue, after data is formated tap on wipe but now tap on advanced wipe, in advanced wipe , wipe cache,data,dalvik only
5 After advanced wipe, tap on install and select the ROM file
6 Also flash magisk (NEEDED DONT SKIP)
7 Reboot
Post Install:
1 Download and install magisk manager from the github
2 Download termux
3 type "su" into termux and give it root rights
4 After that type "setenforce 1" into termux, now selinux will be enabled (its disabled in the rom,but enabling it doesnt do anything, and if something bad did happen, just rebooting will undo the change and unbrick itself)
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