Related
Visit this link for Rooting A50s with Magisk v19.3 ( Magisk Manager Custom Channel Update ):
https://forum.xda-developers.com/galaxy-a50s/how-to/guide-root-galaxy-a50s-magisk-v19-3-t4001271
Complete Guide for Rooting Samsung Galaxy A50s using Magisk only ( tested on SM-A507FN ), You need Latest Magisk Manager ( MagiskManager-v7.3.4.apk ) and Stock ROM:
1. Download the firmware Galaxy A50s (SM-A507FN).
2. Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5. Copy AP tar file and MagiskManager-v7.3.4.apk to your phone.
3. Install Magisk Manager ( MagiskManager-v7.3.4.apk ) on your phone.
4. In Magisk Manager: Install → Install → Select and Patch a File
5. Select the AP tar file. Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar. Copy magisk_patched.tar the tar file to your PC
6. Reboot to Bootloader: Turn Power Off. Press and hold Volume Up key + Power Key, When Samsung Logo appears release Power Key only, keep pressing Volume Up key until Android Recovery Mode Appears. Select Reboot to bootloader. Connect the phone to PC using USB Cable.
7. Flash magisk_patched.tar as AP in ODIN, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do.
8. Important: Uncheck “Auto Reboot” in Options!
9. Magisk is now successfully flashed to your device! Several steps before you can properly use the device.
10. Full data wipe is mandatory! Do not skip this step.
Press and hold Volume Down + Power Key, when the screen blank quickly press and hold Volume Up + Power key, when Samsung Logo appears release Power key only, keep pressing Volume Up key in the Android Logo screen with text "Erasing", when screen blank again Press and Hold Volume Up + Power key. When Samsung Logo appears release Power Key only, keep pressing Volume Up key until Android Recovery Mode Appears. Select Wipe data / Factory reset.
11. This time to boot to the system with Magisk. Select Reboot system now, and immediately press the Volume Up + Power key, After seeing the bootloader warning screen, release all keys so it can boot to the system.
12. After the device is booted up, do the usual initial setup. It need more time and patient. After finished, You will see Magisk Manager app in app drawer. If not, Install it manually.
13. Connect the phone to Internet, If you can not see Magisk Manager, Install it manually and Open Magisk Manager. It will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
14. Done! You can use Root Checker to check it, Enjoy!
Watch this video https://youtu.be/_psSLUiCZi0
It look like not easy for pressing key combination, so you need read and watch it
Note: Magisk v20 does not work on A50s, don't update it to Magisk v20. FYI: Magisk v20 works stable on A50 and A6 that I have tested. Share here if someone can fix it
This is not A50s group . This is A50 thread
immortalized2018 said:
This is not A50s group . This is A50 thread
Click to expand...
Click to collapse
Well it's same processor same specification.Only 1+ later.
---------- Post added at 11:07 PM ---------- Previous post was at 11:06 PM ----------
redymedan said:
Complete Guide for Rooting Samsung Galaxy A50s using Magisk only ( tested on SM-A507FN ), You need Latest Magisk Manager ( MagiskManager-v7.3.4.apk ) and Stock ROM:
1. Download the firmware Galaxy A50s (SM-A507FN).
2. Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5. Copy AP tar file and MagiskManager-v7.3.4.apk to your phone.
3. Install Magisk Manager ( MagiskManager-v7.3.4.apk ) on your phone.
4. In Magisk Manager: Install → Install → Select and Patch a File
5. Select the AP tar file. Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar. Copy magisk_patched.tar the tar file to your PC
6. Reboot to Bootloader: Turn Power Off. Press and hold Volume Up key + Power Key, When Samsung Logo appears release Power Key only, keep pressing Volume Up key until Android Recovery Mode Appears. Select Reboot to bootloader. Connect the phone to PC using USB Cable.
7. Flash magisk_patched.tar as AP in ODIN, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do.
8. Important: Uncheck “Auto Reboot” in Options!
9. Magisk is now successfully flashed to your device! Several steps before you can properly use the device.
10. Full data wipe is mandatory! Do not skip this step.
Press and hold Volume Down + Power Key, when the screen blank quickly press and hold Volume Up + Power key, when Samsung Logo appears release Power key only, keep pressing Volume Up key in the Android Logo screen with text "Erasing", when screen blank again Press and Hold Volume Up + Power key. When Samsung Logo appears release Power Key only, keep pressing Volume Up key until Android Recovery Mode Appears. Select Wipe data / Factory reset.
11. This time to boot to the system with Magisk. Select Reboot system now, and immediately press the Volume Up + Power key, After seeing the bootloader warning screen, release all keys so it can boot to the system.
12. After the device is booted up, do the usual initial setup. It need more time and patient. After finished, You will see Magisk Manager app in app drawer. If not, Install it manually.
13. Connect the phone to Internet, If you can not see Magisk Manager, Install it manually and Open Magisk Manager. It will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
14. Done! You can use Root Checker to check it, Enjoy!
Watch this video
It look like not easy for pressing key combination, so you need read and watch it
Click to expand...
Click to collapse
Noce jobe my friend
immortalized2018 said:
This is not A50s group . This is A50 thread
Click to expand...
Click to collapse
So, show me the A50s group? You know A50s group does not available right now. It will be moved when A50s group was available. Hi @MikeChannon please move this thread when A50s group has available.
immortalized2018 said:
This is not A50s group . This is A50 thread
Click to expand...
Click to collapse
redymedan said:
So, show me the A50s group? You know A50s group does not available right now. It will be moved when A50s group was available. Hi @MikeChannon please move this thread when A50s group has available.
Click to expand...
Click to collapse
Yes we can move it if we add the A50s (you might need to remind us though)
It's quite common to create a device thread in a "close-match" forum while waiting to see if a new (more precise device) forum is created.
So long as the thread is clearly titled (as this one is) then it's ok.
Mike
@redymedan Very nice works !!
i will try this but i have some concern before root my phone that are
- How can i fully backup all my app and appdata?
the root require full wipe data , factory reset , it is hard for backup everything when we dont have twrp for a50s yet (im not sure if it also require to full wipe when install twrp) and adb backup method only backup some playstore app but not the outside app , or some apps that developer dont give permission to adb backup such as steam
- and what can i do if i accident get bootloop or soft brick? does flash a stock rom will fix these?
HansKila said:
@redymedan Very nice works !!
i will try this but i have some concern before root my phone that are
- How can i fully backup all my app and appdata?
the root require full wipe data , factory reset , it is hard for backup everything when we dont have twrp for a50s yet (im not sure if it also require to full wipe when install twrp) and adb backup method only backup some playstore app but not the outside app , or some apps that developer dont give permission to adb backup such as steam
- and what can i do if i accident get bootloop or soft brick? does flash a stock rom will fix these?
Click to expand...
Click to collapse
For backup all your data, you can try Samsung Smart Switch and If something goes wrong like bootloop, soft brick, Just flash the ROM to make it works again.
@redymedan ok im already backed up all my apps
and have a rom ready to patch but i dont know how to extract the rom to get AP tar file
i downloaded it by sam firm from xda , and its extension is .zip.enc4 and cant be open by 7zip
HansKila said:
@redymedan ok im already backed up all my apps
and have a rom ready to patch but i dont know how to extract the rom to get AP tar file
i downloaded it by sam firm from xda , and its extension is .zip.enc4 and cant be open by 7zip
Click to expand...
Click to collapse
Right click and select extract here or extract to same name with the file name, It will create a folder like the file name. Make sure 7zip installed on your PC
redymedan said:
Right click and select extract here or extract to same name with the file name, It will create a folder like the file name. Make sure 7zip installed on your PC
Click to expand...
Click to collapse
im in step Flashing with Odin , it said something like : only official released binaries are allowed to be flashed
then it stuck , i press down and home to cancel and restart but now it stuck in a screen with the below text:
An error has occurred while updating the device software. Use the Emergency recovery funtion in the Smrt Switch PC software
I tried to use Smart switch but on pc it said unsupported device
What can i do now ?
EDIT : Flash stockrom and everything is ok , but when i tried to flash patched file again , it still stuck in : only official released binaries are allowed to be flashed
HansKila said:
im in step Flashing with Odin , it said something like : only official released binaries are allowed to be flashed
then it stuck , i press down and home to cancel and restart but now it stuck in a screen with the below text:
An error has occurred while updating the device software. Use the Emergency recovery funtion in the Smrt Switch PC software
I tried to use Smart switch but on pc it said unsupported device
What can i do now ?
EDIT : Flash stockrom and everything is ok , but when i tried to flash patched file again , it still stuck in : only official released binaries are allowed to be flashed
Click to expand...
Click to collapse
Make sure the bootloader are unlocked, It look like the bootloader locked
redymedan said:
Make sure the bootloader are unlocked, It look like the bootloader locked
Click to expand...
Click to collapse
I success rooted my phone now after 3~4 kind of softbrick and fail odin flash , i thi k it is something about oem bootloader unlock
Will be back in 1 or 2 week to test if it randomly reboot or softbrick again , also to check my heart status
Thank you for the guide and your help
HansKila said:
@redymedan ok im already backed up all my apps
and have a rom ready to patch but i dont know how to extract the rom to get AP tar file
i downloaded it by sam firm from xda , and its extension is .zip.enc4 and cant be open by 7zip
Click to expand...
Click to collapse
Hi @HansKila I just created video how to decrypt ENC4 file using SamFirm tool, watch this https://youtu.be/QmiF9wMbikw
How to update after root?
Bazz27 said:
How to update after root?
Click to expand...
Click to collapse
You mean firmware update??When root or twrp flashing device you can't update firmware.Only whit odin you can flash new firmware.
muhamet said:
You mean firmware update??When root or twrp flashing device you can't update firmware.Only whit odin you can flash new firmware.
Click to expand...
Click to collapse
Does flashing new firmware will unroot my phone?
HansKila said:
Does flashing new firmware will unroot my phone?
Click to expand...
Click to collapse
Yes
thanks a lot
redymedan said:
Complete Guide for Rooting Samsung Galaxy A50s using Magisk only ( tested on SM-A507FN ), You need Latest Magisk Manager ( MagiskManager-v7.3.4.apk ) and Stock ROM:
1. Download the firmware Galaxy A50s (SM-A507FN).
2. Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5. Copy AP tar file and MagiskManager-v7.3.4.apk to your phone.
3. Install Magisk Manager ( MagiskManager-v7.3.4.apk ) on your phone.
4. In Magisk Manager: Install → Install → Select and Patch a File
5. Select the AP tar file. Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar. Copy magisk_patched.tar the tar file to your PC
6. Reboot to Bootloader: Turn Power Off. Press and hold Volume Up key + Power Key, When Samsung Logo appears release Power Key only, keep pressing Volume Up key until Android Recovery Mode Appears. Select Reboot to bootloader. Connect the phone to PC using USB Cable.
7. Flash magisk_patched.tar as AP in ODIN, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do.
8. Important: Uncheck “Auto Reboot” in Options!
9. Magisk is now successfully flashed to your device! Several steps before you can properly use the device.
10. Full data wipe is mandatory! Do not skip this step.
Press and hold Volume Down + Power Key, when the screen blank quickly press and hold Volume Up + Power key, when Samsung Logo appears release Power key only, keep pressing Volume Up key in the Android Logo screen with text "Erasing", when screen blank again Press and Hold Volume Up + Power key. When Samsung Logo appears release Power Key only, keep pressing Volume Up key until Android Recovery Mode Appears. Select Wipe data / Factory reset.
11. This time to boot to the system with Magisk. Select Reboot system now, and immediately press the Volume Up + Power key, After seeing the bootloader warning screen, release all keys so it can boot to the system.
12. After the device is booted up, do the usual initial setup. It need more time and patient. After finished, You will see Magisk Manager app in app drawer. If not, Install it manually.
13. Connect the phone to Internet, If you can not see Magisk Manager, Install it manually and Open Magisk Manager. It will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
14. Done! You can use Root Checker to check it, Enjoy!
Click to expand...
Click to collapse
I'm stuck at point 7: what does it mean al that words (BL, CP and HOME_CSC)? In my odin screen I have this options: Bootloader,PDA, Phone,CSC (I can't upload images because I'm a new user )
5im1 said:
I'm stuck at point 7: what does it mean al that words (BL, CP and HOME_CSC)? In my odin screen I have this options: Bootloader,PDA, Phone,CSC (I can't upload images because I'm a new user )
Click to expand...
Click to collapse
Extract the firmware files that are consist of 5 files, BL, AP, CP, CSC_OMC and HOME-CSC, then patch AP file with Magisk Manager on Your phone, then you will get magisk_patched.tar file, Now flash the file together with BL, CP, CSC_OMC or HOME_CSC, on AP slot you put magisk_patched.tar file.
For clearly I suggest you watch the Video
This is boot.img.tar for N770FXXU3BTE5/N770FOXM3BTE5/N770FXXU3BTE4/N770FXXU3BTE5 (PHE)
Link:
https://mega.nz/file/<<delete this space>>8J92hQaA#VS0XsDolIfPpbhLkhN0ju0h47IWiuiZEgbaz9KhDxnM
Root done with below steps:
1/ Download right firmware
- Extract downloaded firmware, get AP_xxx_OS10.tar.md5
- Rename AP_xxx_OS10.tar.md5 to AP_xxx_OS10.tar
- Extract AP_xxx_OS10.tar by 7-Zip-ZS
- Extract boot.img.lz4 (in extracted folder) and get boot.img
2/ Patch boot.img
- Copy boot.img (just extracted) to phone
- Use Magisk Manager to patch, you will get magisk_patched.img in Downloads folder (on Phone)
- Rename magisk_patched.img back to boot.img (IMPORTANT)
- Compress this boot.img to boot.tar by Zarchiver (IMPORTANT, Open Zarchiver and choose boot.img in Downloads folder of your phone, choose compress and select .tar at "Archive format".
- You will get "boot.tar" file.
3/ Copy to Computer
- Copy "boot.tar" on end of above step 2 to computer
- Rename this boot.tar to boot.img.tar (IMPORTANT)
4/ Flash by Odin Odin3_v3.14.4 (required Odin3_v3.14.4)
- Required: Unlock bootloader by hold combo Vol+ and Vol- then Plug cable, confirm unlock by Vol+, the phone is on Download mode with unlocked bootloader now.
- Open Odin 3.14.4, choose boot.img.tar at AP (just AP only, NOT BL_,CP_,HOME_CSC_)
- Untick at "Auto reboot" options
- Start to flash
- After Odin "PASS", Press Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press Power + Volume Up to boot to recovery.
- Choose Wipe data/factory reset to wipe the data of the device.
- Select Reboot system now, and immediately press Power + Volume Up to recovery. After seeing the bootloader warning screen, RELEASE ALL BUTTONS so it can boot to the system.
5/ After reboot to system, your phone is rooted. Reinstall Magisk Manager and Enjoy.
FYI:
I tried to patch AP_N770FXXU3BTE5_CL18298188_QB31310299_REV00_user_low_ship_meta_OS10.tar.md5 to magisk_patched.tar and flash together with BL_,CP_,HOME_CSC_ forsaid firmare but always be stuck at:
ODIN MODE (AVB Fail)
recovery:Error validating footer. (0)
recovery: Error verifying vbmeta image: invalid vbmeta header (6)
CUSTOM RECOVERY
Finally, done with above boot.img.tar method.
So you have Twrp??
Sent from my SM-N960U using Tapatalk
butchieboy said:
So you have Twrp??
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
TWRP for Note 10 lite is not available. This way is just root by patched boot.img.
At the end of your post you have Custom Recovery so it appears by your post that you have it. I know the developer that is working on it so I know its not available. Just wanted clarification is all. I understand the root method I wrote it up a week ago
Sent from my SM-N960U using Tapatalk
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.
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.
/*** BEGIN DISCLAIMER ***/
If you follow this procedure and lose every bit of content on your device / end up with a fancy paperweight, I, nor anyone involved with the referenced open source or otherwise licensed projects is responsible. It's all on you, and this will void your warranty. Do not proceed if you don't understand something. Chances are you will have a bad time.
/*** END DISCLAIMER ***/
Hey everyone - my Samsung Galaxy Tab A 10.1" (2019) - SM-T515 - recently applied a security update without my consent (The Samsung Android 11R September 8th 2021 Security update - side note, make sure that you turn off Samsung's push service ), which canned my previous root access. I use server software and internal port forwarding to do... Things on my device, so I needed my root access back.
Here's how I retrieved it, and how I put TWRP in place as my recovery partition in the process.
The Tools
Make sure you have these before you start. Because this is a Samsung device, you'll have to do some things under Windows, like using Frija and Odin (unfortunately).
1.) Frija - Available here - https://forum.xda-developers.com/t/tool-frija-samsung-firmware-downloader-checker.3910594/
2.) The latest SM-T515 / SM-T510 firmware from Samsung for your device's CSC (if you use the firmware for the wrong CSC code the most common problem that I have seen as a result is typically incorrect partition sizes after flashing, which can be corrected with TWRP). Frija is listed first, because you'll use Frija to get this directly from Samsung.
3.) Some kind of generic tool that you're comfortable with for working with archives. Ideally whatever tool you choose should be able to work with .tar, .gz, and .zip archives for this process. Personally I like 7-Zip on *Nix and Windows, and ZArchiver on Android.
4.) Odin (firmware flash tool by Samsung) - attached.
5.) The latest Samsung device USB drivers for your environment (they're fine as long as they enable both ADB and MTP correctly) - available here https://developer.samsung.com/mobile/android-usb-driver.html
6.) The latest TWRP image for Samsung SM-T5xx devices - available here https://androidfilehost.com/?fid=14943124697586374577 (and attached)
7.) ADB - downloading / installing and using adb are outside the scope of this post. It is available here - https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/
8.) The latest Magisk APK file - available here https://github.com/topjohnwu/Magisk/releases/download/v23.0/Magisk-v23.0.apk
The Process
0.) Back up your stuff, and remove your SD card if it makes you more comfortable - do whatever you need to do to be comfortable with "I might lose EVERYTHING on this device." If you plan on following this procedure, you should know how to do this, and I'm not going to try to explain it. If you can't get past this part, you should stop while you're ahead and still have a device that boots.
1.) Unlock your bootloader.
2.) Download the most recent firmware package for your device using Frija and extract all of the individual .md5 files which it contains.
2.) Use Odin to flash the most recent firmware to your device, and factory reset / wipe / format partitions and caches until you have a clean device that boots correctly. If your partitions aren't sized properly at this point it isn't something to be too concerned with, as you can correct them later using TWRP.
3.) Turn developer options back on, enable USB debugging, set the default USB configuration to "File Transfer", connect your device to your PC and copy the Magisk APK over to the internal storage of your device.
4.) Remove .md5 from the filename of the AP file that was included in your firmware package from Samsung and extract its contents into its own directory.
5.) Extract the contents of the latest TWRP package for these devices into the same directory where you extracted the individual partition image files contained in the AP file. Overwrite contents in the destination directory as necessary. The TWRP package should contain three files - param.bin.lz4, recovery.img.lz4, and vbmeta.img.lz4 - If there are uncompressed images (.img files) that correspond to the LZ4 compressed images from the TWRP package in the AP file of your firmware package, remove them first. Odin will (understandably) freak out if you try to flash two different images to the same partition in the same flash operation.
6.) Compress the contents of your modified AP directory which now contains the TWRP package's contents into a tar ball on your PC, and then copy it somewhere that Magisk will be able to access it on the Internal storage of your device (the Downloads directory - "/storage/emulated/0/Downloads/" is a good choice).
7.) Copy the latest Magisk APK to your device (again, the Downloads directory is a good choice), and then install it on your device.
8.) Launch Magisk on your device and choose "Install". Be sure to uncheck the "Recovery Mode" option. We don't want to use "Recovery mode" for Magisk's patching process. Even though this is a Samsung device and this would normally be how to proceed, in this case we're using our own custom TWRP recovery partition, and we don't want Magisk to mess with it. So make sure you aren't patching the bootloader or recovery images in unnecessary ways with Magisk.
9.) In Magisk on your device, choose "Select and patch a file" and then choose the AP file that you created and copied to the device which now contains TWRP as its recovery partition.
10). Let Magisk do its patching and when it has completed take note of where the patched file which it generated was written.
11.) Launch a command line / Powershell / Bash terminal where you can perform ADB commands, and issue the command "adb pull "/storage/emulated/0/Download/magisk_patched-23000_xYzXyZ.tar" (replace "XyZxYz" with whatever random sequence of characters that Magisk generated during its patching operations) to use ADB to download the patched AP file from your device.
12.) Power off your device.
13.) Reboot your device into FANCY download mode by holding the volume up and volume down keys simultaneously while inserting a USB cable that is connected to your PC into your device's USB C charger port. Your device should boot as you insert the USB cable and your bootloader should already be unlocked, so when prompted press the volume up button to continue.
14.) Launch Odin on your PC, and choose the BL, CP, CSC, and UserData images from the firmware package that you retrieved from Samsung to flash the corresponding slots in Odin. In the AP file slot, choose the Magisk patched AP file which contains TWRP as its recovery partition which you retrieved previously using ADB.
15.) Start the flash operation in Odin, and wait patiently for it to complete. Stay alert, because if you left "Auto reboot" checked in the Odin options, your device will reboot immediately upon completion, and there are actions that you need to take while the device is in its "off" state before it re-launches itself.
16.) Once the Odin flash operation has completed, boot to recovery mode. If you left "Auto reboot" checked in Odin, immediately as the flash operation completes, press and hold the power key and the volume up key and remove the USB cable from the device. Otherwise press and hold the power button and the volume down button until the device restarts, and while the device is in its "off" state remove the USB cable and press and hold the power button and the volume up button during device restart to enter recovery mode.
17.) Immediately upon entering recovery mode you should see TWRP do a couple of things that ensure that Samsung's device protection solutions don't remove it. Once those operations have completed, reboot into the system partition.
18.) Your device should be BASICALLY ready to go. Go through the steps to "complete" setup as you see fit. If you have not already done so, connect your device to a WiFi or to an LTE network and then launch the Magisk application.
19.) Magisk may want to download updates, if it does, let it do so.
20.) Once any necessary updates / downloads have completed, re-launch Magisk and it should present you with a prompt to the effect of "Magisk is installed, but additional configuration needs to be done on your device for it to work the right way. Do you want to reboot now?" If you've made it this far, the answer is "Yes, please do."
21.) After rebooting, your device will now be configured, and be running TWRP in its recovery partition, along with a properly Magisk rooted system partition.
22.) ????
23.) PROFIT!
I hope this helps some people out!
- The Scarecrow - 2021/09/22
Has anyone besides been successful?
mydjtl said:
Has anyone besides been successful?
Click to expand...
Click to collapse
I can provide screenshots from the device that I did this to if you would like.
It's pretty cool to see the TWRP logo on a Samsung Tab series device that's running Android 11.
I don't even get the little Samsung warning prompt during device bootup that says "This device's software can't be verified" or whatever Samsung's custom ROM message is. All I get is the "This device's bootloader is unlocked" message, no warning about the integrity of the software.
mydjtl said:
Has anyone besides been successful?
Click to expand...
Click to collapse
Follow this simple as he'll no need to read all these things
pankspoo said:
Follow this simple as he'll no need to read all these things
Click to expand...
Click to collapse
Yeah - pretty much exactly that, except I Magisk patched the system image, and then copied the TWRP package's vbmeta and recovery image into the AP file for the Odin flash, and then flashed every slot rather than just the AP.
is it systemless root?
Will this work on Galaxy Tab A sm-t595? on android 10?
or know of a root guide that will work with said device?
If you dont untick auto reboot, how do you fix any issues that happen because of it?
I rooted my t500 but I think it auto rebooted, which then caused a vbmeta error that stopped it booting. It worked again after flashing the stock rom, but now it gives a vbmeta error if I try to flash a modded rom to root it and I cant get oem unlock to appear in the stock os (download mode says its already unlocked tho)
Hello,
Code:
9.) In Magisk on your device, choose "Select and patch a file" and then choose the AP file that you created and copied to the device which now contains TWRP as its recovery partition
Step 9 yields an error on T515 : Unsupported/Unknown image format
I also tried to install AP patched file with Odin, same result.
Any idea ?
Damn this works so nicely, thanks mate! Cheers!