Database Info

TWRP Recovery with Mate 8 Nougat AL-10

Update:
This was the answer: https://forum.xda-developers.com/mate-8/development/unofficial-twrp-3-0-3-0-mate-8-t3524025. I'm now in TWRP.
- - -
I got an AL10 as a gift the other day. I let the phone update to Nougat before I tried to root it.
I used DC unlocker to unlock the bootloader, as well as unlock FRP. However, there is no option to unlock FRP from Developer options in the Android settings.
On Linux I use adb to reboot into the bootloader. Then, I use fastboot to flash the latest TWRP image (3.0.2.0).
That's where the problems start. Once TWRP is flashed, I try to reboot the device and into TWRP.
Nothing happens if I press volume up + power. I've also tried volume down + power, and doing this without the USB cable attached. I've tried letting go of volume up and power when the screen flashes on, and holding it down.
It seems one of the three things happens:
1. I get stuck at a phone is unlocked and can't be trusted, device is booting now, and then Android boots as normal.
2. I get stuck at device is booting now, and the device doesn't boot.
3. I end up in Huawei eRecovery.
I've also tried using fastboot to boot directly into the TWRP image, but I get a failed error.
Any insights or advice? I'd like to run Linux Deploy on this phone, which requires root.
Many thanks in advance.

[Help] Bootloop after re-locking Bootloader!

After reading the news that a new method had been found for Verizon/EE-UK Google Pixel (Sailfish) Phones to unlock the Bootloader - I decided to do so and then proceed to flash Magisk for root and other benefits however as there was recently a new update which was showing as 'Failed to Install'.
Of cause I wanted to update the device so I attempted to re-lock the Bootloader using 'fastboot flashing lock' and proceeding to select Yes from the prompt. Which seemed to be acceptable and worked to lock the Bootloader.
Now my phone is stuck in a crazy boot-loop where by the phone will turn on - flash the Google logo on the white background for a split second then shut itself down and repeat.
Does anybody have any tips for me to recover the phone from this awful state?

Mr Ian said:
After reading the news that a new method had been found for Verizon/EE-UK Google Pixel (Sailfish) Phones to unlock the Bootloader - I decided to do so and then proceed to flash Magisk for root and other benefits however as there was recently a new update which was showing as 'Failed to Install'.
Of cause I wanted to update the device so I attempted to re-lock the Bootloader using 'fastboot flashing lock' and proceeding to select Yes from the prompt. Which seemed to be acceptable and worked to lock the Bootloader.
Now my phone is stuck in a crazy boot-loop where by the phone will turn on - flash the Google logo on the white background for a split second then shut itself down and repeat.
Does anybody have any tips for me to recover the phone from this awful state?
Click to expand...
Click to collapse
Man, when you lock the bootloader you need to make sure you're 100% back on stock without any modifications flashed. Seems to me you tried locking while having magisk flashed.
Try to see if you're able to get into recovery. Get into bootloader menu by pressing power button+volume down and the press volume upp until you get to recovery and then press power button. If you're able to get into recovery then download the full ota image for Google pixel sailfish from here https://developers.google.com/android/ota and then while you're in there should be an option to update using adb. You need to adb sideload the update from your computer to your phone. I know this should work on a non Verizon phone but I hope and assume that is what's needed this time. If you're not able to get into recovery and your bootloader is still locked then you pretty much have a bricked device.

Arju said:
Man, when you lock the bootloader you need to make sure you're 100% back on stock without any modifications flashed. Seems to me you tried locking while having magisk flashed.
Try to see if you're able to get into recovery. Get into bootloader menu by pressing power button+volume down and the press volume upp until you get to recovery and then press power button. If you're able to get into recovery then download the full ota image for Google pixel sailfish from here removed-link and then while you're in there should be an option to update using adb. You need to adb sideload the update from your computer to your phone. I know this should work on a non Verizon phone but I hope and assume that is what's needed this time. If you're not able to get into recovery and your bootloader is still locked then you pretty much have a bricked device.
Click to expand...
Click to collapse
At the minute I've taken it to a Phone shop hoping they will be able to figure a way to get to the recovery menu - baring in mind I had TWRP flashed.
Yeah, It will go to the Bootloader menu but when trying to go into recovery it will just repeat the same process as before where by it will flash the Google splash-screen then restart. Any notes on how to go about hard flashing the image?

have you tried fastboot boot twrp.img? does it bootloop aswell? if so, you might have hard bricked your pixel... last solution is to try flash stock image and then try again with stock recovery / twrp img.

Mr Ian said:
At the minute I've taken it to a Phone shop hoping they will be able to figure a way to get to the recovery menu - baring in mind I had TWRP flashed.
Yeah, It will go to the Bootloader menu but when trying to go into recovery it will just repeat the same process as before where by it will flash the Google splash-screen then restart. Any notes on how to go about hard flashing the image?
Click to expand...
Click to collapse
If you can't access stock recovery and your bootloader is locked then your device is pretty much hard bricked unfortunately. Don't think the phone shop would figure it out, they might change the motherboard as a solution if they don't have the right tools to reflash on a deeper level. Hope they figure it out. Please let us know if they managed to fix it. If not then someone else might have some suggestions. I'll try to think of something else.
Try either of these commands to see if you can unlock the bootloader again:
fastboot oem unlock
or
Code:
fastboot flashing unlock
And then try what the post above me suggests.

Hey, did you ever figure out a solution to this? I did the same thing to myself today...

any solution??
---------- Post added at 03:49 PM ---------- Previous post was at 03:48 PM ----------
Mr Ian said:
After reading the news that a new method had been found for Verizon/EE-UK Google Pixel (Sailfish) Phones to unlock the Bootloader - I decided to do so and then proceed to flash Magisk for root and other benefits however as there was recently a new update which was showing as 'Failed to Install'.
Of cause I wanted to update the device so I attempted to re-lock the Bootloader using 'fastboot flashing lock' and proceeding to select Yes from the prompt. Which seemed to be acceptable and worked to lock the Bootloader.
Now my phone is stuck in a crazy boot-loop where by the phone will turn on - flash the Google logo on the white background for a split second then shut itself down and repeat.
Does anybody have any tips for me to recover the phone from this awful state?
Click to expand...
Click to collapse
Did you managed to unlock it???

You can unlock the bootloader with htc-fastboot if you have a bricked android 7-8.
They patched it on Android 9.
On android 9 your only chance is to reflash it in edl mode. Anyone here who can help me to enter edl mode with my pixel?

leagoo t5 wont boot after unlocking bootloader

Had a bad idea this morning and decided to try to root the phone, leagoo t5. The last time Im going to go messing with a phone that wasnt broken! after spending 10hrs trying to sort it! I downloaded adb tools and and twrp. I unlocked the bootloader with fastboot and installed twrp. However when I rebooted the phone it just booted straight into twrp. I cant get it to boot normally. I reinstalled the firmware but it will still not boot. I can get into recovery and factory modes but thats it. what can I do? Thanks

pcfreeze said:
Had a bad idea this morning and decided to try to root the phone, leagoo t5. The last time Im going to go messing with a phone that wasnt broken! after spending 10hrs trying to sort it! I downloaded adb tools and and twrp. I unlocked the bootloader with fastboot and installed twrp. However when I rebooted the phone it just booted straight into twrp. I cant get it to boot normally. I reinstalled the firmware but it will still not boot. I can get into recovery and factory modes but thats it. what can I do? Thanks
Click to expand...
Click to collapse
Have you tried factory resetting in recovery?

ktmom said:
Have you tried factory resetting in recovery?
Click to expand...
Click to collapse
Yes I did. No Joy. When I power on I just get the leagoo logo coming on and off repeatedly. Pressing the power button then will not turn the phone off again. I can switch it off by pressing vol- and pwr together though.
Is the problem caused by unlocking the bootloader with fastboot or that the firmware I installed is not suiting? Rebooting the phone after unlocking the bootloader before reflashing the firmware caused the leagoo logo to come on and off repeatedly accompanied by this message in very small text "Orange State - Your device has been unlocked and can't be trusted, Your device will boot in 5 seconds". After flashing the firmware with Sp Flash Tool this message is not being shown. Does reflashing firmware undo the action of unlocking the bootloader?

What your are describing is a bootloop. It sounds like the device can not find the system kernel to boot to. Did you boot the device after unlocking but before doing anything else?
Where did you get the TWRP recovery from?
Isn't this a mediatek chipset? If so, I think you need to use SP Flash Tool*to install.
I would look for a stock ROM for this device to revert to.
I'm not experienced on mediatek devices, but maybe @SubwayChamp could help.

pcfreeze said:
Yes I did. No Joy. When I power on I just get the leagoo logo coming on and off repeatedly. Pressing the power button then will not turn the phone off again. I can switch it off by pressing vol- and pwr together though.
Is the problem caused by unlocking the bootloader with fastboot or that the firmware I installed is not suiting? Rebooting the phone after unlocking the bootloader before reflashing the firmware caused the leagoo logo to come on and off repeatedly accompanied by this message in very small text "Orange State - Your device has been unlocked and can't be trusted, Your device will boot in 5 seconds". After flashing the firmware with Sp Flash Tool this message is not being shown. Does reflashing firmware undo the action of unlocking the bootloader?
Click to expand...
Click to collapse
Then to unlock bootloader is not normal that Android refuses to boot normally but when you flash a custom recovery or modify other partition this usually could happen so either or both you have to do a factory resetting/format data as @ktmom said or/and flash a kind of DM-verity for your device, this last avoids that bootloader checks the integrity of the partitions and can boot normally to system.
The warning message is normal then to unlock bootloader and reflashing the stock rom doesn´t relock it, you have to relock it at similar way that you unlocked it via fastboot command, most commom is "fastboot oem relock" but there are other variants and keep in mind that you have to return completely to stock before to apply it.

SubwayChamp said:
Then to unlock bootloader is not normal that Android refuses to boot normally but when you flash a custom recovery or modify other partition this usually could happen so either or both you have to do a factory resetting/format data as @ktmom said or/and flash a kind of DM-verity for your device, this last avoids that bootloader checks the integrity of the partitions and can boot normally to system.
The warning message is normal then to unlock bootloader and reflashing the stock rom doesn´t relock it, you have to relock it at similar way that you unlocked it via fastboot command, most commom is "fastboot oem relock" but there are other variants and keep in mind that you have to return completely to stock before to apply it.
Click to expand...
Click to collapse
I relocked the boot loader with the command "fastboot flashing lock". small white text dialogue on phone screen stated bootloader was locked successfully. rebooted phone then and it was still stuck in the boot loop. For a few seconds in between the leagoo logo a strange circular graphic was displayed on the phone with word "erasing" under it. What does this mean?
Can you tell me more about how to flash DM-verity?

pcfreeze said:
I relocked the boot loader with the command "fastboot flashing lock". small white text dialogue on phone screen stated bootloader was locked successfully. rebooted phone then and it was still stuck in the boot loop. For a few seconds in between the leagoo logo a strange circular graphic was displayed on the phone with word "erasing" under it. What does this mean?
Can you tell me more about how to flash DM-verity?
Click to expand...
Click to collapse
Ok, then to relock bootloader I guess that you did successfully boot to system again, right?
When you unlocked bootloader first then device is formatted to avoid a new user can access to the user´s data and when you relock it again the same happens.
As for DM-verity, newer devices strictly since nougat can´t boot to system after any partition was modified like happened when you flashed a custom recovery on it, here is when DM-verity can be useful, is used to avoid bootloader checks the integrity and allow a modified device can perform a reboot and more custom actions not officially permitted. You had to flash it through a custom recovery, sometimes flashing only Magisk is enough but not always.

You *might* be able to use this universal dm-verify script. It can be flashed only in a custom recovery and I'm not certain that is available to you.

ktmom said:
You *might* be able to use this universal dm-verify script. It can be flashed only in a custom recovery and I'm not certain that is available to you.
Click to expand...
Click to collapse
Good news and bad news! I got the phone to boot! I reinstalled twrp and the "magisk","no verity opt encrypt" and "disable dm verity" zips from the ext sdcard with fastboot. Twrp stated the zips installed ok but there were also some red line failure lines in the dialogue as they were being installed. I rebooted the phone via fastboot but this just resulted in it booting direct to twrp as before. I tried normal boot from twrp but it still booted straight back to twrp. I then tried selecting normal boot from the fastboot, normal, recovery option menu accessed on the Leagoo T5 by powering off the phone and then pressing the pwr and vol+ buttons together but this still resulted in it booting straight to twrp. I then decided to uninstall twrp by flashing the stock firmware recovery image to try to boot from stock recovery. I did same and rebooted from fastboot and it booted to system.
The bad news is there is an imei failure message and the sim is not connecting to the network.I googled imei failure and saw that its can happen when firmware is changed. I installed the "mobileuncle" app but according to a youtube video I watched, when I tap "Engineer Mode" there should be 2 further options available, one being MTK Mode. I am only getting one option "Engineering Mode (Android) which when I select just results in being returned to the previous menu. please say this is not a major problem!

@pcfreeze you quoted me, but as I said earlier, I'm not experienced with mediatek devices. You'd be better off quoting @SubwayChamp

pcfreeze said:
Good news and bad news! I got the phone to boot! I reinstalled twrp and the "magisk","no verity opt encrypt" and "disable dm verity" zips from the ext sdcard with fastboot. Twrp stated the zips installed ok but there were also some red line failure lines in the dialogue as they were being installed. I rebooted the phone via fastboot but this just resulted in it booting direct to twrp as before. I tried normal boot from twrp but it still booted straight back to twrp. I then tried selecting normal boot from the fastboot, normal, recovery option menu accessed on the Leagoo T5 by powering off the phone and then pressing the pwr and vol+ buttons together but this still resulted in it booting straight to twrp. I then decided to uninstall twrp by flashing the stock firmware recovery image to try to boot from stock recovery. I did same and rebooted from fastboot and it booted to system.
The bad news is there is an imei failure message and the sim is not connecting to the network.I googled imei failure and saw that its can happen when firmware is changed. I installed the "mobileuncle" app but according to a youtube video I watched, when I tap "Engineer Mode" there should be 2 further options available, one being MTK Mode. I am only getting one option "Engineering Mode (Android) which when I select just results in being returned to the previous menu. please say this is not a major problem!
Click to expand...
Click to collapse
It could be many reasons why device didn´t boot to system. Then to flash it you had to format data + flash DM-verity. Also is possible that this TWRP version is not completely suitable for your device or is unable to mount/unmount partitions correctly, you have to check from where you downloaded it and if some users are experiencing similar issues with it.
As per you IMEI lost, better is ever take a backup of the NVRAM through TWRP before to go further then it´ll be easy to recover it. In almost all firmwares for mediatek devices you´ll fnd inside the zips SPFT and SN Writer that is to recover your IMEI. Your IMEI is not really lost only got actually covered by blank codes due to a bad/incorrect flashing/wrong sequence firmware, so be careful what you do with Mobile Uncle tool if you´re not experimented with otherwise you´ll lost permanently.

SubwayChamp said:
It could be many reasons why device didn´t boot to system. Then to flash it you had to format data + flash DM-verity. Also is possible that this TWRP version is not completely suitable for your device or is unable to mount/unmount partitions correctly, you have to check from where you downloaded it and if some users are experiencing similar issues with it.
As per you IMEI lost, better is ever take a backup of the NVRAM through TWRP before to go further then it´ll be easy to recover it. In almost all firmwares for mediatek devices you´ll fnd inside the zips SPFT and SN Writer that is to recover your IMEI. Your IMEI is not really lost only got actually covered by blank codes due to a bad/incorrect flashing/wrong sequence firmware, so be careful what you do with Mobile Uncle tool if you´re not experimented with otherwise you´ll lost permanently.
Click to expand...
Click to collapse
I got into engineering mode via dialer code. CDS option was missing from connectivity. I installed https://m.apkpure.com/cds-mobile/com.doubleapaper.cds.cds_mobile but CDS is still missing from engineering mode

pcfreeze said:
I got into engineering mode via dialer code. CDS option was missing from connectivity. I installed https://m.apkpure.com/cds-mobile/com.doubleapaper.cds.cds_mobile but CDS is still missing from engineering mode
Click to expand...
Click to collapse
Sorry, just realised that this is the wrong app! nothing to do with cds in engineering mode! I triedhttps://apkcombo.com/common-data-service/com.mediatek.connectivity/
but got message that the file was corrupted and it would not install

[Guide] TWRP and ROOT for A20e (A202f) [Updated]

My way of installing TWRP and ROOT on A20e (only tested on a202f).
Everything is working both on TWRP and MAGISK.
Versions:
-Magisk (v26.1)
-MagiskManager (v26.1)
-TWRP (3.6.1_9.0)
_________________________________________________
Download attached files:
-TWRP and ROOT(magisk) Odin is included!
_________________________________________________
#Factory reset is recommended!
#Make sure BOOTLOADER is unlocked!
#If you don't need MAGISK stop at step 6 and reboot to system
[TWRP Installation]
1. Extract required files, open ODIN (as Administrator) click on the "AP" button and choose TWRP-3.6.1_9.0.tar file.
2. In the "Options" menu untick "Auto-Reboot" .
3. On your phone boot into the "Download Mode" then in ODIN you can press the START button. (make sure you are connected to PC)
4. If everything is fine there should be green "PASS!" text in ODIN.
[ If your flashing failed make sure the bootloader is unlocked and check if cable is properly connected ]
[Don't let the phone boot into system because it will replace TWRP with stock recovery.img]
6. Boot into TWRP and FORMAT DATA (Wipe/Format Data) to remove encryption.
# If you don't need MAGISK you can reboot to system. Otherwise continue reading the guide.
[MAGISK Installation]
7. From TWRP reboot into RECOVERY again.
8. Connect your phone to PC or if you moved Magisk-v26.1.zip and Magisk-v26.1.apk to SD card then use SD card.
9. Flash the Magisk-v26.1.zip file and reboot to system.
10. When you boot into system install the Magisk apk.
11. Open it and finish the installation process.
12. Reboot
ENJOY!

[UPDATE]
-Updated versions of both TWRP and MAGISK
# TWRP 3.5.2_9-0 --> TWRP 3.6.1_9-0
# Magisk v23 --> Magisk v24.3
-Remodifed VBMETA
For ANY help contact me on Telegram: https://t.me/SerbianGeek

does encryp work on this ? dont need to backup just hide data part if fone is stole

This one flashes and boots the first time, but after a reboot there is the infamous error "only official released binaries are allowed to be flashed"

/dev/null/ said:
This one flashes and boots the first time, but after a reboot there is the infamous error "only official released binaries are allowed to be flashed"
Click to expand...
Click to collapse
No problems on my end, pal.

SerbianGeekster said:
No problems on my end, pal.
Click to expand...
Click to collapse
this phone is really a PITA. every time i try to do something it's 1 step forward and 2 steps back. never suffered so much. i flashed it like 20 times. all i want is a working twrp on stock rom and pass safetynet

/dev/null/ said:
This one flashes and boots the first time, but after a reboot there is the infamous error "only official released binaries are allowed to be flashed"
Click to expand...
Click to collapse
to bypass this error:
1. connect to wifi
2. change the date to 2 august 2019
3. boot into download mode
4. flash twrp

Thank you! It worked! No problems got me.
I kinda feel like idiot that I couldn't install it with that ease before

OH **** IT WORKED !!!
I've been at this for hours, thank you so much !!!

Hello,
I have a Samsung A20e running with the a202fxxu4cvk1 firmware (a11 version). I would like to install twrp and then to root it. I tried several tutorials (Odin, OEM unblocked, USB debugging, time change) but twrp installation fails with message 'custom recovery blocked by frp'.
Can anyone help me?

I duckduckgoed, and found this XDA thread, where the second post says the following :
Nemirtingas said:
FRP: https://www.samsung.com/us/support/frp/
FRP Just locks your phone if you alter the boot or recovery image and you had a google account registered. To unlock it you have to wipe data (factory reset) and reflash stock boot.img and recovery.img before using it again. If your cousin wants to flash my ROM (lineageos-13.0) he'd better not, its not stable and he will encouter random reboots and codecs bugs. The best thing to do is to remove FRP from his phone and flash Magisk (a root manager like SuperSU) and debloat it.
For more information, find the Grandprimevelte group on Telegram.
Click to expand...
Click to collapse
The rest of the posts mention the need for a modified boot.img, else your phone would brick after adding a Google account, but I don't know about that... I have MicroG on mine with a Google account and no problems.
Anyway, frp seems to be a related to having a Google account on your phone.

fjunk said:
Hello,
I have a Samsung A20e running with the a202fxxu4cvk1 firmware (a11 version) /.../ Custom recovery blocked by frp'.
Can anyone help me?
Click to expand...
Click to collapse
Hello..I was wrong. My issue is not related to frp but OEM. OEM is unlocked according to developper menu but is not effective. Not able to upload any custom rom or bootloader.
I read that there was issue (use of a volume up button in download mode).
Any idea?

fjunk said:
Hello..I was wrong. My issue is not related to frp but OEM. OEM is unlocked according to developper menu but is not effective. Not able to upload any custom rom or bootloader.
I read that there was issue (use of a volume up button in download mode).
Any idea?
Click to expand...
Click to collapse
Indeed, my issue is that in download mode I can only do a volume down button and power button to reboot in system mode. No option to unlock bootloader.

I think you only need to do that once, afterwards, download mode doesn't warn you.
What error message do you get exactly when trying to flash TWRP, at what point, and what gives it (phone, odin) ?

lPolarisl said:
I think you only need to do that once, afterwards, download mode doesn't warn you.
What error message do you get exactly when trying to flash TWRP, at what point, and what gives it (phone, od
Click to expand...
Click to collapse
Many thanks for your update. Attached are pictures of the mobile and the Odin result. The error is an OEM issue (red text on the top of the mobile screen). In other forums, I can see that the download mode has an option to unlock OEM bootloader. I can't see it on my phone.

Putting the camera so that it covers the error message, what an amazing idea xD
I have never encountered this error, so let's start from the beginning.
Have you enabled the developer options, and activated "allow USB debugging" on the phone ? Also, if there is an option "allow OEM unlock", activate that as well (not all Samsung phones have it).
Have you installed the proper ADB and Samsung drivers ? Which version of Odin are you using ?

lPolarisl said:
Putting the camera so that it covers the error message, what an amazing idea xD
I have never encountered this error, so let's start from the beginning.
Have you enabled the developer options, and activated "allow USB debugging" on the phone ? Also, if there is an option "allow OEM unlock", activate that as well (not all Samsung phones have it).
Have you installed the proper ADB and Samsung drivers ? Which version of Odin are you using ?
Click to expand...
Click to collapse
Thanks for your reply.
That's sure that it doesn't really help to hide the error message. Usb debugging is enabled (I am able to run adb commands) and OEM is unlocked on the preference setting. I did the test with Odin 3.13 but same results with newer version. I installed an A11 firmware (a202fxxu4cvk1).
Don't t know how to go ahead. It seems that I don't have the possibility to unlock OEM in the download mode interface....

Wait, what is that about the firmware ? What did you flash, how and why ?
also, try a patched version of Odin from this post (I have 3.13.1_3B)

lPolarisl said:
Wait, what is that about the firmware ? What did you flash, how and why ?
also, try a patched version of Odin from this post (I have 3.13.1_3B)
Click to expand...
Click to collapse
I bought a refurbished mobile phone (blackmarket). It came with a 9.0 version. I tried to update to a custom rom without success so I installed the latest 'official' version
Download Samsung Galaxy A20e SM-A202F XEF France A202FXXU4CVK1 firmware
Fast download latest Samsung Galaxy A20e firmware SM-A202F from France with A202FXXU4CVK1 and Android version 11
www.sammobile.com
I uploaded this version using Odin. I also tried the patched Odin version. I read that the patched version only works with a10 version.

Huh...
I have no idea how that behaves, but I hardly see why it would cause a problem.
What else could you try... Restore factory settings maybe ?
Pressing volume up when starting in download mode ? (Note, this supposedly relocks the bootloader if it has been unlocked, if that happens and your phone isn't 100% on stock, it will brick.)

Flashing TWRP without first flashing a vbmeta image with verity disabled rendered my Galaxy Note10 exynos unable to boot

Newbie here. Tried to download TWRP onto unrooted device (Galaxy Note10 Exynos d1) with Odin and now my phone is stuck on "downloading" screen. When I try to cancel (restart phone) it goes to the startup/booting screen for less than a second and then jumps back to "downloading". It says this at the top left corner of the screen:
recovery: Error validating footer (6) CUSTOM RECOVERY VBMETA N970F XXU1 ASG0. 24967245R
I am able to get into the custom OS installation screen (don't know what it's actually called but second picture) by letting the battery drain so that the phone turns off and then holding volume up + volume down key and plugging the phone into my laptop with USB.
The bootloader is unlocked. I went to https://twrp.me/samsung/samsunggalaxynote10.html and even there it says "Flashing TWRP without first flashing a vbmeta image with verity disabled will render your device unable to boot." Does anyone know how to fix this? Thanks in advance.

TheAckermans said:
Newbie here. Tried to download TWRP onto unrooted device (Galaxy Note10 Exynos d1) with Odin and now my phone is stuck on "downloading" screen. When I try to cancel (restart phone) it goes to the startup/booting screen for less than a second and then jumps back to "downloading". It says this at the top left corner of the screen:
recovery: Error validating footer (6) CUSTOM RECOVERY VBMETA N970F XXU1 ASG0. 24967245R
I am able to get into the custom OS installation screen (don't know what it's actually called but second picture) by letting the battery drain so that the phone turns off and then holding volume up + volume down key and plugging the phone into my laptop with USB.
The bootloader is unlocked. I went to https://twrp.me/samsung/samsunggalaxynote10.html and even there it says "Flashing TWRP without first flashing a vbmeta image with verity disabled will render your device unable to boot." Does anyone know how to fix this? Thanks in advance.
Click to expand...
Click to collapse
Go first to the unlocking menu to check if your device is really unlocked, long press volume up, and see which the menu says.
If it is unlocked, then flash the vbmeta file provided, then try to boot to recovery and perform a factory reset.

SubwayChamp said:
Go first to the unlocking menu to check if your device is really unlocked, long press volume up, and see which the menu says.
If it is unlocked, then flash the vbmeta file provided, then try to boot to recovery and perform a factory reset.
Click to expand...
Click to collapse
Bootloader is unlocked and I've flashed the vbmeta file but now my phone is stuck on the startup screen and I can't seem to boot into recovery. Why?

TheAckermans said:
Bootloader is unlocked and I've flashed the vbmeta file but now my phone is stuck on the startup screen and I can't seem to boot into recovery. Why?
Click to expand...
Click to collapse
Maybe you missed some essential part of the process, by unlocking your device through the Download menu option your data has to be erased, it's recommendable after to unlock the bootloader, to reboot again to system and check once the UBS debugging and OEM unlock options if they remain fine, from there you should reboot to download mode again, uncheck the Auto-reboot option within Odin, flash the vbmeta.tar and then flash the TWRP, if all till here goes well you should reboot manually to TWRP by powering off completely, pressing the three buttons, and just now, pressing the volume up + PWR key buttons till your device boots to TWRP.

SubwayChamp said:
Maybe you missed some essential part of the process, by unlocking your device through the Download menu option your data has to be erased, it's recommendable after to unlock the bootloader, to reboot again to system and check once the UBS debugging and OEM unlock options if they remain fine, from there you should reboot to download mode again, uncheck the Auto-reboot option within Odin, flash the vbmeta.tar and then flash the TWRP, if all till here goes well you should reboot manually to TWRP by powering off completely, pressing the three buttons, and just now, pressing the volume up + PWR key buttons till your device boots to TWRP.
Click to expand...
Click to collapse
Thanks for the help, tough i am struggling to get acces to the download menu option. Could you give me a example to acess the menu?

TheAckermans said:
Thanks for the help, tough i am struggling to get acces to the download menu option. Could you give me a example to acess the menu?
Click to expand...
Click to collapse
The screenshots you uploaded some months ago, are the download screen, you, successfully did boot to, download mode doesn't have a useful menu, it's just a mode, so you can flash some things, using Odin. To boot to, use the same way you did it previously, usually, doing it manually, or if you are rooted, you can use other ways too.