Hi All...
i unlocked my Samsung A8 2021 bootloader, patched the AP file with magisk and flashed it with odin.
i am now in bootloop without any way to go into recovery or download mode.
tried all buttons combinations with pluging ang nnpuging the device.
i now sww posts regarding pathing only the boot.img and the entire AP file but the damage has been done...
anything i can do to make my device working again?
thank you!
ok i managed to enter download and went back to stock with odin.
what did i miss?
should i now patch only the boot.img in magisk and do it again?
will that work?
thanks
Hey @tlccksww , how did you get back into Download Mode? I botched my update with Odin and can't get Download Mode to launch. I can get to the recovery, can also run ADB commands, but can't get back into the bootloader.
Related
Hello family; you all much appreciated for the support here:
i have an G925A stuck in a boot loop and asks to check DRK. i seem to have no clue on how to go about it, and asking for your kind help.
I have the same problem.
I have updated from 5.0.2 to 6.0.1 (I tried different firmwares found here) and now the phone doesn't boot anymore (it says something about DRK) and goes automatically into recovery mode.
Download mode still working but I don't know what to flash anymore....I can't downgrade to 5.0.2 since the bootloader doesn't allow and I can't try to upgrade to Nougat since "install zip from adb" in original recovery doesn't work...
JdKatumba said:
Hello family; you all much appreciated for the support here:
i have an G925A stuck in a boot loop and asks to check DRK. i seem to have no clue on how to go about it, and asking for your kind help.
Click to expand...
Click to collapse
I had the same issue after trying MM ROM from 5.1.1. Finally I solved this issue following step.
1) My trial MM ROM is PK5 version
2) I try Download ROM (full 4 files) via Odin
3) The issue is remained. I try Download ROM via Odin which is 5.1.1 root version in development board. In recovery mode, you can select reboot. Then phone is freezed with galaxy logo screen without entering recovery mode again.
4) I retry Download PK5 AP ROM only via Odin.
Then phone start to work normally with MM.
But it is not fixed issue. If you enter recovery mode. You will meet the DRK error again.
Anyway, I hope you can slove DRK error issue
I followed the steps in this guide attempting to flash a rom. https://forum.xda-developers.com/tm...lopment/rom-stock-debloated-deodexed-t3423387
I was able to flash the BL and modem no problem. I proceeded to flash twrp and have been stuck at boot since. I can only go back into DL mode. Read a few places that said to reinstall rom. How do i go about installing a rom via odin? Any help is greatly appreciated.
jleed88 said:
I followed the steps in this guide attempting to flash a rom. https://forum.xda-developers.com/tm...lopment/rom-stock-debloated-deodexed-t3423387
I was able to flash the BL and modem no problem. I proceeded to flash twrp and have been stuck at boot since. I can only go back into DL mode. Read a few places that said to reinstall rom. How do i go about installing a rom via odin? Any help is greatly appreciated.
Click to expand...
Click to collapse
Okay. Here's what you do...
First, boot to DOWNLOAD MODE. Once in Download Mode, press the keys again like you are booting to Download Mode (VOLUME DOWN + HOME + POWER)
Watch the screen while holding the keys. When the screen goes blank, switch to the key combination for booting RECOVERY (VOLUME UP + HOME + POWER) and hold them until the TWRP screen appears. If the TWRP screen does not appear then we know TWRP didn't stick when you flashed it via Odin.
If the TWRP screen appears, release the keys and let it continue to boot to TWRP.
If TWRP does not boot, then I'd suggest flashing the stock firmware for your device. You can download the stock firmware for your device from www.sammobile.com or from www.updato.com
Sammobile.com is a very slow download unless you pay for a premium account. Updato is much faster. Make sure to select the correct region for your device before downloading the firmware.
Which version of Odin are you using? I've been using 3.12.3 and haven't had any problems at all with this version.
Once you habe downloaded the stock firmware, open Odin. Boot your device to Download Mode and then connect your USB cable. Make sure Odin shows you are connected.
Next, click the OPTIONS TAB in Odin and un-check
AUTO REBOOT. Then, select the AP TAB in Odin and navigate to the firmware file you have downloaded. Let Odin do its thing to verify the file and click START to begin the flash. Once the flash is complete, disconnect the USB Cable and press the key combination for booting to Download Mode again. Once the screen goes black, switch to the key combination for booting RECOVERY. Once in recovery you can select the reboot option to boot your device normally and start fresh from there and attempt to flash TWRP again.
Also, which Note 5 do you have?
fast69mopar said:
Okay. Here's what you do...
First, boot to DOWNLOAD MODE. Once in Download Mode, press the keys again like you are booting to Download Mode (VOLUME DOWN + HOME + POWER)
Watch the screen while holding the keys. When the screen goes blank, switch to the key combination for booting RECOVERY (VOLUME UP + HOME + POWER) and hold them until the TWRP screen appears. If the TWRP screen does not appear then we know TWRP didn't stick when you flashed it via Odin.
If the TWRP screen appears, release the keys and let it continue to boot to TWRP.
If TWRP does not boot, then I'd suggest flashing the stock firmware for your device. You can download the stock firmware for your device from www.sammobile.com or from www.updato.com
Sammobile.com is a very slow download unless you pay for a premium account. Updato is much faster. Make sure to select the correct region for your device before downloading the firmware.
Which version of Odin are you using? I've been using 3.12.3 and haven't had any problems at all with this version.
Once you habe downloaded the stock firmware, open Odin. Boot your device to Download Mode and then connect your USB cable. Make sure Odin shows you are connected.
Next, click the OPTIONS TAB in Odin and un-check
AUTO REBOOT. Then, select the AP TAB in Odin and navigate to the firmware file you have downloaded. Let Odin do its thing to verify the file and click START to begin the flash. Once the flash is complete, disconnect the USB Cable and press the key combination for booting to Download Mode again. Once the screen goes black, switch to the key combination for booting RECOVERY. Once in recovery you can select the reboot option to boot your device normally and start fresh from there and attempt to flash TWRP again.
Also, which Note 5 do you have?
Click to expand...
Click to collapse
Hey, thanks for your response. So I was able to get my System back to working. I had to downoad the stock firmware through sammobile. I ended up paying for the fast download (30days of service) Well ill keep updato in mind if this every happens again. Im on N920TUVU4EQE1 For the n920T since i had already flashed the modem and bootloader before i flashed twrp. I'm on Odin 3.12.3 as well.
"This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab."
Apparently the kernel i was using wasnt allowing twrp to install. So now i have to figure out how to root my new stock firmware and install recover so i can flash a rom.
jleed88 said:
Hey, thanks for your response. So I was able to get my System back to working. I had to downoad the stock firmware through sammobile. I ended up paying for the fast download (30days of service) Well ill keep updato in mind if this every happens again. Im on N920TUVU4EQE1 For the n920T since i had already flashed the modem and bootloader before i flashed twrp. I'm on Odin 3.12.3 as well.
"This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab."
Apparently the kernel i was using wasnt allowing twrp to install. So now i have to figure out how to root my new stock firmware and install recover so i can flash a rom.
Click to expand...
Click to collapse
What you have to do is this...
Flash TWRP, swipe to allow system modifications and then flash the no_verity_opt_encrypt_5.1.zip available from
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
This zip will disable dm-verity and forced encryption in the fstab and allow you to boot normally.
Once this had been done you can flash the root zip of your choice and go to town with debloating, custom ROM's and custom kernels.
jleed88 said:
Hey, thanks for your response. So I was able to get my System back to working. I had to download the stock firmware through sammobile. I ended up paying for the fast download (30days of service) Well ill keep updato in mind if this every happens again. Im on N920TUVU4EQE1 For the n920T since i had already flashed the modem and bootloader before i flashed twrp. I'm on Odin 3.12.3 as well.
"This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab."
Apparently the kernel i was using wasnt allowing twrp to install. So now i have to figure out how to root my new stock firmware and install recover so i can flash a rom.
Click to expand...
Click to collapse
fast69mopar said:
What you have to do is this...
Flash TWRP, swipe to allow system modifications and then flash the no_verity_opt_encrypt_5.1.zip available from
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
This zip will disable dm-verity and forced encryption in the fstab and allow you to boot normally.
Once this had been done you can flash the root zip of your choice and go to town with debloating, custom ROM's and custom kernels.
Click to expand...
Click to collapse
When i flashed TWRP i unchecked the Auto-Reboot option. did a key combo to get to twrp but it didnt ask me to swipe to allow system modification. So i went ahead and flashed no_verity_opt_encrypt_5.1.zip with success. Proceeded to flash SuperSU-v2.66 and it got stuck at -Creating paths. I rebooted to recovery and found this guide https://forum.xda-developers.com/galaxy-s6/general/root-s6-nougat-supersu-t3570740
Coming from sickmade 6.0.1 and through all the struggles i am now at stock ROOTED firmware EQG3 andriod 7.0! I just had to take my time and search around a bit. You guys are all amazing. Hopefully if someone has this problem they will find this thread.
jleed88 said:
When i flashed TWRP i unchecked the Auto-Reboot option. did a key combo to get to twrp but it didnt ask me to swipe to allow system modification. So i went ahead and flashed no_verity_opt_encrypt_5.1.zip with success. Proceeded to flash SuperSU-v2.66 and it got stuck at -Creating paths. I rebooted to recovery and found this guide https://forum.xda-developers.com/galaxy-s6/general/root-s6-nougat-supersu-t3570740
Coming from sickmade 6.0.1 and through all the struggles i am now at stock ROOTED firmware EQG3 andriod 7.0! I just had to take my time and search around a bit. You guys are all amazing. Hopefully if someone has this problem they will find this thread.
Click to expand...
Click to collapse
Glad it's working for you. Good job. Now you can make your Note 5 your own. I'm an S6 Edge Plus user. We use the exact same ROM as the Note 5. We just use a different kernel. Happy flashing. If you run into any issues don't hesitate to ask me or anyone else here at XDA. This is a great place to read and learn especially with your Note 5. If a problem has occurred before you can bet that someone has posted about it and you will find a solution.
the phone initially booted up normally. and i power off try to enter recovery mode but i got bootloop , is there any way to get into odin mode , recovery mode is broken ( i flashed recovery with odin it took 15 minutes so i click stop and it crashed ) my phone is sm m20
is there any reason why flashing twrps via ADB would send z5 pro gt into boot loop into bootloader unable to access the custom recovry or phone needing to do emergency flashing via qfil to stock firmware i did previously use trwps on device to flash files and to sign boot to always boot twrps recovery when trying to access recovery mode . (before bootlooping)
affter bootlooping and fixing via qfil i have been unable to successful install trwps if i do it bootloop to bootloader.
whats the difference between "meta" / "flat" options in qfil
tried locked and unlocked bootloader on both 10.5.304 and 11.1.021 also tried to go straight to recovery mode affter twrps flashing on both firmware same thing lead me bootloop needing to qfill to 10.5.30
another question can i qfil flash to 11.1.021 straight away without having having to qfil 10.5.30 then ota updating to 11.1.021..
thanks in advance
leerh said:
is there any reason why flashing twrps via ADB would send z5 pro gt into boot loop into bootloader unable to access the custom recovry or phone needing to do emergency flashing via qfil to stock firmware i did previously use trwps on device to flash files and to sign boot to always boot twrps recovery when trying to access recovery mode . (before bootlooping)
affter bootlooping and fixing via qfil i have been unable to successful install trwps if i do it bootloop to bootloader.
whats the difference between "meta" / "flat" options in qfil
tried locked and unlocked bootloader on both 10.5.304 and 11.1.021 also tried to go straight to recovery mode affter twrps flashing on both firmware same thing lead me bootloop needing to qfill to 10.5.30
another question can i qfil flash to 11.1.021 straight away without having having to qfil 10.5.30 then ota updating to 11.1.021..
thanks in advance
Click to expand...
Click to collapse
Okay ?
The point is ? I must unlock , install twrp and flashing via ota ?
Flash via qfil done and isn't working
My touchscreen still have thats issue
IamRdw said:
Okay
The point is ? I must unlock , install twrp and flashing via ota ?
Flash via qfil done and isn't working
My touchscreen still have thats issue
Click to expand...
Click to collapse
if you want OTA(over the air) updates you need to lock bootloader. otherwise the updater will say something like phone has been rooted and they cant provide you an update
https://forum.xda-developers.com/z5-pro-gt/how-to/installing-ota-update-11-5-141-via-twrp-t4050027
http://anago.2ch.sc/test/read.cgi/sm...ne/1577014188/ theres a lot of information on this link here are some highlights for me
_____________________________________
>> Crash dump loop of 113 ROM burnt Z5PROGT can be restored by burning CNROM for the time being,
Even if I tried it again, it was useless, so if I look at the syntax at the time of batch execution, it seems that vbmeta.img is not burned.
It says unrecognised option `--disable-verification '.
This time, the boot loader loop only started, and TWRP couldn't start.
This time it may be packed
__________________________________________
>> 117
I'm sorry I want to confirm.
Where did you use the fastboot command?
①fastboot --disable-verification flash vbmeta vbmeta.img
②fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
It is ① that I instructed, but it looks like there are two kinds when I check it on the net.
He seemed to have hit it without knowing it.
Excuse me, can you hit both again?
________________________________________
>> 150
>> I burned 113 ZUI11 version Gro ROM.
I re-added TWRP, but when I started it, it was usable normally, so I could add Magisk,
After that, it only seems to be unavoidable that it only starts up in normal recovery mode.
It is troublesome to do it every time you want to use TWRP, but it can't be helped.
__________________________________________________ _______
this helped Solved
Hello,
I have S10 Exynos version with rooted android 9. I tried to install TWRP but after flashing it my device couldn't boot up. My mistake was probably that I wanted to hard reset the phone and after entering download mode I pressed VOL-UP button for a few seconds. After that my phone always boots to download mode and in the right upper corner these lines are written :
VBMETA: Error veryfing vbmeta image: OK_NOT_SIGNED (3)
CUSTOM VBMETA
VBMETA : No sign info
VBMETA .
Before opnening that download mode (which starts after 1 sec of booting) I managed to open normal download mode but unfortunately on the 6 lines it's written that : OEM LOCK: ON(U).
I dont know what should I do now. Is it possible to flash stock rom? In this instruction https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root it's written that I mustn't flash stock rom without previously patching it in Magisk.
Please help me guys.
Przezro098 said:
Hello,
I have S10 Exynos version with rooted android 9. I tried to install TWRP but after flashing it my device couldn't boot up. My mistake was probably that I wanted to hard reset the phone and after entering download mode I pressed VOL-UP button for a few seconds. After that my phone always boots to download mode and in the right upper corner these lines are written :
VBMETA: Error veryfing vbmeta image: OK_NOT_SIGNED (3)
CUSTOM VBMETA
VBMETA : No sign info
VBMETA .
Before opnening that download mode (which starts after 1 sec of booting) I managed to open normal download mode but unfortunately on the 6 lines it's written that : OEM LOCK: ON(U).
I dont know what should I do now. Is it possible to flash stock rom? In this instruction https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root it's written that I mustn't flash stock rom without previously patching it in Magisk.
Please help me guys.
Click to expand...
Click to collapse
I don't know if it's same situation, but I tried to flash twrp , decided to go back to stock magisk and it just wouldn't flash, kept saying only official binaries can be flashed. After a good few hours of freaking out I thought I'll try to just flash stock rom including stock ap file, and thank god it worked. I then ran setup as normal , made sure OEM unlock was turned on, proceeded to flash stock pie patched magisk and it worked.
Hi guys,
I can't seem to boot up after I successfully root it with the file name "SM-N950F_U6_9.0" through odin v3.13.1
Really not sure what I did wrong :crying:
Currently trying to download the stock firmware to recover it
How do I upload pics when I'm still new?
*edit*
I flashed the stock firmware and managed to install magisk through TWRP. The issue is that I didn't go into recovery straight from fastboot :laugh: