Unlock oem and flash 908b's firmwares AP on odin 3 or 4, and flash vbmeta.tar
[TWRP][Unofficial] TWRP for Samsung Galaxy A90 5G [A908B/N/O]
- Thread starter PseudonymXIV
- Start date
Gonna chime back in on a thing or two.
It's been difficult finding sufficient information here and there; to do everything alone.
Which includes compiling the kernel, which has been successful to compile a kernel alone, but it may seem that this is not the way to properly build TWRP for a device, so that had been halted.
Beyond that, it would seem futile of me to attempt compiling custom ROMs, bringing up security updates, or upstreaming a kernel.
So the motivation to develop for the device has dwindled, and now I just find a half-ass TWRP build is sufficient for me.
Which in my opinion with the latest Magisk update, that the installer still seeks the stock recovery image, that it may be worthwhile to patch the TWRP image.
The footnote to this is, that people have priorities. And that persistent failure without any conclusive idea on how to develop your environment just doesn't seem worthwhile.
For what it's worth, device tree for twrp is on TeamWins github, if anyone wants to perfect it.
I just don't find much viability in spending weeks back-to-back, research, trial and error, resulting in the same failure without sight of success.
It's been difficult finding sufficient information here and there; to do everything alone.
Which includes compiling the kernel, which has been successful to compile a kernel alone, but it may seem that this is not the way to properly build TWRP for a device, so that had been halted.
Beyond that, it would seem futile of me to attempt compiling custom ROMs, bringing up security updates, or upstreaming a kernel.
So the motivation to develop for the device has dwindled, and now I just find a half-ass TWRP build is sufficient for me.
Which in my opinion with the latest Magisk update, that the installer still seeks the stock recovery image, that it may be worthwhile to patch the TWRP image.
The footnote to this is, that people have priorities. And that persistent failure without any conclusive idea on how to develop your environment just doesn't seem worthwhile.
For what it's worth, device tree for twrp is on TeamWins github, if anyone wants to perfect it.
I just don't find much viability in spending weeks back-to-back, research, trial and error, resulting in the same failure without sight of success.
Right back to it, I did experimenting to build a kernel inline(To modify Kernel to allow Google MTP drivers) which did build successfully as far as a compile went, but with aosp manifest, I couldn't get TWRP to boot, so refreshing the environment to replicate a build on omni sources.(Which does boot)(Going from shallow to complete sources)
Last time I tried AOSP sources, bootlooped and TWRP was never accessed.
Omni however is a breeze, so attempting to compile kernel inline with the build itself, so hopefully MTP can be enabled in recovery, and honestly, it's my only major fault in this build, I want the ease for the end-user.
Once that's working, I'll update the fstab to list crucial partitions, which you may have noticed aren't present on 'backup'.
I'll keep you updated.
Last time I tried AOSP sources, bootlooped and TWRP was never accessed.
Omni however is a breeze, so attempting to compile kernel inline with the build itself, so hopefully MTP can be enabled in recovery, and honestly, it's my only major fault in this build, I want the ease for the end-user.
Once that's working, I'll update the fstab to list crucial partitions, which you may have noticed aren't present on 'backup'.
I'll keep you updated.
Last edited:
Update: Had a lot of assistance from a developer to nudge me in the correct direction.
So, many thanks to that developer, and another developer that I was able to cherry-pick commits from their repo.
Latest Update for this project for the R3Q, Standalone Kernel has been compiled, with MTP changes implemented(Thanks to the cherrypick) into said Kernel.
I've yet to compile the TWRP with this Kernel, once it had been compiled and tested, I'll update the link and add a new message to this thread.
So, many thanks to that developer, and another developer that I was able to cherry-pick commits from their repo.
Latest Update for this project for the R3Q, Standalone Kernel has been compiled, with MTP changes implemented(Thanks to the cherrypick) into said Kernel.
I've yet to compile the TWRP with this Kernel, once it had been compiled and tested, I'll update the link and add a new message to this thread.
Please, share the device tree and kernel source. Not releasing them goes agaisn't the GPL license.
bagaimana perkembangannya, apakah layak untuk diuji?
bagaimana perkembangannya, apakah layak untuk diuji?
I have in the past compiled a standalone kernel that could be used for building as a prebuilt inside a new recovery build, sources are available, and I'd have to attempt to correct issues that arise from this.
More on testing anything, currently the device is out of my possession for the foreseeable future, so I cannot build or test it until it is within my possession, which I shall announce when it is, but for now due to that, I cannot proceed anywhere until that time.
But yeah, sources are available, I'd invite anyone that would like to take helm, to do so if they wished.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1
I have in the past compiled a standalone kernel that could be used for building as a prebuilt inside a new recovery build, sources are available, and I'd have to attempt to correct issues that arise from this.
More on testing anything, currently the device is out of my possession for the foreseeable future, so I cannot build or test it until it is within my possession, which I shall announce when it is, but for now due to that, I cannot proceed anywhere until that time.
But yeah, sources are available, I'd invite anyone that would like to take helm, to do so if they wished. -
1I've decided to release my compiled build (early, little or lotta' buggy perhaps) of the Teamwin Recovery Project for the Samsung Galaxy A90 5G, build from source.
As always, flashing unsigned firmware(including this one) will permanently destroy KNOX, and irreversibly set the KNOX bit to 0x1.
(Let me know if the statement above is incorrect, but yeah, this will destroy
Currently, it is built on the 9.0 manifest targeting the A908BXXU5EVK3
So, aside from that, I'm unsure what it is completely compatible for, therefore, I would like to disclaim, that I cannot guarantee success nor the quality of the build that I have on my device, to reflect the same upon your device, and that if you decide to flash this, you are responsible for any potential damage that could theoretically be caused, you have been warned.
It works, Boots to recovery, and boots to system, and a magisk installed system, on my device, Android 12, A908BXXU5EVK3, A908B.
Installation:
- Tap 'Build Number' several times to enable Developer Options.
- Exit both 'About Phone' and 'Software Information' Page until you are on the primary settings page.
- 'Developer Options' should now be available, enter this, and enable Developer Options if it is disabled.
- Enable OEM Unlock.
- Reboot to Download Mode
- Power off the device, Hold both Volume up and down, insert data cable while holding volumes.
- Long hold volume up for several seconds to be prompted if you wish to unlock the bootloader, confirm this. Do note that confirming the bootloader unlock will format your devices data, if you have any important files you wish to retain, return to system, transfer your files to another device beforehand.
- If it is already unlocked, you do not need to do this step, as you will instead be prompted to lock the bootloader, deny this.
- Acquire the TWRP tar file present through the link in this thread.
- Acquire both the multidisabler(if required) and vbmeta.tar from Corsicanu downloads, and acquire an Odin executable.
- Launch Odin, and insert vbmeta.tar in userdata, and the twrp tar file in AP.
- Connect the Samsung A90 5G to the PC in 'Download Mode', flash.
- The Device will automatically reboot after flash by default, during the reboot, Hold Volume up and down, while USB is connected.
- Allow Modifications, Format Data, confirm by typing 'yes'; reboot to recovery.
- Install Magisk(Optional), install multidisabler.
- Reboot to system.
Currently, everything but MTP(Needs a kernel fix), and Decryption appears to work(As I'm also sure this may be a TWRP12 branch thing too); so you will need to sideload any zips, or utilise OTG Storage or SD.
All three have been tested, and provide some means to transfer files into the TWRP environment.
It may not be optimised, and may have slight issues, such as what's explained, and perhaps mounts that shouldn't be there, and mounts that aren't but should.
Download and test, at your own discretion. If you are unsure about installing this; you are not obliged to do so.
Download [TWRP A908B R3QXX]
This TWRP image is not patched with Magisk
Note: To the best of my knowledge; at least two Korean recipients have accessed the file; I have yet to hear anything from other regional models.
So my presumption would be that; perhaps it works, as success would normally yield lack of a follow-up than failure would.
But still, take caution until or unless it has been verified, flashing is still your own risk.
Device Tree Source:
Kernel Source:
GitHub - PseudonymXIV/kernel_samsung_r3q at Dev
Contribute to PseudonymXIV/kernel_samsung_r3q...
github.com
1111
New posts
-
-
[APP][6.0+] Remote Fingerprint Unlock - unlock your Windows PC with your fingerprint
- Latest: Ivan Fuentes Hagar
