[ROM] [11.0] [UNOFFICIAL] Project Sakura [ARM64] [Galaxy A20]

[CawfeeOG]

So you weren't supposed to use the OTA.

What you want to try is :
- Boot into TWRP
- Backup Data
- Wipe System/Data/Dalvik/Cache/Vendor
- Reflash Sakura 5.R April 2021
- Flash GApps
- Restore Data
- Reboot System

This should bring your device to back to working order.

I had to flash stock firmware... couldn't even get to TWRP.
Now I can't even get TWRP to flash successfully with Odin so I'm stuck.

No matter what I try, I am getting an error after flashing TWRP in Odin and trying to reboot to recovery manually.
The error is in download mode:

Recovery: Error validating footer. (Something cut off here because of the A20's front camera)
CUSTOM RECOOVERY
VBMETA A205WVLS7BUA1, 37649171R

 

[KineSight]

I had to flash stock firmware... couldn't even get to TWRP.
Now I can't even get TWRP to flash successfully with Odin so I'm stuck.

No matter what I try, I am getting an error after flashing TWRP in Odin and trying to reboot to recovery manually.
The error is in download mode:

Recovery: Error validating footer. (Something cut off here because of the A20's front camera)
CUSTOM RECOOVERY
VBMETA A205WVLS7BUA1, 37649171R

Did you make sure that Bootloader OEM unlock is showing in Developer Options before flashing TWRP in ODIN?

 

[IamTheBRAVE]

Seems like a vbmeta.img error, maybe try flashing the one from the rooting/flashing guide by Physwizz?

 

[lochstar]

So you weren't supposed to use the OTA.

Glad I read this, I was just about to do it.

 

[CawfeeOG]

Did you make sure that Bootloader OEM unlock is showing in Developer Options before flashing TWRP in ODIN?

Yes, that is unlocked.

Seems like a vbmeta.img error, maybe try flashing the one from the rooting/flashing guide by Physwizz?

Thank you, that is what solved it. I assume it's something to do with vbmeta.img and boot.img not being included with the new TWRP, should I be re-compressing a new tar file with those files included in it to upgrade to latest TWRP for A20?

 

[IamTheBRAVE]

Yes, that is unlocked.

Thank you, that is what solved it. I assume it's something to do with vbmeta.img and boot.img not being included with the new TWRP, should I be re-compressing a new tar file with those files included in it to upgrade to latest TWRP for A20?

Yeah, try that.

 

[lochstar]

So.. any acknowledgement of NFC not working?

 

[KineSight]

Yes, that is unlocked.

Thank you, that is what solved it. I assume it's something to do with vbmeta.img and boot.img not being included with the new TWRP, should I be re-compressing a new tar file with those files included in it to upgrade to latest TWRP for A20?

To update TWRP, you can flash the 'twrp.img' to the Recvoery slot in TWRP. No need to reflash in ODIN.

 

[KineSight]

So.. any acknowledgement of NFC not working?

My SM-A205F doesn't even have NFC.

 

[CawfeeOG]

Any reason 5G wifi is disabled in this ROM?

I noticed that on stock firmware 5G networks show, but for some reason in Project Sakura 5G is disabled. Is there a way to turn this on anywhere that I am missing?

 

[burningcreation]

I noticed I'm not able to cast from YouTube to my Chromecast on this ROM.

 

[IamTheBRAVE]

Would you say May 13th update is better than the last one or is it a security patch update only?

 

[burningcreation]

Would you say May 13th update is better than the last one or is it a security patch update only?

I'd like to know this too. I'm not sure I want to update just yet.

 

[KineSight]

I'd like to know this too. I'm not sure I want to update just yet.

@IamTheBRAVE @burningcreation I suggest you not to update yet.

There is currently an issue with the Blur on Lockscreen and Notification Panel.

The ProjectSakura Devs are going to push out an update soon that will fix this.

There are some cool new features that came with this update that you can find here - https://projectsakura.xyz/posts/5.R-May-2021-update.html

 

[Laxmi128]

Sound seems to be broken on the latest build. Even when I kept the settings at 100 %, the sound is like 40% compared to the stock one? Any fix? Or is it just me? Thanks in advance.

 

[KineSight]

Sound seems to be broken on the latest build. Even when I kept the settings at 100 %, the sound is like 40% compared to the stock one? Any fix? Or is it just me? Thanks in advance.

Try Viper4Android, you can find it on the Magisk App modules list.

 

[AxelCC]

You also need to wipe Vendor.

How many times did it reboot before you stopped it ?

What exact name and version of NikGapps (Provide file name) ?

I solved the problem by not installing the NickGapps (NikGapps-basic-arm64-11-20210501-signed.zip), and rooting after installing the rom, after it booted i install the gapps and works well

 

[KineSight]

I solved the problem by not installing the NickGapps (NikGapps-basic-arm64-11-20210501-signed.zip), and rooting after installing the rom, after it booted i install the gapps and works well

Great Stuff.

 

[Laxmi128]

Sound seems to be broken on the latest build. Even when I kept the settings at 100 %, the sound is like 40% compared to the stock one? Any fix? Or is it just me? Thanks in advance.

Try Viper4Android, you can find it on the Magisk App modules l

Try Viper4Android, you can find it on the Magisk App modules list.

Thank you, now it's much better than before!

 

[KineSight]

Cool .