Galaxy A13 (SM-A135F and SM-A137F) Custom Kernel

edward0181 said:

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.

He claimed he made it with a friend
Hmmm

physwizz said:

Exynos 850 Resources

Here

Exynos 850 Resources

Exynos 850 Devices 1. A12s A127f & A127m 2. M12 M127f & M127g 3. A21s A217f & A217m 4. F12s F127g 5. A13 A135f & A135m 6. M13 M135f & M135m 7. F13 E135f 8. A04s A047f 9. XCover5 G525f

forum.xda-developers.com

@physwizz

Click to expand...

this ones mtk tho
exynos 850 is the other 13 model im pretty sure

physwizz said:

He claimed he made it with a friend
Hmmm

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!

RDS5 said:

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!

Click to expand...

So you forked the dt from Edward?
He said he created it with his friend and I wrongly assumed he built it from scratch

physwizz said:

So you forked the dt from Edward?
He said he created it with his friend and I wrongly assumed he built it from scratch

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

RDS5 said:

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 wTrk of others!

T

Click to expand...

edward0181 said:

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.

i know, we didnt want to steal the work, we just wanted to make it work. (dm-40 wasnt a directory/symlink for us)

edward0181 said:

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.

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

edward0181 said:

Only way is formatting data and prevent it from ever being encrypted again, which is pretty much against all Android safety advice.

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..

RDS5 said:

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..

Look at the screenshot.
If you remove the name of the original author then that's stealing!

physwizz said:

Look at the screenshot.
If you remove the name of the original author then that's stealing!

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..

RDS5 said:

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..

Keep the original author's name or give credit

physwizz said:

Keep the original author's name or give credit

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.