Develop Bugs

sideload failed

i was rooted with twrp custom recovery installed. i wanted to unroot my phone so i flash the recovery and locked he bootloader again and now im trying to sideload the latest oos to my phone but it keeps failing. everytime i plug my device in i get a popup saying to insatll device drivers and when i let it do it abd its successful i still get a sideload failed error. what am i doing wrong?

envious86 said:
i was rooted with twrp custom recovery installed. i wanted to unroot my phone so i flash the recovery and locked he bootloader again and now im trying to sideload the latest oos to my phone but it keeps failing. everytime i plug my device in i get a popup saying to insatll device drivers and when i let it do it abd its successful i still get a sideload failed error. what am i doing wrong?
Click to expand...
Click to collapse
- Unlock the BL again
- Flash modded TWRP
- Flash stock OOS rom using TWRP (TWRP will be replaced by stock recovery!)
-Check if everything wroks as it should
-Relock the BL
-DONE

LS.xD said:
- Unlock the BL again
- Flash modded TWRP
- Flash stock OOS rom using TWRP (TWRP will be replaced by stock recovery!)
-Check if everything wroks as it should
-Relock the BL
-DONE
Click to expand...
Click to collapse
probably a stupid question but how do i unlock the bootloader again?

envious86 said:
probably a stupid question but how do i unlock the bootloader again?
Click to expand...
Click to collapse
Just like the time before.
fastboot oem unlock

LS.xD said:
Just like the time before.
fastboot oem unlock
Click to expand...
Click to collapse
OK I'll try thanks.

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!!!

Security Update

Hey guys, I just recently got a Google pixel XL.
I played around for a few days a then decided to go back to factory image ....stock everything. Using ADB platform-tools did a flash-all.bat then relocked the bootloader
Now I'm good to go....so I thought. it cant complete the first security update. It says "unable to complete installation”. Any help will be much appreciated.

Have you tried to ADB it back to stock? That's how I do it

yeah my bad.......i wrote TWRP I was meaning ADB platform-tools. But yes I returned to a stock image. I really don't know what to do.

killermankrew said:
Hey guys, I just recently got a Google pixel XL.
I played around for a few days a then decided to go back to factory image ....stock everything. Using ADB platform-tools did a flash-all.bat then relocked the bootloader
Now I'm good to go....so I thought. it cant complete the first security update. It says "unable to complete installation”. Any help will be much appreciated.
Click to expand...
Click to collapse
When you did the flash-all was the -w in the flash-all.bat file?

No w or. -w. Would that matter? I guessing so since you mentioned it. Please elaborate

By
I rooted the phone using TWRP and magjic. <misspelled. Then tried a custom kernel. Something went wrong....had bootloop. So I flashed-all.bat.
I then did a factory reset. .
I think I'ma have to redo everything with all new file downloads(images) and reinstall platform tool too.
Oh also relocked the bootloader.

Be sure to unlock again before messing with anything else.
Sent from my Pixel XL using Tapatalk

killermankrew said:
No w or. -w. Would that matter? I guessing so since you mentioned it. Please elaborate
Click to expand...
Click to collapse
This line in the flash-all.bat file has the -w:
fastboot -w update image-marlin-PQ3A.190605.003.zip
The -w in the flash-all, will erase all data (factory reset).
If you remove the -w from the flash-all, your data and the internal storage are not wiped.
When relocking the bootloader it is, extremely, important the the phone be 100 present stock before relocking it.
Some, have bricked their phone because they relocked the bootloader without returning the phone to stock [No root (magic), Custom ROM or Custom Kernel].
A Factory reset or flash-all with the -w ensures the phone is 'out of the box' stock.
This guide might help: [Guide] Pixel XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + by Homeboy76

It obvious it's not back to 100% stock. I scared now to try and re unlock the bootloader. I don't know what to do.
Is there a chance I could unlock it again without ?

killermankrew said:
It obvious it's not back to 100% stock. I scared now to try and re unlock the bootloader. I don't know what to do.
Is there a chance I could unlock it again without ?
Click to expand...
Click to collapse
I do not know.

Good news I unlocked the bootloader without a problem.
But that's all now I need or want to reroot and get the latest updates. I know there are tutorials on this site or links to other sites. In your opinion which would you prefer?

killermankrew said:
Good news I unlocked the bootloader without a problem.
But that's all now I need or want to reroot and get the latest updates. I know there are tutorials on this site or links to other sites. In your opinion which would you prefer?
Click to expand...
Click to collapse
Is Settings ==> System ==> Advance ==> Developer options ==> OEM unlocking: Allow bootloader to be unlocked on? If yes do #4 'wipe data' to return your phone to 'out of the box' stock condition with the latest factory image. Then do #7 or #8 to root/reroot.

ok....i downloaded all new files and reinstalled adb fastboot.
ive unlocked the bootloader, its in debugging mode, but when i do a flash-all.bat this is what i get.
[FONT="Arial Black"C:\Users\Administrator>"C:\Android fast adb\platform-tools\marlin-pq3a.190605.003\flash-all.bat"
fastboot: error: cannot load 'bootloader-marlin-8996-012001-1904111134.img': No such file or directory
rebooting into bootloader OKAY [ 0.015s]
Finished. Total time: 0.018s
fastboot: error: cannot load 'radio-marlin-8996-130281-1903110834.img': No such file or directory
rebooting into bootloader OKAY [ 0.010s]
Finished. Total time: 0.011s
W/ziparchive( 6416): Unable to open 'image-marlin-pq3a.190605.003.zip': No such file or directory
fastboot: error: failed to open zip file 'image-marlin-pq3a.190605.003.zip': I/O error
Press any key to exit...][/FONT]
HELP

Last post on this thread. I was able to flash-all.bat using powershell only. i coundn't get command-line to work no matter what.
so im up to date now time to root!

Glad to read that.

killermankrew said:
Last post on this thread. I was able to flash-all.bat using powershell only. i coundn't get command-line to work no matter what.
so im up to date now time to root!
Click to expand...
Click to collapse
Good job

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.