Use Magisk to boot to recoveryI have flashed twrp to my phone via odin and can not enter into twrp afterwards with button combo.
Use Magisk to boot to recoveryI have flashed twrp to my phone via odin and can not enter into twrp afterwards with button combo.
Thank you. I found a detailed guide on this russian forum (https://4pda.to/forum/index.php?showtopic=1027599&view=findpost&p=109398039) and eventually manage to obtain root.if you have your firmware for your phone sitting on your PC this version of 7zip can open both .tar archives and .LZ4 archives
that means you can go the slightly less painful route to patch with magisk by extracting the boot.lz4 from the AP archive and extracting the boot.img after that.Releases · mcmilk/7-Zip-zstd
7-Zip with support for Brotli, Fast-LZMA2, Lizard, LZ4, LZ5 and Zstandard - mcmilk/7-Zip-zstdgithub.com
use magisk to patch just the boot.img on your phone and then flash the patched version with TWRP to the boot partition.
Who did you see writing in Russian here? and you want an answer!Я так понимаю никто не может починить TWRP что бы видеть sd карту?
I understand that no one can fix TWRP to see the sd card?Who did you see writing in Russian here? and you want an answer!
don't write in Russian anymore because no one bothers to translate what you want ...
not so far, no.
if you use a good file browser on your phone that can open tar files, you can extract the recovery.img file from inside and flash that in TWRP as an image. use reboot to recovery and look for the version change
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:* Your warranty is now void. * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or your getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this ROM * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at me for messing up your device, I will laugh at you.
Supported Models:
Galaxy S20 FE 5G G7810, G781B, G781N, G781U, G781U1, G981W and G780G (4G).
US/Canada bootloader unlock thread:
here
Download & Guide:
1. Unlock your bootloader.
2. Download S20 FE 5G: r8q.
3. Reboot to download mode and flash vbmeta_disabled.tar in AP slot and reboot. Device will reboot to stock recovery mode prompting you to wipe data so wipe data and reboot to download mode again.
4. Put the TWRP tar for your device with Odin in the AP slot and click start.
5. Reboot to recovery via recovery key combo.
6. Disable encryption:
- Flash multidisabler-samsung-3.x.zip.Or:
- Go to Advanced > Terminal, type:multidisabler
.If vendor complain about free space left on device, will attempt to resize vendor. and it ask to- Run multidisabler again!
.- Type:7. Go back to Wipe > Format Data > typemultidisabler
again. will see- Finished.
when done.yes
.
8. Reboot to recovery.
9. Flash magisk apk in twrp.
10. Reboot to system, Enjoy.
Note:
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram group
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@ooobs007 for testing on S20 FE 5G G781B
ianmacd for multidisabler
Sources:
Kernel tree
Device tree
yesDoes twrp-3.6.0_11-6_afaneh92-r8q.tar support SM-G780G (4G) Model?
Connect to internet, kg status must be checkingThanks man, btw I'm getting this error message: "only official released binaries are allowed to be flashed(vbmeta)". Bootloader was already unlocked through Developer Options.
if you use a good file browser on your phone that can open tar files, you can extract the recovery.img file from inside and flash that in TWRP as an image. use reboot to recovery and look for the version change
Please can you update to latest kernel sourceChangelog:
29.11.2021 - Update to TWRP 3.6.0
- Add Symlinked dynamic partitions to fstab
- Updated to latest kernel source
- Update multidisabler
- fstab clean up
- Fix haptic feedback
23.05.2021 - Update to latest TWRP source, update kernel to G781BXXU3CUD6.
03.03.2021 - Update to latest TWRP source, Add terminal multidisabler script. fstab cleanup.
22.01.2020 - Fix USB-OTG for Q & R builds.
15.01.2020 - Initial build for Android 11
31.12.2020 - Update TWRP to 3.5.0
15.11.2020 - Add TWRP fastbootd support, Move kernel to gz format.
11.11.2020 - Initial Release.
Mounting /system_root...
Attempt Faileed. Mounting at /system_root...
mount: '/dev/block/dm-0'->'/system_root': Invalid argument
Even that attempt failed. Aborting...
use my instructionsHas anyone else encountered issues when flashing the multidisabler file? I am experiencing this issue below:
Code:Mounting /system_root... Attempt Faileed. Mounting at /system_root... mount: '/dev/block/dm-0'->'/system_root': Invalid argument Even that attempt failed. Aborting...
I have unlocked my bootloader successfully as it says OEM Lock: OFF (U), and I have the G7810 Model. Flashing CleanOS just gives me a bootloop and I can't boot to my OS. TWRP warns me that "No OS is installed" whenever I select reboot to recovery or system.
Any help is appreciated, thank you.
Hello, I am encountering the issue "Only Official released binaries are allowed to be flashed(vbmeta)" when I try to flash it in ODIN.
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
multidisabler
. - Run multidisabler again!
.multidisabler
again. will see - Finished.
when done.yes
.To disable encryption manually:
You need to replace fileencryption=ice with encryptable=ice only in userdata line (maybe rest lines) in vendor/etc/fstab.qcom
To avoid stock recovery restoration manually:
Rename system/recovery-from-boot.p to recovery-from-boot.p.bak
I will start working on the new kernel source soon.@afaneh92 just checking in to ask what if any sources to you want / need to help you ?
I'm on the Samsung open source site now and downloading a zip for G781BXXU2CUD1 but I've no idea if it's kernel sources inside (280mbs ish). another page I saw here mentioned using the inquiry tab to submit a request.
if you can tell me exactly what you want I'll more than happily put in a request for it, I'm sure others would too.
I'll edit this later and add the zip files full name that I've downloaded and if you want that I'll put it mediafire or similar.
SM-G781B_SEA_RR_Opensource.zip is the archive name, taken from clicking on G781BXXU2CUD1 which matches my current baseband and buildnumberView attachment 5299763
New build is up.
Note: steps 2-6 are important, missing any will lose your data.Hi everybody,
Sorry in advance for this noob question.
Starting from stock Android12, I went thru all @afaneh92 process and it's working nicely.
Now I'd like to upgrade to Androi13: do I have to rerun exactly all the process (& so loosing my data)?
In other words: are BL unlock and avb disable persistent after an Odin flash ?
Thank you for sharing your skills !