Patched Magisk v23 for A21s (A11/OneUI 3)
Since I've seen and tried installing Magisk via the default instructions from the legend topjohnwu himself, I noticed it does not work at all. The phone
just doesn't even boot into Android at all, and after researching I have seen that this is a very specific problem with the phone itself due to weird implementation from Samsung.
Extremely simplified, apparently there is a conflict with skip-initramfs because of System-as-Root and the A/B system partitioning introduced with Project Treble. I will still have to read more into it.
There are already patched Magisk apps/images for this phone available, but I noticed they are not really in active development (last patched Magisk was still v22), so I pulled the latest Magisk from the official repository and implemented the fix from this pull request on the official repo. They are not interested in accepting the pull request, so we'll have to do our own "Magisk" for the time being.
I will try to update this as much as possible and try to incorporate fixes, user feedback and more. This has been only tested on latest A11 and OneUI 3. I will also start working on TWRP soon.
Since the APK isn't signed yet, please uninstall Magisk Manager if present, and install this one. It will display a warning when installing, but don't worry.
Options to install:
Flash boot.tar from the ZIP in Odin on AP
Install the APK from this thread and patch your own boot image
magisk app-debug.apk working, but boot.img from
Model Number : SM-A217M
Region Code : COB
Device Version info :->>
BL version : A217MUBS5CUE2
AP version : A217MUBS5CUE2
DKXC said:
Patched Magisk v23 for A21s (A11/OneUI 3)
Since I've seen and tried installing Magisk via the default instructions from the legend topjohnwu himself, I noticed it does not work at all. The phone
just doesn't even boot into Android at all, and after researching I have seen that this is a very specific problem with the phone itself due to weird implementation from Samsung.
Extremely simplified, apparently there is a conflict with skip-initramfs because of System-as-Root and the A/B system partitioning introduced with Project Treble. I will still have to read more into it.
There are already patched Magisk apps/images for this phone available, but I noticed they are not really in active development (last patched Magisk was still v22), so I pulled the latest Magisk from the official repository and implemented the fix from this pull request on the official repo. They are not interested in accepting the pull request, so we'll have to do our own "Magisk" for the time being.
I will try to update this as much as possible and try to incorporate fixes, user feedback and more. This has been only tested on latest A11 and OneUI 3. I will also start working on TWRP soon.
Since the APK isn't signed yet, please uninstall Magisk Manager if present, and install this one. It will display a warning when installing, but don't worry.
Options to install:
Flash boot.tar from the ZIP in Odin on AP
Install the APK from this thread and patch your own boot image
Click to expand...
Click to collapse
Good job. thanks you, i wait updates
Elkingb said:
magisk app-debug.apk working, but boot.img from
Model Number : SM-A217M
Region Code : COB
Device Version info :->>
BL version : A217MUBS5CUE2
AP version : A217MUBS5CUE2
Click to expand...
Click to collapse
Forgot to mention that I used the latest DBT boot image for SM-217F/DSN. Not sure if it works for other models, but there aren't really many models anyways.
DKXC said:
Forgot to mention that I used the latest DBT boot image for SM-217F/DSN. Not sure if it works for other models, but there aren't really many models anyways.
Click to expand...
Click to collapse
For SM-217M Working full
everything is fine for the SM-217F
Im waiting for the twrp so much Good job!
To DKXC:
Hi There Expert,
I Would Recommend You To Upload Your Project To Github,
So Everyone Will Be Able To Give You Feedback
It Will Probably Help You In Developing A Better A21s Community
LonelyCracker said:
Github twrp a21s
Click to expand...
Click to collapse
Flashing this patched_magisk_v23\boot.tar ain't working.
Error displayed on the DL screen:
Only official released binaries are allowed to be flashed (BOOT)
My specs:
Loading ADB module.............OK
Starting ADB module...OK
Searching for SAMSUNG ADB device...OK
Checking device authorization...OK
Reading ADB device information...
ADB Serial Number : R58R52BFNKP
Model Name : SM-A217F
Device CodeName : A21S
Hardware : EXYNOS850 EXYNOS850
Modem Board : SHANNON318
HW Version : MP 0.500
BL version : A217FXXU5CUD6
AP version : A217FXXU5CUD6
CP version : A217FXXU5CUD4,A217FXXU5CUD4
CSC version : A217FOXM5CUD6
Android version : 11
Build date : Thu Apr 29 11:41:41 +07 2021
Country : Poland
IMEI : 35xxxxxxxx691
Serial Number : N/A
Carrier : XEO
Unlock by IMEI : Unknown
SIM State : ABSENT,ABSENT
Debug Level : 0x4f4c
CP Debug Level : N/A
Warranty VOID : 1
SIM operator : N/A
USB Settings : MTP,ADB
SamKEY Team (2017)
Installed app-debug.apk (patched Magisk) onto the phone.
Downloaded original XEO firmware.
Samfw.com_SM-A217F_XEO_A217FXXU5CUD6_fac.zip
Unzipped it.
Found AP file inside unzipped folder:
AP_A217FXXU5CUD6_CL21209953_QB39896814_REV00_user_low_ship_MULTI_CERT_meta_RKEY_OS11.tar.md5
Unpacked the AP file.
Contents:
Decoded the boot.img.lz4 file using LZ4 tool:
Copied boot.img file to the phone internal memory.
Opened Magisk and patched the boot.img file, which created magisk_patched-23001_nmETW.img in the phone Downloads folder
Copied patched file (magisk_patched-23001_nmETW.img) from the phone to my laptop - and changed its name to boot.img
Compressed it into boot.tar file using 7zip.
Restarted the phone into DOWNLOAD mode (using SamKey, or adb, or key combinantion, whatever).
Put boot.tar into AP section in ODIN.
Go to Options tab and disable "Auto Reboot", make sure "Re-Partition" is also disabled.
Aaand it fails again.
And the message in phone DL mode says:
Only official released binaries are allowed to be flashed(boot)
Perhaps vsmeta.img also needs to be included into the tar file?
No idea how to move on with this subject.
skazi.chris said:
Installed app-debug.apk (patched Magisk) onto the phone.
Downloaded original XEO firmware.
Samfw.com_SM-A217F_XEO_A217FXXU5CUD6_fac.zip
Unzipped it.
Found AP file inside unzipped folder:
AP_A217FXXU5CUD6_CL21209953_QB39896814_REV00_user_low_ship_MULTI_CERT_meta_RKEY_OS11.tar.md5
Unpacked the AP file.
Contents:
View attachment 5336407
Decoded the boot.img.lz4 file using LZ4 tool:
View attachment 5336525
Copied boot.img file to the phone internal memory.
View attachment 5336527
Opened Magisk and patched the boot.img file, which created magisk_patched-23001_nmETW.img in the phone Downloads folder
View attachment 5336541View attachment 5336543
Copied patched file (magisk_patched-23001_nmETW.img) from the phone to my laptop - and changed its name to boot.img
Compressed it into boot.tar file using 7zip.
View attachment 5336545
Restarted the phone into DOWNLOAD mode (using SamKey, or adb, or key combinantion, whatever).
Put boot.tar into AP section in ODIN.
Vá para a guia Opções e desative "Reinicialização automática", certifique-se de que "Re-Partição" também esteja desativado.
View attachment 5336551
Aaand ele falha novamente.
View attachment 5336553
E a mensagem no modo DL do telefone diz:
Apenas binários lançados oficialmente podem ser atualizados (boot)
View attachment 5336559
Talvez o vsmeta.img também precise ser incluído no arquivo tar?
Não tenho ideia de como seguir em frente com esse assunto.
Click to expand...
Click to collapse
Edit3: Use MiracleBox to pass the Prenormal you have to Checking, I had this problem on J7NXT, and I made this post to help.
Edit4: Full AP patch on Magisk, and use full patched on Odin.
First with Unlock, go to developer options and activate Unlock Bootloader, restart in download mode, Press the Vol UP button, if reset only, do it again, Download->VolUP Mode, until formatting, In download mode, with all Unlock, go to Odin. Now with the Magisk patched file modified for the A21s, the entire Magisk .tar, you don't need to unpack boot.img.lz4, After this it is normal to start, it will give you an unlocked system alert, just press the Power button to continue, then an Unofficial System warning will appear and just wait A few seconds it starts normally (first boot takes considerable time)
Some tips:
-With V23 use LsPosed to use Xposed framework, Edxposed has infinite log bugs, which causes conflict and slowdown.
-For SatefyNet, Use MagiskHide only apps needed to avoid unnecessary processes, install Universal SatefyNet Fix module, Only this gets through SafetyNet, you don't need to install additional modules for SafetyNet, it will just slow down the system.
For those who use Lucky Patcher:
-Use in LsPosed, and activate it for System Framework and Play Store, you don't need to activate for each app, it will only slow down. Use CorePatch to go through the signatures as Lucky Patcher cannot do this function on Android 11. Use Lucky Patcher with LsPosed as LP Patch's are not compatible with Android 11 But LSPOSED does, so it can work just fine.
For those who use Game Guardian:
-It is best to use a Virtual System, as its functions on Android 11 are limited as it is not 100% compatible.
All I have from my own experience is:
-Avoid redundant modules as much as possible, as they can affect the battery and the System.
To skazi.chris :
Try Unchecking Re-Partition
Jukmisael said:
Edit3: Use MiracleBox to pass the Prenormal you have to Checking, I had this problem on J7NXT, and I made this post to help.
Edit4: Full AP patch on Magisk, and use full patched on Odin.
First with Unlock, go to developer options and activate Unlock Bootloader, restart in download mode, Press the Vol UP button, if reset only, do it again, Download->VolUP Mode, until formatting, In download mode, with all Unlock, go to Odin. Now with the Magisk patched file modified for the A21s, the entire Magisk .tar, you don't need to unpack boot.img.lz4, After this it is normal to start, it will give you an unlocked system alert, just press the Power button to continue, then an Unofficial System warning will appear and just wait A few seconds it starts normally (first boot takes considerable time)
Some tips:
-With V23 use LsPosed to use Xposed framework, Edxposed has infinite log bugs, which causes conflict and slowdown.
-For SatefyNet, Use MagiskHide only apps needed to avoid unnecessary processes, install Universal SatefyNet Fix module, Only this gets through SafetyNet, you don't need to install additional modules for SafetyNet, it will just slow down the system.
For those who use Lucky Patcher:
-Use in LsPosed, and activate it for System Framework and Play Store, you don't need to activate for each app, it will only slow down. Use CorePatch to go through the signatures as Lucky Patcher cannot do this function on Android 11. Use Lucky Patcher with LsPosed as LP Patch's are not compatible with Android 11 But LSPOSED does, so it can work just fine.
For those who use Game Guardian:
-It is best to use a Virtual System, as its functions on Android 11 are limited as it is not 100% compatible.
All I have from my own experience is:
-Avoid redundant modules as much as possible, as they can affect the battery and the System.
Click to expand...
Click to collapse
Patching the entire TAR with patched Magisk did the trick. Thank you very much!
Did this solution also work on the latest SW update?
I tried all, but Stuck at ODIN prism.img
when I use the Magisk tutorial
How to Root Samsung Galaxy A21s using Magisk (Android 11)
Samsung Galaxy A21s is a budget smartphone with great features and decent performance. But there are some limits to what the phone can do without rooting
magiskapp.com
i get the error Only official released binaries are allowed to be flasehd (boot)
Relock/Unlock Bootloader is necessary, then it work with patching the complete AP file
thanks for the tips
DKXC said:
Patched Magisk v23 for A21s (A11/OneUI 3)
Since I've seen and tried installing Magisk via the default instructions from the legend topjohnwu himself, I noticed it does not work at all. The phone
just doesn't even boot into Android at all, and after researching I have seen that this is a very specific problem with the phone itself due to weird implementation from Samsung.
Extremely simplified, apparently there is a conflict with skip-initramfs because of System-as-Root and the A/B system partitioning introduced with Project Treble. I will still have to read more into it.
There are already patched Magisk apps/images for this phone available, but I noticed they are not really in active development (last patched Magisk was still v22), so I pulled the latest Magisk from the official repository and implemented the fix from this pull request on the official repo. They are not interested in accepting the pull request, so we'll have to do our own "Magisk" for the time being.
I will try to update this as much as possible and try to incorporate fixes, user feedback and more. This has been only tested on latest A11 and OneUI 3. I will also start working on TWRP soon.
Since the APK isn't signed yet, please uninstall Magisk Manager if present, and install this one. It will display a warning when installing, but don't worry.
Options to install:
Flash boot.tar from the ZIP in Odin on AP
Install the APK from this thread and patch your own boot image
Click to expand...
Click to collapse
Haha thank you so much bro it worked for M12 too I took the apk file and flashed
Olep84 said:
Did this solution also work on the latest SW update?
I tried all, but Stuck at ODIN prism.img
when I use the Magisk tutorial
How to Root Samsung Galaxy A21s using Magisk (Android 11)
Samsung Galaxy A21s is a budget smartphone with great features and decent performance. But there are some limits to what the phone can do without rooting
magiskapp.com
i get the error Only official released binaries are allowed to be flasehd (boot)
Relock/Unlock Bootloader is necessary, then it work with patching the complete AP file
thanks for the tips
Click to expand...
Click to collapse
Are you sure you unlock Bootloader?
[How To] Unlock Bootloader
How To Unlock Bootloader A21s. *** Disclaimer I am not responsible for any damage you made to your device You have been warned - Go to Settings -> About phone and find your build number. - Tap on your build number 6 times until you see...
forum.xda-developers.com
====#####=======
In relation to the topic, I think that this one will also be abandoned. Eagerly waiting for a developer to look at the A21S/M12 to finally get Magisk working without a patch
Olep84 said:
Did this solution also work on the latest SW update?
I tried all, but Stuck at ODIN prism.img
when I use the Magisk tutorial
How to Root Samsung Galaxy A21s using Magisk (Android 11)
Samsung Galaxy A21s is a budget smartphone with great features and decent performance. But there are some limits to what the phone can do without rooting
magiskapp.com
i get the error Only official released binaries are allowed to be flasehd (boot)
Relock/Unlock Bootloader is necessary, then it work with patching the complete AP file
thanks for the tips
Click to expand...
Click to collapse
Have you used the patched magisk or official one; see official one doesn't work on a21s and m12 i was getting that error before but it solved by using patched one see the first post and download the .apk
I have the SM-A215U. I get the impression this method won't work for me.
I have Developers Options, but do NOT have the OEM option in that menu.
Is there anyway to unlock it without that menu item?
dbreed53 said:
I have the SM-A215U. I get the impression this method won't work for me.
I have Developers Options, but do NOT have the OEM option in that menu.
Is there anyway to unlock it without that menu item?
Click to expand...
Click to collapse
No idea
Related
Here's how to root the Pixel 3 running on official and stock Android 10 release, step by step :
(not tested on Pixel 3 XL but it might work the same, just use the right firmware for your device)
What do you need :
> Pixel 3 phone with Android 10
> Unlocked bootloader on your Pixel device
> Latest ADB and FASTBOOT tools on your computer
1 ) Download the latest Android 10 factory image for your device ("Blueline" is the regular Pixel 3) :
Link > Android 10 factory image
2 ) Extract the "boot.img" file on your phone
3 ) Download latest Magisk Manager application on your phone and install it :
Link > https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
4 )Press on the Install Magisk button (the one on the top, not the Magisk Manager), then Install > Select and Patch a File and now select the Boot.img file you extracted earlier. When the process is done, just put the patched boot.img file on your computer in the same folder as your ADB and FASTBOOT tools, the file's name is magisk_patched
5 ) Enable adb debugging on your Pixel phone and connect it to your computer via USB.
Open a command prompt on your computer and migrate to the folder where the ADB and Fastboot tools are located.
(for exemple, for me it's : cd C:\\adb).
7 ) Reboot your phone to fastboot by typing adb reboot bootloader
8 ) Flash the Boot.img you just patched with magisk by typing fastboot flash boot magisk_patched.img
9 ) When i'ts done, reboot by typing fastboot reboot
10 ) Open your Magisk Manager app and chek if everything is good, and it should be ! You can now install Adaway after you enable Systemless root in the Magisk settings and rebooting your phone.
Note that this guide is actually for using adaway. I don't know if it will work for any other root related feature on your phone.
Great guide, thanks!
ibolito said:
11 ) Open your Magisk Manager app and chek if everything is good, and it should be ! You can now install Adaway after you enable Systemless root in the Magisk settings.
Click to expand...
Click to collapse
I would just add not to forget to reboot again after enabling Systemless hosts in the Magisk settings and before installing Adaway (or after installing any other module)
bafforosso said:
Great guide, thanks!
I would just add not to forget to reboot again after enabling Systemless hosts in the Magisk settings and before installing Adaway (or after installing any other module)
Click to expand...
Click to collapse
Thanks its done!
I get a "This site can't be reached" message when I click the link for magisk manager in step 3. Not sure if anyone else sees it.
Thank you for making this guide!
Thanks, works perfectly!
I think my boot.img was not patched successfully. The original file has 64 mb while the patched one has only 30 mb. I've already pdated to Android 10. When I try to path the boot.img I get the following error: FAILED (remote: Not allowed to flash (bootb))
Could anyone please send me his patched boot.img?
Oberbergler said:
I think my boot.img was not patched successfully. The original file has 64 mb while the patched one has only 30 mb. I've already pdated to Android 10. When I try to path the boot.img I get the following error: FAILED (remote: Not allowed to flash (bootb))
Could anyone please send me his patched boot.img?
Click to expand...
Click to collapse
Don't worry the new patched boot.img is 30mb, that's absolutely normal. Make sure you have unlocked your bootloader and that your phone's firmware matches the one you used to extract the boot.img. And also make sure your files are all in the same folder (adb and fastboot files + patched boot.img) and, most important of all, check if your platform tools (adb and fastboot) are up to date, then tell us if you managed to make it work.
If I updated via ota adb side load to 10. But used the boot.img from the factory image, would this explain why it did boot, however not one app would start. The system ui would then crash. Just trying to figure out where I screwed up. Thank you.
ibolito said:
Don't worry the new patched boot.img is 30mb, that's absolutely normal. Make sure you have unlocked your bootloader and that your phone's firmware matches the one you used to extract the boot.img. And also make sure your files are all in the same folder (adb and fastboot files + patched boot.img) and, most important of all, check if your platform tools (adb and fastboot) are up to date, then tell us if you managed to make it work.
Click to expand...
Click to collapse
Thanks man Everything was right but I forgot to update adb and fastboot. Now I have root
ignore me -- im idiot.
i am not sure if my pixel 3 is really rooted. all the apps requiring root says they are granted root access, but, for example, i cannot modify system files with a root file manager at all unlike i could with android 9. how can i confirm it is surely rooted?
So I have a problem, maybe someone can help me with.
Back in March I made the following post:
"I was running on the original September Update since I got the phone, I used this guide when I first rooted https://www.xda-developers.com/googl...r-root-magisk/
Today I decided it was time to update so I used this guide https://www.xda-developers.com/flash...-google-pixel/
Then I wanted to reroot my phone. So I bootet the TWRP image and flashed the magisk 18.1 zip. But after that I softbricked my phone and it wouldn't boot anymore.
So in my panic I flashed the TWRP zip and my phone worked again, but now everytime I try to flash the magsik zip the same thing happens, bootloop and back to flashing twrp.zip. "
After that didn't work, I tried flashing the magisk uninstaller, through twrp, but it exited with "Error 1" everytime. (Running TWRP 3.3.0)
So i decided to give up, because I had some personal stuff to take care of, but after Android 10 came out yesterday, I decided to give this another go.
I flashed the factory image without "-w" and everything is working fine. So today I followed this guide, double checked everything but after I flash the patched boot image I get stuck with a bootloop again... I can flash back the original boot image and everything works so it's not a huge deal, but right now I can't use google pay, because it says I'm rooted.
Any idea what I could do? Can't run the uninstaller and can't reroot... ???
thanks!
Have you checked if your patched boot.img matches the firmware on your phone?
Well it's the same one I used to flash the firmware.
I flashed yesterday without an issue and today I loaded that boot.img onto my phone, used the canary magisk manager to patch it and then transfered it back to my PC to flash it.
Edit: I'm thinking this might have to do with the fact that I couldn't uninstall magisk before.
I went back to Pie because Viper4Android doesn't work on 10. No matter what version. The Legacy version I usually use keeps asking me to install the driver like it had on previous phones when installs were borked.
GohanBurner said:
I went back to Pie because Viper4Android doesn't work on 10. No matter what version. The Legacy version I usually use keeps asking me to install the driver like it had on previous phones when installs were borked.
Click to expand...
Click to collapse
I had it working before I bodged a magisk module install
No luck here. The steps SEEM to work perfectly. Flashed the modified boot image, booted up fine, but magisk says it's still not installed. No root.
- Latest magisk canary
- Used the same firmware
- No errors anywhere along the way
Hey Mac users, I had to use the command fastboot flash boot_b magisk_patched.img
To get the patched image over to my phone. It worked out great. I was able to reboot,
and see the root in Magisk Manager.
YMMV
Thanks, worked like a charm on Linux with latest platform-tools! I thought I'd have to wait a lot longer to get root back on my device.
I have also tried this multiple times. No errors, but I can't edit system files or add modules.
Hi,
I'm trying to root the tablet. Unfortunately so far without success. I have tried several rooting tools (Desktop and Tablet App).
What promised most success is Magisk. It is also known that it works with Android 9. I copied the bootimage on the tablet from the stock-ROM, patched the image with the latest Magisk-APP (7.5.1) (Magisk 20.3 (20300)). Then back to the PC, and with fastboot written to the boot partition. After unlock the partition, this was possible. After a restart, however, the tablet will remain on the boot logo. Original stock-ROM on it again, tablet runs again (no boot loop).
Then I looked at the image sizes. The original is 16,385 kB. However, the patched Magisk file is only 7,148 kB. That can't really be, can it?
Does anyone have an idea of what this can be, or what I'm wrong about?
Thank you for your help.
hw-schrauber said:
Hi,
I'm trying to root the tablet. Unfortunately so far without success. I have tried several rooting tools (Desktop and Tablet App).
What promised most success is Magisk. It is also known that it works with Android 9. I copied the bootimage on the tablet from the stock-ROM, patched the image with the latest Magisk-APP (7.5.1) (Magisk 20.3 (20300)). Then back to the PC, and with fastboot written to the boot partition. After unlock the partition, this was possible. After a restart, however, the tablet will remain on the boot logo. Original stock-ROM on it again, tablet runs again (no boot loop).
Then I looked at the image sizes. The original is 16,385 kB. However, the patched Magisk file is only 7,148 kB. That can't really be, can it?
Does anyone have an idea of what this can be, or what I'm wrong about?
Thank you for your help.
Click to expand...
Click to collapse
Seems like Magisk Manager is not able to patch the boot.img properly.
The size of patched image is never lesser than the original boot image.
Try patching your boot image using an older version of Magisk Manager.
HIT THANKS IF FOUND USEFUL
Augustoandro said:
Seems like Magisk Manager is not able to patch the boot.img properly.
The size of patched image is never lesser than the original boot image.
Try patching your boot image using an older version of Magisk Manager.
HIT THANKS IF FOUND USEFUL
Click to expand...
Click to collapse
Thank you Augustoandro, but unfortunately I can't use an older version. Since I want to run my device with magic, I only have to install the apk. If I take an older one here, I will only get to the patch buttons when the app is updated.
So this proposal does not help.
Perhaps it is also because the 7305F does not seem to have the partitions set up as usual. If I want to make a BackUp using the tool "MTKdroidTools 2.5.3" (screenshot), it means that the partition structure does not fit and no backup is possible. A root with the tool is also not possible.
Is there another idea?
For more information:
CPU MT8321 (32bit), Memory 1/16GB, kernel 4.9.117+ (#25.10.2019)
I was able to patch the file with magisk and flash the
boot, but no root. Were you able to find a solution to your problem?
macgajos said:
I was able to patch the file with magisk and flash the
boot, but no root. Were you able to find a solution to your problem?
Click to expand...
Click to collapse
You have to root by means of Magisk: Magisk itself doesn't root the Android.
jwoegerbauer said:
You have to root by means of Magisk: Magisk itself doesn't root the Android.
Click to expand...
Click to collapse
Thank you for your reply. Sorry for not being clear here: I get "Magisk is not installed" info in magisk manager after flashing the magisk patched boot img in fastboot mode.
I have found the way to install MAGISK. You have to install MAGISK to the recovery.img. Then start in Recovery-mode and the system will boot to the normal System with installed MAGISK. Works perfect to me.
Some more information. There is an update named TB-7305F_100049_200508_ROW. After you have update to this release, you haven't MAGISK installed and you are not able to reinstall MAGISK. Also, when you get the original recovery from the version it is not possible. As well, I have tested to use the working recovery from the prerelease with the newest release, this also don't possible. For me the only working release is the TB-7305F_100043_200223.
If someone flash a later version that woks, please let know here!
hw-schrauber said:
I have found the way to install MAGISK. You have to install MAGISK to the recovery.img. Then start in Recovery-mode and the system will boot to the normal System with installed MAGISK. Works perfect to me.
Some more information. There is an update named TB-7305F_100049_200508_ROW. After you have update to this release, you haven't MAGISK installed and you are not able to reinstall MAGISK. Also, when you get the original recovery from the version it is not possible. As well, I have tested to use the working recovery from the prerelease with the newest release, this also don't possible. For me the only working release is the TB-7305F_100043_200223.
If someone flash a later version that woks, please let know here!
Click to expand...
Click to collapse
Yes, recovery is the way to go. I have figured it after reading this:
topjohnwu - install.html#boot-image-patching
As I have X model, TB-7305X_S100043_200224_ROW and TB_7305X_S100062_200610_ROW was the ROM that worked. Cool thing is that you can get roms from lenovo with "Rescue and smart assistant" app.
The trick that makes magisk rooted all the time is to choose 'reset phone' after rooting. This would cause the tablet to start with root each time.
macgajos said:
Yes, recovery is the way to go. I have figured it after reading this:
topjohnwu - install.html#boot-image-patching
As I have X model, TB-7305X_S100043_200224_ROW and TB_7305X_S100062_200610_ROW was the ROM that worked. Cool thing is that you can get roms from lenovo with "Rescue and smart assistant" app.
The trick that makes magisk rooted all the time is to choose 'reset phone' after rooting. This would cause the tablet to start with root each time.
Click to expand...
Click to collapse
What do you mean with reset? When MAGISK is in recovery, the only way to start is in the recovery-mode. Then you have ever MAGISK working when it is installed!?!
Today I have seen, that there is a new version for the "F" model. TB_7305F_S100055_200703_ROW. I will test and report!
How do I pull the Recovery.img from this tablet in the first place? Please help. Thanks.
Hi. I am trying to manage root without twrp for a couple of days. I picked up the solution with recovery.
I've tried to flash root to recovery with magisk patched recovery.img via fastboot. But the .img size is to large (is texted in fastboot). By the way i was curious after magisk patching cause the patched .img file has the same size as the original .img file. I downloaded twrp port tool and ported recovery.img and got a recovery.img with a smaller size so i was able to flash it via fastboot. Fastboot flash recovery recovery.img
Fastboot reboot.
Device is booting to Lenovo splash screen with the warning that the device is unlocked and boot in 5s. Could wait forever. After 2min pushed vol+, Lenovo Banner starts to flip and it booted to system.
But no root.
Reboot.
Boot with key combo
Hold Vol+ and power, released as lenovo splash with the warning appears. Nothing happend.
Pushed vol+. Nothing happened. It stuck at splash.
After that i could not boot the device with power key anymore. It stays at splash every time i rebooted.I had to reboot to recovery and do rebooting to system from recovery.
From bootloader i was able to boot to system also.
I like to flash magisk patched boot.img via fastboot but magisk doesn't make the .img file smaller.
I tried with sp flash tool but after patching the img is not signed anymore soflash tool doesn't flash it.
So that is my state for now.
_
_
Hi all,
I want to remove all of the google apps from my tablet 7305F in a bid to save ram, adb does most of the trick. can even uninstall play store, but the google play services com.google.android.gms is very hard to disable, keeps popping a "play services has stopped" message frequently.
till now I was able to free upto 50 % ram using this trick only its annoying that the play services message keeps popping.
PART HO said:
Hi all,
I want to remove all of the google apps from my tablet 7305F in a bid to save ram, adb does most of the trick. can even uninstall play store, but the google play services com.google.android.gms is very hard to disable, keeps popping a "play services has stopped" message frequently.
till now I was able to free upto 50 % ram using this trick only its annoying that the play services message keeps popping.
Click to expand...
Click to collapse
.....Install twrp and root rights, it's not difficult. You can then do whatever is needed
I rooted my Lenovo M7 (TB-7305X) the folling way
On a PC Get and Install LMSA "Lenovo Rescue and Smart Assistan"
* Using LMSA do a recovery, this way you are sure you have al the drivers working and that you have a correct rom
On the Tabled enabled developer mode
* enable remote debugging
* enable oem unlocking
Unlock the bootloader using fastboot
(you will find adb and fastboot in the location where LMSA was installed)
P.S. this will erase of data on your tablet
* adb reboot-bootloader
* fastboot flashing unlock
* fastboot reboot
PS tablet well be in orange state (because the bootloader is unlocked)
* android boots
On the tablet create a rooted boot.img using magisk
* download and install the latest magisk.apk
* look for boot.img (boot.img_verified) the ROW downloaded by LMSA (some where in c:\programdata)
* uplad the boot.img to the tablet
* start magisk and patch the boot.img file
* download the patched boot.img
On the PC start MTK_Flash tool
P.S. this will erase of data on your tablet
* open the download tab
* the download agent should be set by default (MTK_AllInOne_DA.bin)
* select the scater file (from the LMSA rom directory)
* deselct all files except BOOTIMG
* change the location of the BOOTIMG and select the pached boot.img
Flash boot.img by clicking download
Rooting instructions for TB_7305X (Should be the same for TB_7305F using TB-7305X_S100043_200223_ROW)
Install Rescue and Smart Assistant from Lenovo
Start Rescue and download latest ROM
Replace the latest ROM files from C:\ProgramData\RSA\Download\RomFiles\TB_7305X_S1000xx_xxxxxx_ROW with the ones from TB-7305X_S100043_200224_ROW
Can be downloaded from:
https://mirrors.lolinet.com/firmware/lenovo/Tab_M7/TB-7305X/
Rescue the device as per the RSA instructions
Install latest Magisk
Upload recovery-verified.img from the TB-7305X_S100043_200224_ROW ROM to the Internal Shared Storage of the device in Download directory
Run Magisk Manager
Patch the recovery-verified.img with magisk
Copy the newly created magisk_patched-xxxxxxxx.img file in Downloads to C:\Program Files (x86)\Rescue and Smart Assistant and rename to magisk_patched.img
It will later be used to flash the device after unlocking
Enable developer mode on the device
From developer options enable:
OEM Unlocking (needs Internet connection)
USB Debugging
Start cmd and navigate to C:\Program Files (x86)\Rescue and Smart Assistant directory
adb reboot bootloader
Wait for reboot. You will see “=> FASTBOOT mode …” message when ready
fastboot.exe flashing unlock
Press volume up key to confirm
fastboot flash recovery magisk_patched.img
disconnect USB cable
press volume-up+volume-down+power buttons to switch off the tablet
press volume-up+volume-down+power buttons to switch on the tablet in Recovery mode
When Lenovo logo appears release the buttons.
Wait several minutes. Do not give up, do not restart. It takes time.
Reconfigure device
Enable USB Debugging
Disable System updates
Reinstall Magisk
Your device is rooted.
Whenever you want to use it in rooted mode you have to switch to recovery mode
The normal mode calls boot.img where magisk is not installed and the device will not be rooted.
You may proceed with removing Orange mode 5 sec wait message. Instructions available on the Internet.
If at some point the device writs back the original Recovery mode just reflash with magisk patch recovery-verified.
Hi,
I would like to root my Lenovo TB-7305F as well. The file I have leased from Magisk generates "size is too large" in fastboot. This problem has been written by others. I have compared the original filesize and the patched filesize. They are identical. Exactly to the byte. I did it exactly as greenbul describes. However, he uses the 7305X and I use the 7305F.
Also the SP tool cannot upload this patched file.
I have the 1GB 7305F model.
Do you have any idea?
Many thanks
Andreas
Skylon5000 said:
Hi,
I would like to root my Lenovo TB-7305F as well. The file I have leased from Magisk generates "size is too large" in fastboot. This problem has been written by others. I have compared the original filesize and the patched filesize. They are identical. Exactly to the byte. I did it exactly as greenbul describes. However, he uses the 7305X and I use the 7305F.
Also the SP tool cannot upload this patched file.
I have the 1GB 7305F model.
Do you have any idea?
Many thanks
Andreas
Click to expand...
Click to collapse
Lenovo Tab M7 - Обсуждение - 4PDA
Lenovo Tab M7 - Обсуждение, Планшет, 7"
4pda.to
Lenovo 7 tb-7305f
Root and TWRP
Lenovo Tab M7 - Обсуждение - 4PDA
Lenovo Tab M7 - Обсуждение, Планшет, 7"
4pda.to
is there a custom rom SM-A107f ?
and how to install TWRP recovery on SM-A107f?
-No
-And does not exist yet from what I can tell.
ShaDisNX255 said:
-No
-And does not exist yet from what I can tell.
Click to expand...
Click to collapse
thats a sad news
Consider this
ddiv1de said:
thats a sad news
Click to expand...
Click to collapse
Have you tried gsi roms? for more information head over to geektoandroid.com i hope this helps
Infant9099 said:
Have you tried gsi roms? for more information head over to geektoandroid.com i hope this helps
Click to expand...
Click to collapse
I've tried a couple, none have booted for me.
GSI Treble rom
ShaDisNX255 said:
I've tried a couple, none have booted for me.
Click to expand...
Click to collapse
I currently have a Samsung galaxy A105F/DS-U3 and it supports treble and seamless update - a/b. I have searched and it has lineageOS , Paranoid android and ViperOS. I'm gonna try LineageOS 17.0 - which gives me Anddroid Q. I'll let you know if i find one for you.
Infant9099 said:
I currently have a Samsung galaxy A105F/DS-U3 and it supports treble and seamless update - a/b. I have searched and it has lineageOS , Paranoid android and ViperOS. I'm gonna try LineageOS 17.0 - which gives me Anddroid Q. I'll let you know if i find one for you.
Click to expand...
Click to collapse
You have the A10, which is a bit different than the A10s so it is most likely that any GSI that boots to your phone will not boot for mine. Besides, A10s does not have TWRP yet and A10 does
Infant9099 said:
I currently have a Samsung galaxy A105F/DS-U3 and it supports treble and seamless update - a/b. I have searched and it has lineageOS , Paranoid android and ViperOS. I'm gonna try LineageOS 17.0 - which gives me Anddroid Q. I'll let you know if i find one for you.
Click to expand...
Click to collapse
any luck pal?
Infant9099 said:
I currently have a Samsung galaxy A105F/DS-U3 and it supports treble and seamless update - a/b. I have searched and it has lineageOS , Paranoid android and ViperOS. I'm gonna try LineageOS 17.0 - which gives me Anddroid Q. I'll let you know if i find one for you.
Click to expand...
Click to collapse
any luck pal?
Can A107F (A10s) be rooted?
Rootthegalaxy said:
Can A107F (A10s) be rooted?
Click to expand...
Click to collapse
Yes.
how to root SM-A107f Samsung Galaxy A10s
ShaDisNX255 said:
Yes.
Click to expand...
Click to collapse
so this is what i did to root my A10s.
1. check what binary your phone is running I already updated mine so my phone is on Android 10 binary 6.
how to check your binary - goto setings-about phone-software info, check Baseband version so on my phone its A107FXXU6BTES the U6 indicates your binary some has U3 binary 3 or U5, S5 binary 5
once you determined your binary.
2. activate DEVELOPER OPTIONS then activate OEM UNLOCK
samfw.com/firmware/SM-A107F/XTC/A107FXXU6BTF
go to this website and download the appropriate firmware.
each will contain a BL, AP, CP, and Home_CSC.
3. once finished downloading unlock your bootloader just boot to download mode then there is an option to press and HOLD VOLUME UP to unlock bootloader then press volume up again. if it didn't reboot instantly press and hold volume up and down again just do it again until when you choose to unlockbootloader it will reboot instatly.
4. after unlocking bootloader just go through the entire process of setting up your phone keep the bootloader unlock, INSTALL Magisk manager, so yeah install magisk choose patch image then from your downloaded firmware remove the "MD5" at the end of the files so it will be AP_A107F.tar then choose the AP to patch hrough magisk
5. after patching copy the patched file to your PC extract it by WINRAR get the boot.img if its boot.img.lz4 it means patch was not sucessful
6. after getting the boot.img copy it to your phone again and patch again make sure to rename it boot.img from inside the generated patch file then compress it as TAR using 7zip
7. flash it through odin on AP section and there your magisk rooted.
sorry for the long post
nyxl said:
how to root SM-A107f Samsung Galaxy A10s
so this is what i did to root my A10s.
1. check what binary your phone is running I already updated mine so my phone is on Android 10 binary 6.
how to check your binary - goto setings-about phone-software info, check Baseband version so on my phone its A107FXXU6BTES the U6 indicates your binary some has U3 binary 3 or U5, S5 binary 5
once you determined your binary.
2. activate DEVELOPER OPTIONS then activate OEM UNLOCK
samfw.com/firmware/SM-A107F/XTC/A107FXXU6BTF
go to this website and download the appropriate firmware.
each will contain a BL, AP, CP, and Home_CSC.
3. once finished downloading unlock your bootloader just boot to download mode then there is an option to press and HOLD VOLUME UP to unlock bootloader then press volume up again. if it didn't reboot instantly press and hold volume up and down again just do it again until when you choose to unlockbootloader it will reboot instatly.
4. after unlocking bootloader just go through the entire process of setting up your phone keep the bootloader unlock, INSTALL Magisk manager, so yeah install magisk choose patch image then from your downloaded firmware remove the "MD5" at the end of the files so it will be AP_A107F.tar then choose the AP to patch hrough magisk
5. after patching copy the patched file to your PC extract it by WINRAR get the boot.img if its boot.img.lz4 it means patch was not sucessful
6. after getting the boot.img copy it to your phone again and patch again make sure to rename it boot.img from inside the generated patch file then compress it as TAR using 7zip
7. flash it through odin on AP section and there your magisk rooted.
sorry for the long post
Click to expand...
Click to collapse
HOW THA?
it worked guy
thank yu guy
I hope that you maybe able to help me as my bootloader will not load
1 The OEM UNLOCK is on
2 Have pressed buttons as instructions but the phone just switches of
guyz that they dont know how to write magisk patch with odin
i had same problem that when i started to writing i got a failed error
if your bootloader is unlocked and yu renamed patched.img to boot.img
but yu got error do this :
change your frimware
if your a10s frimware is
A107FU5ATA9 it dosent support any root . change your frimware to a107fxxs5asl3
now start patching magisk !
Mirloo_HK said:
guyz that they dont know how to write magisk patch with odin
i had same problem that when i started to writing i got a failed error
if your bootloader is unlocked and yu renamed patched.img to boot.img
but yu got error do this :
change your frimware
if your a10s frimware is
A107FU5ATA9 it dosent support any root . change your frimware to a107fxxs5asl3
now start patching magisk !
Click to expand...
Click to collapse
Hi '''Mirloo''''About rooting the (Samsung Galaxy 10s SM-A107f) I have tried most of the rooting akps with no luck (cfautoroot I have not tried yet)'''''''As for using Odin & magisk I am getting so many different instructions from different posts
1 unlock the bootloader This I have done successfully
The next steps using Magisk & Odin Start to get misleading
one site says Copy the AP to your phone and patch it where another site says says change the format of the AP file to tar by deleting .mds then copy it to your phone
I seem to get confused now as what to do next ''''Please could you give me full instructions ....Thank you
I have attempted to patch boot.img around 7 times unsuccessfully, I have the SM-A107F, can someone please send me the correctly patched boot image for my device, will be much appreciated.
i have this device, SM-A107F/DS, still no custom rom? is it possible to install lineage os?
fatdog1 said:
i have this device, SM-A107F/DS, still no custom rom? is it possible to install lineage os?
Click to expand...
Click to collapse
I'm also waiting for this. Tried flashing twrp recovery using odin but I failed. The error says "only official binaries are allowed to be flashed" tried flashing the original firmware but same error. Wondering why.
Hello is the Galaxy tab s7+ wifi model bought in the us rootable? i ask this becuase i know that the us model galaxy phones arent rootable so im asking if the same applys to the tablets
Yes, it is rootable, just rooted my SM-T970 today
Can you still watch netflix/amazon in HD after rooting? On which windevine level are you now?
I don't use either of these services, so I don't know, sorry.
BigBucha said:
Yes, it can be rooted, just rooted my SM-T970 today
Click to expand...
Click to collapse
merhaba s7'm var artı t970'im var nasıl rootlayacağız
Translation: hello i have s7 plus i have t970 how do we root
I followed this guide below that I found somewhere in this forum, it is not mine, I just added some notes to it. I recommend searching for the original thread. There could also be a newer firmware version now, please check yours before rooting. It has been almost 2 months since I did it.
Unlock OEM (under developer options)
Boot in download mode (with the tablet powered down, press volume up + volume down and connect USB cable to PC)
Long press volume up to unlock bootloader (you will lose all your data!)
Download the original firmware ( https://www.sammobile.com/samsung/galaxy-tab-s7/firmware/SM-T970/XAR/download/T970XXU1ATJ4/502568/ )
Flash it using ODIN in download mode (Optional, just to make sure you are using the same image you are going to patch)
Extract boot.img.lz4 from AP_xxxx tar file.
Decompress the lz4 to get the uncompressed boot.img (I had to use a separate tool since 7zip was not able to compress/uncompress the lz4 archive, https://github.com/lz4/lz4/releases )
Copy the file to the tablet
Patch it using the latest Magisk Manager. ( https://github.com/topjohnwu/Magisk)
Copy the patched boot image back to the PC.
Recompress it as boot.img.tar (rename magisk_patched.img to boot.img then compress as boot.img.tar)
Flash it using AP slot in Odin and reboot tablet. (I had to do a full factory reset)
Install Magisk again
For AdAway to work you will need to enable systemless module in Magisk
You are done! Magisk manager should say now it is rooted. (you will also have a BIG warning every time the tablet is powered on, telling you how irresponsible and despicable you are by modifying the device)
I rooted my Samsung S20 before by following this guide
it is very similar to what is described above.
BigBucha said:
Mod edit, broken quote removed
Click to expand...
Click to collapse
Mod edit: Google Translate translation added.
I have android 11 installed on my device, can you help me with remote team use?
Original post:
Cihazımda yüklü android 11 var, uzak ekip kullanımında bana yardım edebilir misin?
@simerenya Please use English on XDA Forums. If you want, you can use the translating service of your choice. See the forum rules for more details.
@BigBucha I suggest that you do not link to that particular website for Magisk downloads (or any other website that pretends to be the Magisk website). None of those websites are run by @topjohnwu and in the best case they're just re-hosting the files to get ad-revenues, but in the worst case you'll download a malicious version of Magisk. That wouldn't be good. The only place for sure and safe downloads of Magisk is on @topjohnwu's Github: https://github.com/topjohnwu/Magisk
@Didgeridoohan , understood, thanks! I didn't know about Magisk's official web site, just googled it. I updated my previous post.
@simerenya,
Not sure if I understood your question. I used google translate.
You asked for a screen-sharing session?
I have done rooting of this tablet model only once myself, that was 2 months ago, not sure if I can be of much help to you.
Please try following the guide step by step yourself. If in doubt, I recommend not doing this since you may brick your tablet.
You can post your questions in the forum if you get stuck or brick your device. I will try to answer them.
I was able to root my tablet from the first try.
Good luck.
Is it possible to root Galaxy tab s7+ using Kingroot, kingoroot, towelroot, or any of the other 1 click rooting apps?
BigBucha said:
I followed this guide below that I found somewhere in this forum, it is not mine, I just added some notes to it. I recommend searching for the original thread. There could also be a newer firmware version now, please check yours before rooting. It has been almost 2 months since I did it.
Unlock OEM (under developer options)
Boot in download mode (with the tablet powered down, press volume up + volume down and connect USB cable to PC)
Long press volume up to unlock bootloader (you will lose all your data!)
Download the original firmware ( https://www.sammobile.com/samsung/galaxy-tab-s7/firmware/SM-T970/XAR/download/T970XXU1ATJ4/502568/ )
Flash it using ODIN in download mode (Optional, just to make sure you are using the same image you are going to patch)
Extract boot.img.lz4 from AP_xxxx tar file.
Decompress the lz4 to get the uncompressed boot.img (I had to use a separate tool since 7zip was not able to compress/uncompress the lz4 archive, https://github.com/lz4/lz4/releases )
Copy the file to the tablet
Patch it using the latest Magisk Manager. ( https://github.com/topjohnwu/Magisk)
Copy the patched boot image back to the PC.
Recompress it as boot.img.tar (rename magisk_patched.img to boot.img then compress as boot.img.tar)
Flash it using AP slot in Odin and reboot tablet. (I had to do a full factory reset)
Install Magisk again
For AdAway to work you will need to enable systemless module in Magisk
You are done! Magisk manager should say now it is rooted. (you will also have a BIG warning every time the tablet is powered on, telling you how irresponsible and despicable you are by modifying the device)
I rooted my Samsung S20 before by following this guide
it is very similar to what is described above.
Click to expand...
Click to collapse
Thanks for the instruction. I was finally installed magdisk on S7+ tab. Root check is good. But some app like adaway does not detect root and never ask for root access when installed. Do you know how to solve this?
xiaozi said:
Thanks for the instruction. I was finally installed magdisk on S7+ tab. Root check is good. But some app like adaway does not detect root and never ask for root access when installed. Do you know how to solve this?
Click to expand...
Click to collapse
Not sure about other apps, but for AdAway to work I had to do these steps:
1. Open Magisk
2. Go to Modules (the jigsaw icon)
3. Install "Systemless Hosts" module
4. Reboot and try selecting root mode in AdAway again
Please check this thread https://forum.xda-developers.com/t/systemless-adaway-with-magisk.3733839/
BigBucha said:
I followed this guide below that I found somewhere in this forum, it is not mine, I just added some notes to it. I recommend searching for the original thread. There could also be a newer firmware version now, please check yours before rooting. It has been almost 2 months since I did it.
Unlock OEM (under developer options)
Boot in download mode (with the tablet powered down, press volume up + volume down and connect USB cable to PC)
Long press volume up to unlock bootloader (you will lose all your data!)
Download the original firmware ( https://www.sammobile.com/samsung/galaxy-tab-s7/firmware/SM-T970/XAR/download/T970XXU1ATJ4/502568/ )
Flash it using ODIN in download mode (Optional, just to make sure you are using the same image you are going to patch)
Extract boot.img.lz4 from AP_xxxx tar file.
Decompress the lz4 to get the uncompressed boot.img (I had to use a separate tool since 7zip was not able to compress/uncompress the lz4 archive, https://github.com/lz4/lz4/releases )
Copy the file to the tablet
Patch it using the latest Magisk Manager. ( https://github.com/topjohnwu/Magisk)
Copy the patched boot image back to the PC.
Recompress it as boot.img.tar (rename magisk_patched.img to boot.img then compress as boot.img.tar)
Flash it using AP slot in Odin and reboot tablet. (I had to do a full factory reset)
Install Magisk again
For AdAway to work you will need to enable systemless module in Magisk
You are done! Magisk manager should say now it is rooted. (you will also have a BIG warning every time the tablet is powered on, telling you how irresponsible and despicable you are by modifying the device)
I rooted my Samsung S20 before by following this guide
it is very similar to what is described above.
Click to expand...
Click to collapse
get an error : blocked by OEM...What did I wrong? andoid 11 latest firmware
dolf123 said:
get an error : blocked by OEM...What did I wrong? andoid 11 latest firmware
Click to expand...
Click to collapse
Did you successfully unlock bootloader? My phone was not locked to any mobile carrier. Please paste a screenshot.
These instructions are for the CPH2459 – Unlocked Nord N20 50
I wanted to give back and distribute an easy to follow step-by-step guide as many were asking for a complete guide and I had a little time to create it today. Hopefully this will help kick off some good dev for the device as we are light currently.
I take no responsibility for any issues with your device and do not have backups in the steps, so use at your own risk as always...
COMPLETE STEPS......
Update your phone to the latest OS/patch level over Internet OTA from 1+ and reboot
Verify you are running OS/patch à CPH2459_11_C_10 (latest at time of this)
Enable developer options by clicking on the build number until activation appears (Under Setting-->About-->Version)
Enable Unlock bootloader in the new Developers Options section now in the Phone menu
Enable USB debugging under the new Developers Options
Plug in your phone with usb connected to pc and select transfer files if prompted
Download and extract install latest ptools-n20.zip (with included patched boot files)
Open a windows command prompt in the folder that you extracted the platform tools into
Run adb devices and be sure the phone shows up as a device that is attached
Accept device fingerprint if asked
Run command to boot to bootloader: adb reboot bootloader
Run command to ensure connection in bootloader to your phone: fastboot devices
Run Command to unlock bootloader: fastboot flashing unlock
Lave command prompt open
Use volume keys to select “unlock bootloader” then press “power” to unlock
The device will reset and will now be unlocked
After phone boots, complete the quick setup
Repeat step #3, #5-6, #9-12
In Command prompt where platform tools are installed run command: fastboot flash boot a.img
Reboot phone and you will be patched
Install Magisk 25.2 App from official repo & Enable Zygisk in settings
Enable Magisk hide and reopen the app
Add your google account if not already added and use Play Store or use Aurora store to install Safetynet Checker by flink apps
Run Safetynet checker and notice the device fails 2 checks
Transfer 2 zip files included to your phone: Shamiko & Safetynet fix. These will help hiding root and will allow your phone to pass Safetynet fixes
Install both zips under module section in Magisk. (you can do 1…don’t reboot when asked, then do other and reboot to activate both)
Run Safetynet Checker again and you should pass all checks.
Viola…you are unlocked/rooted/patched and pass safetynect checks.....ENJOY!
I will update here on how to take future OTAs as more come out and if time allows.
NOTES: Files in platform tools
a.img = boot_a.img magisk patched
b.img = boot_b.img magisk patched (just in case)
boot_a.img = Unpatched a (just in case)
boot_b.img = Unpatched b (just in case)
==============================================
2/3/23 UPDATE: How to take an OTA and preserve root
==============================================
1. First, Under developer options, make sure the option to apply automatic updates on reboot is ENABLED. (If you do not do this, you will loose root)
2. Unroot the device. We wont completely remove Magisk, just restore images. To do this Open Magisk, click uninstall magisk, and only click "restore images". DO NOT REBOOT!
3. Check for software updates. Install OTA update after downloaded. DO NOT REBOOT!
4. Open Magisk again and now reinstall it but select "inactive slot" for the option.
5. REBOOT. Boot will take about 30 seconds to apply.
You are now updated
ScarletWizard said:
Thank you for this I will post this on the telegram channel
Click to expand...
Click to collapse
What is the link to the telegram chan?
mvincent2k said:
What is the link to the telegram chan?
Click to expand...
Click to collapse
My CPH2459 crappped out on me, and I have had little luck since moving from GN2200 to this model and could use a backup if you could lend a hand
mvincent2k said:
What is the link to the telegram chan?
Click to expand...
Click to collapse
OnePlus Nord N20 | Official
You can view and join @oneplusnordn20 right away.
t.me
ScarletWizard said:
Incorrect link
Click to expand...
Click to collapse
Can you share the right channel.
mvincent2k said:
These instructions are for the CPH2459 – Unlocked Nord N20 50
I wanted to give back and distribute an easy to follow step-by-step guide as many were asking for a complete guide and I had a little time to create it today. Hopefully this will help kick off some good dev for the device as we are light currently.
Click to expand...
Click to collapse
Damn son, your attention to detail is admirable! Very thorough and well-documented. Thanks.
Can I use this on the new ota update
mvincent2k said:
a.img = boot_a.img magisk patched
Click to expand...
Click to collapse
killerex said:
Can I use this on the new ota update
Click to expand...
Click to collapse
No you would need an updated img if you are on the latest upgrade. I no longer have an N20 to test with otherwise would create one for the group. Someone else may possibly.
How? I'm not updated yet can guide me how to do it.thank
killerex said:
How
Click to expand...
Click to collapse
Search the other XDA threads here for this device. A few explain how to extract payload and patch.
If you are on the previous update, see the update to my instructions just posted on how to take the OTA and stay rooted with Magisk
I'm getting installation error.. I'm in previous update
mvincent2k said:
These instructions are for the CPH2459 – Unlocked Nord N20 50
I wanted to give back and distribute an easy to follow step-by-step guide as many were asking for a complete guide and I had a little time to create it today. Hopefully this will help kick off some good dev for the device as we are light currently.
I take no responsibility for any issues with your device and do not have backups in the steps, so use at your own risk as always...
COMPLETE STEPS......
Update your phone to the latest OS/patch level over Internet OTA from 1+ and reboot
Verify you are running OS/patch à CPH2459_11_C_10 (latest at time of this)
Enable developer options by clicking on the build number until activation appears (Under Setting-->About-->Version)
Enable Unlock bootloader in the new Developers Options section now in the Phone menu
Enable USB debugging under the new Developers Options
Plug in your phone with usb connected to pc and select transfer files if prompted
Download and extract install latest ptools-n20.zip (with included patched boot files)
Open a windows command prompt in the folder that you extracted the platform tools into
Run adb devices and be sure the phone shows up as a device that is attached
Accept device fingerprint if asked
Run command to boot to bootloader: adb reboot bootloader
Run command to ensure connection in bootloader to your phone: fastboot devices
Run Command to unlock bootloader: fastboot flashing unlock
Lave command prompt open
Use volume keys to select “unlock bootloader” then press “power” to unlock
The device will reset and will now be unlocked
After phone boots, complete the quick setup
Repeat step #3, #5-6, #9-12
In Command prompt where platform tools are installed run command: fastboot flash boot a.img
Reboot phone and you will be patched
Install Magisk 25.2 App from official repo & Enable Zygisk in settings
Enable Magisk hide and reopen the app
Add your google account if not already added and use Play Store or use Aurora store to install Safetynet Checker by flink apps
Run Safetynet checker and notice the device fails 2 checks
Transfer 2 zip files included to your phone: Shamiko & Safetynet fix. These will help hiding root and will allow your phone to pass Safetynet fixes
Install both zips under module section in Magisk. (you can do 1…don’t reboot when asked, then do other and reboot to activate both)
Run Safetynet Checker again and you should pass all checks.
Viola…you are unlocked/rooted/patched and pass safetynect checks.....ENJOY!
I will update here on how to take future OTAs as more come out and if time allows.
NOTES: Files in platform tools
a.img = boot_a.img magisk patched
b.img = boot_b.img magisk patched (just in case)
boot_a.img = Unpatched a (just in case)
boot_b.img = Unpatched b (just in case)
==============================================
2/3/23 UPDATE: How to take an OTA and preserve root
==============================================
1. First, Under developer options, make sure the option to apply automatic updates on reboot is ENABLED. (If you do not do this, you will loose root)
2. Unroot the device. We wont completely remove Magisk, just restore images. To do this Open Magisk, click uninstall magisk, and only click "restore images". DO NOT REBOOT!
3. Check for software updates. Install OTA update after downloaded. DO NOT REBOOT!
4. Open Magisk again and now reinstall it but select "inactive slot" for the option.
5. REBOOT. Boot will take about 30 seconds to apply.
You are now updated
Click to expand...
Click to collapse
Thank you for this! Glad to see people are picking up the slack. I havent updated yet because im worried about having to battle tighter restrictions that newer versions of android inevitably bring. I wont be able to use the images as i have the gn2200 but grateful for the how to guide on updating. Didnt realize it was quite that easy. Im still on May on one device and July on the other tho recently had to downgrade it to restore it in an emergency situation and was thankfully able to do all the flashing from the may device otg
PsYk0n4uT said:
Thank you for this! Glad to see people are picking up the slack. I havent updated yet because im worried about having to battle tighter restrictions that newer versions of android inevitably bring. I wont be able to use the images as i have the gn2200 but grateful for the how to guide on updating. Didnt realize it was quite that easy. Im still on May on one device and July on the other tho recently had to downgrade it to restore it in an emergency situation and was thankfully able to do all the flashing from the may device otg
Click to expand...
Click to collapse
Not a problem. Always glad to help the community out!
Very nice. I'm expecting delivery of one of these phones tomorrow. It already has Android 12 installed on it. So, I'm wondering if it's safe to use the attached image files to root it or should I go through the process of having Magisk patch the phone's existing a and b images?
Raybo58 said:
Very nice. I'm expecting delivery of one of these phones tomorrow. It already has Android 12 installed on it. So, I'm wondering if it's safe to use the attached image files to root it or should I go through the process of having Magisk patch the phone's existing a and b images?
Click to expand...
Click to collapse
Just make sure your using a12 boot image if your trying to use a posted one.balso be sure to use the same security patch boot image as the system you already have installed.
Safest bet is to use the DSU sideloader method to pull your own boot image and then patch it if your unsure of which patched boot image to use. It's a little more complicated but pulling your own boot image will ensure that you have an exact match for your device.
If you have or can locate and obtain an unpatched boot image that matches your system. You should have one on hand just in case the patched boot image doesn't work so that you can simply reflash your stock image in that case.
A mismatching boot image can lead to an unbootable state so you need to be prepared.
You shouldn't have to worry much about anything crazy or unrepairable so long as your flashing boot images made for the device your flashing them to. Just don't flash boot images from a completely different device as that can cause you to end up with any sort 9f crazy weird issues that may not even be fixable.
Raybo58 said:
Very nice. I'm expecting delivery of one of these phones tomorrow. It already has Android 12 installed on it. So, I'm wondering if it's safe to use the attached image files to root it or should I go through the process of having Magisk patch the phone's existing a and b images?
Click to expand...
Click to collapse
By any chance you got the latest boot.img
Will this work on a GN2200?
NO
Followed instructions and it worked. BUT, can't update the firmware. When I try to restore images in Magisk it says they don't exist. So I can't update to the latest firmware. Suggestions?
alipps1 said:
Followed instructions and it worked. BUT, can't update the firmware. When I try to restore images in Magisk it says they don't exist. So I can't update to the latest firmware. Suggestions?
Click to expand...
Click to collapse
I recently ran into this on another device and had to fix so you are in luck. I believe something broke with magisk running on 13 during the last OTA with security, so here are the steps...
1) Unhide and Uninstall magisk app completely and Update to the latest canary version of magisk apk here and restart: https://github.com/topjohnwu/Magisk
2) Verify it sees magisk installed and has latest build.
3) Try restoring images again and it may work.
If that does not work...
1) You will need to do a full unroot...which technically should not work if the images were not present, but it does, so images are present (proving it is a bug)
2) You will need to complete the full procedure of patching the boot image again yourself.
3) Extract payload and patch the boot.img per instructions in this forum, then flash per my instructions above.
FYI. I did this on the current version of the OS and then did the restore images and upgrade to take the OTA and prove the bug and that OTA updates will work as in the instructions above in the future again, which it did.
Alternatively, you could also update the to the latest OTA after unrooting and just do it once, but I wanted to play it safe just in case Google updated something in the latest 13 builds blocking magisk... So your choice, but please post back here how you make out.
Good luck