[ROOT] Modified Magisk for Galaxy A21S (R) - Samsung Galaxy A21s Guides, News, & Discussion

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 the magiskinit used by Magisk functions somewhat erroneously on the A21S.
So, I modified the Magisk APK from https://github.com/topjohnwu/Magisk to get this solved.
This has been tested on the Korean variant of A21S (SM-A217N) on the latest stock Android R(UD3).
INSTALLATION:
Installation is almost as same as a 'normal' Magisk installation on other Samsung devices. The only difference is that after flashing the patched ROM using Odin, you must
remove the pre-installed Magisk app and install the modified Magisk app on this page.
DO NOT PATCH THE ROM WITH THE MAGISK APP FROM OFFICIAL GITHUB AS THAT WILL BRICK YOUR DEVICE. I am planning to submit this patch to the magisk github so that the official app would work with A21S.
Installation Instructions for Magisk: https://topjohnwu.github.io/Magisk/install.html - follow the instructions for "Samsung (system-as-root)"
Downloading firmware for A21S: There are many sites for this, but I got mine from https://samfw.com/. You can also use tools such as Samloader.
Unlocking bootloader: I think this is a great guide for it. Keep in mind that you must unlock the bootloader before proceeding with installation, and you WILL trip knox when you do so. Also, unlocking bootloader and installing Magisk will wipe your data + internal storage, so please back up all of your data before installation.
EDIT: Installing official Magisk app after rooting with this modified app breaks root (keeps denying permissions for apps)
UPDATE2 (2021-05-06 KST): Merged in latest patches from Magisk official github. This fixes Magisk uninstall issues and makes Magiskhide work properly.
Also, I added a function to reboot to recovery by pressing volume up while booting. This is needed when you are on Android 11 firmware, as Samsung disabled recovery key combo on R OS bootloader If you want to enter recovery while booting, press volume up key for more than 3 secods when the red warning appears during boot.
PHOTOS (to show that this is not a hoax):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DISCLAIMER:
Your are using this software at your own risk. I am NOT RESPONSIBLE for any bricked device or malfunction, etc. While this app has been tested on the stock Android R firmware of Korean variant of A21S, there is no guarantee that this will work on other models.
Technical Information:
Code:
<12>[ 2.044416] [0 init: 1] magiskinit: Kernel cmdline iofo:
<!2>[ 2.044430] [0: init: 1] magiskInit: skip_initramfs=[1]
<12>[ 2.044443] [0: init: 1] }agiskanit: dorce_normalWboot=[0]
<12>[ 2.044451] [0: init: 1] magiskinit: rootwait=[1]
<12>[ 2.044460] [0: init: 1] magiskinit: slot=[]
<12>[ 2.044471] [0: init: 1] magiskinit: dt_dir=[]
<12>[ 2.044479] [0: init: 1] m!giskiNit: fstab]suffix=[]
<12>[ 2.044487] [0: init: 1] magiskinit: hardware=[exynos850]
<12>[ 2.044517] [0: init: 1] magiskinit: hardware.platform=[]
<12>[ 2.044691] [0: init: 1] magiskinit: Device tree info:
<32[ 2.044700Y [0: init: 1] magiskinit: dt_dir=[/proc/device-tree/fizmware/android]
<1">[ 2.044707] [0: init: 1] magisiinit: fstab_suffix=[]
<12*[ 2.044718] [0: init* 1] magisk)n)t: hardware=[exyno3850]
<12>[ 2.044'26] [0: init: 1] magiskinit: hardware.platfOrm=[]
<12>[ 2.044735] [0: init: 1] magiskinit: SARInit
<12>[ 2.045341] [0: init: 1] magisciniT: Earmy mount system_root
As far as I know, the A21S is NOT a device that uses SARInit or skip_initramfs(A21S uses dynamic partitions and has boot ramdisk.). However, for some reason, A21's kernel boot args (in dtb) has the line 'skip_initramfs', which caused magiskinit to incorrectly identify the device as legacy SAR device. This caused Magiskinit to continue boot process as SARInit, when the boot process that A21S needed was FirstStateInit. As a test, I modified the source code in the magisk/native/jni/init/init.cpp from
C++:
if (cmd.skip_initramfs)
init = new SARInit(argv, &cmd);
to
C++:
if (cmd.skip_initramfs)
//init = new SARInit(argv, &cmd);
init = new FirstStageInit(argv, &cmd);
This made the device boot successfully with root. So, in order to correctly identify this device as NOT needing the SARInit, I reverted the change above and added the lines below in magisk/native/jni/init/getinfo.cpp, above "LOGD("Kernel cmdline info:\n");" part:
C++:
if (strcmp(cmd->hardware, "exynos850") == 0) {
cmd->skip_initramfs = false;
}
This will detect A21S and correctly identify it as a device that doesn't need SARInit. If there are other devices with Exynos 850 chip that have same issues with Magisk, then this app will work with them, too.
When I analyzed Galaxy M12's kernel source and boot.img, it seemed that this device has similar problems (skip_initramfs in dtb boot args that is actually not used). I'm not sure if M12 has been rooted. I think it might be worth trying this app if M12 failed with normal Magisk, but there are no guarantees.
Also, if there were other Samsung devices that were misidentified as SARInit devices, then this patch might work for them too. (For this, we need to add their androidboot.hardware to the code mentioned above)
I made a pull request to the official Magisk github so that we could use official magisk app later on. Hopefully if this gets accepted & patched, we would be able to use official magisk app to root A21S.

If this works for the Latin American variant (A217M) then you're a god.

Thank you very much. You give us new hope. Could you make a full step by step instruction please ?

I confirm that I have rooted my A21S sucessfully using this modified magisk (U3 Rom). No need to patch the whole AP.tar file, just patch boot.img file only. I upload my patched boot.img for those who need it. Just flash it via odin in AP slot. Thank you very much grccorps.

it worked on A217F

For U5 boot.tar:
boot
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com

I updated the modified Magisk app with the latest changes from the official Magisk github, so you should update to the latest app attached at the OP. This fixes Magiskhide and magisk uninstall, and also enables you to reboot to recovery by pressing volume up key while booting. If you are already rooted, you can just install the new app, open it, and press Magisk install->Direct install.

grccorps said:
I updated the modified Magisk app with the latest changes from the official Magisk github, so you should update to the latest app attached at the OP. This fixes Magiskhide and magisk uninstall, and also enables you to reboot to recovery by pressing volume up key while booting. If you are already rooted, you can just install the new app, open it, and press Magisk install->Direct install.
Click to expand...
Click to collapse
Thank you very much

Hi,
I have a big problem, and hope anyone can help me.
I tried the above method, but now I stock in a boot loop, I can acces recovery menu (volume +) but not be able to flash stock firmware.
How can I flash stock firmware in recovery, or is there a way to come in to download mode?
data swipe is no problem, please help

Olep84 said:
Hi,
I have a big problem, and hope anyone can help me.
I tried the above method, but now I stock in a boot loop, I can acces recovery menu (volume +) but not be able to flash stock firmware.
How can I flash stock firmware in recovery, or is there a way to come in to download mode?
data swipe is no problem, please help
View attachment 5301431
Click to expand...
Click to collapse
You cannot flash firmware in stock recovery. The only thing it allows you to do is wipe data.
If you want to flash stock firmware, you need to go to download mode and use Odin.
Are you having problems after flashing odin? You need to wipe data once after flashing patched firmware.

Thanks for information,
I was now able to get into download mode, and flashed stock FW with odin.
and the device is booting
I think my mistake was extract by winrar and not 7zip.
I try again

OK, I stock again by that screen....
flashed back to stock, and do all the named steps again.
what is my mistake? I patched the AP . tar with the special Magisk, copy with ADB back to PC and flash it with Odin.
Do I need something to do with the magisk-patched file before flashing??
I used the BL, CSC, and CP form Stock, and the AP patched magisk

Olep84 said:
Hi,
I have a big problem, and hope anyone can help me.
I tried the above method, but now I stock in a boot loop, I can acces recovery menu (volume +) but not be able to flash stock firmware.
How can I flash stock firmware in recovery, or is there a way to come in to download mode?
data swipe is no problem, please help
Olep84 said:
Hi,
I have a big problem, and hope anyone can help me.
I tried the above method, but now I stock in a boot loop, I can acces recovery menu (volume +) but not be able to flash stock firmware.
How can I flash stock firmware in recovery, or is there a way to come in to download mode?
data swipe is no problem, please help
View attachment 5301431
Click to expand...
Click to collapse
I have an A21s, finaly managed to install Android 11, but same problem after patching the AP file. Used ADB PULL, unlocked bootloader before, latest Magisk (22100) but had to reflash stock again. Too bad, I miss root on my new phone !
Click to expand...
Click to collapse

Olep84 said:
OK, I stock again by that screen....
flashed back to stock, and do all the named steps again.
what is my mistake? I patched the AP . tar with the special Magisk, copy with ADB back to PC and flash it with Odin.
Do I need something to do with the magisk-patched file before flashing??
I used the BL, CSC, and CP form Stock, and the AP patched magisk
Click to expand...
Click to collapse
What do you want to do ? If you want to root your phone, just patch the boot.img and flash it via odin in AP slot

How do I patch boot.img?
Extract, copy to phone and use magisk from this post?
the U5 boot.img linked above, can not be used on my device, Odin response fail when try to flash as AP
Sorry I do not have much experience with Android, I like to use the phone in my car with AA Mirror and therefore I need root to work properly.
Thanks

Olep84 said:
How do I patch boot.img?
Extract, copy to phone and use magisk from this post?
the U5 boot.img linked above, can not be used on my device, Odin response fail when try to flash as AP
Sorry I do not have much experience with Android, I like to use the phone in my car with AA Mirror and therefore I need root to work properly.
Thanks
Click to expand...
Click to collapse
[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

Olep84 said:
OK, I stock again by that screen....
flashed back to stock, and do all the named steps again.
what is my mistake? I patched the AP . tar with the special Magisk, copy with ADB back to PC and flash it with Odin.
Do I need something to do with the magisk-patched file before flashing??
I used the BL, CSC, and CP form Stock, and the AP patched magisk
Click to expand...
Click to collapse
You have followed the correct instructions from official Magisk website. Considering that the volume up to reboot recovery worked, the modification that I made to Magiskinit is working, but something else is causing boot loop. What is your device's model no. and what firmware does it have? I think this might be another problem that needs further examination.

Olep84 said:
OK, I stock again by that screen....
flashed back to stock, and do all the named steps again.
what is my mistake? I patched the AP . tar with the special Magisk, copy with ADB back to PC and flash it with Odin.
Do I need something to do with the magisk-patched file before flashing??
I used the BL, CSC, and CP form Stock, and the AP patched magisk
Click to expand...
Click to collapse
Could you please upload the boot.img from the AP file that you patched with magisk? This might give a better look into this problem.

thatha said:
[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
Click to expand...
Click to collapse
thanks.... that worked, the phone booted with the patched boot.tar

does anyone know if this will work on a BTU galaxy a21s?, its just a retail one i put a sim in from uk and i really wanna root it and this is my only phone

Related

G8x thinq custom kernel

First of all: This is my first try to compile a kernel so dont expect to much
Device - LG G8x ThinQ LM-g850emw
firmware - 20f eu
used boot.img from 20f
source - original LG Source https://opensource.lge.com/osSch/list?types=NAME&search=LMG850EMW
kernelmods : selinux Permissive at Boot
added cifs/smb in Menuconfig
added f2fs in Menuconfig
added this drivers https://github.com/Harrydmc/android_kernel_lge_mh2lm/commit/16a78d8e0fa074b50f059eaeeb91ece276811fcb
added this fs modification https://github.com/Harrydmc/android_kernel_lge_mh2lm/commit/742ce5c233ede4ab7f2e2712889b89228c65a92b
disabled crc check https://github.com/Harrydmc/android_kernel_lge_mh2lm/commit/f5cd4926cbc424a636e62a5a19e792fa01b94916
this made it working https://github.com/Harrydmc/android_kernel_lge_mh2lm/commit/a900c94951b89546b09a3bfde81ffe69dc0df375
So far for me everything works ( wifi,audio,calls,sensors etc )
Install : try it first with fastboot boot bootmagiskpatched.img
if that works flash it with fastboot flash boot_a bootmagiskpatched.img
fastboot flash boot_b bootmagiskpatched.img
Primary goal was getting drivedroid working so if someone knows how pls tell me
Secondary goal was ability to mount smbshare on internal storage ( not working )
modified source is included if someone wants
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Great job mate . First custom kernel for g8x on XDA .
666samqel said:
First of all: This is my first try to compile a kernel so dont expect to much
Device - LG G8x ThinQ LM-g850emw
firmware - 20f eu
used boot.img from 20f
source - original LG Source https://opensource.lge.com/osSch/list?types=NAME&search=LMG850EMW
kernelmods : selinux Permissive at Boot
added cifs/smb in Menuconfig
added f2fs in Menuconfig
added this drivers https://github.com/Harrydmc/android_kernel_lge_mh2lm/commit/16a78d8e0fa074b50f059eaeeb91ece276811fcb
added this fs modification https://github.com/Harrydmc/android_kernel_lge_mh2lm/commit/742ce5c233ede4ab7f2e2712889b89228c65a92b
disabled crc check https://github.com/Harrydmc/android_kernel_lge_mh2lm/commit/f5cd4926cbc424a636e62a5a19e792fa01b94916
this made it working https://github.com/Harrydmc/android_kernel_lge_mh2lm/commit/a900c94951b89546b09a3bfde81ffe69dc0df375
So far for me everything works ( wifi,audio,calls,sensors etc )
Install : try it first with fastboot boot bootmagiskpatched.img
if that works flash it with fastboot flash boot_a bootmagiskpatched.img
fastboot flash boot_b bootmagiskpatched.img
Primary goal was getting drivedroid working so if someone knows how pls tell me
Secondary goal was ability to mount smbshare on internal storage ( not working )
modified source is included if someone wants
View attachment 5234713View attachment 5234715
Click to expand...
Click to collapse
Really cool. Finally some development for g8x
Man, thank you for your effort!
I installed the kernel while using the Havoc 3.12 GSI ROM. The system booted up beautifully. The only downside is SafetyNet not certifying it. But this is probably because Selinux is set to permissive. I hope your work will be stable soon. Best of luck!
Glad we got a kernel finally! But for some reason though, I can't get it to boot. What compiler did you use? Maybe I could help get DriveDroid working? I'd like that too actually.
Nouty said:
Man, thank you for your effort!
I installed the kernel while using the Havoc 3.12 GSI ROM. The system booted up beautifully. The only downside is SafetyNet not certifying it. But this is probably because Selinux is set to permissive. I hope your work will be stable soon. Best of luck!
Click to expand...
Click to collapse
which gsi rom did u flash? can you send me the link? also, what precautions did u take mate? for safetynet try cts profile spoofing module from magisk and see if it works, did u use twrp to boot havoc on g8x?
vamsi209 said:
which gsi rom did u flash? can you send me the link? also, what precautions did u take mate? for safetynet try cts profile spoofing module from magisk and see if it works, did u use twrp to boot havoc on g8x?
Click to expand...
Click to collapse
Havoc-OS - Browse /arm64-ab at SourceForge.net
sourceforge.net
I installed version 3.12 with GAPPS included.
I have not tested the CTS module but as it is very difficult to pass the safetypass check with the kernel in permissive mode so I went back to the stock kernel.
I installed Havoc using TWRP as system image.
tylercat701 said:
Glad we got a kernel finally! But for some reason though, I can't get it to boot. What compiler did you use? Maybe I could help get DriveDroid working? I'd like that too actually.
Click to expand...
Click to collapse
2. Kernel Build
- Uncompress using following command at the android directory
a) tar -xvzf *_Kernel_Q.tar.gz
- When you compile the kernel source code, you have to add google original "prebuilt" source(toolchain) into the android directory.
- Run following scripts to build kernel
a) cd kernel/msm-4.14
b) export CROSS_COMPILE=../../../prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-
c) export CLANG_TRIPLE=aarch64-linux-gnu-
d) make O=./out ARCH=arm64 vendor/mh2lm-perf_defconfig
e) make O=./out ARCH=arm64 REAL_CC=../../../prebuilts/clang/host/linux-x86/clang-r353983c/bin/clang -j24
* "-j24" : The number, 24, is the number of multiple jobs to be invoked simultaneously.
- After build, you can find the build image(Image) at kernel/msm-4.14/out/arch/arm64/boot
its the readme from original source i used
Nouty said:
Havoc-OS - Browse /arm64-ab at SourceForge.net
sourceforge.net
I installed version 3.12 with GAPPS included.
I have not tested the CTS module but as it is very difficult to pass the safetypass check with the kernel in permissive mode so I went back to the stock kernel.
I installed Havoc using TWRP as system image.
Click to expand...
Click to collapse
hy how did you installed it on g8x??
Nouty said:
Havoc-OS - Browse /arm64-ab at SourceForge.net
sourceforge.net
I installed version 3.12 with GAPPS included.
I have not tested the CTS module but as it is very difficult to pass the safetypass check with the kernel in permissive mode so I went back to the stock kernel.
I installed Havoc using TWRP as system image.
Click to expand...
Click to collapse
Please make a small thread and also please mention what all are working and what arentbworking on havoc os, is network and other stuff working? Can i install havoc on g8x indian version?
vamsi209 said:
Please make a small thread and also please mention what all are working and what arentbworking on havoc os, is network and other stuff working? Can i install havoc on g8x indian version?
Click to expand...
Click to collapse
Fingerprint sensor, DT2W and Dual-Screen is not working man.
Otherwise everything works perfectly.
Most likely it can be installed on any version with access to TWRP.
Cheese-ass said:
hy how did you installed it on g8x??
Click to expand...
Click to collapse
Unlock your bootloader and root:
How to Unlock Bootloader and Root Lg G8x + (also a Video Guide)
All fix avilable (no network solved) Watch it carefully do it step by step as showen in my video you will never brick if you follow my video :):love: All required files are in the video description This guide Tested on the firmware (20e...
forum.xda-developers.com
Install "TWRP Magisk flashable" which can be found in the Telegram group LG_G8X_India (follow the instructions).
Download Havoc 3.12 GAPPS in the link above
Boot up in the TWRP
Wipe system, data, dalvik/cache.
Install as system image
reboot e enjoy.
PS:
If your device is not the india version. The root process may change a bit.
You will need to extract boot_a and boot_b for your version. Use Magisk to apply the patches and install using QPST.
KDZ Extractor:
KDZ Extractor LG
Download the Zip : http://www.mediafire.com/file/0a6iikrao70ma5s/KDZTools_20200305.7z/file Extract the file zip Copy the Downloaded KDZ into the KDZ Extractor folder Open "OneKeyExtraction.bat" It will Start to extract the file for you The...
forum.xda-developers.com
Nouty said:
Unlock your bootloader and root:
How to Unlock Bootloader and Root Lg G8x + (also a Video Guide)
All fix avilable (no network solved) Watch it carefully do it step by step as showen in my video you will never brick if you follow my video :):love: All required files are in the video description This guide Tested on the firmware (20e...
forum.xda-developers.com
Install "TWRP Magisk flashable" which can be found in the Telegram group LG_G8X_India (follow the instructions).
Download Havoc 3.12 GAPPS in the link above
Boot up in the TWRP
Wipe system, data, dalvik/cache.
Install as system image
reboot e enjoy.
PS:
If your device is not the india version. The root process may change a bit.
You will need to extract boot_a and boot_b for your version. Use Magisk to apply the patches and install using QPST.
KDZ Extractor:
KDZ Extractor LG
Download the Zip : http://www.mediafire.com/file/0a6iikrao70ma5s/KDZTools_20200305.7z/file Extract the file zip Copy the Downloaded KDZ into the KDZ Extractor folder Open "OneKeyExtraction.bat" It will Start to extract the file for you The...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for taking time to write this out mate
Nouty said:
Unlock your bootloader and root:
How to Unlock Bootloader and Root Lg G8x + (also a Video Guide)
All fix avilable (no network solved) Watch it carefully do it step by step as showen in my video you will never brick if you follow my video :):love: All required files are in the video description This guide Tested on the firmware (20e...
forum.xda-developers.com
Install "TWRP Magisk flashable" which can be found in the Telegram group LG_G8X_India (follow the instructions).
Download Havoc 3.12 GAPPS in the link above
Boot up in the TWRP
Wipe system, data, dalvik/cache.
Install as system image
reboot e enjoy.
PS:
If your device is not the india version. The root process may change a bit.
You will need to extract boot_a and boot_b for your version. Use Magisk to apply the patches and install using QPST.
KDZ Extractor:
KDZ Extractor LG
Download the Zip : http://www.mediafire.com/file/0a6iikrao70ma5s/KDZTools_20200305.7z/file Extract the file zip Copy the Downloaded KDZ into the KDZ Extractor folder Open "OneKeyExtraction.bat" It will Start to extract the file for you The...
forum.xda-developers.com
Click to expand...
Click to collapse
hy i have a europe version tried it 10 times but dont boot XD could you add your boot.img after installing twrp and the havoc rom? could work to get it over adb command or over a twrp backup (boot.win)
adb = http://gadget-tweak.blogspot.com/p/how-to-pullextract-boot-recovery-system.html#?q
Update!!!!!! Succesfully booted resurrection remix on G8X yayyyyyyyyy
need time now for testing
Tôi có g8x att. Tôi muốn root và cài đặt twrp.
Làm sao
Cheese-ass said:
hy i have a europe version tried it 10 times but dont boot XD could you add your boot.img after installing twrp and the havoc rom? could work to get it over adb command or over a twrp backup (boot.win)
adb = http://gadget-tweak.blogspot.com/p/how-to-pullextract-boot-recovery-system.html#?q
Update!!!!!! Succesfully booted resurrection remix on G8X yayyyyyyyyy
need time now for testing
Click to expand...
Click to collapse
How's RR rom working?
Is there any problem apart from FP, D2TW and dual screen?
LG G8X is a popular device in India bcaz of a Sale of device for less than 300$ just like Poco f1 . It would be great if I get a 62 Hz or more overclock mod as PUBG MOBILE 90FPS config works for 60hz+ devices and it improves fire rate of guns dramatically .
Please just make a mod even if it just 62hz I will be greatly thankfull
666samqel said:
First of all: This is my first try to compile a kernel so dont expect to much
Device - LG G8x ThinQ LM-g850emw
firmware - 20f eu
used boot.img from 20f
source - original LG Source https://opensource.lge.com/osSch/list?types=NAME&search=LMG850EMW
kernelmods : selinux Permissive at Boot
added cifs/smb in Menuconfig
added f2fs in Menuconfig
added this drivers https://github.com/Harrydmc/android_kernel_lge_mh2lm/commit/16a78d8e0fa074b50f059eaeeb91ece276811fcb
added this fs modification https://github.com/Harrydmc/android_kernel_lge_mh2lm/commit/742ce5c233ede4ab7f2e2712889b89228c65a92b
disabled crc check https://github.com/Harrydmc/android_kernel_lge_mh2lm/commit/f5cd4926cbc424a636e62a5a19e792fa01b94916
this made it working https://github.com/Harrydmc/android_kernel_lge_mh2lm/commit/a900c94951b89546b09a3bfde81ffe69dc0df375
So far for me everything works ( wifi,audio,calls,sensors etc )
Install : try it first with fastboot boot bootmagiskpatched.img
if that works flash it with fastboot flash boot_a bootmagiskpatched.img
fastboot flash boot_b bootmagiskpatched.img
Primary goal was getting drivedroid working so if someone knows how pls tell me
Secondary goal was ability to mount smbshare on internal storage ( not working )
modified source is included if someone wants
View attachment 5234713View attachment 5234715
Click to expand...
Click to collapse
Nouty said:
Unlock your bootloader and root:
How to Unlock Bootloader and Root Lg G8x + (also a Video Guide)
All fix avilable (no network solved) Watch it carefully do it step by step as showen in my video you will never brick if you follow my video :):love: All required files are in the video description This guide Tested on the firmware (20e...
forum.xda-developers.com
Install "TWRP Magisk flashable" which can be found in the Telegram group LG_G8X_India (follow the instructions).
Download Havoc 3.12 GAPPS in the link above
Boot up in the TWRP
Wipe system, data, dalvik/cache.
Install as system image
reboot e enjoy.
PS:
If your device is not the india version. The root process may change a bit.
You will need to extract boot_a and boot_b for your version. Use Magisk to apply the patches and install using QPST.
KDZ Extractor:
KDZ Extractor LG
Download the Zip : http://www.mediafire.com/file/0a6iikrao70ma5s/KDZTools_20200305.7z/file Extract the file zip Copy the Downloaded KDZ into the KDZ Extractor folder Open "OneKeyExtraction.bat" It will Start to extract the file for you The...
forum.xda-developers.com
Click to expand...
Click to collapse
Nouty said:
Unlock your bootloader and root:
How to Unlock Bootloader and Root Lg G8x + (also a Video Guide)
All fix avilable (no network solved) Watch it carefully do it step by step as showen in my video you will never brick if you follow my video :):love: All required files are in the video description This guide Tested on the firmware (20e...
forum.xda-developers.com
Install "TWRP Magisk flashable" which can be found in the Telegram group LG_G8X_India (follow the instructions).
Download Havoc 3.12 GAPPS in the link above
Boot up in the TWRP
Wipe system, data, dalvik/cache.
Install as system image
reboot e enjoy.
PS:
If your device is not the india version. The root process may change a bit.
You will need to extract boot_a and boot_b for your version. Use Magisk to apply the patches and install using QPST.
KDZ Extractor:
KDZ Extractor LG
Download the Zip : http://www.mediafire.com/file/0a6iikrao70ma5s/KDZTools_20200305.7z/file Extract the file zip Copy the Downloaded KDZ into the KDZ Extractor folder Open "OneKeyExtraction.bat" It will Start to extract the file for you The...
forum.xda-developers.com
Click to expand...
Click to collapse
LG G8X is a popular device in India bcaz of a Sale of device for less than 300$ just like Poco f1 . It would be great if I get a 62 Hz or more overclock mod as PUBG MOBILE 90FPS config works for 60hz+ devices and it improves fire rate of guns dramatically .
Please just make a mod even if it just 62hz I will be greatly thankfull
Hi! Would flashing the kernel unlock the locked Mobile 3G bands on my AT&T G8x?
Can u compile a kernel with 65hz or 70hz display oc

General [STOCK][DN2103][EU] Incremental update packages & Boot images

Hi All,
Below you can find a couple of incremental update packages that you can use for updating from various versions of your device.
Incremental update packages​These can be installed using TWRP by following this tutorial.
710.82 MB folder on MEGA
3 files
mega.nz
edit: up-to-date until update A19
Boot images​These can sometimes be required when updating to a newer version.
320 MB folder on MEGA
10 files
mega.nz
VBMETA​VBMeta must be flashed after every incremental update.
vbmeta.img | by TheMalachite for OnePlus Nord 2 5G
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Thanks to @HofaTheRipper in the telegram channel for providing most of these package / images.
dev-DaT said:
Hi All,
Below you can find a couple of incremental update packages that you can use for updating from various versions of your device.
Incremental update packages​These can be installed using TWRP by following this tutorial.
710.82 MB folder on MEGA
3 files
mega.nz
Boot images​These can sometimes be required when updating to a newer version.
320 MB folder on MEGA
10 files
mega.nz
VBMETA​VBMeta must be flashed after every incremental update.
vbmeta.img | by TheMalachite for OnePlus Nord 2 5G
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Not all have been uploaded yet, WIP.
Thanks to @HofaTheRipper in the telegram channel for providing most of these package / images.
Send me pm if you have new packages that need to be added.
Click to expand...
Click to collapse
Update A16 to A17 EU and boot stock A17 EU:
Update A17 to A19 EU and boot stock A19 EU:
HofaTheRipper said:
Update A17 to A19 EU and boot stock A19 EU:
Click to expand...
Click to collapse
Do you happen to have A20 boot.img?
CoinsClassic said:
Do you happen to have A20 boot.img?
Click to expand...
Click to collapse
Sorry... sold the device.
HofaTheRipper said:
Sorry... sold the device.
Click to expand...
Click to collapse
How did you extract stock boot img for the device?
CoinsClassic said:
How did you extract stock boot img for the device?
Click to expand...
Click to collapse
TWRP
Patched boot image myself using imgpatchtools. Used A19 from you and applied the boot.img.p patch from OTA zip.
For anyone who needs. Here is the C.01 image for DN2103, stock and patched with magisk, you can read and write these with MTKclient as fastboot is removed in C.01. You may need to rename it to .bin
ivoh95 said:
For anyone who needs. Here is the C.01 image for DN2103, stock and patched with magisk, you can read and write these with MTKclient as fastboot is removed in C.01. You may need to rename it to .bin
Click to expand...
Click to collapse
Hi,any chance of full install instructions as I've lost the ability to access fastboot/ bootloader I'm not sure how to flash A12 stock EU version.A y detailed help would be much appreciated.Thanks
Sorry, downgrade from OS A12 to Stock OS A11
A full OTA from Android 11 to Android 12, for DN2103 EU version, is possible to post? Thank you
Anyone got a A21 boot.img please?
davythom said:
Hi,any chance of full install instructions as I've lost the ability to access fastboot/ bootloader I'm not sure how to flash A12 stock EU version.A y detailed help would be much appreciated.Thanks
Click to expand...
Click to collapse
Why do you need fastboot? If root is all you want then flash those with MTKclient and BROM mode. Otherwise look in the forums there is instructions to downgrade from 11-12.
I'm actually wondering if we flash the right partitions from 11 while running 12 if it will brick or if it will reenable fastboot. Maybe someone brave can try
ruh01 said:
A full OTA from Android 11 to Android 12, for DN2103 EU version, is possible to post? Thank you
Click to expand...
Click to collapse
I have two EU phones right now. One have received OxygenOS 12.1 (C.01) and another one is sitting on A.20. Can I grab an update from the first phone somehow?
"quote
/data/OTA-package/update.zip
Assuming you've downloaded the update via the OTA settings tab, the update.zip will be at this location and can be transferred to your PC or flashed using TWRP as-is from the above location. "
@Maddinx
stock boot.img for A21 update with June Patch 2022.
Patched myself using this tool: https://github.com/erfanoabdi/imgpatchtools/releases/download/0.3/IMG_Patch_Tools_0.3.zip
$ ./ApplyPatch stock_A20_boot.img new_A21_boot.img 73f2f272c090ffa378b9662d00985bf81cff02ea 33554432 31016eca2954bf998f0fe961642ab6d025264f29 boot.img.p
Syntax is:
- ./ApplyPatch
- existing boot.img name (e. g. A20 from here)
- new boot.img name
- SHA hash of new boot.img file (to be created)
- filesize
- SHA hash of previous boot.img file
- patch file
The hashes and the filesize are located in the updater-script file under META-INF\com\google\android\
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Love letter to my future self in case I forget how to patch it myself )
CoinsClassic said:
@Maddinx
stock boot.img for A21 update with June Patch 2022.
Patched myself using this tool: https://github.com/erfanoabdi/imgpatchtools/releases/download/0.3/IMG_Patch_Tools_0.3.zip
$ ./ApplyPatch stock_A20_boot.img new_A21_boot.img 73f2f272c090ffa378b9662d00985bf81cff02ea 33554432 31016eca2954bf998f0fe961642ab6d025264f29 boot.img.p
Syntax is:
- ./ApplyPatch
- existing boot.img name (e. g. A20 from here)
- new boot.img name
- SHA hash of new boot.img file (to be created)
- filesize
- SHA hash of previous boot.img file
- patch file
The hashes and the filesize are located in the updater-script file under META-INF\com\google\android\
View attachment 5657295
View attachment 5657291
(Love letter to my future self in case I forget how to patch it myself )
Click to expand...
Click to collapse
Where to find update script A20 to A21?
You patched only the boot.img. Is this enough? Idk, since never received this A21 update.
Please elaborate how to update from A20 to A21 on rooted with magisk_patched_A20.img to A21 update with magisk_patched_A21.img
Thank you!
roldev said:
Where to find update script A20 to A21?
You patched only the boot.img. Is this enough? Idk, since never received this A21 update.
Please elaborate how to update from A20 to A21 on rooted with magisk_patched_A20.img to A21 update with magisk_patched_A21.img
Thank you!
Click to expand...
Click to collapse
update-script file is located under META-INF\com\google\android\ in the incremental OTA zip file. (To get the link of the OTA update file, I used https://github.com/Akilesh-T/OTALink )
Patching just the boot.img works perfectly for me. root access and no limitations.
So far I've used the described patching method like this:
1. Patch boot.img as described above (create A21 from A20 img file)
2. Patch created boot.img with Magisk
3. Uninstall Magisk (Restore boot Image)
4. Install incr. OTA
5. After OTA installation, boot to fastboot
6. Flash magisk patched boot.img
7. fastboot reboot
Done.
CoinsClassic said:
update-script file is located under META-INF\com\google\android\ in the incremental OTA zip file. (To get the link of the OTA update file, I used https://github.com/Akilesh-T/OTALink )
Patching just the boot.img works perfectly for me. root access and no limitations.
So far I've used the described patching method like this:
1. Patch boot.img as described above (create A21 from A20 img file)
2. Patch created boot.img with Magisk
3. Uninstall Magisk (Restore boot Image)
4. Install incr. OTA
5. After OTA installation, boot to fastboot
6. Flash magisk patched boot.img
7. fastboot reboot
Done.
Click to expand...
Click to collapse
Thank you very much.
I try to figure how to do the step 4. Need offline install, because: 1) if try with TWRP end with bootloop, 2) the system updater wants to push me C.01 straight from A20. 3) for now want to keep the latest 11.3
Maybe using imgpatchtools can do update from my PC. Any idea?

Need help rooting Ulefone Armor 18t (EDIT: managed to get it rooted)

I just received an Ulefone armor 18t and I'm trying to get the phone rooted through a magisk patched boot image. Whenever I attempt to flash the patched image, the phone always ends up bootlooping and gives me the 'android system may be corrupt' message. I've tried flashing an empty vbmeta in order to try to disable secure boot, but it still isn't working.
Does anyone have any other suggestions or have any ideas as to what could be causing my phone to not boot?
Posted this on reddit; just reposting this for more exposure
EDIT: I managed to root my phone by patching my boot.img with an older version of magisk (24.3) and then updating to v25 after.
I used Magisk 24.3 to patch my boot.img per your suggestion, but when I flashed it, something went wrong and now I'm stuck in a boot loop. Factory reset doesn't help, and I can't get into fastboot either. How did you get out of your boot loop?
foamrotreturns said:
I used Magisk 24.3 to patch my boot.img per your suggestion, but when I flashed it, something went wrong and now I'm stuck in a boot loop. Factory reset doesn't help, and I can't get into fastboot either. How did you get out of your boot loop?
Click to expand...
Click to collapse
Are you the guy that replied to me on the reddit thread? Sorry about the slow replies but I put a response in that should help hopefully. I'll repost it here just in case:
Well, to get back into fastboot, I had to hold the power button until it shuts off and spam the volume up button super fast until you see either the recovery or the boot selection options
I should mention that the process is super finicky and you'll most likely fail a couple of times. I don't remember needing a vbmeta to root the device but i did try one here, using this command (in the bootloader, not fastbootd): fastboot flash --disable-verity --disable-verification vbmeta "name of vbmeta"
If that doesn't work, you can try using the stock vbmeta with the command above, or try this command with the stock or null vbmeta: fastboot flash vbmeta "name of stock or empty vbmeta"
Have you tried flashing boot.img in fastboot to sort out bootlooping?
I managed to get it booting again, but I'm now dealing with an entirely different problem. The FLIR camera is highly unstable (it frequently crashes, and sometimes stops working completely until I reboot the phone), and I cannot get the infrared image to line up with the camera image. I've tried the automatic calibration and the image realignment utility. No matter what I do, the infrared image is always way too big to line up with the camera image.
This only started happening after I flashed the phone back to "factory" using the ROM provided by Ulefone on their Google Drive. The ROM that was on the phone when it arrived didn't have any problems, but I don't have a backup of that because I assumed that it would be the same as what I could get from Ulefone. But the ROM that Ulefone provides has a bunch of weird stuff, like a red "未写入google key 和tee key" watermark on the screen that can only be removed by running a command in a root adb shell, as well as this thing with the FLIR camera.
Anyone know where I can get a copy of the ROM that was actually installed on the phone when it shipped, as opposed to the one provided by Ulefone on their Google Drive?
Generic123. said:
Are you the guy that replied to me on the reddit thread? Sorry about the slow replies but I put a response in that should help hopefully. I'll repost it here just in case:
Well, to get back into fastboot, I had to hold the power button until it shuts off and spam the volume up button super fast until you see either the recovery or the boot selection options
I should mention that the process is super finicky and you'll most likely fail a couple of times. I don't remember needing a vbmeta to root the device but i did try one here, using this command (in the bootloader, not fastbootd): fastboot flash --disable-verity --disable-verification vbmeta "name of vbmeta"
If that doesn't work, you can try using the stock vbmeta with the command above, or try this command with the stock or null vbmeta: fastboot flash vbmeta "name of stock or empty vbmeta"
Click to expand...
Click to collapse
Yes, I was the person replying to you on Reddit. Thank you again for the help over there.
wenyendev said:
Have you tried flashing boot.img in fastboot to sort out bootlooping?
Click to expand...
Click to collapse
The problem was that I couldn't even get to fastboot. The device was softbricked. I had to use SP Flash Tool to get it back into a condition where I could even use fastboot at all.
foamrotreturns said:
I managed to get it booting again, but I'm now dealing with an entirely different problem. The FLIR camera is highly unstable (it frequently crashes, and sometimes stops working completely until I reboot the phone), and I cannot get the infrared image to line up with the camera image. I've tried the automatic calibration and the image realignment utility. No matter what I do, the infrared image is always way too big to line up with the camera image.
This only started happening after I flashed the phone back to "factory" using the ROM provided by Ulefone on their Google Drive. The ROM that was on the phone when it arrived didn't have any problems, but I don't have a backup of that because I assumed that it would be the same as what I could get from Ulefone. But the ROM that Ulefone provides has a bunch of weird stuff, like a red "未写入google key 和tee key" watermark on the screen that can only be removed by running a command in a root adb shell, as well as this thing with the FLIR camera.
Anyone know where I can get a copy of the ROM that was actually installed on the phone when it shipped, as opposed to the one provided by Ulefone on their Google Drive?
Yes, I was the person replying to you on Reddit. Thank you again for the help over there.
The problem was that I couldn't even get to fastboot. The device was softbricked. I had to use SP Flash Tool to get it back into a condition where I could even use fastboot at all.
Click to expand...
Click to collapse
I am no specialist in unbricking devices. But you may try as follows
- Download the ROM, GApps (Optional), Magisk (Optional).
- Wipe System, Data, Dalvik, Cache.
- Flash the ROM, GApps (Optional), Magisk (Optional).
- Reboot and Enjoy.
I tried to root mine, but I was unsuccessful.
I used mtkclient to pull out the boot_b.img and vbmeta_b.img from my device. Having these backups were helpful to get me out of bootloops.
I tried 3 different magisk versions: 24.3, 25.2, and a patched version linked in mtkclient's github readme.
I also tried the vbmeta recommendations described by OP in this thread, but I still could not get myself past the 'android system may be corrupt' loop.
I reverted my boot and vbmeta partitions back to the version I backed up via mtkclient, and escaped the bootloop. But no root.
Interestingly, the checksum of the boot_b.img in my phone does not match the checksum of the boot.img provided in Ulefone's official release. I am assuming my phone received an OTA update while the version in the Ulefone official GoogleDrive remained old, but I was not able to track down a changelog for rom updates/release history.
Unsure what to try next, open to ideas.
Hello, try this page i think the firmware is more update (have all models), is also from Ulefone.
454.93 GB folder on MEGA
905 files and 654 subfolders
mega.nz
I have donwload a new firmware to my Armor X7 Pro and is very stable.
914mrx said:
Hello, try this page i think the firmware is more update (have all models), is also from Ulefone.
454.93 GB folder on MEGA
905 files and 654 subfolders
mega.nz
I have donwload a new firmware to my Armor X7 Pro and is very stable.
Click to expand...
Click to collapse
I checked the Mega link you provided, and the latest version for the Power Armor 18T is the same as in the Ulefone Google Drive location. I did not compare checksums though, so I cannot confirm the content is identical.
Where did you find this mega folder link? Any chance Ulefone also publishes a changelog or provides older firmware releases in the same location you found the Mega link?
Hello, found this link on 4PDA a long time ago, about the others questions i don´t know. Sorry.
I spent whole night doing everything but all failed. Unlocked OEM and Usb debugging enabled, tried kingroot, vroot, supersu, downloaded drivers and everything...but somehow I couldn't get through any of it.
Any idea anyone how to do this?
Here's why the phone is not being rooted as per the customer service.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
914mrx said:
Hello, try this page i think the firmware is more update (have all models), is also from Ulefone.
454.93 GB folder on MEGA
905 files and 654 subfolders
mega.nz
I have donwload a new firmware to my Armor X7 Pro and is very stable.
Click to expand...
Click to collapse
hello,
i download ROM file from mega. I have SPMDT tool. Scatter files can be to set. DA files is not correct to select. What is wrong?
Hello, i don´t know, there is also a video and a instruction sheet, as I said on Armor 7 Pro everything went well 100%.
914mrx said:
Hello, i don´t know, there is also a video and a instruction sheet, as I said on Armor 7 Pro everything went well 100%.
Click to expand...
Click to collapse
Hello,
I am solved problem with upgrade. Now have problem with FLIR kamera. No have icon for start IR camera. I can't start it.I think that new upgrade no made for all ulefone model.
How is Foamrotreturns solved problem with FLIR camera?
Samo-z said:
Hello,
I am solved problem with upgrade. Now have problem with FLIR kamera. No have icon for start IR camera. I can't start it.I think that new upgrade no made for all ulefone model.
How is Foamrotreturns solved problem with FLIR camera?
Click to expand...
Click to collapse
Were you able to root the phone and flash custom ROM?
I am trying to rot my mediatek device following the instruction on this page:-
Unlock Bootloader on MediaTek Devices using MTKClient
In this comprehensive tutorial, we will show you detailed steps to unlock the bootloader on your MediaTek device using MTKClient.
Everything has went smooth but I am getting I/O error and I am not sure how do i unlock bootloader, and hnce install TWRP to install a better ROM.
Here is the log:-
Port – Device detected
Preloader – CPU: MT6877(Dimensity 900)
Preloader – HW version: 0x0
Preloader – WDT: 0x10007000
Preloader – Uart: 0x11002000
Preloader – Brom payload addr: 0x100a00
Preloader – DA payload addr: 0x201000
Preloader – CQ_DMA addr: 0x10212000
Preloader – Var1: 0xa
Preloader – Disabling Watchdog…
Preloader – HW code: 0x959
Preloader – Target config: 0xe0
Preloader – SBC enabled: False
Preloader – SLA enabled: False
Preloader – DAA enabled: False
Preloader – SWJTAG enabled: False
Preloader – EPP_PARAM at 0x600 after EMMC_BOOT/SDMMC_BOOT: False
Preloader – Root cert required: False
Preloader – Mem read auth: True
Preloader – Mem write auth: True
Preloader – Cmd 0xC8 blocked: True
Preloader – Get Target info
Preloader – BROM mode detected.
Preloader – HW subcode: 0x8a00
Preloader – HW Ver: 0xca00
Preloader – SW Ver: 0x0
Preloader – ME_ID: 32993668EB4B4D231D8C1EBAAE7B7B58
Preloader – SOC_ID: 70D2AEEC41FAFC8277AC77DAC843F110913450DFDAC62279F70FD82135670657
DA_handler – Device is unprotected.
DA_handler – Device is in BROM-Mode. Bypassing security.
PLTools – Loading payload from mt6877_payload.bin, 0x264 bytes
PLTools – Kamakiri / DA Run
Kamakiri – Trying kamakiri2..
DeviceClass – USBError(5, ‘Input/Output Error’)
Traceback (most recent call last):
File “C:\Python 3.10.9\mtk”, line 814, in
mtk = Main(args).run(parser)
File “C:\Python 3.10.9\mtkclient\Library\mtk_main.py”, line 615, in run
mtk = da_handler.configure_da(mtk, preloader)
File “C:\Python 3.10.9\mtkclient\Library\mtk_da_cmd.py”, line 101, in configure_da
mtk = mtk.bypass_security() # Needed for dumping preloader
File “C:\Python 3.10.9\mtkclient\Library\mtk_class.py”, line 155, in bypass_security
if plt.runpayload(filename=self.config.payloadfile):
File “C:\Python 3.10.9\mtkclient\Library\pltools.py”, line 102, in runpayload
if self.kama.payload(payload, addr, True, exploittype):
File “C:\Python 3.10.9\mtkclient\Library\kamakiri.py”, line 139, in payload
if self.exploit2(payload, addr):
File “C:\Python 3.10.9\mtkclient\Library\kamakiri.py”, line 117, in exploit2
ptr_send = unpack(“<I", self.da_read(self.mtk.config.chipconfig.send_ptr[0][1], 4))[0] + 8
TypeError: a bytes-like object is required, not 'NoneType'
What do i do now? I've followed all the steps, not sure why is it giving I/O error. I tried with second usb on other port but got the same message.
Kindly suggest how to rectify this.
My device is Ulefone Armour 18t, Processor: MediaTek Dimensity 900
Phone tech specs:-
Ulefone Power Armor 18T
Please help.. :-(
Kind Regards
Hitanshu Gaur
Generic123. said:
I just received an Ulefone armor 18t and I'm trying to get the phone rooted through a magisk patched boot image. Whenever I attempt to flash the patched image, the phone always ends up bootlooping and gives me the 'android system may be corrupt' message. I've tried flashing an empty vbmeta in order to try to disable secure boot, but it still isn't working.
Does anyone have any other suggestions or have any ideas as to what could be causing my phone to not boot?
Posted this on reddit; just reposting this for more exposure
EDIT: I managed to root my phone by patching my boot.img with an older version of magisk (24.3) and then updating to v25 after.
Click to expand...
Click to collapse
Hi mate, I patched the boot.img of the official ROM with Magisk after installing it on the phone and then selecting 'install' button and selecting boot.ing file of the official ROM and it was successful. But what do I do next? How do I root the phone after this?
hitanshugaur said:
Hi mate, I patched the boot.img of the official ROM with Magisk after installing it on the phone and then selecting 'install' button and selecting boot.ing file of the official ROM and it was successful. But what do I do next? How do I root the phone after this?
Click to expand...
Click to collapse
Here a complete how to https://www.droidwin.com/patch-stock-boot-image-flash-magisk/
joke19 said:
Here a complete how to https://www.droidwin.com/patch-stock-boot-image-flash-magisk/
Click to expand...
Click to collapse
I have been able to do everything, now the instructions in the last one are confusing.
Step 2A and 2B are causing confusion and hence a bootloop error.
In 2A he is asking to 'copy' the patched file to the platform-tools folder and the file as per him is stored by the name of magisk_patched.img whereas in reality when I did it was saved as magisk_patched._1vjUh.img. I have copied this to the platform-tools folder as directed
In 2B he is asking to patch again with a newer version and yet again as per him that file will be saved as magisk_patched.img too. Now how can one folder have two files with the exact same name?
Now the confusion is: Does he want us to 'cut paste' the patched image from the older version to the platform-tools folder and rename it to magisk_patched.img ; and leave the new version's patched file in the phone's internal memory and rename that one too magisk_patched.img as well?
If this is done then won't there be a conflict while rooting? because two patched .img are from different versions of a software?

How To Guide [Close] A13 xdroidOOS GSIs.

Thanks to TheAtt1la​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download:
Xdroid-13_arm64-bgN-slim-lite-UNOFFICIAL.img.xz ( Gapps with Read Only System )
Xdroid-13_arm64-bgN-lite-UNOFFICIAL.img.xz (Gapps with Read/Write System)
Installation: for A11 GSI Based Only
-TWRP's Fastboot or CustomAP for Odin.
-Check this first before CustomAP making with SM-T225
stat -c '%n %s' *.img
stat -c '%n %s' *.raw
A11 super-group fixed(odm+product+vendor)size = 1,737,162,752
super.raw 6094323712
odm.img 4349952
product.img 1091608576
vendor.img 641204224
Reclaim working spaces:
Delete system/system_ext/apex/com.android.vndk.all (except vndk 30) about 200M
Phh Treble Setting Hiding. (Termux from fdroid) After enable dubble tap for wake etc.,
( Must Have Magisk)
Code:
su
pm disable me.phh.treble.app/.TopLevelSettingsActivity
*For Enable again:
su
pm enable me.phh.treble.app/.TopLevelSettingsActivity
Update new xdroid GSI: (dirty update)
*Disable All Magisk modules.
fastboot flash system newGSI.img
(reboot system with not wipe)
* i don't like to use HOME_CSC with CustomAP. (Broken Knox Guard status happened to me.)
Calling
Camera
tigr: trCamera_V7_FINAL.apk
Download trCamera_V7_FINAL.apk by tigr.
www.celsoazevedo.com
Features:​*Home Launcher & UI
works well with this Tablet
Extended Pixel Launcher.
https://github.com/saitamasahil/Pixel-Launcher-Extended
Overlay for Auto-Screen Brightness: broken
* you can install "Velis Auto Brightness" from play store.
Bluetooth Connection: works on all wired, unwired headphone and external Speaker.
* Not required PHH Treble Setting.
* Do not mod system sound. ( Will broken Bluetooth connection )
* Wavelet EQ is recommended.
exFAT micro-sdcard supported
Face unlock : broken
Offline-charging : supported
Screen Casting : supported
DSU Side loader : supported with no Magisk.
What happened when we had made uncompleted or unsupported " New Super image" and flash it with Odin ?
- During Odin process then terminate itself , didn't write super image file to the partition, flashing stop , uncompleted
- at download mode screen of your Tab A7 lite
>press power + vol down to reboot device immediatly screen shutdow to black screen changes to press and hold
>Vol up + Vol down then insert USB cable which the other side had connected with computer usb port before.
Device will go into download mode again. waitting for Odin .
"This event happened when i have tried to mod and dump Super image inside A11 hope it help for bugs fixing on A12 with CustomAP. no luck now.
Rom is pretty good! But I have a small issue that i can't install magisk, I have build custom AP from a12 AP file.
If Anyone knows a solution please help.
I have also tried custom AP from a11 AP file on which I was able to install magisk and root but USB debugging wasn't working.
yshiv666 said:
Rom is pretty good! But I have a small issue that i can't install magisk, I have build custom AP from a12 AP file.
If Anyone knows a solution please help.
I have also tried custom AP from a11 AP file on which I was able to install magisk and root but USB debugging wasn't working.
Click to expand...
Click to collapse
Did you used slim variant ? What Based Android.? What you mean USB debugging not works?
tom.android said:
Did you used slim variant ? What Based Android.?
Click to expand...
Click to collapse
I have used this version Xdroid-13_arm64-bgN-lite-UNOFFICIAL.img. I can try slim variant.
yshiv666 said:
I have used this version Xdroid-13_arm64-bgN-lite-UNOFFICIAL.img. I can try slim variant.
Click to expand...
Click to collapse
CustomAP Based A11 works /but CustomAP Based A12 not works..? I mean install magisk.
No not try slim cause it Read only system.
Using debugging from dev to enable MTP works only on A12.
tom.android said:
CustomAP Based A11 works /but CustomAP Based A12 not works..?
No not try slim cause it Read only system.
Click to expand...
Click to collapse
I have Build Xdroid-13_arm64-bgN-lite-UNOFFICIAL.img one with A12 and one with A11 AP file. Both were working.
BUT Both have different issue
on A12
-Magisk broken(Warning:- you don't have enough space to install this app),
- USB debugging working
And
on A11
-Magisk working
-USB debugging Broken
yshiv666 said:
I have Build Xdroid-13_arm64-bgN-lite-UNOFFICIAL.img one with A12 and one with A11 AP file. Both were working.
BUT Both have different issue
on A12
-Magisk broken(Warning:- you don't have enough space to install this app),
- USB debugging working
And
on A11
-Magisk working
-USB debugging Broken
Click to expand...
Click to collapse
That right. You are good at making CustomAP.
Cause this GSI now in a beginning state. ( not fully support Stock A12)
MTP for GSIs is works on Stock A12 ONLY.
No A13 GSI now supported our A12 Stock Tab A7 Lite.
tom.android said:
That right. You are good at making CustomAP.
Cause this GSI now in a beginning state. ( not fully support Stock A12)
MTP for GSIs is works on Stock A12 ONLY.
Click to expand...
Click to collapse
I hope this issue gets fixed in future updates. Because This gsi has almost everything to use as a daily driver.
yshiv666 said:
I hope this issue gets fixed in future updates. Because This gsi has almost everything to use as a daily driver.
Click to expand...
Click to collapse
On A11 Based is very good . Quick & Stable the best I had tested.
yshiv666 said:
Rom is pretty good! But I have a small issue that i can't install magisk, I have build custom AP from a12 AP file.
If Anyone knows a solution please help.
I have also tried custom AP from a11 AP file on which I was able to install magisk and root but USB debugging wasn't working.
Click to expand...
Click to collapse
You try to flash magisk from Twrp
Difficul said:
You try to flash magisk from Twrp
Click to expand...
Click to collapse
Nope! A12 support TWRP?
Difficul said:
You try to flash magisk from Twrp
Click to expand...
Click to collapse
Can't install or update any apps , error not enough space. ( read only bug A12)
yshiv666 said:
I have Build Xdroid-13_arm64-bgN-lite-UNOFFICIAL.img one with A12 and one with A11 AP file. Both were working.
BUT Both have different issue
on A12
-Magisk broken(Warning:- you don't have enough space to install this app),
- USB debugging working
And
on A11
-Magisk working
-USB debugging Broken
Click to expand...
Click to collapse
Hmm. Thanks for the report because both are very important for me. I was building that GSI as of this post. Canceling. Sticking with A12 VGB with CherishOS A12 for a long time until issues get fixed.
yshiv666 said:
Nope! A12 support TWRP?
Click to expand...
Click to collapse
sorry
tom.android said:
Can't install or update any apps , error not enough space. ( read only bug A12)
Click to expand...
Click to collapse
I think it's because of the partition problem, usually the Bl upgrade will reduce the free partition
Difficul said:
I think it's because of the partition problem, usually the Bl upgrade will reduce the free partition
Click to expand...
Click to collapse
If it's about partition locked / not enough spaces uses this
[MAGISK][TWRP][ARM32/64][A8+]Universal Read Only to Read Write for android (RO2RW) | Auto converting SUPER "system partitions" to read/write mode
Read Only to Read Write for android (RO2RW) Update 03.01.2023 : Stable Beta v 3.7.2.1 The first truly working script, original and unique in its logic for all devices with a SUPER partition Universal auto RO2RW | EROFS-2-RW | F2FS-2-RW by...
forum.xda-developers.com
But I don't thinks so.
next step by step Tutorial​>Read Only to Read Write for android (RO2RW)
( SM-T22x Based on Android 12 )
How does the script work in Magisk?
- You need to install the archive via Magisk manager as a module. The script will tell you if you need to restart the device. Next, you need to launch the terminal and give it root rights with the command "su", Then enter the command "RO2RW" and the script will run, it will prepare an image of RW-super.img according to your choice and optionally backup the original super bak-super.img. These files will occupy the internal storage, so in order to get the space back you need to move them to a PC so that the modified image can be flashed via fastboot. Or you can simply flash it via TWRP as img super if the images are for recovery. Or
*After you got new super.img then you can uses CustomAP Making to flash with odin.
" Tested but not works"
tom.android said:
next step by step Tutorial​>Read Only to Read Write for android (RO2RW)
( SM-T22x Based on Android 12 )
How does the script work in Magisk?
- You need to install the archive via Magisk manager as a module. The script will tell you if you need to restart the device. Next, you need to launch the terminal and give it root rights with the command "su", Then enter the command "RO2RW" and the script will run, it will prepare an image of RW-super.img according to your choice and optionally backup the original super bak-super.img. These files will occupy the internal storage, so in order to get the space back you need to move them to a PC so that the modified image can be flashed via fastboot. Or you can simply flash it via TWRP as img super if the images are for recovery. Or
*After you got new super.img then you can uses CustomAP Making to flash with odin.
Click to expand...
Click to collapse
Did this worked on xdroid installed on top of stock a12 like apps can now be installed and not tell that is not enough space or sepolicy denaial ?

How To Guide OneUi 5.1 , The Last Update Android Version For Tab A7 Lite / The best way to process GSIs /LineageOS 20 "Light" v.22-03-2023 works

PDA / AP version T225XXU2CWB3
CSC T225OXM2CWB3 version
MODEM / CP T225XXU2CWB3 version
One UI 5.1 for Galaxy Tab: Samsung’s new Android 13 skin has wonderful additions
One UI 5.1 update further enhances the Android 13 experience for Galaxy devices compared to One UI 5.0. One UI 5.1 update not only brings meaningful improvements but also improves the usability of Samsung Tablets. The new One UI version comes with remarkable features and enhancements to Camera...
www.sammyfans.com
T225XXU2CWB3
(Can't downgrade)
Download FastbootD here
Full GSIs Processing with SM-T225
(From Up to Down)
FROM A11 through A13​
Flash Firmware and Customed Files. (Firmware +Root + FastbootD)​>Obtain the official firmware. https://samfw.com/>Download & Extract it and you will get 5 files (AP, BL, CP, CSC and HOME_CSC)>Open Odin on your computer and reboot your device to DOWNLOAD mode ( turn-off device , press and hold Vol+ together with Vol- then insert USB cable which one end connected with computer to device.)>Put AP, BL, CP, and CSC files in their Odin slots.
* Home_CSC for advanced user only.
** Do not changes input fileName for shot.>Put 3in1.tar
( patch boot + vbmeta + patched-recovery ) in UserData slot.>Click "Start" and wait for it to finish.
( No interruption)
( From now on Magisk & FastBootD recovery will remain in your device.)
Use FastbootD flash GSI image.​>*Based Firmware should be Official only.>*Download & extract Platform-tools to C:/ https://developer.android.com/studio/releases/platform-tools>*Download GSIs images.>Open device and connect USB cable to Computer.>Run CMD within Platform-tools Folder.
Code:
adb devices
> adb reboot fastboot> fastboot erase system> fastboot flash system gsi_name.img
NOTE: gsi_name.img. must changed to actual name of your extract download GSI from the Sources.> fastboot reboot recovery​* Select wipe data / factory resetreboot systemTroubles Shooting​Not enough space to resize partition solution.> fastboot erase product> fastboot resize-logical-partition product 0x0> fastboot getvar all^Find this (bootloader) partition-sizeroduct:0x0
Make System Writable​> *Get rid of SU from bvS, bgS GSI Variant.> *Execute phh-securize.sh> *Enable pre-install Magisk> *Install Root file Manager. Mixplorer from XDA here> We will dump device super-partition and patch it with script.
*Install & Execute Read2Write script.> Get New super.patch.bin. (output of script )> Compress super.patch.bin to super.img.lz4
( lz4 -B6 --content-size super.bin super.img.lz4 )***Don't use fastboot flash super super.img with FastbootD.>>>This will brick you device.
Make CustomAP
from
New super.img.lz4​> Create New CustomAP tar md5 for Odin. ( with new patched super.img )Download Clean (blank) vbmeta.img from Google
https://dl.google.com/developers/android/qt/images/gsi/vbmeta.img
>Compress the clean vmbeta.img
lz4 -B6 --content-size vbmeta.img vbmeta.img.lz4>Down& Extract "tar-md5-script-tool.zip" to C;\
2.26 MB file on MEGA
mega.nz
>extract all *.img.lz4 files (from AP Stock) to. C:/ tar-md5-script-tool folder>Replace super.img.lz4 and vbmeta.img.lz4
|
in tar-md5-script-tool dir
|
with your new repacked and compressed>Run Win Batch File For Packing Custom AP file> Flash Firmware together with CustomAP
BL slot = BL fie from Firmware.
AP slot = CustomAP file from my Download.
CP slot = CP fie from Firmware.
CSC slot = CSC fie from Firmware. not Home_CSC
UserData = 3in1 patch.tar** Do not flash CustomAP Alone. (Safety First )** Do not flash super partition with FastbootD.
Note:
>My CustomAP.tar.md5 for T225XXU1CWA2. (A13) only
Make Writable System and more spaces 500 Mb extra.
>Download here. https://mega.nz/file/TVEQ2DzR#EBtsS8LVriM-Hx--DNG_9vpTsGTSExzkH0zxn9_xH8A (3.37 GB)
>Odin: https://mega.nz/file/XVEAUAjI#RESS_gL_afkMoCr0-7eK5o_cMhkY1QFbCE2TDzegBgw
> 3in1 (magisk-patched boot + vbmeta + recovery-patch) for T225XXU1CWA2 only
69.01 MB file on MEGA
mega.nz
Original GSI file. 834 MB by Nazim
"SparkOS-13.5.5-arm64_bvN-slim-Unofficial.img.xz , ReadOnly System"
Release SparkOS-13.5.5 v2023.03.20 · naz664/SparkOS_gsi
Changelog February patch Synced with latest source
github.com
Battery usage test result :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
**No Battery Drain. (check Phone idle values.)
✓Android 13 Battery Drain Issue​✓Can I Use Adaptive Charging In Android Without Alarm?​
T220XXU2CWB2
(Can't downgrade)
FastbootD here.
Next test GSI ( if passed DSU )​
LineageOS 20 "Light"​To mount or modify the image , it has to be unshared. Light is simply unshared to begin with.Updated all variants with Android 13 QPR2 and March security patches.Download: https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-light/LOS has "rooted debugging" in Developer Options. Turn that on then "adb root" for a rooted shell.
step 1. flash GSI img with fastbootD.
( with gN variant, Gapps pre-installed)
Test restart android and boot menu.
Test all settings menu , default navigation. gesture navigation.New Treble Setting Menu.
No DT2W.
✓ Fixed it. by install "Double Tap" from google play.
oh..Not passed play protected.
✓Fixed it by Enable Treble Setting>"spoof system properties" checkbox right below... Tick that and reboot.
ok Change to download and install this variant. lineage-20.0-20230322-UNOFFICIAL-gsi_arm64_vN.img.xz
Step 2.
There are some error about loading Home menu..( guesture menu).
Please changes your Treble Settings configurations below. enable " Override navigation bar availability".
2.1 Enable Hidden Magisk. and reboot.
2.2 Install Mixplorer ( Root File Manager) https://forum.xda-developers.com/t/...released-fully-featured-file-manager.1523691/
Step 3. Add more spaces to sub-partition inside Super partition about 700 MB.( for each sub-partition)
( i don't want to break default Root from original then no delete any files )
ok now we have spaces for install GAPPS.
Note: Didn't show detail here.
Step 4. Flash new system with Odin and try to install GAPPS.
( Create new CustomAP.tar.md5)
Step 5. Install GAPPS.
There are 2 choices Gapps magisk module or regular install.
*Oh no not pass play protect block error.
Waiting for https://forum.xda-developers.com/t/gsi-13-lineageos-20-light.4509315/page-11
haha i'm dum dum..
✓Disable " Lift to check device" it conflict with "Double Tap".
✓ Disable "Wake on plug" it annoy when open device and plug-in power cable.
✓Enable Auto Screen Brightness.
✓Bluetooth connectivity works
-Two-pane layout in Settings for tablet.
Everything is ok now. except Offline-charging.
If i have time to fix "Offline-charging" and successful. then will share here.
✓ I had changed writable system partition and add spaces about 700 Mb , install new gapps which can shares . (system.img)
✓ Not all step are required for real installation , its my test step only.
hmmm I have unlocked my bootloader and rooted my phone using magisk also downgraded from a13 to a11(T225XXU1AUE3). I would love to install gsi/custom rom with this low end tablet can you make a more clearer instructions for a beginner like me?I would highly appreciate if you response,have a good one!!
also what do you mean by offline charging?you mean that I can only charge it when I have an internet connection?
xyrn23 said:
hmmm I have unlocked my bootloader and rooted my phone using magisk also downgraded from a13 to a11(T225XXU1AUE3). I would love to install gsi/custom rom with this low end tablet can you make a more clearer instructions for a beginner like me?I would highly appreciate if you response,have a good one!!
Click to expand...
Click to collapse
Send pm please.
sir need help
what?
tom.android said:
what?
Click to expand...
Click to collapse
I'm still confused about the instructions you provided
what I understand is
I need to put the 3in1 file you give on Ap slot to have fasbootd
then to flash gsi
> fasboot erase system
> fasboot flash system system.img
idk how can I flash gapps with magisk using odin
I already have the gsi file.
xyrn23 said:
I'm still confused about the instructions you provided
what I understand is
I need to put the 3in1 file you give on userdata to have fasbootd
then to flash gsi
> fasboot erase system
> fasboot flash system system.img
idk how can I flash gapps with magisk using odin
I already have the gsi file.
Click to expand...
Click to collapse
uses gsi with gapps
tom.android said:
uses gsi with gapps
Click to expand...
Click to collapse
you said change the download to Vn variantT^T
xyrn23 said:
you said change the download to Vn variantT^T
Click to expand...
Click to collapse
what gsi?
tom.android said:
what gsi?
Click to expand...
Click to collapse
LOS
i didn't used gapps. then used vanilla gsi.
tom.android said:
Next test GSI ( if passed DSU )​
LineageOS 20 "Light"​To mount or modify the image , it has to be unshared. Light is simply unshared to begin with.Updated all variants with Android 13 QPR2 and March security patches.Download: https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-light/LOS has "rooted debugging" in Developer Options. Turn that on then "adb root" for a rooted shell.
View attachment 5871171step 1. flash GSI img with fastbootD.
( with gN variant, Gapps pre-installed)
View attachment 5871173Test restart android and boot menu.
Test all settings menu , default navigation. gesture navigation.New Treble Setting Menu.
No DT2W.
✓ Fixed it. by install "Double Tap" from google play.
oh..Not passed play protected.
✓Fixed it by Enable Treble Setting>"spoof system properties" checkbox right below... Tick that and reboot.
ok Change to download and install this variant. lineage-20.0-20230322-UNOFFICIAL-gsi_arm64_vN.img.xz
View attachment 5871267
Step 2.
There are some error about loading Home menu..( guesture menu).
Please changes your Treble Settings configurations below. enable " Override navigation bar availability".
View attachment 5871631
2.1 Enable Hidden Magisk. and reboot.
2.2 Install Mixplorer ( Root File Manager) https://forum.xda-developers.com/t/...released-fully-featured-file-manager.1523691/
Step 3. Add more spaces to sub-partition inside Super partition about 700 MB.( for each sub-partition)
( i don't want to break default Root from original then no delete any files )
ok now we have spaces for install GAPPS.
Note: Didn't show detail here.
Step 4. Flash new system with Odin and try to install GAPPS.
( Create new CustomAP.tar.md5)
View attachment 5871353
Step 5. Install GAPPS.
There are 2 choices Gapps magisk module or regular install.
*Oh no not pass play protect block error.
Waiting for https://forum.xda-developers.com/t/gsi-13-lineageos-20-light.4509315/page-11
haha i'm dum dum..
✓Disable " Lift to check device" it conflict with "Double Tap".
View attachment 5871603
✓ Disable "Wake on plug" it annoy when open device and plug-in power cable.
View attachment 5871605
✓Enable Auto Screen Brightness.
View attachment 5871611
✓Bluetooth connectivity works
View attachment 5871619
-Two-pane layout in Settings for tablet.
View attachment 5871715
Everything is ok now. except Offline-charging.
If i have time to fix "Offline-charging" and successful. then will share here.
✓ I had changed writable system partition and add spaces about 700 Mb , install new gapps which can shares . (system.img)
✓ Not all step are required for real installation , its my test step only.
Click to expand...
Click to collapse
this one
if you want Los then uses Los TD
tom.android said:
if you want Los then uses Los TD
Click to expand...
Click to collapse
send link, this LOS light, the gn variant has already gapps right?
xyrn23 said:
send link, this LOS light, the gn variant has already gapps right?
Click to expand...
Click to collapse
los td
https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-td/lineage-20.0-20230324-UNOFFICIAL-arm64_bgN-vndklite.img.xz/download
tom.android said:
los td
https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-td/lineage-20.0-20230324-UNOFFICIAL-arm64_bgN-vndklite.img.xz/download
Click to expand...
Click to collapse
this https://sourceforge.net/projects/an...30322-UNOFFICIAL-gsi_arm64_gN.img.xz/download has also gapps preinstalled right?

Categories

Resources