If your devuce wont boot after installing a module dont panic safe mode can unbrick you without pc adb twrp or data loss
1 hold down power and volume down while connected to charger when the animation appears unplug charger and device will shut itself down
2.turn device on and hold down volume down button untill device boots with safe mode watermark then release
3.reboot device .you will boot with all module disabled
4.go to magisk app remove the offending module(s) enable magisk hide enable all other modules and reboot
And there you are unbricked without losing your userdata
Related
Crash Recovery for the Samsung Galaxy A20
1. Be Prepared
Most of us will suffer from a crash at some time. If you know how to fix it, you will have a lot less stress.
There are certain files you need to keep in readiness.
Always backup boot, data, system before you try any new ROM.
A. On your PC
- Firmware you downloaded from one of these sites
https://samfrew.com or https://www.samfirmware.net
or for a faster download: https://forum.xda-developers.com/galaxy-a20/how-to/a20-repair-firmware-t4066551
- recovery.tar you can download from here https://forum.xda-developers.com/galaxy-a20/how-to/guide-quick-root-twrp-galaxy-a20-t4069423
B. On your A20 external sd
Don't keep any important files on your internal sd card. Keep backups on the external sd and on usb otg.
- Boot, data, system backup
- Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
or this one
View attachment 4975463
To go to download mode
Normal method
1. Turn off phone
2. Hold down both volume keys
3. Plug in computer
Bootlooping
1. Plug in to computer
2. Hold down both volume keys
For a difficult phone
1. Connect usb to computer but not to phone
2. Hold down all 3 keys
3. When it buzzes release power and quickly plug in usb to phone.
It might take a few times to get it right.
If it's REALLY BAD
1. Wait for the battery to completely run down and use normal method.
2. Soft Crash
This is when you get a bootloop.
Recover method
1. Reboot into TWRP( hold down all 3 keys and release vol down when it reboots)
2. Restore your backup.
3. Hard Crash
This is when you get red text along the top.
Recover method
1. Connect phone cord to PC
2. Reboot into download mode (Hold down all 3 keys
When the phone reboot release power key and plug in to computer at the same time
It may take a few times to get the timing right)
3. Flash each part of the firmware into its slot.
BL_20xxxxxxx.tar.md5 goes into the BL slot
AP_20xxxxxxx.tar.md5 goes into the AP slot
CP_20xxxxxxx.tar.md5 goes into the CP slot
HOME_CSC_xxxxxx.tar.md5 goes into the CSC slot
4. You might do a Factory data reset
5. Wait for the restart
6. Skip through a minimal setup
7. Activate developer mode
8. Allow usb debugging
9. Reboot into download mode
10. Flash recovery.tar in the AP slot
11. Reboot the A20 into TWRP and mount everything that you can.
12. Format Data (not just wipe) - don't restart
13. Flash Disable_Dm-Verity_ForceEncrypt
14. Wipe both caches then go back and Reboot into Recovery.
15. Restore your data backup.
16. Reboot
physwizz collection
A collection of guides, kernels and ROMs. Guides Complete Guide to the A20 GSIs for the A20 Quick Root and TWRP for the A20 Making my First Kernel for the A20 A20 Rooting Guide Making Your Own ROM Making Your Own Version of QwizzROM-a20...
forum.xda-developers.com
If anyone finds a better way to do this, please let me know.
physwizz said:
If anyone finds a better way to do this, please let me know.
Click to expand...
Click to collapse
Link to that version on dmverity pkease
shumway66 said:
Link to that version on dmverity pkease
Click to expand...
Click to collapse
Done,
I have FBE not present in TWRP recovery, is that a problem?
Engineer_Virus said:
I have FBE not present in TWRP recovery, is that a problem?
Click to expand...
Click to collapse
8. Reboot the A20 into TWRP and mount everything that you can.
9. Format Data (not just wipe)
10. Flash Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
11. Reboot into Recovery.
physwizz said:
8. Reboot the A20 into TWRP and mount everything that you can.
9. Format Data (not just wipe)
10. Flash Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
11. Reboot into Recovery.
Click to expand...
Click to collapse
Please how to boot manually to download mode? I have installed Carlos Kernel and my phone has black screen after Samsung boot logo.
Dan225 said:
Please how to boot manually to download mode? I have installed Carlos Kernel and my phone has black screen after Samsung boot logo.
Click to expand...
Click to collapse
turn phone off
connect to computer and hold down both volume keys
but for twrp mode
hold all 3 buttons until the phone reboots and release volume down
When it arrives at recovery it crashes and ends with error
jp_f said:
When it arrives at recovery it crashes and ends with error
Click to expand...
Click to collapse
More information
physwizz said:
Crash Recovery for the Samsung Galaxy A20
1. Be Prepared
Most of us will suffer from a crash at some time. If you know how to fix it, you will have a lot less stress.
There are certain files you need to keep in readiness.
Always backup boot, data, system before you try any new ROM.
A. On your PC
- Firmware you downloaded from one of these sites
https://samfrew.com or https://www.samfirmware.net
or for a faster download: https://forum.xda-developers.com/galaxy-a20/how-to/a20-repair-firmware-t4066551
- recovery.tar you can download from here https://forum.xda-developers.com/galaxy-a20/how-to/guide-quick-root-twrp-galaxy-a20-t4069423
B. On your A20 external sd
Don't keep any important files on your internal sd card. Keep backups on the external sd and on usb otg.
- Boot, data, system backup
- Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
or this one
View attachment 4975463
To go to download mode
Normal method
1. Turn off phone
2. Hold down both volume keys
3. Plug in computer
Bootlooping
1. Plug in to computer
2. Hold down both volume keys
For a difficult phone
1. Connect usb to computer but not to phone
2. Hold down all 3 keys
3. When it buzzes release power and quickly plug in usb to phone.
It might take a few times to get it right.
If it's REALLY BAD
1. Wait for the battery to completely run down and use normal method.
2. Soft Crash
This is when you get a bootloop.
Recover method
1. Reboot into TWRP( hold down all 3 keys and release vol down when it reboots)
2. Restore your backup.
3. Hard Crash
This is when you get red text along the top.
Recover method
1. Connect phone cord to PC
2. Reboot into download mode (Hold down all 3 keys
When the phone reboot release power key and plug in to computer at the same time
It may take a few times to get the timing right)
3. Flash each part of the firmware into its slot.
BL_20xxxxxxx.tar.md5 goes into the BL slot
AP_20xxxxxxx.tar.md5 goes into the AP slot
CP_20xxxxxxx.tar.md5 goes into the CP slot
HOME_CSC_xxxxxx.tar.md5 goes into the CSC slot
4. You might do a Factory data reset
5. Wait for the restart
6. Skip through a minimal setup
7. Activate developer mode
8. Allow usb debugging
9. Reboot into download mode
10. Flash recovery.tar in the AP slot
11. Reboot the A20 into TWRP and mount everything that you can.
12. Format Data (not just wipe) - don't restart
13. Flash Disable_Dm-Verity_ForceEncrypt
14. Wipe both caches then go back and Reboot into Recovery.
15. Restore your data backup.
16. Reboot
Click to expand...
Click to collapse
hello sir, i need help.
after rooting my phone succesfully and try to using eureka kernel my phone just get bootloop. before that, i dont know why i cannot backup data, system and etc you just write on guide. then i enter download mode and inadvertenly pressing "dont unlock bootloader". now my phone just stay in download mode with text writed on it in red colour "vbmeta: error verifying vbmeta image..."
if it can be fixed please tell me how to fix that. Thank you very much @
Astreinz said:
hello sir, i need help.
after rooting my phone succesfully and try to using eureka kernel my phone just get bootloop. before that, i dont know why i cannot backup data, system and etc you just write on guide. then i enter download mode and inadvertenly pressing "dont unlock bootloader". now my phone just stay in download mode with text writed on it in red colour "vbmeta: error verifying vbmeta image..."
if it can be fixed please tell me how to fix that. Thank you very much @
Click to expand...
Click to collapse
Try again.
This time use a long press to unlock
cant even boot into download mode or twrp i actually have a scv46 that is actually samsung a20 rip my phone
louiskaneko said:
cant even boot into download mode or twrp i actually have a scv46 that is actually samsung a20 rip my phone
Click to expand...
Click to collapse
For a difficult phone
1. Connect usb to computer but not to phone
2. Hold down all 3 keys
3. When it buzzes release power and quickly plug in usb to phone.
It might take a few times to get it right.
If it's REALLY BAD
1. Wait for the battery to completely run down and use normal method.
I was able to follow instructions to patch the AP file with magisk. I saved it to my SD card, removed the SD card and put it on my computer and flashed it with Odin. I now have the unlocked Bootloader warning and the not Factory firmware warning. I cannot get Magisk to give me root access. When I Boot to recovery with volume up, Bixby, and Power, if nothing is plugged into the USB C port it will not go into recovery at all. If I press all three of those keys almost any length of time with the computer plugged into the USB C Port, it will go into Factory recovery. It will never boot with magisk giving root access so I can further install Magisk and Root Checker always shows not rooted. I even tried plugging in the USB C while holding the buttons, and even unplugging it while holding in the buttons.
Push.
I have the same problem. Flashed Android 11 with patched magisk AP but it seems like it does not start into the revcovery 'mode' (only factory recovery when plugged to the pc). Worked before with Android 9.
Connect the phone by computer and use ADB command reboot recovery...
With g9700 you can not simply reboot the phone, you always will lost root! You have always to turn off the phone by power button and then turn it on.
Thanks for your reply. However, if I do this, I only get into the recovery menu.
I cannot find any option to boot into recovery "mode" (where magisk is available).
The model is G970F if it makes any differences.
Hi, i had the same problem. I tried the flashing process again and again with Odin v3.14 from the beginning (patched AP only! No other files used) and finally it worked! First, after flashing hold the [power button + vol. down] for 7 seconds and when the display turns off because of the restart then immediately hold [power + bixby + vol up] until you pass all warnings and finally you will see the recovery.
Hi. I have a Samsung Galaxy Note 10 5G (d1x) device, rooted with magisk. The recovery key combo (Power+VolUp) is not working on the second reboot since flashing magisk (exiting download mode to be the first), pressing the key combo only gets me into a unrooted os. Issuing adb reboot recovery command from a pc will only get me into Magisk-enabled os, whether VolUp is long-pressed or not. After I tried to flash a TWRP image patched by the Magisk App using Odin, the situation remained same: key combo not working, adb command gets me into Magisk-enabled os. But if I use the Reboot to Recovery option inside the Magisk App, the phone blacks out for a few seconds after the Note 10 splash screen, and then reboots and gets into unrooted os.
So my question is: Is there something wrong with my method (patching the TWRP image from their official site with Magisk App, renaming it into recovery.img and flashing a tarball containing it with Odin), and how can I get both Magisk and TWRP working (and also how can I fix the recovery key combo).
REPLY:Both TWRP and Magisk work properly after the third reboot.
Hi, I have the same problem. Note 10+ and root from Magisk (Patching AP). Every time I normally reset the phone, I lose root. Then, to recover root, I have to combine on computer with the commands "adb reboot" plus a combination of PWR + Vol Up keys on the first inscription "Samsung" immediately after launching this restores root. It doesn't matter if the phone will reset 1 or 5 times. I will always lose root after a regular reset without a combination of PWR + Vol Up. I have enough of it. What am I doing wrong ?
Note 10+ and root from Magisk (Patching AP) Android 12.
Every time when I normally reset the phone, I lose root. Then, to recover root, I need to combine with the commands "adb reboot" from Windows via USB and a combination of PWR + Vol UP keys on the first inscription "Samsung" immediately after reset phone. This is the only way I can get root permissions to the next normal reset ... I will always lose root after a regular reset or turning off phone without a combination of PWR + Vol Up. I have enough of it. How to make root permanent ??
And everything is clear, I will answer myself. In addition, in Android above 11, when restarting, you need to connect the phone to the computer or USB headphones and when turning on the power, hold PWR + VolUP and release the buttons right after the first "Samsung" logo.
Second solution. Install the "Reboot options" application from google play and each time reset the phone by selecting the recovery option, this way we do not lose ROOT every time we reset ...
Due to the fact that some devices no longer uses ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition. For these devices, you will have to boot to recovery every time if you want Magisk. Since both Magisk and recovery lives in the same partition, what you actually end up getting when you choose to boot to recovery will be determined by how long you press volume up.
(Powering up normally) → (System with NO Magisk)
(OEM Recovery Key Combo) → (Splash screen) → (Release all buttons) → (System with Magisk)
(OEM Recovery Key Combo) → (Splash screen) → (Keep pressing volume up) → (Actual recovery)
One question,
how does twrp and magisk gonna work together,
or is it possible to use both..
I ask because anytime I flash twrp (magisk installed)
restart my phone it's goes into a black screen and won't even show charging when charger is connected or plugged into PC
Phone galaxy note 10 5g n971n
Bootloader: unlocked
Root access: yes
I was installing magisk modules and install busybox from magisk after rebooting to apply the modules and busybox everything started fine there was no bootloop or anything but being already on the lock screen of the device the screen flickered and wouldn't let me do anything just turn off the screen to stop flashing but it let me enter the options by holding down the power button, I already removed the modules using Magisk Manager for Recovery Mode but it still doesn't work and keeps flashing and not letting me do anything.
JigZaw17 said:
I was installing magisk modules and install busybox from magisk after rebooting to apply the modules and busybox everything started fine there was no bootloop or anything but being already on the lock screen of the device the screen flickered and wouldn't let me do anything just turn off the screen to stop flashing but it let me enter the options by holding down the power button, I already removed the modules using Magisk Manager for Recovery Mode but it still doesn't work and keeps flashing and not letting me do anything.
Click to expand...
Click to collapse
Welcome to the forums, you might have better chance on your devices section.
JigZaw17 said:
I was installing magisk modules and install busybox from magisk after rebooting to apply the modules and busybox everything started fine there was no bootloop or anything but being already on the lock screen of the device the screen flickered and wouldn't let me do anything just turn off the screen to stop flashing but it let me enter the options by holding down the power button, I already removed the modules using Magisk Manager for Recovery Mode but it still doesn't work and keeps flashing and not letting me do anything.
Click to expand...
Click to collapse
just go to platform tools and open cmd as administrator or open minimal adb and fastboot and check adb devices if it shows devices just type the command
adb wait-for-device shell magisk --remove-modules
it'll remove all the magisk modules but hey! your phone is recovered
if you look up ig you'll find commands for specific modules too but go this and install modules again