Database Develop

[TWRP 3.0.2-1][ROOT] Samsung galaxy A9 pro SM-A910F/9100 - 26/7/2016

TWRP 3.0.2-1. for the Samsung Galaxy A9 pro SM-A910/9100 - Qualcomm MSM8976
Please note I don't own this device.
Stock Recovery is posted below if required.
NOTE:
FLASHING CUSTOM STUFF VOIDS YOUR WARRANTY. THIS WILL TRIP THE KNOX FLAG.
Install:
Boot to download mode.
Flash with Odin using the AP slot.
Uncheck Auto-reboot.
Reboot to recovery immediately after flashing using POWER + HOME + VOL DOWN, as soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
TWRP should now boot.
NOTE: ON SOME ANDROID 5.1.1 and 6.01 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Install with ODIN:
twrp_3.0.2-1_sm-a910f_25716
Update 8/2/2017
Fixed build for latest firmware :
twrp_3.0.2-1_sm-a910_a9100_7217
Stock recovery:
A910FXXU1APFC_stock_recovery
IMPORTANT
At the moment TWRP isn't working with encryption, this means the DATA Partition and internal storage cannot be mounted.
To mount the Data partition encryption needs to be removed and the boot image patcher needs to be flashed below
This can be done via the FORMAT DATA button under the WIPE option in TWRP.
Please note this will erase all user data.
The boot image patcher can be flashed with TWRP.
The boot image patcher MUST be flashed before booting the device to system or the DATA partition will be re-encrypted at boot time.
BOOT IMAGE PATCHER
Boot image patcher to remove DM-verity and Forced encryption.
Instead of flashing one of the boot images above flash the zip below with TWRP.
This was built by jcadduono not me, so props to him, I just modified it to work for this device and to remove the SEANDROID ENFORCING message.
Steps:
1. BOOT TO TWRP
2. FORMAT DATA
3. FLASH SUPERSU
4. FLASH THE BOOT IMAGE PATCHER
5. REBOOT TO RECOVERY
6. CHECK DATA IS STILL MOUNTABLE
no-verity-no-encrypt_ashyx
TO ROOT
Flash the file below in twrp.
http://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.

Reserved

Thanks mate
everything is working
---------- Post added at 12:49 ---------- Previous post was at 12:43 ----------
may you know how to do Custom Boot Splash for A9100 pro ?

Hi, I'm on firmware A9100ZCU1APD5 so these boot images wont work right. So now to be able to mount data, what I got is that I'll have to first wipe data in twrp and then flash the boot image patcher in order to get full access to twrp?

omar.abbas said:
Hi, I'm on firmware A9100ZCU1APD5 so these boot images wont work right. So now to be able to mount data, what I got is that I'll have to first wipe data in twrp and then flash the boot image patcher in order to get full access to twrp?
Click to expand...
Click to collapse
TWRP >BOOT IMAGE PATCHER >FORMAT DATA >SUPERSU
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU

ashyx said:
TWRP >BOOT IMAGE PATCHER >FORMAT DATA >SUPERSU
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
Thanks I'll try now and get back to you
Sent from my SM-A9100 using XDA-Developers mobile app

Wow thanks a lot it works. Dont have to change the language to English everytime I boot into recovery ? and can finally make backups. Thanks once again, you're the man!!
Sent from my SM-A9100 using XDA-Developers mobile app

Thanks, hope for more development.
Thanks for the development, not much out there for the A9100/A910f. Own a A9100(CH), which came without any Google apps and full of Chinese applications and region locked. Was able to load recovery and unencrypt boot, root, sideload Google apps. Is there a way to remove my region lock? Wish someone would develope the A910f international firmware to port over to the A9100. The A9 phone has some pretty impressive specs, hope for more development. Thank you.

gsnewport said:
Thanks for the development, not much out there for the A9100/A910f. Own a A9100(CH), which came without any Google apps and full of Chinese applications and region locked. Was able to load recovery and unencrypt boot, root, sideload Google apps. Is there a way to remove my region lock? Wish someone would develope the A910f international firmware to port over to the A9100. The A9 phone has some pretty impressive specs, hope for more development. Thank you.
Click to expand...
Click to collapse
By region lock you mean unable to flash with ODIN?
You can use FLASHFIRE to flash the stock firmware.
Sent from my SM-T280 using XDA-Developers mobile app

ashyx said:
By region lock you mean unable to flash with ODIN?
You can use FLASHFIRE to flash the stock firmware.
Sent from my SM-T280 using XDA-Developers mobile app
Click to expand...
Click to collapse
No, flashed recovery with Odin. I mean by region locked is the csc file is just for China and it's the only csc on the phone. So I'm seeing some Chinese in some of the stock apps still even though I changed the language to english. Location is working for me. But some of the apps still show Chinese

gsnewport said:
No, flashed recovery with Odin. I mean by region locked is the csc file is just for China and it's the only csc on the phone. So I'm seeing some Chinese in some of the stock apps still even though I changed the language to english. Location is working for me. But some of the apps still show Chinese
Click to expand...
Click to collapse
So what's actually stopping you from flashing another rom? Like I say you can use Flashfire.

Would like to stay stock Marshmallow 6.0.1. Tried to flash the rom for the A910f but if failed, same with the A9000(Android L). Both of these roms have multiple crc files for other regions. I think the failure is being caused by partition size. Didn't want to mess with for fear of bricking.

ashyx said:
So what's actually stopping you from flashing another rom? Like I say you can use Flashfire.
Click to expand...
Click to collapse
Have you tried it? Does it work? I tried using Odin but got some partition size errors and soft bricked my phone. So just need to make sure before I give Flashfire a go.
Sent from my SM-A9100 using XDA-Developers mobile app

So the actual failure to flash is the partition size, but which partition is failing?
More info needed here.
There are ways of adjusting the partition size on the device by simply flashing with the required PIT file.
Or the actual image itself can be resized to fit.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU

ashyx said:
So the actual failure to flash is the partition size, but which partition is failing?
More info needed here.
There are ways of adjusting the partition size on the device by simply flashing with the required PIT file.
Or the actual image itself can be resized to fit.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
I can't remember which partition size error it was as it was a few days ago. So do you know anyone who has done that on this phone successfully? Because if it is possible then thats all I'd want right now.
Sent from my SM-A9100 using XDA-Developers mobile app

omar.abbas said:
I can't remember which partition size error it was as it was a few days ago. So do you know anyone who has done that on this phone successfully? Because if it is possible then thats all I'd want right now.
Sent from my SM-A9100 using XDA-Developers mobile app
Click to expand...
Click to collapse
It is possible as I myself have done it with other devices.
If you can try the flash again with ODIN and then post the output log then we can find out which partition fails.
Just reflash your stock firmware after the failure.
By the way I don't own this particular device.
In the meantime I'm going to download the stock A9100 firmware and check the image sizes against the a910f firmware.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU

I tried to flash the A910F with Odin and It's give Auth fail on pitfile and stops there. I downloaded the firmware via samfirm 0.36 with binary to get the full 4 firmware files. Extract the pit file, point to it in Odin and BL, CSC, CP, AP in their slots and it always fail. Also does not work with flashfire with a single firmware file.
But now there is another way, I did it yesterday and works great. No Chinese! Credits to @dadimon29. You flash the full A9100 firmware but untick autoreboot. Once finished you boot back in download mode and flash @ashyx TWRP with Odin with no reboot. Reboot again to TWRP, flash the no-verity-no-encrypt_ashyx.zip, reboot again to twrp, now format data not wipe! Mount system and flash Supersu, your own CSC file and GPS.conf for your region and the GAPPS micro package. Now reboot to samsung and you will find everything is English or whatever language you prefer. And Google works out of the box, no permission errors. Now I can keep this phone!

steberg said:
I tried to flash the A910F with Odin and It's give Auth fail on pitfile and stops there. I downloaded the firmware via samfirm 0.36 with binary to get the full 4 firmware files. Extract the pit file, point to it in Odin and BL, CSC, CP, AP in their slots and it always fail. Also does not work with flashfire with a single firmware file.
But now there is another way, I did it yesterday and works great. No Chinese! Credits to @dadimon29. You flash the full A9100 firmware but untick autoreboot. Once finished you boot back in download mode and flash @ashyx TWRP with Odin with no reboot. Reboot again to TWRP, flash the no-verity-no-encrypt_ashyx.zip, reboot again to twrp, now format data not wipe! Mount system and flash Supersu, your own CSC file and GPS.conf for your region and the GAPPS micro package. Now reboot to samsung and you will find everything is English or whatever language you prefer. And Google works out of the box, no permission errors. Now I can keep this phone!
Click to expand...
Click to collapse
Could you tell me what firmware files you downloaded exactly? When you reboot your phone, does it show Galaxy A9 Pro in english? I'm still a little confused on the procedure too
Sent from my SM-A9100 using XDA-Developers mobile app

In order to get rid of the Chinese when you boot up I guess you have to flash the bootloader from A910F but you can't.
Download Samfirm 0.36 and download the latest SM-A9100 firmware.
http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Be sure to tick Binary Nature.

gsnewport said:
Thanks for the development, not much out there for the A9100/A910f. Own a A9100(CH), which came without any Google apps and full of Chinese applications and region locked. Was able to load recovery and unencrypt boot, root, sideload Google apps. Is there a way to remove my region lock? Wish someone would develope the A910f international firmware to port over to the A9100. The A9 phone has some pretty impressive specs, hope for more development. Thank you.
Click to expand...
Click to collapse
You can try this out.
I have repacked the A910F firmware so it will be flashable on the A9100. I have replaced the A910F build.prop with the A9100 build.prop to help prevent boot issues.
It is the system image only. It should flash fine with ODIN in the AP slot. Whether it will boot or not is another matter, but I should think it will. If everything will be working, I don't know.
It may also be necessary to flash the A910F kernel boot.img. NOTE: this boot.img does not support encryption.
A910FXXU1APFC_no_encryptable_boot
Make sure you have a TWRP backup of the system partition or the stock firmware before flashing just in case you need to restore.
sm-a9100_system.img.tar.zip
.
.

Magisk without TWRP, with full device encryption?

I have a Samsung Galaxy S7 edge, international version, Android 6, unlocked bootloader, rooted with CF-auto-root, now has SuperSU installed, pure stock rom.
And I am wondering whether it will be possible to install Magisk (even if I have to uninstall SuperSU) without TWRP or any other custom recovery?
Will it also be possible to have full disk encryption (to be honest I don’t know whether my device is currently encrypted - is there a way to check this)?

orifori said:
I have a Samsung Galaxy S7 edge, international version, Android 6, unlocked bootloader, rooted with CF-auto-root, now has SuperSU installed, pure stock rom.
And I am wondering whether it will be possible to install Magisk (even if I have to uninstall SuperSU) without TWRP or any other custom recovery?
Will it also be possible to have full disk encryption (to be honest I don’t know whether my device is currently encrypted - is there a way to check this)?
Click to expand...
Click to collapse
Yes it is possible... Check the magisk release thread for the method applicable for you... About encryption, it works just fine...
Edit: here https://forum.xda-developers.com/showthread.php?t=3473445
Sent from my MI 5 using Tapatalk

Thank you! I need some help regarding the Installation Instructions.
The stock rom I have (which is to be patched by Magisk Manager) is a ZIP file with 5 .tar.md5 files in it...
1 - Where should I copy it - internal phone memory?
2 - Should I copy the ZIP file or the 5 files in it?
3 - Magisk Manager asks for .RAR or .IMG file while I have a .ZIP - should I simply rename the .ZIP to .RAR or...?
4 - Installing CSC_... would do a wipe while HOME_CSC_... would not - and I definitely do not want a wipe - so how to proceed?
5 - If I want full device encryption I just tick Preserve force encryption option (I don't know whether the phone is now encrypted)?

orifori said:
Thank you! I need some help regarding the Installation Instructions.
The stock rom I have (which is to be patched by Magisk Manager) is a ZIP file with 5 .tar.md5 files in it...
1 - Where should I copy it - internal phone memory?
2 - Should I copy the ZIP file or the 5 files in it?
3 - Magisk Manager asks for .RAR or .IMG file while I have a .ZIP - should I simply rename the .ZIP to .RAR or...?
4 - Installing CSC_... would do a wipe while HOME_CSC_... would not - and I definitely do not want a wipe - so how to proceed?
5 - If I want full device encryption I just tick Preserve force encryption option (I don't know whether the phone is now encrypted)?
Click to expand...
Click to collapse
You need to patch and flash the boot image only. That'll be inside the ROM zip. Don't forget to change the output format in the Manager settings to .img.tar.
It usually says under Android settings -> Security if your device is encrypted or not. But I've no idea if Samsung do that. I don't do Samsung.
This has been discussed a few times in the Magisk forums already, so if you search you'll be able to find more info on it. Always do your homework before flashing...
Examples of threads to search and/or read trough:
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
https://forum.xda-developers.com/apps/magisk/magisk-discussion-thread-t3467229
https://forum.xda-developers.com/apps/magisk/flashing-patched-boot-img-odin-t3670503

Worked like a charm, thank you! Extracted AP_... file from the zip archive, them extracted boot.img file from AP_... file and copied it onto the SD card of the phone, then Magisk modified it, I copied it to my laptop and flashed it in Odin (AP field).

Everything works fine, except OTA updates - I try to download updates manually (About device -> Download updates manually) but I get a message "The operating system on your device has been modified in an unauthorized way."
So are OTA updates possible 1. without TWRP and 2. with preserved encryption - like in my case - and how is that possible? Maybe Magisk settings?

orifori said:
Everything works fine, except OTA updates - I try to download updates manually (About device -> Download updates manually) but I get a message "The operating system on your device has been modified in an unauthorized way."
So are OTA updates possible 1. without TWRP and 2. with preserved encryption - like in my case - and how is that possible? Maybe Magisk settings?
Click to expand...
Click to collapse
In order to be able to take an ota, you need stock recovery, with unmodified system, and probably stock boot... (Magisk only touched the boot.img, so you just need to restore that)...
Sent from my MI 5 using Tapatalk

orifori said:
Everything works fine, except OTA updates - I try to download updates manually (About device -> Download updates manually) but I get a message "The operating system on your device has been modified in an unauthorized way."
So are OTA updates possible 1. without TWRP and 2. with preserved encryption - like in my case - and how is that possible? Maybe Magisk settings?
Click to expand...
Click to collapse
You can't update with OTA if you've modified /system or the boot image (Magisk). A custom recovery would also cause it to fail, but that's not an issue for you...
Since you've got a Samsung there are probably more checks as well (unlocked bootloader and such).
You might have to flash updates manually... Best place for answers would be your device's forum.

Didgeridoohan said:
You can't update with OTA if you've modified /system or the boot image (Magisk)
Click to expand...
Click to collapse
So there is absolutely no chance for OTA updates in case of installed Magisk? I have a pure stock rom and the only thing modified is the boot.img file (modified by Magisk in order to gain root).

orifori said:
So there is absolutely no chance for OTA updates in case of installed Magisk? I have a pure stock rom and the only thing modified is the boot.img file (modified by Magisk in order to gain root).
Click to expand...
Click to collapse
You could restore the stock boot image to get the OTA and then re-root.
Don't know if Samsung updates care about KNOX (which will be triggered). I don't think they do, but I don't do Samsung so I can't say for sure...

I am trying to root my phone using magisk. I do not have any custom recovery. I was told that I can still root it by patching my stock boot image. But I couldn't find it anywhere. I do have my phone's stock firmware, and if I'm not wrong it Should be inside it, but the problem is that, the firmware file is in .nb0 format. I do not know how to open it and get access to the boot.img, can someone please help me.
My phone is Infocus m535
This is the firmware ?
mediafire.com/file/y2zru5gda08jder/Infocus_M535_G40-026P-0-00WW-A02.zip
???? Please help

Loku_kika said:
I am trying to root my phone using magisk. I do not have any custom recovery. I was told that I can still root it by patching my stock boot image. But I couldn't find it anywhere. I do have my phone's stock firmware, and if I'm not wrong it Should be inside it, but the problem is that, the firmware file is in .nb0 format. I do not know how to open it and get access to the boot.img, can someone please help me.
My phone is Infocus m535
This is the firmware [emoji116]
mediafire.com/file/y2zru5gda08jder/Infocus_M535_G40-026P-0-00WW-A02.zip
[emoji120][emoji120][emoji120][emoji120] Please help
Click to expand...
Click to collapse
Try 7zip...
You have to have an unlocked bootloader and a working fastboot in order to root without custom recovery...
Sent from my MI 5 using Tapatalk

Loku_kika said:
I am trying to root my phone using magisk. I do not have any custom recovery. I was told that I can still root it by patching my stock boot image. But I couldn't find it anywhere. I do have my phone's stock firmware, and if I'm not wrong it Should be inside it, but the problem is that, the firmware file is in .nb0 format. I do not know how to open it and get access to the boot.img, can someone please help me.
My phone is Infocus m535
This is the firmware
mediafire.com/file/y2zru5gda08jder/Infocus_M535_G40-026P-0-00WW-A02.zip
Please help
Click to expand...
Click to collapse
For future references: Samsungs firmware files can be compressed with their LZ4 format and thus needs to be uncompressed again in the case of a boot.img.lz4 file so that you have boot.img file which magisk then can properly use. Otherwise you might get an error sating something like: unable repack boot image, when trying to patch the boot image with Magisk.

guys i have flash magisk patched image without custom recovery and via fastboot but now I am always boot to recovery.. Phone doesnt start at all.

In focus m535 magisk
OK bro I try it

Sorry

Hi, I try do to same thing on my S7 but with a Oreo 8.0 Android version.
Perhaps it's change something.
And each time I reboot after flash a boot.img patched or even patch TWRP, my phone don't boot and ask me to reset it (in French it write reinistialisation in an tactile screen).
If I reload with Odin a BL, AP ect... my phone restart and I didn't lose any data. But it is no root.
Could you help me please ?

[Galazy Z Fold2 F916U/U1_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 magislk 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 1 With Higher Firmware!!!!
Unless Using Bit Safe Firmware That Is Patched​
Downloads
SM-F916U/U1/W- Model
USERDATA_AIO_F916U_5G_FORCE_WIPE_10_10_21.tar.md5
This will force a wipe of data no mater what.
Full Odin 3.1.1 Bit1 Safe Firmware
F916USQS2EUH9_BIT1_SAFE.7z Thanks @markfm
This are odin files and will safely update all image files too bit 4 and keep bit 1 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_G78*_FORCE_WIPE_NO_BL is newer than the one in this zip use the newer one from above
Odin3_v3.14.1_3B_PatcheD.zip
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_F916U_**.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_F916U_**.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_F916U_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_F916U_NO_WIPE_NO_BL.tar.md5 in odin you can use AIO_Magisk_22_S20_Series.zip found in post 2
Features
No patches or mod zips are needed phone will already be rooted
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
Xylvion for testing s21
dark11b for testing s21

Hi, can i have the procedure for rooted Fold2 F916B for firmware update.

I'm super excited about this. Hope to see the info for bootloader unlock soon so I can try it. Thanks you're awesome!

Does this mean it can be updated on the latest firmware with root?

PLZ PLZ PLZ do this for the z Fold 3 u1 snapdragon please sir your work has been a God send since the s8+ for me. Thank you

The full odin bitsafe firmware link isn't working

Hey can you fix the link to the odin firmware please?

Nothing? Please fix the link to the odin firmware it doesn't work.

same here. Please reupload to the drive.

halx said:
same here. Please reupload to the drive.
Click to expand...
Click to collapse
What's going on here ? Why hasn't the OP responded to us?

Ok it's official....samsung murked the OP.

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.