Database Develop

Stuck in Bootloop after installing SuperSu using TWRP for samung M20

So, I was on Android 10, I was trying to root using Magisk & TWRP as mentioned in this XDA Post.
Title:: "[RECOVERY] TWRP 3.3.0 for Galaxy M20" , By DarkLord1731, Senior Member on 3rd March 2019, 08:54 AM (**mentioning because i cant post link**)
Even after multiple attempts, I was unable to install
1. no-verity-opt-encrypt 2. RMM Bypass zip using TWRP.
Both kept on failing even when i tried different versions.
-------------
Later on when i tried flashing SuperSU , phone got bootlocked
still stuck, any help would be appreciated.
-------
Installation Steps:
- First, make sure your phone isn't RMM Locked.
- Download Odin3 v3.13.1, Samsung USB Drivers, latest TWRP's tar for your variant, latest no-verity-opt-encrypt zip, latest Magisk.zip and RMM Bypass zip by Black Mesa, and copy all of them to your external sd card.
- Go to Settings App, Developer Options and enable OEM Unlock (If you don't see Developer Setings, go into About phone>Software info and tap "Build number" 10 times to show Developer Options menu).
- Do a backup of all your important data and files in your phone.
- Shutdown the phone. Once it's off, Power it On in Download Mode (Connect your phone to your PC, press and hold Power, Vol + and Vol - buttons together )
- Open Odin3, go in Option section and untick "Auto-reboot". Once that click the "AP" button and select the TWRP tar you downloaded before, then press the "Start" button.
- Once Odin3 finished to flash the recovery (you should see a "PASS" message), force reboot your phone (Press and hold Power and Vol - buttons together) and once the screen is off, press and hold Power and Vol + buttons together to boot in TWRP.
- Once TWRP is booted you first need to decrypt your /data partition. To do so touch Wipe>Format Data and follow the instructions in screen.
- Once it finished go back at the home screen and touch Reboot>Recovery. TWRP should be able to mount your data partition. Now flash the no-verity-opt-encrypt, Magisk(necessary to prevent bootloops) and RMM Bypass zip you downloaded before (touch Install and select each zip to flash it)
- You're now able to reboot to your OS without re-encrypting /data partition and without RMM Prenormal lock.

Akshay4497 said:
So, I was on Android 10, I was trying to root using Magisk & TWRP as mentioned in this XDA Post.
Title:: "[RECOVERY] TWRP 3.3.0 for Galaxy M20" , By DarkLord1731, Senior Member on 3rd March 2019, 08:54 AM (**mentioning because i cant post link**)
Even after multiple attempts, I was unable to install
1. no-verity-opt-encrypt 2. RMM Bypass zip using TWRP.
Both kept on failing even when i tried different versions.
-------------
Later on when i tried flashing SuperSU , phone got bootlocked
still stuck, any help would be appreciated.
-------
Installation Steps:
- First, make sure your phone isn't RMM Locked.
- Download Odin3 v3.13.1, Samsung USB Drivers, latest TWRP's tar for your variant, latest no-verity-opt-encrypt zip, latest Magisk.zip and RMM Bypass zip by Black Mesa, and copy all of them to your external sd card.
- Go to Settings App, Developer Options and enable OEM Unlock (If you don't see Developer Setings, go into About phone>Software info and tap "Build number" 10 times to show Developer Options menu).
- Do a backup of all your important data and files in your phone.
- Shutdown the phone. Once it's off, Power it On in Download Mode (Connect your phone to your PC, press and hold Power, Vol + and Vol - buttons together )
- Open Odin3, go in Option section and untick "Auto-reboot". Once that click the "AP" button and select the TWRP tar you downloaded before, then press the "Start" button.
- Once Odin3 finished to flash the recovery (you should see a "PASS" message), force reboot your phone (Press and hold Power and Vol - buttons together) and once the screen is off, press and hold Power and Vol + buttons together to boot in TWRP.
- Once TWRP is booted you first need to decrypt your /data partition. To do so touch Wipe>Format Data and follow the instructions in screen.
- Once it finished go back at the home screen and touch Reboot>Recovery. TWRP should be able to mount your data partition. Now flash the no-verity-opt-encrypt, Magisk(necessary to prevent bootloops) and RMM Bypass zip you downloaded before (touch Install and select each zip to flash it)
- You're now able to reboot to your OS without re-encrypting /data partition and without RMM Prenormal lock.
Click to expand...
Click to collapse
Don't touch twrp with stock rom, it is quite complicated.
Guide:
1. Download magisk manager(mm) and stock rom
(Backup data using Smart Switch on windows)
2. Copy AP file into internal storage
3. Open mm and choose install magisk
4. Choose select and patch a file
5. Patch the AP file.
6. Use Odin flash the AP file with other files(BL, CSC,...)
7. Reboot( all of ur data will be wiped)
8. Restore data
9. Enjoy
(P/s: i thought i posted last week but just found out that i didn't click post)

Try to root using Magisk to patch boot.img
it is wrking on all samsung devices even with last update of android 10.

TWRP Recovery for Samsung M31s

Hello everyone,
I am looking for TWRP recovery image for Samsung M31s. Everywhere I seem to only find either M30s or M31. Kindly help. Unable to root the device so far. Thanks.

ROOT without TWRP
1. Download the latest firmware to your phone.
2. copy boot.img from the downloaded firmware to the phone:
2.1 On a PC, go to the folder with your unpacked firmware and find the AP file.
2.2 Open it with the 7-Zip archiver (download 7-Zip from here - https://github.com/mcmilk/7-Zip-zstd/releases/tag/19.00-v1.4.5-R3)
2.3 Inside there will be a file boot.img.lz4 - open it.
2.4 It contains only 1 boot.img file - unpack it and copy it to your phone.
3. Patch the file with magisk
3.1 Install Magisk Manager on the phone. (https://github.com/topjohnwu/Magisk/releases/download/v23.0/Magisk-v23.0.apk)
3.2 Open Magisk and click INSTALL. Patch boot image. Select our boot.img file. Install.
3.3 When finished, the magisk_patched.img file will appear in the Download folder
3.4 Copy it to a PC, rename it to boot.img and archive it to TAR via 7-zip.
3.5 There should be a boot.tar file inside which the boot.img file
4. Stitching.
4.1 Turn off the phone. We transfer to Download mode (hold down 2 volume buttons and connect with a cable to the PC).
4.2 Open Odin.
4.3 Select only the AP field in which we specify the boot.tar file. Do not touch the rest of the fields (leave them empty).
4.4 Press start.
4.5 The phone must flash and turn on with root.

After all these steps, i had to open Magisk again and it updated itself, and now the phone is rooted. Thanks everyone.

As a summary, after installing Magisk in recovery (starting from power off):
(Power up normally) → (System with NO Magisk)
(Recovery Key Combo) → (Splash screen) → (Release all buttons) → (System with Magisk)
(Recovery Key Combo) → (Splash screen) → (Long press volume up) → (Recovery Mode)

@sammiev - I didn't understand. This is summary of?
Once the boot.tar file is stiched using Odin, a normal reboot would launch the rooted OS, right?

abhishekgupta92 said:
After all these steps, i had to open Magisk again and it updated itself, and now the phone is rooted. Thanks everyone.
Click to expand...
Click to collapse
does everything work well?

abhishekgupta92 said:
@sammiev - I didn't understand. This is summary of?
Once the boot.tar file is stiched using Odin, a normal reboot would launch the rooted OS, right?
Click to expand...
Click to collapse
This is for root without TWRP
The second choice would boot you in root mode after doing what @pipkakill posted.
(Recovery Key Combo) → (Splash screen) → (Release all buttons) → (System with Magisk)

Samsung Galaxy stuck in download mode loop when TWRP is flashed on Odin

Hi, I recently flashed the latest TWRP for S10 (twrp-3.5.2_9-3-beyond1lte.img) using Odin.
In the Odin app, everything appears to be successful, however, the phone now shows the warning for the bootloader being unlocked and immediately switches to a Download Mode screen. At the top left of the screen it shows this:
ODIN MODE (AVB Fail)
recovery: Error validating footer. (0)
recovery: Error verifying vbmeta image: invalid vbmeta header (6)
VBMETA 6973FXXSBFUF3, 41014081R
No matter how many times I turn the phone off and on, it constantly keeps going back to this screen. The only way I can fix this is by flashing the stock firmware onto the phone with Odin. IfI try to flash TWRP again after this, it just repeats the previous problem. TWRP was working yesterday when I was using it, sol am really confused
as to why this issue is occurring.
This issue seems to have started after I flashed Lineage 18.1 onto my phone through TWRP. Lineage was constantly launching so I turned the phone off and went back onto TWRP and deleted my data, OS and internal storage. I don't know how this would affect anything though, but I can't access TWRP since.
If anyone would have any idea how to resolve this problem and allow me to access TWRP on my phone again, it would be greatly
appreciated. Thank you
(My phone model number is SM-G973F/DS).

Did you ever manage to get this solved?
I'm having the same issue with my S10e.
After flashing TWRP it goes into download mode and whatever I try it always boots into download mode until I flash the stock rom and start over again.

My phone is Samsung Galaxy S10 (SM-G973F).
I have never used Lineage, but I read that Lineage has problems with TWRP.
I root Stock ROM with Magisk. With Magisk I patched AP file, and install BL, CP, CSC and patched AP with ODIN.
After that I install TWRP and vbmeta.
TWRP.img I patched with Magisk. Version of Magisk is 25.1. After I patched .img with Magisk, I copy it on PC with ADB. After copy on PC, I convert patched .img to .tar and it install with ODIN.
First of all, transfer the patched TWRP image (magisk_patched.img) file from your phone’s storage to the PC.
Open the folder where the file was transferred.
Hold the SHIFT key on the keyboard and right-click on any empty space inside the folder.
Then select the ‘Open PowerShell window here’ option.
Now, enter the following command to rename the ‘magisk_patched.img’ to ‘recovery.img’:
mv magisk_patched.img recovery.img
Instead of magisk_patched.img, type the name you got when you patched the .img with Magisk and then Enter.
For me it looks like this:
Next command for Galaxy S10 is: tar cf twrp-beyond1lte.img.tar recovery.img
Now you can install TWRP with ODIN.
I installed TWRP.tar and vbmet.tar with ODIN.

Thanks!
I will give it a try.
Where did you get the vbmeta file?
Or did you have create it yourself? - That's one part I'm unsure of.

Cilvaring said:
Thanks!
I will give it a try.
Where did you get the vbmeta file?
Or did you have create it yourself? - That's one part I'm unsure of.
Click to expand...
Click to collapse
Before root Android.
From here:
[RECOVERY][OFFICIAL][3.6.1-x] TWRP for Galaxy S10/e/+/5G Exynos
Official TWRP 3.6.1-* For Galaxy S10/e/+/5G Only for exynos variants - G970F / G973F / G975F / G977B (Europe - Global, Single/Dual-SIM), G970N / G973N / G975N / G977N (South Korea) Disclaimer I am not responsible for bricked devices, dead SD...
forum.xda-developers.com
Here you can download TWRP, vbmeta and multidisabler samsung.
For vbmeta and multidisabler samsung you need click on Instructions: Odin (Windows) CLICK TO SHOW CONTENT. Here are links for download.
Boot into TWRP, Flash Multi-Disabler zip, and Format the Data
Press Power and Volume Down buttons together to exit Download Mode.
As soon as the screen turns off, quickly press and hold the Power, Volume Up, and Bixby buttons together until the Bootloader Warning message appears.
Once the Bootloader Warning screen appears, release the Bixby and Power buttons, and keep holding the Volume Up button to enter TWRP recovery mode.
Tap on the ‘Install’ button in TWRP.
Navigate to the MicroSD card and select the Multi-Disabler ZIP file.
Swipe the button on the screen to flash the Multi-Disabler zip file on your Galaxy S10.
Once the file has been flashed successfully, go to ‘Wipe’ > ‘Format Data’ in TWRP.
Enter ‘Yes’ in the field to format the data partition/factory reset the device.
Finally, go to the ‘Reboot’ menu in TWRP and select ‘Recovery’ to boot your Samsung Galaxy S10 device into rooted OS with.

this method of patching is good, thanks for sharing!
ZmisiS said:
My phone is Samsung Galaxy S10 (SM-G973F).
I have never used Lineage, but I read that Lineage has problems with TWRP.
I root Stock ROM with Magisk. With Magisk I patched AP file, and install BL, CP, CSC and patched AP with ODIN.
After that I install TWRP and vbmeta.
TWRP.img I patched with Magisk. Version of Magisk is 25.1. After I patched .img with Magisk, I copy it on PC with ADB. After copy on PC, I convert patched .img to .tar and it install with ODIN.
First of all, transfer the patched TWRP image (magisk_patched.img) file from your phone’s storage to the PC.
Open the folder where the file was transferred.
Hold the SHIFT key on the keyboard and right-click on any empty space inside the folder.
Then select the ‘Open PowerShell window here’ option.
Now, enter the following command to rename the ‘magisk_patched.img’ to ‘recovery.img’:
mv magisk_patched.img recovery.img
Instead of magisk_patched.img, type the name you got when you patched the .img with Magisk and then Enter.
For me it looks like this:
Next command for Galaxy S10 is: tar cf twrp-beyond1lte.img.tar recovery.img
Now you can install TWRP with ODIN.
I installed TWRP.tar and vbmet.tar with ODIN.
Click to expand...
Click to collapse

Foxlegendary said:
this method of patching is good, thanks for sharing!
Click to expand...
Click to collapse
You are welcome.

[RECOVERY][UNOFFICIAL] TWRP for SM-p205 (Tab A 8.0 2019 Exynos model)

Flash at your own Risk !!!
Tested Working:
Flash gsi roms
How to Flash:
1. Reboot Device to Downloadmode
2. Unlock Bootloader
3. Install adb and Fastboot driver and Device Drivers ( Google will Help )
4. Download the VBMeta-disabled.tar and the twrp-3.6.0_9-0-p205.tar and the multidisable script
5. Download Odin3 from Attachments and start Odin on PC
6. In Odin Press on Options and untick Auto Reboot
7. Flash VBMeta-disabled.tar with Odin ( In Odin click on AP - select the vbmeta-disabled.tar and press start )
8. After flash vbmeta without errors press on AP and select twrp-3.6.0_9-0-p205.tar and press on start
9. If all is Flashed without errors longpress power and vol- on device
10. instantly after device goes Blackscreen press and hold power and vol+ for 5-8 seconds to boot to TWRP
11.Click Wipe in twrp ,
12.Click Advanced Wipe
13.Select the Data checkbox
14.Click Repair of Change File System
15.Click Change File System
16.Click Ext4
17.Swipt to change(Warn !!! that will wipe your data)
18.Cilck Black
19.Go back TWRP maim screen
11.Copy the multidisable script to the device
12. Run multidisabler script on TWRP via adb or TWRP TermInal
13. Reboot
The TWRP file:
Twrp_sm-p205 - Google Drive
drive.google.com

Deleted

NOTE : the twrp isn't made by me i found it at
Pledge for TWRP for Tab A with S-pen (SM-P205)?
Hi! I am relativelly new at XDA. I think i read somewhere that pledging cash for help to get a certain thing done is allowed but am a bit unsure. So excuse me if this post is perhaps slightly against the rules or so. Moderators can of course in...
forum.xda-developers.com

How To Guide How to root SM-X200

Hello guys. I failed several times rooting this device and finally managed to root.
You need to extract AP tar and then replace the boot.img with a magisk patched one.
You then need to re tar the file using 7zip and flash as normal.
AP CSC HOME CSC and BL

If there's enough demand I'll write a proper guide. Also if soft bricked you need to press both volume buttons and plug in usb at right point on restart.

jameswalker457 said:
Hello guys. I failed several times rooting this device and finally managed to root.
You need to extract AP tar and then replace the boot.img with a magisk patched one.
You then need to re tar the file using 7zip and flash as normal.
AP CSC HOME CSC and BL
Click to expand...
Click to collapse

Thanks @jameswalker457
Which one did you use CSC_HOME or CSC?
When I run with CSC, I get a 'fail' in ODIN However, it does run with CSC_HOME, BL and the patched AP - but it doesn't actually root the device.
Greatful for your help.
Thanks

Used BL AP (with patched boot.img) CSC and HOME_CSC in the userdata

kevinsims said:
Thanks @jameswalker457
Which one did you use CSC_HOME or CSC?
When I run with CSC, I get a 'fail' in ODIN However, it does run with CSC_HOME, BL and the patched AP - but it doesn't actually root the device.
Greatful for your help.
Thanks
Click to expand...
Click to collapse
See above. Missed the quotation

I'm not sure why we need a third thread for this:
SM-X200 root failed...
It's now a bricked tablet after a boot loop, I think should wait to magisk get an update. It won't power on or charge I think. I have two days trying to power on in several times and many key conbinations. No Samsung logo or something. Can I do...
forum.xda-developers.com
The best way to root samsung tab a8 2021 pls
Android 11 I got fast as f boot loop solution below btw An 4 gamers I got fps/ping boost solution below to
forum.xda-developers.com
I still do not have root. What I did:
1. unlocked bootloader
2. install magisk manager 24.3
3. Download X200XXU1AVC1 from Samfw
4. unzip the firmware
5. Untar the AP tar file
6. Extract boot.img, send to device, and patch with magisk 24.3. Patched boot is magisk_patched-24300-9Iez2.img
7. Replace boot.img with the newly patched one (renamed to boot.img)
8. Create a tar file from the AP folder using
" tar -C AP_folder -cvf AP_patched.tar ."
9. "adb reboot bootloader" to download mode
10. open Odin v3.14.1 and add BL, HOME_CSC, and the AP_patched.tar
9. Flash via Odin, exit download mode, enter stock recovery, factory reset
For some reason I can't get from download mode to recovery w/o first booting the fresh android.
No boot loop, but no root either.

These are the file names I got from Samfw:
AP_X200XXU1AVC1_CL23784803_QB49828201_REV00_user_low_ship_MULTI_CERT_meta_OS11.tar.md5
BL_X200XXU1AVC1_CL23784803_QB49828201_REV00_user_low_ship_MULTI_CERT.tar.md5
HOME_CSC_OMC_XAR_X200XAR1AVC1_CL23784803_QB49838021_REV00_user_low_ship_MULTI_CERT.tar.md5
The md5sum of the files:
AP stock: fa97e5cee1deaf26175b27d26df94266
AP patched: 006b12f713fc3caa127bc5cba01ae4b9
BL: 2172ca468462a46917d78e94157aed54
HOME_CSC: 5ede57b9ffe8059f3166dd5de6ef8721

The tar file worried me. It had file names like ./boot.img instead of boot.img. So I created a new file, with the patched boot.img, this way:
cd AP_folder
tar -cvf ../AP_patched.tar *
Then flashed that. Took longer than the previous tar.
On reboot, it asks me to press PWR to accept boot loader unlocked. Then a splash screen saying: unapproved software, then a few boot loops.
I got to recovery, factory reset, the tablet does the LONG boot, does the initial setup thing.
Install Magisk Manager, and root! Google Play still works.
Whoopee! I can now wait for a working TWRP.

jameswalker457 said:
Hello guys. I failed several times rooting this device and finally managed to root.
You need to extract AP tar and then replace the boot.img with a magisk patched one.
You then need to re tar the file using 7zip and flash as normal.
AP CSC HOME CSC and BL
Click to expand...
Click to collapse
Hello, I have a problem/doubt. I have the files AP, BP... etc I use 7zip to extract the boot.img ..... if I unzip all the AP XXX.tar.md5 the 7zip warns me that there is data after the file, it warns me of an error and at the end it stops in the fota . ...when I replace the boot.img in the AP folder by the one corresponding to the patched with Magisk and use the 7zip again to create the .tar the file does not work with ODIN...I do not know what step or mistake I make. Regards
PS: I'm extracting the files instead of unzipping the .tar.md5 to see if that's the problem ....
PS: Root! Thanks Jameswalker457 Cheers! ....
Translated with www.DeepL.com/Translator (free version)

IkeGolden said:
Hello, I have a problem/doubt. I have the files AP, BP... etc I use 7zip to extract the boot.img ..... if I unzip all the AP XXX.tar.md5 the 7zip warns me that there is data after the file, it warns me of an error and at the end it stops in the fota . ...when I replace the boot.img in the AP folder by the one corresponding to the patched with Magisk and use the 7zip again to create the .tar the file does not work with ODIN...I do not know what step or mistake I make. Regards
PS: I'm extracting the files instead of unzipping the .tar.md5 to see if that's the problem ....
PS: Root! Thanks Jameswalker457 Cheers! ....
Translated with www.DeepL.com/Translator (free version)
Click to expand...
Click to collapse
> if I unzip all the AP XXX.tar.md5
That is because a .tar.md5 is a tar file with an md5 concatenated to it.
> use the 7zip again to create the .tar the file does not
The proper tool to create .tar files is "tar".
>PS: I'm extracting the files instead of unzipping the .tar.md5 to see if that's the problem ....
Care to be more specific on how you did that?
>PS: Root! Thanks Jameswalker457 Cheers! ....
Good news.

Have root my SM-X205 (LTE) for 1 Feb Patch level but no go with latest May update.
Getting constant boot loop (exactly same process, magisk boot.bin etc) so rolled back to Feb for now.

lufee84 said:
Have root my SM-X205 (LTE) for 1 Feb Patch level but no go with latest May update.
Getting constant boot loop (exactly same process, magisk boot.bin etc) so rolled back to Feb for now.
Click to expand...
Click to collapse
What firmware version worked, and which failed?
X200XXU1AVC1 worked for me.

Yes, X205XXU1AVC1 works.
No luck with latest X205XXS1AVE1 (May Patch).

garyemiller said:
I'm not sure why we need a third thread for this:
SM-X200 root failed...
It's now a bricked tablet after a boot loop, I think should wait to magisk get an update. It won't power on or charge I think. I have two days trying to power on in several times and many key conbinations. No Samsung logo or something. Can I do...
forum.xda-developers.com
The best way to root samsung tab a8 2021 pls
Android 11 I got fast as f boot loop solution below btw An 4 gamers I got fps/ping boost solution below to
forum.xda-developers.com
I still do not have root. What I did:
1. unlocked bootloader
2. install magisk manager 24.3
3. Download X200XXU1AVC1 from Samfw
4. unzip the firmware
5. Untar the AP tar file
6. Extract boot.img, send to device, and patch with magisk 24.3. Patched boot is magisk_patched-24300-9Iez2.img
7. Replace boot.img with the newly patched one (renamed to boot.img)
8. Create a tar file from the AP folder using
" tar -C AP_folder -cvf AP_patched.tar ."
9. "adb reboot bootloader" to download mode
10. open Odin v3.14.1 and add BL, HOME_CSC, and the AP_patched.tar
9. Flash via Odin, exit download mode, enter stock recovery, factory reset
For some reason I can't get from download mode to recovery w/o first booting the fresh android.
No boot loop, but no root either.
Click to expand...
Click to collapse
Not sure if this helps but i read an article that says you should patch the whole AP tar file rather than extract just the boot.img. Maybe because it patches the recovery and super etc img files too? I havet tried this yet as I cant even get my bootloader unlocked

dan.langridge88 said:
Not sure if this helps but i read an article that says you should patch the whole AP tar file rather than extract just the boot.img. Maybe because it patches the recovery and super etc img files too? I havet tried this yet as I cant even get my bootloader unlocked
Click to expand...
Click to collapse
Dunno where you read that, don't care. This works (as above):
1. unlocked bootloader
2. install magisk manager 24.3
3. Download X200XXU1AVC1 from Samfw
4. unzip the firmware
5. Untar the AP tar file
6. Extract boot.img, send to device, and patch with magisk 24.3. Patched boot is magisk_patched-24300-9Iez2.img
7. Replace boot.img with the newly patched one (renamed to boot.img)
8. Create a tar file from the AP folder using
" cd AP_folder"
" tar -cvf AP_patched.tar ."
9. "adb reboot bootloader" to download mode
10. open Odin v3.14.1 and add BL, HOME_CSC, and the AP_patched.tar
9. Flash via Odin, exit download mode, enter stock recovery, factory reset
Note the fixed "tar" command. Do not use "tar -C".

garyemiller said:
Dunno where you read that, don't care. This works (as above):
1. unlocked bootloader
2. install magisk manager 24.3
3. Download X200XXU1AVC1 from Samfw
4. unzip the firmware
5. Untar the AP tar file
6. Extract boot.img, send to device, and patch with magisk 24.3. Patched boot is magisk_patched-24300-9Iez2.img
7. Replace boot.img with the newly patched one (renamed to boot.img)
8. Create a tar file from the AP folder using
" cd AP_folder"
" tar -cvf AP_patched.tar ."
9. "adb reboot bootloader" to download mode
10. open Odin v3.14.1 and add BL, HOME_CSC, and the AP_patched.tar
9. Flash via Odin, exit download mode, enter stock recovery, factory reset
Note the fixed "tar" command. Do not use "tar -C".
Click to expand...
Click to collapse
OK, I've un-tarred the AP tar.md5 and patched the old boot-img file on the device, renamed it and replaced the original boot.img in the AP "folder".
Steps 8 & 9 are a little confusing for me, if you could expand on those. Can I use 7zip to re-tar? Those look like DOS commands in step 8.

Ar-Pharazon said:
OK, I've un-tarred the AP tar.md5 and patched the old boot-img file on the device, renamed it and replaced the original boot.img in the AP "folder".
Steps 8 & 9 are a little confusing for me, if you could expand on those. Can I use 7zip to re-tar? Those look like DOS commands in step 8.
Click to expand...
Click to collapse
Slightly expanded:
1. unlocked bootloader
2. install magisk manager 24.3 on the tablet
3. Download X200XXU1AVC1 firmware from Samfw onto PC
4. unzip the X200XXU1AVC1 firmware zip file
5. Make a directory for the AP tar contents
"mkdir AP"
6. Untar the AP tar file into directory AP, all on one line:
"tar -xvf AP_X200XXU1AVC1_CL23784803_QB49828201_REV00_user_low_ship_MULTI_CERT_meta_OS11.tar.md5 -C AP"
7. Change the current directoy to the AP directory:
"cd AP"
8. Using adb send boot.img, to the tablet,.
9. Patch boot.img with magisk 24.3. Patched boot is magisk_patched-24300-9Iez2.img
10. Using adb copy magisk_patched-24300-9Iez2.img from the tablet and into the AP directory.
11. Rename magisk_patched-24300-9Iez2.img to boot.img:
"mv magisk_patched-24300-9Iez2.img boot.img"
12 Create a tar file from the AP directory Note the space and period(".") after ".tar":
" tar -cvf AP_patched.tar ."
13. Use adb on PC to enter download mode on tablet:
"adb reboot bootloader"
14. open Odin v3.14.1 and add BL, HOME_CSC, and the AP_patched.tar as files to be flashed.
15. Flash via Odin, exit download mode, enter stock recovery, factory reset
How about that?

garyemiller said:
Slightly expanded:
1. unlocked bootloader
2. install magisk manager 24.3 on the tablet
3. Download X200XXU1AVC1 firmware from Samfw onto PC
4. unzip the X200XXU1AVC1 firmware zip file
5. Make a directory for the AP tar contents
"mkdir AP"
6. Untar the AP tar file into directory AP, all on one line:
"tar -xvf AP_X200XXU1AVC1_CL23784803_QB49828201_REV00_user_low_ship_MULTI_CERT_meta_OS11.tar.md5 -C AP"
7. Change the current directoy to the AP directory:
"cd AP"
8. Using adb send boot.img, to the tablet,.
9. Patch boot.img with magisk 24.3. Patched boot is magisk_patched-24300-9Iez2.img
10. Using adb copy magisk_patched-24300-9Iez2.img from the tablet and into the AP directory.
11. Rename magisk_patched-24300-9Iez2.img to boot.img:
"mv magisk_patched-24300-9Iez2.img boot.img"
12 Create a tar file from the AP directory Note the space and period(".") after ".tar":
" tar -cvf AP_patched.tar ."
13. Use adb on PC to enter download mode on tablet:
"adb reboot bootloader"
14. open Odin v3.14.1 and add BL, HOME_CSC, and the AP_patched.tar as files to be flashed.
15. Flash via Odin, exit download mode, enter stock recovery, factory reset
How about that?
Click to expand...
Click to collapse
I'm guessing those are Linux commands?
In any event, I made 7zip re-tar the AP folder with the patched boot.img, but it ends in .tar.tar
Is this an issue, or should/can it be renamed .tar.md5 like the original?

Ar-Pharazon said:
I'm guessing those are Linux commands?
In any event, I made 7zip re-tar the AP folder with the patched boot.img, but it ends in .tar.tar
Is this an issue, or should/can it be renamed .tar.md5 like the original?
Click to expand...
Click to collapse
I do them on Linux, but they can also work on WinBlows. Since I do not use M$ products, I can only say I've seen those commands work on WinBlows, but can't say how to set that up.
I also can't help you with 7zip, it can run on Linux, but never use it myself.
People have problems when they don't use "real" tar, so don't. Save yourself the pain.
You do not need to convert the .tar to a .tar.md5. Odin will use either file type. A .tar.md5 file is a .tar file with its md5 hash appended. Odin can use the file to verify the .tar integrity, but that is optional.