⚠️Galaxy A51 Root || Unlock Bootloader || Flash Official Firmware [Binary 3] May

T

ToddNachste

Member
Apr 15, 2020
8
12
0
Apr 20, 2020 at 7:36 PM
By the way i found another way to get root but it's not tested yet:
0. Download with SamFirm the same firmware you’re running now and extract AP file from firmware archive
1. Extract boot.img.lz4 from AP file
2. Add boot.img.lz4 to .tar archive
3. Put this archive to the phone and patch it with magisk manager
4. Flash magisk_patched.tar with odin in AP
5. Then you should do factory reset and restart the phone
6. Install Magisk Manager and update environment
Of course it needs unlocked bootloader.
Sorry for my bad english, i wrote this without a translator.
 
Last edited:
  • Like
Reactions: ghaniso1 and YOisuPU
O

obodzin

Member
Nov 5, 2012
44
4
0
PL
Apr 20, 2020 at 7:44 PM
Is there any way to debrand A51?
I downloaded the XEO rom (not branded), but after the flashing there are applications, old screen and the operator's logo.
I installed according to the instructions, I also tried with the pit file, but still the same.
Can anyone help? :(
 
X

Xiomax

Member
Jan 5, 2013
17
5
0
Apr 20, 2020 at 7:52 PM
gabrielfrias said:
3) Now you’re going to make a brand new super.img file containing all 4 files of the previous step. This is a critical and tricky step. Run Linux terminal and type:
./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

Note that in this code, the numbers highlighted in bold are the sizes of the 3 .img files you extracted (odm, vendor and product) in step 2 plus system.img you downloaded/renamed, IN BYTES. Update the code with YOUR files's sizes!

system:readonly:1577095168:main (size of unsparsed system.img in bytes)
vendor:readonly:342155264:main (size of vendor.img in bytes)
odm:readonly:643456:main (size of odm.img in bytes)
as @phhusson stated (thanks!), no need sto use product.img, just supress it at all

--group main:4293513600 (main partition size 1577095168+342155264+643456=2776752512)
*The size of main is the sum of the 4 .img files*

You may face two different problems here:
1) Odm.img file requested a not avaliable space. Just sum and update main’s size.
2) System.img is larger than expected. Just sum and update main’s size again.

Your original super.img file is now created, like Samsung does. Congrats!

Back in Windows:
1) Create, using 7zip, anyname.tar file cointaining just the super.img you created. Simple.
2) Open Odin, untick Auto Reboot, add anyname.tar file to AP, put your phone in Download Mode and flash it. Flash boot(NoForcedEnforce).tar the same way.
3) Reboot your phone, do a Factory Reset in original recovery.

In Android:
1) Install terminal emulator and run the following commands:
su
setenforce 0
getenforce (it should show Permissive)

Job is done.
Click to expand...
Hey,

I'm stuck at where the quote begins, and i get this error message:
Screenshot

Do you have a suggestion for me?

Thanks!
 
M

map220v

Member
Jul 26, 2016
49
36
18
Apr 20, 2020 at 8:21 PM
ToddNachste said:
By the way i found another way to get root but it's not tested yet:
0. Download with SamFirm the same firmware you’re running now and extract AP file from firmware archive
1. Extract boot.img.lz4 from AP file
2. Add boot.img.lz4 to .tar archive
3. Put this archive to the phone and patch it with magisk manager
4. Flash magisk_patched.tar with odin in AP
5. Then you should do factory reset and restart the phone
6. Install Magisk Manager and update environment
Of course it needs unlocked bootloader.
Sorry for my bad english, i wrote this without a translator.
Click to expand...
It's won't work. this phone uses system-as-root (no ramdisk in kernel).
We need to patch recovery.img instead. Right now flasing recovery.img useless because it's gives vbmeta error.
 
  • Like
Reactions: YOisuPU and kkosnuss
X

Xiomax

Member
Jan 5, 2013
17
5
0
Apr 20, 2020 at 8:51 PM
O

obodzin

Member
Nov 5, 2012
44
4
0
PL
Apr 21, 2020 at 2:08 PM
obodzin said:
Is there any way to debrand A51?
I downloaded the XEO rom (not branded), but after the flashing there are applications, old screen and the operator's logo.
I installed according to the instructions, I also tried with the pit file, but still the same.
Can anyone help? :(
Click to expand...
Someone solved this problem? Please help. :crying:
 
Y

YOisuPU

Member
Jul 29, 2019
25
16
0
Apr 22, 2020 at 3:18 AM
Hello everyone!
many thanks! phhusson map220v gabrielfrias
1) what do these numbers mean. ./lpmake --metadata-size 65536 - super-name super -metadata-slots 2 - device super: 4294967296 --group home:. I see a description of the remaining numbers.
2) is this instruction suitable for a phone with 6/128 memory or do you need to change the numbers mentioned above?
3) do we need a patch that is next to phhusson firmware?
4) what specific GSI firmware should I choose if I need the cleanest without gapps for this phone.
5) we flash it or not (((Permissive kernel (..drive.google /file/d/1Jq8...ew?usp=sharing) -thanks to map220v
How do you boot it and flash it? Edit: Nevermind, Samsung's ****ty broken secure boot only apply on recovery not boot.img. I ... s.)))
I apologize for the many questions they arise from the difficulties associated with the translation. many thanks!
 
  • Like
Reactions: ghaniso1
G

gabrielfrias

Senior Member
May 27, 2012
63
37
0
Apr 22, 2020 at 5:25 PM
Xiomax said:
It fails, am I doing something wrong here?
http://prntscr.com/s2wl2z
My phone also says "Custom Binary (Super) blocked by OEM lock", but i have the boot loader unlocked.
Click to expand...
try to relock and reunlock, than flash.

obodzin said:
Someone solved this problem? Please help. :crying:
Click to expand...
don't know. try to leave as is and debrand when TWRP is released.

YOisuPU said:
Hello everyone!
many thanks! phhusson map220v gabrielfrias
1) what do these numbers mean. ./lpmake --metadata-size 65536 - super-name super -metadata-slots 2 - device super: 4294967296 --group home:. I see a description of the remaining numbers.
2) is this instruction suitable for a phone with 6/128 memory or do you need to change the numbers mentioned above?
3) do we need a patch that is next to phhusson firmware?
4) what specific GSI firmware should I choose if I need the cleanest without gapps for this phone.
5) we flash it or not (((Permissive kernel (..drive.google /file/d/1Jq8...ew?usp=sharing) -thanks to map220v
How do you boot it and flash it? Edit: Nevermind, Samsung's ****ty broken secure boot only apply on recovery not boot.img. I ... s.)))
I apologize for the many questions they arise from the difficulties associated with the translation. many thanks!
Click to expand...
1) don't know, but I believe they are directions to partition creation. leave as they are.
2) I believe it is, since the original firmware is the same. do not change them.
3) no need to patch any file
4) I tryed GAPPS version only, but I think FLOSS and VANILLA are the ones you're looking for.
5) yes, flash it, without it, root would not be possible.
 
  • Like
Reactions: YOisuPU
R

Ricobal

New member
Apr 22, 2020
4
0
0
Apr 22, 2020 at 10:48 PM
gabrielfrias said:
it has to be the same firmware your're currently using on your device, so it's not possible to flash the same super.img
Click to expand...
Thnx for the quick reply
I saw it in the comments.
Is regional.
Maybe a long shot but can somebody do it or help me with this with my Version?
I cannot get Ubuntu to Work.
Sorry for my english
 
You must log in or register to reply here.

New posts

Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone