No, no need to flash a later version until you upgrade your firmware.Thanks a lot for the fixed version! :good:
Should I flash v2.5 now, even though I didn't experience any problems with v2.3 yet? Will there be anything better or more stable with v2.5? Please advise.
[Pie/10] [System-as-root] Multidisabler: encryption, Vaultkeeper, proca, etc.
- Thread starter ianmacd
- Start date
Version 2.6 released.
Change log
v2.6 (2020-10-05)
Change log
v2.6 (2020-10-05)
- Add support for the North American Z Fold2 5G (F916U/U1).
- Add support for the A71 (A715F).
- Add support for the Note10 Lite (N770F).
A70 compatibility
I have successfully installed the multidisabler with root and TWRP on my A70 (model A705YN, modified script to accept any A70) after a few hours experimenting with a reformat and various things, and it seems to be good so far so it might be able to be added onto the compatible list. However, there may be issues I haven't encountered yet so fair warning to anyone else that wants to try it on an A70. I had a boot loop problem when trying to boot rooted for awhile, but it was related to Magisk and my boot partition rather than the disabler. I'll give a brief overview of how I got it to work anyway.
0. Move/backup any essential data from internal storage to sdcard (or elsewhere)
1. Extract AP file from latest firmware (BTH4 in my case) and use Magisk to patch it.
2. Extract boot.img from the AP tar, make a backup copy in case needed, and create a patched version with Magisk.
3. Replace vbmeta.img file in AP.tar with the version from the A70 TWRP thread.
4. Use Magisk to patch the latest TWRP recovery.img file from above thread (latest is v3.3.1.7 at time of this writing), use Tar to convert it to .tar.
5. Copy patched/tar'd TWRP recovery.tar and stock boot.img files onto SD card.
6. Install patched AP.tar file via Odin, also using stock BL, CP, and CSC files. (this will erase data partition and give you root)
7. Reboot phone, skip all setup stuff, go to settings and disable strong encryption (not sure if this is necessary but it seems to help)
8. Reboot to (stock) Recovery mode, factory reset to format data partition again to remove FBE.
9. Reboot to Download mode, use Odin to flash patched TWRP recovery.img.tar onto AP.
10. Reboot to (TWRP) Recovery mode, install stock patched boot.img to Boot partition.
11. Install Multidisabler (modified to accept A70 until included in official update), format data partition again.
12. Reboot System, now setup should work and encryption should be disabled.
I might have some of the above wrong or done some steps unnecessarily, because most of the time I spent on this was trial and error to fix a boot loop problem and I only started to write it all down once I was satisfied the phone is now working normally again. I'm not actually sure why the Magisk patched AP file didn't seem to create a working boot.img and install it properly, because from what I can tell the one manually installed from TWRP should be the exact same file. Might be some sort of checksum error in Odin that I didn't read properly and causing it to not write the boot image at all.
To modify the script to accept A70 as a compatible device, I just added "A70|" to the start of device-checking lines after the greps. I'm not sure if it was sensible to let the script disable anything and everything that it does on my phone, but this was an experiment for me while I had the time and opportunity to reformat my phone on any fails, so it didn't bother me if I broke anything important by disabling it all.
I'm also operating off my memory of the steps I did above, so apologies for any errors that might set fire to your house or something similar. All care taken but no responsibility, etc. If there are any glaring errors though, please let me know asap and I will update the steps accordingly.
I have successfully installed the multidisabler with root and TWRP on my A70 (model A705YN, modified script to accept any A70) after a few hours experimenting with a reformat and various things, and it seems to be good so far so it might be able to be added onto the compatible list. However, there may be issues I haven't encountered yet so fair warning to anyone else that wants to try it on an A70. I had a boot loop problem when trying to boot rooted for awhile, but it was related to Magisk and my boot partition rather than the disabler. I'll give a brief overview of how I got it to work anyway.
0. Move/backup any essential data from internal storage to sdcard (or elsewhere)
1. Extract AP file from latest firmware (BTH4 in my case) and use Magisk to patch it.
2. Extract boot.img from the AP tar, make a backup copy in case needed, and create a patched version with Magisk.
3. Replace vbmeta.img file in AP.tar with the version from the A70 TWRP thread.
4. Use Magisk to patch the latest TWRP recovery.img file from above thread (latest is v3.3.1.7 at time of this writing), use Tar to convert it to .tar.
5. Copy patched/tar'd TWRP recovery.tar and stock boot.img files onto SD card.
6. Install patched AP.tar file via Odin, also using stock BL, CP, and CSC files. (this will erase data partition and give you root)
7. Reboot phone, skip all setup stuff, go to settings and disable strong encryption (not sure if this is necessary but it seems to help)
8. Reboot to (stock) Recovery mode, factory reset to format data partition again to remove FBE.
9. Reboot to Download mode, use Odin to flash patched TWRP recovery.img.tar onto AP.
10. Reboot to (TWRP) Recovery mode, install stock patched boot.img to Boot partition.
11. Install Multidisabler (modified to accept A70 until included in official update), format data partition again.
12. Reboot System, now setup should work and encryption should be disabled.
I might have some of the above wrong or done some steps unnecessarily, because most of the time I spent on this was trial and error to fix a boot loop problem and I only started to write it all down once I was satisfied the phone is now working normally again. I'm not actually sure why the Magisk patched AP file didn't seem to create a working boot.img and install it properly, because from what I can tell the one manually installed from TWRP should be the exact same file. Might be some sort of checksum error in Odin that I didn't read properly and causing it to not write the boot image at all.
To modify the script to accept A70 as a compatible device, I just added "A70|" to the start of device-checking lines after the greps. I'm not sure if it was sensible to let the script disable anything and everything that it does on my phone, but this was an experiment for me while I had the time and opportunity to reformat my phone on any fails, so it didn't bother me if I broke anything important by disabling it all.
I'm also operating off my memory of the steps I did above, so apologies for any errors that might set fire to your house or something similar. All care taken but no responsibility, etc. If there are any glaring errors though, please let me know asap and I will update the steps accordingly.
after install 2.5 on 2.3 worked good maybe one week
but today i put my frend's SD card and phone didnt saw it.
i try to reboot with it, but
forget to press keys and boot in normal mode w/o root.
after i reboot again with root..and i boot in system 2sec and auto reboot..as was with 2.4
so it works good when boot without root...so i really dont know whats happen...flash 2.6 dont helps, also flash 2.3 too...
maybe it happens only with me but i really dont know the reason :crying:
UI2.5 S10e exy
but today i put my frend's SD card and phone didnt saw it.
i try to reboot with it, but
forget to press keys and boot in normal mode w/o root.
after i reboot again with root..and i boot in system 2sec and auto reboot..as was with 2.4
so it works good when boot without root...so i really dont know whats happen...flash 2.6 dont helps, also flash 2.3 too...
maybe it happens only with me but i really dont know the reason :crying:
UI2.5 S10e exy
Last edited:
Hello, Sir Can You Please Make one for A30s. Please. Requet
---------- Post added at 10:25 PM ---------- Previous post was at 10:24 PM ----------
Hello, Sir Can You Please Make one for A30s. Please. Request
---------- Post added at 10:25 PM ---------- Previous post was at 10:24 PM ----------
Hello, Sir Can You Please Make one for A30s. Please. Request
@ianmacd, is there any chance you can add support for the Galaxy Tab A 8.0 (2019) [SM-T290]?
(ro.boot.bootloader = T290XXU3BTG1)
(ro.boot.bootloader = T290XXU3BTG1)
im again face on the problem i wrote before
and today i just find out what is the problem
the problem comes when you change lockscreen to "pattern" and do "restart" pnone.
so even if you backup your data it not helps.
when you back it, the problem back with it.
how to see the problem.
1. go to TWRP - format data to be shure any another apps not affect
2. load system with root and skip all settings, set lock screen skiped, so it will be set on "swipe"
2.1 if you not setup "pattern" now or later there is no problem!
but if you setup it from first setup or later...so it is a triger
2.2. if you not setup it so go into setting, and change lock screen in "pattern"
4. use "restart" button to restart phone.
5. wait system loads without root.
6. power off phone by any method, its not nessesery anymore.
7. try to load with root...and
if you input your pattern it just back you on lock and not go in system.
but if you load again without root it loads ok
if back "pattern" on any "swipe" or "no" and try root again
it just going into bootloop after 10sec....
so something broke and do conflict with root when you set "pattern" and restart with restart button.
so one day when you forget to press keys to boot with root
or for some reason if you need to do one login without root you lost everything without way to back it....
when i install first time i use same files but v2.3 and i use "restart" button for load without root,and get no problems.
what i missing now? is it v2.6 problem// or what?
if there is any solution please help me..becouse i so tired and dont wanna setup all for 3 time....
hello I have a problem when I restart my phone the system does not start anymore it remains on the written galaxy note 10+ and keeps restarting why does it do so? how can i solve?
@ianmacd
I was trying to find an accurate answer, but it's a very long thread and I may have missed it.
I am using a rooted (Magisk) stock Android 10 rom on Galaxy Note 10 Plus (N975F, exynos). I have patched it with your excellent multidisabler too of course. It works well unencrypted.
I would like to get FBE or FDE encryption on it. Is there any way to do it without losing my data? If so, how?
Thank you
I was trying to find an accurate answer, but it's a very long thread and I may have missed it.
I am using a rooted (Magisk) stock Android 10 rom on Galaxy Note 10 Plus (N975F, exynos). I have patched it with your excellent multidisabler too of course. It works well unencrypted.
I would like to get FBE or FDE encryption on it. Is there any way to do it without losing my data? If so, how?
Thank you
Yes, if you edit the fstab, swap the commented out userdata entry for the active one, and reboot, the device will re-encrypt itself.
You will, however, lose access to /data from TWRP in the process. TWRP needs (the content of) /data to be unencrypted in order to read it.
Thanks.
Doesn't TWRP supposed to prompt for the PIN in order to decrypt /data when launching recovery?
Doesn't TWRP supposed to prompt for the PIN in order to decrypt /data when launching recovery?
No, TWRP cannot decrypt Samsung's proprietary encryption on Exynos devices.
hi, how about my bagreport upper?
please answer. cuz now im waiting on system without any protect on lock screen, cuz if i setup pattern i lost root again...its not good.
i on S10e Andr10 UI2.5
Wow, that's a serious deal breaker...
What about Samsung devices with Snapdragon?
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone