Does anyone know where I can get the BL, CL, and CSC ?
For some devices in the official supported list, obtain adb-root access on stock system is needed to install TWRP using the “dd” way. (https://doc.e.foundation/devices/d802/install)
But you are right, magisk is not mentionned in /e/'s documentation,
but magisk is mentionned in some TWRP’s documentation. (https://twrp.me/samsung/samsunggalaxys10plus.html)
.
https://rootmygalaxy.net/how-to-install-magisk-without-twrp-in-2021/
1 Like
Thank you for providing that link to How to Install Magisk without TWRP in 2022 - Rootmygalaxy.net. I followed it up to
- Instructions was to ‘Load BL file, CP file, and HOME_CSC file from the extracted firmware to BL tab, CP tab, CSC tab.’
- e1.4 zip does not have BL, or HOME_CSC file. It only has boot.img which I used 7zip to convert to boot.tar to upload to phone to be patched by Magisk and then transfer to pc to upload to Odin as the AP file.
*Once I uploaded only the AP file (magisk patched.tar file) I clicked Start button.
*Odin’s log show it being stuck at SetupConnection…
*I did use the latest version of Odin v3.13.3
What do I do to fix being stuck at SetupConnection? Do I need the BL, CP, CSC file that e1.4 zip does not have to continue?
This should happen if you go to Settings > System updates > top right 3 dot menu > Preferences > Update recovery.
The position of this toggle changes with Android version.
When update recovery is selected, we expect TWRP to be replaced by the /e/ Recovery to match the /e/ version being installed as the /e/ OS update happens.
If you originally used Easy Installer, you are likely to be on a stable build (reference: https://doc.e.foundation/build-status). You should avoid lightly changing from Stable to dev channel (or vice versa).
On Android 10, this can be confirmed from
Settings > About phone > Android version > /e/ OS version – Long press on /e/ OS version to copy to clipboard.
Thanks for the suggestion. I have replaced TWRP with e.14 recovery already. Now I am hoping someone can help me install Magisk without TWRP if that is possible for S9+.
S9+: Unable to update to eos1.4 due to TWRP will not Decrypt Data - #13 by piero
.
Why not install TWRP after each /e/ update to flash the patched-boot and then replace it by recovery-e before each /e/ update ?
OR simply keep TWRP and just “dirty flash” latest e-build over the precedant instead of perform OTA update ?
which TWRP version do you recommend that does not have data decryption issues with the S9+?
Maybe None,
it is the reason why it was (provisoiry ?) abandonned.
can I still use twrp (even though it does not decrypt data) with s9+ to install Magisk or another recovery like Shrp?
Yes, you have already did it in the past, before opening this topic… no ?
Only actual Problem with TWRP is OTA update using the system updater, because it will store the file under “/data/lineageos_updates” and TWRP can’t uncrypt “/data”
No problem if you download the latest /e/.zip file and flash it using the “sideload way”.
that’s true. I did have twrp (that did not decrypt) that also installed Magisk but when I installed e1.4 os it wiped Magisk and twrp off. I was just wondering if there was an easier way to install Magisk without TWRP but I guess you are implying there is not an easier way. If there are future eos updates, do I reinstall TWRP again in order to get Magisk every time?
Thanks. How do you do a dirty flash?
Download the latest /e/.zip file, reboot into TWRP, tap to install, navigate to the downloaded /e/.zip file …
WITHOUT WIPING ANYTHING is a dirty-flash
If it don’t work because “/data” can’t be uncrypted, use the “sideload method”
when I did that last time to install e1.4 to update, it automatically replaced TWRP with e1.4 recovery. Did I do something wrong? I don’t think I wipe anything.
Not If you unselect this feature.
Under Settings, System updates, there is
Auto updates check (never, once a day, once a week, once a month)
Delete updates when installed
Mobile data warning
I do not see Update recovery.
I do not have the Update Recovery feature
As @aibd often advise, “sleep on it”…
And Re-read the entire thread
Perhaps it is because you are on stable build, perhaps it is because recovery-e is actually installed …