Develop Bugs

Problems with Safety Net

After the last OTA update, my Moto G5 started to boot with the following warning:
"
Your device has failed verification and may not work properly.
To learn more visit:
motorolacom/unlockbootloader
ID: N/A
Your device will boot in 5 seconds
"
It also started to restart randomly.
I did some research on the web and found out that this warning appears when someone unlocks/roots the device.
The problem is that I aver never unlocked the bootloader or rooted the device.
When I boot to fastboot it says "OEM Locked" and the app DevCheck says that I am not rooted.
It seems to me that the update corrupted something and now some piece of software flags my device as unlocked.
Besides the irritating screen, some apps are not working properly or cannot be downloaded from the store.
I tried to reset to factory settings and wipe caches. Problem still happens.
I'd like to know if you guys know a solution for this problem.
I saw on another post that this problem was happening on some Verizon Moto Zs and they provided a software to reinstall the rom
Unfortunately, Motorola has not released a software to do the same to unlocked devices.
My ROM version is: NPPS25.137-33-6 (yeah, there is an "S" that I don't find in the roms available here)
The baseband is: M8937_8000.122.02.45R
(CEDRIC_BRAZILDSDS_CUST)
I was thinking in loading the rom into internal memory, reboot in recovery mode and flash the rom using the option "Install package from zip".
Do you know if it would work without an unlocked bootloader. Is it safe?
Thank you for the help,

Don't know if you can flash the boot logo without an unlocked bootloader but if you can here it is
Put phone in fastboot mode
Download logo from link below
Enter the following in a windows command prompt where you have fastboot files (Google to learn howto install Android sdk) & the logo file
Code:
fastboot.exe flash logo logo-g5-fix.bin
http://drive.google.com/file/d/0B-idWfPYugGvREJaR3B0UFIxUkU/view?usp=sharing
If you can't then you have no option but to wait for Motorola to fix it if you really haven't modded your phone

TheFixItMan, I really appreciate your answer.
But in that case wouldn't I just be changing the warning screen?
The problems with Netflix and other apps would remain.
I need something to fix the cause of the problem.
Have you guys heard about that problem before?
This guy had the same problem, but verizon patched it:
https://community.verizonwireless.com/thread/921991

hoferbr said:
TheFixItMan, I really appreciate your answer.
But in that case wouldn't I just be changing the warning screen?
The problems with Netflix and other apps would remain.
I need something to fix the cause of the problem.
Have you guys heard about that problem before?
This guy had the same problem, but verizon patched it:
/QUOTE]
I have the same problem as you. Could you fix it?
Thank you,
Luciano
Click to expand...
Click to collapse

You can go back to stock using ADB update or by flashing VERIFIED images in bootloader mode. This will work even when bootloader is locked.

p8tgames said:
You can go back to stock using ADB update or by flashing VERIFIED images in bootloader mode. This will work even when bootloader is locked.
Click to expand...
Click to collapse
To flash using bootloader I need just to copy the .zip in the internal memory, reboot in reboot in bootloader mode and select the option "install from .zip file"?
Where do I find the verified image for my device?
If I flash an unverified image will my device brick ou the bootloader will present a "impossible to procede" screen?
Thank you for the help!

hoferbr said:
To flash using bootloader I need just to copy the .zip in the internal memory, reboot in reboot in bootloader mode and select the option "install from .zip file"?
Where do I find the verified image for my device?
If I flash an unverified image will my device brick ou the bootloader will present a "impossible to procede" screen?
Thank you for the help!
Click to expand...
Click to collapse
you can flash what ever you want in fastboot -
However - In terms of firmware, if you are trying to flash incorrect firmware then the verification check will fail and it will not flash
Just don't flash a new bootloader if you are worried about it - its not needed unless you are upgrading an android version and that version has an updated bootloader

So I am safe if I follow these steps:
Manually Update Android Nougat for Moto G5 (NPP25.137-33) via Recovery
First of all, Go to Settings –> About Phone –> Tap on Build Number 7 Times.
Go to Developer Options –> Enable USB Debugging.
Save Stock Android Nougat rom for Moto G5 and save it in Internal storage.
Reboot Moto G5 Plus to Recovery Mode.
Select Apply Update from SD Card.
Select the Downloaded ZIP file from SD Card.
Wait until Installation process Completes.
Once the Installation completed. Reboot the Phone.
If my ROM is a wrong version, will the bootloader detect and deny instalation?

hoferbr said:
So I am safe if I follow these steps:
Manually Update Android Nougat for Moto G5 (NPP25.137-33) via Recovery
First of all, Go to Settings –> About Phone –> Tap on Build Number 7 Times.
Go to Developer Options –> Enable USB Debugging.
Save Stock Android Nougat rom for Moto G5 and save it in Internal storage.
Reboot Moto G5 Plus to Recovery Mode.
Select Apply Update from SD Card.
Select the Downloaded ZIP file from SD Card.
Wait until Installation process Completes.
Once the Installation completed. Reboot the Phone.
If my ROM is a wrong version, will the bootloader detect and deny instalation?
Click to expand...
Click to collapse
if you are talking about an official ota update then it will fail - you cannot update like this
An offical ota zip requires a non rooted device, unmodified system partition and stock recovery
you maybe able to download the ota update and save it (its in the cache partition)
then use flashfire app to install it
note if its a custom rom than recovery mode will allow you to flash any zip and will flash anything unless the updater script specifies a certain build.prop target eg phone model or other criteria that would stop it flashing if it was false
If you want to flash firmware you need the firmware image and flash it via fastboot

TheFixItMan said:
if you are talking about an official ota update then it will fail - you cannot update like this
An offical ota zip requires a non rooted device, unmodified system partition and stock recovery
you maybe able to download the ota update and save it (its in the cache partition)
then use flashfire app to install it
note if its a custom rom than recovery mode will allow you to flash any zip and will flash anything unless the updater script specifies a certain build.prop target eg phone model or other criteria that would stop it flashing if it was false
If you want to flash firmware you need the firmware image and flash it via fastboot
Click to expand...
Click to collapse
I have the same problem, but I unlock the booloader after with the intention to relock when flashing a stock rom.
But every stock rom I have downloaded when flashing with mfastboot shows a version security downgrade error and cannot reflash stock rom.
My bootloader is B8.23.
Any help appreciatte.

jdonadel said:
I have the same problem, but I unlock the booloader after with the intention to relock when flashing a stock rom.
But every stock rom I have downloaded when flashing with mfastboot shows a version security downgrade error and cannot reflash stock rom.
My bootloader is B8.23.
Any help appreciatte.
Click to expand...
Click to collapse
You need firmware that matches or exceeds your current firmware version - you cannot flash a lower firmware version

TheFixItMan said:
You need firmware that matches or exceeds your current firmware version - you cannot flash a lower firmware version
Click to expand...
Click to collapse
Yeah, I see that, but looking into the stock rom .zip file I cannot find the correct ID that matches to my. But since I posted the reply, I´ve downloaded from a mirror in lolinet, and correct flash my phone.

I can't Lock Bootloader (Mediapad M2 10 A01W)

Hi.
I rooted my M2 10 Wifi (A01W) with Kingroot and apparently now it's unroot (Magisk Manager said that). Even I made a factory reset.
I have the _B007 version and when I try to upgrade via OTA to _B008, it always fail and show "Failed to check the update files. Please download the package again".
I've working with ADB, Fastboot... and I could see that it's unroot, but the Bootloader is Unlock and I can't Relock it. Maybe it's the reason because the OTA doesn't work.
So I got a fastboot code with DC-UNLOCKER and tried to relock (fastboot oem relock CODE) and the answer was:
FAILED (Remote: root type is risk)
If I execute "fastboot oem check-rootinfo":
old_stat: RISK
now_stat: RISK
change_time: xxxxxxxxx
Apparently, the Recovery is stock, with EMUI logo showing 3 options:
Reboot, Wipedata/factory reset and Wipe chache partition
I made the factory reset that way.
Any idea? Thanks.

ma2crmam said:
Hi.
I rooted my M2 10 Wifi (A01W) with Kingroot and apparently now it's unroot (Magisk Manager said that). Even I made a factory reset.
I have the _B007 version and when I try to upgrade via OTA to _B008, it always fail and show "Failed to check the update files. Please download the package again".
I've working with ADB, Fastboot... and I could see that it's unroot, but the Bootloader is Unlock and I can't Relock it. Maybe it's the reason because the OTA doesn't work.
So I got a fastboot code with DC-UNLOCKER and tried to relock (fastboot oem relock CODE) and the answer was:
FAILED (Remote: root type is risk)
If I execute "fastboot oem check-rootinfo":
old_stat: RISK
now_stat: RISK
change_time: xxxxxxxxx
Apparently, the Recovery is stock, with EMUI logo showing 3 options:
Reboot, Wipedata/factory reset and Wipe chache partition
I made the factory reset that way.
Any idea? Thanks.
Click to expand...
Click to collapse
Well, I've read that flashing a system.img extracted from the UPDATE.APP I would can restore the Stock ROM... but I don't find a complete Stock ROM for Mediapad M2 10 Wifi (A01W).
I found the OTA in Romfirmware or Fordroid (sorry, I'm new user and I can not post external links). With this I can flash BOOT.img and RECOVERY.img, but the problem persist.
Does someone has any idea... or where can I get the complete Stock ROM?
Thanks!!!

ma2crmam said:
Well, I've read that flashing a system.img extracted from the UPDATE.APP I would can restore the Stock ROM... but I don't find a complete Stock ROM for Mediapad M2 10 Wifi (A01W).
I found the OTA in Romfirmware or Fordroid (sorry, I'm new user and I can not post external links). With this I can flash BOOT.img and RECOVERY.img, but the problem persist.
Does someone has any idea... or where can I get the complete Stock ROM?
Thanks!!!
Click to expand...
Click to collapse
Stokk ROM maybe available through a paid service by easy firmware. Got my LTE Stock ROM frim there. For the Wi-Fi edition you could first take a look here.
Sent from my HTC U11 using XDA Labs

5m4r7ph0n36uru said:
Stokk ROM maybe available through a paid service by easy firmware. Got my LTE Stock ROM frim there. For the Wi-Fi edition you could first take a look here.
Sent from my HTC U11 using XDA Labs
Click to expand...
Click to collapse
Thanks!!! I didn't know that page. It's fine and does not look very expensive.
Just one more doubt.
The firmaware I need (as read on the tablet) is M2-A01w...B008 for West Europe
The firmware that the page shows is M2-A01w...B008CUSTC100D001
Do you know what CUSTC100D001 mean? Could I used it without problems?

ma2crmam said:
Thanks!!! I didn't know that page. It's fine and does not look very expensive.
Just one more doubt.
The firmaware I need (as read on the tablet) is M2-A01w...B008 for West Europe
The firmware that the page shows is M2-A01w...B008CUSTC100D001
Do you know what CUSTC100D001 mean? Could I used it without problems?
Click to expand...
Click to collapse
Glad it helped and yes it is not so expensive regarding the fact that there are all sorts of official firmware (mostly leaked ones) available for a lot of manufacturers.
The CUST reference at the end if the firmware version can be found in settings > about the tablet in the very last line. Mine is in German, So translated this line would state something like adapted/customized version. D001 is definitely Western Europe,this should be fine.
If not familiar how to install it google or search the forum for dload method. It will tell you what to do.
Sent from my HTC U11 using XDA Labs

I've done:
1. Get the correct firmware (version ...B007) and extract the RECOVERY.IMG and UPDATE.APP.
2. Flash the RECOVERY with Fastboot and install the UPDATE with the "dload" in the SD.
3. Reboot in RECOVERY MODE, wipe all and restore factory settings.
4. Then, the tablet was updated via OTA to the ...B008 version.
Then, positive:
1. The OTA works fine.
2. I was abble to install the Nextlix App and the HBO Spain App plays videos. Both didn't work before.
3. If I execute "fastboot oem check-rootinfo":
old_stat: RISK
now_stat: SAFE
Then, negative:
1. I can't relock the Bootloader yet. When I try to relock (fastboot oem relock CODE) and the answer was again: FAILED (Remote: root type is risk)
Well, for normal use that's enough, but... THE RELOCK is becoming personal!!!

Global OTA 9.5.4.0 + TWRP = fail

My phone has unlocked bootloader, TWRP, and is rooted with magisk. Got the OTA for (global) 9.5.4.0 last night - it downloads/de-crypts ok, reboots into TWRP, and then fails to flash. I also tried to flash manually via TWRP by locating the downloaded file, still fails. During the night, it rebooted itself (to try again I suppose), and my alarm didn't go off.
So here I am, late in work, wasting more "work time" to ask you for a possible solution :angel:

Go back to original miui recovery then you can update your miui successfully. After update,reflash twrp and magisk.

jimandy60 said:
Go back to original miui recovery then you can update your miui successfully. After update,reflash twrp and magisk.
Click to expand...
Click to collapse
Sounds easy, but I don't know how to do that. Could you point me in the right direction?

you can't flash an OTA with TWRP

Flash recovery img with fastboot
Code:
fastboot flash recovery recovery.img
then boot your phone
settings->about phone->system update->update
it will get in origin miui recovery and update system automatically
after update finished,reflash twrp and magisk

Thank you very much @jimandy60
With all the respect though, I would prefer downloading the file from a popular location. Is there any way to find this hosted somewhere else, maybe by Xiaomi?

ang3l said:
Thank you very much @jimandy60
With all the respect though, I would prefer downloading the file from a popular location. Is there any way to find this hosted somewhere else, maybe by Xiaomi?
Click to expand...
Click to collapse
maybe try this site?
en.miui.com

Hello!
I got the same problem but instead to come here and ask for help I tried to solve myself. I downloaded the lastest TWRP version and the device was not going into recovering mode. Then I installed again the previous one without results. I downloaded the TWRP app from Play Store and trying to solve I made wipe data, cache and I am not sure but I think also choose wipe system. Now my phone is stuck on the fastboot screen. Does not start. Using ADB I installed back the stck recovery but the problem remains. Somebody can help me please?

reflash the full rom?
download&unzip full rom package,get in fastboot mode and run flash_all.bat

Check out my guide here:
https://forum.xda-developers.com/mi-mix-2/how-to/guide-mi-mix-2-unroot-restore-recovery-t3770690
It has all the steps and files you will need to go from rooted stock MIUI Nougat to rooted stock MIUI Oreo applying the OTA update

colorado_al said:
Check out my guide here:
https://forum.xda-developers.com/mi-mix-2/how-to/guide-mi-mix-2-unroot-restore-recovery-t3770690
It has all the steps and files you will need to go from rooted stock MIUI Nougat to rooted stock MIUI Oreo applying the OTA update
Click to expand...
Click to collapse
Thanks, I'll take a look.

Pre-rooted Boot Image OP7T European HD65BA 10.0.7

Hello,
I have seen few requests about providing pre-rooted boot image file for OP7T European version for firmware 10.0.6 so here you go.
Steps :
1) Reboot your phone in bootloader mode (fastboot mode).
2) Execute command fastboot boot magisk_patched.img
3) Reboot the device
4) Install Magisk Manager
5) Click on Install, then direct install and wait the end of the process
6) Reboot the device
Also attaching the stock boot file in case anything goes wrong.
P.S : I don't own European OP7T.
Link : https://www.androidfilehost.com/?w=files&flid=303273

*delete*

Can you do one for the 10.0.6 USA Version? I can't find one anywhere. Thanks so much. I can't even find a copy of the stock 10.0.6 US boot img

Worked well, got my phone rooted yesterday.
Lähetetty minun HD1903 laitteesta Tapatalkilla

click4dylan said:
Can you do one for the 10.0.6 USA Version? I can't find one anywhere. Thanks so much. I can't even find a copy of the stock 10.0.6 US boot img
Click to expand...
Click to collapse
USA version is HD65AA ? Can you send the product code and I will try

Yes, my build number is 10.0.6.HD65AA and model number is HD1905. Thank you so very much! Also, can you show me how you are getting the boot image for these new versions so I can do it myself in the future? Thanks again. SKU on the box says 5011100751

Hi!
Sorry for this question, flashing this boot image will wipe my device?
Thanks.

paulo_snower said:
Hi!
Sorry for this question, flashing this boot image will wipe my device?
Thanks.
Click to expand...
Click to collapse
NO! First time you unlock your bootloader thats wipe your device, not when flashing a boot.img

it's not working for me with Oxygen 10.0.6 HD65BA.
If i try to boot the magisk patched boot image the phone just reboot within fastboot mode, and if i try to normally boot i just can't update magisk.
-----
Update:
I found this surfing the net :
Unlike older OnePlus phones, the current bootloader of the OnePlus 7 Pro doesn’t allow ‘fastboot boot’ (also known as tethered booting) command. The situation is same as Essential PH-1 as well some other phones where you can’t temporarily boot a kernel or recovery.

nicoilboss said:
it's not working for me with Oxygen 10.0.6 HD65BA.
If i try to boot the magisk patched boot image the phone just reboot within fastboot mode, and if i try to normally boot i just can't update magisk.
-----
Update:
I found this surfing the net :
Unlike older OnePlus phones, the current bootloader of the OnePlus 7 Pro doesn’t allow ‘fastboot boot’ (also known as tethered booting) command. The situation is same as Essential PH-1 as well some other phones where you can’t temporarily boot a kernel or recovery.
Click to expand...
Click to collapse
click4dylan said:
Yes, my build number is 10.0.6.HD65AA and model number is HD1905. Thank you so very much! Also, can you show me how you are getting the boot image for these new versions so I can do it myself in the future? Thanks again. SKU on the box says 5011100751
Click to expand...
Click to collapse
zanderzone said:
USA version is HD65AA ? Can you send the product code and I will try
Click to expand...
Click to collapse
Sorry for being late. Please try this : https://forum.xda-developers.com/oneplus-7t/how-to/pre-rooted-boot-image-op7t-global-t4009305

Thanks, I found the instructions on how to do it already and took the Global boot image. I am just booting it with fastboot boot instead of flash. Just being cautious is all.

Same situation over there, trying either boot or flash the image, the phone reboots itself into bootloader. Stock 10.0.6.
Enviado desde mi HD1903 mediante Tapatalk

What is the difference between global and European? And can i still update ota after flashing this?

Hello !
Thanks for the guide !
I successfully installed Magisk, but once I install Riru core and EdXposed, my OP7T also gets stuck and boots only into fastboot. After wiping everything to factory reset, my phone is back to normal.
Is EdXposed working with this version of Magisk ?
(OpenPlus 7T HD65BA 10.0.6)
Thanks for help
Edit : problem solved with this method.

Excellent.
Many thanks @zanderzone

Can i still update ota in settings adter installing this version? Or will i loose root everytime?

karayemis said:
Can i still update ota in settings adter installing this version? Or will i loose root everytime?
Click to expand...
Click to collapse
Most likely you won't get any notifications if there are updates. You won't be able to use incremental updates.
But you can keep root flashing magisk right after the update before rebooting your phone.

could someone help me? I got the european version but if i try to boot the magisk_patched.img i just get stuck in fastboot mode and if i try to flash the patched image i get stuck in fastboot mode and i've to flash again the stock boot.
I also tried the global one but without any results.
Thanks
edit. I have the HD65BA 10.0.6 version

I was able to boot using your magisk_patched.img using "fastboot boot magisk_patched.img", but WIFI doesn't work now. I haven't inserted the SIM yet so I am unable to install magisk (it can't connect to download it). Is it only my case, or did it happen to anyone else? Any fixes?
Or is ir a temporary thing and after installing magisk it will work (WIFI)?
EDIT: with "fastboot boot Stock_boot.img" I get the same WIFI problem. Rebooting normally makes WIFI work again.
EDIT2: I tried it with the SIM on and the process was perfect. Thank you for that patched boot image and the tutorial!!!

Any chance @zanderzone that you could put a 10.0.7 version up?
I lost root with the recent update...
I found the detailed instructions too late.
Detailed instructions here: https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Many thanks

Question Locked bootloader while in download mode boot loop

Hey i was attempted to install TWRP and got stuck in download mode boot loop. Fixed it by flashing stock firmware. I noticed a small error with my camera so i tried to lock bootloader again to see if that would fix the issue. But after flashing stock firmware a second time after locking the bootloader it didnt work and im stuck in download mode boot loop again. Only this time i dont get the option to unlock the bootloader and i cant enter the OS in order to enable OEM Unlock.
Here is the error screen: https://prnt.sc/q8vmG--mTHxY
Anyone know how to get out of this mess? Thanks

Am i doomed?

cheen11 said:
Hey i was attempted to install TWRP and got stuck in download mode boot loop. Fixed it by flashing stock firmware. I noticed a small error with my camera so i tried to lock bootloader again to see if that would fix the issue. But after flashing stock firmware a second time after locking the bootloader it didnt work and im stuck in download mode boot loop again. Only this time i dont get the option to unlock the bootloader and i cant enter the OS in order to enable OEM Unlock.
Here is the error screen: https://prnt.sc/q8vmG--mTHxY
Anyone know how to get out of this mess? Thanks
Click to expand...
Click to collapse
You can't lock your bootloader when your phone have unsigned binaries such as TWRP/Magisk installed. Have you tried to flash again the stock firmware (BL/CP/AP/CSC)?
EDIT: by looking at the error it seems like your bootloader and vbmeta aren't from the same build (bootloader: DVK5, vbmeta: DVL2), I highly suggest you to flash the latest firmware available for your country

BlackMesa123 said:
You can't lock your bootloader when your phone have unsigned binaries such as TWRP/Magisk installed. Have you tried to flash again the stock firmware (BL/CP/AP/CSC)?
EDIT: by looking at the error it seems like your bootloader and vbmeta aren't from the same build (bootloader: DVK5, vbmeta: DVL2), I highly suggest you to flash the latest firmware available for your country
Click to expand...
Click to collapse
I can try other countries but im not sure what the exact country version is. Im from denmark and my country is not on the list so i just choose UK.

cheen11 said:
I can try other countries but im not sure what the exact country version is. Im from denmark and my country is not on the list so i just choose UK.
Click to expand...
Click to collapse
Shouldn’t be a big deal unless there’s something Carrier specific required by your phone. Just make sure you don’t lock your bootloader again while using custom binaries or you might soft brick your device again. To bypass the camera lock you can use a SafetyNet fix module for Magisk which will spoof the bootloader status to the camera HAL

cheen11 said:
I can try other countries but im not sure what the exact country version is. Im from denmark and my country is not on the list so i just choose UK.
Click to expand...
Click to collapse
You can try also the NEE for Nordic Countries...

BlackMesa123 said:
You can't lock your bootloader when your phone have unsigned binaries such as TWRP/Magisk installed. Have you tried to flash again the stock firmware (BL/CP/AP/CSC)?
EDIT: by looking at the error it seems like your bootloader and vbmeta aren't from the same build (bootloader: DVK5, vbmeta: DVL2), I highly suggest you to flash the latest firmware available for your country
Click to expand...
Click to collapse
Am i supposed to flash only AP or all of them? I have only ever flashed AP and worked without problems but after locking the bootloader i only get the above error boot loop.

cheen11 said:
Am i supposed to flash only AP or all of them? I have only ever flashed AP and worked without problems but after locking the bootloader i only get the above error boot loop.
Click to expand...
Click to collapse
The error in your device happens for this exact reason: vbmeta partition in the AP tar can’t verify other system binaries since they’re older and you didn’t update them (DVL2 vs. DVK5). First flash the whole firmware package via Odin (BL, CP, AP and CSC), if you wanna root your device make sure you flash TWRP+a patched vbmeta image to avoid this error to happen again. Also do not relock your bootloader again while your phone has custom binaries flashed, if you wanna lock your bootloader flash the whole stock firmware package before.

BlackMesa123 said:
The error in your device happens for this exact reason: vbmeta partition in the AP tar can’t verify other system binaries since they’re older and you didn’t update them (DVL2 vs. DVK5). First flash the whole firmware package via Odin (BL, CP, AP and CSC), if you wanna root your device make sure you flash TWRP+a patched vbmeta image to avoid this error to happen again. Also do not relock your bootloader again while your phone has custom binaries flashed, if you wanna lock your bootloader flash the whole stock firmware package before.
Click to expand...
Click to collapse
Ah, once choosing all the files it worked, thanks a bunch

BlackMesa123 said:
The error in your device happens for this exact reason: vbmeta partition in the AP tar can’t verify other system binaries since they’re older and you didn’t update them (DVL2 vs. DVK5). First flash the whole firmware package via Odin (BL, CP, AP and CSC), if you wanna root your device make sure you flash TWRP+a patched vbmeta image to avoid this error to happen again. Also do not relock your bootloader again while your phone has custom binaries flashed, if you wanna lock your bootloader flash the whole stock firmware package before.
Click to expand...
Click to collapse
I dont know if im using the right files but i still get the same boot loop (https://prnt.sc/1lCk2FQEymPn) after adding twrp-3.7.0_12-2-a52sxq.img.tar to AP and vbmeta_disable.tar to USERDATA.

cheen11 said:
I dont know if im using the right files but i still get the same boot loop (https://prnt.sc/1lCk2FQEymPn) after adding twrp-3.7.0_12-2-a52sxq.img.tar to AP and vbmeta_disable.tar to USERDATA.
Click to expand...
Click to collapse
Are you flashing the patched vbmeta in the TWRP XDA thread or another one? Also the latest TWRP version is 3.7.0-3 so flash that one.

BlackMesa123 said:
Are you flashing the patched vbmeta in the TWRP XDA thread or another one? Also the latest TWRP version is 3.7.0-3 so flash that one.
Click to expand...
Click to collapse
Im using the vbmeta from this thread: https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-note10-lite-exynos.4350891/
I tried flashing that along with this: twrp-3.7.0_12-3-a52sxq.img.tar
But i still get the boot loop. Not sure if i can keep trying to re-flash these if the boot loop already happened

cheen11 said:
Im using the vbmeta from this thread: https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-note10-lite-exynos.4350891/
I tried flashing that along with this: twrp-3.7.0_12-3-a52sxq.img.tar
But i still get the boot loop. Not sure if i can keep trying to re-flash these if the boot loop already happened
Click to expand...
Click to collapse
You must use the patched vbmeta linked in the a52s TWRP thread, flash that one and you should boot fine in TWRP.

BlackMesa123 said:
You must use the patched vbmeta linked in the a52s TWRP thread, flash that one and you should boot fine in TWRP.
Click to expand...
Click to collapse
Hmm i tried using the vbmeta from this thread: https://forum.xda-developers.com/t/recovery-official-twrp-3-7-0-3-for-galaxy-a52s-5g.4488419/
But this time i got a fail with odin: https://prnt.sc/9HfVrQtC-gSO

cheen11 said:
Hmm i tried using the vbmeta from this thread: https://forum.xda-developers.com/t/recovery-official-twrp-3-7-0-3-for-galaxy-a52s-5g.4488419/
But this time i got a fail with odin: https://prnt.sc/9HfVrQtC-gSO
Click to expand...
Click to collapse
I think it has something to do with the space in “New folder” name, try to copy the TWRP tar in a path that has no spaces

BlackMesa123 said:
I think it has something to do with the space in “New folder” name, try to copy the TWRP tar in a path that has no spaces
Click to expand...
Click to collapse
Oh yeah good catch, i renamed the folder and didnt consider that it might not be updated it odin. It finally worked, thanks again for the help very much appreciated

Hmm i guess problems keep popping up. I guess its best that i just post here instead of creating a new thread. Im successfully in the TWRP UI but now i cant boot to system, it will just restart 2 times and then boot to TWRP. Also it fails to backup the boot image (with the error "Unable to mount storage") which i read in a tutorial that you were supposed to do.

cheen11 said:
Hmm i guess problems keep popping up. I guess its best that i just post here instead of creating a new thread. Im successfully in the TWRP UI but now i cant boot to system, it will just restart 2 times and then boot to TWRP. Also it fails to backup the boot image (with the error "Unable to mount storage") which i read in a tutorial that you were supposed to do.
Click to expand...
Click to collapse
As mentioned in the TWRP thread guide, you must format your data partition in TWRP in order to be able to boot back in the OS.