Related
This Guide will work on S7 and S7 Edge Variants, probably also on other Samsung Phones. It doesn't matter if you have xposed and/or supersu installed
I did lately try to encrypt my device after installing my rom. So I tried to search on xda but I couldn't find anything useful until now.
After quit some time I finally managed it to get a working encryption, even with custom rom installed (which contains root and xposed). I will present the following steps here to help you folks to get an encrypted device.
Root will work as always after encryption :highfive:
Attention, TWRP can't read /data partition after this guide, that's because twrp doesn't support samsungs encryption at all
Pre requests:
- A working pc with adb installed
- Enough battery (at least 80%)
- Charger in your near field
- Working internet connection
Steps:
1. Go to SuperSU application on your device
2. Head over to the settings Tab
3. Scroll down and hit Full unroot
4. Click continue, when it asks you to install stock boot.img say NO, also NO on restoring stock recovery
5. SuperSU app should disappear
6. Make one full reboot
7. Head over to settings, lock screen and security, set a password
8. Plug in your charger and start encryption
9. Wait until your phone has fully encrypted (this can take quit some time)
10. After your device has successfully encrypted, we want to gain root access again
11. Boot into TWRP recovery
12. You now need a pc with working adb connection
13. Click adb sideload on twrp
14. Download latest super su to your PC, you can get that from here: Beta Thread
15. Open a terminal on your PC
16. Put the supersu.zip in the same direction as your terminal is opened (example: user/home)
17. Type into terminal: adb sideload *supersu_name*.zip
18. Reboot your phone and you have a working, encrypted phone with root installed!
If this guide helped you, please share it and hit thanks as well! :good:
@Tkkg1994
I don't think it could protect your data.
Here is a simple way to steal data from a encrypted phone with unlocked FRP.
Just add this script to ramdisk of kernel.
Code:
#!/system/bin/sh
rm -rf /data/system/lock*
rm -rf /data/system/gatekeep*
And this script will automaticlly remove any screen locks after the data partition is already unlocked by the system after boot.
You may ask:
Could I prevent unauthorized kernel from booting? (by re-enable FRP lock)
No, you can't because systemless install of SuperSU already modify the kernel and you can't boot modified kernel with FRP on.
Could I restore to stock kernel after finish this and then enable FRP?
You will lose your root.
And this way cannot prevent theft from reset your phone and then use it.
So, in a word, any tries to keep your phone safely after root are stupid.
It could only stop those low-IQ theft but it could not stop someone who really concern your data.
Jesse Chan said:
@Tkkg1994
I don't think it could protect your data.
Here is a simple way to steal data from a encrypted phone with unlocked FRP.
Just add this script to ramdisk of kernel.
Code:
#!/system/bin/sh
rm -rf /data/system/lock*
rm -rf /data/system/gatekeep*
And this script will automaticlly remove any screen locks after the data partition is already unlocked by the system after boot.
You may ask:
Could I prevent unauthorized kernel from booting? (by re-enable FRP lock)
No, you can't because systemless install of SuperSU already modify the kernel and you can't boot modified kernel with FRP on.
Could I restore to stock kernel after finish this and then enable FRP?
You will lose your root.
And this way cannot prevent theft from reset your phone and then use it.
So, in a word, any tries to keep your phone safely after root are stupid.
It could only stop those low-IQ theft but it could not stop someone who really concern your data.
Click to expand...
Click to collapse
Some guys need encrypted phones for their work (as some exchange server or email clients only work on encrypted devices)
I know that it is pretty much useless (since we have root access and can pretty much do anything with it)
So basically it brings you some more security but mainly gives those guys who need an encrypted phone for work a chance to have root and encryption together
Sent with my SM-G930F powered by SuperMan
Maybe my remark is stupid but with lollipop the user had to enter the decryption key just before loading the system... So even if the system was rooted, without the key it was impossible to recover the data...
You are saying me that now, in marshmallow Android is storing the key directly in the device ? And if one day there is a small flaw in the kernel all the data could be decrypt...
Thanks for you answer, i'am not an expert in security but i'am really interested in.
Hi,
I installed SuperMan rom without root/xposed and I can't get it to encrypt. It just restart the phone.
is there something else I need to do?
jesec said:
@Tkkg1994
I don't think it could protect your data.
Here is a simple way to steal data from a encrypted phone with unlocked FRP.
Just add this script to ramdisk of kernel.
Code:
#!/system/bin/sh
rm -rf /data/system/lock*
rm -rf /data/system/gatekeep*
And this script will automaticlly remove any screen locks after the data partition is already unlocked by the system after boot.
You may ask:
Could I prevent unauthorized kernel from booting? (by re-enable FRP lock)
No, you can't because systemless install of SuperSU already modify the kernel and you can't boot modified kernel with FRP on.
Could I restore to stock kernel after finish this and then enable FRP?
You will lose your root.
And this way cannot prevent theft from reset your phone and then use it.
So, in a word, any tries to keep your phone safely after root are stupid.
It could only stop those low-IQ theft but it could not stop someone who really concern your data.
Click to expand...
Click to collapse
Even with a locked FRP=1 I have been able to defeat it and gain access to the phone to USE, but never the data. Your script will only remove the locks once the data partition has beenunlocked, you still have not successfully recovered the data.
remixtech said:
Maybe my remark is stupid but with lollipop the user had to enter the decryption key just before loading the system... So even if the system was rooted, without the key it was impossible to recover the data...
You are saying me that now, in marshmallow Android is storing the key directly in the device ? And if one day there is a small flaw in the kernel all the data could be decrypt...
Thanks for you answer, i'am not an expert in security but i'am really interested in.
Click to expand...
Click to collapse
The key is ofc stored on the device, but it is in an encrypted state. ofc if there is a flaw in the kernel, unreported, this can be exploited to remove encryption somehow. Also you could remove the system rom chips and virtual simulate them and try to unlock thousands/millions of times defeating any format on bad password, etc. IF someone wants to access your data, they will. Just like the FBI iphones were opened. Its only a matter of money and time, no encryption is safe forever.
cridtohs said:
Even with a locked FRP=1 I have been able to defeat it and gain access to the phone to USE, but never the data. Your script will only remove the locks once the data partition has beenunlocked, you still have not successfully recovered the data.
The key is ofc stored on the device, but it is in an encrypted state. ofc if there is a flaw in the kernel, unreported, this can be exploited to remove encryption somehow. Also you could remove the system rom chips and virtual simulate them and try to unlock thousands/millions of times defeating any format on bad password, etc. IF someone wants to access your data, they will. Just like the FBI iphones were opened. Its only a matter of money and time, no encryption is safe forever.
Click to expand...
Click to collapse
Admittedly, yes.
It could only remove screen lock AFTER data partition is unlocked.
But in most situations, it could recover data because most people didn't set password as startup password.(What means data partition is already unlocked automatically before UI appear)
jesec said:
Admittedly, yes.
It could only remove screen lock AFTER data partition is unlocked.
But in most situations, it could recover data because most people didn't set password as startup password.(What means data partition is already unlocked automatically before UI appear)
Click to expand...
Click to collapse
how do we make sure that we set a "start up" password then? Is it the same if you use a long pin instead of a password?
|mickey said:
how do we make sure that we set a "start up" password then? Is it the same if you use a long pin instead of a password?
Click to expand...
Click to collapse
in security Lock screen and security there is an option for set pin on startup.
Also as an update to this method, if you had Xposed and magisk root, or if you had supersu and suhide, they need to all be reinstalled. This is the same method as flashing a stock bootloader then re-rooting afterwards. With new TWRP though you do not need to sideload because it has password to decrypt /data and allow flashing of the ramdisk, so you dont HAVE to sideload the supersu, but I suggest following TKK's tutorial exactly for sucess
cridtohs said:
in security Lock screen and security there is an option for set pin on startup.
Also as an update to this method, if you had Xposed and magisk root, or if you had supersu and suhide, they need to all be reinstalled. This is the same method as flashing a stock bootloader then re-rooting afterwards. With new TWRP though you do not need to sideload because it has password to decrypt /data and allow flashing of the ramdisk, so you dont HAVE to sideload the supersu, but I suggest following TKK's tutorial exactly for sucess
Click to expand...
Click to collapse
When you press encrypt you have to set such a password anyway so I don't see your point... You have to set a password, that is requested whenever you start your device... Is that not the same thing your describing?
Can't get encryption to work. The process starts and after a few seconds my phone just reboots.
Tested on several ROMs and Kernels, same result.
Anybody got an idea? I'm clueless...
unique730 said:
Can't get encryption to work. The process starts and after a few seconds my phone just reboots.
Tested on several ROMs and Kernels, same result.
Anybody got an idea? I'm clueless...
Click to expand...
Click to collapse
Same problem here - one more scream for HELP
unique730 said:
Can't get encryption to work. The process starts and after a few seconds my phone just reboots.
Tested on several ROMs and Kernels, same result.
Anybody got an idea? I'm clueless...
Click to expand...
Click to collapse
darkman088 said:
Same problem here - one more scream for HELP
Click to expand...
Click to collapse
When I tested this I had similar issues due to root. You made both a full unroot and followed all steps?
Sent from my SuperMan powered SM-G930F
Tkkg1994 said:
When I tested this I had similar issues due to root. You made both a full unroot and followed all steps?
Sent from my SuperMan powered SM-G930F
Click to expand...
Click to collapse
Hello and thanks for replying.
No, I didn't do a full unroot, because when I was testing this, I hadn't come across this thread And now I am not willing to invest that much time again, just to find out, that it's not working, once again
But I've tried many other strategies, which are very similar, but didn't work:
1) Disable SuperSU from the Application manager
2) Disable SuperSU from the settings of the app
3) Install busybox, boot in safe mode, connect the phone to my laptop, launche adb and enter there pkill -KILL daemonsu - this must be equivalent, as ps | grep daemonsu was not showing anything...
4) Tilting my phone in landscape mode
5) Repeating the attempt to encrypt several times after eachother
6) Many many more useless tips, which I found on the internet
Please kindly advise. Many thanks!
P. S.: HOW COME only the ROM of artas182x has encryption working PERFECTLY and I couldn't manage to encrypt my phone with no other ROM ? For example, I tried Slim ROM, which (if I'm not wrong) is not rooted and again - encryption didn't work, it hung somewhere along the process This is really terrible. Please excuse my total frustration
darkman088 said:
Hello and thanks for replying.
No, I didn't do a full unroot, because when I was testing this, I hadn't come across this thread And now I am not willing to invest that much time again, just to find out, that it's not working, once again
But I've tried many other strategies, which are very similar, but didn't work:
1) Disable SuperSU from the Application manager
2) Disable SuperSU from the settings of the app
3) Install busybox, boot in safe mode, connect the phone to my laptop, launche adb and enter there pkill -KILL daemonsu - this must be equivalent, as ps | grep daemonsu was not showing anything...
4) Tilting my phone in landscape mode
5) Repeating the attempt to encrypt several times after eachother
6) Many many more useless tips, which I found on the internet
Please kindly advise. Many thanks!
P. S.: HOW COME only the ROM of artas182x has encryption working PERFECTLY and I couldn't manage to encrypt my phone with no other ROM ? For example, I tried Slim ROM, which (if I'm not wrong) is not rooted and again - encryption didn't work, it hung somewhere along the process This is really terrible. Please excuse my total frustration
Click to expand...
Click to collapse
Ehm what is artas182x rom? or slim rom? we don't have that on our s7 as far as I know.
This guide may needs some adaptions to work on other devices
Tkkg1994 said:
Ehm what is artas182x rom? or slim rom? we don't have that on our s7 as far as I know.
This guide may needs some adaptions to work on other devices
Click to expand...
Click to collapse
It's a Marshmallow port from Galaxy S5 made by artas182x. I didn't like Slim ROM - it doesn't even have a file maanger
installed with it and when I tried encryption with it, it didn't work
Thank you!
We need someone xposed module to emulate knox 0x0 so that we can use knox again.
Tried with King Nougat V5 custom tom
After encryption finish and boot it keep showing "system ui has closed" error
I cannot type my password
Now doing full wipe
jimmod said:
Tried with King Nougat V5 custom tom
After encryption finish and boot it keep showing "system ui has closed" error
I cannot type my password
Now doing full wipe
Click to expand...
Click to collapse
I assume you have a modded systemUI. Try it with a stock one
Sent from my SuperMan powered SM-G930F
data encryption and root and TWRP toegether - is that working in android nougat ?
I really, really want encyption on my rooted S7 (930FD) incl. TWRP - but before I try this method here I have two questions:
- you are using the "terminal" - means you are using Linux? Or can I do this with windows powershell as well?
- encryption and root incl. TWRP works with Marshmallow MM only or will this work in Nougat as well?
Is there any new instruction how to force VoLTE and VoWifi to work on PIXEL3?
Features works great on S9, SIM card is provisioned. The IMS options are blacked out on PIXEL.
Does any Custom ROM forces the feature to work even if carrier says that they don't officialy support it?
If it is just that your provider does not allow this service on Pixel you could try MagiskHide Props Config module to change device fingerprint to match a phone that is supported by your carrier. Not sure if it will word, but worth a shot.
wangdaning said:
If it is just that your provider does not allow this service on Pixel you could try MagiskHide Props Config module to change device fingerprint to match a phone that is supported by your carrier. Not sure if it will word, but worth a shot.
Click to expand...
Click to collapse
Carrier says that the issue is not on their side, they claim that they have enabled services. I checked on S10 with the same SIM card, both VoLTE and VoWifi works without issues.
The other thing is that I don't want to dive deep into changing factory images to force the features. I would need to unlock bootloader and root phone.
Until now Google does everything just to avoid questions and providing support for modem issues for other carriers than US.
mxtuu222 said:
Carrier says that the issue is not on their side, they claim that they have enabled services. I checked on S10 with the same SIM card, both VoLTE and VoWifi works without issues.
The other thing is that I don't want to dive deep into changing factory images to force the features. I would need to unlock bootloader and root phone.
Until now Google does everything just to avoid questions and providing support for modem issues for other carriers than US.
Click to expand...
Click to collapse
It might have something to do with the modem files in the vendor partition, we have that issue here in China. Only way to fix that is to be rooted and systemlessly make the phone read the files correctly. Custom roms cannot change the vendor.img.
wangdaning said:
It might have something to do with the modem files in the vendor partition, we have that issue here in China. Only way to fix that is to be rooted and systemlessly make the phone read the files correctly. Custom roms cannot change the vendor.img.
Click to expand...
Click to collapse
;/ so probably there is no easy workaround. Rooting and modem modification makes it too complex. Especially that on Android Q there is a problem with USB debugging mode for Qualcomm in fastboot
PIXEL2: [GUIDE]Enable VoLTE for unsupported carriers
mxtuu222 said:
;/ so probably there is no easy workaround. Rooting and modem modification makes it too complex. Especially that on Android Q there is a problem with USB debugging mode for Qualcomm in fastboot
PIXEL2: [GUIDE]Enable VoLTE for unsupported carriers
Click to expand...
Click to collapse
Rooting is not really dangerous, and the modem modification makes no real changes. It is systemless changes, which means no files are actually modified. What carrier do you use, odd that a US carrier would not be supported natively by google.
wangdaning said:
Rooting is not really dangerous, and the modem modification makes no real changes. It is systemless changes, which means no files are actually modified. What carrier do you use, odd that a US carrier would not be supported natively by google.
Click to expand...
Click to collapse
I need to have an option for carrier PLAY in POLAND.
I'm curious if just a root and enabling VoEnabler packet from MAGISK will be enough.
Some of the guys from PIXEL 2 were suggesting to use modem configs with VoLTE, VoWifi from the same chipsets Qualcomm 845 and putting it to PIXEL 3.
mxtuu222 said:
I need to have an option for carrier PLAY in POLAND.
I'm curious if just a root and enabling VoEnabler packet from MAGISK will be enough.
Some of the guys from PIXEL 2 were suggesting to use modem configs with VoLTE, VoWifi from the same chipsets Qualcomm 845 and putting it to PIXEL 3.
Click to expand...
Click to collapse
That is problematic, as looking at the modem files (on my device), their is nothing under the folders for PLAY network. That would mean you could get the modem file from another similar device that has it, but the magisk setup would need to change two files instead of one. You would have to mock load a mbn file for your provider. You would need to change /mcfg_sw/generic/"modem file you want to try" and /mcfg_sw/mbn_sw.txt to include the directory of the file you want to include.
In reality, those mbn files you get might never work. This is google borking their work. For us in China, the modem files are their, they just refuse to reference them. For you the files are not even there it seems.
Try this. You will need magisk root to do it. You will also need to edit the zip file with the mbn file you can get a hold of. It will go in this file "For Help Pixel 3 LTE-VoLTE Enabler.zip\system\vendor\rfs\msm\mpss\readonly\vendor\mbn\mcfg_sw\generic\EU\Play" directory. It will simlpy load the modem file you need/want/got from a similar device at boot(just name it mcfg_sw.mbn and put it in there replacing the "put mcfg_sw.mbn here.txt"). You also need to delete the files in the description of the module (these are auto generated files) before this will take place. Good luck.
If you are doubtful, have a good look at what I am asking it to do.
wangdaning said:
Try this. You will need magisk root to do it. You will also need to edit the zip file with the mbn file you can get a hold of. It will go in this file "For Help Pixel 3 LTE-VoLTE Enabler.zip\system\vendor\rfs\msm\mpss\readonly\vendor\mbn\mcfg_sw\generic\EU\Play" directory. It will simlpy load the modem file you need/want/got from a similar device at boot(just name it mcfg_sw.mbn and put it in there replacing the "put mcfg_sw.mbn here.txt"). You also need to delete the files in the description of the module (these are auto generated files) before this will take place. Good luck.
If you are doubtful, have a good look at what I am asking it to do.
Click to expand...
Click to collapse
Great, thank you for all the tips. I will try to find some mbn files from NOKIA modems.
Do you know if it's possible to unlock the bootloader, root, make possible changes, unroot, lock bootloader?
Is the modem file will be permanently on vendor partition even if I install newest OTA?
mxtuu222 said:
Great, thank you for all the tips. I will try to find some mbn files from NOKIA modems.
Do you know if it's possible to unlock the bootloader, root, make possible changes, unroot, lock bootloader?
Is the modem file will be permanently on vendor partition even if I install newest OTA?
Click to expand...
Click to collapse
I am pretty sure you will need to keep root, as magisk is mocking the modem file you need. It somehow could cause the phone to connect and after the phone stays connected, but I do not see how that could work.
Hello, is there a way to root the phone where everything works now (Bluetooth, Face ID, etc.)?
I would very much like to see this answered. I've seen some application-specific instructions such as this reddit thread for enabling Samsung Health, and I've read about hiding the fact that the phone is rooted from apps by using MagiskHide, but it's not clear whether this works for all apps and features or just some. There's also this recently updated guide to rooting that claims:
Magisk is a highly advanced way of rooting android systemless-ly. This means that Magisk root android without changing or modifying the system partition. Hence you can receive OTA updates, run apps that require to pass Google’s SafetyNet tests.
Click to expand...
Click to collapse
However, many hacks that sound good when you read about them in advance run into snags and gotchas once you actually get into implementing them, and I'm hesitant to just give it a try and see how it works out when tripping Knox is irreversible and if things stop working you can't get them back by flashing the stock ROM.
I'd be grateful if anyone who has actual experience on this subject could vouch for being able to re-enable all lost functionality after rooting or to not lose it in the first place, or whether even some lost functionality can be enabled (and if so, what have you been able to get working and what haven't you? I don't know about OP, but to me the most important ones are Secure Folder and Samsung Health).
Also, does anyone have experience with retaining Knox-sensitive functionality on rooted S9 Exynos with Android 11 (either rooting after upgrading to 11, or rooting first and retaining root when upgrading)?
@bis225
IMO noone needs Magisk to root a device's Android. Rooting Android means having the SU-binary present on Android - a ~100KB file - nothing else. Copying SU-binary onto Android allows you to temporariy give you root access when needed.
jwoegerbauer said:
@bis225
IMO noone needs Magisk to root a device's Android. Rooting Android means having the SU-binary present on Android - a ~100KB file - nothing else. Copying SU-binary onto Android allows you to temporariy give you root access when needed.
Click to expand...
Click to collapse
I'm not sure I understand what you're saying. Are you telling me that you can simply copy the file onto an unrooted phone, and voila, you can gain root access?? Can you point to information about what to do and how this works? It runs contrary to everything I've ever read on the subject.
To the best of my understanding, in order to install su binary unto an unrooted phone you need to install a custom recovery, and use that to flash the su binary onto the phone. I thought the idea of Magisk was to provide root access without modifying system files so that SafetyNet can't detect that the system has been modified. Unless I'm missing something there's no disadvantage to rooting with Magisk, only advantages, but regardless, I don't see how it makes a difference with respect to this topic. Installing a custom recovery is what trips Knox and prevents some features and apps from working, so it doesn't really matter what root method you use if you have to use a custom recovery to install it.
If you know of a way to root a Galaxy S9 without using a custom recovery or tripping Knox and that can't be detected by SafetyNet, please elaborate.
Rooting Android simply means to add a ( hidden ) user called root ( AKA super-user ) who has ALL rights to Android's file system.
For example from within ADB you activate this user and let run him any command what requires to have ALL rights - assumed the SU-binary is located in /sdcard
Code:
adb shell "/sdcard/su -c '<command-here>'"
AFAIK Magisk installs the SU-binary in /data/adb/magisk/busybox, but I may err.
@jwoegerbauer
But I didn't ask what rooting means. Unfortunately, this doesn't answer any of my questions.
I think I clearly expressed that neither a Custom Revovery nor Magisk itself is needed to have root, that simply copying SU-binary to Android's user-space is enough.
If you want to root via Magisk then do it.
Personally never would do it this way.
jwoegerbauer said:
I think I clearly expressed that neither a Custom Revovery nor Magisk itself is needed to have root, that simply copying SU-binary to Android's user-space is enough.
If you want to root via Magisk then do it.
Personally never would do it this way.
Click to expand...
Click to collapse
This really seems contrary to everything I've read, and this Stack Exchange thread specifically explains why that wouldn't work, but if you say you have experience with this and it works for you, I'm certainly willing to give it a try and see how far it gets me. Do you know where a copy of the su binary can be obtained? All my searches for su binary lead to the supersu APK and instructions for installing it by flashing, or something along those lines. I can't find an su executable that can just be copied to internal storage as-is anywhere.
I own some old samsung Galaxy models like J7 Prime and had tried good Custom ROMs on them but up recent I purchased this Samsung Galaxy M21 2021 Edition (SM-M215G/DS) a few days ago thinking that it's going to be same as Galaxy M21 2019 (SM-M215F) model, to my horor its bootloader & recovery seems to work differently from J7 prime (with bar codes in download mode) . So it's a differrent model. The bootloader unlock process on this Galaxy M21 2021 Edition is same as mentioned in Galaxy M21 2019 thread ( https://forum.xda-developers.com/t/rom-full-oneui-10-totsukaos-q-for-galaxy-m21.4219975/ ) but none of the unofficial TWRP recoveries work nor does Magisk boot.img patch method work for rooting this model. Samsung does not support Fastboot as I understand & everything ends with Error : Signature verification failed. The only option left to me is sell off this phone but its so new.
If any developer can help me with some Custom Recovery that could install itself for rooting and perhaps custom ROM (I know I'm asking for too much ) for this device (SM-M215/DS), I will gladly donate $20.00/month for a year (Pls consider the bad times of pandemic we all are in). As right now I've put up this device (SM-M215G/DS) for sale. I've attached a few screenshots of the device maybe it could help any Dev who's interested (Hopefully ).
To root Android a Custom Recovery isn't required at all.
jwoegerbauer said:
To root Android a Custom Recovery isn't required at all.
Click to expand...
Click to collapse
jwoegerbauer said:
Firstly, I THANK YOU for replying to my desperate post. I'm delighted that Dev (jwoegerbauer) wanted to help.
Coming to the topic, Yes I was aware that rooting didnt require Custom Recovery.
1> I had tried to install Magisk_V23.zip via command [adb sideload magisk.zip] but the
response I had got was [Error: Signature verification failed, Error: Aborted.] on this device
(SM-M215G/DS).
2> When I flashed couple of TWRPs (one official for Galaxy M20 from www.twrp.me & few
unofficial TWRP builds from the net) via latest ODINv14.3 , ODIN displayed PASS! and
rebooted as I had kept Auto Reboot & F.Reset Time ON. But Native Android revovery came
on with Custom Binary Error. Again, I did the same with F.Reset Time & Auto Reboot OFF this
time and when I manually rebooted to recovery (Vol UP + Power) it was back to native
android recovery. I had to factrory reset to get the samsung logo then booted into welcome
screen.
3> I have checked the link ( https://forum.xda-developers.com/t/...al-adb-fastboot-
drivers.4185535/post-83851013 ) you provided. Awesome work! My questions are will it
enable FASTBOOT on SAMSUNG? Because when I select Reboot to Bootloader option in Anroid Recovery the phone does go into Fastboot Mode but apparently Fastboot seems
disabled by Samsung because from the PC it does not recognise the Fastboot Devices. So,
as a noob if I've understood whats mentioned in the link you provided is that Samsung didnt
provide the Native Samsung Fastboot Drivers for the Galaxy M21 2021 DELIBERATELY? So,
the link you provided will help me install the required Fastboot Drivers? & then I can flash
TWRP.img or Magisk.img?
Thanks in advance
Click to expand...
Click to collapse
jwoegerbauer said:
To root Android a Custom Recovery isn't required at all.
Click to expand...
Click to collapse
Followup 1:
Hi, I tried your ADB-FASTBOOT-Installer but it doesnt seem to go beyond "Waiting for devices" screen.
1> I tried installing magisk v.19.3.zip (renamed to just "OTA") using command (adb sideload OTA)
first error i got was (adb: failed to read command: No error)
2> second time i tried installing from another folder belonging to 15-seconds-adb and it showed [ (0.01x) success ] something like that
3> I installed magisk manager 2021.4.9 Magisk v22.1 by Package Installer method not sideload method. When i rebooted & checked magisk manager it wasnt rooted so I tried boot.img patch method and got error: unable to unpack boot.img
I have attched some screenshots of the errors but what I understand from this is that the new Samsung devices might have img files written in some new format i guess because why else would magisk manager fail to unpack and patch a boot.img file, ususally it does fine.
I have also attached a copy of the device stock boot image file (hope i'm not breaking some xda rules here about posting img files , i just joined yesterday so )
Maybe its of some help to some Dev who might need these to find a workable solution.
The stock firmware I downloaded is flashing well on the device (SM-M215G/DS), the link is here- https://samfrew.com/download/Galaxy__M21__2021__Edition__/lOg2/INS/M215GDDU1AUG2/M215GODM1AUF3/
Also Magisk isn't needed to root a phone's Android: that's a widespread misconception,1000 times reported on the Internet and also here on XDA .
jwoegerbauer said:
Also Magisk isn't needed to root a phone's Android: that's a widespread misconception,1000 times reported on the Internet and also here on XDA .
Click to expand...
Click to collapse
Well what necessarily needed for rooting an android phone is just modifying some files in /system? I have seen the phrase 'toybox 0.8.5' a multiple times in your posts, not sure what is that.
LR7875 said:
Well what necessarily needed for rooting an android phone is just modifying some files in /system? I have seen the phrase 'toybox 0.8.5' a multiple times in your posts, not sure what is that.
Click to expand...
Click to collapse
Toybox is a replacement for many Linux command-line utilities that is targeted at embedded systems - similar to BusyBox. It was created by Rob Landley, who is also a former BusyBox maintainer. Toybox is merged into any Android starting with version 6.
jwoegerbauer said:
Toybox is a replacement for many Linux command-line utilities that is targeted at embedded systems - similar to BusyBox. It was created by Rob Landley, who is also a former BusyBox maintainer. Toybox is merged into any Android starting with version 6.
Click to expand...
Click to collapse
Oh learned something more.
Well what is the definition of root then?
LR7875 said:
Oh learned something more.
Well what is the definition of root then?
Click to expand...
Click to collapse
Sorry to barge in LR7875, to my knowledge (I have rooted & installed Roms on some older Samsung/Redmi/Laptops etc.) rooting is the process through which we gain Admin Rights / Super User on Linux devices. Correct me if I'm wrong. Im not a programmer by any means so.
jwoegerbauer said:
Also Magisk isn't needed to root a phone's Android: that's a widespread misconception,1000 times reported on the Internet and also here on XDA .
Click to expand...
Click to collapse
Hi there jwoegerbauer, thanks for responding. If im not being bothersome , I'll need to stalk you on XDA for some help on this issue of rooting this device, if it s okay with you . Pray tell me what else other than magisk could root this stubborn Samsung model ? Im getting some good offers for this device on the local online market but i really didnt want to sell it off just wanted to root & install roms like before.. Other than magisk I just know of SuperSU by chainfire which I think stopped working well post android 8 oreo but will it work for Android 11? No way any changes to /system/Priv-app and the phones factory reset themselves. One-Click Root only takes calls & they charge $50 for rooting, but whats the guarantee if we pay up that theyll root it properly & taht too it would be just root not Recovery or ROMs. I'm lost.
Installing Magisk DOESN'T ROOT Android. Installing SuperSU DOESN'T ROOT Android. POV.
To have said it:
Magisk is successor to XPosed, means a software framework what once get added to Android allows you to systemless apply modules, means some functionalities modders are missing on standard Android. The crux with Magisk is it patches device's bootloader.
SuperSU simply is a per-app root-access management tool, nothing else: it requires Android got rooted.
OldNoobOne said:
...
The stock firmware I downloaded is flashing well on the device (SM-M215G/DS), the link is here- https://samfrew.com/download/Galaxy__M21__2021__Edition__/lOg2/INS/M215GDDU1AUG2/M215GODM1AUF3/
Click to expand...
Click to collapse
How are you "flashing"?
Why do you say it "is flashing well"?
As far as I know, you need to use Odin (on a PC) to "flash" a Samsung device. Samsung does not support fastboot -- no amount of updating drivers on your PC will make a Samsung device start supporting fastboot.
Magisk is much more than just a way to root, but a side effect of installing Magisk is that you will be rooted.
If you have installed the Magisk Manager app and tried to patch the AP.tar of the stock firmware, and you are getting an error, you should look through the main Magisk thread, and maybe ask there.
J.Michael said:
Magisk is much more than just a way to root, but a side effect of installing Magisk is that you will be rooted.
Click to expand...
Click to collapse
IMO you're WRONG: Magisk DOESN'T ROOT Android, but you additionally can install MagiskSU app what grants elevated rights ( AKA SU ) to Magisk.
jwoegerbauer said:
Magisk is successor to XPosed, means a software framework what once get added to Android allows you to systemless apply modules, means some functionalities modders are missing on standard Android. The crux with Magisk is it patches device's bootloader.
Click to expand...
Click to collapse
I need to hop on and correct a few details here...
Magisk is not a successor to Xposed. That's like comparing apples and oranges. If you want to know how Magisk came to be John has written about that in a couple of places, here for example:
Spoiler
https://www.reddit.com/r/Android/comments/7oem7o
And Magisk does not patch the bootloader, but the ramdisk which can be found in either the boot or recovery image depending on your device. Details about that here:
https://topjohnwu.github.io/Magisk/boot.html
OldNoobOne said:
Sorry to barge in LR7875, to my knowledge (I have rooted & installed Roms on some older Samsung/Redmi/Laptops etc.) rooting is the process through which we gain Admin Rights / Super User on Linux devices. Correct me if I'm wrong. Im not a programmer by any means so.
Click to expand...
Click to collapse
Oh I see, it is used to do something that are restricted originally, e.g. access system files, delete system apps, etc.
Didgeridoohan said:
I need to hop on and correct a few details here...
And Magisk does not patch the bootloader, but the ramdisk which can be found in either the boot or recovery image depending on your device.
Click to expand...
Click to collapse
Correct: it should also have been called boot.img instead of bootloader. Sorry for this.
LR7875 said:
Oh I see, it is used to do something that are restricted originally, e.g. access system files, delete system apps, etc.
Click to expand...
Click to collapse
True . Don't quote me, (In a nut shell ) up from Andoid 9 (Pie) modification to /system /app etc. is difficult per my knowledge, thats why probably magisk sits in the boot partition, no one dare touches the system partition anymore while the gadget is ON. Only Gugle stays in the system partition im sure. The Custom Recoveries do wipe the device but are unable to erase the core andoid OS inside . Even 'Fastboot Erase' command cant get andoid out completely (exception Linux-phones i think). So practically Andoid devices are just gadgets that are 'leased' to the so-called 'owner' of the device (without explicitly mentioning the term 'leased' by gugle). The cost of the smart-gadget is practically the 'Down Payment' we pay to Gugle & OEMs then the rest of the revenue they make from Ads etc. which goes as 'Rent/lease payment' to them ultimaately & we never get to own the devices we purchase EVER! .
My sixth-sense says The chinese OEMs allowing Fastboot Mode only for now but only to make inroads into the smart-gadget market, once they have made everyones profile Gugle & pentgon might just make the softwares on these smart-gadgets wholly tamper-proof & focus more on 'managing' or keeping an eye on their 'subjects' [given that the whole gugle business,- 'search-engine', 'smart-device' etc. started officially in 2004 which was POST the 9.11 ATTACK].
So they're probably maintaining the Big-Data on everyone who uses their devices & 2014 is when data-warehousing became the need if i remember correctly; so, it was all about compressing the Big-data gathered & then Analytecs took the spotlight by 2016-17 coz they needed to analyize all the data collected & remove the junk from it then home in on pentgons targets. It's Obvious . No wonder they're pushing PX-Xperience ROMs through the ROM channels to cover the gap created by chinese OEMs eating into their market share. Why else do they charge other OEMs $2 for OTG-support while Shamshung (and now MYUI) already had native OTG-support on their devices shipped? so that's what Sekure-folder all about, YOUR DATA LOADED & LOCKED real-time then SHIPPED back to Gugle-Analytecs. Obvious.
Well so root is basically... Removing those ads and trackware up to the bare bones of the phone, to ensure all your data isn't used to make the spammy advertisements?
Android is nothing else then a derivated Linux. In the world of Linux the Root User is the user that has all rights esp. accessing / modifying system files, it's comparable to the Administrator in the world of Windows.
In the world of Linux this Root User typically is called superuser ( commonly abbreviated: SU ). In the world of Android such a superuser isn't in general implemented by default: it must get added to Android by modding it, means adding a SU ( read: Switch User ) binary - in whatever form - to Android what is systemwide accessible. In the world of Android an user root exists what is the user with user ID 0.
[ deleted ]
how do i get the samsung screen recorder and secure folder on my a226b and or any other samsung ad i dont have them for some reason and i would like to know if theres any universal twrp or odin thing to flash that would gove them back or maybe secret setting to enable or apk to install
Win_7 said:
how do i get the samsung screen recorder and secure folder on my a226b and or any other samsung ad i dont have them for some reason and i would like to know if theres any universal twrp or odin thing to flash that would gove them back or maybe secret setting to enable or apk to install
Click to expand...
Click to collapse
There Isn't a screen recorder or secure folder on the SM-A226B you can use calculator+ and flash a android 13 GSI to use the screen recorder.
You can enable screenrecorder by modifiying some lines in /system/etc/floating_feature.xml
<SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>TRUE</SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>
<SEC_FLOATING_FEATURE_FRAMEWORK_CONFIG_SCREEN_RECORDER_ITEM>-pip</SEC_FLOATING_FEATURE_FRAMEWORK_CONFIG_SCREEN_RECORDER_ITEM>
Without spaces. If there is already the value simply change to this. I'm working on a way to enable secure folder in my free time. First tests were successful however there are still some problems. I'm extracting files from A13 5G (SM-A136B) because it has the same chipset as A22 5G and has secure folder
fede2782 said:
You can enable screenrecorder by modifiying some lines in /system/etc/floating_feature.xml
<SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>TRUE</SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>
<SEC_FLOATING_FEATURE_FRAMEWORK_CONFIG_SCREEN_RECORDER_ITEM>-pip</SEC_FLOATING_FEATURE_FRAMEWORK_CONFIG_SCREEN_RECORDER_ITEM>
Without spaces. If there is already the value simply change to this. I'm working on a way to enable secure folder in my free time. First tests were successful however there are still some problems. I'm extracting files from A13 5G (SM-A136B) because it has the same chipset as A22 5G and has secure folder
Click to expand...
Click to collapse
thanks!!!! will this work on any other phone other than a226b?
and do you know of any file manager app that can actually edit system files (i have a good one called filemanager+ but it can only read even if i do mount -o remount,rw /
Yes, it should. If this doesn't work there is another line that may need to be changed. Make sure you have at least one ui 3. Updating Samsung Capture may be required (https://www.apkmirror.com/apk/samsu.../samsung-capture-5-4-22-android-apk-download/) Let me know.
I do not know any good file manager because I modify system files with Magisk. You can use termux. Pull file to pc or use quick edit on phone.
fede2782 said:
Yes, it should. If this doesn't work there is another line that may need to be changed. Make sure you have at least one ui 3. Updating Samsung Capture may be required (Here's where you can download latest apk) Let me know.
I do not know any good file manager because I modify system files with Magisk. You can use termux. Pull file to pc or use quick edit on phone.
Click to expand...
Click to collapse
eh thats ok i used adb and accepted root on device
my phone didnt have the file is that ok if i just create it?
also you made a mistake on the url can you send a working one?
fede2782 said:
Yes, it should. If this doesn't work there is another line that may need to be changed. Make sure you have at least one ui 3. Updating Samsung Capture may be required (Here's where you can download latest apk) Let me know.
I do not know any good file manager because I modify system files with Magisk. You can use termux. Pull file to pc or use quick edit on phone.
Click to expand...
Click to collapse
um how can i fix "system partition doesnt have enough free space" when trying to convert newer samsung capture to system app
You don't need to convert. Just update with apk when phone on. Like every app. I made a mistake in the link. I fixed it. The file should exist on every Samsung one ui device.
fede2782 said:
You don't need to convert. Just update with apk when phone on. Like every app. I made a mistake in the link. I fixed it. The file should exist on every Samsung one ui device.
Click to expand...
Click to collapse
oh bruh i deleted system app and reinstalled
An apk of Samsung capture must remain in the /system partition in order to get priv-app permissions
I recommend you to reinstall original firmware (One UI 5.1 if it is available in your region) then modify floating_feature.xml.
This file is placed in every samsung device in /system/etc/floating_feature.xml
You do not have to create nothing. Just modify it add that lines. In my firmware (official one UI 5.1) the second line is already placed in the file. So I simply added:
<SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>TRUE</SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>
in the middle of the file
fede2782 said:
An apk of Samsung capture must remain in the /system partition in order to get priv-app permissions
I recommend you to reinstall original firmware (One UI 5.1 if it is available in your region) then modify floating_feature.xml.
This file is placed in every samsung device in /system/etc/floating_feature.xml
You do not have to create nothing. Just modify it add that lines. In my firmware (official one UI 5.1) the second line is already placed in the file. So I simply added:
<SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>TRUE</SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>
in the middle of the file
Click to expand...
Click to collapse
i still didnt have the file i made it and updated capture but didnt get screen recorder even after reboot :/ am on android 11 and im not updating especially as theres bootloader update
For me it is working. The file floating_feature.xml needs to exist. if it doesn't exist this means your firmware version is old and it doesn't have modern one UI. I don't know how I can help you more
fede2782 said:
For me it is working. The file floating_feature.xml needs to exist. if it doesn't exist this means your firmware version is old and it doesn't have modern one UI. I don't know how I can help you more
Click to expand...
Click to collapse
i have a70 with screenrecorder its on android 10
my a22 is on oneui 3.1
I don't know.
fede2782 said:
I don't know.
Click to expand...
Click to collapse
alright then sorry for bothgering you
Win_7 said:
alright then sorry for bothgering you
Click to expand...
Click to collapse
Don't worry
Image clipper wip being prepared! Object Eraser! deCorizer - Add missing One UI features to A22 5G
You can flash this Magisk module AT YOUR OWN RISK. I AM NOT RESPONSIBLE for lost warranty, bootloops, lost data or any other damage to your device. THE SOFTWARE IS PROVIDED “AS IS” This module tries to add as many One UI features as possible to...
forum.xda-developers.com
fede2782 said:
Image clipper wip being prepared! Object Eraser! deCorizer - Add missing One UI features to A22 5G
You can flash this Magisk module AT YOUR OWN RISK. I AM NOT RESPONSIBLE for lost warranty, bootloops, lost data or any other damage to your device. THE SOFTWARE IS PROVIDED “AS IS” This module tries to add as many One UI features as possible to...
forum.xda-developers.com
Click to expand...
Click to collapse
it didnt work
it just said system is root and a couple other things then i rebooted nthing
Win_7 said:
it didnt work
it just said system is root and a couple other things then i rebooted nthing
Click to expand...
Click to collapse
At the moment is only for DWC1 OXM
I'll try to download your file from AVA1 as soon as I can and I'll patch it
fede2782 said:
At the moment is only for DWC1 OXM
I'll try to download your file from AVA1 as soon as I can and I'll patch it
Click to expand...
Click to collapse
i have AVA6 not 1