yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] physwizz:
1. Download firmware from samfw

2. Use zarchiver to extract it from ap section of firmware
[Android Q&A, Help & Troubleshooting] aleksandrs117:
here

boot.img.lz4

drive.google.com

xda didnt allow to put that format file so i putted it in google drive
[Android Q&A, Help & Troubleshooting] physwizz:
Not boot.img.lz4.

I need recovery.img.lz4
[Android Q&A, Help & Troubleshooting] aleksandrs117:
Ok i will send it to u tomorow somthing happened to my pc
[Android Q&A, Help & Troubleshooting] aleksandrs117:
Ok

recovery.img.lz4

drive.google.com

here
[Android Q&A, Help & Troubleshooting] physwizz:
Unzip to find the tar file then follow the instructions.
[Android Q&A, Help & Troubleshooting] aleksandrs117:
Another thing......can you find me a rom what works with this phone?
[Android Q&A, Help & Troubleshooting] arsfr:
use a GSI... https://xdaforums.com/t/guide-gsi-installing-lineageos-or-gsi-roms-for-a127f-binary-u7.4513051/

follow this guide but do not use the twrp or kernel included, use the ones physwizz gave you...
[Android Q&A, Help & Troubleshooting] aleksandrs117:
But i have sm-a136b/dsn model....idk if this will work....
[Android Q&A, Help & Troubleshooting] physwizz:
Let's see if the twrp boots first
[Android Q&A, Help & Troubleshooting] arsfr:
it will. This works for the A125F too, and that is mediatek like your a136b.
[Android Q&A, Help & Troubleshooting] physwizz:
I ported it from a146p so we'll see what happens
[Android Q&A, Help & Troubleshooting] arsfr:
I hope you guys the best on getting twrp on this device!
[Android Q&A, Help & Troubleshooting] physwizz:
I only own a127f and a205 so I rely on lots of testers
[Android Q&A, Help & Troubleshooting] arsfr:
same thing lol but I only own the a205u not a205yn. It's surprising how I found you on both forums and how we have pretty much the same devices lol. (I have more but those are like tablets, etc)
[Android Q&A, Help & Troubleshooting] aleksandrs117:
i will try not lets pray that i will not brick my phone bcuz its my main
[Android Q&A, Help & Troubleshooting] aleksandrs117:
this is so complicated XD
[Android Q&A, Help & Troubleshooting] aleksandrs117:
my phone is stuck in bootloader...(this phones bootloader is unlocked .....press power key to continue i am pressing power key but nothing happens
[Android Q&A, Help & Troubleshooting] physwizz:
Slowly
[Android Q&A, Help & Troubleshooting] aleksandrs117:
how do i install it......i tought it wiould be like a .zip file to download it from twrp
[Android Q&A, Help & Troubleshooting] arsfr:
if it does, then you can always restore the phone using SP Flash tool or unlock tool. you can ask

This person: mvikrant97

for help to unbrick your phone. He helped a lot of people, including me.
[Android Q&A, Help & Troubleshooting] arsfr:
read the guide...
[Android Q&A, Help & Troubleshooting] moresat:
I have same device A136B, I've tryed this TWRP but it doesn't work for me. Maybe because different firmware version?

The strange with my phone is also this: same fastboot commands work other not. gevar all work and gevar parrtition-type not, getvat product also not,

fastboot --disable-verification flash vbmeta vbmeta.img

also does not work... what can be the cause? Any idea?

Have already tested 5 different cables , different drivers, different PC and different ports. I do not know what I can else do. I'm really frustrated now
[Android Q&A, Help & Troubleshooting] moresat:
Dear Phiswizz, may I ask you if you can please help me too, like you did for Aleksandrs117?
[Android Q&A, Help & Troubleshooting] physwizz:
You forgot to patch the ap file

Read the instructions
[Android Q&A, Help & Troubleshooting] moresat:
Thanks for answer maestro,but I don't understand what you mean now. I have rooted the phone with magisk so I believe I did it. But I am on a different firmware ( U5 ) and I cannot downgrade, even with the patched Odin is it possible. I tried your TWRP, but it did not work for me. I believed that the TWRP needs to match the Bootloader and Binary System, is'n it? I just asked if I send you my stock recovery file if you please would help me, like you did for Aleksandrs117, I thought was the better way. If I did something wrong with the AP file can you please tell me what and how schould I now proceed?
[Android Q&A, Help & Troubleshooting] physwizz:
Patching the ap file using the correct magisk version results in changes to boot.img and vbmeta.img.

Boot.img is needed for root and vbmeta.img is needed for twrp.

If you use the wrong magisk then boot.img will be changed but vbmeta.img won't. This is what's happening to you.

If after correctly patching the ap file it still doesn't work then I will certainly help further
[Android Q&A, Help & Troubleshooting] moresat:
I thank you for your time and help. I'll tried what you advised me to do, after that I'll report the results. I wish you a happy Easter Monday
[Android Q&A, Help & Troubleshooting] moresat:
I am ready to start now, if I understood all well I need the delta magisk first. I will reflash my phone, so to start with a clean installation; my phone is already rooted but with the official magisk. Am I right so far? My firmware is A136BXXU5CWH2, android 13, One UI 5.1

Do I need a particular version of Delta Magisk or can I use the latest one?

Do I have to stay on the same firmware or can I even upgrade to Android 14 before starting?
[Android Q&A, Help & Troubleshooting] moresat:
I've tried in every possible way, but the result is always the same. Let me first summarize what I did. I started with a clean flash of the firmware, then I patched the AP with Magisk Delta 27.0 which I then loaded with ODIN. And up to this point everything seemed fine except that after the reboot I was forced to perform a factory reset because the system wouldn't load. After this the system loaded normally, but obviously I had to reinstall Magisk (still the same: Delta 27.0). The first strange thing was this: Magisk remains stuck on the logo after launch. I waited for minutes, but nothing else happens. Regardless of this effect I believe that Magisk still works as it should, only the interface doesn't load. because after installing Adaway and Power Menu, the classic question appears on the display whether or not to grant root permissions to the apps. So I probably won't be able to install modules, but the root is there. For the moment not so dramatic

After that, following the instructions, I installed twrp with ODIN in AP, I removed the check in the settings for auto reboot, I didn't receive any errors. So I tried rebooting into recovery. to exit download mode you need to press volume down and power, as soon as the screen goes black I release the two keys and press them again immediately.

After the Samsung logo the screen goes black and nothing happens anymore. Luckily after several attempts with different key combinations I managed to at least enter download mode and after flashing the firmware again I managed to turn the phone back on. I wasted the whole day trying and trying again, but the result doesn't change: black screen, everything blocked. The same thing happened to me when I tried this TWRP 2 months ago, so I guess I did everything right that time too. Unless the problem is Delta Magisk itself? I thought about it, so I also tried the TWRP app method, just to get things out of the fire...I installed the recovery.img via the TWRP app and rebooted to recovery (Power Menu)...same result: black screen and apparently dead phone...now I have to restore everything again, firmware, apps etc etc...Amen

But at least I tried and I remain confident
[Android Q&A, Help & Troubleshooting] physwizz:
Try this magisk
[Android Q&A, Help & Troubleshooting] moresat:
I did, this Magisk Delta has the same behavior as version 27.0, but the root is there and is guaranteed to the apps anyway. However, I continued the TWRP installation procedure, reaching at the end, after rebooting into recovery, with the same black screen and blocked phone as before.
[Android Q&A, Help & Troubleshooting] moresat:
I don't care or care too much if Magisk behaves like this. Since the root works as it should, the function is fulfilled. What I'm wondering is: at point 3 of Recovery problems in the instructions it says "Did you download the recovery to match your baseband?" well the answer is obviously No! Since this recovery was built for a completely different software and binary than mine.

Are you sure this isn't the problem?
[Android Q&A, Help & Troubleshooting] physwizz:
You can't install a twrp from a different device.

You're not getting vbmeta.img error?

What is your baseband?
[Android Q&A, Help & Troubleshooting] moresat:
good morning, no I am not getting any error. I managed to get Magisk running, but not with the Delta that was always stucking on Husky Logo, but I had to flash the official Magisk 27.0

Now at least I can install the magisk modules. Root is there and everything look good for now. Unfortunately the Delta version doesn't work for me. My baseband version currently is this:

A136BXXU5CWH2 but I would like to upgrade to Android14 remaining on the same binary so that I can always downgrade if something doesn't work.

In this case the Baseband would be A136BXXU5DWK7, or you don't recommend me to Upgrade ?
[Android Q&A, Help & Troubleshooting] physwizz:
That's up to you
[Android Q&A, Help & Troubleshooting] moresat:
I remain on the android 13 so my Baseband is : A136BXXU5CWH2
[Android Q&A, Help & Troubleshooting] physwizz:
If you didn't get the vbmeta.img error then the magisk is working OK.

The problem is with the twrp.

I'll try to port another one.
[Android Q&A, Help & Troubleshooting] moresat:
Fantastic, do you need something? vbmeta.img, recovery.img or something else?
[Android Q&A, Help & Troubleshooting] physwizz:
Try this one.
[Android Q&A, Help & Troubleshooting] moresat:
Thank you, do I need to perform a factory reset or can I flash it so?
[Android Q&A, Help & Troubleshooting] moresat:
I know your instructions, but your post here (https://xdaforums.com/t/galaxy-a14-...ernels-and-twrps.4558515/reply?quote=88673847) maked me confuse. Anyway... I've tried several times but I can't launch the recovery after flashing with Odin. I've tried all possible key combinations, but it won't go into recovery. Either it reboots normally or you're left with a black screen. The good thing is that it boots, there are no bootloops. I just need a twrp for a GSI Flash, that's why I was looking for it, because this A136B doesn't have fastbootd and even though I found yesterday a script on github that allows to modify the stock recovery and activate it I still do not understand how to use it, I need time to learn. If you allow me, I tell you something. About a month ago a "David" contacted me and offered his help, it was on telegram if I remember correctly, he asked me for the vbmeta.img and the boot.img (first he asked me for the recovery.bin, but then he told me: I need the boot.img sorry no prebuild kernel in recovery.img This is the case with some devices) and that in about an hour the twrp would be ready. After that I never heard from him again... not one word, strange.. After this strange episode I started to believe that it must not be as easy as we thought. Look Phiswizz, we are more or less the same age old and my knowledge is for sure not as refined as yours, if I'm boring you or if it's too difficult we can let it go. It will mean that I will sell this phone, I could take the A146P for which I saw that you have already done several twrps, which apart from the camera seems almost identical. Little by little I'm starting to have full balls too, I don't know if it's said that way in English too. Tell me what you realy think, should I sell it?
[Android Q&A, Help & Troubleshooting] physwizz:
The A146p TWRP works successfully so the decision is yours.
[Android Q&A, Help & Troubleshooting] moresat:
well, no sooner said than done. I did it. For my part this A136B twrp discussion can be closed here. Changing phone was not a problem: the A13 and A14 differ from each other almost only in the camera quality and 2/3 mm in size. Even the CPU is the same if I'm not mistaken. I would like to thank you anyway, before leaving this discussion, and if you allow me I would like to offer you at least a beer. I also follow you on Telegram and the amount of work you produce is impressive.
[Android Q&A, Help & Troubleshooting] physwizz:
Thanks.

It's a bit early for a beer.

I'll have it tonight
[General Questions and Answers] tmanner:
anyone here that is very familiar with the advanced config tool v3.3 that can guide me to the best set up for performance? many thanks in advance.
[General Questions and Answers] Imyman:
Well...best performance really depends on what you'd like to do with your phone. If by best performance you mean things like faster loading/bootup etc you can do that using the 'splash screen' option under advanced config. Check out the 'performance' key as well. Spend some time playing with the application.....it's pretty easy to understand and operate...giving you great control over what you'd like to accomplish using your device. If you have some specific requests...let me know.
[General Questions and Answers] nir36:
honestly, i'd just try everything that seems to be performence related until i found out what's best for me.

it's highly individual.
[General Questions and Answers] tmanner:
one issue I would like to see resolved through advanced config is this......if i have a program running like google maps or any other internet intense program and my phone rings it takes FOREVER for it to acknowledge when i push the answer button. any idea why this is or how to fix it?
[General Questions and Answers] Imyman:
Hmm....I guess that's like default phone functionality. What device are you using? For better performace all around....you might wanna consider flashing a cooked rom onto your device. Pick one that's relatively clean...and with some luck....your phone will probably run faster that way.
[Samsung Galaxy S22 Ultra] tiarlitos:
I watched a video on YouTube and I saw a service inside the Game Optimizing Service, the name Game Intent Service, I saw too that disabling this service should help improve battery life and more some stuff, the GOS has 7 services and the game intent service is one of them, in the video, Lycan was running but on oneui5.1 we can't install Lycan anymore, so does anyone know how can I disable this? I searched about this but I never found anything about it.
[Samsung Galaxy S22 Ultra] raul6:
It doesn't help, just leave it be
[Fire TV Q&A, Help & Troubleshooting] harryzee:
I have an Insignia 50 inch Fire TV that is approx. two years old. For the last year plus, I have been using the single USB port via an ethernet to USB adaptor to access my ethernet signal with no issues. Just had to turn off WiFi and the ethernet signal came through the USB port and showed as such. No problems! Sometime during the last three weeks (July 1- July 20 2023) after an Amazon update I was no longer able to access the ethernet signal via the USB port. I have eliminated the ethernet cable itself since it continues to work using the ethernet port, the USB port appears to be fully functional using a flash drive to test, the ethernet to USB adaptor works ( swapped out with its twin unit that I use with a new TLC Q7 55) with both adaptors working with the TLC, no issues with Spectrum router. It just stopped working! The only culprit I have left is the last or next to last Amazon update to the TV. However, what possible reason would Amazon have for deciding to eliminate the ability to access an ethernet signal through the USB port? Rebooting and unplugging TV power to reset has not helped. Totally perplexed!!!
[Fire TV Q&A, Help & Troubleshooting] Finnzz:
I don't either know why Amazon would intentionally disable Ethernet over USB. Amazon sells their own USB Ethernet adapters which are included with the 1st and 2nd gen Cubes

https://www.amazon.com/Amazon-Ethernet-Adapter-Fire-Devices/dp/B074TC662N

If Ethernet over USB was disabled it might have been unintentional. Maybe they updated some driver and now there is a compatibility issue with the particular model you are using?
[Fire TV Q&A, Help & Troubleshooting] harryzee:
Thanks. I got the "Cable Matters" version which has a 3.0+ USB connector rather than the Amazon version with the 2.0 USB. Worked flawlessly on the Fire TV until recently and continues to work flawlessly on the TCL Q7. When I finally checked out the USB port on the Fire TV with a flash drive and saw it was still functional, that was the last piece in the hardware issue puzzle. It has to be a change in the software.
[Fire TV Q&A, Help & Troubleshooting] harryzee:
Has anyone else with a Fire TV (NOT "Stick"!) generation 2 or later (Insignia/Amazon) run into this issue or am I truly an isolated situation? Repeat: I have effectively eliminated any/all hardware issues that could be the cause of this loss of capability. Cannot remotely grasp that Amazon would have eliminated this ability with their most recent firmware upgrades. Worked fine through the end of June! I know I could get a 4K Firestick or Cube to see if they do or do not allow this connection but am very resistant to doing that. Any realistic help would be greatly appreciated. Yes, everything is working fine with the ethernet port connection using the original cable so I am far from being out of luck in terms of functional usage.
[Fire TV Q&A, Help & Troubleshooting] harryzee:
Follow-up: Amazon told me to contact Insignia which I did. Insignia confirmed that no updates had been issued by them and that all of my hardware tests and checks were correct and I had eliminated any issue with the USB port, the cables, and the adaptor. Went back to Amazon about that and the rep now states that the forum is not the place to address the issue! This is after I had politely and repeatedly corrected their comments, especially as to the Ethernet port being the only place to make that connection! For reasons I will never understand, the last Fire TV update from Amazon in late June/early July has to be the remaining culprit. Cannot remotely imagine why they would have deliberately blocked Ethernet access via the USB port!
[Android Software/Hacking General [Developers Only]] janith4:
SWAP File mod​

Magisk module to enable or increases the SWAP memory by an additional 4GB or 8GB for Lineage OS 14 or above. It should also work with AOSP and other ROMs, but it has only been tested on Lineage OS 20.

Tested on Lineage OS 20. Magisk 26.

Requirements​

Android 7.0 or above

Requires Magisk v24 +

6Gb or more of free space in /data if you select 4GB

10GB or more of free space in /data if you select 8GB

Installation Steps​

Download the ZIP file for this module (lin_os_swap_mod.zip)

Flash the ZIP file in Magisk v24 or above

During the installation, it will ask you to press the volume key for an interactive install

As soon as it prompts you to press the volume key, do so

- If the volume key is detected, you can choose between a 4GB or 8GB SWAP size​

- If the volume key is not detected, the module will use a 4GB SWAP size by default​

Wait for the creation to complete, it may take more than a minute

Reboot

To verify if the SWAP is enabled, follow these steps:​

1. Download a terminal app

2. Switch to SU (Super User) mode

3. Type "htop" in the terminal app

4. If you see a value above 4GB, then the SWAP is successfully enabled

---OR---

Use one of the apps available in the play store

Does Not touch ZRAM config​

This module unlike others does not touch the device's ZRAM config but rather runs alongside.

if you run `cat /proc/swaps`, you will see 2.

Impact​

For optimal results, open a few apps and keep them running for a few hours. The performance improvement is highly conditional. The biggest difference i noticed in my case was battery life and less lag.

This module has been tested on Lineage 20 with a device having 4GB RAM. With an additional 8GB SWAP, the device was capable of running more apps and it felt like having more than 4GB RAM. Additionally, improved battery performance was observed. The average memory usage dropped from 89% to 65% with over 30 apps in the recent apps list and using a bulky Gapps package with all the future flags set to true.

Issue​

This module is only about 24 hours old as of the time I'm making this post, so you might encounter some bugs, or may not work.

This module is hardly capable of bricking in case it doesn't work.

Uninstallation​

To uninstall the module, simply deactivate the module in Magisk and then reboot your device.

Support​

If you find this module useful, please consider starring the repository on GitHub: lin_os_swap_mod

I am the author of this module @janithcooray.

This is my first time creating a post on XDA let alone creating a Magisk module, so go easy.

Download Latest - Swapfile Mod​

Upcoming​

[ETA 2024-02-07] Adding an app to manage Configuration

[TBD] Updating to make it TWRP flashable
[Android Software/Hacking General [Developers Only]] janith4:
2024-02-7 [ETA]

Version 2.0 - Adding an app to manage Configuration

2023-10-15

Version 1.3 - Increased Swappiness to fix usage issues

2023-07-25

Version 1.2 - Added Option to choose RAM Priority over ZRAM

2023-07-22

Version 1.1 - Updated SWAP Priority to auto and less then ZRAM
[Android Software/Hacking General [Developers Only]] BABYFACE10:
Nice work, going to try this now on s21 FE on custom rom,
[Android Software/Hacking General [Developers Only]] r80x:
Hi!

The link doesn't work. I see that you released 1.3 on github, but the downloaded zip doesn't work for me there. Will this thread be updated or have you stopped working on it?

Thank you!
[Android Software/Hacking General [Developers Only]] Samuel Holland:
Very nice, thanks for sharing. 👍👍
[Android Software/Hacking General [Developers Only]] janith4:
Sorry my bad, ive forgotten to add the correct file name on the release artifacts. already fixed.

"have you stopped working on it?" - I initially thought that this was going to be some lame module with about 10 users max, but there have been a lot of downloads and positive feedback on this. I have already decided and started to make a configuration application. Let me know your thoughts on it Expect it to be out somewhere around 1st week of February
[Android Software/Hacking General [Developers Only]] billy996:
Bro, I want to completely close the Swap partition. Will this Module provide such an option?
[Android Software/Hacking General [Developers Only]] janith4:
Sorry, this one doesn't remove existing swaps
[Android Software/Hacking General [Developers Only]] shadowofdeth:
Any reason this wouldn't do anything on oxygen os 13?
[Android Software/Hacking General [Developers Only]] Jimmy Glex:
hey you still working in version 2.0 ?
[Android Software/Hacking General [Developers Only]] Candiety:
Got a problem here. So I initially used this version, 1.3.1-2

GitHub - janithcooray/lin_os_swap_mod at v1.3.1-2

increases the SWAP memory by an additional 4GB or 8GB for Android 7.0 or above - GitHub - janithcooray/lin_os_swap_mod at v1.3.1-2

github.com

It set to 4GB and was working fine. I uninstalled it, then installed from the "download latest - swap file" link to the mod in this thread, thinking it was version 2.0 (I now see it's the exact same file I originally used, from the latest file on github.

It worked absolutely fine originally. Then, the second time, I set it to 8GB, and when it asked if I wanted to prioritise the swap over zram, I said no. It took quite a while to flash in Magisk, about 5-10 minutes this time. After it was done I instantly checked in a dev info tool, and saw that the 8GB swap had been applied, and I had 2GB original ram + 8GB new swap ram = 10GB.

Then it crashed. Now when I boot my phone, the phone is fine for about 30 seconds, then it restarts. I can't open magisk to uninstall it because it instantly crashes. I'm currently in fastboot and about to try and uninstall it.

Any ideas why it might be crashing after 30 seconds or so? Any tips for resolution?

E/OS 2.1 android 13, Moto G7 River. Any help much appreciated.