[Guide] How to update without losing data when rooted - Samsung Galaxy Tab S7 / S7 Plus Guides, News, & Di

[Guide] How to update without losing data when rooted - Samsung Galaxy Tab S7 / S7 Plus Guides, News, & Di

I see there is no correct/clear instructions on how to update firmware when you already rooted your tablet without losing data.
Many people, including myself, are forced to factory reset by following wrong instructions floating around.
So I think it is necessary to post a clear guide on how to update with root without losing data.
There are two correct ways, and the key is never flash stock AP without patching vbmeta at the same time. Never let the stock vbmeta.img flash to your device. The stock vbmeta.img in stock AP will enable Android verified boot and will lead to factory reset in the next boot.
First and preferred method:
1. use magisk to patch the whole AP file and magisk will patch both boot.img and vbmeta.img.
2. Flash magisk patched AP in AP slot and BL in BL slot and HOME_CSC in CSC slot, and done.
Second method:
1. Download vbmeta_disabled.tar from https://forum.xda-developers.com/t/...root-s20-series-and-upgrade-firmware.4079353/
2. Patch boot.img using magisk: extract boot.img.lz4 from stock AP, compress it to a tar file and patch the tar file in magisk.
3. Uncheck auto reboot in ODIN, flash stock AP in AP, BL in BL and HOME_CSC in CSC slot, and vbmeta_disabled.tar in USERDATA slot at the same time. With the vbmeta_disabled.tar, Android verified boot remains disabled. Remember to flash them at the same time in ODIN so that Android verified boot remains disabled. If you flash vbmeta_disabled.tar after flashing stock AP, Android verified boot will be re-enabled and it will ask for factory reset.
4. Check auto reboot in ODIN, flash magisk patched boot.img in AP slot.

googlephoneFKLenAsh said:
I see there is no correct/clear instructions on how to update firmware when you already rooted your tablet without losing data.
Many people, including myself, are forced to factory reset by following wrong instructions floating around.
So I think it is necessary to post a clear guide on how to update with root without losing data.
There are two correct ways, and the key is never flash stock AP without patching vbmeta at the same time. Never let the stock vbmeta.img flash to your device. The stock vbmeta.img in stock AP will enable Android verified boot and will lead to factory reset in the next boot.
First and preferred method:
1. use magisk to patch the whole AP file and magisk will patch both boot.img and vbmeta.img.
2. Flash magisk patched AP in AP slot and BL in BL slot and HOME_CSC in CSC slot, and done.
Second method:
1. Download vbmeta_disabled.tar from https://forum.xda-developers.com/t/...root-s20-series-and-upgrade-firmware.4079353/
2. Patch boot.img using magisk: extract boot.img.lz4 from stock AP, compress it to a tar file and patch the tar file in magisk.
3. Uncheck auto reboot in ODIN, flash stock AP in AP, BL in BL and HOME_CSC in CSC slot, and vbmeta_disabled.tar in USERDATA slot at the same time. With the vbmeta_disabled.tar, Android verified boot remains disabled. Remember to flash them at the same time in ODIN so that Android verified boot remains disabled. If you flash vbmeta_disabled.tar after flashing stock AP, Android verified boot will be re-enabled and it will ask for factory reset.
4. Check auto reboot in ODIN, flash magisk patched boot.img in AP slot.
Click to expand...
Click to collapse
When you're using the preferred method to patch the AP file, are you just using a tool such as the Samsung Firmware Downloader to get the zip and then extracting that into the 4 .tar.md5 files? If so, how are you patching the AP .tar.md5 file with Magisk? It fails for me when I attempt it

Skidoo03 said:
When you're using the preferred method to patch the AP file, are you just using a tool such as the Samsung Firmware Downloader to get the zip and then extracting that into the 4 .tar.md5 files? If so, how are you patching the AP .tar.md5 file with Magisk? It fails for me when I attempt it
Click to expand...
Click to collapse
I used Frija to download but it shouldn't matter where/how you download the firmware as soon as it's the correct firmware.
Just use magisk to patch the AP .tar.md5 file. You should see in the magisk patch log saying patching both vbmeta.img and boot.img.
It shouldn't fail if you are using latest magisk canary.
Any error message in magisk when you patch the AP?

googlephoneFKLenAsh said:
I see there is no correct/clear instructions on how to update firmware when you already rooted your tablet without losing data.
Many people, including myself, are forced to factory reset by following wrong instructions floating around.
So I think it is necessary to post a clear guide on how to update with root without losing data.
There are two correct ways, and the key is never flash stock AP without patching vbmeta at the same time. Never let the stock vbmeta.img flash to your device. The stock vbmeta.img in stock AP will enable Android verified boot and will lead to factory reset in the next boot.
First and preferred method:
1. use magisk to patch the whole AP file and magisk will patch both boot.img and vbmeta.img.
2. Flash magisk patched AP in AP slot and BL in BL slot and HOME_CSC in CSC slot, and done.
Second method:
1. Download vbmeta_disabled.tar from https://forum.xda-developers.com/t/...root-s20-series-and-upgrade-firmware.4079353/
2. Patch boot.img using magisk: extract boot.img.lz4 from stock AP, compress it to a tar file and patch the tar file in magisk.
3. Uncheck auto reboot in ODIN, flash stock AP in AP, BL in BL and HOME_CSC in CSC slot, and vbmeta_disabled.tar in USERDATA slot at the same time. With the vbmeta_disabled.tar, Android verified boot remains disabled. Remember to flash them at the same time in ODIN so that Android verified boot remains disabled. If you flash vbmeta_disabled.tar after flashing stock AP, Android verified boot will be re-enabled and it will ask for factory reset.
4. Check auto reboot in ODIN, flash magisk patched boot.img in AP slot.
Click to expand...
Click to collapse
Thank you for the guide. Still haven't tried but cleared some doubts. I even thought of restoring and relocking bootloader. Will update my result after trying the preferred method.

I didn’t update since one year. I was on UI 3 and android 11. I was not sure at all to succeed but it worked. Updated with no data lost.
Don’t forget to patch the all AP file before with the last magisk (25.1 for me). Then, use the patched file instead of the original AP.
Use the "Home" CSC.
Magisk can need a reboot before de wake up
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Thank you so much for posting these instructions. Update my rooted s7 fe without having to wipe.

Thanks I updated my Tab S7 T875 from Android 11 to 12 a week ago without wipe and root preserved. Your guide has refreshed my memory of how to go about it
Now Android 13 is available and am downloading firmware and will update from 12 to 13 now .

Hi there,
is it possible to patch all 4 files (incl. patched AP) at once?
BR

BlackHoleSun2015 said:
Hi there,
is it possible to patch all 4 files (incl. patched AP) at once?
BR
Click to expand...
Click to collapse
I am not sure, but I did it like this, I hope it helps.
The resources/drivers/programs I used can be found at the bottom of this comment.
Firmware Upgrade Guide Samsung Galaxy Tab S7+ | SM-T970 | CSC:EUX | while keeping/retaining Magisk Root.
1.Download Latest firmware on PC via Frija (CSC:EUX & Model:SM-T970 for me)
2.Extract ZIP Open extracted directory and delete ZIP.(I like to keep a clean overview, so optional)
3.In the directory you find BL, AP, CP, CSC & HOME_CSC files. If you use the Wifi only version of the Tablet, you can remove the CP file.
This leaves the BL file (should be left untouched), AP file & CSC & HOME_CSC files.
Choose one of the two CSC files to keep.
4.a. Want to Keep your data? Use Home_CSC....tar.md5 file using ODIN, other file can be removed.
4.b. Factory reset? Use other CSC file instead.
5.Move (not copy, but move) AP file (AP......tar.md5) to Tablet and patch whole file in Magisk (I am using the latest Canary Magisk version)
When this is done, move the patched AP file called magisk_patchedsomethingsomething back to the first extracted directory (step 2) AP-file name does not matter.
Connect tablet to PC with USB.
Using Terminal in ADB directory, use " adb devices" to check if PC can find tablet when tablet operates normally. Use command " adb reboot download" to boot the tablet directly into download mode.
Open ODIN (no settings need to be adjusted in ODIN other than selecting the correct files)
In ODIN,
Select AP ---select ---> magisk_patched.#######.tar
Select BL ---> BL_####.tar.md5
Select CSC ---> HOME_CSC_####.tar.md5
OR use CSC_####.tar.md5 if factory reset is required
Click Start. Wait. And enjoy!
Resources used:
-Friji v1.4.4 for downloading latest firmware real fast.
-Minimal ADB Fastboot v1.4.3.exe for minimalistic ADB-installation
-Samsung USB Driver for Mobile Phones (for PC to recognize the tablet in Download mode)
-Odin (I used the latest version v3.14.4)

Patch whole AP take times, my device is ramdisk + no vbmeta so i just patch boot.img
Theres a chance bootloader got locked again then you may brick your phone so remember, always BACK UP before doing anything!

I really missed a decade of new methods for rooting complications and what not finally upgrading from note 3 being stuck on android 5.0 LoL, i feel sad it served me really well , thanks for the update method .

1. use magisk to patch the whole AP file and magisk will patch both boot.img and vbmeta.img.
Click to expand...
Click to collapse
I get installation failed when attempting this

Hello,
I tried the first method but it still said vbmeta error and I had to reset all data...
I was using stock Magisk 25.2 version. Before I do it again after some months...
1) I know I have to use Canary now is there any specific version to have?
2) Is there any verification that vbmeta was really patched? In both versions of Magisk (stock and Canary) it always said in logs "patching vbmeta..." so how can I know it really happened?
3) Can I patch whole AP from stock firmware and just extract already patched boot img from that AP in the second option? Not to extract boot.img and patch only that file separately?
4) To be safe can I combine both options? Using patched AP from option 1 and use vbmeta disabled in option 2 in USERDATA?
Thank you!

Love, OP
TIA

Related

[N10 SM-N970U/U1/W_Snapdragon]-[Upgrade Easily Firmware Using Odin]-[Automatically Root Remove Forceencrypt Patch Bluetooth And Fix Safetynet]

Must Have An Unlocked Bootloader To Do This!
This An odin tar file I have created to flash along with stock odin firmware to automatically install TWRP recovery along with Disable VBMETA image. The tar file will also automatically install magisk root along with remove force encryption and patch bluetooth library file. It will also patch safetynet. No flashing of zips is required
Info For Bootloader Unlocks Can Be Found In Post 2
I Do Not Recommend Mixing Bit 5 With Higher Firmware!!!!
Unless Using Bit Safe Firmware That Is Patched
Downloads
SM-N970U/U1/W- Model
USERDATA_AIO_N970_FORCE_WIPE_10_10_21.tar.md5 --Use on android 10 or 11
This will force a wipe of data no mater what.
Full Odin 3.1.1 Bit1 Safe Firmware
N970USQS7FUH3_BIT5_SAFE.7z
This are odin files and will safely update all image files too bit 7 and keep bit 5 bootloaders. Unfortunately this will wipe data this is beyond my control as it seems to be a side affect of mixing firmware it causes data not to mount and therefore my AIO will format it. This is full firmware with USERDATA_AIO. This will put you on U firmware. Before flashing I recommend removing your google account and make sure in download mode you are not frp locked
If above USERDATA_AIO_N970_FORCE_WIPE_08_30_21.tar.md5 is newer than the one in this zip use the newer one from above
Odin3_v3.14.1_3B_PatcheD.zip
Files For SM-N975 Found Here
TWRP Recovery Provide by @afaneh92
Be prepared to have your data wiped. The process tries to determine if you do or do not need to have data wipe but as a precaution just assume your data will be wiped. Especially if using U1 or W firmware
Install Instructions For Newly Unlocked Devices
You must be OEM Unlocked Bootloader
1. On Initial unlock of phone you must through setup and be signed into your google account.
2. Reboot phone too download mode and make sure KG STATUS=CHECKING (see pic) and not PRENORMAL. If PRENORMAL then do step 1 again
View attachment 5217631
3. Use patched 3.14 odin and load file USERDATA_SLOT_*9**U_**.tar.md5 you must choose one of the FORCE_WIPE files and load in the USERSDATA slot of odin and flash file
4. Phone will reboot to TWRP and remove encryption which will wipe phone. Phone will reboot back too TWRP to finish install then reboot to setup
Install Instructions For Updating Firmware On Phone Already Unlocked
1. Reboot phone too download mode and make sure KG STATUS=CHECKING. If not see above
2. Use patched 3.14 odin and load stock firmware in appropriate slots use regular CSC file in the CSC slot and load file one of the USERDATA_SLOT_*9**U_**.tar.md5 in the USERSDATA slot of odin and flash firmware. Do not use the User Data file that comes with firmware.
3. Phone will reboot to TWRP and check for encryption and remove if needed which will wipe phone. If phone is not encrypted data will not be wiped. Phone will reboot back too TWRP to finish install then reboot to setup if data was wiped or reboot normally if it was not
Install Instructions If Updating Images With TWRP
1. When done flashing images in TWRP Reboot phone too download mode and make sure KG STATUS=CHECKING. If not see above.
2. Use patched 3.14 odin and load file USERDATA_AIO_*9**_NO_WIPE_NO_BL.tar.md5 in the USERSDATA slot of odin and flash file.
3. Phone will reboot to TWRP and check for encryption and remove if needed which will wipe phone. If phone is not encrypted data will not be wiped. Phone will reboot back too TWRP to finish install then reboot to setup if data was wiped or reboot normally if it was not.
4. Alternatively to using USERDATA_AIO_*9**_NO_WIPE_NO_BL.tar.md5 in odin you can use AIO_Magisk_21_4_N10U_US_Series_Android_R.zip found in post 2
Features
No patches or mod zips are needed phone will already be rooted
Fix Safetynet
Bluetooth is patched for pairing to survive reboots
Samsung Health working
Bugs
Samsung Pay, Secure Folder and Samsung Pass do not work as on most Samsung Rooted Roms
Thanks To People That Make My Life Easier
@elliwigy
@klabit87
@Krog18
@me2151
@stang5litre
@Raymonf for modified odin
@rayan-refoua for boot animation
@TheMadScientist
@afaneh92
@kdrag0n for safetynet fix
3arthur6 for bluetooth patch zip
@JDBarlow for test S20 stuff

Info For Bootloader Unlocks Can Be Found
[Android][UNSAMLOCK] Bootloader Unlock for Samsung US/Canada Devices
This thread is @svetius approved Important notice: Do not update to April 2023 security update (XXXXXXXXXXWCX) or later. Examples: G998USQS6EWCA, N986USQU4HWD1. Samsung has patched the bootloader unlock again on those updates. NOTE: The OneUI...
forum.xda-developers.com

Hey can you help me with this process. I am not entirely to sure if my s10e varient is capable of root/unlocking bootloader.

Question A32 4G root and twrp

Hi forum readers,
I think about buying an A32 4G (SM-A325FZKGEUB). In two threads here it was mentioned that rooting was successful. But how about twrp? I found an article on unofficialtwrp.com with description and download of an unofficial twrp and vbmeta.img with another tool for also unencrypting the data partition.
1) With all previous phones I only used xda stuff. What do you think, is it safe to use unofficial twrp?
2) If that twrp fails, I think it is possible to get the original recovery back using Odin. Correct?
3) Is it safe to use the vbmeta.inf and tool to unencrypt the data? I don't need Knox and also not Safety Net. Would it be possible to revert to factory status using Odin?
4) Ist necessary to unlock the bootloader for only flashing the Magisk-patched boot image? How about encrypted data?
Many Greetings
Florian

To root you need bootloader unlocked, if it isn't your phone will fail to flash and it will boot on EDM. If twrp fails you can always flash a .tar as AP containing only recovery.img

@ZModder, thank you for your hint. I was already successfully unlocking and installing Magisk 23. Because of your hint I dared to flash TWRP from the above mentioned web site. It didn't boot. But I could successfully return to original recovery. So waiting for a real device specific TWRP.

fbalder18 said:
@ZModder, thank you for your hint. I was already successfully unlocking and installing Magisk 23. Because of your hint I dared to flash TWRP from the above mentioned web site. It didn't boot. But I could successfully return to original recovery. So waiting for a real device specific TWRP.
Click to expand...
Click to collapse
how did you install Magisk? could you tell?

kkintr0 said:
how did you install Magisk? could you tell?
Click to expand...
Click to collapse
1st: Download appropriate firmware for your region and version of Samsung.
2nd: Unlock your bootloader. This will wipe your data.
3rd. Download magisk manager from github.
4th. Open Magisk and check what Ramdisk says.
4th: Extract your downloader firmware. There should be AP.... File. Open it via 7zip. Inside there you should have boot.img.lz4. Extract that file. If Ramdisk Says NO. Do the same with recovery file.
5th: Zip your boot file to tar format and place it on your phone.
6th: Open Magisk. and Press first Install Button.
7th: Press Select and Patch File. Magisk should create a new file inside Downloads folder. Called magisk..patched...etc Insert that file inside your pc. Do the same with recovery file if needed.
8th. Get into Download mode. You can do this by first turning off your phone and pressing both volume keys as you insert your usb cable.
9th: Open Odin File. If you have recovery file uncheck autoreboot. Place your patched file inside AP section.
10th: Reboot your phone and wipe your data.
11th: Volia!

Question About S22 boot failed

Hi
Recently, Samsung post the latest Firmware(S9010ZCU2AVDC). Because of my S22(SM-S9010) rooted, I have to upgrade my system by using BootLoader. But before I shut my phone down, I upgraded my magisk24.1 to 24.3, and I uninstalled "shizuku", instead I installed a magisk module "sui". Then I use magisk to patch NEW firmware AP files, and transport it to my PC. I use odin to flash my phone, but I cann't boot successfully. Some loop passed, I received a error called like "supported API3?". But when I flash the origin firmware(without magisk patch), I can boot to system but my root lost. So, can somebody help me to root my phone again? Thanks~

You need to flash the bl file, patched ap file, cp file, and home csc file not just patched ap.

mr.herbert said:
You need to flash the bl file, patched ap file, cp file, and home csc file not just patched ap.
Click to expand...
Click to collapse
I'm sorry for my description. In fact I flashed them for 3 origin files and ap patched. Also I have upgraded my firmware for 2 times successfully, but this time failed. I don't know whether the special firmware(like this one, bulletin tells me if I flash this firmware, I cannot downgrade anymore) need some special method. Thanks~

Question Rooting a gsi?

Is there any way to root a gsi? All the tutorials seem to make you flash stock everything. Any way to get magisk running on a android 12 gsi? (Descendant os)

Airpewdiepie said:
Is there any way to root a gsi? All the tutorials seem to make you flash stock everything. Any way to get magisk running on a android 12 gsi? (Descendant os)
Click to expand...
Click to collapse
You can get the boot.img from the stock firmware, lemme explain it to you:
1. Get the firmware.
2. Open the file beginning with AP
3. Extract boot.img.lz4 with WinRAR
4. Get lz4, drag the file into the lz4.exe
5. There is a new file named "boot.img"
6. install 7Zip
7. right click > 7Zip > Add to archive
8. make sure its .tar
9. Enable debugging mode and drag drop the boot.tar into any folder in your phone
10. Patch it with magisk
11. Drag it back to your PC.
12. Open ODIN, then put the magisk_patched... into the AP slot.
13. Press "Start" (i think)

Franzyy said:
You can get the boot.img from the stock firmware, lemme explain it to you:
1. Get the firmware.
2. Open the file beginning with AP
3. Extract boot.img.lz4 with WinRAR
4. Get lz4, drag the file into the lz4.exe
5. There is a new file named "boot.img"
6. install 7Zip
7. right click > 7Zip > Add to archive
8. make sure its .tar
9. Enable debugging mode and drag drop the boot.tar into any folder in your phone
10. Patch it with magisk
11. Drag it back to your PC.
12. Open ODIN, then put the magisk_patched... into the AP slot.
13. Press "Start" (i think)
Click to expand...
Click to collapse
It wont replace my rom? also, can i do it without a factory reset?

Airpewdiepie said:
It wont replace my rom? also, can i do it without a factory reset?
Click to expand...
Click to collapse
1. It wont replace your rom
2. You sadly have to do a factory reset, then reflash the boot.tar again

Never root at boot, there are many people who lost IMEI by rooting at boot.

Melky777 said:
Never root at boot, there are many people who lost IMEI by rooting at boot.
Click to expand...
Click to collapse
You have to delete the imei folder to make imei working again

Melky777 said:
Never root at boot, there are many people who lost IMEI by rooting at boot.
Click to expand...
Click to collapse
A fix has been found for it.

Franzyy said:
1. It wont replace your rom
2. You sadly have to do a factory reset, then reflash the boot.tar again
Click to expand...
Click to collapse
Any reason for the factory reset?

i was able to root my phone running crdroid 8.8. all i did was first download the firmware. after that i copied over the AP file of the firmware to my phone and then selected that in magisk to patch it. after it patched it i copied it back over to my pc and flashed the ap file along with bl, cp and CSC file. it reset and it worked fine! now any GSI i try and i install magisk v22.0 apk it works just fine.

How To Guide Easiest way to Flash Pixel Experience 13+ GSI rom !!!

Disclaimer
Your warranty will be void
Some carriers' Terms of Service prohibit device modifications
Modifying will trip Samsung Knox and SafetyNet, so be aware that some apps will cease to work
I AM NOT RESPONSIBLE FOR BRICKED DEVICES, FAILED ATTEMPTS AND OTHER CAUSES OF IMPROPER USAGE OF THIS GUIDE!Now that we got that out of the way, we can continue.
Unlocking the BootloaderUNLOCKING THE BOOTLOADER WILL ERASE ALL OF YOUR DATA!How to flash PE+ GSi
this super.tar is based on A528BXXS2DWA9 Bit-2 2023/2/01
1. Unlock Bootloader Link
2. Download Link SamFw Tool 4.2 or Odin 3.14.4 Link,TWRP And Disabled VBMETA LINK Thanks To @BlackMesa123 for disabled VBMETA
3. Turn phone into Download mod.
4. a) in SamFw Tool 4.2 or Odin 3.14.4 attach super.tar to AP.
b) in SamFw Tool 4.2 or Odin 3.14.4 attach Disabled VBMETA.tar to Data(User data) Flash it.
c) (uncheck Restart if no TWRP Recovery is Flashed earlier,)in SamFw Tool 4.2 or Odin 3.14.4 attach TWRP.tar to AP & Flash it.
Jai Shree Ram, you have PE 13+
Reboot to Recovery & Root
5. Flash Magisk.zip by TWRP
6. for Fixes Check :- https://forum.xda-developers.com/t/how-to-configure-a-treble-gsi-properly.4564191/
7. 5g works but SMS service doesn't work in any GSI rom...,
To Enable this:-
go to settings a section called "Phh Treble Settings"
RIL
Misc > Automatic restart RIL > Enable it.
Thanks to @TheGsmWork for tutorials.
Check Proper setup of SamFw Tool 4.2 or Odin 3.14.4
how to make Super.tar
Thanks to @ponces for Best GSI Rom Link & @Darkaos006 for How to configure a Treble GSI properly.
Download Link
https://www.jiocloud.com/l/?u=jmu59xBVVPq98RvJCv0jiViunpxBqDRzsvpppiQkryM=Oe5
Use 7Zip Link & extract achieves

Thanks !

Develop Bugs

welcome