Develop Bugs

Can't update software - file system may be corrupted.

Went through the whole process to get an unlocked phone working on verizon - unlock bootloader, TWRP, s-off, etc.
Went back and flashed stock 1.21 recovery since that's what my phone was on, did a factory reset after getting this error the first time.
Still getting the error -
Code:
Can't update software. There was an unexpected error and the file system may be corrupted. Please contact HTC support for further assistance.
Before flashing the stock recovery I did try to restore the recovery/system image from TWRP's system backup, not sure if that has anything to do with it.

noahjk said:
Went through the whole process to get an unlocked phone working on verizon - unlock bootloader, TWRP, s-off, etc.
Went back and flashed stock 1.21 recovery since that's what my phone was on, did a factory reset after getting this error the first time.
Still getting the error -
Code:
Can't update software. There was an unexpected error and the file system may be corrupted. Please contact HTC support for further assistance.
Before flashing the stock recovery I did try to restore the recovery/system image from TWRP's system backup, not sure if that has anything to do with it.
Click to expand...
Click to collapse
Try flashing this zip in download mode (fastboot flash zip pathtozip.zip)
https://drive.google.com/file/d/0B8OH6sFjVE1ld1ptNTFEaEc3Rms/view?usp=docslist_api
Reboot and try ota again.
This will flash the unlocked radio though, so you'll need to reperform the steps from the Verizon thread after you do this. please report back if it works.

jollywhitefoot said:
Try flashing this zip in download mode (fastboot flash zip pathtozip.zip)
https://drive.google.com/file/d/0B8OH6sFjVE1ld1ptNTFEaEc3Rms/view?usp=docslist_api
Reboot and try ota again.
This will flash the unlocked radio though, so you'll need to reperform the steps from the Verizon thread after you do this. please report back if it works.
Click to expand...
Click to collapse
Worked great. Thanks!
For anyone else following this thread, if you're flashing the zip and see this:
Code:
remote: 90 hboot pre-update! please flush image again immediately
Just flash again right away and it'll work fine.

noahjk said:
Worked great. Thanks!
For anyone else following this thread, if you're flashing the zip and see this:
Code:
remote: 90 hboot pre-update! please flush image again immediately
Just flash again right away and it'll work fine.
Click to expand...
Click to collapse
I'm glad that worked for you. I went ahead and wrote a guide in case anyone else has trouble. It includes the message about reflashing.
http://forum.xda-developers.com/htc-10/how-to/guide-how-to-ota-receive-corrupt-message-t3378187

international version
jollywhitefoot said:
Try flashing this zip in download mode (fastboot flash zip pathtozip.zip)
Reboot and try ota again.
This will flash the unlocked radio though, so you'll need to reperform the steps from the Verizon thread after you do this. please report back if it works.
Click to expand...
Click to collapse
Hey there, Ive come across your post after experiencing the same problem on a HTC10 international version. Can I ask if the file that you've provided work on the international version? Also do I have to restore my twrp backup as well? Thanks a lot!

Hi there, same problem: "Can't update software. There was an unexpected error and the file system may be corrupted. Please contact HTC support for further assistance."
Htc 10 unlocked, v. 1.90.401.5
I followed post #2 without success.
Some idea please?

Help, please! ?

I gave up with the same problem and switched to a custom rom - Leedroid.

Thank you Simplici. So no chance with official stock to solve this problem?

last_nooby said:
Thank you Simplici. So no chance with official stock to solve this problem?
Click to expand...
Click to collapse
There is. You could flash an appropriate RUU if available. Although it'll wipe all you're data, it should restore the phone to a status, making an OTA update possible again. Those errors could be caused by a once r/w mounted system partition, or a tripped dm-verity flag. You'll find more on this issues and help of how to properly restore over at the Guides section of this forum.
Edit: here's the link regarding the corrupt system partition error: http://forum.xda-developers.com/htc...o-ota-receive-corrupt-message-t3378187/page43
Sent from my htc_pmeuhl using XDA Labs

jollywhitefoot said:
Try flashing this zip in download mode (fastboot flash zip pathtozip.zip)
https://drive.google.com/file/d/0B8OH6sFjVE1ld1ptNTFEaEc3Rms/view?usp=docslist_api
Reboot and try ota again.
This will flash the unlocked radio though, so you'll need to reperform the steps from the Verizon thread after you do this. please report back if it works.
Click to expand...
Click to collapse
can some one reload the file again? there's no file in google drive

Help needed ! stuck in Bootloop

Hey guys. Today I tried rooting for the first time using this guide
In the third step of the article "3.Flashing TWRP and Rooting via TWRP" I pressed cancel when it asks for an encryption password(I hadn't put one yet). I also flashed the english TWRP( Recovery file) and not the one provided in the article . Now the phone just wont boot. Whenever I try to boot it, it gives me the error message:
"Your device has been unlocked and cannot be trusted.
ID: N/A"
And TWRP comes up everytime .
When i try booting from factory it shows:
"Your device has been unlocked and cannot be trusted.
ID: bad key"
and TWRP comes up.
The phone is still recognized in adb.I still haven't flashed SuperSU if that helps.
Should i Flash stock recovery and try again ?
Please send help, guys.

porthumor said:
Hey guys. Today I tried boot for the first time using this guide
In the third step of the article "3.Flashing TWRP and Rooting via TWRP" I pressed cancel when it asks for a password. I also flashed the english TWRP( Recovery file) and not the one provided in the article . Now the phone just wont boot. Whenever I try to boot it, it gives me the error message:
"Your device has been unlocked and cannot be trusted.
ID: N/A"
And TWRP comes up everytime .
When i try booting from factory it shows:
"Your device has been unlocked and cannot be trusted.
ID: bad key"
and TWRP comes up.
The phone is still recognized in adb.I still haven't flashed SuperSU if that helps.
Should i Flash stock recovery and try again ?
Please send help, guys.
Click to expand...
Click to collapse
I have similar problem like yours. The solution to boot your drvice. If your in twrp go to advance - reboot - bootloader. And in bootloader menu click start. And your phone now is booted
This is a alternative solution. But it wont damage your device. Trust me

Kap_Tutan said:
I have similar problem like yours. The solution to boot your drvice. If your in twrp go to advance - reboot - bootloader. And in bootloader menu click start. And your phone now is booted
This is a alternative solution. But it wont damage your device. Trust me
Click to expand...
Click to collapse
Tried this . It displays :
"Your device has been unlocked and cannot be trusted.
ID: bad key"
Reboots to show :
"Your device has been unlocked and cannot be trusted.
ID: N/A"
and goes into TWRP .

I think you need to flash new logo bin from here
https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153

mijing said:
I think you need to flash new logo bin from here
https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153
Click to expand...
Click to collapse
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.

porthumor said:
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
Click to expand...
Click to collapse
I am not sure but
Yes
If showing "Your device has been unlocked and cannot be trusted"
I fix my device flashing new logo bin .

mijing said:
I am not sure but
Yes
If showing "Your device has been unlocked and cannot be trusted"
I fix my device flashing new logo bin .
Click to expand...
Click to collapse
Well thank you for the tip but that's not the problem here.The problem is that my phone never boots into OS ,it is stuck in recovery.Any Indication as to why would be a huge help !

porthumor said:
Well thank you for the tip but that's not the problem here.The problem is that my phone never boots into OS ,it is stuck in recovery.Any Indication as to why would be a huge help !
Click to expand...
Click to collapse
Are you sure OS is even there?

flashallthetime said:
Are you sure OS is even there?
Click to expand...
Click to collapse
I don't think I messed with the OS . I just unlocked the bootloader and flashed TWRP without flashing SuperSU.(done it for the first time for my Moto Z play). Used Wipe to clear davlik,cache and that's it.haven't done anything in the recovery since then.
The only thing i remember messing up was to not input the encryption key when it prompt me for it by clicking cancel.
I've read in some forums that it doesn't boot if it doesn't have SuperSU flashed,but I'm not sure if it's safe since i don't exactly know what might or might now permanently brick my phone.
Also some forums had something to do with patching the kernels (don't know if that's what you call it) but i don't know if it's a safe thing to do since it might also permanently brick my phone.
Running Nougat April Security Patch.

porthumor said:
I don't think I messed with the OS . I just unlocked the bootloader and flashed TWRP without flashing SuperSU.(done it for the first time for my Moto Z play). Used Wipe to clear davlik,cache and that's it.haven't done anything in the recovery since then.
The only thing i remember messing up was to not input the encryption key when it prompt me for it by clicking cancel.
I've read in some forums that it doesn't boot if it doesn't have SuperSU flashed,but I'm not sure if it's safe since i don't exactly know what might or might now permanently brick my phone.
Also some forums had something to do with patching the kernels (don't know if that's what you call it) but i don't know if it's a safe thing to do since it might also permanently brick my phone.
Running Nougat April Security Patch.
Click to expand...
Click to collapse
You used the Chinese TWRP originally? Now you have alberto97 TWRP? Is this correct?
I would flash a custom ROM, why I'm saying that is it's far safer flashing a zip ROM than trying to flash the stock firmware.
Again I will remind people the flashing bootloaders on moto devices will inevitably cause hard bricks if you downgrade and the accept an ota.
---------- Post added at 06:47 PM ---------- Previous post was at 06:39 PM ----------
The only solution and this applies only if you want to remain on the stock ROM.
Download the retail firmware and only manually flash the boot.img, the 10 sparsechunks and the OEM.img.
Do not use rsdlite!!
This should boot your phone.

flashallthetime said:
You used the Chinese TWRP originally? Now you have alberto97 TWRP? Is this correct?
Click to expand...
Click to collapse
Yes,exactly.
flashallthetime said:
I would flash a custom ROM, why I'm saying that is it's far safer flashing a zip ROM than trying to flash the stock firmware.
Click to expand...
Click to collapse
Which Custom ROM do you think is the safest possible alternative?
flashallthetime said:
Again I will remind people the flashing bootloaders on moto devices will inevitably cause hard bricks if you downgrade and the accept an ota.
Click to expand...
Click to collapse
Can you explain this a bit better ? I would like to understand what i'm getting into !
flashallthetime said:
The only solution and this applies only if you want to remain on the stock ROM.
Download the retail firmware and only manually flash the boot.img, the 10 sparsechunks and the OEM.img.
Do not use rsdlite!!
This should boot your phone.
Click to expand...
Click to collapse
Could you,if possible, link to me to the respective article ? Do I need to Get the firmware for Nougat or does it depend on security patch as well?
Gotcha,No rsdlite !

porthumor said:
Yes,exactly.
Which Custom ROM do you think is the safest possible alternative?
Can you explain this a bit better ? I would like to understand what i'm getting into !
Could you,if possible, link to me to the respective article ? Do I need to Get the firmware for Nougat or does it depend on security patch as well?
Gotcha,No rsdlite !
Click to expand...
Click to collapse
I would install the aosp ROM as it is bare bones android.
As for bootloaders, when you receive an ota it flashes a new bootloader.
What some folks have done is because they feel like a new ota isn't working to their liking, they have downgraded their firmare, either by flashing the firmware package that can be downloaded. They flash the entire package including bootloader, what this does is set up a perfect hard brick scenerio for moto devices.
They accept an ota or for reasons that are beyond uderstanding, sideload the package and bam as soon as they restart there device it bricks their device due to the mismatched bootloaders.
You are unlocked and the easiest way to prevent hard bricks is to for go flashing firmware.
I'm running validus 7.1.2 on the original bootloader that was installed on MM.
---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ----------
I'm attempting to build a stock flashable TWRP stock 7.1.1 ROM.
You may also flash any flashable TWRP stock 7 rom, either bye me or dedracks

flashallthetime said:
I would install the aosp ROM as it is bare bones android.
As for bootloaders, when you receive an ota it flashes a new bootloader.
What some folks have done is because they feel like a new ota isn't working to their liking, they have downgraded their firmare, either by flashing the firmware package that can be downloaded. They flash the entire package including bootloader, what this does is set up a perfect hard brick scenerio for moto devices.
They accept an ota or for reasons that are beyond uderstanding, sideload the package and bam as soon as they restart there device it bricks their device due to the mismatched bootloaders.
You are unlocked and the easiest way to prevent hard bricks is to for go flashing firmware.
I'm running validus 7.1.2 on the original bootloader that was installed on MM.
---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ----------
I'm attempting to build a stock flashable TWRP stock 7.1.1 ROM.
You may also flash any flashable TWRP stock 7 rom, either bye me or dedracks
Click to expand...
Click to collapse
Is it fine if i go ahead with this and see if it works ?
I will try to flash a custom ROM if it doesn't.

porthumor said:
Is it fine if i go ahead with this and see if it works ?
I will try to flash a custom ROM if it doesn't.
Click to expand...
Click to collapse
That's fine and it's my ROM lol.
You may want to format your data but first try to flash the ROM and see if it boots.
That Chinese TWRP is a nasty thing

porthumor said:
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
Click to expand...
Click to collapse
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite

Kap_Tutan said:
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Click to expand...
Click to collapse
Rsdlite sucks, never flash any firmware with resdlite unless you know which lines need to be removed from the text file that tells rsdlite what to flash.
manually flashing firmware is IMO much safer and all you need to flash is the boot.img all the spareschunks and oem.img

Kap_Tutan said:
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Click to expand...
Click to collapse
I did what you had asked me to ,unfortunately it doesn't work. I would be happy just being able to boot using the above method.
Thanks for the suggestion tho !
flashallthetime said:
That's fine and it's my ROM lol.
You may want to format your data but first try to flash the ROM and see if it boots.
That Chinese TWRP is a nasty thing
Click to expand...
Click to collapse
I'll try to get this done by tomorrow and see if it helps !

porthumor said:
I did what you had asked me to ,unfortunately it doesn't work. I would be happy just being able to boot using the above method.
Thanks for the suggestion tho !
I'll try to get this done by tomorrow and see if it helps !
Click to expand...
Click to collapse
Hopefully it does

flashallthetime said:
Rsdlite sucks, never flash any firmware with resdlite unless you know which lines need to be removed from the text file that tells rsdlite what to flash.
manually flashing firmware is IMO much safer and all you need to flash is the boot.img all the spareschunks and oem.img
Click to expand...
Click to collapse
When flashing the boot the sparsechunk and the oem then can i able to receive a OTA in my device? Or do i need to flash the recovery.img also?
Anyways thanks bro i learned again something from you

Kap_Tutan said:
When flashing the boot the sparsechunk and the oem then can i able to receive a OTA in my device? Or do i need to flash the recovery.img also?
Anyways thanks bro i learned again something from you
Click to expand...
Click to collapse
You also need to flash the recovery image as well

BAC-L21C full firmware

i guess i got my new nova 2 plus bricked after trying to install twrp recovery
bootloader unlocked but now its stuck or bricked
i cant find rom to flash it or even in fastboot
hope anyone do have a link for a full firmware and how to flash it
thank you

firmware
crazylife said:
i guess i got my new nova 2 plus bricked after trying to install twrp recovery
bootloader unlocked but now its stuck or bricked
i cant find rom to flash it or even in fastboot
hope anyone do have a lick for a full firmware and how to flash it
thank you
Click to expand...
Click to collapse
i have done the same thing, there is a website combinefile,com there u can download the full firmware of ur device, but i am teling u the sdcard dload method does not work, i have tried every possible way, plz keep me updated if u found a solution for urs, also u can download the firmware in easy firmware website, but it is exclusive means u have to have a paid membership.

bejan89 said:
i have done the same thing, there is a website combinefile,com there u can download the full firmware of ur device, but i am teling u the sdcard dload method does not work, i have tried every possible way, plz keep me updated if u found a solution for urs, also u can download the firmware in easy firmware website, but it is exclusive means u have to have a paid membership.
Click to expand...
Click to collapse
I know its not working... Thats why i was looking for full firmware and how to flash it by flashtool
Hope someone can help us abiut that soon

crazylife said:
I know its not working... Thats why i was looking for full firmware and how to flash it by flashtool
Hope someone can help us abiut that soon
Click to expand...
Click to collapse
i mentioned earlier where u can get the full firmware, it is a 3.1 GB file, and here are the methods i have tried
sdcard dload force flash
extracting the images and flash them individually using adb, for that u can use huawei update extractor, and for going into fastboot mod, plug in your phone and press power+volume down, tell me if u had any luck booting up

bejan89 said:
i mentioned earlier where u can get the full firmware, it is a 3.1 GB file, and here are the methods i have tried
sdcard dload force flash
extracting the images and flash them individually using adb, for that u can use huawei update extractor, and for going into fastboot mod, plug in your phone and press power+volume down, tell me if u had any luck booting up
Click to expand...
Click to collapse
Couldnt find any full rom.. Its all ota in there
About 400mb only
If u have it upload it and let me trying fixing the issue

crazylife said:
Couldnt find any full rom.. Its all ota in there
About 400mb only
If u have it upload it and let me trying fixing the issue
Click to expand...
Click to collapse
go to combinefile.com homepage click on firmware folder>huawei firmware>B series huawei>Barca-L21
there are two firmwares uploaded there, c185b102 and c185b140
Barca-L21 is same as BAC-L21, downloaded it and extract the zip you will get the BAC-L21 folder inside it

https://drive.google.com/open?id=1tGuu5Y6Qfo5baHjEO_-tJ3irXAXIWa53
here is the full rom

bejan89 said:
https://drive.google.com/open?id=1tGuu5Y6Qfo5baHjEO_-tJ3irXAXIWa53
here is the full rom
Click to expand...
Click to collapse
Thank you... Too bad couldn't flash it... Seems no devs available for this mobile to make our mistakes fixed easly...
I will send it to the service and dunno how much it will cust

crazylife said:
Thank you... Too bad couldn't flash it... Seems no devs available for this mobile to make our mistakes fixed easly...
I will send it to the service and dunno how much it will cust
Click to expand...
Click to collapse
you cant flash it unless you have the exact same rom u had before u brick ur phone, which was bac l21 b150.....d002, and so far i cant find that firmware online

why i cannot flash anything with bootloader ?!

I've unlocked my bootloader but now each time i try to use the bootloader it won't do anything !! it keeps showing me FAILED (remote: unknown command) ! does anyone facing the same problem ? because i cannot even stock flash my phone !

https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
This guide should help you

Dielahn said:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
This guide should help you
Click to expand...
Click to collapse
I've done everything before and I rooted my phone but now I'm trying to stock flash 8.1 but it won't do it and neither will let me even flash anything ! I even tried to relock my bootloader and unlock it again it won't even let me do that ! all that it shows is the error that i've mentioned before

Khalid_am said:
I've done everything before and I rooted my phone but now I'm trying to stock flash 8.1 but it won't do it and neither will let me even flash anything ! I even tried to relock my bootloader and unlock it again it won't even let me do that ! all that it shows is the error that i've mentioned before
Click to expand...
Click to collapse
Did you unlock critical?

Khalid_am said:
I've done everything before and I rooted my phone but now I'm trying to stock flash 8.1 but it won't do it and neither will let me even flash anything ! I even tried to relock my bootloader and unlock it again it won't even let me do that ! all that it shows is the error that i've mentioned before
Click to expand...
Click to collapse
Maybe you need to update platform tools. I just went from 8.0 to 8.1 and i couldn't flash the flash-all for some odd reason but i got it to work by sideload the ota zip.

murphyjasonc said:
Did you unlock critical?
Click to expand...
Click to collapse
No and everytime i try to do that it keeps telling me the same error

Dielahn said:
Maybe you need to update platform tools. I just went from 8.0 to 8.1 and i couldn't flash the flash-all for some odd reason but i got it to work by sideload the ota zip.
Click to expand...
Click to collapse
i downloaded the latest version

Khalid_am said:
i downloaded the latest version
Click to expand...
Click to collapse
Can you explain exact steps you are taking so we can help you better?

Dielahn said:
Can you explain exact steps you are taking so we can help you better?
Click to expand...
Click to collapse
I downloaded the platform-tools and started the cmd from the platform folder then each time i try to flash anything or interact with the bootloader it just keeps showing me this message (FAILED (remote: unknown command)

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.