Related
Latest recommended firmware for latest update faster: (Updated weekly).https://samfrew.com/model/SM-A715F/region/SEK/
WARNING: You can't downgrade anymore once you flashed U2 update !
You will need:
-Odin v3.14.1
https://dl2018.sammobile.com/Odin3-v3.14.1.zip
-Galaxy A71 Latest USB Driver
https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
You want to download latest firmware directly from server? (fast download)
Samfirm 0.4.1 or Frija 1.4.2
https://samfirmtool.com/samfirm-v0-4-1
https://github.com/wssyncmldm/frija/releases
Frija not working ? install both vcredist_x00 for your device !
(Check your windows settings to know which version to install).
(Microsoft Visual C++ 2010 Redistributable Package) and (Microsoft Visual C++ 2008 Redistributable Package)
-https://www.microsoft.com/en-US/download/details.aspx?id=29 (x86) 2008
-https://www.microsoft.com/en-US/download/details.aspx?id=5555 (x86) 2010
-https://www.microsoft.com/en-US/download/details.aspx?id=15336 (64bit) 2008
-https://www.microsoft.com/en-US/download/details.aspx?id=14632 (64bit) 2010
-Open Frija and type in your model (mine is SM-A715F) and your CSC : (mine is LUX).
(All CSC's and models on Samfrew: https://samfrew.com/model/SM-A715F/).
-Download and extract SM-A715XX_1_00000000000000_xxxxxxxxxx_fac.zip
On your device:
If you want to unlock bootloader:
-Go to Settings then to About phone and find your build number.
-Tap on your build number 6 times until you see “You’re now a developer”.
-Go in Developer options > enable OEM unlocking.
-Connect the device to your PC.
-Power off your device with POWER and volume DOWN and directly hold volume UP and DOWN together!
-Device will boot in DOWNLOAD MODE.
-Long press volume UP to unlock the bootloader. This will wipe your data and automatically reboot your device!
If you dont want to unlock bootloader:.
-Download and extract Odin and open it as administrator.
Still in DOWNLOAD MODE:
-Click on BL and select BL_A715FXXXU1AXXX_CL16843479_QB27603640_REV00_user_low_ship_MULTI_CERT.tar.md5
-Click on AP and select AP_A715FXXXU1AXXX_CL16843479_QB27603640_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar.md5
-Click on CP and select CP_A715FXXXU1AXXX_CP14483800_CL16843479_QB27603640_REV00_user_low_ship_MULTI_CERT.tar.md5
(If you want to keep your data don't flash CSC).
-Click on CSC and select CSC_OMC_OXM_A715FXOXM1AXXX_CL16843479_QB27603640_REV00_user_low_ship_MULTI_CERT.tar.md5
-Click on USERDATA and select HOME_CSC_OMC_OXM_A715FXOXM1AXXX_CL16843479_QB27603640_REV00_user_low_ship_MULTI_CERT.tar.md5
-Click on START and wait for installation, when done you can unplug your device.
ROOTYour KNOX status will be tripped if you follow this tutorial...What's knox ? : https://www.google.com/search?q=samsung+knox+explained
-Download the latest stock firmware for your Samsung Galaxy A71 with Samfirm/Frija app (faster) or Samfrew/Sammobile website (way slower).
https://samfrew.com/model/SM-A715F/
-Extract the SM-A715XX_1_EXAMPLE_0000000000_fac.zip file with 7zip or any other unzipper.
-Copy the (AP_A715XXXXU1XXXX_CL00000000_QB00000000_REV00_user_low_ship_MULTI_CERT_meta_OS10.tar.md5) file and transfer it to your internal storage.
-Download and install Magisk Manager APK https://github.com/topjohnwu/Magisk/releases/download/manager-v7.5.1/MagiskManager-v7.5.1.apk
-Open Magisk Manager and go to Install > Install > Select and Patch a file.
-Navigate through the storage and select the extracted AP file.
The firmware will be patched and will be found in Internal Storage/Download/magisk_patched.tar.
-Transfer the patched file to your PC.
-Turn OFF your device and boot into DOWNLOAD MODE.
-In Odin, click on AP and select the patched tar file, Uncheck “Auto Reboot” and click on Install.
The tool will flash Magisk V20 on your Samsung Galaxy A71.
To boot in recovery or boot the system with Magisk installed:
1. Powering up normally → System without Magisk
2. Power + Volume Up → Bootloader warning → Release all buttons → System with Magisk
3. Power + Volume Up → Bootloader warning → Keep holding volume up → Actual recovery
Discord A series group to help users:
https://discord.gg/xrnrU8k
Don't need to dowload theses files if you don't know their purposes.
A71_EUR_OPEN.pit
https://mega.nz/#!Z1BRVQIZ!j3EkHOBbp7--iUAgZ2T56iBMzZMtKZoh17lphPqugtc
Combination firmwares:
COMBINATION_FAC_FAQ0_A715FXXU1ATA1
https://androidfilehost.com/?fid=4349826312261713325
COMBINATION_FAC_FAQ0_A715FXXU1ATA2
https://androidfilehost.com/?fid=4349826312261713327
Finally a reason to actually buy this phone, thank you
@BK☑️
Thanks for the share, would be appreciated if you can mention how to update over OTA when we have root the phone. Thanks.
Cuvillier said:
@BK
Thanks for the share, would be appreciated if you can mention how to update over OTA when we have root the phone. Thanks.
Click to expand...
Click to collapse
The reason it's not mentionned is simply because we can't, we just need to download latest firmware and patch it with magisk.
topjohnwu stated ( and i tested it myself ) that if we flash the latest OTA it will brick the device, which is logic.
We need to patch the latest firmware with magisk, if we go from a rooted environment to a non rooted it will brick.
I hope i cleared your thoughs.
BK said:
The reason it's not mentionned is simply because we can't, we just need to download latest firmware and patch it with magisk.
topjohnwu stated ( and i tested it myself ) that if we flash the latest OTA it will brick the device, which is logic.
We need to patch the latest firmware with magisk, if we go from a rooted environment to a non rooted it will brick.
I hope i cleared your thoughs.
Click to expand...
Click to collapse
Okay, so let's say if i get new OTA push notification, i download it first online and then i follow your root tutorial to update it with magisk included?
Cuvillier said:
Okay, so let's say if i get new OTA push notification, i download it first online and then i follow your root tutorial to update it with magisk included?
Click to expand...
Click to collapse
exactly, download the needed firmware and extract the AP file and put it in the download folder on your A71 device, then patch it to obtain a magisk_patched.tar file to flash in odin.
BK said:
exactly, download the needed firmware and extract the AP file and put it in the download folder on your A71 device, then patch it to obtain a magisk_patched.tar file to flash in odin.
Click to expand...
Click to collapse
Understood. Do you know if it will be possible to install twrp too ?
Cuvillier said:
Understood. Do you know if it will be possible to install twrp too ?
Click to expand...
Click to collapse
twrp is compatible, ask the developers of theses devices to build twrp for the a71 :
(the Galaxy A71 have the same Soc has theses devices)
(Snapdragon 730).
-Xiaomi Redmi K20
-Samsung Galaxy A80
-Poco X2
-Realme X2
-Oppo Reno 2
-Lenovo Z6
ill ask samsung open source release center to provide the source code for this device. (i'm an A70 user not A71).
edit: the source code will be released later this week.
edit2: source code is released. (18/02/2020)
BK said:
twrp is compatible, ask the developers of theses devices to build twrp for the a71 :
(the Galaxy A71 have the same Soc has theses devices)
(Snapdragon 730).
-Xiaomi Redmi K20
-Samsung Galaxy A80
-Poco X2
-Realme X2
-Oppo Reno 2
-Lenovo Z6
ill ask samsung open source release center to provide the source code for this device. (i'm an A70 user not A71).
edit: the source code will be released later this week.
Click to expand...
Click to collapse
Thanks, and about unlocking bootloader, is there something I should be aware of after that ?
Cuvillier said:
Thanks, and about unlocking bootloader, is there something I should be aware of after that ?
Click to expand...
Click to collapse
just that your knox bit will be tripped (0x1).
BK said:
just that your knox bit will be tripped (0x1).
Click to expand...
Click to collapse
Thank you, and got another question (sorry ), on your booting instructions, you say that to boot using using magisk we need to press vol+ and power, but will that be possible to boot as usual with power button and boot with magisk by default ?
Cuvillier said:
Thank you, and got another question (sorry ), on your booting instructions, you say that to boot using using magisk we need to press vol+ and power, but will that be possible to boot as usual with power button and boot with magisk by default ?
Click to expand...
Click to collapse
once twrp is released yes (if someone port it).
there is another method but that's another story.
BK said:
once twrp is released yes (if someone port it).
there is another method but that's another story.
Click to expand...
Click to collapse
Thanks, and about the root, if i understood, that way we can flash magisk without need to unlock bootloader ?
Cuvillier said:
Thanks, and about the root, if i understood, that way we can flash magisk without need to unlock bootloader ?
Click to expand...
Click to collapse
Nope you didn't understood, you can't root without unlocking bootloader.
It is not working
I downloaded hungarian firmware from frija, copied the AP file to my phone, patched with magisk, copied the patched file to my computer, booted my phone into download mode, flashed the ap file with odin (and yes i unchecked the auto reboot), and after it finished, I pressed the volume down and power button to reboot, and when the screen went off, I quickly changed to volume up and power button and hold until the bootloader warning appeared, and realased all buttons. After it booted, i opened magisk manager and it says magisk is not installed what can i do? ( and yes, I unlocked the bootloader)
Source code is up and can be downloaded on here! :
https://opensource.samsung.com/uploadSearch?searchValue=A715
I've tried rooting several times to no avail, I've unlocked and flashed everything with the patched magisk setup, I'm using the SM-A715F BTU firmware as that's what my phone was beforehand
When i try and do the volume up boot then release at the warning screen it just does a reboot cycle and never boots I have to force it it shut down and boot normally
I cant even restore phone to a point where SafetyNet validates so no Pokemon Go and such
can we unroot and recover the samsung knox?
Cyber Axe said:
I've tried rooting several times to no avail, I've unlocked and flashed everything with the patched magisk setup, I'm using the SM-A715F BTU firmware as that's what my phone was beforehand
When i try and do the volume up boot then release at the warning screen it just does a reboot cycle and never boots I have to force it it shut down and boot normally
I cant even restore phone to a point where SafetyNet validates so no Pokemon Go and such
Click to expand...
Click to collapse
Ok ladies and gentlemen I finally got it working, and here's what I had to do
You'll need to install 7zip or something that handles TARs and LZ4 that you can grab from github it was the second result on google for me
Once you've patched the AP file in Magisk Manager and copy it back to your pc, Open up that tar file and delete all files except recovery.img and vbmeta.img
Then open the original prepatched AP file in 7Zip and extract the boot.img.lz4 then take that file and drag it onto the lz4.exe from the lz4 utilities
you should now have a nice clean uncompressed boot.img, put that back onto the phone and patch it with magisk manager, you should now have magisk_patched.img copy that back to the pc and rename it boot.img and put it in the tar file from earlier so you should have boot.img recovery.img and vbmeta.img
With just these 3 files in the tar you dont have to worry about wiping your data again and it will patch pretty fast
Open up ODIN again and select AP and choose your new tar file and flash it
Then shut down the phone fully and power it on while holding vol up till you get to the warning screen about the unlocked bootloader let go of vol up and press power to continue and you should find that it boots properly now and magisk manager will show that magisk is installed.
So after you unlocked the boot loader ( see my previous post)
you can start rooting with magisk manager / patching the boot.img from the original firmware
I used this thread in order to get root ; i modified the contents so it would fit the moto phone a bit better:, but thnx goes to Ibolito over at the pixel 3 forums
1 ) Download the latest Android factory image for your device ("see this guide on where to find it.
2 ) Extract the "boot.img" file from the downloaded image and copy it to your phone.
Warning! Make absolutely sure the firmware is exactly the same as the installed one. If not, you might loose touch.
Be aware that LMSA will download the latest firmware, even if it is not yet installed. That might break your touchscreen
Click to expand...
Click to collapse
3 ) Download latest Magisk Manager application on your phone and install it :
Link
4 )Press on the Install Magisk button (the one on the top, not the Magisk Manager), then Install > Select and Patch a File and now select the Boot.img file you extracted earlier. When the process is done, just put the patched boot.img file on your computer in the same folder as your ADB and FASTBOOT tools, the file's name is magisk_patched.img
edit: i received a comment that the name might be something like Magisk_patched_somerandomletters_.img since the latest magisk update
5 ) Enable adb debugging on your phone and connect it to your computer via USB.
Open a command prompt on your computer and migrate to the folder where the ADB and Fastboot tools are located.
(for exemple, for me it's : cd C:\adb).
7 ) Reboot your phone to fastboot by typing adb reboot bootloader
8 ) Flash the Boot.img you just patched with magisk by typing fastboot flash boot magisk_patched.img
extra: You could test a single boot with that image by typing "fastboot boot magisk_patched.img"
if it boots fine you should have root for this single boot / magisk would show as installed.
9 ) When it's done, reboot by typing fastboot reboot
10 ) Open your Magisk Manager app and check if everything is good, and it should be
extra info:
I did worry a bit because the original boot.img is 64 megs , while the patched version is only 12
but i went with it, and it was fine.
good luck to you all
Edit: rewritten entire post so it would look more like a guide, and extra warning because a lot of people seem to loose touch if they don't have the exact same firmware downloaded as on their phone.
Thanks for posting this. I unlocked my bootloader and would like to root like you did.
Do you install magisk first on your phone, then get the magisk_patched file from your phone? Or is the magisk_patched file obtained somewhere else?
testtubebaby said:
Thanks for posting this. I unlocked my bootloader and would like to root like you did.
Do you install magisk first on your phone, then get the magisk_patched file from your phone? Or is the magisk_patched file obtained somewhere else?
Click to expand...
Click to collapse
You need to install the magisk manager
In magisk manager you can click on "install (magisk)"--> "by patching a file"
then you select the file to be patched ( extracted from the original rom )
after that you can copy the patched file from your phone back to the pc and install it via fastboot.
After that magisk is installed
i hope you succeed
pjottrr said:
You need to install the magisk manager
In magisk manager you can click on "install (magisk)"--> "by patching a file"
then you select the file to be patched ( extracted from the original rom )
after that you can copy the patched file from your phone back to the pc and install it via fastboot.
After that magisk is installed
i hope you succeed
Click to expand...
Click to collapse
The firmware I see is the EU firmware. I don't see the GB firmware in the link you posted (it's RETGB). Any idea where I can find the correct firmware?
Sorry, no idea, i found the provided link via google,
testtubebaby said:
The firmware I see is the EU firmware. I don't see the GB firmware in the link you posted (it's RETGB). Any idea where I can find the correct firmware?
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/sofiar/official/
zuggi_m said:
https://mirrors.lolinet.com/firmware/moto/sofiar/official/
Click to expand...
Click to collapse
@zuggi_m , how does posting the same url help?
i don't see a retgb here ....
Maybe someone with more dev experience can tell if you need the exact same firmware or if the version numbers are the same it is ok to use that file ?
No fastbootd?
One Hyper needs fastbootd in order to flash boot and root
mingkee said:
No fastbootd?
One Hyper needs fastbootd in order to flash boot and root
Click to expand...
Click to collapse
i don't really understand the question i guess,
a magisk patched boot is flashed via fastboot. after that you have magisk installed and root access.
pjottrr said:
i don't really understand the question i guess,
a magisk patched boot is flashed via fastboot. after that you have magisk installed and root access.
Click to expand...
Click to collapse
Yours should be G8 Power (9)
Native Android 10 uses fastbootd to flash boot, dtbo, and recovery
mingkee said:
Yours should be G8 Power (9)
Native Android 10 uses fastbootd to flash boot, dtbo, and recovery
Click to expand...
Click to collapse
maybe i'm missing your point here, my description is just so people who have to figure it out can just use my steps to get root, it is indeed based on fastboot flashing . so i'm not sure what you are trying to say, or am i misinterpreting something?
https://forum.xda-developers.com/motorola-one-hyper/development/rom-omnirom-t4044405
I did root on One Hyper (shipped with Android 10) using fastbootd method
Used old method soft brick my One Hyper
That's why I'd like to know
pjottrr said:
so after you unlocked the boot loader ( see my previous post)
you can start rooting with magisk manager / patching the boot.img from the original firmware
I used this thread in order to get root
you need to download the firmware for our device,
That can be found here;
https://mirrors.lolinet.com/firmware/moto/sofiar/official/RETEU/
after that, extract, patch, fastboot install patched version, done.
I did have some issues with the current magisk manager ( from highonandroid, i did find another source, installed version 7.5.1 of the magisk manager from this source
and that one was able to patch the boot.img
I did worry a bit because the original boot.img is 64 megs , while the patched version is only 12
but i went with it, and it was fine.
good luck to you all
Click to expand...
Click to collapse
There's a head up
US version: Sofia
The rest: Sofiar
I will buy US G Power in May and let's the fun begin
Check out One Hyper general to install Dolby Atmos and it can be toggle on/off.
Has anyone tried copying something to the root of the phone or making build.prop edits? I have the Stylus and have achieved root using the same method, however there is something not quite right with the permissions. I cannot make changes to any root files.
CCivale said:
Has anyone tried copying something to the root of the phone or making build.prop edits? I have the Stylus and have achieved root using the same method, however there is something not quite right with the permissions. I cannot make changes to any root files.
Click to expand...
Click to collapse
So you should know G Stylus ROM is Sofiap.
Be aware the way Android 10 flashing is different.
Download and install the latest ADB in order to access fastbootd (fastboot reboot fastboot) and flash boot, recovery, dtbo, vbmeta, and super
Hmmmm, I will have to read more about fastbootd in your other thread.
I did use the boot.img for the sofiap.
Hello,
I followed all the instructions in the first post and was able unlock the bootloader, install magisk, and use it to make the magisk_patched.img file from a boot.img file.
The only variation, was that I got my boot.img file from mirrors.lolinet.com/firmware/moto/sofia/official/RETUS/XT2041-4_SOFIA_RETUS_10_QPM30.80-13-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip since my phone is a US retail model.
After flashing, the phone boots up properly but the touchscreen does not work.
The side buttons do work and I was able to reboot into recovery. In recovery, the build on the phone is indicated as QPM30.80-51. The build in the above indicated file is QPM30.80-13-2. Could this be the source of the problem?
I have tried flashing the original boot.img (from the file above) back and the touchscreen still does not work. I have also tried “wipe data/factory reset” in recovery.
hazd said:
Hello,
I followed all the instructions in the first post and was able unlock the bootloader, install magisk, and use it to make the magisk_patched.img file from a boot.img file.
The only variation, was that I got my boot.img file from mirrors.lolinet.com/firmware/moto/sofia/official/RETUS/XT2041-4_SOFIA_RETUS_10_QPM30.80-13-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip since my phone is a US retail model.
After flashing, the phone boots up properly but the touchscreen does not work.
The side buttons do work and I was able to reboot into recovery. In recovery, the build on the phone is indicated as QPM30.80-51. The build in the above indicated file is QPM30.80-13-2. Could this be the source of the problem?
I have tried flashing the original boot.img (from the file above) back and the touchscreen still does not work. I have also tried “wipe data/factory reset” in recovery.
Click to expand...
Click to collapse
maybe try with the "correct" firmware? ( not sure if the minor diference changes anything, but you could try....
i found it here:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
pjottrr said:
maybe try with the "correct" firmware? ( not sure if the minor diference changes anything, but you could try....
i found it here:
rsdsecure-cloud.motorola.com/download/SOFIA_RETAIL_QPM30.80-51_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Thanks for finding this link.
Unfortunately i am not able to download this for some reason. I get an access denied error message.
edit:
I was able to find the most recent firmware here:
github.com/AndroidDumps/motorola_sofia_dump/tree/sofia_retail-user-10-QPM30.80-51-bd0b4-release-keys
I downloaded just the boot.img file and flashed it. That fixed the touchscreen issue. I then used magisk to batch the boot.img and I now have root.
Just to be clear, this worked on a US retail moto g power purchased unlocked from best buy. The phone model number is XT2041-4.
Hope this helps.
hazd said:
Thanks for finding this link.
Unfortunately i am not able to download this for some reason. I get an access denied error message.
edit:
I was able to find the most recent firmware here:
github.com/AndroidDumps/motorola_sofia_dump/tree/sofia_retail-user-10-QPM30.80-51-bd0b4-release-keys
I downloaded just the boot.img file and flashed it. That fixed the touchscreen issue. I then used magisk to batch the boot.img and I now have root.
Just to be clear, this worked on a US retail moto g power purchased unlocked from best buy. The phone model number is XT2041-4.
Hope this helps.
Click to expand...
Click to collapse
I downloaded the kernel and waiting for the unit.
I can flash full ROM with fastboot and fastbootd, but just flashing kernel would be much faster.
Moreover, check One Hyper general to get Dolby Atmos because you can turn on and off anytime you want.
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.
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!
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.
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
Method 1 works like charm.
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