Related
This guide is similar to what is described in this thread, so credit for him on the guide.
If you've tried countless numbers of times to make secure folder work, but keep on getting "Failed to create Knox mode", this guide is for you.
This guide MAY work for others who wish to use different ROM, similar processs, different rom. That is all, please feel free to try and let me know
What I've found out (Regardless if it is true or not):
There are people saying security patch dated June 2017 from Samsung patched the Secure folder stuff
If your secure folder never worked before (after rooting your phone and flash new ROM), or at some point, secure folder stopped working, you need to start from official FW all over again. Which is what this guide is for.
Notes:
Not responsible for any damage or bricked devices.
If the phone is bricked, you can always start from flashing official FW via Odin.
Requirements:
Make a backup of everything you need. In case things go wrong and bricked your phone.
Any Nougat official firmware released BEFORE June 2017
TWRP, Odin and Samsung Phone drivers from here
SuperSU by Chainfire from here
The very first version of Secure Folder (1.0.01-020) from here
Batman ROM, other related fix and join the Telegram group of Batman listed inside here
Upon joining the telegram group, use the search function to search for Secure Folder fix. The file is less than 700kb.
A micro SD card.
Steps listed below are what I did and worked for me, and I hope they work for you too.
Put any flashable zips file to your SD card. Phone's internal storage will be wiped several times in the processes below.
Boot phone into download mode and flash official FW via Odin, put the files in the respective slot. AP to AP, BL to BL, CP to CP, CSC to CSC. I disregard the HOME_CSC file.
Reboot and setup. (Doesn't matter account setup etc, just skip everything and get to home screen)
Go to Settings > Enable developer options > Enable OEM unlocking inside developer options.
Power off phone, boot into download mode, flash twrp .tar file via Odin. (AP slot, untick Auto-Reboot)
After Odin shows pass/success. Unplug USB, hold [Volume Down] + [Home] + [Power] to exit download mode, when the screen goes blank, with those 3 buttons held down, immediately switch from holding Vol down to Vol up, to boot into Recovery mode, which in this case will boot into TWRP.
Any time you see a warning in TWRP about swipe to allow modification, swipe it.
Go to wipe > format data. Type yes to wipe data
Flash superSU, flash Super Stock kernel and reboot your phone.
(Not sure this step here is needed, but I did it anyway) Download My Knox, just open and exit after it is installed on your phone.
Install the Secure Folder apk downloaded. Clear Secure Folder's app data. And run it.
At this point, Secure Folder should work without any problem. If Secure Folder failed to install/set up. Please do let me know in the comments.
Boot into TWRP, flash Batman ROM.
In Aroma: Clean flash (wipe everything except SD card), tick Knox, latest modem and bootloader from ROM, and also both modded settings / UI.
Upon exiting Aroma, the phone will auto reboot itself because you ticked "update to latest bootloader" in Aroma, but not to worry. Just let it boot.
It'll take awhile to boot. After booting up, set up the phone nicely. Check for Secure Folder enabled in the setup process. It is enabled by default.
Clear Secure Folder's app data/cache.
Reboot to TWRP.
Flash the Secure Folder fix twice (I flashed it twice, don't ask me why), and other fix/mods (sticker fix etc) you want.
Reboot to system
Tap on Secure Folder, it should work now.
Do let me know in the comments how it worked out for you guys and report any missing links that I may not have listed here.
Secure folder fix will not be listed, you can find it in the telegram group.
I've not tested with any other kernel other than the Batstock that comes with Batman ROM.
Credits:
Respective owners of the files
People in the telegram for giving out suggestion and advice
The helpful guy in telegram group, Jonathan, for his time and patience for helping me out.
I got the same messagge in the step 11 ... Error .. i made all the past steps.
julloas said:
I got the same messagge in the step 11 ... Error .. i made all the past steps.
Click to expand...
Click to collapse
After you root and flash with superstock kernel.
Download the app, phone info, it'll show knox 0x0 instead of 0x1, with this, it tricked secure folder thinking you're not rooted / tripped knox
Nice guide. Maybe this is the secure folder fix file?
kykint said:
Nice guide. Maybe this is the secure folder fix file?
Click to expand...
Click to collapse
I've been looking for this fix zip file everywhere! I Just flashed it on my batman rom 1.1.1 and i can confirm that the secure folder now works like a charm.
Needles to say i ticked the knox option in the initial setup when i installed the rom a few days ago. Cheers mate.
Creedo4Life said:
I've been looking for this fix zip file everywhere! Just flashed it and on my batman rom 1.1.1 rom and the secure folder now works like a charm.
Needles to say i ticked the knox option in the initial setup when i installed the rom a few days ago. Cheers mate.
Click to expand...
Click to collapse
Glad it still works Maybe I should update the fix sometime later to automatically install a working version of secure folder as well..
Would this ever work on the s8 plus
problem with this guide
i have error in step 11, error knox can't create space help
Jeyssondjx said:
i have error in step 11, error knox can't create space help
Click to expand...
Click to collapse
did you follow exactly all the previous steps with the requirements?
Superman rom
Does this fix work for superman rom too? Secure folder is not working in latest superman rom
not working.. pls help
Same problem in sac23 rom.
xIceCream said:
This guide is similar to what is described in this thread, so credit for him on the guide.
If you've tried countless numbers of times to make secure folder work, but keep on getting "Failed to create Knox mode", this guide is for you.
This guide MAY work for others who wish to use different ROM, similar processs, different rom. That is all, please feel free to try and let me know
What I've found out (Regardless if it is true or not):
There are people saying security patch dated June 2017 from Samsung patched the Secure folder stuff
If your secure folder never worked before (after rooting your phone and flash new ROM), or at some point, secure folder stopped working, you need to start from official FW all over again. Which is what this guide is for.
Notes:
Not responsible for any damage or bricked devices.
If the phone is bricked, you can always start from flashing official FW via Odin.
Requirements:
Make a backup of everything you need. In case things go wrong and bricked your phone.
Any Nougat official firmware released BEFORE June 2017
TWRP, Odin and Samsung Phone drivers from here
SuperSU by Chainfire from here
The very first version of Secure Folder (1.0.01-020) from here
Batman ROM, other related fix and join the Telegram group of Batman listed inside here
Upon joining the telegram group, use the search function to search for Secure Folder fix. The file is less than 700kb.
A micro SD card.
Steps listed below are what I did and worked for me, and I hope they work for you too.
Put any flashable zips file to your SD card. Phone's internal storage will be wiped several times in the processes below.
Boot phone into download mode and flash official FW via Odin, put the files in the respective slot. AP to AP, BL to BL, CP to CP, CSC to CSC. I disregard the HOME_CSC file.
Reboot and setup. (Doesn't matter account setup etc, just skip everything and get to home screen)
Go to Settings > Enable developer options > Enable OEM unlocking inside developer options.
Power off phone, boot into download mode, flash twrp .tar file via Odin. (AP slot, untick Auto-Reboot)
After Odin shows pass/success. Unplug USB, hold [Volume Down] + [Home] + [Power] to exit download mode, when the screen goes blank, with those 3 buttons held down, immediately switch from holding Vol down to Vol up, to boot into Recovery mode, which in this case will boot into TWRP.
Any time you see a warning in TWRP about swipe to allow modification, swipe it.
Go to wipe > format data. Type yes to wipe data
Flash superSU, flash Super Stock kernel and reboot your phone.
(Not sure this step here is needed, but I did it anyway) Download My Knox, just open and exit after it is installed on your phone.
Install the Secure Folder apk downloaded. Clear Secure Folder's app data. And run it.
At this point, Secure Folder should work without any problem. If Secure Folder failed to install/set up. Please do let me know in the comments.
Boot into TWRP, flash Batman ROM.
In Aroma: Clean flash (wipe everything except SD card), tick Knox, latest modem and bootloader from ROM, and also both modded settings / UI.
Upon exiting Aroma, the phone will auto reboot itself because you ticked "update to latest bootloader" in Aroma, but not to worry. Just let it boot.
It'll take awhile to boot. After booting up, set up the phone nicely. Check for Secure Folder enabled in the setup process. It is enabled by default.
Clear Secure Folder's app data/cache.
Reboot to TWRP.
Flash the Secure Folder fix twice (I flashed it twice, don't ask me why), and other fix/mods (sticker fix etc) you want.
Reboot to system
Tap on Secure Folder, it should work now.
Do let me know in the comments how it worked out for you guys and report any missing links that I may not have listed here.
Secure folder fix will not be listed, you can find it in the telegram group.
I've not tested with any other kernel other than the Batstock that comes with Batman ROM.
Credits:
Respective owners of the files
People in the telegram for giving out suggestion and advice
The helpful guy in telegram group, Jonathan, for his time and patience for helping me out.
Click to expand...
Click to collapse
My knox is tripped what i do
Sent from my SM-G935F using Tapatalk
kykint said:
Nice guide. Maybe this is the secure folder fix file?
Click to expand...
Click to collapse
Does it work with any ROM ?
---------- Post added at 07:39 PM ---------- Previous post was at 07:21 PM ----------
Creedo4Life said:
I've been looking for this fix zip file everywhere! I Just flashed it on my batman rom 1.1.1 and i can confirm that the secure folder now works like a charm.
Needles to say i ticked the knox option in the initial setup when i installed the rom a few days ago. Cheers mate.
Click to expand...
Click to collapse
still works? You tried it in stock or custom kernel?
Does it work with SuperMan rom?
Still working? May work it on s7 edge with Batman rom?
Enviado desde mi SM-G935F mediante Tapatalk
Wondering if it still works with Batman ROM 1.5 as well, and whether we can update Secure Folder after that.
I found a fix not going to share it here because samsung will patch it anyway. Never will buy Samsung again. Glad my s7 edge broke.
amakuramio said:
I found a fix not going to share it here because samsung will patch it anyway. Never will buy Samsung again. Glad my s7 edge broke.
Click to expand...
Click to collapse
can share with me the secure folder fix in private message?
Sent from my [device_name] using XDA-Developers Legacy app
There is no fix - If that's the case everyone will know about this!! He's talking out of this back side!!!!
I have a canadian S7 (8.0.0/R16NW/G930W8VLS5CSA1)
It's a company owned device that we are trying to re-purpose from a terminated employee. The device has been wiped but we appear to be stuck verifying account. I've gone over a number of threads but i can't seem to find a concise set of instructions.
Any help would be appreciated.
geopgin said:
I have a canadian S7 (8.0.0/R16NW/G930W8VLS5CSA1)
It's a company owned device that we are trying to re-purpose from a terminated employee. The device has been wiped but we appear to be stuck verifying account. I've gone over a number of threads but i can't seem to find a concise set of instructions.
Any help would be appreciated.
Click to expand...
Click to collapse
Can't you sign in with the email and password of the Google account of the terminated employee?
cooltt said:
Can't you sign in with the email and password of the Google account of the terminated employee?
Click to expand...
Click to collapse
You mean the x employees personal gmail account. No thats definitely not possible
geopgin said:
You mean the x employees personal gmail account. No thats definitely not possible
Click to expand...
Click to collapse
OK well for future reference always,....ALWAYS remove the google account from the phone before doing any kind of factory reset when you don't know the credentials.
Method 1 take it to a Samsung service shop with proof of purchase / ownership and they will reset the device for you, (might want to do this before messing around with it).
Method 2 is to get TWRP onto the phone to wipe "user data" then reboot , once you get TWRP on your home and dry. Can flash with Odin and depending on how up to date the device firmware is will depend if it will work or not.
Method 3 is to use the use the OTG cable (which came with the phone) to plug in a USB drive with all manner of frp disabling .apk's on. Lots of guides on line for this.
Method 4. I know some of the videos on youtube look confusing but depending on how old your device firmware is some of them still work. Any guides from late 2018 onwards should be tried, don't bother with any guides older than September 2018
Method 5. Is the nuclear option of "nand erase all" in Odin only use this if you are desperate as it's likely to corrupt the efs partition
It's very difficult to give specific advice without knowing the exact state of the phone, firmware update, security patch etc.
FRP lock is an absolute bast**d to resolve. I hope this helps.
Update
Apparently this method works on an S7
cooltt said:
OK well for future reference always,....ALWAYS remove the google account from the phone before doing any kind of factory reset when you don't know the credentials.
Method 1 take it to a Samsung service shop with proof of purchase / ownership and they will reset the device for you, (might want to do this before messing around with it).
Method 2 is to get TWRP onto the phone to wipe "user data" then reboot , once you get TWRP on your home and dry. Can flash with Odin and depending on how up to date the device firmware is will depend if it will work or not.
Method 3 is to use the use the OTG cable (which came with the phone) to plug in a USB drive with all manner of frp disabling .apk's on. Lots of guides on line for this.
Method 4. I know some of the videos on youtube look confusing but depending on how old your device firmware is some of them still work. Any guides from late 2018 onwards should be tried, don't bother with any guides older than September 2018
Method 5. Is the nuclear option of "nand erase all" in Odin only use this if you are desperate as it's likely to corrupt the efs partition
It's very difficult to give specific advice without knowing the exact state of the phone, firmware update, security patch etc.
FRP lock is an absolute bast**d to resolve. I hope this helps.
Update
Apparently this method works on an S7
Click to expand...
Click to collapse
How are you suppose to get into the device and remove the google account when you don't have the device password? Most if not all of those options require USB debugging be enabled no? Which i can't / wasn't able to do without pwd. We don't have samsung service shops around here.
Is there no way to load from usb drive
geopgin said:
How are you suppose to get into the device and remove the google account when you don't have the device password? Most if not all of those options require USB debugging be enabled no? Which i can't / wasn't able to do without pwd. We don't have samsung service shops around here.
Is there no way to load from usb drive
Click to expand...
Click to collapse
None of the methods i've listed require you to have password access to the device. I'm assuming from what you've written in your first post, you can turn the device on but are stuck at the Google verification screen? AKA, FRP lock
No you do not necessarily need USB debugging turned on
The OTG cable IS connected to a USB drive if you use that method
I mean this in the nicest possible way but do you have a basic understanding of the steps required to modify this phone?
cooltt said:
None of the methods i've listed require you to have password access to the device. I'm assuming from what you've written in your first post, you can turn the device on but are stuck at the Google verification screen? AKA, FRP lock
No you do not necessarily need USB debugging turned on
The OTG cable IS connected to a USB drive if you use that method
I mean this in the nicest possible way but do you have a basic understanding of the steps required to modify this phone?
Click to expand...
Click to collapse
Thanks, You have instructions for usb otg chance?
geopgin said:
Thanks, You have instructions for usb otg chance?
Click to expand...
Click to collapse
Read through this
cooltt said:
Read through this
Click to expand...
Click to collapse
i don't believe any of those methods work on s7 on android 8. No file manager pop, no google assist on keyboard, sidesync doesn't pop either. I believe the latest that tutorial works on reliably is 6.1 i may be wrong however.
geopgin said:
i don't believe any of those methods work on s7 on android 8. No file manager pop, no google assist on keyboard, sidesync doesn't pop either. I believe the latest that tutorial works on reliably is 6.1 i may be wrong however.
Click to expand...
Click to collapse
also just tried realterm method which is the most recent and it also doesn't work.
can i downgrade the rom without root? if so how, is there a otg method (without twrp)?
managed to bypass frp on my verizon s7 G930VVRU8CRJ3. I will try and list the steps so you can test it for yourself
From the start screen hold vol up and vol down simultaneously to start talkback
Draw a L to open global context menu.
Select talkback settings
Long press vol up and down together to turn off talkback
Select text to speech setting
Select the gear next to preferred engine
Select install voice data
Select the download arrow next to any language
Select the grey oval that says tools under the title of whatever language you chose
(You may have to update the galaxy store)
Select the magnifying glass and search for "internet"
Download samsung internet browser then open by pressing the triangle that appears in the same spot the download button was
Type frptools.com
Click on the second link that says All Frp Bypass Apk Download - frptools.com
Download FRPTools_8.1.apk install and open
Click on open google login. It will say you need google account manager then automatically down load it. Install that then it will take you back in to the frptools apk.
Click open google login again
Click on the three dots in the top right and choose browser sign in
Input your google account and password
Download apex launcher from frp tools apk and install.
Pull down notification shade and select settings gear
Select general management setting
Select reset
Select factory data reset. You should see your email account on this screen
Select reset.
Once it reboots you should be able breeze through setup wizard with your credentials.
Good luck! Please let me know if this works for you
awanderingponderer said:
managed to bypass frp on my verizon s7 G930VVRU8CRJ3. I will try and list the steps so you can test it for yourself
From the start screen hold vol up and vol down simultaneously to start talkback
Draw a L to open global context menu.
Select talkback settings
Long press vol up and down together to turn off talkback
Select text to speech setting
Select the gear next to preferred engine
Select install voice data
Select the download arrow next to any language
Select the grey oval that says tools under the title of whatever language you chose
(You may have to update the galaxy store)
Select the magnifying glass and search for "internet"
Download samsung internet browser then open by pressing the triangle that appears in the same spot the download button was
Type frptools.com
Click on the second link that says All Frp Bypass Apk Download - frptools.com
Download FRPTools_8.1.apk install and open
Click on open google login. It will say you need google account manager then automatically down load it. Install that then it will take you back in to the frptools apk.
Click open google login again
Click on the three dots in the top right and choose browser sign in
Input your google account and password
Download apex launcher from frp tools apk and install.
Pull down notification shade and select settings gear
Select general management setting
Select reset
Select factory data reset. You should see your email account on this screen
Select reset.
Once it reboots you should be able breeze through setup wizard with your credentials.
Good luck! Please let me know if this works for you
Click to expand...
Click to collapse
Thanks for response,
When i holde volume up and down it doesn't do anything from start screen. On my device voice assistance is turned on by holding 2 fingers on the screen until it beeps. Then a tutorial comes up. swiping L shape does nothing.
Simple go to ebay search for samsung galaxy Google lock removal service and have one of them remove it for you. I have done this many times and it dose not cost that much.
I have been searching the internet for days now and I haven't found a single way to root samsung SM-J337P Android 9 I hope to have some feedback on this site
Ive been looking to do the same for the last couple of months now & haven't had a bit of luck finding anythng or having any tried methods turn out successful
Root is fairly simple using Magisk pre patched method.
As for TWRP. Seems no one has bothered yet.
If there is a warrant for it I'll look into it, but I don't have as much enthusiasm nowadays as there seems to be a hit and run nature now on XDA.
I can't even get any feedback half the time.
ashyx said:
Root is fairly simple using Magisk pre patched method.
As for TWRP. Seems no one has bothered yet.
If there is a warrant for it I'll look into it, but I don't have as much enthusiasm nowadays as there seems to be a hit and run nature now on XDA.
I can't even get any feedback half the time.
Click to expand...
Click to collapse
tell me about it man. they even let me be a mod!! they must be hard up!! I had better button my lip, dont want any senior mods to think im attempting a mutiny LOLOLOL
it used to be back in the day that people would just accomplish stuff that the mfg said was impossible just to piss them off. Not because they wanted to do anything nefarious with the new found ability, just to poke a stick in their eyes! Man, i miss the OG Evo 4G days
@Androidhelper77 @poppas210 sorry, didnt mean to threadjack, but the root method is available, it just takes some reading of the threads to get there
Thank u
ashyx said:
Root is fairly simple using Magisk pre patched method.
Click to expand...
Click to collapse
This is probably obvious, but what do you mean by "pre patched method?"
EDIT: Nevermind, I figured out what you mean.
Ok, for anyone else who stumbles accross this thread, here's the steps:
Prerequisites:
- Samsung USB Drivers
- Patched Odin flashing tool. v. 1.13 or later. (Mine is v3.13.1_3B_PatcheD) (You might not need the patched one. It's just what I happened to use.) You do indeed need the patched one.
- Stock firmware img (To find version: Settings > About phone > Software version)
1. Activate developer mode.
- Settings > About Phone > Software Information
- Click "Build Number" repeatedly until it says "Congratulations! You are a developer!"
2. Enable USB Debugging and authorize computer.
- Settings > Developer Options > USB Debugging
3. Disable screen lock: Settings > Lock Screen > Screen lock type > None
4. Remove any Google or Samsung accounts: Settings > Accounts and backup > Accounts
5. Unlock boot loader WARNING: THIS WILL ERASE YOUR DEVICE
- Settings > Developer Options > OEM Unlocking
6. Copy the stock farmware img to your phone. You want the file that starts with "AP"
7. Install Magisk Manager by going to the magisk manager website on your phone and hitting "Download Magisk Manager" button and installing the app. The first time you open it, it will need to do additional setup and reboot your device.
8. Open Magisk Manager and select "Install" next to "Magisk." Click Install again, and then click "Select and Patch a File"
9. Select the firmware img you just copied to the phone.
10. Wait for process to complete. (Writing: system.img.lz4 takes a minute)
11. When Magisk Manager says "All done!" close it.
12. Copy the file called "magisk_patched.tar" from your phone to your computer. It should be found in your phone's internal memory "Download" folder.
13. Turn off the phone
14. Open Odin on PC
15. Boot phone into Odin mode: With the phone powered off, press and hold Vol-, Home, and Power until the blue warning screen appears, and then press Vol+ to enter Odin mode.
16. Your phone should appear in Odin on your PC
17. Click the AP button and select the "magisk_patched.tar" file.
18. Click "Start" and then DON'T TOUCH ANYTHING!
19. When the process is complete, a boc in Odin should say "PASS!" and be green. Your phone will reboot. (It will take longer than normal.)
20. Close Odin
21. Initial phone setup. Blah blah...
22. After initial setup, you may get a notification on your phone warning you of unauthorized changes. (Duh.) Just select it and hit cancel.
23. Install Magisk Manager on your phone again (repeat step 6)
24. After a reboot, open Magisk Manager again and it should say "Magisk is up to date."
You are done! Enjoy root access!
SlickStretch said:
Ok, for anyone else who stumbles accross this thread, here's the steps:
Prerequisites:
- Samsung USB Drivers
- Patched Odin flashing tool. v. 1.13 or later. (Mine is v3.13.1_3B_PatcheD) (You might not need the patched one. It's just what I happened to use.)
- Stock firmware img (To find version: Settings > About phone > Software version)
1. Activate developer mode.
- Settings > About Phone > Software Information
- Click "Build Number" repeatedly until it says "Congratulations! You are a developer!"
2. Enable USB Debugging and authorize computer.
- Settings > Developer Options > USB Debugging
3. Disable screen lock: Settings > Lock Screen > Screen lock type > None
4. Remove any Google or Samsung accounts: Settings > Accounts and backup > Accounts
5. Unlock boot loader WARNING: THIS WILL ERASE YOUR DEVICE
- Settings > Developer Options > OEM Unlocking
6. Copy the stock farmware img to your phone.
6. Install Magisk Manager by going to the magisk manager website on your phone and hitting "Download Magisk Manager" button and installing the app. The first time you open it, it will need to do additional setup and reboot your device.
7. Open Magisk Manager and select "Install" next to "Magisk." Click Install again, and then click "Select and Patch a File"
8. Select the firmware img you just copied to the phone.
9. Wait for process to complete. (Writing: system.img.lz4 takes a minute)
10. When Magisk Manager says "All done!" close it.
11. Copy the file called "magisk_patched.tar" from your phone to your computer. It should be found in your phone's internal memory "Download" folder.
12. Turn off the phone
13. Open Odin on PC
14. Boot phone into Odin mode: With the phone powered off, press and hold Vol-, Home, and Power until the blue warning screen appears, and then press Vol+ to enter Odin mode.
15. Your phone should appear in Odin on your PC
16. Click the AP button and select the "magisk_patched.tar" file.
17. Click "Start" and then DON'T TOUCH ANYTHING!
18. When the process is complete, a boc in Odin should say "PASS!" and be green. Your phone will reboot. (It will take longer than normal.)
15. Close Odin
19. Initial phone setup. Blah blah...
20. After initial setup, you may get a notification on your phone warning you of unauthorized changes. (Duh.) Just select it and hit cancel.
21. Install Magisk Manager on your phone again (repeat step 6)
22. After a reboot, open Magisk Manager again and it should say "Magisk is up to date."
You are done! Enjoy root access!
Click to expand...
Click to collapse
Bro I need your help,am stuck at stock farmware img,how do i get it because files come in 5 parts as my firmware?, how I get the boot img?,please help.
desmond462 said:
Bro I need your help,am stuck at stock farmware img,how do i get it because files come in 5 parts as my firmware?, how I get the boot img?,please help.
Click to expand...
Click to collapse
I'm getting ready to leave for work. I'll get back to you in when I get home. I know what you're talking about, but I'll have to look at the files to tell you which goes where.
SlickStretch said:
I'm getting ready to leave for work. I'll get back to you in when I get home. I know what you're talking about, but I'll have to look at the files to tell you which goes where.
Click to expand...
Click to collapse
OK bro, I truly appreciate the help. I await your help, am on pie just wondering if it could make a difference in it being able to root.
desmond462 said:
OK bro, I truly appreciate the help. I await your help, am on pie just wondering if it could make a difference in it being able to root.
Click to expand...
Click to collapse
You're going to want the file that starts with 'AP'. It should be the biggest one. (Mine is about 2.5 GB)
SlickStretch said:
You're going to want the file that starts with 'AP'. It should be the biggest one. (Mine is about 2.5 GB)
Click to expand...
Click to collapse
ok, wat i did was to change md5 to tar of AP, so it turn into zip then I extract boot.img from it, am i on the right path of doing this correctly?
then put in phone storage and open magisk manager to install and then select the boot img which start to flash and about few second it said it failed.
desmond462 said:
ok, wat i did was to change md5 to tar of AP, so it turn into zip then I extract boot.img from it, am i on the right path of doing this correctly?
Click to expand...
Click to collapse
No, I don't think you need to extract anything from it. Just remove the .md5 extension, and Magisk should be able to patch it.
For example, my file is named "AP_J337PVPS4BSI5_CL16191886_QB26045544_REV00_user_low_ship_meta_OS9.tar.md5" so I will remove the .md5 ext leaving me with "AP_J337PVPS4BSI5_CL16191886_QB26045544_REV00_user_low_ship_meta_OS9.tar" which is copied to the phone.
SlickStretch said:
No, I don't think you need to extract anything from it. Just remove the .md5 extension, and Magisk should be able to patch it.
For example, my file is named "AP_J337PVPS4BSI5_CL16191886_QB26045544_REV00_user_low_ship_meta_OS9.tar.md5" so I will remove the .md5 ext leaving me with "AP_J337PVPS4BSI5_CL16191886_QB26045544_REV00_user_low_ship_meta_OS9.tar" which is copied to the phone.
Click to expand...
Click to collapse
ok so u copy that file to phone storage then patch it using magisk?
---------- Post added at 06:57 AM ---------- Previous post was at 06:00 AM ----------
SlickStretch said:
No, I don't think you need to extract anything from it. Just remove the .md5 extension, and Magisk should be able to patch it.
For example, my file is named "AP_J337PVPS4BSI5_CL16191886_QB26045544_REV00_user_low_ship_meta_OS9.tar.md5" so I will remove the .md5 ext leaving me with "AP_J337PVPS4BSI5_CL16191886_QB26045544_REV00_user_low_ship_meta_OS9.tar" which is copied to the phone.
Click to expand...
Click to collapse
oh wow bro, thank you a thousand times over. am root now. Just that step about not extracting that you mention that i dont need to do made the difference in doing the right thing. truly appreciate your help. thank you again.
desmond462 said:
ok so u copy that file to phone storage then patch it using magisk?
---------- Post added at 06:57 AM ---------- Previous post was at 06:00 AM ----------
oh wow bro, thank you a thousand times over. am root now. Just that step about not extracting that you mention that i dont need to do made the difference in doing the right thing. truly appreciate your help. thank you again.
Click to expand...
Click to collapse
You're welcome! I'm glad it worked
SlickStretch said:
You're welcome! I'm glad it worked
Click to expand...
Click to collapse
Yea mon thanks again. So my reason to root is wanting to unlock my sim lock device, am outside US. But even after rooting it still not unlock using the software magic thunder which say it unlock it but still not seeing that it is unlock when I put in another sim, just showing invalid sim. so am stuck again. magic thunder was asking for root permission and not that its root am still unable to unlock it. Just wondering if you have any ideas or knowledge on this unlocking this device.
desmond462 said:
Yea mon thanks again. So my reason to root is wanting to unlock my sim lock device, am outside US. But even after rooting it still not unlock using the software magic thunder which say it unlock it but still not seeing that it is unlock when I put in another sim, just showing invalid sim. so am stuck again. magic thunder was asking for root permission and not that its root am still unable to unlock it. Just wondering if you have any ideas or knowledge on this unlocking this device.
Click to expand...
Click to collapse
It sounds like what you're looking for is a "carrier unlock," but I don't know anything about doing that. Good luck.
Been searching for J337P also...
Androidhelper77 said:
I have been searching the internet for days now and I haven't found a single way to root samsung SM-J337P Android 9 I hope to have some feedback on this site
Click to expand...
Click to collapse
The Best explanation / instructional video I've found so far is: h ttps://youtu.be/BOfv0F12gSI
But, TWRP does not have FW for j3topeltespr. And firmwar.mobi misidentified phone as galaxy j7 2016.
Two and a half days of reading and tubing and have better understanding but not much progress.
h ttps://youtu.be/nOGpFJnLP3A
Think I've found everything
poppas210 said:
Ive been looking to do the same for the last couple of months now & haven't had a bit of luck finding anythng or having any tried methods turn out successful
Click to expand...
Click to collapse
Think I've found everything
Instructions:
h ttps://rootmygalaxy.net/how-to-install-twrp-and-root-samsung-galaxy-j3-achieve/
The Release:
h ttps://github.com/TwrpBuilderTests/android_device_samsung_j3topeltespr/releases/tag/TWRP-3.2.3-TwrpBuilder-2018-10-28_03-45
Question:
Is this the version that causes the boot loop?
I'm seeing so many different posts. Is it rootable or not? I wanna purchase the device but don't want to not be able to root it. Please let me know directly. I'm tmo btw
Got it already, on launch. It's fair, no real stutters at all, quick, but smooth(so don't mess with settings in developer options "drawing" section. There used to be a way, you could build, or "nominate", a twrp for your phone. I don't see that option anymore, just statistics. I'd like a twrp blog.
reggjoo said:
Got it already, on launch. It's fair, no real stutters at all, quick, but smooth(so don't mess with settings in developer options "drawing" section. There used to be a way, you could build, or "nominate", a twrp for your phone. I don't see that option anymore, just statistics. I'd like a twrp blog.
Click to expand...
Click to collapse
I am reading this comment AFTER I replied to your other on a different post and am realizing that your comment was NOT butchered and you DID indeed mean "builder". You can disregard the second half of my comment on that reply because it assumes you meant "build" and an actual "builder" which I had never even heard of. To that note, that actually would be great if there was still one around to utilize for this phone. A TWRP build is much needed to deal with the update problem I am having. The latest update in Lenovo Rescue does not provide the update since it is the same version number. The boot image can not be patched because they are actually different. I guess I can try my hand at capturing the download file if I only knew where it saved it.
There's an experimental build of TWRP for the Edge (NON +). I haven't tried it personally. Mine is BL unlocked and not rooted with Magisk patcher.
Yes the phone is rootable. I got mine a couple days ago - US retail model at BestBuy. Set the phone up, took the update...
Got: XT2063-2_RACER_RETUS_10_QPD30.114-80_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from a thread here, made a tar archive with boot.img, ran the tar through Magisk, flashed it in fastbootd (I get there by booting the phone to recovery; in recovery hold power button for 3 seconds, keep holding it, hold vol up for 2 seconds, release vol up and there ya go. I 'enter fastboot', which shows fastbootd) - rebooted, opened magisk manager and it told me to continue setup - did. Root. Now, it's mine.
I don't undertand why TWRP is so important - I tried 3.4.0 beta9 on the moto g power last week, what a fuk'n mess. No way I was messing with twrp at all on the edge. AM I missing something? What do we even need twrp for anymore? Make a dump with adb, flash with it, do anything...
bronkish said:
Yes the phone is rootable. I got mine a couple days ago - US retail model at BestBuy. Set the phone up, took the update...
Got: XT2063-2_RACER_RETUS_10_QPD30.114-80_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from a thread here, made a tar archive with boot.img, ran the tar through Magisk, flashed it in fastbootd (I get there by booting the phone to recovery; in recovery hold power button for 3 seconds, keep holding it, hold vol up for 2 seconds, release vol up and there ya go. I 'enter fastboot', which shows fastbootd) - rebooted, opened magisk manager and it told me to continue setup - did. Root. Now, it's mine.
I don't undertand why TWRP is so important - I tried 3.4.0 beta9 on the moto g power last week, what a fuk'n mess. No way I was messing with twrp at all on the edge. AM I missing something? What do we even need twrp for anymore? Make a dump with adb, flash with it, do anything...
Click to expand...
Click to collapse
Could you lay out the process in detail, or link us to an existing step by step with the correct download(s) that will work for the Edge? I'd really like to root but want to minimize my chance of creating a brick. Thanks!
If I remembered how I got to the firmware, I would have linked it, sorry - I do not. The filename is: XT2063-2_RACER_RETUS_10_QPD30.114-80_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip. No doubt I followed a thread here.
1 - obtain firmware, extract the archive, make a .tar archive of the boot.img file
2 - request bootloader unlock code from motorola (you must create an account)
3 - unlock bootloader
4 - install magisk manager
5 - in magisk, top section, install: patch file - feed it the boot.img.tar file you made. It will spit you out a new tar file
6 - in fastbootd, flash the patched boot.img file
you are rooted, unless you flashed in fastboot - you must flash the patched boot.img file in fastbootd
Hi,
could you please give the commands you used?
I have completed steps 1-5
I am not sure how to complete step 6
I have the magisk_patched_j5iak.tar file (there is a bot.img file in the archive)
Should I unpack the created magisk_patched_j5iak.tar file?
Please help
Umm, tell you what - try it both ways and then you'll know.
6: your phone is in fastbootd (I told you how to get there) and you flash the boot.img file that you just patched in magisk.
@bronkish Thanks again! I now have my beloved Titanium Backup again! It's been so long since I was rooted I'm going to have to see what else is available again.
[Edit]
Titanium looks a bit dated. Is there a better app now for doing what titanium did?
Rock ON!! SO many "I's" to follow....
I use to use Titanium (pro), too. Today I just export data from apps (settings, really) and I host a nextcloud server - which is handy as fuk (add a calendar event, or contact, on my phone, it's on my server, too, and vice-versa): I can 'share' dumps (exported nova settings, say) and data to nextcloud and if I take a picture 'in the field' it is immediately uploaded to my local nextcloud server and deleted (optional) from my phone. One can achieve all manner of function with nextcloud.
I restore and sync my calendar and contacts from nextcloud (dav), call log from sms backup & restore, which works great - although titamium, 3C, and others do the same.
I do keep handy an apk of every app I like to have installed on my phone, which, really isn't that many. I sometimes use app manager to export apks, or I use FX file manager. I use 3C to backup apps/data. I restore few apps/data with it. 3C can import titanium dumps, as well. I have less need for app/data dumps these days, though. DOn't care at all about twrp, but I'd be more inclined to use the twrp and full system dump restore methodology, as in the past, than using an app like titanium or 3c which requires setting up the phone again first, flashing or installing the app and then restoring apps/data - in this scenario a google account is required for some apps to function again (3c restore) or market links are broken as is handy to do in titanium. A restore from a twrp dump negates all this. You could also use adb for system level (phone) dumps/restore; it's fast and easy.
What do you need to backup? Why? Can you use app exports and a cloud or SD card or some connection to a server/desktop/drive? Can you employ dav? DO you even generate data worthy of backing up?
phone logs
firewall settings (as an example of app settings)
apps/apks in order to achieve function, if you even need to have them handy
texts (if you save them, I use signal and export a text dump to a folder on my sd card, if I even do, which is rare)
contacts, if you don't use google, or whatever
calendar
any important or usable generated data, apps likely have dump scenario
Like anything, there are myriad ways to accomplish the task.
If I'm gonna wipe or reset my phone I have common immediate dumps on my sd card (of course, the phone must have the slot). So, on my card is a folder with some app settings for a quick restore. AFWall settings are there. I have notification sounds and whatnot on the sd root so the phone picks them up. There's a contacts file and calendar file in the dump folder in case I'm near no network when restoring, which, would be odd. There's a couple text dumps, too. Hell, one is 2 years old - why do i keep it? lol.
Also on the card is a key file I use with keepassx as well as a keepass database dump, in case I need it - it's old but has what I need to 'start from scratch' if necessary. I typically just open the keepass dump from nextcloud I just reinstalled from the apk and bam, keepass opens on my phone with my thumb - fuk'n handy. The sd card dumps are just jump-starts if necessary, like, no networking, or something. But, they are there because they would be sorely missed if they were not.
I keep from setting up a google account on the phone for as ong as I can - everything restored, firewall tight, apps frozen, snuffed, or otherwise mitigated. I set the google account up to check fo app updates and for that pain in the ass poweramp which needs to hit the playstore every time it's reinstalled. Pfft. The sd maid and fx file manager apps are so much better to restore because no need for google to validate the purchase.
pffft.
bronkish said:
If I remembered how I got to the firmware, I would have linked it, sorry - I do not. The filename is: XT2063-2_RACER_RETUS_10_QPD30.114-80_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip. No doubt I followed a thread here.
1 - obtain firmware, extract the archive, make a .tar archive of the boot.img file
2 - request bootloader unlock code from motorola (you must create an account)
3 - unlock bootloader
4 - install magisk manager
5 - in magisk, top section, install: patch file - feed it the boot.img.tar file you made. It will spit you out a new tar file
6 - in fastbootd, flash the patched boot.img file
you are rooted, unless you flashed in fastboot - you must flash the patched boot.img file in fastbootd
Click to expand...
Click to collapse
After doing all of this I'm stuck on the Motorola boot screen. Is there any way to fix this?
bronkish said:
Yes the phone is rootable. I got mine a couple days ago - US retail model at BestBuy. Set the phone up, took the update...
Got: XT2063-2_RACER_RETUS_10_QPD30.114-80_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from a thread here, made a tar archive with boot.img, ran the tar through Magisk, flashed it in fastbootd (I get there by booting the phone to recovery; in recovery hold power button for 3 seconds, keep holding it, hold vol up for 2 seconds, release vol up and there ya go. I 'enter fastboot', which shows fastbootd) - rebooted, opened magisk manager and it told me to continue setup - did. Root. Now, it's mine.
I don't undertand why TWRP is so important - I tried 3.4.0 beta9 on the moto g power last week, what a fuk'n mess. No way I was messing with twrp at all on the edge. AM I missing something? What do we even need twrp for anymore? Make a dump with adb, flash with it, do anything...
Click to expand...
Click to collapse
Question what update is that mine is the same XT2063-2 except mine reads QPDS30.114-80-2
Mine, too.
adbman said:
After doing all of this I'm stuck on the Motorola boot screen. Is there any way to fix this?
Click to expand...
Click to collapse
FastbootD
I gave instructions.
I don't mean to be a rude necromancer of posts but, I know nothing of these... tar files you speak of. I tried to do some homework and I see .tar.md5 and .tar.gz. Question 1: Does it make a difference? Is there a post somewhere I can learn from?
Question 2: How does one, or what software is available to, perform this work?
Respectfully,
Me
tar.md5 or, anything.md5 is just a text file containing the md5 hash of the file. You need or want it only if and when you do - if you don't know, then you don't. A .tar file is an archive like a .zip file. a tar.gz, or, .tgz is a compressed tar archive. tar only makes an envelope for the file(s), it doesn't compress unless you tell it to. There's lots of compression schemes - leave all that alone unless you wanna get back to it later. Magisk needs a .tar archive with the boot.img file in it - let's root
Rooting, with stock recovery, is just a couple simple steps. Magisk really makes it easy.
1 - get the firmware and extract it. You'll need the boot.img file.
2 - make an archive (*.tar) to contain the boot.img file. So, on linux, in a terminal, cd into the extracted firmware directory, do: tar -cvf boot-for-magisk.tar boot.img
windows user do your thing. I got a right-click, I don't even know anymore, check my command.
3 - drop that archive you just made onto your phone for magisk to use
4 - get and install magisk , the apk is fine
5 - open magisk. Top section, choose to install (touch the word: install), in next screen, choose select and patch file - feed it the tar achive you made of the extracted boot.img. point to the .tar file. do it.
Magisk will do its thing to the boot image and will spit out a new one that you can install to take advantage; to have root. Wicked. I copy it back to my computer for fastboot action. DO it - copy the new boot image that magisk generated to your computer.
6 - boot your phone to fastbootD - listen....plug your phone into your computer - usb-c cable.
reboot to recovery. In a terminal, do: fastboot devices <return> to check for your phone.
in recovery, press the power button for 3 seconds - at 3(onethousand), press the vol up button as well, for 2 more seconds
after you count 5, release the buttons and you should see a new menu - one of the items says to enter fastboot - that is fastbootD. If you attempt the power and vol up button task and it doesn't work, do it again - it works. SOmetimes it takes a time or 2 to catch it right. In any case, enter this fastboot. one onethousand...
FastbootD!
now, back in your terminal, flash the new boot image that magisk made for you. So: fastboot flash boot FILENAMEOFNEWBOOTIMAGE.img
following the successful flash, enter: fastboot reboot in your terminal - you may unplug your phone.
Success!
bronkish said:
If I remembered how I got to the firmware, I would have linked it, sorry - I do not. The filename is: XT2063-2_RACER_RETUS_10_QPD30.114-80_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip. No doubt I followed a thread here.
1 - obtain firmware, extract the archive, make a .tar archive of the boot.img file
2 - request bootloader unlock code from motorola (you must create an account)
3 - unlock bootloader
4 - install magisk manager
5 - in magisk, top section, install: patch file - feed it the boot.img.tar file you made. It will spit you out a new tar file
6 - in fastbootd, flash the patched boot.img file
you are rooted, unless you flashed in fastboot - you must flash the patched boot.img file in fastbootd
Click to expand...
Click to collapse
I remembered how you got to the firmware
Click this link thing down below the here.
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
You'll be rooted in no time. Careful, now.
Hello, This is a work in progress guide to help you with rooting your phone for whatever reason (i root it to use the Automate app as i am lazy)
I hope this is not a total mess, i will edit this if you have too much trouble reading
DISCLAIMER /!\
• Please consider that you follow this guide at your own risks, i am a random person in the internet, if you do not trust any part of this guide, dont follow it!
• I am adressing this guide to experimented users, i have probably missed a lot of steps and i will try to correct myself, (or not, it takes time sry)
• i am from Europe; not a native english speaker + a noob in the field. feel free to criticize, but be elaborate to help others
I did this on the GALAXY A53 5G phone with :
• Build ver. SP1A.210812.016.A536BXXU1AVCC
• One UI 4.1
• Android Version 12
The following is needed in order to speedrun this :
+MAGISK25.1
+LZ4
+ODIN3.14
+YOUR BOOT.IMG (FROM THE AP_ FILE OF THE FIRMWARE)
1) On your phone go to Settings -> About phone
2) Then -> Software info
3) Check at (the 6th line) ; BUILD Versionfor me it was:
SP1A.210812.016.A536BXXU1AVCC
4) You will have to download yours at sammobile or any other website you trust more : (needs an account but then is free to download)
Download Samsung Galaxy A53 5G SM-A536B firmware
Download the latest Samsung firmware for Galaxy A53 5G with model code SM-A536B. Check out our free download or super fast premium options.
www.sammobile.com
Then when you have you files , the one that matters is the one starting with AP_
5) extract the boot.img.lz4
6) download one of the versions of LZ4 from : https://github.com/lz4/lz4/releases
7) extract all files into a folder
8) drag and drop the extracted file from part 5) INTO the .exe file from part 7)
YOU HAVE YOUR BOOT.IMG
9) Now drag and drop this Boot.img INTO your phone
The version 25.1 of Magisk (or above is needed ? as i used that version of magisk to root my phone i guess)
10) Install it on your A53 you can download it from :
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
11) inside the app, click on INSTALL (written in blue on top right)
12) select the only option
13) go to the boot.img (that you dropped into your phone at part 9)
14) wait
15) when it is done, plug your phone again if you unplugged it and drop the new file generated by MAGISK into your computer and rename it boot.img.tar
Unlock the bootloader of your phone by either ;
• Watch a tutorial it helped me understand why i kept having an error while doing the next steps (i "unlocked" OEM only within dev options, that wasn't enough)
and skip to 22)
• Or follow these steps
on your A53 go developper mode by clicking 7-10 times on the VERSION in settings -> about phone -> Software
turn on the switch for OEM unlocking (wifi must be connected if the button doesnt appear)
and i am not sure if we need to but , turn on the switch for USB DEBUGGING as well (for adb)
16) stay pressed on both VOL UP + VOL DOWN
17) plug your phone to computer
18) wait
19) long press VOL UP
20) wait
21) press VOL UP
ez
So now get ODIN 3.14 on ur computer
I got the official website but cant remember where from, i will look into it, maybe you can find it on google but be carefull of malicious ones i swear !
(if you are kind enough you will share it below ♥)
22)after launching ODIN
23)The on the AP button put your boot.img.tar file that you got from part 15)
24) on your A53 go developper mode by clicking 7-10 times on the VERSION in settings -> about phone -> Software
25) check that you wave wifi connected
26) go to dev options and check if OEM unlock is grey'd out
30) turn OFF your A53 phone
wait for it to BZZZZZZZZ (viber)
31)STAY PRESSED onto the 2 buttons VOL UP + POWER
on recovery choose the 2nd option with your volume keys, "reboot to bootloader"
then if odin recognise the phone press start
This looks like a great guide. Too bad OEM Unlocking doesn't appear on US carrier phones, or else I'd totally do this :/
sorry if i sound stupid but how do i get the boot.img.lz4 file?
This does NOT work on VD7 or most likely later with Magisk 25.1/25.2 (the BL is unlocked on this SM-A536B as I get the warning on reboot and the OEM unlocked is on and greyed out in developer options).
I used the patch the entire AP file method in Magisk and flashing the patched AP file (you can google T505N XDA root Samsung; I will find the forum link later and remember to post it here (this method works on VD7 and probably higher)
I am now rooted with TWRP, thanks to this site, https://www.droidwin.com/install-twrp-recovery-and-root-samsung-galaxy-a53-5g/
Still cannot delete system/app, system/priv-app (not even in twrp) but am able to access data/app (and remove .digest and .dm files)
crazyut said:
I used the patch the entire AP file method in Magisk and flashing the patched AP file (you can google T505N XDA root Samsung; I will find the forum link later and remember to post it here (this method works on VD7 and probably higher)
Click to expand...
Click to collapse
Confirmed, works with VG1 and latest VGA. I used patched AP along with BL, CP and (Home) CSC. Please note that you have to do a factory reset after this, so remember to backup your data properly.
Hlo I rooted my a53 5g thanks to you but cannot remount system partition as read write
I get this output after running
Code:
mount -o remount,rw / <
'/dev/block/dm-0' is read-only
Please help me with it
And also cannot disable dm-verity flashed disable-dm-verity.zip but after formatting data device stuck in bootloop...
Hello. I am new to programming. I have a rudimentary knowledge of android, i.e. whatever I figured out while jailbreaking JP5 and JP6 Securus tablets, and I await academic coursework for formal education in computer hardware and software engineering.
Clarity and redundancy is greatly APPRECIATED regarding any replies to my post.
The question(s) are, what benefits would I obtain from rooting my A53, what about the Cons? I Can I improve the performance of my phone, processing data, etc.
Afterwards in the future, can I still flash the Android 13 firmware? Does Samsung find out?
I know I have to read up, I am being lazy.
THANK YOU.
JoseAndDiezel104 said:
Hello. I am new to programming. I have a rudimentary knowledge of android, i.e. whatever I figured out while jailbreaking JP5 and JP6 Securus tablets, and I await academic coursework for formal education in computer hardware and software engineering.
Clarity and redundancy is greatly APPRECIATED regarding any replies to my post.
The question(s) are, what benefits would I obtain from rooting my A53, what about the Cons? I Can I improve the performance of my phone, processing data, etc.
Afterwards in the future, can I still flash the Android 13 firmware? Does Samsung find out?
I know I have to read up, I am being lazy.
THANK YOU.
Click to expand...
Click to collapse
While I don't have a Galaxy A53, I can speak from experience that almost all Samsung phones suffer from the same pros and cons to rooting
Let's start with the pros:
Using a system-wide adblocker like Adaway is much more battery friendly and more effective using it on root mode than any non-root alternative. This one is the main reason a lot of people root and I think it merits it, it's a really amazing ad blocker.
You'd be able to activate some features that Samsung likes to disable on A-series, like full edge lighting and the camera privacy toggle (I don't know if it's disabled on A53 by default but I'm leaning towards yes)
You get to experiment with GSI and maybe some custom ROMs in the future
You can install some neat Magisk modules like the Pixelify module for example, that tricks Google Photos and lets you have unlimited space like the Pixels have.
With root, you have almost unlimited possibilities of modding your phone, it's just a matter of knowing what you want to modify and finding the right mods to it.
Now, the cons:
Samsung phones have an e-fuse. Flashing custom firmware automatically trips this fuse and it is impossible to recover from unless you change the motherboard. When this fuse is blown, you will never be able to use Samsung's security features like Samsung Pass, Pay, Secure Folder, Secure Wifi, etc...
Even if you flash your stock firmware and even if you re-lock your bootloader, the fuse will still be blown.
There are some regions which even deny any warranty claims if they find out that this fuse is blown, but some places in Europe still accept the phone in this condition.
Another con is that sometimes some apps refuse to work if they detect you are rooted like Google Pay and I believe Netflix and others too (like banking apps). Some are easy to fool/bypass root detection and some are more complicated. It all depends on the app.
And to answer your final question. Fortunately for you, you still should be able to flash the latest stock firmware and if you re-lock your bootloader, you should still be able to receive updates via OTA, just keep in mind of the services that will never work again I mentioned above
Hello. I am following up with my previous post.
I found the exact zip and Odin file at Sammobile. Would this be a good start? My understanding is that the bootloader option is not available yet
...
I am learning as I go and before I move forward (big IF) I want as many redundancies as I can.
JoseAndDiezel104 said:
Hello. I am following up with my previous post.
I found the exact zip and Odin file at Sammobile. Would this be a good start? My understanding is that the bootloader option is not available yet
...
I am learning as I go and before I move forward (big IF) I want as many redundancies as I can.
Click to expand...
Click to collapse
I din't have unlocking bootloader option. But I did:-
1)factory reset phone
2)insert sim
3)restart phone
4)enable developer mode
5)And you will get a message "Welcome to Samsung your device is registered"
6)that's it OEM unlocking option will be avilable
7)power off phone
8)holding vol +&- keys connect usb to pc
9) leave both keys after you see waring messages
10)press and hold volume + key , bootloader will be unlocked and phone will be factory resetted.
aryanrh said:
I din't have unlocking bootloader option. But I did:-
1)factory reset phone
2)insert sim
3)restart phone
4)enable developer mode
5)And you will get a message "Welcome to Samsung your device is registered"
6)that's it OEM unlocking option will be avilable
7)power off phone
8)holding vol +&- keys connect usb to pc
9) leave both keys after you see waring messages
10)press and hold volume + key , bootloader will be unlocked and phone will be factory resetted.
Click to expand...
Click to collapse
Would this work for US phones?
nsfxpython said:
Would this work for US phones?
Click to expand...
Click to collapse
Unless you find a a hack, any U/U1 (USA/United States/The States/States/American/America) and W series (Canada) phones have not been bootloader unlock or root for the last 5+ years or more. If you want root options, get a B (EU/UK) or E series phone.
crazyut said:
Unless you find a a hack, any U/U1 (USA/United States/The States/States/American/America) and W series (Canada) phones have not been bootloader unlock or root for the last 5+ years or more. If you want root options, get a B (EU/UK) or E series phone.
Click to expand...
Click to collapse
Is there any way to recover deleted pictures in the Samsung A53 5G (USA version) if it is impossible to root this version of the phone?
I accidentially manually deleted some photos in my phone today with my computer (so it doesn't appear in the photo's trash bin), and every single recovery program I encountered says I need to root my phone in order to use a deep scan to look for the deleted files.
I have litte hope that there is anything to recover. Despite the fact that us versions can't be unlocked what would be necessary for rooting, flash storage management (also garbage collection, trim etc.) tends to shift data all the time to other/new cells making it unlikely for you to recover lost data on an active device. Better backup from time to time, always your best bet.
Hello! Im having an issue, maybe im doing somthing wrong. I'm at 13) After giving the img.boot.lz4 i wait and wait and the memory of the phone fills completly (Around 120+Gb) and the patched img do not comes out, any thougths?
This is a deprecated method. You have to patch the whole AP file with magisk and flash it along with BP, CP and (Home) CSC after you've unlocked the bootloader.
Andoreid said:
This is a deprecated method. You have to patch the whole AP file with magisk and flash it along with BP, CP and (Home) CSC after you've unlocked the bootloader.
Click to expand...
Click to collapse
That's right, but for folks with no experience rooting new Samsung devices, please:
- DO read OP's "Unlock bootloader" section. Visitors to this page who skip to the end and have never rooted non-Samsung or older devices might think "adb reboot fastboot" followed by "fastboot flashing unlock" or "fastboot oem unlock" will do the trick. It won't. To clarify: fastboot will NOT recognize this phone, which is normal because it doesn't have a standard fastboot mode, and simply enabling "Allow OEM unlock" in developer settings is necessary but not enough.
Do follow OP's steps for unlocking.
- For rooting, I followed the instructions here https://samsungusbdriver.me/root-samsung-galaxy-a53-5g/ (second method).
But the instructions on that page for getting the actual model number and CSC for Frija are unclear. Finding that information was not straightforward. Depending on the method I used, the model number would be SEPF_SM-A536B_12_0001, SM-A536B/DS, A536B... and you need to know CSC stands for "country-specific code" and it's a 3-character code. I eventually figured out my model was SM-A536B and CSC was EUX. But it took quite a bit of research.
-If you're not familiar with Magisk's DenyList, google it. You might have to use it some apps, particularly banking apps. I think you need it for Netflix, too. Speaking of Netflix, the version that comes preinstalled won't work after rooting. The way I got it to work was uninstalling that version and sideloading the Netflix APK from Apkpure. And adding it to Magisk's DenyList.
Hello,
I have a rooted (Magisk) A53 with TWRP. For a week, I get a notification asking me to update to security patch level of May 1st, 2023. I thought that with unlocked bootloaders, OTA wasn't possible, but whatever. My question is if it's possible to perform the update without losing TWRP and Magisk, and also if it's possible to keep all user data and installed apps. I have little time to spare after work and really don't want to go again through the process of resetting my phone.
Thanks.