Database Info

[GUIDE][SGH-I337] TWRP 3.0.2-0 Recovery & ROOT for AT&T Samsung Galaxy S4

Hi guys! Welcome back to another R&R guide and I've been tricking out the AT&T Galaxy S4 of one of my friends, Laguire, and decided to make this guide. So as usual here comes the requirements, followed by a detailed and noob-friendly guide and download links whatsoever. If you have any questions about the guide, you know what to do underneath. This guide is my riskiest guide EVER, so use it at your own risk. Don't blame me if it dies.
Requirements
A PC running Windows
Your AT&T S4
Samsung USB cable(not neccesary to be Samsung's, as long as it is the same type)
A stable Internet connection
How-To
1. Download files to the correct devices:
-Root ZIP -> S4
-Odin and Recovery -> PC\
2. Connect your device to the PC via USB cable
3. Boot into download mode (Power off > Power and Volume Down)
4. Run Odin
5. Uncheck the Auto Reboot box.
6. Click AP and locate the MD5 file you downloaded earlier
7. Click OK or Start(haven't been using Odin recently)
8. Wait for the first box above to say PASS
9. Power off your S4 and unplug the cable.
10.Boot into recovery mode(Power+Volume up)
11.Tap Install > Locate to the folder where you downloaded the Root zip earlier > Select
12.Swipe to flash
13.After finished reboot your S4 and download Root Checker to check root
Done! Your AT&T Samsung Galaxy S4 is now officially rooted!
Downloads
Odin(Don't download from any other sources): https://www.androidfilehost.com/?fid=24572369242686499
Root ZIP(by Chainfire): http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
TWRP 3.0.2-0 Recovery(RISK AVAILABLE): https://www.androidfilehost.com/?fid=24591023225176226
Special Thanks
Laguire Sien Tiamat
Brano Esmeer
Kohlner Freisch
Liam Francis
and Kamross Sorberg
In Memoriam: DAFFEN KURM-THIS ONE'S FOR YOU

this question seems pretty stupid, but its worth a shot. is this for devices without the loki exploit or no?

Sterben Pistole said:
this question seems pretty stupid, but its worth a shot. is this for devices without the loki exploit or no?
Click to expand...
Click to collapse
It is probably for SGH-i337 with exploitable old bootloaders (MDB, MDL). Odin and TWRP is a new one but superSU is 2 years old.

How It Will Works ? I Think Not Possible To Install TWRP ! .... Because AT&T i337 Locked Bootloader ... How I Will Install This ?

Sorry guys, I haven't noticed that Laguire's I337 is the old version. Sorry again for the convenience though.

I have a smart question >.< :/.
Does this work for the Galaxy S4 I337..OC4<-- kernel? lollipop*
Thank you!

Does this work with build ok2?
And why is this considered the riskiest???

This seems to be for phones with the MDB and MDL firmware as if you try to flash TWRP recovery on any other firmware, it won't install.

its not warking for me i get this problem : E: Failed to mount / system (Invalid argument) is there any Solution

bouba05f said:
its not warking for me i get this problem : E: Failed to mount / system (Invalid argument) is there any Solution
Click to expand...
Click to collapse
This guide is for the MDB and MDL bootloaders that can use the Loki doki patch. Once you've upgraded your firmware, there's no going back.

:good:
err on the side of kindness

I'm on oc4 rooted, I tried flashing twrp 3230 using flashify...
Big mistake tried to boot into recovery and it said I wasnt using official at&t software and had me stuck until I finally found if I set odin to autostart 1 after flashing the stock kernel it will boot up.... trying to find a recovery to use atm

I thought that the carriers locked the bootloader sometime before kitkat, I'm still using my AT&T sg4. I looped it installing superuser,had a difficult time getting fixed,found a group of F/W files at sammobile that had to be flashed 1 at a time all the way up to lollipop 5.0 then it took an OTA to 5.01. I need to Root so I can clean out all the useless apps at&t installs. I haven't been able to tether my tablet and forgot what files to use to root with.
Did you still have bootloader you use Recovery on,that would be great.

kmbbo said:
I'm on oc4 rooted, I tried flashing twrp 3230 using flashify...
Big mistake tried to boot into recovery and it said I wasnt using official at&t software and had me stuck until I finally found if I set odin to autostart 1 after flashing the stock kernel it will boot up.... trying to find a recovery to use atm
Click to expand...
Click to collapse
The only recovery you can use is the stock recovery given you are on OC4 which patched the bootloader exploit that allowed TWRP to be installed.
---------- Post added at 01:27 PM ---------- Previous post was at 01:21 PM ----------
vtails said:
I thought that the carriers locked the bootloader sometime before kitkat, I'm still using my AT&T sg4. I looped it installing superuser,had a difficult time getting fixed,found a group of F/W files at sammobile that had to be flashed 1 at a time all the way up to lollipop 5.0 then it took an OTA to 5.01. I need to Root so I can clean out all the useless apps at&t installs. I haven't been able to tether my tablet and forgot what files to use to root with.
Did you still have bootloader you use Recovery on,that would be great.
Click to expand...
Click to collapse
You are correct, AT&T locked the bootloader from day 1 of the S4 launch. However, there was an exploit for the MDL firmware that allowed TWRP to be installed. If you updated past MDL then there's no going back. MDL was Android 4.2.2 jellybean. The only thing you can do with later firmware is root and boot custom TW ROMs by using safe strap for kit kat and flash fire for lollipop.

Hi All,
I have a Canadian S4, SGH-I337M. It is essentially identical to the AT&T version except the Canadian one's bootloader is UNLOCKED. I have been running TWRP 3.1.1-0 to create nandroid backup for YEARS.
Unfortunately, all the sudden I'm getting this error message when I backup, "E: Another threaded action is already running -- not running 1 actions starting with 'nandroid'". It would try to do something and then quit after a minute without creating anything.
So where do I start to troubleshoot this issue? Again, it has always worked in the past! Thank you

luckysoul777 said:
Hi All,
I have a Canadian S4, SGH-I337M. It is essentially identical to the AT&T version except the Canadian one's bootloader is UNLOCKED. I have been running TWRP 3.1.1-0 to create nandroid backup for YEARS.
Unfortunately, all the sudden I'm getting this error message when I backup, "E: Another threaded action is already running -- not running 1 actions starting with 'nandroid'". It would try to do something and then quit after a minute without creating anything.
So where do I start to troubleshoot this issue? Again, it has always worked in the past! Thank you
Click to expand...
Click to collapse
Are you sure the Canadian version's boot loader is unlocked? When I go in download mode there is still this line "Write protect enabled" on...

so I do have an S4 on the MDL bootloader, and i've followed all the steps but I can't flash TWRP.
pretty much every link is dead for the i337 root now except for this which doesn't appear to work. if someone is able to provide the loki, motochopper, and other necessary files for this device so i can get this paperweight loki'd, that would be sweet.

How I bricked it... share your experiences!

So it seems that we are having the first (hope soft...) bricks here... :crying:
I think it could be interesting for ALL sharing HOW you brick it with details, so others can avoid to do same errors.
Eventually would be even more interesting how you have recovered from your brick status (if you...:fingers-crossed with detailed guide...
I think that having all in a single thread could be very useful, so... share your (bad) experiences...

Flashed the rogers firmware on my retapac moto z then updated to us version nougat. Root didnt work so flashed back to rogers mm. Not booting anymore. Not flashing anything nor side loading since cant downgrade bl and gpt. Nougat sideload refuses because it sees device as already on new firmware.
So edited the flashfile.xml on rogers mm firmware. Removed the bootloader and gpt flash and reflashed partial mm system. Sideloaded nougat again and everything went perfect.

i23u8 said:
Flashed the rogers firmware on my retapac moto z then updated to us version nougat. Root didnt work so flashed back to rogers mm. Not booting anymore. Not flashing anything nor side loading since cant downgrade bl and gpt. Nougat sideload refuses because it sees device as already on new firmware.
So edited the flashfile.xml on rogers mm firmware. Removed the bootloader and gpt flash and reflashed partial mm system. Sideloaded nougat again and everything went perfect.
Click to expand...
Click to collapse
Can you help me? I tried installing twrp and when I finally got it, it started looping on the unlocked bootloader screen, I already tried everything, I installed custom roms by twrp and even the stock rom by commands I saw in another topic (http: // forum. Xda-developers.com/moto-z/help/help-phone-bricked-t3499573) but it seems that nothing happens and I still stay on the screen or bootloader or on that warns that the phone has been unlocked and can not be trusted .
I had upped some images to show my problem
http://imgur.com/Zm1Mja5
http://imgur.com/bgoGwQQ
Sorry for my bad english, I really need help

rogerxcamargo said:
Can you help me? I tried installing twrp and when I finally got it, it started looping on the unlocked bootloader screen, I already tried everything, I installed custom roms by twrp and even the stock rom by commands I saw in another topic (http: // forum. Xda-developers.com/moto-z/help/help-phone-bricked-t3499573) but it seems that nothing happens and I still stay on the screen or bootloader or on that warns that the phone has been unlocked and can not be trusted .
I had upped some images to show my problem
http://imgur.com/Zm1Mja5
http://imgur.com/bgoGwQQ
Sorry for my bad english, I really need help
Click to expand...
Click to collapse
The warning message is normal. So what happens when you go to Recovery mode. When you installed twrp, you executed both fastboot flash recovery twrp.img and fastboot boot twrp.img? So it boots directly to twrp.
So if you're upgrading to nougat, the sequence should be:
Go to bootloader screen.
Flash rogers MM firmware thru rsd lite.
Go to bootloader screen again and select recovery.
Choose adb sideload.
Type the command to sideload the nougat firmware.
Optionals are install twrp, install the odexed custom nougat firmware from the other thread, and root.

i have no more access to fastboot or recovery after flashing retmx nougat on my device. my pc recognizes the qualcomm device and i've already installed drivers for it. but i need the files to flash the stock rom including bootloader. (please also have a look to my post in the other thread http://forum.xda-developers.com/showpost.php?p=70014076&postcount=21)

M!tch said:
i have no more access to fastboot or recovery after flashing retmx nougat on my device....
Click to expand...
Click to collapse
Could you explain better what steps have you done exactly (to brick...)?

i came from latest marshmallow with unlocked bootloader and rooted. because the ota didn't work i flashed stock marshmallow reteu via fastboot and loaded the ota again via the update menu in settings. it failed again. therefore i flashed stock nougat retmx via fastboot. the result was a black screen and only an unknown device named "qusb_bulk" at the windows device manager. meanwhile i've installed qualcomm drivers and qfil but still need the right files for my xt1650.

M!tch said:
i came from latest marshmallow with unlocked bootloader and rooted. because the ota didn't work i flashed stock marshmallow reteu via fastboot and loaded the ota again via the update menu in settings. it failed again. therefore i flashed stock nougat retmx via fastboot. the result was a black screen and only an unknown device named "qusb_bulk" at the windows device manager. meanwhile i've installed qualcomm drivers and qfil but still need the right files for my xt1650.
Click to expand...
Click to collapse
Is rsd lite still seeing your device? There are full firmware files somewhere here in the forums. Or do you only need bootloader and boot img files?

rsd lite is just using fastboot. i need the files for qfil. (rawprogram0.xml and patch0.xml)

I came fresh out the box xt1650-03 and was trying to get twrp (which worked) and then root which failed. So installed on of these ROMS that had root and maybe even the 7.0. Now I just get the your devices is unlocked screen and nothing else. I just want to get back to the way it came but cannot get RSD to see my phone. Any help or ideas?

i23u8 said:
The warning message is normal. So what happens when you go to Recovery mode. When you installed twrp, you executed both fastboot flash recovery twrp.img and fastboot boot twrp.img? So it boots directly to twrp.
So if you're upgrading to nougat, the sequence should be:
Go to bootloader screen.
Flash rogers MM firmware thru rsd lite.
Go to bootloader screen again and select recovery.
Choose adb sideload.
Type the command to sideload the nougat firmware.
Optionals are install twrp, install the odexed custom nougat firmware from the other thread, and root.
Click to expand...
Click to collapse
I managed to get into recovery mode, if I remember correctly I had upgraded my nougat before this whole problem.
Unfortunately I do not know why but I can not get my phone to be identified by rsd lite, is there any tutorial by xda?
I tried installing odexed custom nougar firmware and root by twrp but it is restarting in looping in the screen of "your device can not be trusted"

i23u8 said:
Is rsd lite still seeing your device? There are full firmware files somewhere here in the forums. Or do you only need bootloader and boot img files?
Click to expand...
Click to collapse
I can get RSD to see it now so I need a full firmware but cannot find it my search skill must be week

OK i can see it in fastboot but cannot do anything else
this is what i see

ryanwv24 said:
OK i can see it in fastboot but cannot do anything else
this is what i see
Click to expand...
Click to collapse
Your BL (90.xx) is still in MM, Nougat is 91.xx. You can still rsd the MM firmware for your region.
---------- Post added at 07:56 PM ---------- Previous post was at 07:54 PM ----------
rogerxcamargo said:
I managed to get into recovery mode, if I remember correctly I had upgraded my nougat before this whole problem.
Unfortunately I do not know why but I can not get my phone to be identified by rsd lite, is there any tutorial by xda?
I tried installing odexed custom nougar firmware and root by twrp but it is restarting in looping in the screen of "your device can not be trusted"
Click to expand...
Click to collapse
Can you look at BL version? 90.xx and you are still on MM and you can rsd to stock MM. 91.xx and you will have to sideload the nougat firmware.

i23u8 said:
Your BL (90.xx) is still in MM, Nougat is 91.xx. You can still rsd the MM firmware for your region.
---------- Post added at 07:56 PM ---------- Previous post was at 07:54 PM ----------
Can you look at BL version? 90.xx and you are still on MM and you can rsd to stock MM. 91.xx and you will have to sideload the nougat firmware.
Click to expand...
Click to collapse
I do not know what I did but it is working now.
build MPL24.246-45
Baseband M8996_1227.36.01.115.01R SRS
kernel 3.18.24-perf-g0c28d32
[email protected]#1
Why the lack of updates on this phone?
Wed Aug 31

As Peter Griffin says - if they're not giving it to you, you probably don't need it. Remember these large groups of men know what's best for you.
Seriously though, there might be tons of unique adoptions to the phone that need time to port?
CM14.1 was out a week ago but Moto Mods aren't working and that's 50% of the phone not working.

i23u8 said:
Your BL (90.xx) is still in MM, Nougat is 91.xx. You can still rsd the MM firmware for your region.
---------- Post added at 07:56 PM ---------- Previous post was at 07:54 PM ----------
Can you look at BL version? 90.xx and you are still on MM and you can rsd to stock MM. 91.xx and you will have to sideload the nougat firmware.
Click to expand...
Click to collapse
BL on bootloader is showing 91.05, sorry but how i sideload nougat firmware?

rogerxcamargo said:
BL on bootloader is showing 91.05, sorry but how i sideload nougat firmware?
Click to expand...
Click to collapse
You should be on the roger firmware, goto bootloader and select recovery mode. Select adb sideload from the recovery menu.

i23u8 said:
You should be on the roger firmware, goto bootloader and select recovery mode. Select adb sideload from the recovery menu.
Click to expand...
Click to collapse
When i try to use adb sideload appears a error "loading Blur_Version.24.21.46.griffin.retail.en.US.zip" and then "* cannot read Blur_Version.24.21.46.griffin.retail.en.US.zip"
when i try to update from SD card appears a error "Internal and external memory cannot be mounted"

rogerxcamargo said:
When i try to use adb sideload appears a error "loading Blur_Version.24.21.46.griffin.retail.en.US.zip" and then "* cannot read Blur_Version.24.21.46.griffin.retail.en.US.zip"
when i try to update from SD card appears a error "Internal and external memory cannot be mounted"
Click to expand...
Click to collapse
Can you try and open the zip on your pc and extract all contents in a directory? Just to make sure it isnt corrupt? Also, there are 2 versions of the file, one international and the other US, I used the international variant file.

SM J500H sw rev check fail fused 2 binary 1

hello can you please help me I really hate android 6.1
I flashed my j5 sm j500h with Odin installed android marshmallow downloaded it from SamMobiles
when I tried to flash back android lollipop 5.1 it gave me this error in download mode sw rev check fail fused 2 binary 1
Odin failed to flash it
please help me ASAP battery draining real fast on android 6.1

J500h same this problem after rooted my devices
:after rooted my devices odin fail auth devices screen show this message fused 2 > binary 1 please solve this problem

Wajikhan said:
:after rooted my devices odin fail auth devices screen show this message fused 2 > binary 1 please solve this problem
Click to expand...
Click to collapse
You are trying to flash something that has a lower binary than the firmware that is currently installed on your device. In other words, you cannot downgrade your firmware via Odin, the bootloader will not allow it. Find the build number for the stock firmware that is on your device, look at the 5th digit from the right end of your firmware number, then, compare that to the 5th digit from the end of the build number that you are trying to flash. If the 5th digit from the right end of the firmware that is currently installed on the device has a 2 or higher in that position, you can only flash a firmware that is binary 2 or higher, you can't go back to a firmware that is binary 1. If you have a binary 3 firmware, you can't go back to binary 2 or binary 1. If you have a binary 4 firmware, you can't go back to binary 3 or binary 2 or binary 1.
You can only flash the build number that you currently have on the device or you can flash a newer build number, you cannot flash an older build number. Samsung bootloader will not allow downgrading the binary.
What method did you use to root your device? Did you use TWRP or Magisk to root your device? I'm willing to be that you did not use TWRP or Magisk because you probably have a locked bootloader, which is why the binary is preventing Odin flashing.
Sent from my SM-S767VL using Tapatalk
---------- Post added at 11:53 AM ---------- Previous post was at 11:47 AM ----------
armando1990 said:
hello can you please help me I really hate android 6.1
I flashed my j5 sm j500h with Odin installed android marshmallow downloaded it from SamMobiles
when I tried to flash back android lollipop 5.1 it gave me this error in download mode sw rev check fail fused 2 binary 1
Odin failed to flash it
please help me ASAP battery draining real fast on android 6.1
Click to expand...
Click to collapse
Simple, you can't downgrade Samsung firmware unless the downgraded firmware has the same binary as your currently installed firmware or a higher binary, you can't flash a firmware that has a lower binary than your current firmware. In other words, you seem to have a binary 2 firmware currently installed and you're trying to flash a binary 1 firmware, the binary 2 bootloader will not allow the binary 1 firmware to flash. You can flash a binary 2 or higher firmware but not a binary 1.
Sent from my SM-S767VL using Tapatalk

Won't boot into anything but DL mode, error SW rev check fail (bootloader) device: 5

EDIT: This problem has been resolved thanks to good advice in this thread!
I'm not sure what I've managed to do, but here are the symptoms:
I installed a custom rom and it was working, had TWRP and magisk installed, but couldn't get the s7 exynos to recognize that magisk was installed. I attempted to restore to a stock rom. At this point, it will not boot past the samsung logo. It will also not boot into recovery. I can boot into download mode. The DL mode screen reports the error SW rev check fail (bootloader) device: 5 binary: 2
No matter stock ROM what I attempt to flash via Odin, just after the process log gets to sboot.bin, the next line is FAIL! then Complete (Write) operation failed. I am attempting to flash the latest version of 8.0 from sammobile for s7 exynos (I selected BTU).

kettir said:
I'm not sure what I've managed to do, but here are the symptoms:
I installed a custom rom and it was working, had TWRP and magisk installed, but couldn't get the s7 exynos to recognize that magisk was installed. I attempted to restore to a stock rom. At this point, it will not boot past the samsung logo. It will also not boot into recovery. I can boot into download mode. The DL mode screen reports the error SW rev check fail (bootloader) device: 5 binary: 2
No matter stock ROM what I attempt to flash via Odin, just after the process log gets to sboot.bin, the next line is FAIL! then Complete (Write) operation failed. I am attempting to flash the latest version of 8.0 from sammobile for s7 exynos (I selected BTU).
Click to expand...
Click to collapse
Device 5 means boot loader version 5, binary 2 means bootloder your trying to flash is older, you cannot flash an older boot loader than version 5. This means the firmware you are trying to flash is not the latest.
Sammobile has BTU version 5, search for it and download it, follow the guide how to flash.

cooltt said:
Device 5 means boot loader version 5, binary 2 means bootloder your trying to flash is older, you cannot flash an older boot loader than version 5. This means the firmware you are trying to flash is not the latest.
Sammobile has BTU version 5, search for it and download it, follow the guide how to flash.
Click to expand...
Click to collapse
Thank you, this is invaluable advice and just what I was hoping for.
When the phone arrived I could briefly see that it was a Saudi Arabia firmware. Looking at saudi STC SFU the date is 7/1/19, that might explain this. I flashed Alexndr 8.0 over that. It was during the time I tried to get magisk to stick that I bricked the phone.
I did download and attempt (with fail) to flash G930FXXS4ESC1_G930FOXA4ERKF_BTU dated 5/12/19 on the sammobile page. So I may try United Kingdom dated 7/11/19 and see if that will flash. I can't tell which version of BTU might have a boot loader version 5 among those listed. Does this seem a reasonable attempt to you?
EDIT: I did download and flash, and it's starting to boot....huzzah! I'm now filling out the startup information. Thank you!!

kettir said:
Thank you, this is invaluable advice and just what I was hoping for.
When the phone arrived I could briefly see that it was a Saudi Arabia firmware. Looking at saudi STC SFU the date is 7/1/19, that might explain this. I flashed Alexndr 8.0 over that. It was during the time I tried to get magisk to stick that I bricked the phone.
I did download and attempt (with fail) to flash G930FXXS4ESC1_G930FOXA4ERKF_BTU dated 5/12/19 on the sammobile page. So I may try United Kingdom dated 7/11/19 and see if that will flash. I can't tell which version of BTU might have a boot loader version 5 among those listed. Does this seem a reasonable attempt to you?
EDIT: I did download and flash, and it's starting to boot....huzzah! I'm now filling out the startup information. Thank you!!
Click to expand...
Click to collapse
Great.
The boot loader version is shown in the firmware, G930FXXS4ESC1 is boot loader version 4, S4= V4.
S5 = V5 etc.
For info, version 5 (S5) was the final BTU firmware release for the S7 so no more firmware updates after that.

cooltt said:
Great.
The boot loader version is shown in the firmware, G930FXXS4ESC1 is boot loader version 4, S4= V4.
S5 = V5 etc.
For info, version 5 (S5) was the final BTU firmware release for the S7 so no more firmware updates after that.
Click to expand...
Click to collapse
Thanks for the clue, it is much appreciated!

Please help I wiped my note 9 from TWRP and Odin is stuck at recovery.img

Hi guy I am panicking here I accidentally wiped everything from my samsung note 9 and there is no OS on the phone. I tried to flash older firmware but Odin is stuck at recovery and the phone shows a red line saying "SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 6, BINARY:5
PLEASE SOMEONE HELP ME

Skulper said:
Hi guy I am panicking here I accidentally wiped everything from my samsung note 9 and there is no OS on the phone. I tried to flash older firmware but Odin is stuck at recovery and the phone shows a red line saying "SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 6, BINARY:5
PLEASE SOMEONE HELP ME
Click to expand...
Click to collapse
The firmware that you flashed has a lower binary than the firmware that you had on the device before you modified it. You need to flash a firmware that has the same binary as what you had before you modified the device, or you need to flash a firmware that has a higher/newer binary than what you had.
See where the error says that your device is binary 6 but the firmware that you flashed has binary 5? You need a binary 6 or higher firmware. You can identify the binary by looking at the 5th character from the right end of the firmware build number.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
The firmware that you flashed has a lower binary than the firmware that you had on the device before you modified it. You need to flash a firmware that has the same binary as what you had before you modified the device, or you need to flash a firmware that has a higher/newer binary than what you had.
See where the error says that your device is binary 6 but the firmware that you flashed has binary 5? You need a binary 6 or higher firmware. You can identify the binary by looking at the 5th character from the right end of the firmware build number.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
i think i might be in love with you,(not in a weird way) this reply here saved my ass,i was stuck on odin wondering what was wrong & just this simple explanation helped me a lot

brokboi said:
i think i might be in love with you,(not in a weird way) this reply here saved my ass,i was stuck on odin wondering what was wrong & just this simple explanation helped me a lot
Click to expand...
Click to collapse
Be aware, once you flash a firmware that upgrades your device binary to a higher binary, you can not go back to the lower binary. A lot of times, flashing a firmware that upgrades the binary also upgrades the bootloader to a more secure bootloader that can't be unlocked, this kills virtually any chance of rooting the device or flashing TWRP custom recovery and/or custom ROMs. Then you're stuck with a device that you can't modify the way you want.

Droidriven said:
Be aware, once you flash a firmware that upgrades your device binary to a higher binary, you can not go back to the lower binary. A lot of times, flashing a firmware that upgrades the binary also upgrades the bootloader to a more secure bootloader that can't be unlocked, this kills virtually any chance of rooting the device or flashing TWRP custom recovery and/or custom ROMs. Then you're stuck with a device that you can't modify the way you want.
Click to expand...
Click to collapse
Ya i had that in mind so i flashed accordingly & i have unlocked bootloader with twrp not that i needed it though, cuz i just wanted to use samsung dex

brokboi said:
Ya i had that in mind so i flashed accordingly & i have unlocked bootloader with twrp not that i needed it though, cuz i just wanted to use samsung dex
Click to expand...
Click to collapse
Have you used TWRP to create a android backup of your stock ROM after you got it fixed? If not, do so, then store a copy of the backup on a PC or USB flashdrive, external sdcard, etc.. That backup can be used to restore your device, if needed.