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.
Related
I haven't had any luck building or finding TWRP yet for the ZenFone AR, but I found a way to get root access without needing the recovery.
To start, you will need:
The unlock APK from ASUS:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZS571KL/SIGNED_UnlockTool-9.0.0.35.apk
The matching system image for your phone: BE SURE TO DOWNLOAD THE CORRECT VERSION BETWEEN JP (Japan) AND WW (WorldWide) or your wifi will break.
https://www.asus.com/us/Phone/ZenFone-AR-ZS571KL/HelpDesk_Download/
As of the time of writing, I downloaded:
ZS571KL Software Image: V14.1600.1711.36 for WW/TIM SKU only
The installation steps are pretty standard, but I'll summarize them here:
1) Get working copies of adb and fastboot
2) Push the Unlock APK to your phone and install and unlock on the device. THIS WILL ERASE ALL OF YOUR DATA.
3) Install Magisk Manager as described here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
A) Download this APK, copy to your phone, and install.
B) From your system image, uncompress and find the boot.img and copy to your SD Card.
C) Open MagiskManager and Press Install > Install > Patch Boot Image File, and select your stock boot image file (boot.img)
D) Magisk Manager will now download a file and patch your boot image, and store it in [Internal Storage]/MagiskManager/patched_boot.img
E) Copy the patched boot image to your PC. If you can't find it via MTP, you can pull the file with ADB: adb pull /sdcard/MagiskManager/patched_boot.img
F) adb reboot bootloader
G) sudo fastboot flash boot patched_boot.img
H) Press the Power button to "Start"
You should now have MagiskManager installed, this is a program similar to SuperSU and it can enable and manage root for you.
Try look the TWRP of the Asus Zenfone 3 Deluxe if you can use it
Sent from my Asus ZenFone 3 Deluxe using XDA Labs
This is great!! Why isn't Verizon supported in this method? Is it because of the unlocking process?
Worked well for me with the installation via the magick.apk (non-recovery/non-rooted method) on the WW model.
Without this thread, i would not have known the unlock apk had been released nor that Majick worked with the AR.
thank you chadrockey
comomomo said:
This is great!! Why isn't Verizon supported in this method? Is it because of the unlocking process?
Click to expand...
Click to collapse
I would consider the Verizon version an almost different phone. I've been fortunate enough to have them side by side and they are very different. The builds and model numbers are different, as well as things you wouldn't expect like screen coloration or the scaling and menu options for the screens. There's also changes like the USB working much differently on the Verizon (much more locked down).
I haven't tried using the unlock tool on the Verizon model, but I don't expect it to work. As long as that's the case, I wouldn't expect root to come to Verizon.
Suspicious link
Why is the link to the apk redirected and hosted on an untrustworthy site? I would advise against using this app from this link.
Everything about the link screams malware.
huginnaesir said:
Why is the link to the apk redirected and hosted on an untrustworthy site? I would advise against using this app from this link.
Everything about the link screams malware.
Click to expand...
Click to collapse
It's a direct link from the ASUS download page. You can go to www.asus.com/us/Phone/ZenFone-AR-ZS571KL/HelpDesk_Download and click the same link there
For anyone who has got root install this and he will build your twrp.
https://www.mediafire.com/file/e5d1ojafoefcgbw/app-release-1.apk
Sent from my LEX727 using xda premium
Hi. Did just like this article explained, and now my wifi is gone. Any fix for this??
Has anyone tried to install the WW software on the Verizon Model?
chadrockey said:
I haven't had any luck building or finding TWRP yet for the ZenFone AR, but I found a way to get root access without needing the recovery.
To start, you will need:
The unlock APK from ASUS:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZS571KL/SIGNED_UnlockTool-9.0.0.35.apk
The matching system image for your phone: BE SURE TO DOWNLOAD THE CORRECT VERSION BETWEEN JP (Japan) AND WW (WorldWide) or your wifi will break.
https://www.asus.com/us/Phone/ZenFone-AR-ZS571KL/HelpDesk_Download/
As of the time of writing, I downloaded:
ZS571KL Software Image: V14.1600.1711.36 for WW/TIM SKU only
The installation steps are pretty standard, but I'll summarize them here:
1) Get working copies of adb and fastboot
2) Push the Unlock APK to your phone and install and unlock on the device. THIS WILL ERASE ALL OF YOUR DATA.
3) Install Magisk Manager as described here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
A) Download this APK, copy to your phone, and install.
B) From your system image, uncompress and find the boot.img and copy to your SD Card.
C) Open MagiskManager and Press Install > Install > Patch Boot Image File, and select your stock boot image file (boot.img)
D) Magisk Manager will now download a file and patch your boot image, and store it in [Internal Storage]/MagiskManager/patched_boot.img
E) Copy the patched boot image to your PC. If you can't find it via MTP, you can pull the file with ADB: adb pull /sdcard/MagiskManager/patched_boot.img
F) adb reboot bootloader
G) sudo fastboot flash boot patched_boot.img
H) Press the Power button to "Start"
You should now have MagiskManager installed, this is a program similar to SuperSU and it can enable and manage root for you.
Click to expand...
Click to collapse
Thanks as first for that thread. I did it, it has been patched and booted successfully but my device is it no rooted yet...
hello,please help for Verizon device
i want to root it as any device,also i want to install custom Rom as normal as any device !!
any help and co operate ??
Hello
I bought a new Oppo A5 2020 and want to recovery my Titnaium Backups.
I search now 8-10 Hours to find a solution to root my phone, but no tutorial works.
I want to root my phone with Magisk and the right boot.img but i found only this file:
CPH1931_11_A.08_190905_cb4610de.ofp
I can not extract the ofp without some hardware parts.
Has anyone a idea how to root the Oppo A 2020 CPH1931
(CPH1931EX_11_A.08)
(CPH1931EX_11_A.13) <<- now aviable
Thank u so much
deadmeiker said:
Hello
I bought a new Oppo A5 2020 and want to recovery my Titnaium Backups.
I search now 8-10 Hours to find a solution to root my phone, but no tutorial works.
I want to root my phone with Magisk and the right boot.img but i found only this file:
CPH1931_11_A.08_190905_cb4610de.ofp
I can not extract the ofp without some hardware parts.
Has anyone a idea how to root the Oppo A 2020 CPH1931
(CPH1931EX_11_A.08)
(CPH1931EX_11_A.13) <<- now aviable
Thank u so much
Click to expand...
Click to collapse
Me too
me three
deadmeiker said:
Hello
I bought a new Oppo A5 2020 and want to recovery my Titnaium Backups.
I search now 8-10 Hours to find a solution to root my phone, but no tutorial works.
I want to root my phone with Magisk and the right boot.img but i found only this file:
CPH1931_11_A.08_190905_cb4610de.ofp
I can not extract the ofp without some hardware parts.
Has anyone a idea how to root the Oppo A 2020 CPH1931
(CPH1931EX_11_A.08)
(CPH1931EX_11_A.13) <<- now aviable
Thank u so much
Click to expand...
Click to collapse
Me four. I want to root my A5 2020
Can you boot into bootloader? Cause i can't stay in bootloader mode.
Me 5..
Setting - about phone - tap "version" 7 times
Additional option - developer option - oem unlock bootloader
Tried download ota
Extracted from phone manager.. and got boot.img
But magisk say its corrupted.. maybe it cant read it.. some says to use its recovery.img but i cant find it.. im a noob in rooting so i cant opt to experiment
Tried these things (3rd might be a possiible solution)
1.)
I tried using the OTA update which is a .ozip file, and needs a certain key to be usable (Needs to be decrypted to zip), key differs depending on the device
as for reference:
filedesc.com/en/file/ozip
tried tools such as
github.com/bkerler/oppo_ozip_decrypt
(But with no luck, A5 2020 isn't supported)
2.)
I found something on the web which is the CPH1931_11_A.08_190905_cb4610de.ofp
which i cannot decrypt to get the boot.img file
3.)
If your willing to take the risk, i found this
forum.gsmdevelopers.com/oppo-android-unified/84350-oppo-a5-2020-cph1931-dead-boot-alive-akshay-bhandare.html
which leads to the boot.img here (Just extract then you'll find boot.bin, change the file extension to boot.img (Just replace/rename .bin to .img))
mediafire.com/file/8kb8ilgz0mxaga3/OPPO_A5_2020%2528CPH1931_%2529DEAD_BOOT_ALIVE_BY_AKSHAY_BHANDARE.rar/file
(If link doesn't work anymore, ill upload the one I've downloaded already)
I tried patching this using Magisk and it works, but i haven't tried flashing it to A5 2020
Thank u so much[/QUOTE]
---------- Post added at 04:43 PM ---------- Previous post was at 04:17 PM ----------
KrisAmaba said:
1.)
I tried using the OTA update which is a .ozip file, and needs a certain key to be usable (Needs to be decrypted to zip), key differs depending on the device
as for reference:
filedesc.com/en/file/ozip
tried tools such as
github.com/bkerler/oppo_ozip_decrypt
(But with no luck, A5 2020 isn't supported)
2.)
I found something on the web which is the CPH1931_11_A.08_190905_cb4610de.ofp
which i cannot decrypt to get the boot.img file
3.)
If your willing to take the risk, i found this
forum.gsmdevelopers.com/oppo-android-unified/84350-oppo-a5-2020-cph1931-dead-boot-alive-akshay-bhandare.html
which leads to the boot.img here (Just extract then you'll find boot.bin, change the file extension to boot.img (Just replace/rename .bin to .img))
mediafire.com/file/8kb8ilgz0mxaga3/OPPO_A5_2020%2528CPH1931_%2529DEAD_BOOT_ALIVE_BY_AKSHAY_BHANDARE.rar/file
(If link doesn't work anymore, ill upload the one I've downloaded already)
I tried patching this using Magisk and it works, but i haven't tried flashing it to A5 2020
Click to expand...
Click to collapse
If your going to try the 3rd possible solution in rooting Oppo A5 2020
DISCLAIMER NOTICE
* I'm not responsible for bricked devices, dead SD cards or thermonuclear war.
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
Here's what you need
Download ADB and Fastboot files and extract them in the C:/drive. (Windows/MAC)
getdroidtips.com/how-to-install-adb-and-fastboot-on-windows
Download and Install Oppo USB Drivers.
getdroidtips.com/download-oppo-usb-drivers/
Oppo A5 2020 (Boot.img)
mediafire.com/file/8kb8ilgz0mxaga3/OPPO_A5_2020%2528CPH1931_%2529DEAD_BOOT_ALIVE_BY_AKSHAY_BHANDARE.rar/file
Here are the steps:
(Steps to do on your Phone)
1. Download the boot.img (Originally boot.bin in the link given)
2. Download Latest Magisk Manager
github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk
3. Launch Magisk Manager. When a popup appears asking to install Magisk, select INSTALL and choose install again.
4. Tap on “Patch Boot Image File”
5. Navigate to internal storage and select your phone’s boot image that you've downloaded earlier.
6. Wait for a couple of seconds. Magisk will start patching the boot image.
7. Once the boot image has been patched, copy the “patched_boot.img” from the internal storage and replace it in the ADB fastboot extracted ROM folder on your PC.
(Steps to do on your PC)
1. We assume that you have already downloaded the ADB & Fastboot tool from the link given above.
2. Now, extract the ADB fastboot tool, then move the patched boot image to the same folder.
3. Hold the Shift key and right-click on the mouse to open the command window/PowerShell.
4. Next, enter the following command:
Flash the “patched_boot.img” to install Magisk and root your Android device:
fastboot flash boot patched_boot.img
The flashing process will begin. Once done, run
fastboot reboot
5. Done, Open Magisk to see if it's successful
---------- Post added at 04:52 PM ---------- Previous post was at 04:43 PM ----------
KrisAmaba said:
If your going to try the 3rd possible solution in rooting Oppo A5 2020
DISCLAIMER NOTICE
* I'm not responsible for bricked devices, dead SD cards or thermonuclear war.
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
Here's what you need
Download ADB and Fastboot files and extract them in the C:/drive. (Windows/MAC)
getdroidtips.com/how-to-install-adb-and-fastboot-on-windows
Download and Install Oppo USB Drivers.
getdroidtips.com/download-oppo-usb-drivers/
Oppo A5 2020 (Boot.img)
mediafire.com/file/8kb8ilgz0mxaga3/OPPO_A5_2020%2528CPH1931_%2529DEAD_BOOT_ALIVE_BY_AKSHAY_BHANDARE.rar/file
Here are the steps:
(Steps to do on your Phone)
1. Download the boot.img (Originally boot.bin in the link given)
2. Download Latest Magisk Manager
github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk
3. Launch Magisk Manager. When a popup appears asking to install Magisk, select INSTALL and choose install again.
4. Tap on “Patch Boot Image File”
5. Navigate to internal storage and select your phone’s boot image that you've downloaded earlier.
6. Wait for a couple of seconds. Magisk will start patching the boot image.
7. Once the boot image has been patched, copy the “patched_boot.img” from the internal storage and replace it in the ADB fastboot extracted ROM folder on your PC.
(Steps to do on your PC)
1. We assume that you have already downloaded the ADB & Fastboot tool from the link given above.
2. Now, extract the ADB fastboot tool, then move the patched boot image to the same folder.
3. Hold the Shift key and right-click on the mouse to open the command window/PowerShell.
4. Next, enter the following command:
Flash the “patched_boot.img” to install Magisk and root your Android device:
fastboot flash boot patched_boot.img
The flashing process will begin. Once done, run
fastboot reboot
5. Done, Open Magisk to see if it's successful
Click to expand...
Click to collapse
Forgot to Mention, that before proceeding to the steps to do on your PC
you need to do this.
1. Setting - about phone - tap "version" 7 times (To unlock Developer Option)
2. Additional option - developer option - oem unlock bootloader
3. Additional option - developer option - allow USB Debugging
4. turn off device
5. Volume up + power button if logo appears, stop pressing
6. Connect to PC (then proceed to the given steps)
Anyone try this method?
jayaduana said:
Anyone try this method?
Click to expand...
Click to collapse
I bought this phone 24-1-2020. I wanna know to if anyone tried this method.
yes!it works...
Can more people (mainly the ones who allrdy did comment in this thread) confirm method 3 is working?
I updated to CPH1931EX_11_A.28. Do i need a patched boot.img of CPH1931EX_11_A.28 or can i use any boot.img of all versions?
I wanted to know if the boot.img for all versions is the same.
i.daniyal said:
yes!it works...
Click to expand...
Click to collapse
i dont know how u've managed it. i can't boot into fastboot, using vol down + power buttons or using adb reboot bootloader. can u tell me how to boot into fastboot?
Is your OPPO A5 2020 rooted now
jayaduana said:
i dont know how u've managed it. i can boot into fastboot, using vol down + power buttons or using adb reboot bootloader. can u tell me how to boot into fastboot?
Click to expand...
Click to collapse
Do i understand, you did try method 3 using the boot.img provided in the link?
You were able to patch the boot.img with magisk?
Did you flash the patched boot.img to phone successfully? If so, its safe to use the boot.img provided in the link?
Are you rooted now?
I really need root in order to get boldbeast call recording working properly with pie 9.
jayaduana said:
i dont know how u've managed it. i can't boot into fastboot, using vol down + power buttons or using adb reboot bootloader. can u tell me how to boot into fastboot?
Click to expand...
Click to collapse
Read the instructions carefully it's vol up ?
Typo
hotcold65 said:
Read the instructions carefully it's vol up
Click to expand...
Click to collapse
That has to be a typo, because for the OPPO A5 2020 its powerbutton + volume down
ron23ny said:
That has to be a typo, because for the OPPO A5 2020 its powerbutton + volume down
Click to expand...
Click to collapse
Yes, when use volume up, its keep restarting. When use volume down, its login to coloros recovery mode,not fastboot mode.
jayaduana said:
Yes, when use volume up, its keep restarting. When use volume down, its login to coloros recovery mode,not fastboot mode.
Click to expand...
Click to collapse
Can you please answer my questions in post #12, i really need to know if you rooted successfully.
i.daniyal said:
yes!it works...
Click to expand...
Click to collapse
Some guidance please, or was your answer just a prank?
Ok, i tried to get in fastboot mode with command adb reboot bootloader. I do get the fastboot logo screen for a second, but then it just loading the OS pie 9, like someone stated here before. I read in some sources, OPPO company disabled the fastboot mode for this phone, so you will not able to flash files using adb. I also read power + volume down = recovery mode (working) and power + volume up = fastboot mode (not working because company disabled this).
I use firmware CPH1931EX_11_A.28. Now the big question: does somebody know, if some older version of firmware has fastboot not disabled by company?
Seems for now, you can only root this phone by using hardware tools like miracle box and easy jtag pro.
gffg
ron23ny said:
Can more people (mainly the ones who allrdy did comment in this thread) confirm method 3 is working?
I updated to CPH1931EX_11_A.28. Do i need a patched boot.img of CPH1931EX_11_A.28 or can i use any boot.img of all versions?
I wanted to know if the boot.img for all versions is the same.
Click to expand...
Click to collapse
I also using CPH1931EX_11_A.28 and have exact same bootloader problem.
I manage to extract boot.img from 11_A.13 and 11_A.28 firmwares using "ubuntu ozip to zip" and files appear identical and patched successfully using Magisk. The boot.img provided in the link is not the same, I wouldn't use it.
Did you find out if some older version of firmware has fastboot not disabled by company?
Many thanks for taking time to read reply.
Sotirious said:
I also using CPH1931EX_11_A.28 and have exact same bootloader problem.
I manage to extract boot.img from 11_A.13 and 11_A.28 firmwares using "ubuntu ozip to zip" and files appear identical and patched successfully using Magisk. The boot.img provided in the link is not the same, I wouldn't use it.
Did you find out if some older version of firmware has fastboot not disabled by company?
Many thanks for taking time to read reply.
Click to expand...
Click to collapse
Still no luck. Fastboot is disabled.
After a couple of months of deep research I have managed to find a solution to unlock bootloader and root our SMAO15F device.
1st step: If your on android 10 it's possible to unlock bootloader even if our device has that option by default.
Fortunately with the newly released of official android 11 we are able to do so all you gotta do is you have to jump to android 11 if you're still on android Q then proceed to the unlocking method.
2nd step: after bootloader unlock download this .tar file (patched boot image for android 11 samsung sma015f).
Final process: Go to download mode, open latest odin and import the attached file with the AP button, phone will automatically restart after the process or restart it manually if not,
voila our samsung a01 is now rooted without twrp. Now we just have to wait for someone to make a custom twrp for our device or wait for official twrp or kindly please let me know if there is.
Credits: to that russian guide for the patched boot file for android11 (sma015f)
Cool bro!, but, how i'm unlock the bootloader for A01?
ROOT WITH MAGISK 23 WORKING 100% ON ANDROID 11 JUST UPGRADE UNLOCK BOOTLOADER AND FOLLOW THE INSTALLATION GUIDE https://topjohnwu.github.io/Magisk/install.html
Kaik Ricardo said:
Cool bro!, but, how i'm unlock the bootloader for A01?
Click to expand...
Click to collapse
Vol+ and Vol - and plug the usb cable then long press vol+
Hello,
Finally, I can unlock the bootloader, flash twrp and root my Samsung Galaxy A01 (a01q) (SM-A015M).
All I need is just update to Android 11 and then I can unlock the bootloader and flash the magisk patched boot.img together the patched vbmeta.img.
I can flash TWRP using the image file "TWRP_3.5.2_A015F.img" sent by @tariqa
How To Root Samsung A01 (a015f/DS)
Hello, I want to ask how to root samsung galaxy a01 (a015f) , i want to instal f.lux for better blue light filter, Thanks!
forum.xda-developers.com
Thank you very much
1. Unlock your bootloader enter in download mode Vol+ + Vol- + USB conected to pc (Keep in mind that by doing this you will lose your files, it is advisable to make a backup of your photos, music, etc.)
2. Once you start your cell phone install magisk manager, Choosing the boot.img file of your rom into the app (Tip: Only!!! If your model is SM-A015M Android 11 I leave you my own modified boot.img to flash:
File on MEGA
mega.nz
Otherwise, you can download the firmware (3.79 gb) and extract the boot.img from the firmware of your model SM-A015 M / F ... Android 10, Android 11... etc. And No need for pc
https://samfrew.com/model/SM-A015M/
3. The image will begin to flash
4. When it restarts you will have Root on the cell phone!
------------------------------------------------------------------------------------------------------------------------------------------------
Extra: If you need the custom recovery I give you the link with my TWRP which is installed through the Odin program on a PC (this step does not delete your files)
File on MEGA
mega.nz
Keep in mind that to install TWRP you must deactivate the DM-VERITY & FORCEENCRYPT DISABLER I leave it in a link:
Zackptg5 - Android
zackptg5.com
This is a module that can be installed via magisk, which is necessary to decrypt the system ... so once TWRP is installed, it is advisable to uninstall it via Magisk to avoid R / W errors
Marti_Fajardo said:
After a couple of months of deep research I have managed to find a solution to unlock bootloader and root our SMAO15F device.
1st step: If your on android 10 it's possible to unlock bootloader even if our device has that option by default.
Fortunately with the newly released of official android 11 we are able to do so all you gotta do is you have to jump to android 11 if you're still on android Q then proceed to the unlocking method.
2nd step: after bootloader unlock download this .tar file (patched boot image for android 11 samsung sma015f).
Final process: Go to download mode, open latest odin and import the attached file with the AP button, phone will automatically restart after the process or restart it manually if not,
voila our samsung a01 is now rooted without twrp. Now we just have to wait for someone to make a custom twrp for our device or wait for official twrp or kindly please let me know if there is.
Credits: to that russian guide for the patched boot file for android11 (sma015f)
Click to expand...
Click to collapse
after flashing the AP, the phone won't boot and says can't load android system.
edit: i patched my own AP with Magisk and it worked.
So i managed to upgrade my samsung a01m/ds to android 11 & i had unlocked the bootloader. Afterwards i had use the magisk rooting process, then flashed a boot.img that i had extracted from firmware (if needed i will upload) then the phone restated and took like 7 minutes to start, having said that i setup my device but upon doing so i noticed i was not able to use wifi but i had mobile data , managed to get in and install root checker pro and i had root but there was root( will leave an image ) but i didn't enjoy the fact that the wifi was not working, my hotspot wasn't working. i never managed to install TWRP becuase i was tampering a little more and trip my knox. it's been like 2 months since it trip and the OEM UNLOCKING in developer options is yet to be visible so i can unlock the oem and start a fesh.
Marti_Fajardo said:
After a couple of months of deep research I have managed to find a solution to unlock bootloader and root our SMAO15F device.
1st step: If your on android 10 it's possible to unlock bootloader even if our device has that option by default.
Fortunately with the newly released of official android 11 we are able to do so all you gotta do is you have to jump to android 11 if you're still on android Q then proceed to the unlocking method.
2nd step: after bootloader unlock download this .tar file (patched boot image for android 11 samsung sma015f).
Final process: Go to download mode, open latest odin and import the attached file with the AP button, phone will automatically restart after the process or restart it manually if not,
voila our samsung a01 is now rooted without twrp. Now we just have to wait for someone to make a custom twrp for our device or wait for official twrp or kindly please let me know if there is.
Credits: to that russian guide for the patched boot file for android11 (sma015f)
Click to expand...
Click to collapse
I managed to root my phone using this method but after I rooted, my wifi was stuck at turning on. I would then restore it to its stock firmware to have the wifi back and it did, but then I rooted again and wifi got stuck again. How do I fix this problem?
Johnmarr said:
I managed to root my phone using this method but after I rooted, my wifi was stuck at turning on. I would then restore it to its stock firmware to have the wifi back and it did, but then I rooted again and wifi got stuck again. How do I fix this problem?
Click to expand...
Click to collapse
Did you try to enable or disable MAC randomizing?
how
VD171 said:
Did you try to enable or disable MAC randomizing?
Click to expand...
Click to collapse
How do I enable or disable mac randomizing?
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
I just share my experience. Do it at your own risk
I. Unlock bootloader
1. Enable developer options by tapping build number 7 times
2. Go to Developer options, turn on OEM unlocking
3. Turn off Tab A7 Lite, connect it to the computer while holding Volume Up and Volume Down keys until you see the bootloader screen
4. Long-press Volume Up key to enter Device unlock mode
5. Press Volume Up key to confirm and unlock the bootloader
Done
II. Root
1. Unlock bootloader (skip this if you have done it)
2. (On PC) Extract boot.img.lz4 from Stock AP...tar file, then copy it to Tab
3. (On Tab) Install ZArchiver to extract boot.img from boot.img.lz4
4. (On Tab) Install Magisk and patch the boot.img that you have just extracted from step 3
5. (On PC) Copy magisk_patched.img (in Tab\download) to pc, rename it to boot.img
6. (On PC) Use 7zip to pack boot.img from step 5 into boot.tar
7. (On PC) Use odin to flash boot.tar from step 6 (in AP slot)
8. After Tab reboot, open Magisk, update to newest version, open again and let it install something then reboot
Done
In case you don't want to do a full step by step as above, you can use my already patched boot.tar below, just download and flash it via odin. After flashing and reboot, open Magisk, update to newest version, open again and let it install something then reboot
For T225XXU1AUJ1:
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
For T225XXU1AUL1:
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
III. Debloat
1. Root
2. Open Magisk and install the following module:
https://www.mediafire.com/file/nlvw540lpgllygj/physwizz-debloater-module-v3.zip/file
3. Reboot
Sorry, I did put the tablet in download mode, but it says the boot image cannot be flashed with odin becaouse its custom binary even if developer mode is on and OEM unlock is on... Strange! Any Ideas?
Bercsenyilaszlo said:
Sorry, I did put the tablet in download mode, but it says the boot image cannot be flashed with odin becaouse its custom binary even if developer mode is on and OEM unlock is on... Strange! Any Ideas?
Click to expand...
Click to collapse
What binary is your Tab firmware ?
Sorry it was alright I just didnt press long enough the volume up button its different from a short press when unlocking the OEM.... Thats all a long press needed instead a short one.. Otherwise boot loader will stay locked.
Thanks for the thread GREAT WORK!
thatha said:
I just share my experience. Do it at your own risk
I. Unlock bootloader
1. Enable developer options by tapping build number 7 times
2. Go to Developer options, turn on OEM unlocking
3. Turn off Tab A7 Lite, connect it to the computer while holding Volume Up and Volume Down keys until you see the bootloader screen
4. Long-press Volume Up key to enter Device unlock mode
5. Press Volume Up key to confirm and unlock the bootloader
Done
II. Root
1. Unlock bootloader (skip this if you have done it)
2. (On PC) Extract boot.img.lz4 from Stock AP...tar file, then copy it to Tab
3. (On Tab) Install ZArchiver to extract boot.img from boot.img.lz4
4. (On Tab) Install Magisk and patch the boot.img that you have just extracted from step 3
5. (On PC) Copy magisk_patched.img (in Tab\download) to pc, rename it to boot.img
6. (On PC) Use 7zip to pack boot.img from step 5 into boot.tar
7. (On PC) Use odin to flash boot.tar from step 6 (in AP slot)
8. After Tab reboot, open Magisk, update to newest version, open again and let it install something then reboot
Done
In case you don't want to do a full step by step as above, you can use my already patched boot.tar below, just download and flash it via odin. After flashing and reboot, open Magisk, update to newest version, open again and let it install something then reboot
For T225XXU1AUJ1:
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
For T225XXU1AUL1:
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
III. Debloat
1. Root
2. Open Magisk and install the following module:
physwizz-debloater-module-v2
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
3. Reboot
Click to expand...
Click to collapse
Can you do files for a T220xxu1au13? Would love to debloat mine and start using it as a offline game tablet.
IronGearGaming said:
Can you do files for a T220xxu1au13? Would love to debloat mine and start using it as a offline game tablet.
Click to expand...
Click to collapse
Yes if I have some free time to download your firmware. If you can extract boot.img.lz4 from your firmware and send me, I can do it soon
I don't have boot . tar
master12311 said:
I don't have boot . tar
Click to expand...
Click to collapse
What country ?
england
Hello,
thank for your work I succeeded with root but I mistakenly installed a faulty twrp which bricked the tablet. I have access to download mode but I can't reinstall a functional version ("security fail tip) the only thing that odin accepts is your great work "patched boot.tar" but the boot still blocks. an idea to unlock it. thanks in advance
antineas said:
Hello,
thank for your work I succeeded with root but I mistakenly installed a faulty twrp which bricked the tablet. I have access to download mode but I can't reinstall a functional version ("security fail tip) the only thing that odin accepts is your great work "patched boot.tar" but the boot still blocks. an idea to unlock it. thanks in advance
Click to expand...
Click to collapse
I also bricked my tablet, and the only firmware ODIN accepted was downloaded by Frija. Got errors from Sam firm and Galaxyfirm.
antineas said:
Hello,
thank for your work I succeeded with root but I mistakenly installed a faulty twrp which bricked the tablet. I have access to download mode but I can't reinstall a functional version ("security fail tip) the only thing that odin accepts is your great work "patched boot.tar" but the boot still blocks. an idea to unlock it. thanks in advance
Click to expand...
Click to collapse
What is your firmware and country before ?
thatha said:
What is your firmware and country before ?
Click to expand...
Click to collapse
France and T225XXU1AUJ1
jorjee said:
I also bricked my tablet, and the only firmware ODIN accepted was downloaded by Frija. Got errors from Sam firm and Galaxyfirm.
Click to expand...
Click to collapse
thank I ve many error too whith Odin. I try to find it
antineas said:
thank I ve many error too whith Odin. I try to find it
Click to expand...
Click to collapse
What odin version are you using ?
antineas said:
Hello,
thank for your work I succeeded with root but I mistakenly installed a faulty twrp which bricked the tablet. I have access to download mode but I can't reinstall a functional version ("security fail tip) the only thing that odin accepts is your great work "patched boot.tar" but the boot still blocks. an idea to unlock it. thanks in advance
Click to expand...
Click to collapse
Flash stock recovery via odin in AP slot
recovery
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
thatha said:
Flash stock recovery via odin in AP slot
recovery
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
Click to expand...
Click to collapse
Hello, thank you for taking the time to help me. the recovery is accepted and gave me back access to the recovery. A real progress but it still does not boot I did a factory reset without effect. I am not sure of the version I put image of the recovery in case .sorry I don't have much knowledge in these manipulations. I am only a copier...... But having access to recovery gives me hope. thank you very much
I use Odin 3_v3.14.
antineas said:
Hello, thank you for taking the time to help me. the recovery is accepted and gave me back access to the recovery. A real progress but it still does not boot I did a factory reset without effect. I am not sure of the version I put image of the recovery in case .sorry I don't have much knowledge in these manipulations. I am only a copier...... But having access to recovery gives me hope.
Click to expand...
Click to collapse
I think you should download and flash latest firmware. You can download from this site:
samfw.com
Hello,
thank you for your help i have repaired the boot. it was a question of firmware indeed but beware for tablets version T225 "N" the firmware is not the same and is more difficult to find. they are not offered on dedicated sites.