yashsingh1/xdaforums huggingface dataset:
[General Topics] physwizz:
To Unlock Bootloader

1. On phone developer options in settings allow OEM unlocking and enable usb debugging by moving both

sliders RIGHT

If you don't see the OEM unlock

-Disable Auto System Update

-Then disable Automatic date and time (Found in General Management) > then set the time back 14 days

- Connect to the internet

-Go to software update then check for update and wait a long time till it registers the device on server

-Once it's registered the OEM Unlock should be visible in the Developer Options

then connect phone to PC

2. Reboot into download mode by holding down both Vol up and Vol down

(You might need to long press vol up to unlock bootloader)

then press vol up to continue
[General Topics] LonelyCracker:
physwizz, I don't think I've the option to long press volume up to unlock bootloader.

The moment I press the volume up it just Continue.

Here are the only available option more me.

Vol + (Continue), Vol - (Restart), Side Key (Show Bar Code).

It is super weird...

Also this is a XME version and I'm still in contract...

But looks like the lock is unlockable after the contract end, which it just started three months ago.
[General Topics] nazagan:
I tried both, neither worked, bootloop. Do you have any other file ?
[General Topics] physwizz:
Installing Custom Recoveries

A. Preparation.

1. Download firmware for your device

2. Extract ap file using Zarchiver

3. Patch the ap file with a magisk which will patch both boot.img and vbmeta.img

For Exynos 850 android 11 use a21s patched magisk.

For Exynos 850 android 12 and most other devices use delta magisk

4. Unlock OEM in developer options

5. Attach phone to pc and reboot to download mode

6. flash patched ap file.

7. Download recovery.img or download twrp.tar and extract recovery.img using Zarchiver.

B.Installation

Method 1.

1. Connect to pc and boot into stock recovery

2. Factory reset

3. Reboot into download mode.

4. flash twrp.tar into the ap slot

5. reboot to recovery.

6. Advanced, terminal.

7. Type multidisabler (twice).

Or flash samsung multidisabler zip

Or, for older phones flash dmverity zip

8. Reboot to recovery

Backup boot, data, super and dtbo

9. Reboot to system

Method 2.

If you have already installed recovery and decrypted.

1. Boot to recovery.

2. Install recovery.img

3. Choose recovery partition

4. Reboot to recovery

Backup boot, data, super and dtbo

(For Pitch-black just install the zip)

Method 3.

1. Install TWRP app

2. Install TWRP

3. Choose file to flash.(don't select device)

4. Select recovery.img.

5. Reboot to recovery.

6. (You may need to change data partition to ext4 first if format ruins your system)

7. Reboot to recovery.

8. Wipe, format data, type YES.

9. Advanced, terminal.

10.Type multidisabler (twice).

Or flash samsung multidisabler zip

Or, for older phones flash dmverity zip

11.Reboot to recovery

12. Flash Magisk for root(only for method 3)

13. Backup boot, data, super and dtbo

C. Recovery Problems

Most recovery issues can be solved by attending to the following issues.

1. Did you root using the full ap file patched Magisk .

(This contains the patched boot.img and vbmeta.img)

Exynos 850 users must use the special a217 magisk?

2. Did you then go all the way through the setup process?

3. Did you download the recovery to match your baseband?

See https://t.me/a127f_res/54 for Exynos 850 recoveries

4. Did you hold down power and volume up after Odin says pass?

5. Did you format data, not just wipe?

6. Did you type multidisabler twice?

7. Did you reboot to recovery by choosing reboot from the menu and then choosing recovery?

8. To avoid touch issues go to settings and untick "allow time out"

D.To restore Stock Recovery

1. Attach phone to pc and reboot to download mode

2. flash patched ap file.

3. reboot

@physwizz
[General Topics] SlendowManX:
Can you please build custom kernel for Samsung Galaxy A035f-A035XXU1AVD3?

The previous kernel you uploaded for a035f resulted in stuck logo
[General Topics] physwizz:
This is for a135f
[General Topics] SlendowManX:
This kernel, you previously uploaded
[General Topics] umdragaogamer:
can i use this kernel in gsi
[General Topics] mazlumelarslan:
Has anyone successfully installed twrp on a137f?
[General Topics] mazlumelarslan:
I can't use it because my computer is broken, I found twrp file for a137f.

Download the twrp file and; Can you tell if it's working or not?

I am attaching the file.
[General Topics] physwizz:
No I can't check it.

Use method 3

Method 3.

1. Install TWRP app

2. Install TWRP

3. Choose file to flash.(don't select device)

4. Select recovery.img.

5. Reboot to recovery.

6. (You may need to change data partition to ext4 first if format ruins your system)

7. Reboot to recovery.

8. Wipe, format data, type YES.

9. Advanced, terminal.

10.Type multidisabler (twice).

Or flash samsung multidisabler zip

Or, for older phones flash dmverity zip

11.Reboot to recovery

12. Flash Magisk for root(only for method 3)

13. Backup boot, data, super and dtbo
[General Topics] nazagan:
It's not working either, I managed to root by flashing ap patched files with magisk delta and ODIN but TWRP is not working with any of the method you indicate. It simply bootloop, can't flash it with twrp app, it does not accept the files.

It is possible to install GSI by following this guide : https://xdaforums.com/t/installing-gsi-by-repacking-super-img-on-sm-127f-and-sm-a325f-linux.4365511/

but there is some issues like locking the phone and waking it up again make the screen unresponsive, and the network is locked in 3G max (might need ims.apk tweeking)
[General Topics] umdragaogamer:
Another question, do this kernel breaks de camera, because mine stop working
[General Topics] physwizz:
It shouldn't affect camera
[General Topics] umdragaogamer:
Well maybe my device dont suport, its a EUX device
[General Topics] physwizz:
Baseband?
[General Topics] umdragaogamer:
i dont know if this can help but thats the link from sammobile: https://www.sammobile.com/samsung/galaxy-a13/firmware/SM-A135F/EUX/download/A135FXXU2AVJ3/1685792/
[General Topics] physwizz:
u2 binary is the same as the new kernel in post #1
[General Topics] WerBn:
Hello

I want to install a custom ROM without samsung bloatware in this phone.

I have some noob questions, wondering if anyone can help me:

1. What's the advantage of installing this kernel?

2. In the post, you say "For OneUI 4( also works for GSIs)". What does this mean?
[General Topics] physwizz:
OneUI is the os supplied with the phone.

GSI is generic system image.

The kernel makes your phone run better
[General Topics] WerBn:
Can I use a GSI image and get a good performance without the bloatware?
[General Topics] physwizz:
Just use my wizzROM

Instructions next post
[General Topics] physwizz:
wizzROM Creator magisk module v4 Thermal

DO NOT INSTALL FROM TWRP

for all Samsung phones

OneUI 2.0 will become QwizzROM

OneUI 3.1 will become RwizzROM

OneUI 4.0 will become SwizzROM

Debloated ROM with Extras

Fixed apps in system/product

Extras:

Battery charge limit

Clean Master

ES file explorer

HKtweaks

SimpleReboot

Root Explorer

Zarchiver

physwizz-2

Thermal throttling removed

Make sure your OneUI ROM iis running befote you start

Installation

1 Backup system from recovery

2 Install the creator from Magisk

Physwizz Collection

t.me

3 Reboot

4 Enjoy

NOTE: you may still need to delete some apps from the app drawer.

Name your wizzROM (optional)

1. Use a root explorer to navigate to system/build.prop

2. Tap to Edit build.prop like this

ro.build.display.id=<your-name>

3. Tap disk icon to Save & Reboot

Xda post

https://xdaforums.com/t/wizzrom-creator.4300953/

@physwizz
[General Topics] WerBn:
Hello

Even after installing your wizzRom(I did not install your kernel), I'm having some problems:

1. Root explorer says it does not have root permissions, but I've checked and it is allowed by Magisk already.

2. Why can't I uninstall other bloatware? Like "Galaxy Sore", "Samsung Cloud", "Google Duo"? When I try to uninstal with adb "su" commands, I get "DELETE_FAILED_INTERNAL_ERROR" and with an app, for example "System app remover" it just says "not uninstalled". What am I doing wrong?
[General Topics] physwizz:
1. Reinstall root explorer apk

2. Delete others from twrp
[General Topics] WerBn:
I cannot uninstall root explorer. Only disable. Even with root.

Is there twrp for this phone?

Can you provide it?
[General Topics] physwizz:
Because I made it a system app
[General Topics] wojtekojtek:
ohh

I bought a137f

and is there ANY custom recovery for this phone?

like TWRP, orangefox, CWM etc

please create it/give me liks to them :<
[General Topics] physwizz:
Yes

A135f

Twrp
[General Topics] wojtekojtek:
a135f

but I need for a137f

these phones have a different processor
[General Topics] physwizz:
Yep

I haven't seen one
[General Topics] wojtekojtek:
nevermind
[General Topics] physwizz:
If you send me your recovery.img.lz4 and boot.img.lz4 I'll see what I can do
[General Topics] wojtekojtek:
I compiled a WORKING recovery with my friend for samsung a137f ! and its working. I have proof

this recovery was found at https://github.com/edward0181/android_device_samsung_a13ve

but I have encrypted Data partition and I want to decrypt it...

I can't format data through TWRP ;-;
[General Topics] physwizz:
Great news.

Use stock recovery to format

Method 1.

1. Connect to pc and boot into stock recovery

2. Factory reset

3. Reboot into download mode.

4. flash twrp.tar into the ap slot

5. reboot to recovery from main menu (not just reboot)

be patient- It may take a while

6. Advanced, terminal. Type multidisabler (twice).

7.

Or flash samsung multidisabler zip

Or, for older phones flash dmverity zip

8. Reboot to recovery from main menu (not just reboot)

Backup boot, data, super and dtbo

9. Reboot to system
[General Topics] wojtekojtek:
method 1)

I typed multidisabler and console says unaccessible or not found

method 2) i found multidisabler here (https://androidfilehost.com/?fid=17248734326145725182) it said that I have android 11 (lol? I have android 13, not 12 or 11)

I can't make backup because I still can't do anything with twrp

please help me
[General Topics] physwizz:
Add multidisabler to the twrp
[General Topics] RDS5:
hes working on fixing that twrp

currently the fstab is incorrect, but thats fixed.

now we're gonna see if we can get it to properly format data and boot into android correctly, then we'll test flashing a little more thoroughly
[General Topics] physwizz:
Great
[General Topics] physwizz:
Exynos 850 Resources

Here

https://xdaforums.com/t/exynos-850-resources.4546963/

@physwizz
[General Topics] edward0181:
Fun to see my work here. Although twrp isn’t functioning as it should just yet
[General Topics] edward0181:
Would have been nice if people just asked if it’s ok.

But anyway, above solution would work. Still building it up with decryption working. Need the correct libs and init files configs.
[General Topics] wojtekojtek:
Hello :D

when will new version release? and can you compile it yourself and add to releases? and.... why you had error in fstab to mount userdata? lol

if you want, I can test it / or help you with sth (I have a137f phone)

edit: I can now wipe data but I can't boot into OS after this, it show an Android Rescue party trigger

reason is fs_mgr_mount_all
[General Topics] edward0181:
Had bigger challenges then that hihi.

My biggest issue is the touchscreen not working on my kernel version. To mount data correctly isn’t an issue. Getting it to decrypt on these stupid mtk devices is….

Will push it once done. It’ll take me some time.

Edward
[General Topics] wojtekojtek:
mouse is working, touch screen also but after 1-2 minutes
[General Topics] edward0181:
Common issue on stock kernel. Need to build kernel with correct drivers. Is on my to do list for tomorrow.

I do have the same device, did the twrp on sm-a125f as well. Just need more then 24 hours in one day
[General Topics] physwizz:
He claimed he made it with a friend

Hmmm
[General Topics] RDS5:
this ones mtk tho

exynos 850 is the other 13 model im pretty sure
[General Topics] RDS5:
he did?

what happened was that me and @wojtekojtek were working with unrelated things on the a13, and i stumbled upon this twrp so we built it and started fixing the fstab to format data and maybe even decrypt it properly

i dont recall claiming i made it, but if i did thats not the case at all

what we did was fork his work and make some patches to fix(ish, WIP) wiping data in the fstab

its open source tho, we all gotta work together lol.

when he said created he meant built, as thats all we did at the time he made that post.. (now we have made patches tho)

we dont mean to take credit away from the work of others, thats immoral and at the end brings us no benefit

open source means to work together with the work of eachother, not to take the work of others!
[General Topics] physwizz:
So you forked the dt from Edward?

He said he created it with his friend and I wrongly assumed he built it from scratch
[General Topics] physwizz:
Decrypt is done from stock recovery
[General Topics] RDS5:
yes, we forked it and tried to fix its data (we fixed formatting but not mounting/decrypting, and formatting doesnt work properly anyways)

its still a WIP basically lol

but yeah we didnt create it, we just made some patches for it and built the code
[General Topics] edward0181:
Then please keep names etc as they where if its not stealing work. Or just merge changes. Changing dm-40 to symlinked bootdevice/userdata isn’t much coding.

Encryption and decryption on mediatek Samsung devices can’t be done in fstab. You’ll need the correct services and init.rc to have it working. And i can tell you. That’s hard as no other mtk device has this working.

Only way is formatting data and prevent it from ever being encrypted again, which is pretty much against all Android safety advice.
[General Topics] RDS5:
i know, we didnt want to steal the work, we just wanted to make it work. (dm-40 wasnt a directory/symlink for us)

oh, ive never done anything with mediatek devices so i honestly dont know

thats why we were modifying fstab in the first place, since wiping data wasnt working correctly (dm-40 is not a directory on his device), so we're trying to make it work for his model..

its honestly better than nothing and its not like we have any adversaries or important data to hide, at least not on a mediatek device..
[General Topics] physwizz:
Look at the screenshot.

If you remove the name of the original author then that's stealing!
[General Topics] RDS5:
we forked the repository and pointed the commands in the readme to our forks..

the intent wasnt to steal, it was to make the commands work and easier to copy for us..
[General Topics] physwizz:
Keep the original author's name or give credit
[General Topics] RDS5:
the screenshot they provided was the readme with the commands, the rom itself says edward0181 in it, so we wont change that since its his work.
[General Topics] physwizz:
Ok

But someone reading the ReadMe will think it's yours.

Perhaps you should leave a credit to Edward in there too.
[General Topics] wojtekojtek:
Done.
[General Topics] physwizz:
Thank you
[General Topics] mazlumelarslan:
hello first of all

Thanks to you developers, I think we will install twrp on our A137F.

Thanks for this.

Here, the language that the software developers understand is spoken.

I couldn't follow much, naturally, what is the latest situation?

Can twrp be installed for A137F?

If not, I'd appreciate it if you let me know here when it's ready.

I have magisk on my phone, I've been waiting for twrp for months, good news.
[General Topics] wojtekojtek:
yes, TWRP can be installed on a137f but its little bugged

remember if you want to (for example) wipe data, then you must reflash stock recovery. Report any bugs to @edward0181 <---
[General Topics] edward0181:
Been doing quite some work on this bloody MTK phones.

Have twrp working, with some downsides.

Encryption / decrypt of /userdata isn't working (WIP).

If you'll format data encryption is gone... once rebooted to Android it'll automatic re-encrypt. If using external SD card, it'll be ok.

Touchscreen is a big woobly, need time to construct correct kernel for touchscreen. There is a timeout setting of 2 mins... Not really an issue for normal work.

Will post asap
[General Topics] edward0181:
Flashable with odin.

As said, it's a work in progress
[General Topics] edward0181:
anyone who would like to assist,

device tree + kernel sources are on github

DT: https://github.com/edward0181/android_device_samsung_a13ve

Kernel: https://github.com/edward0181/android_kernel_samsung_a13ve with big thanks to @

physwizz​
[General Topics] mazlumelarslan:
Well, I would be glad if you know that I am a beginner at the installation stage.

1) Stock recovery Wipe data/wipe cache

2) download mode flash "recovery.tar"

3) Reboot to recovery.

4) Type Advanced, terminal multidisabler (twice).

Is it enough for me to do these?

You said you will update the A137F twrp file soon, it might be better for me to wait until the update comes.

Because

i am a beginner
[General Topics] edward0181:
Multidisabler has been removed from this build. It’s breaking working on android 13

If you just need twrp to flash gsi roms you can just use this one.

Rest will be build this week
[General Topics] wojtekojtek:
can you replace the black bar at the top of the screen?
[General Topics] plarfman:
LineageOS ROM is being worked on, Lineage recovery already booted.
[General Topics] edward0181:
That would be great. I’d like to help. Could you pm me the repo so I can look and assist?
[General Topics] edward0181:
Will fix the notch tomorrow
[General Topics] plarfman:
Sorry, it's private and I already have actual developers I know, you can know the progress on the @a13_mtk telegram group.
[General Topics] os64:
hi does the sm-135f custom kernel work for the sm-135m
[General Topics] physwizz:
I think so
[General Topics] os64:
thank you last question what gsi should i use to make my phone run 64bit apps and how do i install it probably using twrp recovery (sm-a135m) thank you
[General Topics] physwizz:
Installing a GSI

for Exynos 850

Download Android 11 GSI (arm64 ab) with GApps

1. Unzip img file

2.Wipe data from TWRP recovery

3. Install system.img into system partition

4. Install my kernel

5. Reboot

GSI list

Exynos 850 Resources

https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-%28GSI%29-list

t.me

Try this one

physwizz(MCMLIV) in Exynos 850 Testing & Development

t.me

@physwizz
[General Topics] os64:
thank you
[General Topics] os64:
the gsi wont install it keeps showing failed
[General Topics] physwizz:
Perhaps the img file is too large.

Try this one.

physwizz(MCMLIV) in Exynos 850 Testing & Development

t.me
[General Topics] os64:
no it still showing the failed that the file target is to large
[General Topics] physwizz:
Are you installing the system.img file?
[General Topics] os64:
yes but i get stuck in a bootloop and another i cant wipe the system :( this photo isnt mine because i dont know how to make screenshot while twrp is on but its something like this
[General Topics] physwizz:
Press power and volume down to take screenshot
[General Topics] edward0181:
Go to command line in twrp and just enter twrp wipe system or wipe system_root
[General Topics] edward0181:
Go to command line in twrp and just enter
[General Topics] ax0:
Could you attach a prebuilt image file?
[General Topics] physwizz:
A14 is here

Galaxy A14 (SM-A145 and SM-A146) Custom Kernels and TWRPs

Galaxy A14 ========= A145P A145R 4g Mediatek MT6769 (a14m) Kernel: post #1 TWRP: post #143 & post #164 A145f A145m 4g Exynos 850 (a14) Kernel: post #359 TWRP: post #6 A146B A146M 5g Exynos 1330 (a14x) Android 13 Kernel: post #363 Android 14...

xdaforums.com
[General Topics] ax0:
@physwizz could you maybe attach a built version of the a137f twrp tar file cause I can't build it?

@wojtekojtek please man
[General Topics] physwizz:
@edward0181 is building it
[General Topics] ax0:
ok lmk when its done building
[General Topics] wojtekojtek:
theres older version (not mine, but @edward0181 )

it should work
[General Topics] ax0:
ok im gonna sound a little dumb,

but the phone bootloops!

Ive done everything you've set before

What should I do now?
[General Topics] wojtekojtek:
1. Download samsung's stock firmware here

2. Extract zip file

3. Using 7zip unpack the recovery.img.lz4 file

4. Pack it into tar file,

5. Reboot to download mode

6. Flash the recovery tar file

7. Boot your phone

-------------------

To make TWRP working:

8. Install Magisk on phone

9. Copy AP file to phone

10. Patch it using magisk

11. Move it to pc

12. Flash it (you will lose data)

- in AP slot add your patched file

- in BL add BL file

- in CSC add CSC file

- in CP add CP file

13. Boot your phone

14. Flash TWRP

15. Boot your phone again
[General Topics] ax0:
What magisk should I use? When I tried using Magisk, the phone tried to boot up but after the "Powered by Android" screen it rebooted

update: even when I flash stock firmware it still bootloops 😭 (even with factory reset it bootloops, is the bootloader the problem?)

update's update: I bricked the phone? It just bootloops, Re-Partioning doesnt work and it restarts every time, event in recovery, even when "erasing" 😢
[General Topics] wojtekojtek:
Did you flashed all files? (Cp, csc, bl, ap)

If no, then try, maybe it will work...

Edit: also wipe data after flashing stock firmware
[General Topics] ax0:
(crashes = restarts)

When I try to reset, it crashes

When im in recovery, it crashes

When I pass the bootloader unlocked warning, it crashes

BUT it doesnt crash on download mode
[General Topics] oswald_pu:
Thank you very much for your work on 137f.

Will some day a easy-to-handle solution like a lineageOS build result from your valued work?

I recently obtained a 137f, but my S5 is still working, so lazy bone I am I'd rather take an easy path...

Cheers,

Wolf
[General Topics] physwizz:
Thanks.

I don't own this device.

While you're waiting for a rom you could try my wizzROM magisk creator module.

wizzROM Creator magisk module v4 Thermal

DO NOT INSTALL FROM TWRP

for all Samsung phones

Debloated ROM with Extras

Fixed apps in system/product

Extras:

Battery charge limit

Clean Master

ES file explorer

HKtweaks

SimpleReboot

Root Explorer

Zarchiver

physwizz-2

Thermal throttling removed

Make sure your OneUI ROM iis running befote you start

Installation

1 Backup system from recovery

2 Install the creator from Magisk

Physwizz Collection

t.me

3 Reboot

4 Enjoy

NOTE: you may still need to delete some apps from the app drawer.

Name your wizzROM (optional)

1. Use a root explorer to navigate to system/build.prop

2. Tap to Edit build.prop like this

ro.build.display.id=<your-name>

3. Tap disk icon to Save & Reboot

Xda post

https://xdaforums.com/t/wizzrom-creator.4300953/

@physwizz
[General Topics] wojtekojtek:
just use LineageOS TD-based GSI
[General Topics] edward0181:
Hi, I've build Orangefox TWRP variant for A13 SM-A137F (MTK) phone.

Decryption still not working and disabling FBE break Samsung OS... so take it as it is.

If someone wants to help with correct decyption blobs, then please ;-)
[General Topics] physwizz:
Great work
[General Topics] notnoelchannel:
Great work mate!
[General Topics] RDS5:
disabling encryption in vendor breaks oneui?
[General Topics] edward0181:
It does.

Remove fileencryption= strings in fstab and oneui fails to boot. Will boot back to recovery
[General Topics] RDS5:
which fstab? fstab from vendor partition or from system partition (stock rom)?

im not very familiar with gsi devices and their layouts so sorry if this is a noob question
[General Topics] edward0181:
I am not running gsi.

Fstab in vendor partition. System doesnt hold fstabs in normal roms
[General Topics] wojtekojtek:
can you send here vendor.img with modified fstab?