⚠️Galaxy A71 Root || Unlock Bootloader || Flash Official Firmware [Binary 1] February

[BK☑️]

can we unroot and recover the samsung knox?

we can't recover a tripped knox on newer samsung devices.

 

[H113408]

Ok ladies and gentlemen I finally got it working, and here's what I had to do

You'll need to install 7zip or something that handles TARs and LZ4 that you can grab from github it was the second result on google for me

Once you've patched the AP file in Magisk Manager and copy it back to your pc, Open up that tar file and delete all files except recovery.img and vbmeta.img

Then open the original prepatched AP file in 7Zip and extract the boot.img.lz4 then take that file and drag it onto the lz4.exe from the lz4 utilities

you should now have a nice clean uncompressed boot.img, put that back onto the phone and patch it with magisk manager, you should now have magisk_patched.img copy that back to the pc and rename it boot.img and put it in the tar file from earlier so you should have boot.img recovery.img and vbmeta.img

With just these 3 files in the tar you dont have to worry about wiping your data again and it will patch pretty fast

Open up ODIN again and select AP and choose your new tar file and flash it

Then shut down the phone fully and power it on while holding vol up till you get to the warning screen about the unlocked bootloader let go of vol up and press power to continue and you should find that it boots properly now and magisk manager will show that magisk is installed.

I tried what you described exactly, but it didn't work for me. I'm also a bit confused because all what magisk does is to patch 3 files, vbmeta - recovery and boot. So why do we need to patch the boot image again (separately) ?
Anyway even doing the steps you described I still got stuck on bootloop when trying to load magisk.

 

[r3d1x]

Ok ladies and gentlemen I finally got it working, and here's what I had to do

You'll need to install 7zip or something that handles TARs and LZ4 that you can grab from github it was the second result on google for me

Once you've patched the AP file in Magisk Manager and copy it back to your pc, Open up that tar file and delete all files except recovery.img and vbmeta.img

Then open the original prepatched AP file in 7Zip and extract the boot.img.lz4 then take that file and drag it onto the lz4.exe from the lz4 utilities

you should now have a nice clean uncompressed boot.img, put that back onto the phone and patch it with magisk manager, you should now have magisk_patched.img copy that back to the pc and rename it boot.img and put it in the tar file from earlier so you should have boot.img recovery.img and vbmeta.img

With just these 3 files in the tar you dont have to worry about wiping your data again and it will patch pretty fast

Open up ODIN again and select AP and choose your new tar file and flash it

Then shut down the phone fully and power it on while holding vol up till you get to the warning screen about the unlocked bootloader let go of vol up and press power to continue and you should find that it boots properly now and magisk manager will show that magisk is installed.

Okay, this method is working for me except the last, but i solved it:
I patched the AP file in Magisk Manager, copied back to my pc, opened the tar file with 7zip and deleted all files except recovery.img and vbmeta.img.
I opened the original prepatched AP file in 7Zip and extracted the boot.img.lz4 and dragged it to lz4.exe.
I copied the uncompressed boot.img to my phone and patched it in magisk manager, copied back the patched file to my pc and put it in the tar file, flashed with odin (before flashing I unticked the auto reboot), after it's done, I pressed and held volume down and power and when the screen went off, quickly changed to volume up and power button and hold until the bootloader warning appeared, I released the buttons, and I pressed the power button to continue to samsung logo, and my phone got bootloop (after a few seconds).
After it restarts and the screen went off I quickly pressed and held the volume up and power button until the bootloader warning appeared again, pressed the power button, and after the samsung logo appeared, quickly pressed and held the volume up until the stock recovery does not appear -> stock recovery -> mount system -> reboot to the system -> hold volume up and power button (!) -> bootloader warning - press power button to continue -> samsung logo -> press and hold the volume up until the recovery does not appear -> recovery -> reboot to the system -> wait until the bootloader warning (and do not press and hold volume up and power (!) ) -> press the power to continue -> samsung logo, and wait and the phone is booted and working with magisk root. If you reboot the phone or shutdown it, magisk root is still working without pressing volume up and power.

 

[eg74]

Okay, this method is working for me except the last, but i solved it:
I patched the AP file in Magisk Manager, copied back to my pc, opened the tar file with 7zip and deleted all files except recovery.img and vbmeta.img.
I opened the original prepatched AP file in 7Zip and extracted the boot.img.lz4 and dragged it to lz4.exe.
I copied the uncompressed boot.img to my phone and patched it in magisk manager, copied back the patched file to my pc and put it in the tar file, flashed with odin (before flashing I unticked the auto reboot), after it's done, I pressed and held volume down and power and when the screen went off, quickly changed to volume up and power button and hold until the bootloader warning appeared, I released the buttons, and I pressed the power button to continue to samsung logo, and my phone got bootloop (after a few seconds).
After it restarts and the screen went off I quickly pressed and held the volume up and power button until the bootloader warning appeared again, pressed the power button, and after the samsung logo appeared, quickly pressed and held the volume up until the stock recovery does not appear -> stock recovery -> mount system -> reboot to the system -> hold volume up and power button (!) -> bootloader warning - press power button to continue -> samsung logo -> press and hold the volume up until the recovery does not appear -> recovery -> reboot to the system -> wait until the bootloader warning (and do not press and hold volume up and power (!) ) -> press the power to continue -> samsung logo, and wait and the phone is booted and working with magisk root. If you reboot the phone or shutdown it, magisk root is still working without pressing volume up and power.

hi, I tried it this way, but when I try to flash the modified AP file with Odin, it says 'File analysis..' in Odin and doesn't go further (I've waited for more than 15 min, then broke up, reopened Odin and tried it again, same result). I did every step like you said, patched the AP file in Magisk Manager, copied back to my pc, opened the tar file with 7zip and deleted all files except recovery.img and vbmeta.img, etc.

Do you have any idea?

---------- Post added at 03:12 PM ---------- Previous post was at 03:03 PM ----------

I've tried rooting several times to no avail, I've unlocked and flashed everything with the patched magisk setup, I'm using the SM-A715F BTU firmware as that's what my phone was beforehand

When i try and do the volume up boot then release at the warning screen it just does a reboot cycle and never boots I have to force it it shut down and boot normally

I cant even restore phone to a point where SafetyNet validates so no Pokemon Go and such

same here, except that I'm using DBT firmware.

 

[Cyber Axe]

hi, I tried it this way, but when I try to flash the modified AP file with Odin, it says 'File analysis..' in Odin and doesn't go further (I've waited for more than 15 min, then broke up, reopened Odin and tried it again, same result). I did every step like you said, patched the AP file in Magisk Manager, copied back to my pc, opened the tar file with 7zip and deleted all files except recovery.img and vbmeta.img, etc.

Do you have any idea?

---------- Post added at 03:12 PM ---------- Previous post was at 03:03 PM ----------



same here, except that I'm using DBT firmware.

Since writing my initial post that I've discovered you don't need to use the vol up at boot thing you just turn it on and it boots into rooted OS with a successful SafetyNet check

As for your specific problem:
Do you have the same firmware version already installed on the phone as the tar you're trying to flash? If not flash the original tar with the BL, AP, CP and home csc file under csc (hoem CSC should mean you don't lose your data but i'd backup to be safe if you've not already and need to)

Are you flashing the tar as AP?

Are you using Odin v3.14.1?

If so, then it seems the tar is corrupt; It will take a long time on the original AP doing the file analysis due to the large file sizes but on the modified tar if done correctly then it should take less than 5 seconds.

---------- Post added at 10:54 AM ---------- Previous post was at 10:37 AM ----------

I tried what you described exactly, but it didn't work for me. I'm also a bit confused because all what magisk does is to patch 3 files, vbmeta - recovery and boot. So why do we need to patch the boot image again (separately) ?
Anyway even doing the steps you described I still got stuck on bootloop when trying to load magisk.

For me the boot.img did not patch correctly, I had to take the vanilla boot.img out of the original AP and patch it seperatly and put into the new tar, that for me made it work.

I do not know what is happeing on the low level as I'm not a developer of Magisk and did not go trawling through the logs for answers (though since it thinks it was successful i doubt the log would have shown anything)

The reason I tried doing the boot.img seperatly as that process is used on other phones that have a bare boot.img so i tried it and it worked when combined with the other files (I did try it on its own first)

 

[eg74]

Since writing my initial post that I've discovered you don't need to use the vol up at boot thing you just turn it on and it boots into rooted OS with a successful SafetyNet check

As for your specific problem:
Do you have the same firmware version already installed on the phone as the tar you're trying to flash? If not flash the original tar with the BL, AP, CP and home csc file under csc (hoem CSC should mean you don't lose your data but i'd backup to be safe if you've not already and need to)

Are you flashing the tar as AP?

Are you using Odin v3.14.1?

If so, then it seems the tar is corrupt; It will take a long time on the original AP doing the file analysis due to the large file sizes but on the modified tar if done correctly then it should take less than 5 seconds.

thanks for your reply.

yes, I use Odin v3.14.1. I repeated everything from scratch: downloaded the firmware via Frija, installed it (BL, AP, CP and CSC) to be sure it's the same, booted (no problem), installed Magisk Manager, put the AP file on my phone and patched it with Mgisk Manager, copied the patched AP file to my PC, opened it with 7zip, deleted everything but recovery.img and vbmeta.img, took the boot.img.lz4 from the original AP file and de-compressed it with lz4, put this file onto my phone and patched it with Magisk Manager, copied it back to my PC and renamed it to boot.img and added it to magisk_patched.tar so that there are 3 files in it (boot.img, recovery.img and vbmeta.img), then opened Odin as admin and tried to flash the modified tar as AP, sadly with the same result: in Odin it stays at 'File analysis..' and doesn't go further.

 

[H113408]

Since writing my initial post that I've discovered you don't need to use the vol up at boot thing you just turn it on and it boots into rooted OS with a successful SafetyNet check

As for your specific problem:
Do you have the same firmware version already installed on the phone as the tar you're trying to flash? If not flash the original tar with the BL, AP, CP and home csc file under csc (hoem CSC should mean you don't lose your data but i'd backup to be safe if you've not already and need to)

Are you flashing the tar as AP?

Are you using Odin v3.14.1?

If so, then it seems the tar is corrupt; It will take a long time on the original AP doing the file analysis due to the large file sizes but on the modified tar if done correctly then it should take less than 5 seconds.

---------- Post added at 10:54 AM ---------- Previous post was at 10:37 AM ----------



For me the boot.img did not patch correctly, I had to take the vanilla boot.img out of the original AP and patch it separately and put into the new tar, that for me made it work.

I do not know what is happening on the low level as I'm not a developer of Magisk and did not go trawling through the logs for answers (though since it thinks it was successful i doubt the log would have shown anything)

The reason I tried doing the boot.img separately as that process is used on other phones that have a bare boot.img so i tried it and it worked when combined with the other files (I did try it on its own first)

It did work at the end and even better than I expected (very strange). I don't have to boot into recovery in order to have magisk loaded, Magisk is loaded directly when booting into system (just like the old phones). Knowing this I flashed back the stock recovery to the phone and now it's working perfectly.
When I have some time I will see why this is happening but nothing is mentioned about this change on the Magisk documentation

 

[phsnake]

Just a wee question, if I want to root only (w/o unlocking bootloader) is enough to flash patched AP? Thanks 4 answer

 

[BK☑️]

Just a wee question, if I want to root only (w/o unlocking bootloader) is enough to flash patched AP? Thanks 4 answer

this is indeed a 'wee' question, since you can't root without unlocking bootloader.

 

[phsnake]

Maybe wrong formulation, if I want to root, is enough to flash AP? Unlock bootloader, then patch AP_*.tar using Magisk Manager, and afterwards flash patched version via ODIN? I know this are stupid questions, but from my experience usually (SG4-8, SG Tab etc.) was necessary to flash boot and recovery(at least for twrp) as well.THX

 

[warvegan]

Need some help here,

-In Odin, click on AP and select the patched tar file, Uncheck “Auto Reboot” and click on Install.

I used the "magisk.patched.tar" on odin as AP file and install it
It ended up wiping all my data on my phone
Any idea how to fix this ?

*Edit
Finally it works

 

[warvegan]

Does anyone have TWRP file for samsung A71 ?

 

[icerose34]

Hello
my phone is in U2
is there a possibility for root?

 

[awdrifter]

I used this tutorial for rooting the S10+.
https://youtu.be/o3a8YnWT3yk

however, I was told to flash not just the patched AP, but also the BL, CP, CSC with the stock files. Is this still the case with the A71? Thanks.

Seems like I have the One UI Version 2.0, is that why you mean by U2 firmware?

Sent from my SM-G955F using Tapatalk

---------- Post added at 02:52 AM ---------- Previous post was at 02:50 AM ----------

Need some help here,


I used the "magisk.patched.tar" on odin as AP file and install it
It ended up wiping all my data on my phone
Any idea how to fix this ?

*Edit
Finally it works

How did you get it to work?

Sent from my SM-G955F using Tapatalk

 

[awdrifter]

I followed the first post, but I'm getting bootloop after flashing the magisk_patched.tar. Please help.

Edit: The phone will boot normally if I don't try to boot it with Magisk (volumne up and power).

Followed Cyber Axe h113408's instruction on repatching the boot.img. https://forum.xda-developers.com/showpost.php?p=81802479&postcount=20

Then r3d1x's instructions on mounting the system in recovery. https://forum.xda-developers.com/showpost.php?p=81817333&postcount=23

Now I have root!

 

[Cyber Axe]

I followed the first post, but I'm getting bootloop after flashing the magisk_patched.tar. Please help.

Edit: The phone will boot normally if I don't try to boot it with Magisk (volumne up and power).

Followed h113408's instruction on repatching the boot.img. https://forum.xda-developers.com/showpost.php?p=81814413&postcount=22

Then r3d1x's instructions on mounting the system in recovery. https://forum.xda-developers.com/showpost.php?p=81817333&postcount=23

Now I have root!

I believe you mean Cyber Axe's instruction on re-patching the boot.img not h113408, he was replying to me

Glad it worked for you.

 

[awdrifter]

I believe you mean Cyber Axe's instruction on re-patching the boot.img not h113408, he was replying to me

Glad it worked for you.

Updated my post to reflect your original post. Thanks.

 

[hello_hello]

Updated my post to reflect your original post. Thanks.

Can you please explain what you have done especially the r3d1x post https://forum.xda-developers.com/showpost.php?p=81817333&postcount=23

Been reading that few times but I cant really understand the process.

Do you need to do that part? I mean after the tutorial by Cyber Axe, you did get bootloop and solved by using r3d1x?

Thanks

 

[awdrifter]

Can you please explain what you have done especially the r3d1x post https://forum.xda-developers.com/showpost.php?p=81817333&postcount=23

Been reading that few times but I cant really understand the process.

Do you need to do that part? I mean after the tutorial by Cyber Axe, you did get bootloop and solved by using r3d1x?

Thanks

I have followed the original post, got stuck on not being able to boot into the system with Vol Up + Power. I think means the patching of the boot.img has some issues. So I followed Cyber Axe's guide on how to patch the boot.img and reflash it with Odin.

After that, I just followed literally this part of R3d1x's post.

After it restarts and the screen went off I quickly pressed and held the volume up and power button until the bootloader warning appeared again, pressed the power button, and after the samsung logo appeared, quickly pressed and held the volume up until the stock recovery does not appear -> stock recovery -> mount system -> reboot to the system

After I did that I used Root Check and see that I have root.

 

[gabriel maciel ribeiro]

Freeefire