Yeah, You got a guide on the Telegram Group by typing in /1Yes, I know, I tried and could not flash a GSI in fastboot, can you help me?
Last edited:
Yeah, You got a guide on the Telegram Group by typing in /1Yes, I know, I tried and could not flash a GSI in fastboot, can you help me?
Thanks, do you have a link to the telegram group?
It is on the main post
TReboot into fastboot from TWRP flash vbmeta using this command line:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
We actually use fastbootd from TWRP to disable vbmeta, nothing to do with samsung.Samsung devices do not have fastboot mode, do you mean download mode?
Fastboot command you wrote, will that work from TWRP terminal?
Can I just flash//install vbmeta.img extracted from the offical firmware, from TWRP?
Thank you for your relply.We actually use fastbootd from TWRP to disable vbmeta, nothing to do with samsung.
I would recommend you to use my TWRP as it does not require any Magisk to be installed for it to work, the guy who maintains the official TWRP likes people to use Magisk for some reason.Thank you for your relply.
https://twrp.me/samsung/samsunggalaxya31.html is that means I should use their version? with due respect to your work.
The reason I'm trying to flash TWRP is to extract files resposible for IMEI number, so that I can repair my main phone, i.e. I have screen damaged galaxy a31 dual sim, want extract file(s) and put into galaxy s7 which is my main phone.
Don't know which files I need yet LoL,
Can you help?
Regards,
Giosa
You can download TWRP from GitHub releases, check it's the latest release, if you don't see it do some scroll down.@Zillion Thank you for your hard work making this custom recovery.
As i noticed you have changed TWRP with SHRP. How can I reboot to fastboot from there? I can't find it anywhere so I'm not able to flash vbmeta.
And second question, is it possible to downgrade rom from Binary 2 to Binary 1 using SHRP (bypass "sw rev check")?
How do I decrypt data partitionTeam Win Recovery Project or TWRP for short. Its a fully touch driven user interface, completely theme-able & you can change just about every aspect of the look and feel.
Now ported to the SM-A315F | SM-A315F/DS | SM-A315G/DS | SM-A315G | SM-A315N. (DS means Dual Sim, thing that doesn't matter a lot for TWRP)
Download - You'll always find the latest release in here: https://github.com/Galaxy-MT6768/android_device_samsung_a31x/releases
Known Issues / Report Issues - https://github.com/Galaxy-MT6768/android_device_samsung_a31x/issues
Telegram support group - http://t.me/a31nsxx
How to install
Flashing Disabled vbmeta (To boot a modified system)
Sources
Special thanks to:
Actual TWRP status: Bugfixing; Try at your own risk and only if you know what you're doing.
Decryption is currently not supported, the only way around it is flashing fbe_disabler and formatting data which leaves your /data unencrypted.
I started working on a common for mt6768 (a31 & a41), it was not the best thing but the lineageos recovery status is fully booting and working, even with the adb sideload that twrp does not have fixed. After some builds the OpenGL symlink started to fail without an apparent reason, right now I left this a31 lineageos project on the side.Well this is the start though... Which is a good thing, as long this specific device is supported to run twrp now, i would expect more developers would port a custom roms for this device in the future considering the official site of twrp includes this device plus the specific device starts to be left out for future updates and its forever stuck on android 12 except future security updates, unless you custom rom this device and overclock, since one ui 4.1 is buggy and unoptimized lol.. This thing is still capable
I am not responsible for any bricked imei, when flashing TWRP backup the EFS & NVRAM partitions to be safe, do not root until having an actually good working backup, if you signal goes restore your backup, if you didn't have a previous backup I got a fix for you , flash your firmware as always but on the CP slot in Odin Flash Tool get the CP slot from a CUD4 firmware corresponding your CSC code.
[Boot Into Download mode by inserting an usb cable while holding both volume buttons]
Flash the latest .tar release from releases.
Hold the recovery combination (Volume Up + Power) while the .tar is flashing via the odin tool.
When booted up into TWRP go Flash and flash this zip, then go to Wipe > Format Data, all your data will be lost.
You can now boot into your system and do whatever you want.
Extract the vbmeta.img.lz4 from the AP slot in your firmware.
Remove it's lz4 compression [for Windows use lz4]:
Code:sudo apt-get install lz4 -y lz4 vbmeta.img.lz4
Reboot into fastboot from TWRP flash vbmeta using this command line:
Code:fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Actual TWRP status: Bugfixing; Try at your own risk and only if you know what you're doing.
You can download TWRP from GitHub releases, check it's the latest release, if you don't see it do some scroll down.@Zillion Thank you for your hard work making this custom recovery.
As i noticed you have changed TWRP with SHRP. How can I reboot to fastboot from there? I can't find it anywhere so I'm not able to flash vbmeta.
And second question, is it possible to downgrade rom from Binary 2 to Binary 1 using SHRP (bypass "sw rev check")?
Never heard of custom roms for A32.There's no rom for A31, just for A30 and A32 just don't ask me why... A31 seems like a forgotten phone
U can use GSI, someone booted A51 GSI successfully on A31. Search Nippon GSI on TG.Thanks for doing something for A31 (the forgotten phone). I'll be test as soon as possible. It's a pity there is no rom for flashing through TWRP though.