yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy A51 Guides, News, & Discussion] YOisuPU:
there are many such programs. It is rather for collectors than for a service or store. she has an annual subscription. works.

general site.

https://easy-firmware.com/

specifically this dongle with video.

https://easy-firmware.com/index.php?a=downloads&b=folder&id=34581

look in the search for an alternative, you will find a comparison with other similar ones programs. in many forums.

By the way, a subscription costs US $ 30 per year - just like the guy above offered us all here for one device.

For those who need a root exactly on the drain - a suitable program and its analogues. you can find trial versions on the network :) I personally do not need a stock from the Samsung - I think it’s very dirty firmware - the root will not help.

your method is well tolerated. thank. I got a clean AOSP.
[Samsung Galaxy A51 Guides, News, & Discussion] Huops73:
Thanks a lot!
[Samsung Galaxy A51 Guides, News, & Discussion] map220v:
I Think i found way to sign recovery.img using avbtool.py

You need stock recovery.img and recovery img patched by magisk

also use stock vbmeta (not from patched AP)

1. use this command to get Image size of stock recovery.img (avbtool.py info_image --image .\recovery.img) i got 71106560 bytes

2. use this command to sign magisk recovery.img (avbtool.py add_hash_footer --image magisk_recovery.img --partition_name recovery --partition_size 71106560)

3. now you can flash signed recovery.img using odin

recovery.img sign not working on windows use it on linux or WSL

---------- Post added at 09:58 AM ---------- Previous post was at 09:57 AM ----------

I Just tested TWRP it can't mount system vendor and product. I guess we need to wait for TWRP update.

---------- Post added at 10:21 AM ---------- Previous post was at 09:58 AM ----------

Now i tested Magisk and it can't boot (Magisk Daemon causes kernel panic on post-fs-data) EDIT: it's issue with Magisk or new Kernel Security
[Samsung Galaxy A51 Guides, News, & Discussion] rootadvisor:
Hello and great work ,

I got the ASOP image running in my deviced (follow gabrielfrias instructions )

and thanks to who posted the AOSP10-A515FXXU2ATB1.tar and boot file it saved me a lot of time.

Then i notice this problem.

the root does not let me write on system ... i can write once and if i try to do it again i got I/O error , (the same happens if i do mount instructions)

and then after reboot there is nothing in the /system or etc were i writhed before the reboot

even with in the state permissive.
[Samsung Galaxy A51 Guides, News, & Discussion] map220v:
You disabled verity using (adb disable-verity)?
[Samsung Galaxy A51 Guides, News, & Discussion] rootadvisor:
Nop where i find that can you help ?
[Samsung Galaxy A51 Guides, News, & Discussion] map220v:
You need to connect phone to PC and use (adb disable-verity) command
[Samsung Galaxy A51 Guides, News, & Discussion] kkosnuss:
Does anyone know how to deal with this particular issue ?
[Samsung Galaxy A51 Guides, News, & Discussion] BlastedRemnants:
I haven't made any progress myself yet, but I did try a bit of experimenting and after reverting to stock I noticed that only the stock Samsung camera app can take 48 MP pictures, best I can get with any other camera app is 32 but I have no idea why.
[Samsung Galaxy A51 Guides, News, & Discussion] gabrielfrias:
thanks for explanation. I've done a research and I found out it's the only stock fimware root method available until now, did not find any similar, not even a trial version. as I could notice, root is done by patching boot.img. [MENTION=7618808]map220v[/MENTION], do you think if you get such easy-firmware patched boot.img you could figure out how to patch it correctly? or maybe a dumped boot file from an already rooted device...
[Samsung Galaxy A51 Guides, News, & Discussion] rodrigofd:
[MENTION=4661848]gabrielfrias[/MENTION] when running simg2img.exe, I'm getting the following output, after it generates the unsparsed img (the file does seem to be generated):

> packed img filename: superLZ4.img

> output img filename: superSIMG.img

> Error calling ftruncate() to set the image size

Any ideas? Did you run into this issue?

---

Also, on this command:

./lpmake --metadata-size 65536 --super-name super --metadata-slots 2 --device super:4294967296 --group main:4293513600 --partition system:readonly:1577095168:main --image system=./system.img --partition vendor:readonly:342155264:main --image vendor=./vendor.img --partition odm:readonly:643456:main --image odm=./odm.img --sparse --output ./super.img

What should we put for the size of "super"?

--device super:4294967296

Is that the original byte size of the original, untouched, unsparsed super.img? Or the sparsed one? Or which one?
[Samsung Galaxy A51 Guides, News, & Discussion] gabrielfrias:
i've never experienced such error with simg2img.exe. are you sure superLZ4.img was created correctly? maybe creating it again should fix the problem.

the others ./lpmake arguments (super for example) must be left unalterated. you should modify just what it's in the tutorial, ok?
[Samsung Galaxy A51 Guides, News, & Discussion] map220v:
Magisk already can correctly patch boot.img.

But on A51 for some reason Kernel Panics when Magisk Daemon starts. i disabled it Modules not working but root works on stock Firmware

https://drive.google.com/file/d/1AvtwteSobCJrp6bhp2osfTYKIu1vxPDh/view?usp=drivesdk

---------- Post added at 08:35 PM ---------- Previous post was at 08:21 PM ----------

If someone wants to experiment with TWRP, i leave it here https://drive.google.com/file/d/12g9VQ3RelLV61cXB5AMZFoNgLX2pk40l/view?usp=drivesdk

It's can't mount system, vendor or product, but it can Wipe partitions like data and install boot and recovery images.
[Samsung Galaxy A51 Guides, News, & Discussion] YOisuPU:
there is no solution yet. in our phone 2API is not complete, but limited. We can’t put for example a Google camera. Only the Samsung stock works with this misunderstanding :) maybe someone could solve this but I can not unfortunately not my profile at all sry

p.s. if the camera does not suit you in the firmware AOSP and you cannot find a suitable camera for you, free software. You can always install the (proprietary) original Samsung camera https://www.apkmirror.com/apk/samsu...ung-camera/samsung-camera-10-0-05-49-release/ (original camera from A51 update May 2020) you may have to add this line to build.prop - persist.camera.HAL3.enabled = 1 if there are glitches, remove this line from build.prop

also any proprietary software from the original A51 firmware and not only can be found at https://www.apkmirror.com/

I ask you to understand correctly, I do not advertise non-free software and the site distributing it. it’s just possible you can’t live without it, use it at your discretion.

---------- Post added at 11:58 PM ---------- Previous post was at 11:27 PM ----------

leave as is. both the first and second. and possibly the third: an error in GNU "invalid backup file format for header magic"

ignore it.
[Samsung Galaxy A51 Guides, News, & Discussion] gabrielfrias:
Simply AWESOME! You're the man! You made an impressive job, many thanks! I tested the root and it's working fine!

Congratulations!

---------- Post added at 11:59 PM ---------- Previous post was at 11:58 PM ----------

I going to test TWRP later
[Samsung Galaxy A51 Guides, News, & Discussion] xmannv:
You can guide the method above of [MENTION=7618808]map220v[/MENTION]
[Samsung Galaxy A51 Guides, News, & Discussion] gabrielfrias:
After testing, I'll share everything I've experienced, ok? Probably tomorrow morning
[Samsung Galaxy A51 Guides, News, & Discussion] xmannv:
Waiting for your good news, bro
[Samsung Galaxy A51 Guides, News, & Discussion] rodrigofd:
How did you manage to boot a magisk-patched stock boot img. on this phone?

I've been trying to do so, using latest canary, and also tried with latest stable, but it stays on a bootloop (wiped data)...
[Samsung Galaxy A51 Guides, News, & Discussion] map220v:
On this phone when (magisk post-fs-data) launches phone goes in kernel panic.

I just compiled magisk without (magisk post-fs-data)

EDIT: Also this problem can be fixed by editing init.rc

/proc/sys/kernel/panic_on_oops 1 Change 1 to 0
[Samsung Galaxy A51 Guides, News, & Discussion] rodrigofd:
Can you share it, so I can try it out? Thanks!
[Samsung Galaxy A51 Guides, News, & Discussion] map220v:
https://drive.google.com/file/d/1AvtwteSobCJrp6bhp2osfTYKIu1vxPDh/view?usp=drivesdk
[Samsung Galaxy A51 Guides, News, & Discussion] rodrigofd:
Thanks so much, confirmed working :D

I guess we should restrain from using any magisk module that relies on post fs, right? Until/if there's a fix for it

PS. according to :

> EDIT: Also this problem can be fixed by editing init.rc ->

/proc/sys/kernel/panic_on_oops 1 Change 1 to 0

Should that make all modules work?
[Samsung Galaxy A51 Guides, News, & Discussion] map220v:
After editing init.rc you can use Normal Magisk
[Samsung Galaxy A51 Guides, News, & Discussion] rootadvisor:
So ii just go back to stock (flash all stok) and next the in Odin in AP slap the magisk_patched2,img and we got a rooted stock A51 ?

or i missing something here ?

Thank you
[Samsung Galaxy A51 Guides, News, & Discussion] rodrigofd:
Actually I spoke too soon... flashing the attached patched img., does make it up to the SAMSUNG logo screen, but it stays there, never booting the actual system.

Tried wiping and restarting multiple times, but without success.

How can I edit the init.rc? On TWRP, the data is encrypted, so I can't touch anything there
[Samsung Galaxy A51 Guides, News, & Discussion] map220v:
No. In Magisk Manager click install and select "direct install (recommended)"

---------- Post added at 12:41 PM ---------- Previous post was at 12:36 PM ----------

1. Install magisk that i patched.

2. after boot use root explorer edit init.rc file size should not change. Root Explorer will make init.rc.bak delete it.

3. Reboot.

4.Install normal magisk using direct install.
[Samsung Galaxy A51 Guides, News, & Discussion] rodrigofd:
You provided an .img file... how is that supposed to be installed? I assumed you meant via Odin, renaming it to boot.img, and wrapping it on a .tar, but as stated, that doesn't work (stuck at splash screen)
[Samsung Galaxy A51 Guides, News, & Discussion] map220v:
If you stuck at bootanimation then system partition verity failed. if you can access adb then try (adb disable-verity)
[Samsung Galaxy A51 Guides, News, & Discussion] rootadvisor:
After i Pathed the file and i had to do a factory reset it stays on boot loop.

then boot up to system conect wifi etc...

i eddited the init.rc and restarted ...

i Install magisk manager it recognized the root

its working Thank you for all this work
[Samsung Galaxy A51 Guides, News, & Discussion] gabrielfrias:
tryed this, not working for me, maybe ADB version, will try again.

add it to a .tar file using 7zip and flash using Odin

I'll try this now, but, for me, root works like "on-the-fly". I can modify many things in system, others not and when I reboot, everything is retored.

wait for it to be a full solution, mate
[Samsung Galaxy A51 Guides, News, & Discussion] rodrigofd:
[MENTION=4661848]gabrielfrias[/MENTION] so did flashing this patched img via Odin worked for you, all the way to system? As I mentioned, I'm stuck on the splash screen (as stated, I wiped data/cache, and trying to do adb root & adb disable-verity doesn't work for me (on TWRP), I get "Error getting verity state. Try adb root first?"
[Samsung Galaxy A51 Guides, News, & Discussion] gabrielfrias:
yes, it did. flashed using Odin, it reboots, reboots once again to recovery to do a factory reset and, then, to system. I also tryed to format using provided TWRP, but it does not boot, so I flashed stock firmware I downloaded with Frija and repeated the process. when I try to disable dm-verity, it gives me the error:

verity cannot be disabled/enabled - USER build
[Samsung Galaxy A51 Guides, News, & Discussion] rodrigofd:
Any attempt to modify /init.rc as you indicate, setting the value to 0, seems to be applied (while on the same session), but as soon as I restart, it gets reset to 1...

Maybe that line has to be added to some init.rc file within /data/adb ?
[Samsung Galaxy A51 Guides, News, & Discussion] rootadvisor:
i have patched magisk and all correct , but without verity-disable i ca not change /system ...

i have the same "verity cannot be disabled/enabled - USER build"

(not used twrp on this)
[Samsung Galaxy A51 Guides, News, & Discussion] mitomanu:
I think we must wait another way to root this device. Or, if one of you have root, please, share with us with an accurate method, step-by-step. Thank you!
[Samsung Galaxy A51 Guides, News, & Discussion] gabrielfrias:
[MENTION=7618808]map220v[/MENTION] I was thinking about creating a flashble pre-rooted firmware file, like GSI files. Do you think it could mount system RW and keep root modifications after reboot?
[Samsung Galaxy A51 Guides, News, & Discussion] rodrigofd:
[MENTION=7618808]map220v[/MENTION] once on system, with your patched magisk, if I attempt to install regular magisk, it crashes and restarts the system (canary magisk)

Any ideas?
[Samsung Galaxy A51 Guides, News, & Discussion] rootadvisor:
for those who tryed twrp did u try to flash no-verity-opt-encrypt-samsung-1.0 or other verisons ?
[Samsung Galaxy A51 Guides, News, & Discussion] rodrigofd:
No, I tried via adb.

Can you share that zip?
[Samsung Galaxy A51 Guides, News, & Discussion] HEROMEROHD:
https://androidfilehost.com/?fid=962187416754474353

https://build.nethunter.com/android-tools/no-verity-opt-encrypt/

VBMeta blocked normal boot after flashing one of those zips in my case.
[Samsung Galaxy A51 Guides, News, & Discussion] rodrigofd:
How did you flash them? By using the TWRP attached on this thread?
[Samsung Galaxy A51 Guides, News, & Discussion] HEROMEROHD:
Yeah, through the twrp map220v ported.
[Samsung Galaxy A51 Guides, News, & Discussion] YOisuPU:
if you use AOSP try - menu - Phh Treble Settings - Misc features - Force Enable Camera2API HAL3. I unfortunately can not say if this works. and I can’t check - I deleted the camera altogether.

here they say there is a working camera. https://xdaforums.com/showpost.php?p=82351363&postcount=5 or try alternative open camera options and others may make sense.
[Samsung Galaxy A51 Guides, News, & Discussion] rodrigofd:
I'm still unable to install regular Magisk (with post fs data enabled)

No way to disable the panics (via init.rc edit). Changes to that file don't stick after reboot.

What if you edit that init.rc inside the ramdisk of the boot img?

Can you help me [MENTION=7618808]map220v[/MENTION] ?
[Samsung Galaxy A51 Guides, News, & Discussion] map220v:
Phones starting from Android 10 (SAR) don't have init.rc in ramdisk.

And I think init file won't load it.
[Samsung Galaxy A51 Guides, News, & Discussion] rodrigofd:
So how did you do It, then? How did you manage to update to regular magisk?
[Samsung Galaxy A51 Guides, News, & Discussion] map220v:
idk when i used magisk on stock samsung i could edit init.rc in /
[Samsung Galaxy A51 Guides, News, & Discussion] bagbyte:
I've tried to follow the steps to unpack and repack super.img, in order to change the build.prop inside the system.img, since in my stock super.img is much bigger than the one in your example (around 6GB total), and the system.img itself it's above 4Gb, how can I calculate the value to use for the device option?

Is there a way to check those values before unpacking so that I can have a reference (especially for the device)?
[Samsung Galaxy A51 Guides, News, & Discussion] rodrigofd:
I had a similar issue while attempting to edit 'init.rc' on system.img, when trying to repack super.img.

What you need to do, is to increase the value for the --device super:nnn argument, in blocks of 512, until you succeed.

I managed to create a modified super.img, flashed it, and booted correctly ??

---------- Post added at 02:46 PM ---------- Previous post was at 02:42 PM ----------

So, [MENTION=7618808]map220v[/MENTION], update, I managed to alter that kernel setting, by unpacking super.img, editing init.rc, repacking and flashing (confirmed and it sticked).

After that, I could direct-install the latest canary Magisk successfully, and boot, but although I keep root, there's no way to make any module work.

Actually, after I attempt to install them via the Manager app, they don't appear on the installed module list... and the logs don't show any useful info. :(:confused:
[Samsung Galaxy A51 Guides, News, & Discussion] bagbyte:
I'm trying to flash only AP, but every time, after he finish sending super.img, it stacks at userdata.img and red message appear on the screen saying "Only official released binaries are allowed to be flashed(SUPER)", any idea how to avoid this issue? Now I need to restart and I get the blue screen saying to use Smart Switch PC to restore, but actually it's enough if I flash the BT.

I'm stacked!

PS: my phone is not rooted
[Samsung Galaxy A51 Guides, News, & Discussion] HEROMEROHD:
Flash stock, connect to the internet and try to update the firmware through the settings. You should be able to flash unofficial binarys after you did this.Your KG State was probably prenormal blocking every attempt to flash something besides official firmware. It should be checking after you did all of this, or you just forgot to unlock the bootloader, then look it up in this thread.
[Samsung Galaxy A51 Guides, News, & Discussion] bagbyte:
Finally, I've made it, my system.img now contains 2 properties in /system/build.prop that suppose to unlock multiple users accounts feature, but sadly, when I check getprop, those 2 variables are not set....am I missing something? At least my POC worked, I can change the file without root and without tripping Knox
[Samsung Galaxy A51 Guides, News, & Discussion] arfemre:
if you dont want magisk and only root, i help you rooting a51 with eft pro
[Samsung Galaxy A51 Guides, News, & Discussion] bagbyte:
I don't want to trip Knox, does eft pro trip it?
[Samsung Galaxy A51 Guides, News, & Discussion] arfemre:
i have a dream i want root and knox 0 its funny
[Samsung Galaxy A51 Guides, News, & Discussion] bagbyte:
I don't want to root, maybe you missed that part, but actually I just want to change system.img in order to modify some system property without tripping Knox (which I already succeeded) to enable multiple users account, but even tho those property are set in the /system/build.prop it seems when the phone boot, those properties are not set
[Samsung Galaxy A51 Guides, News, & Discussion] arfemre:
oh i see bro sorry
[Samsung Galaxy A51 Guides, News, & Discussion] King_lilrowrow:
You got the source for this? Drop us a link and I'll either push the required patches if it's your repo or fork it and build it over the next few days, seems a simple few patches (if the TWRP Device tree is somewhat built)
[Samsung Galaxy A51 Guides, News, & Discussion] truhlik:
Hi,

would it be possible using your method to edit CSC files without tripping knox? I also don't need root, but just edit some features in CSC (carrier's device limitation).

Thanks
[Samsung Galaxy A51 Guides, News, & Discussion] map220v:
I Used TWRP-9.0 it's don't have super.img (Dynamic Partition) Support.

TWRP-10.0 still WIP and i can't build it (I Getting recovery.img without TWRP).

EDIT: I fixed TWRP-10.0 compilation. Now im going to try mounting system logical partition.
[Samsung Galaxy A51 Guides, News, & Discussion] rodrigofd:
[MENTION=7618808]map220v[/MENTION] did you manage to have Magisk working with modules? I've tried million things nad versions, but while root works, no luck with modules
[Samsung Galaxy A51 Guides, News, & Discussion] map220v:
I Don't know why Magisk causing kernel panic only on this phone.

Setting panic_on_oops to 0 only disables reboot when magisk daemon causes it. But it's not fixes problem.
[Samsung Galaxy A51 Guides, News, & Discussion] map220v:
TWRP Update

https://drive.google.com/file/d/1W1wPUEGjoYW5vuJlxkRKdiE7IECBaqk_/view?usp=sharing

I Fixed Brightness and Updated TWRP from Android 9 branch to Android 10 branch

System , Vendor , Product Mount still not working.

Also this TWRP uses A51 Device Tree instead of A50 Device Tree

Device Tree Link: https://github.com/map220v/android_device_samsung_a51nsxx
[Samsung Galaxy A51 Guides, News, & Discussion] King_lilrowrow:
I've took a brief look over your recovery tree so far, submitted a few patches: https://github.com/map220v/android_device_samsung_a51nsxx/pull/1
[Samsung Galaxy A51 Guides, News, & Discussion] TheEmpathicEar:
Has anyone posted a comprehensive tutorial on how to get to the point where you are now?
[Samsung Galaxy A51 Guides, News, & Discussion] bagbyte:
How can we use this? And how to install TWRP on the A51?
[Samsung Galaxy A51 Guides, News, & Discussion] King_lilrowrow:
You can't yet, patches where ineffective.

There's a test build above but without being able to mount certain partitions it's not useful to the average user currently but works ongoing.
[Samsung Galaxy A51 Guides, News, & Discussion] bagbyte:
If I root with Magisk now, I read I will not be able to install original firmware anymore without patching them first, will I be able to install non-root/non-patched firmware later? maybe when TWRP will be available? Or I will never ever be able to install Samsung firmware without Magisk/patch?
[Samsung Galaxy A51 Guides, News, & Discussion] bagbyte:
rooted

I've been able to root thanks to: https://github.com/topjohnwu/Magisk/issues/2762#issuecomment-624229430
[Xiaomi Redmi 5 ROMs, Kernels, Recoveries, & Other ] scrppycoco66:
No Mac Randomization

Thanks! The Rom is really great, butter smooth and with all the customization, only thing its missing is full disk encryption, as when i tried, it just reboots.

I also noticed that Mac Randomization is missing as well under wifi settings, its a security feature introduced with Android 10, if you can enable that would be great. Thanks again!!
[Xiaomi Redmi 5 ROMs, Kernels, Recoveries, & Other ] LinuxPanda:
FAQ

1)

Will there be regular updates?

Atleast once/month, usually after aosp security patch is merged.

Apart from that, Ill release a new build in case of major bugs that breaks the ROM to be used as daily driver.

2)

Reporting bugs

DO NOT Report bugs if

• if you didn't perform a clean install.

• if you're running a custom kernel.

• if you've installed Xposed.

• if you're using battery/thermal mods.

3)

How to report bugs?

• Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.

• Mention what custom stuffs you've installed in the rom, like Magisk modules, etc.

• If the problem disappears after disabling selinux, disable SELinux and grab logs using SysLog app.

• If its a random reboot, grab dmesg. [Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless.]

4)

Disabling SELinux

Needs root. You can disable SELinux via the following options.

• SELinux Mode Inverter Magisk module

• SELinuxModeChanger App

• Terminal Emulator App

To disable SELinux using a terminal emulator, run the following commands

> su
> setenforce 0

5)

Taking Logs

Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.

• Using adb

• Using MatLog app

• Using SysLog app for audit logs

[IMG="Logcat Or GTFO"]http://i.qkme.me/3645qt.jpg[/IMG]
[Xiaomi Redmi 5 ROMs, Kernels, Recoveries, & Other ] LinuxPanda:
More Screenshots: https://imgur.com/a/tU1JT0r
[Xiaomi Redmi 5 ROMs, Kernels, Recoveries, & Other ] vu3v:
Thanks for new rom. Does egde gesture support?
[Xiaomi Redmi 5 ROMs, Kernels, Recoveries, & Other ] anooooop:
Nice.

Extended Display missing
[Xiaomi Redmi 5 ROMs, Kernels, Recoveries, & Other ] LinuxPanda:
Please check gesture settings.

That feature will be added soon. Its up to the ROM devs.