Database Develop

[Recovery][LG-H960A] TWRP v3.0.2-0 (unofficial)

This is an unofficial TWRP port for LG-H960A.
Thanks to @KAsp3rd and @GROGG88
I DON'T TAKE ANY RESPONSIBILITY. YOU DO EVERYTHING AT YOUR OWN RISK.
READ EVERYTHING and MAKE A BACKUP BEFORE YOU START.
Instructions:
1. You must be on newest stock Marshmallow: H960A20a_00_0316.kdz
You can use LG Bridge to install official update, or download .kdz file HERE
2. You need to have bootloader ulocked.
Official instructions are here: ( Unlocking the Bootloader @ LG Developer )
Remember that this will completely WIPE YOUR DATA, you will LOSE WARRANTY and this operation is IRREVERSIBLE.
3. Flash TWRP.
I assume you got ADB and FASTBOOT drivers working and adb is paired (it should be if you completed step 2).
Connect your phone to your pc, open command prompt and reboot to bootloader:
Code:
adb reboot bootloader
Your phone should reboot and you should be welcomed by Fastboot Mode screen.
Now download the recovery file (below) to your pc, unpack (to get .img) and rename it to recovery.img and put it in folder where you got command prompt open and:
Code:
fastboot flash recovery recovery.img
4. Boot to TWRP.
As on Marshmallow some fastboot commands are not working and LG is restoring recovery on every boot (so you cant use "adb reboot recovery" right now) you need to use one trick.
DO NOT REBOOT YOUR PHONE.
When still in fastboot from step 3 you need to turn off your phone completely. You can do that by holding power button or if that is not working take the battery out.
Now (put the battery in) and press POWER + VOL DOWN buttons. When you see LG logo release the POWER button (while still holding VOL DOWN) and press POWER button again.
You should see a screen which is asking you if you want to factory reset your phone. Don't worry - if you made everything correctly it should not wipe your phone.
Use volume and power buttons to choose YES (twice) - and you should see a TWRP screen (after a while)
WARNING: IF YOU REBOOTED YOUR PHONE AFTER FLASHING RECOVERY THIS STEP WILL REALLY ERASE ALL DATA. You need to flash recovery again (step 3)
5. (optional) flash SuperSU to get root.
Get SuperSU from official thread and put it in your phone.
While in TWRP from step 4 your phone should be recognized by ADB. Use below to move file to sdcard.
Code:
adb push BETA-SuperSU-v2.74-2-20160519174328.zip /sdcard/supersu.zip
Now in TWRP click Install, go to /sdcard/ and chooose supersu.zip. Follow instructions. After install you should choose to wipe cache/dalvik and reboot to system.
Your phone should be rooted now.
Download:
twrp-3.0.2.0-0-h960a.img.zip
(unpack .zip to get flashable .img)
Issues:
- Layout is wrong, status bar is being drawn on second screen.
- Date/time is wrong.

broken url

OK, now if we have recovery, is it possible to dump rooted system and pack it to .tot file for people who don't want to lose warranty?

11868 said:
broken url
Click to expand...
Click to collapse
Oh, true. Fixed.
rascal0pl said:
OK, now if we have recovery, is it possible to dump rooted system and pack it to .tot file for people who don't want to lose warranty?
Click to expand...
Click to collapse
Maybe.

Thank You it worked!

Great. Just bought it 2 days ago for good price. Will try it.
Sent from my LG-H955 using Tapatalk

Hi,
that's just great, thanks a lot.
As root is now possible has anyone tried to install xposed on th H960A?
I'm wondering if the second screen fix for the Telekom V10 also works with the H960A.
What about Viper4Android and AdAway?

rudi666 said:
This is an unofficial TWRP port for LG-H960A.
Thanks to @KAsp3rd and @GROGG88
I DON'T TAKE ANY RESPONSIBILITY. YOU DO EVERYTHING AT YOUR OWN RISK.
READ EVERYTHING and MAKE A BACKUP BEFORE YOU START.
Instructions:
1. You must be on newest stock Marshmallow: H960A20a_00_0316.kdz
You can use LG Bridge to install official update, or download .kdz file HERE
2. You need to have bootloader ulocked.
Official instructions are here: ( Unlocking the Bootloader @ LG Developer )
Remember that this will completely WIPE YOUR DATA, you will LOSE WARRANTY and this operation is IRREVERSIBLE.
3. Flash TWRP.
I assume you got ADB and FASTBOOT drivers working and adb is paired (it should be if you completed step 2).
Connect your phone to your pc, open command prompt and reboot to bootloader:
Code:
adb reboot bootloader
Your phone should reboot and you should be welcomed by Fastboot Mode screen.
Now download the recovery file (below) to your pc, unpack (to get .img) and rename it to recovery.img and put it in folder where you got command prompt open and:
Code:
fastboot flash recovery recovery.img
4. Boot to TWRP.
As on Marshmallow some fastboot commands are not working and LG is restoring recovery on every boot (so you cant use "adb reboot recovery" right now) you need to use one trick.
DO NOT REBOOT YOUR PHONE.
When still in fastboot from step 3 you need to turn off your phone completely. You can do that by holding power button or if that is not working take the battery out.
Now (put the battery in) and press POWER + VOL DOWN buttons. When you see LG logo release the POWER button (while still holding VOL DOWN) and press POWER button again.
You should see a screen which is asking you if you want to factory reset your phone. Don't worry - if you made everything correctly it should not wipe your phone.
Use volume and power buttons to choose YES (twice) - and you should see a TWRP screen (after a while)
WARNING: IF YOU REBOOTED YOUR PHONE AFTER FLASHING RECOVERY THIS STEP WILL REALLY ERASE ALL DATA. You need to flash recovery again (step 3)
5. (optional) flash SuperSU to get root.
Get SuperSU from official thread and put it in your phone.
While in TWRP from step 4 your phone should be recognized by ADB. Use below to move file to sdcard.
Code:
adb push BETA-SuperSU-v2.74-2-20160519174328.zip /sdcard/supersu.zip
Now in TWRP click Install, go to /sdcard/ and chooose supersu.zip. Follow instructions. After install you should choose to wipe cache/dalvik and reboot to system.
Your phone should be rooted now.
Download:
twrp-3.0.2.0-0-h960a.img.zip
(unpack .zip to get flashable .img)
Issues:
- Layout is wrong, status bar is being drawn on second screen.
- Date/time is wrong.
Click to expand...
Click to collapse
Are there any other known issues? I don`t need to install any custom roms. I need it only for root and xposed on Marshmallow. Is there something that can surprise me?

Hi,
"OK, now if we have recovery, is it possible to dump rooted system and pack it to .tot file for people who don't want to lose warranty? "
Ohh, thats sounds nice if this realy possible.
i love my v10.

orbitandre said:
hi,
"ok, now if we have recovery, is it possible to dump rooted system and pack it to .tot file for people who don't want to lose warranty? "
ohh, thats sounds nice if this realy possible.
i love my v10.
Click to expand...
Click to collapse
+1 ??

cyvr1 said:
As root is now possible has anyone tried to install xposed on th H960A?
I'm wondering if the second screen fix for the Telekom V10 also works with the H960A.
What about Viper4Android and AdAway?
Click to expand...
Click to collapse
Didn't try xposed but I think it should work (if it's working on other V10 models - they are not that different). I just recently bought V10 and was disappointed in dpi, so I needed root to patch second screen to be dpi-independent.
Also: why would you want things like Viper4Android when you got really good sounding hifi dac onboard?
fixxxer102 said:
Are there any other known issues? I don`t need to install any custom roms. I need it only for root and xposed on Marshmallow. Is there something that can surprise me?
Click to expand...
Click to collapse
For sure it's enough to flash packages and get root. Xposed is independent from recovery so I can't say anything about that.
Testing are up to you guys. Don't be afraid as this phone is not easy to brick.

rudi666 said:
Also: why would you want things like Viper4Android when you got really good sounding hifi dac on board?
Click to expand...
Click to collapse
Quite simple answer. The onboard Hifi DAC only works with cable headphones. Viper4Android also supports Bluetooth devices.

rudi666 said:
I just recently bought V10 and was disappointed in dpi, so I needed root to patch second screen to be dpi-independent.
Click to expand...
Click to collapse
Could you write a small guide about the dpi change (I prefer 540-580)?
Thanks in advance.

cyvr1 said:
Quite simple answer. The onboard Hifi DAC only works with cable headphones. Viper4Android also supports Bluetooth devices.
Click to expand...
Click to collapse
Ah, you are right, that makes perfect sense. Sorry, I forgot about that.
paschalism said:
Could you write a small guide about the dpi change (I prefer 540-580)?
Click to expand...
Click to collapse
There is still a long way, right now second screen FCs are fixed, but layouts are still wrong. I don't know if I can fix it to be truly dpi-independent but I think 560 is optimal value for this screen.

Is this working with
H960a
V20a-AME-xx??

1k views and only 11 "thanks"??? Really? Guys! We need support devs! Big THANK YOU for ur hard work @rudi666. I haven't try ur method yet but I am happy with the fact that something is beginning to happen with v10
Wysłane z mojego LG-H960 przy użyciu Tapatalka

asmoroth said:
I haven't try ur method yet but I am happy with the fact that something is beginning to happen with v10
Click to expand...
Click to collapse
I did try his method and it worked like a charm. Ok, you'll have to reflash TWRP if you want to use it but I'm sure it's just a matter of time until we have permanent TWRP like th T-Mobile V10 obviously has.
Thanks to rudi666 I have root, xposed, adaway and viper4audio up and running on my V10. And as there are no interesting custom roms to flash in my opinion it does not matter that I'd need to reflash TWRP. If you plan your flashing in advance you can flash all zip files in one go. No real need for TWRP afterwards.

Thanks guys. Unfortunately I see there is not much going on in V10 scene, and it's a shame.
cyvr1 said:
Ok, you'll have to reflash TWRP if you want to use it but I'm sure it's just a matter of time until we have permanent TWRP like th T-Mobile V10 obviously has.
Click to expand...
Click to collapse
Hm.. if you follow instructions you should get permanent TWRP, just try "adb reboot recovery" to test it if you don't want to risk clearing data when using button combination. There is a file called /system/boot-from-recovery.p which is 'restoring recovery' on every boot (that's why there is an info in instruction about not rebooting your phone the first time), but after all the steps this file will be patched. I don't remember if the first use of TWRP or flashing SuperSU does it, but you should get permanent recovery. If not you can always rename this file manually.

rudi666 said:
Hm.. if you follow instructions you should get permanent TWRP, just try "adb reboot recovery" to test it if you don't want to risk clearing data when using button combination. There is a file called /system/boot-from-recovery.p which is 'restoring recovery' on every boot (that's why there is an info in instruction about not rebooting your phone the first time), but after all the steps this file will be patched. I don't remember if the first use of TWRP or flashing SuperSU does it, but you should get permanent recovery. If not you can always rename this file manually.
Click to expand...
Click to collapse
Hi,
I will try that again and see if I can get permanent TWRP. But as I said currently there is no real requirement for that. I flashed SuperSU and both files for xposed when I first booted into recovery and that is all I need at the moment.

i cant enter bootloader
h960A
after adb reboot booloader it keeb restart to soft

[Easy_Root/Unroot][Any_Oreo/Nougat_Firmware_V4_Bootloaders][Tmp_Twrp_Recovery]

EASY ROOT/UNROOT FOR S7 OR S7E ALL NOUGAT OR OREO STOCK ROMS
THANKS @klabit87 FOR OREO ROOT
TEMPORARY TWRP RECOVERY VIA ADB THANKS TO @afaneh92​
This is for AT&T, T-Mobile and Verizon and Sprint running V4 bootloaders only!​
This tool will allow you too easily root any stock rom allowing you to make any modifications you might want then easily unroot for better performance
This will Also give you a fully functional TWRP recovery that can be accessed via adb. TWRP is fully functional on OREO Roms but is limited on Nougat roms
The initial setup does require a data wipe.​
S7 G935T Edge Odin Factory FIrmware Downloads
G935TUVU4CRI2_8.0_4File_USA (T-Mobile).rar
ADB_Root Temporary Twrp Tool Download
S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z
S7 G935 Edge Root/Unroot Odin Files Downloads
These Files Are Needed To Unroot Your Phone
SM_G935_EDGE_OREO.7z
SM_G935_EDGE_NOUGAT.7z
S7 G930 Flat Root/Unroot Odin Files Downloads
These Files Are Needed To Unroot Your Phone
SM_G930_FLAT_OREO.7z
SM_G930_FLAT_NOUGAT.7z
Instructions
1. Download S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z and your model and version you want from above
2. Unzip S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z to S7_S7E_ROOT_UNROOT_ADB_TOOLS folder
3. Unzip the Model/Version file you downloaded and copy the files to the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder and place them in the Odin folder
4. Prepare your phone for a data wipe
5. Reboot your phone to download mode and flash the AP_ROOT_G93*.tar in the Odin AP slot and reboot your phone to recovery
6. Once phone is in recovery run the Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder
7. Now in the cmd window make sure your device is connected and choose Option (1) Launch TWRP
8. Your phone should launch TWRP leave phone plugged in and command window open on computer
9. Now In Twrp choose wipe and choose format data. Type yes in the box when it ask
10. Now in cmd window choose Option(8) Push Root.zip to Phone
11. Now in TWRP choose install and select the Root.zip
12. After zip is installed reboot and go through setup.
13. Once through setup make sure you are rooted
To Unroot Your Phone
1. In the Root Control app choose phone settings and unroot phone make sure phone is connected to computer
2. Now depending on the type of root you choose your phone will reboot to download if you chose system root or stock recovery if you chose systemless root. If your phone reboots to download mode skip to number 5
3. If your phone reboots to recovery once your phone is in recovery run the Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder
4. In cmd window choose Option(3) Unroot phone will reboot too download mode
5. In Odin BL slot choose the BL_G93*_DELETE_CACHE.tar and flash phone will reboot to recovery and say processing update then get an error and strart rebooting recovery
6. Let recovery bootloop at least once thin force phone back to download mode
7. In Odin AP slot flash BL_ENTER_ENG_RECOVERY_G93*.tar and flash phone will reboot to recovery with a bunch of red cache errors
8. In recovery choose wipe cache then reboot back to bootloader from recovery
9. In Odin BL slot choose BL_OREO_STOCK_G93*.tar for Oreo or BL_RESET_DM_VERITY_G93*.tar for Nougat and flash
10. This is important as soon as odin is done flashing and phone powers off immediately hold buttons to force phone to recovery
11. When phone reboots to recovery you will get no command error then when phone shows recovery options in black box at very botton it should say Successfully verified. If it says unsuccessful or failed then start at number 5 again. If successful and on oreo you are done.
12. If on Nougat and successful from recovery reboot to bootloader in Odin BL slot flash BL_NOUGAT_STOCK_G93*.tar
To Reroot Your Phone
1. Reboot to download in Odin AP slot flash AP_ROOT_G93***.tar
2. Phone will reboot then will reboot one more time and you will be rerooted
To Enter TWRP When Rooted
Remember with Nougat TWRP cannot mount data because of encryption so some zips wont work
1. Manually reboot phone to recovery launch Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder and choose Option(1) Launch TWRP
2. To Exit TWRP simply choose reboot
To Enter TWRP When Unrooted
Remember with Nougat TWRP cannot mount data because of encryption so some zips wont work
1. Put phone in download mode In Odin AP slot flash AP_ROOT_G93***.tar force phone to reboot to recovery. If you let phone boot it will reroot and you will have to run the unroot from the root control app.
2. In recovery launch Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder and choose Option(1) Launch TWRP.
3. Do whatever you need too do
4. To exit Twrp choose reboot to Download
5. In Odin BL slot choose the BL_G93*_DELETE_CACHE.tar and flash phone will reboot to recovery and say processing update then get an error and strart rebooting recovery
6. Let recovery bootloop at least once thin force phone back to download mode
7. In Odin AP slot flash BL_ENTER_ENG_RECOVERY_G93*.tar and flash phone will reboot to recovery with a bunch of red cache errors
8. In recovery choose wipe cache then reboot back to bootloader from recovery
9. In Odin BL slot choose BL_OREO_STOCK_G93*.tar for Oreo or BL_RESET_DM_VERITY_G93*.tar for Nougat and flash
10. This is important as soon as odin is done flashing and phone powers off immediately hold buttons to force phone to recovery
11. When phone reboots to recovery you will get no command error then when phone shows recovery options in black box at very botton it should say Successfully verified. If it says unsuccessful or failed then start at number 5 again. If successful and on oreo you are done.
12. If on Nougat and successful from recovery reboot to bootloader in Odin BL slot flash BL_NOUGAT_STOCK_G93*.tar

Beware If you update to new V8 bootloader then rooting and everything will not work. You will be stuck on stock possibly for good

Thank you sir. Amazing is you, works great much better than safestrap and much easier to get into and out of. I hope one day im able to return the favor and help you out with something to make your life easier as you have done with countless people, much appreciated

Thank you so much for all the work you have done here and for injecting this phone with a much needed revitalization.
Now for the first dumb question, what can be flashed? ROMs? Custom Kernel? (Nethunter?) Any idea would ve helpful. Thanks again!

how to know that which version v4 or v8 on are we?

Rehan Ul Hsaan said:
how to know that which version v4 or v8 on are we?
Click to expand...
Click to collapse
The bootloader version is the 5th to last number in the build version
G935XXXX4XXXX
Sent using some kind of device I modified

gdfdedh8d said:
Thank you so much for all the work you have done here and for injecting this phone with a much needed revitalization.
Now for the first dumb question, what can be flashed? ROMs? Custom Kernel? (Nethunter?) Any idea would ve helpful. Thanks again!
Click to expand...
Click to collapse
No custom boot.img can be flashed
Sent using some kind of device I modified

jrkruse said:
The bootloader version is the 5th to last number in the build version
G935XXXX4XXXX
Sent using some kind of device I modified
Click to expand...
Click to collapse
i thinks i updated to "G935TUVS8CRJ1" can i be flash on it?

Quick question. I just used this method to root my phone (v4 bootloader, CRI2 firmware if I'm reading it right). I had been looking at the post [Rom][ALL+CARRIERS_CRF1][Stock_Oreo_Hybrid][Safestrap_Preinstalled]. That one seemed like a good deal because of the followup post on Safestrap flashable zips, like Xposed framework, Extreme Debloater, Dual Speaker, etc....
I didn't consider that ROM because of the big warning Must Be On Stock CRF1, whereas I'm on CRI2 and this looked nicer anyway.
So, just to be sure I understand, now that I've used this method to root my phone I can install all those things and more by using this technique to get into TWRP on my phone. Correct? Further, I can use TWRP in this way to flash anything except a custom bootloader. Yes?
More specifically, all those ROMs listed over in the general Tools Samsung Galaxy S7 Edge ROMs, Kernels, Recoveries, & Other Development forum that say "for G9350 only", I can use this TWRP to flash those on my G935T ?? Is that right?

Rehan Ul Hsaan said:
i thinks i updated to "G935TUVS8CRJ1" can i be flash on it?
Click to expand...
Click to collapse
Nope that's v8

jrkruse said:
Nope that's v8
Click to expand...
Click to collapse
My bad luck ?

Rehan Ul Hsaan said:
My bad luck
Click to expand...
Click to collapse
Should have been aware of what you are flashing a bootloader update is always an attempt to patch something. Usually root related. It is never to benefit the user. The first indication to me would have been a 4 version jump in bootloader versions all in one shot. I warned people all along that a bootloader change would come one of these days and kill root. Sprint seen it months ago. Tmobile and Sprint can now have there cozy little relationship with one another. I feel bad for you tmobile people. Remember when tmobile was the friendly carrier in the dev community along with sprint as well now they are the most unfriendly carrier in the dev community.

SailorJoe6 said:
Quick question. I just used this method to root my phone (v4 bootloader, CRI2 firmware if I'm reading it right). I had been looking at the post [Rom][ALL+CARRIERS_CRF1][Stock_Oreo_Hybrid][Safestrap_Preinstalled]. That one seemed like a good deal because of the followup post on Safestrap flashable zips, like Xposed framework, Extreme Debloater, Dual Speaker, etc....
I didn't consider that ROM because of the big warning Must Be On Stock CRF1, whereas I'm on CRI2 and this looked nicer anyway.
So, just to be sure I understand, now that I've used this method to root my phone I can install all those things and more by using this technique to get into TWRP on my phone. Correct? Further, I can use TWRP in this way to flash anything except a custom bootloader. Yes?
More specifically, all those ROMs listed over in the general Tools Samsung Galaxy S7 Edge ROMs, Kernels, Recoveries, & Other Development forum that say "for G9350 only", I can use this TWRP to flash those on my G935T ?? Is that right?
Click to expand...
Click to collapse
Twrp gives you no more options than you had before. You cannot just magically go flashing anything you want just because you have twrp. You can run a stock rom and mod it a little and that is it

How do you know what bootloader you're running?

i can not install this metod .
i have problem with sw. rev check faiL device, can any dody help me & please
i use OS G935TUVS8CRJ1

Does this require the fixes for lag/battery life?

jrkruse said:
Beware If you update to new V8 bootloader then rooting and everything will not work. You will be stuck on stock possibly for good
Click to expand...
Click to collapse
im exactly onthis s7 verizon heroltevzw sm g930v latest firmware oreo8.0
v8 bootloader locked:laugh:
can i downgrade and follow your path,s?
if no f9vk it
then time to move on upgrade, please can you recomend me some decent device better/much better than s7 that i can root without bricked it down to paperweight?
thankyou
much appreciated
cheers

omgaruda said:
can i downgrade and follow your path,s?
if no f9vk it
then time to move on upgrade, please can you recomend me some decent device better/much better than s7 that i can root without bricked it down to paperweight?
Click to expand...
Click to collapse
No, if your build number indicates that you're on the v8 bootloader, you're screwed for now. If you like the S7's features, you can grab an Exynos. Those you can root and modify to your heart's content. Plenty of custom ROMs available. It's not too expensive either. It's what I'm going to upgrade to, since I'm tired of this bull with the bootloader, and my glass is cracked anyway. Would probably cost nearly as much to repair as to just buy an Exynos.

S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z this is a trojan

Ihavetodothis said:
S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z this is a trojan
Click to expand...
Click to collapse
That's a false positive by a single antivirus program. VirusTotal gives it clean on 54 out of 56 antivirus programs, and one of those is merely "suspicious," probably because it's a rooting tool.

Question [Updated] This is ENG binary Please Use USER binary after stock flash with Odin

New update to topic:
I decided to repair the software of my Galaxy S21 (Exynos) by flashing official firmware from Samfirmware, same version as I was running. It was in a bootloop before, so there was nothing esle to do. Phone was rooted with magisk, stock recovery.
I found what my firmware is from the recovery, found the exact same file, with the correct CSC.
Downloaded that firmware from Samfirmware, downloaded patched Odin from XDA.
Added, flashed, used HOME_CSC in order to preserve my data.
Reboot and immediately before I even get the boot logo or the charging animation, I get this error:
This is ENG binary Please Use USER binary
Allegedly this is what happens when you flash an engineering build, not an official one. But how? I downloaded and flashed official stuff? It's the exact same version my phone is already running. Where did I go wrong and how can I fix that?
I've attached the Download screen of my phone.
Thanks!
Old news:
Hello,
Hope this is the right place to ask for this kind of help.
I have a Galaxy S21 5G (SM-G991B), rooted with Magisk back in March 2021. Phone is bootloader unlocked, not encrypted, but the recovery is stock. Version currently running is Android 11. USB Debugging is enabled, but my computer is listed as unauthorised.
Yesterday my phone died due to low battery, so I plugged it and after it charged a bit I switched it on, only to be greeted with a constant bootloop. The bootloop is "soft", meaning only the system crashes, it doesn't go all the way to the initial boot screen (as if the battery was unplugged). The phone crashes about 1-2 seconds after the initial lockscreen is displayed.
Is there any way to help me recover this and save my phone? My entire life is there, from photos that can't be recovered, to authenticators I need for work and bank logins I need to be able to pay rent.
I thought about flashing TWRP and just doing a backup from there, but would it be as simple as that? All the tutorials talk about requiring to flash some extra zips and wiping the data, but those tutorials are combo root+twrp tutorials, and I've already done those steps. so no wiping should be needed to put TWRP on?
I'd be very grateful if anyone is profficient enough to help me recover the data, I already gave the phone to a data recovery company but they say it's unlikely anything will come out of it. If you manage to help me get my phone working as it was (or at least get my data back somehow), I'd gladly pay you the money for your efforts.
Help me XDA, you're my only hope.
Click to expand...
Click to collapse

Flashing TWRP = having to delete data (to be able to access the internal storage)
I am pretty sure (wait for confirmation before doing it) that if you flash the HOME_CSC file instead of the CSC on Odin it keeps your data.
This is why we need to vote with our wallets and buy phones with sd cards. I dont really care, because I never keep anything important on my phone, but I feel for you buddy.
EDIT: from here: https://www.droidviews.com/difference-between-csc-and-home_csc-samsung-firmware/
CSC – If you flash the CSC file, it’ll perform a factory reset of your Galaxy device and wipe all data while installing a new firmware to bring your device to the same state as it was when you purchased it. Go with CSC if you want a clean installation.
HOME_CSC – On the other hand, if you want to keep your Samsung phone’s data and settings even flashing the stock firmware, you can select the HOME_CSC file.
At your own risk, pls dont blame me if it doesnt work!

Flash a patched vbmeta again

GeeAyeZee said:
Flash a patched vbmeta again
Click to expand...
Click to collapse
Hi, what do you mean? Flash both TWRP and vbmeta, as if I'm doing it for the first time?
I think the phone was already decrypted while following the Magisk root tutorial, so these two steps should be the only thing necessary for the phone to boot to TWRP, right? I know how to rescue everything once I'm in there.

Try entering safe mode and disable all magisk modules:
Power on your Galaxy phone or tablet in Safe mode
We’ll walk you through how to start your Samsung Galaxy phone or tablet in Safe mode. This mode prevents third-party apps from running on your device.
www.samsung.com
You can access adb when on recovery mode or download mode so you can also enter safe mode via one of these commands:
setprop persist.sys.safemode 1
or
echo "1" > /data/property/persist.sys.safemode

dikime said:
Hi, what do you mean? Flash both TWRP and vbmeta, as if I'm doing it for the first time?
I think the phone was already decrypted while following the Magisk root tutorial, so these two steps should be the only thing necessary for the phone to boot to TWRP, right? I know how to rescue everything once I'm in there.
Click to expand...
Click to collapse
Flash the vbmeta file in odin

shaharofir said:
Try entering safe mode and disable all magisk modules:
Power on your Galaxy phone or tablet in Safe mode
We’ll walk you through how to start your Samsung Galaxy phone or tablet in Safe mode. This mode prevents third-party apps from running on your device.
www.samsung.com
You can access adb when on recovery mode or download mode so you can also enter safe mode via one of these commands:
setprop persist.sys.safemode 1
or
echo "1" > /data/property/persist.sys.safemode
Click to expand...
Click to collapse
The phone auto-enters safe mode after a few bootloops, so I guess that's beat. When the phone is in stock recovery, doing any adb commands tells me the device is recognized, but "unauthorized".

dikime said:
The phone auto-enters safe mode after a few bootloops, so I guess that's beat. When the phone is in stock recovery, doing any adb commands tells me the device is recognized, but "unauthorized
Click to expand...
Click to collapse
So you can enter download mode and flash stock (just super)

You gonna have to get authorized again. Check youtube for help. I had that issue a couple months ago. Think it had to delete the android folder and reinstall adb

Alright, decided to flash stock firmware with Odin. Found my files from Samfirmware, and since I want to keep my data, flashed HOME_CSC. Now the phone won't boot at all, giving the error:
This is ENG binary, please use USER
Now why did this happen and can I do anything to change that? I would really like to not flash CSC and wipe my phone, but it's looking more and more likely.
I used the patched 3.14.1 Odin, could that be the issue? Shouldn't matter.
The Download mode screen says:

How to update a rooted S20 FE 5G (SD) without data loss?

I have bought a S20 FE with Snapdragon and updated it to the newest version from December/January.
After that I flashed TWRP on it and added Magisk.
Now I saw there is a newer firmware from February and I would like to know, how to update the phone without losing all data or if there is a tutorial for doing that?
Thank you, guys.
---
Solution (for me, at least) for firmware update with TWRP and root (Magisk):
- download/copy Magisk-v25.2.apk (or newer) to internal storage of phone
- download your correct firmware, unpack it and delete the CSC file (not HOME_CSC) to PC
- connect USB cable to PC
- turn off phone and go into download mode (press volume down + volume up and quickly connect USB cable (which is still connected to PC))
- open Odin and remove ticks on auto-connect and re-partition (if set)
- flash in Odin all slots (BL, AP, CP, CSC, USERDATA), but use the HOME_CSC instead of the CSC file and vbmeta_disabled.tar under USERDATA
- reboot to download mode within Odin, if possible, otherwise go to download mode again like in first step
- reset/open Odin and remove ticks on auto-connect and re-partition (if set)
- flash in Odin TWRP under AP and vbmeta_disabled.tar under USERDATA
- reboot to TWRP (volume up + power)
- disable encryption: advanced > terminal > type multidisabler
- flash the Magisk apk
- reboot
You need the vbmeta_disabled.tar file, the newest Magisk apk, the correct firmware, the fitting TWRP and Odin for this solution to work.

xsycox said:
I have bought a S20 FE with Snapdragon and updated it to the newest version from December/January.
After that I flashed TWRP on it and added Magisk.
Now I saw there is a newer firmware from February and I would like to know, how to update the phone without losing all data or if there is a tutorial for doing that?
Thank you, guys.
Click to expand...
Click to collapse
Simply use Odin to flash the new firmware package. Make sure you use HOME_CSC, not CSC. After you've flashed the updated firmware, you'll have to reflash TWRP and re-root with Magisk.

Thank you, but wait, if I flash TWRP I have to do a factory reset again, right?
And do I have to tick/add all fields (BP, AP, CP, CSC)?

xsycox said:
Thank you, but wait, if I flash TWRP I have to do a factory reset again, right?
And do I have to tick/add all fields (BP, AP, CP, CSC)?
Click to expand...
Click to collapse
here's a quick guide by Afaneh92 the twrp dev
Note: steps 2-6 are important, missing any will lose your data.
1. Load all files to their respective slots in odin, pick HOME_CSC instead of CSC.
2. Uncheck auto reboot in Odin and hit start.
3. Reboot to download if possible from odin options (not working on all devices), or using buttons combo.
4. Keep auto reboot unchecked, Flash TWRP in AP slot and vbmeta_disabled.tar in USERDATA
5. Hold volume down and power until the screen goes black then immediately switch to holding volume up and power to reboot into TWRP.
6. Disable encryption:
- Go to Advanced > Terminal, type: multidisabler.
You will see " - Finished." When it is done.
7. flash custom kernel and magisk then reboot to system (optional).

Yeah, that did not work. I used the correct AP, CP, BL and HOME_CSC files and vbmeta_disabled.tar, but now it is in bootloop. :/
I flashed TWRP again and am trying now to get a TWRP backup running again I did earlier.

Backup restoration worked. I also think, I found the problem. Will try it again tomorrow or on Sunday.

I have updated the initial post with the successful procedure, just in case other people are in the same situation.

Guess this method should work with s20(non fe) too?
I use a custom ROM and can access all my files via twrp are you able to access your data partition via TWRP with this method?

k2828 said:
Guess this method should work with s20(non fe) too?
I use a custom ROM and can access all my files via twrp are you able to access your data partition via TWRP with this method?
Click to expand...
Click to collapse
Yes, if you do all steps (not forgetting step 9), it should work. I can access everything up to now on every update.
I use this/my guide now for a while (two updates since March).

xsycox said:
Yes, if you do all steps (not forgetting step 9), it should work. I can access everything up to now on every update.
I use this/my guide now for a while (two updates since March).
Click to expand...
Click to collapse
is it possible to leave out a step so my files arent accessible via twrp?
maybe the following one:
- disable encryption: advanced > terminal > type multidisabler

I think that thinking that nothing will happen and you will not lose the data in the ways that they tell you here is naive.
Backup first and then update SAFELY as they tell you.
I would not risk doing what has already been said of using Home_csc and apart from being root.
that cures it
I recommend everyone who reads my comment. Better always support.
then do what the classmates say
one mistake and you lose all your information.

k2828 said:
is it possible to leave out a step so my files arent accessible via twrp?
maybe the following one:
- disable encryption: advanced > terminal > type multidisabler
Click to expand...
Click to collapse
yes you can do that but twrp will be very limited.

3mel said:
yes you can do that but twrp will be very limited.
Click to expand...
Click to collapse
You could still flash stuff, but can't backup and restore I guess?
Can I leave out the following step, as I don't need TWRP:
-flash in Odin TWRP under AP and vbmeta_disabled.tar under USERDATA

k2828 said:
You could still flash stuff, but can't backup and restore I guess?
Can I leave out the following step, as I don't need TWRP:
-flash in Odin TWRP under AP and vbmeta_disabled.tar under USERDATA
Click to expand...
Click to collapse
yes
edit: you could still flash stuff from an OTG adaptor with anything from a flash to a hard-drive. you could also push files to /data/ I'm told even if encrypted... never tried that out but it's an option if you did flash twrp.

Question Fixed - Root help

It's been years since I've rooted an Android device so I gotta say it's been fun getting back to it, if a little bit frustrating. This is the first Samsung device I've owned and I can't wait to get another ROM. Here's what I've done, many times, without success.
1. unlock bootloader
2. download Samfw.com_SM-X200_XAR_X200XXU2CWC1_fac (went from Android 11 to 13)
3. flashed above firmware with Odin3 v3.14.1
4. setup device (basic - bypassed Google login, Samsung installs and options)
5. installed Magisk-v26.1 on tablet
5. Extracted boot.img from AP_.tar, copied to tablet, patched with magisk, back to PC, created boot.tar from magisk patch
6. Odin flash again, added BL from firmware, AP was patched boot.tar from magisk, CSC from firmware.
I've read to flash only the patched boot image (.tar), to patch the full AP package, to flash boot image and add back to AP file, and I've tried all three without success.
My first attempt was with X200XXU1AVC1, with the same result, so I flashed the Android 13 for all subsequent steps.
I feel like I've done everything correctly and could use some guidance in resolving why I can't achieve root.
EDIT: resolved, i didn't know about sideloading magisk!

jcunwired said:
It's been years since I've rooted an Android device so I gotta say it's been fun getting back to it, if a little bit frustrating. This is the first Samsung device I've owned and I can't wait to get another ROM. Here's what I've done, many times, without success.
1. unlock bootloader
2. download Samfw.com_SM-X200_XAR_X200XXU2CWC1_fac (went from Android 11 to 13)
3. flashed above firmware with Odin3 v3.14.1
4. setup device (basic - bypassed Google login, Samsung installs and options)
5. installed Magisk-v26.1 on tablet
5. Extracted boot.img from AP_.tar, copied to tablet, patched with magisk, back to PC, created boot.tar from magisk patch
6. Odin flash again, added BL from firmware, AP was patched boot.tar from magisk, CSC from firmware.
I've read to flash only the patched boot image (.tar), to patch the full AP package, to flash boot image and add back to AP file, and I've tried all three without success.
My first attempt was with X200XXU1AVC1, with the same result, so I flashed the Android 13 for all subsequent steps.
I feel like I've done everything correctly and could use some guidance in resolving why I can't achieve root.
EDIT: resolved, i didn't know about sideloading magisk!
Click to expand...
Click to collapse
I don't understand what you mean by "sideloading magisk". Did you read my post #84? That work with the previous version of Android 13, CWA3. I just copied Magisk apk to the SD card and installed it from there.

lewmur said:
I don't understand what you mean by "sideloading magisk". Did you read my post #84? That work with the previous version of Android 13, CWA3. I just copied Magisk apk to the SD card and installed it from there.
Click to expand...
Click to collapse
Select update from adb in recovery, then:
adb devices
adb sideload Magisk-v26.1.zip

jcunwired said:
Select update from adb in recovery, then:
adb devices
adb sideload Magisk-v26.1.zip
Click to expand...
Click to collapse
I know how to do it. I just don't understand what difference it makes. Why not just copy it to the tablet and install it?

lewmur said:
I know how to do it. I just don't understand what difference it makes. Why not just copy it to the tablet and install it?
Click to expand...
Click to collapse
Because I was in ADB and like you said, what difference does it make?

jcunwired said:
Because I was in ADB and like you said, what difference does it make?
Click to expand...
Click to collapse
The difference is that your post said you installed Magisk and used it to patch the boot.img and it didn't work. Then the edit said you solved it by using adb to sideload magisk and that solved the problem. I'm still trying to understand how it did.